I have a single node, 1 shard/1 replica setup, and I'm using 0.17.8 with
the RabbitMQ river plugin. The thing is, when I restart ES, the river seems
to start consuming right away, even though the indices are still getting
allocated (I'm not sure what this means yet...). This seems to sometimes
corrupt the cluster, thought this could be due to other issues that I'm
trying to debug right now. In general, it'd be nice if I could validate
that the cluster started up properly before the river starts dumping docs
into it for indexing. Is there such a way right now?