Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: use DEBUG level log when F3 is not ready for participation #12700

Merged
merged 1 commit into from
Nov 18, 2024

Conversation

masih
Copy link
Member

@masih masih commented Nov 18, 2024

Related Issues

Proposed Changes

To reduce log verbosity change the log level for message indicating that F3 is not ready for participation yet. Because, the participation logic will reattempt after some backoff and these logs may at times become too verbose.

Additional Info

Checklist

Before you mark the PR ready for review, please make sure that:

To reduce log verbosity change the log level for message indicating that
F3 is not ready for participation yet. Because, the participation logic
will reattempt after some backoff and these logs may at times become too
verbose.

Fixes #12688
@masih masih added the skip/changelog This change does not require CHANGELOG.md update label Nov 18, 2024
@masih masih requested a review from Kubuxu November 18, 2024 09:41
@masih masih merged commit afd45db into master Nov 18, 2024
94 checks passed
@masih masih deleted the masih/f3-not-ready-warning branch November 18, 2024 11:31
rjan90 pushed a commit that referenced this pull request Nov 26, 2024
To reduce log verbosity change the log level for message indicating that
F3 is not ready for participation yet. Because, the participation logic
will reattempt after some backoff and these logs may at times become too
verbose.

Fixes #12688
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release/backport skip/changelog This change does not require CHANGELOG.md update
Projects
Status: ☑️ Done (Archive)
Development

Successfully merging this pull request may close these issues.

Fix F3 log warning when F3 is not running
3 participants