Tim, Quick question on this. Is this code in the master branch? If so this means that the offline shards and controllers are no longer in zookeeper correct?
Depending on the answers we may need to make some more updates to the console prior to releasing 0.2.4 Thanks, Chris On Tue, Sep 16, 2014 at 9:04 PM, Tim Williams (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/BLUR-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Tim Williams closed BLUR-342. > ----------------------------- > Resolution: Fixed > > This is now complete, any issues can be raised as new tickets (bugs/features) > >> Support full cluster operations on random ports >> ----------------------------------------------- >> >> Key: BLUR-342 >> URL: https://issues.apache.org/jira/browse/BLUR-342 >> Project: Apache Blur >> Issue Type: New Feature >> Components: Blur >> Affects Versions: 0.2.2 >> Reporter: Tim Williams >> Assignee: Tim Williams >> Fix For: 0.3.0, 0.2.4 >> >> >> Blur should be able to run in a full cluster environment on completely >> random ports. >> Some things that need to be accounted for in supporting random ports: >> 1) ThriftBlurControllerServer - binding needs fixed when multiple instances >> are running. >> 2) ThriftBlurShardServer - binding needs fixed when multiple instances are >> running. >> 3) BlurClient - add two new methods >> BlurClient.getClient() - use a default BlurConfiguration to build >> the conn string from ZK. >> BlurClient.getClient(BlurConfiguration conf) - use the passed >> conf to build the conn string from ZK. >> 4) Blur GUI ports need randomized >> 5) DistributedLayoutFactory API should change to only give layout strategies >> the online shard servers to work with. >> 6) Remove the persistent registered shard servers *** breaking change *** > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332)
