For keyed data, the mirror maker will just distribute data based on
hash(key)%num_partitions. If num_partitions is different in the target DC
(which it is), a message that lived in partition 0 in the source cluster
might end up in partition 10 in the target cluster.

On Mon, Aug 11, 2014 at 7:23 PM, Bhavesh Mistry <[EMAIL PROTECTED]>
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