Please specify both the brokers in same order for each producer as follows:

The reason I suspect second broker is not functioning as expected because
broker 0 is leader for both partitions as well as it is the only isr.
Assuming producer on second machine can connect to broker on first machine,
it should be able to publish to the first broker which is leader.

You could also check in zookeeper broker node registry to ensure both
brokers are in fact available.

/brokers/ids/[0...N] --> host:port (ephemeral node)

and broker topic registry

/brokers/topics/[topic]/[0...N] --> nPartions (ephemeral node)
On Mon, Nov 11, 2013 at 10:39 PM, ji yan <[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