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
Describe the bug
Search rejection for every shard is being logged even when the debug logging is not enabled. Logging an exception is very expensive as the resulting message can be big wreaking havoc on memory, CPU (due to GC) and disk throughput. Regression commit came from ES 7.10 here.
Search rejection is a mechanism for ensuring resiliency and preventing the cluster from getting overwhelmed. Because of this issue, the cluster degrades further once we see search thread pool rejections
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
The logging should only happen when the debug log is enabled
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
OS: [e.g. iOS]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Search rejection for every shard is being logged even when the debug logging is not enabled. Logging an exception is very expensive as the resulting message can be big wreaking havoc on memory, CPU (due to GC) and disk throughput. Regression commit came from ES 7.10 here.
Search rejection is a mechanism for ensuring resiliency and preventing the cluster from getting overwhelmed. Because of this issue, the cluster degrades further once we see search thread pool rejections
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The logging should only happen when the debug log is enabled
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: