Github user JonathanRider commented on the issue:
    Just ran it on quickdev where I set the in the global json file to 
"node2,node1" where node2 doesn't exist as it is a single node vagrant.
    Using my patch, it writes to ES without a problem as it fails to use node2, 
so it switches to node1.
    I then compiled master and did the same thing and received this error since 
node2 doesn't exist and it fails to use the second host.:
    2016-12-01 21:41:18.942 o.a.m.w.BulkWriterComponent [ERROR] Failing 5 tuples
    org.elasticsearch.client.transport.NoNodeAvailableException: None of the 
configured nodes are available: 

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 or file a JIRA ticket
with INFRA.

Reply via email to