Uh oh!
There was an error while loading. Please reload this page.
HBASE-27873 Asyncfs may print too many WARN logs when replace writer - #5243
HBASE-27873 Asyncfs may print too many WARN logs when replace writer#5243thangTang wants to merge 1 commit into
Conversation
Apache-HBase
commented
May 18, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
May 18, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
May 18, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
May 19, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
May 19, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
May 19, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
May 19, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
May 19, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
May 19, 2023
🎊 +1 overall
This message was automatically generated. |
Apache9
commented
May 19, 2023
Since we use exponential backoff here, the log output is acceptable? We will soon increase the interval between each warn message? |
thangTang
commented
May 23, 2023
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.
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? |
Apache9
commented
Jun 16, 2023
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. Thanks. |
Apache9
commented
Jun 30, 2023
Any updates here? Thanks. |
No description provided.