narendly opened a new issue #1106:
URL: https://github.com/apache/helix/issues/1106
Creating an issue for tracking.
/**
* Retrieve Helix manager property. It returns the property object with
default values.
* Clients may override these values.
*/
public HelixManagerProperty getHelixManagerProperty(String zkAddress,
String clusterName) {
// This configAccessor is a dedicated zkclient because HelixManager is
single realm
HelixZkClient.ZkConnectionConfig connectionConfig =
new HelixZkClient.ZkConnectionConfig(zkAddress);
HelixZkClient zkClient =
DedicatedZkClientFactory.getInstance().buildZkClient(connectionConfig);
ConfigAccessor configAccessor = new ConfigAccessor(zkClient);
CloudConfig cloudConfig;
// The try-catch logic is for backward compatibility reason only. Even
if the cluster is not set
// up yet, constructing a new ZKHelixManager should not throw an
exception
try {
cloudConfig =
configAccessor.getCloudConfig(clusterName) == null ?
buildEmptyCloudConfig(clusterName)
: configAccessor.getCloudConfig(clusterName);
} catch (HelixException e) {
cloudConfig = buildEmptyCloudConfig(clusterName);
}
configAccessor.close();
Properties properties = new Properties();
Need to use a dedicated ZkClient instead of creating a configaccessor with a
sharedZkClient. Only an issue in locally run tests.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
