You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we use exponential backoff here, the log output is acceptable? We will soon increase the interval between each warn message?
At client side, we have configuration to not output the error message in the first several retries, it is called hbase.client.start.log.errors.counter. Maybe we can apply the same pattern here?
Since we use exponential backoff here, the log output is acceptable? We will soon increase the interval between each warn message?
Yes you are right, but still offen seen it. And its level is WARN, this makes me nervous, But after doing a little research I figured out that this shouldn't be a problem, that's why I want to change it.
At client side, we have configuration to not output the error message in the first several retries, it is called hbase.client.start.log.errors.counter. Maybe we can apply the same pattern here?
Can do that, but this config is a client side config(as its name), do you think we need to introduce a new server side config?
Since we use exponential backoff here, the log output is acceptable? We will soon increase the interval between each warn message?
Yes you are right, but still offen seen it. And its level is WARN, this makes me nervous, But after doing a little research I figured out that this shouldn't be a problem, that's why I want to change it.
At client side, we have configuration to not output the error message in the first several retries, it is called hbase.client.start.log.errors.counter. Maybe we can apply the same pattern here?
Can do that, but this config is a client side config(as its name), do you think we need to introduce a new server side config?
We can add a new config for this. And the default value should be 0, to keep the old behavior at least on 2.x. And we can discuss a better value for 3.x.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.