The current node should be included in the total expected number of nodes in the entire cluster at the very least. Without this fix, the configuration is a node short and recovery of the cluster might begin before all of the nodes have reconvened.

The next line, which amends `elasticsearch_instances`, is only used for the Zen discovery module configuration. Each node's own host name isn't necessary for unicast Zen discovery (it has already discovered itself). I did a little reading after your note, however, and at some point, @kimchy [suggests its ok to leave the node's own host in that list](http://elasticsearch-users.115913.n3.nabble.com/Replication-basics-tt3649749.html#a3651360). I'll happily revise my pull request to include removal of the constraint in `elasticsearch_instances` for the `discovery.zen` section as well.