update todo
avoid accidental ES cluster forming with other ES nodes

besides than the config change, if you actually do accidentally
join a cluster, during startup you could get an error like this:

rawes.elastic_exception.ElasticException: ElasticSearch Error:
u'{"error":"RemoteTransportException[[Ego the Living
Planet][inet[/10.90.4.240:9300]][indices/create]]; nested:
IndexAlreadyExistsException[[anthracite] Already exists];
","status":400}'

that's why the check for the IndexAlreadyExistsException needed
some adjusting