Hi Folks, For context, I'm leveraging the ES BulkProcessor class although I don't believe that matters much in this scenario.
I wanted to test the scenario where my ES cluster was offline for a bit to entire my usage of BulkProcessor via the Java API could sustain and recover from the outage. Unfortunately on both 1.2.0 and 1.2.1 it appears the ES background worker thread dies in this scenario. In this test, I'm only ever sending in IndexRequests. Exception in thread "elasticsearch[PROC1][generic][T#2]" java.lang.NullPointerException at org.elasticsearch.action.bulk.TransportBulkAction.setResponseFailureIfIndexMatches(TransportBulkAction.java:178) at org.elasticsearch.action.bulk.TransportBulkAction.access$100(TransportBulkAction.java:65) at org.elasticsearch.action.bulk.TransportBulkAction$1.onFailure(TransportBulkAction.java:137) at org.elasticsearch.action.support.TransportAction$ThreadedActionListener$2.run(TransportAction.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626) at java.lang.Thread.run(Thread.java:804) I would indeed expect the action to fail but not to this extent. Thoughts? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/05fe8053-5b6b-4672-a0c3-912dd2fd29ab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
