-
Notifications
You must be signed in to change notification settings - Fork 984
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
StatsdMeterRegistry infinite reconnect loop with Reactor 2020.0 #2378
Comments
This is obviated in 1.5.x and 1.6.x for now by reverting the upgrade to Reactor 2020.0 for 1.5.9 and 1.6.2 - it was only ever released in version 1.5.8. Considering the apparent risk, the Reactor 2020.0 upgrade will be made for 1.7 instead of in patch versions, and we will need to figure out how to avoid this issue when making that upgrade. |
@shakuzen I was able to repro the micrometer issue using There are three remarks, I would like to highlight:
|
@jonatan-ivanov can we replicate this with the latest versions? |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open. |
In some ad hoc testing, I noticed that behavior like described in #2177 is back again in 1.5.8, which contains #2359 upgrading reactor, reactor-netty, and netty. Since there were no other related changes in 1.5.8, it seems very likely that change is causing this issue to resurface. I will have to investigate more to understand why previously applied measures are no longer working.
Reverting the upgrade until a fix can be worked out may be the best course of action.
When the issue happens, which seems to be some variable amount of time after startup, with the statsd server down the whole time, DEBUG logs like the following are output rapidly and until the application is stopped:
The text was updated successfully, but these errors were encountered: