helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kanak Biscuitwala (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HELIX-344) Add app-specific ideal state validation
Date Fri, 13 Dec 2013 01:38:07 GMT

     [ https://issues.apache.org/jira/browse/HELIX-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kanak Biscuitwala resolved HELIX-344.

    Resolution: Fixed

Done. Review: https://reviews.apache.org/r/16199/

This is checked into both 0.6.x and 0.7.y. To use, do something like:

HelixAdmin helixAdmin = controller.getClusterManagmentTool();
Map<String, String> properties = Maps.newHashMap();
properties.put("IdealStateRule!sampleRuleName", "IDEAL_STATE_MODE=CUSTOMIZED,STATE_MODEL_DEF_REF=MasterSlave");
helixAdmin.setConfig(new HelixConfigScopeBuilder(ConfigScopeProperty.CLUSTER).forCluster(clusterName).build(),

It's important that the "IdealStateRule!" prefix exists. All other simple fields in the cluster
configuration will be ignored.

> Add app-specific ideal state validation
> ---------------------------------------
>                 Key: HELIX-344
>                 URL: https://issues.apache.org/jira/browse/HELIX-344
>             Project: Apache Helix
>          Issue Type: Improvement
>            Reporter: Kanak Biscuitwala
>            Assignee: Kanak Biscuitwala
> The app may have its own rules about ideal states that can live on its cluster. We should
support by providing a way to specify those rules and then not running the pipeline for ideal
states that do not adhere to them.

This message was sent by Atlassian JIRA

View raw message