What is the bug?
During startup several warnings are logged (37 lines of the same message):
[WARN ][o.o.p.c.ThreadPoolMetricsCollector] [xxx] Fail to read queue capacity via reflection
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
Startup without this warning or at least showing the root cause of the warning
What is your host/environment?
OS: Ubuntu
Version 22.04 LTS
Do you have any additional context?
The warnings occured after upgrading opensearch from 2.9 to 2.11
The class ThreadPoolMetricsCollector is logging the warning, but the exception itself is not logged. So, no further information about the deeper lying error is reported.
Maybe the logging can be adjusted to figure out the root cause (if the reason of the warning can't be found)
What is the bug? During startup several warnings are logged (37 lines of the same message): [WARN ][o.o.p.c.ThreadPoolMetricsCollector] [xxx] Fail to read queue capacity via reflection
How can one reproduce the bug? Steps to reproduce the behavior:
What is the expected behavior? Startup without this warning or at least showing the root cause of the warning
What is your host/environment?
Do you have any additional context? The warnings occured after upgrading opensearch from 2.9 to 2.11
The class ThreadPoolMetricsCollector is logging the warning, but the exception itself is not logged. So, no further information about the deeper lying error is reported.
Maybe the logging can be adjusted to figure out the root cause (if the reason of the warning can't be found)