If you are using 0.7.1, it's probably better to use helixconnection directly instead of helixmanager.
Kanak/Jason, can you please confirm. any recommendation workaround before this is fixed? Seems the latest tutorial is updated not to use HelixManager for controller and participant. On Thu, Jul 9, 2015 at 10:02 PM, Zhen Zhang <[email protected]> wrote: > This seems to be a bug. Need to fix it. Created a jira to track this: > https://issues.apache.org/jira/browse/HELIX-605 > > > On Thu, Jul 9, 2015 at 9:03 PM, Changgeng Li <[email protected]> > wrote: > >> Hello, >> >> We are relying on HelixManager.isConnected() method for health check. >> >> >> Following code print true in 0.6.2, but print false in 0.7.1 >> >> HelixManager helixManager = HelixManagerFactory.getZKHelixManager( >> "test-cluster", >> "localhost_9001", >> InstanceType.CONTROLLER_PARTICIPANT, >> "localhost:2181" >> ); >> helixManager.connect(); >> Thread.sleep(5000); >> System.out.println("connected: " + helixManager.isConnected()); >> Thread.sleep(5000); >> >> >
