Home | About | Sematext search-lucene.com search-hadoop.com
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
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> Proper distribution of topics vs consumers


Copy link to this message
-
Re: Proper distribution of topics vs consumers
Hundreds to a few thousands topics should be fine. Depending on the volume
of the data, you may need more brokers to support the load.

Thanks,

Jun
On Mon, Apr 22, 2013 at 8:12 PM, Alex Zuzin <[EMAIL PROTECTED]> wrote:

> Hi all,
>
> I'm dealing with an application where the main semantic entity (equivalent
> to a topic) will take on several hundreds, maybe a couple thousand values.
> The current design calls for topic per entity.
> Is running hundreds, possibly low thousands of topics a sensible thing to
> do?
> If not, is there a canonical multiplexing technique?
>
> Thank you kindly,
> KCBO,
> --
> "If you can't conceal it well, expose it with all your might"
> Alex Zuzin
>
>

 
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