monitoring the process and keep trying to connect to the port?

Every leader in a Kafka cluster exposes the UnderReplicatedPartitionCount
metric. The safest way to issue controlled shutdown is to wait until that
metric reports 0 on the brokers. If you try to shutdown the last broker in
the ISR, the controlled shutdown cannot succeed since there is no other
broker to move the leader to. Waiting until under replicated partition
count hits 0 prevents you from hitting this issue.

This also solves the problem of waiting until the broker comes up since you
will automatically wait until the broker comes up and joins ISR.
On Thu, Aug 29, 2013 at 12:59 PM, Sam Meder <[EMAIL PROTECTED]>wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB