Sure, looking at the top of the logs for the 17th (when the problem started) I can see...
[2014-02-17 00:00:00,278][INFO ][cluster.metadata ] [Caretaker] [logstash-2014.02.17] creating index, cause [auto(bulk api)], shards [5]/[1], mappings [_default_] [2014-02-17 00:00:00,336][WARN ][transport.netty ] [Caretaker] Message not fully read (request) for [5684538] and action [cluster/nodeIndexCreated], resetting [2014-02-17 00:00:00,336][WARN ][transport.netty ] [Caretaker] Message not fully read (request) for [5358797] and action [cluster/nodeIndexCreated], resetting [2014-02-17 00:00:00,336][WARN ][transport.netty ] [Caretaker] Message not fully read (request) for [6186213] and action [cluster/nodeIndexCreated], resetting ... before it gets into the usual stuff about updating dynamic mappings for the types I've got. It only occurs in the logs on one of the nodes and it's the node which is currently the master (and I haven't purposely changed that by restarting nodes or anything similar since then). The logs on the other nodes don't pick up until 09:00 when I was restarting the Logstash processes which had joined the cluster. That pattern of logs actually occurs every day when the new index is created (given the message content I'm assuming that's the case). -- 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/8a9970ce-563c-4dd5-a14b-55079018aedf%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
