-
Notifications
You must be signed in to change notification settings - Fork 102
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
[BUG] Polluting log entry regarding destination migration #1183
Labels
bug
Something isn't working
Comments
still there in v2.11 |
1 task
closing in favor of #1356 |
i am seeing this is version 2.16.0 |
Can confirm i see this all the time [in OS_2.16]
|
OS 2.17, messages still in log |
@riysaxen-amzn could you please reopen this issue? Or shall we create a new one? btw, there is a suggestion there: #1356 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the bug?
There is a specific log that keeps on appearing quite frequently on all OpenSearch clusters (even fresh installations). While it does not somehow harm the cluster, its consistent presence is quite annoying:
I tracked this message on DestinationMigrationCoordinator.kt. I am not sure what is exactly wrong there, but something is.
There are couple of related threads already on the forums, like here and here.
And if you google "Detected cluster change event for destination migration", you'll see that it appears on many logs, for unrelated issues, so my guess is that it's just polluting logs.
How can one reproduce the bug?
Steps to reproduce the behavior:
Just bootstrap a new cluster and check the output logs.
What is the expected behavior?
Not to produce such a polluting log.
What is your host/environment?
The text was updated successfully, but these errors were encountered: