they are, mainly to drive startup/shutdown/status scripts. there's still some outstanding questions with respect to a blur-managed cluster (as opposed to a yarn managed one) that still need thought through - random ports are but a pit-stop on the journey ahead;)
--tim On Wed, Sep 17, 2014 at 12:05 PM, Chris Rohr <[email protected]> wrote: > So, the console today uses Zookeeper not Thrift for the node > information. So that will have to be redone. On a related note, are > there still going to be files in the blur directory that list all of > the nodes (i.e. conf/shards, conf/controllers, etc)? > > On Wed, Sep 17, 2014 at 11:58 AM, Tim Williams <[email protected]> wrote: >> On Wed, Sep 17, 2014 at 11:54 AM, Chris Rohr <[email protected]> wrote: >>> 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 >> >> That's right, if you using thrift api nothing should be "broke" in a >> real sense. It'll just never actually report anything as being >> offline because shardServerList == onlineShardServers and the same for >> controllers. If you still want the console to report 'offline' shards >> you'll want to create a local cache with a a configured expiry I >> guess. >> >> Thanks, >> --tim
