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
Blur >> mail # dev >> cluster on fully random ports


Copy link to this message
-
cluster on fully random ports
Does someone know what all needs to happen to allow a real [non-Mini]
cluster to run on fully random ports?  Currently it looks like:

ThriftBlurControllerServer - binding needs fixed when multiple
instances are running
ThriftBlurShardServer - binding needs fixed when multiple instances are running
BlurClient - needs a way to accept a ZK quorum as a connection string
and discover controllers from ZK.

The controllers already rely on ZK for the shard connections so that
should "just work" I reckon.

what else?

Thanks,

 
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