Github user static-max commented on the issue:
https://github.com/apache/flink/pull/2861
In my tests BulkItemResponse.getFailure().getCause() returns a
RemoteTransportException like this:
`RemoteTransportException[[Harrier][127.0.0.1:9302][indices:data/write/bulk[s]]];
nested:
RemoteTransportException[[Harrier][127.0.0.1:9302][indices:data/write/bulk[s][p]]];
nested: EsRejectedExecutionException[rejected execution of
org.elasticsearch.transport.TransportService$4@3a0f3a6e on
EsThreadPoolExecutor[bulk, queue capacity = 2,
org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@5ac266bd[Running,
pool size = 8, active threads = 8, queued tasks = 2, completed tasks = 206]]];`
So the nested Exception needs to be checked. That's possible, I will
implement that change.
The last to Exceptions are common when a new Index gets created (if you
have new index by day for example), or when a node leaves the cluster and no
master can be elected (no quorum),
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
