Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
1.40.0
-
None
-
None
Description
Currently, if there is a failure to update elasticsearch indexes such as:
[pool-12-thread-1] org.apache.jackrabbit.oak.plugins.index.elastic.index.ElasticBulkProcessorHandler ElasticIndex Update Bulk Failure : Bulk with id 1 threw an error java.net.ConnectException: Timeout connecting to [<ES_SERVER>:<ES_PORT>] at org.apache.http.nio.pool.RouteSpecificPool.timeout(RouteSpecificPool.java:169) [org.apache.jackrabbit.oak-search-elastic:1.40.0.T20210628142906-c91e018] at org.apache.http.nio.pool.AbstractNIOConnPool.requestTimeout(AbstractNIOConnPool.java:628) [org.apache.jackrabbit.oak-search-elastic:1.40.0.T20210628142906-c91e018] at org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.timeout(AbstractNIOConnPool.java:894) [org.apache.jackrabbit.oak-search-elastic:1.40.0.T20210628142906-c91e018] at org.apache.http.impl.nio.reactor.SessionRequestImpl.timeout(SessionRequestImpl.java:184) [org.apache.jackrabbit.oak-search-elastic:1.40.0.T20210628142906-c91e018] at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processTimeouts(DefaultConnectingIOReactor.java:214) [org.apache.jackrabbit.oak-search-elastic:1.40.0.T20210628142906-c91e018]
there is no way of knowing if there is any data loss or not. We should enahance this exception to include the list of documents that were part of the bulk update