[
https://issues.apache.org/jira/browse/HELIX-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhen Zhang updated HELIX-522:
-----------------------------
Description:
We are seeing a couple of use cases where an online service may need to roll
out a set of new configs in a coordinated way without bouncing the service.
Helix can be extended to support this. The basic idea is to generalize
ideal-state to support multi-dimensional mappings. Currently Helix uses
ideal-state to define the target mapping from a partition to the placement and
state of the partition (i.e. partition->(placement, state). The mapping can be
extended to support another attribute, say config-version, so it would be
partition->(placement, state, config-version). Helix controller is then able to
bring the system to the target mappings in a coordinated way. Here is a high
level design for this:
https://cwiki.apache.org/confluence/display/HELIX/Helix+Support+for+Dynamic+Config
was:
We are seeing a couple of use cases where an online service may need to roll
out a set of new configs in a coordinated way without bouncing the service.
Helix can be extended to support this. The basic idea is to generalize
ideal-state to support multi-dimensional mappings. Currently Helix uses
ideal-state to define the target mapping from a partition to the placement and
state of the partition (i.e. partition->(placement, state). The mapping can be
extended to support another attribute, say config-version, so it would be
partition->(placement, state, config-version). Helix controller is then able to
bring the system to the target mappings in a coordinated way. Here is a high
level design for this:
https://cwiki.apache.org/confluence/display/HELIX/Support+Dynamic+Config
> Support dynamic config by Helix
> -------------------------------
>
> Key: HELIX-522
> URL: https://issues.apache.org/jira/browse/HELIX-522
> Project: Apache Helix
> Issue Type: New Feature
> Reporter: Zhen Zhang
>
> We are seeing a couple of use cases where an online service may need to roll
> out a set of new configs in a coordinated way without bouncing the service.
> Helix can be extended to support this. The basic idea is to generalize
> ideal-state to support multi-dimensional mappings. Currently Helix uses
> ideal-state to define the target mapping from a partition to the placement
> and state of the partition (i.e. partition->(placement, state). The mapping
> can be extended to support another attribute, say config-version, so it would
> be partition->(placement, state, config-version). Helix controller is then
> able to bring the system to the target mappings in a coordinated way. Here is
> a high level design for this:
> https://cwiki.apache.org/confluence/display/HELIX/Helix+Support+for+Dynamic+Config
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
