That's interesting. The issue is that we somehow are missing a
response for [libomirror8,3]
specified in the request. I don't know how this is happening in the broker
though. Are you using the latest code in the 0.8 branch?

 Incomplete response (ProducerResponse(334159,Map([libomirror8,9] ->
ProducerResponseStatus(0,96820), [libomirror8,6] ->
ProducerResponseStatus(2,0), [libomirror8,0] ->
ProducerResponseStatus(0,0)))) for producer request (Name: ProducerRequest;
Version: 0; CorrelationId: 334159; ClientId: ProducerPerformance;
RequiredAcks: -1; AckTimeoutMs: 3000 ms; TopicAndPartition: [libomirror8,9]
-> 102660,[libomirror8,6] -> 102660,[libomirror8,3] ->
102660,[libomirror8,0] -> 102660)


On Thu, Jun 6, 2013 at 8:17 AM, Yu, Libo <[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