explicit exception handling of SocketTimeoutException on search request
Explicitly handle SocketTimeoutException
on socket timeouts. In absence of this, Search service have high number of generic failure with 500 error code, making it hard to distinguish real issue with long running queries.
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [NO]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
Google Cloud -
IBM
Does this introduce a breaking change?
- [NO]