[jira] [Assigned] (HELIX-526) sensors automatically move to their proper names upon removal of the tags
[ https://issues.apache.org/jira/browse/HELIX-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson reassigned HELIX-526: Assignee: Xia Lei > sensors automatically move to their proper names upon removal of the tags > - > > Key: HELIX-526 > URL: https://issues.apache.org/jira/browse/HELIX-526 > Project: Apache Helix > Issue Type: Bug >Reporter: John Francis Unson >Assignee: Xia Lei > Original Estimate: 24h > Remaining Estimate: 24h > > - InstanceMonitor.Sensor_ParticipantStatus seems working > - PerInstanceResourceMonitor.Sensor_ParticipantStatus...PartitionGauge seems > not working -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HELIX-526) sensors automatically move to their proper names upon removal of the tags
[ https://issues.apache.org/jira/browse/HELIX-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-526: - Sprint: Scrumban #4, Scrumban #5 (was: Scrumban #4) > sensors automatically move to their proper names upon removal of the tags > - > > Key: HELIX-526 > URL: https://issues.apache.org/jira/browse/HELIX-526 > Project: Apache Helix > Issue Type: Bug >Reporter: John Francis Unson >Assignee: Xia Lei > Original Estimate: 24h > Remaining Estimate: 24h > > - InstanceMonitor.Sensor_ParticipantStatus seems working > - PerInstanceResourceMonitor.Sensor_ParticipantStatus...PartitionGauge seems > not working -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (HELIX-525) Drop a partition from resource ideal-state shall bring partition to initial state and then DROPPED state
[ https://issues.apache.org/jira/browse/HELIX-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson closed HELIX-525. > Drop a partition from resource ideal-state shall bring partition to initial > state and then DROPPED state > > > Key: HELIX-525 > URL: https://issues.apache.org/jira/browse/HELIX-525 > Project: Apache Helix > Issue Type: Bug >Reporter: Zhen Zhang >Assignee: Xia Lei > Original Estimate: 24h > Remaining Estimate: 24h > > If we manually remove a partition from ideal-state, Helix should bring the > partition to initial state (e.g. OFFLINE) on all hosts and then to DROPPED > state. > - Add an integration test to verify this (for AUTO, SEMI_AUTO, and CUSTOM > modes) > - Fix it if not behave in the expected way -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HELIX-525) Drop a partition from resource ideal-state shall bring partition to initial state and then DROPPED state
[ https://issues.apache.org/jira/browse/HELIX-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson resolved HELIX-525. -- Resolution: Fixed > Drop a partition from resource ideal-state shall bring partition to initial > state and then DROPPED state > > > Key: HELIX-525 > URL: https://issues.apache.org/jira/browse/HELIX-525 > Project: Apache Helix > Issue Type: Bug >Reporter: Zhen Zhang >Assignee: Xia Lei > Original Estimate: 24h > Remaining Estimate: 24h > > If we manually remove a partition from ideal-state, Helix should bring the > partition to initial state (e.g. OFFLINE) on all hosts and then to DROPPED > state. > - Add an integration test to verify this (for AUTO, SEMI_AUTO, and CUSTOM > modes) > - Fix it if not behave in the expected way -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HELIX-526) Removing a tag should automatically remove the sensor.
[ https://issues.apache.org/jira/browse/HELIX-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-526: - Remaining Estimate: 24h Original Estimate: 24h > Removing a tag should automatically remove the sensor. > -- > > Key: HELIX-526 > URL: https://issues.apache.org/jira/browse/HELIX-526 > Project: Apache Helix > Issue Type: Bug >Reporter: John Francis Unson > Original Estimate: 24h > Remaining Estimate: 24h > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HELIX-526) Removing a tag should automatically remove the sensor.
[ https://issues.apache.org/jira/browse/HELIX-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-526: - Sprint: Scrumban #4 > Removing a tag should automatically remove the sensor. > -- > > Key: HELIX-526 > URL: https://issues.apache.org/jira/browse/HELIX-526 > Project: Apache Helix > Issue Type: Bug >Reporter: John Francis Unson > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HELIX-525) Drop a partition from resource ideal-state shall bring partition to initial state and then DROPPED state
[ https://issues.apache.org/jira/browse/HELIX-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-525: - Remaining Estimate: 24h Original Estimate: 24h > Drop a partition from resource ideal-state shall bring partition to initial > state and then DROPPED state > > > Key: HELIX-525 > URL: https://issues.apache.org/jira/browse/HELIX-525 > Project: Apache Helix > Issue Type: Bug >Reporter: Zhen Zhang > Original Estimate: 24h > Remaining Estimate: 24h > > If we manually remove a partition from ideal-state, Helix should bring the > partition to initial state (e.g. OFFLINE) on all hosts and then to DROPPED > state. > - Add an integration test to verify this > - Fix it if not behave in the expected way -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HELIX-526) Removing a tag should automatically remove the sensor.
John Francis Unson created HELIX-526: Summary: Removing a tag should automatically remove the sensor. Key: HELIX-526 URL: https://issues.apache.org/jira/browse/HELIX-526 Project: Apache Helix Issue Type: Bug Reporter: John Francis Unson -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HELIX-525) Drop a partition from resource ideal-state shall bring partition to initial state and then DROPPED state
[ https://issues.apache.org/jira/browse/HELIX-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-525: - Sprint: Scrumban #4 > Drop a partition from resource ideal-state shall bring partition to initial > state and then DROPPED state > > > Key: HELIX-525 > URL: https://issues.apache.org/jira/browse/HELIX-525 > Project: Apache Helix > Issue Type: Bug >Reporter: Zhen Zhang > > If we manually remove a partition from ideal-state, Helix should bring the > partition to initial state (e.g. OFFLINE) on all hosts and then to DROPPED > state. > - Add an integration test to verify this > - Fix it if not behave in the expected way -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HELIX-489) Write or rewrite examples using the new API
[ https://issues.apache.org/jira/browse/HELIX-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-489: - Assignee: Xia Lei > Write or rewrite examples using the new API > --- > > Key: HELIX-489 > URL: https://issues.apache.org/jira/browse/HELIX-489 > Project: Apache Helix > Issue Type: Sub-task >Reporter: Kanak Biscuitwala >Assignee: Xia Lei > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HELIX-372) 0.7 cleanup
[ https://issues.apache.org/jira/browse/HELIX-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-372: - Sprint: Scrumban #1, Scrumban #2, Scrumban #3 (was: Scrumban #1, Scrumban #2) > 0.7 cleanup > --- > > Key: HELIX-372 > URL: https://issues.apache.org/jira/browse/HELIX-372 > Project: Apache Helix > Issue Type: Improvement >Reporter: Kanak Biscuitwala > > This is an umbrella issue for cleanup tasks related to 0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HELIX-512) add back HelixManager#getHealthReportCollector() interface to 0.6.x
[ https://issues.apache.org/jira/browse/HELIX-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-512: - Sprint: Scrumban #3 > add back HelixManager#getHealthReportCollector() interface to 0.6.x > --- > > Key: HELIX-512 > URL: https://issues.apache.org/jira/browse/HELIX-512 > Project: Apache Helix > Issue Type: Bug >Reporter: Zhen Zhang >Assignee: Zhen Zhang > > add back HelixManager#getHealthReportCollector() interface to 0.6.x since it > breaks backward compatibility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HELIX-514) ZkBaseDataAccessor#set() should throw BadVersionException instead of return false in case of version mismatch
[ https://issues.apache.org/jira/browse/HELIX-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-514: - Sprint: Scrumban #3 > ZkBaseDataAccessor#set() should throw BadVersionException instead of return > false in case of version mismatch > - > > Key: HELIX-514 > URL: https://issues.apache.org/jira/browse/HELIX-514 > Project: Apache Helix > Issue Type: Bug >Reporter: Zhen Zhang >Assignee: Zhen Zhang > > ZkBaseDataAccessor#set() should throw BadVersionException instead of return > false in case of version mismatch, since caller (e.g. > HelixGroupCommit#commit()) may need to distinguish between fatal error and > transient error (e.g. version mismatch) so it can retry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HELIX-513) ZKHelixAdmin#rebalance with group uses instances from other groups
[
https://issues.apache.org/jira/browse/HELIX-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Francis Unson updated HELIX-513:
-
Sprint: Scrumban #3
> ZKHelixAdmin#rebalance with group uses instances from other groups
> --
>
> Key: HELIX-513
> URL: https://issues.apache.org/jira/browse/HELIX-513
> Project: Apache Helix
> Issue Type: Bug
> Components: helix-core
>Affects Versions: 0.7.1, 0.6.3
>Reporter: Greg Brandt
>
> For example, consider a cluster with one instance with tag NOT_YOURS and a
> resource whose ideal state has INSTANCE_GROUP_TAG=MINE. If we call
> {code}
> manager.rebalance("MY_CLUSTER", "MY_RESOURCE", 1, null, "MINE")
> {code}
> Helix will find no instances with the tag "MINE", so it will instead use all
> available instances in the cluster to perform the rebalance.
> This has undesirable effects when groups are used for multi-tenant clusters
> (i.e. subsets of instances belong to individual tenants, and tenants should
> not share instances).
> Better behavior might be to error out at the point no tagged instances are
> found.
> {code}
> @Override
> public void rebalance(String clusterName, String resourceName, int replica,
> String keyPrefix,
> String group) {
> List instanceNames = new LinkedList();
> if (keyPrefix == null || keyPrefix.length() == 0) {
> keyPrefix = resourceName;
> }
> if (group != null && group.length() > 0) {
> instanceNames = getInstancesInClusterWithTag(clusterName, group);
> }
> if (instanceNames.size() == 0) {
> // OLD
> //logger.info("No tags found for resource " + resourceName + ", use all
> instances");
> //instanceNames = getInstancesInCluster(clusterName);
> //group = "";
> // NEW
> throw new IllegalStateException("No tags found for resource ...");
> } else {
> logger.info("Found instances with tag for " + resourceName + " " +
> instanceNames);
> }
> rebalance(clusterName, resourceName, replica, keyPrefix, instanceNames,
> group);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HELIX-513) ZKHelixAdmin#rebalance with group uses instances from other groups
[
https://issues.apache.org/jira/browse/HELIX-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Francis Unson reassigned HELIX-513:
Assignee: Zhen Zhang
> ZKHelixAdmin#rebalance with group uses instances from other groups
> --
>
> Key: HELIX-513
> URL: https://issues.apache.org/jira/browse/HELIX-513
> Project: Apache Helix
> Issue Type: Bug
> Components: helix-core
>Affects Versions: 0.7.1, 0.6.3
>Reporter: Greg Brandt
>Assignee: Zhen Zhang
>
> For example, consider a cluster with one instance with tag NOT_YOURS and a
> resource whose ideal state has INSTANCE_GROUP_TAG=MINE. If we call
> {code}
> manager.rebalance("MY_CLUSTER", "MY_RESOURCE", 1, null, "MINE")
> {code}
> Helix will find no instances with the tag "MINE", so it will instead use all
> available instances in the cluster to perform the rebalance.
> This has undesirable effects when groups are used for multi-tenant clusters
> (i.e. subsets of instances belong to individual tenants, and tenants should
> not share instances).
> Better behavior might be to error out at the point no tagged instances are
> found.
> {code}
> @Override
> public void rebalance(String clusterName, String resourceName, int replica,
> String keyPrefix,
> String group) {
> List instanceNames = new LinkedList();
> if (keyPrefix == null || keyPrefix.length() == 0) {
> keyPrefix = resourceName;
> }
> if (group != null && group.length() > 0) {
> instanceNames = getInstancesInClusterWithTag(clusterName, group);
> }
> if (instanceNames.size() == 0) {
> // OLD
> //logger.info("No tags found for resource " + resourceName + ", use all
> instances");
> //instanceNames = getInstancesInCluster(clusterName);
> //group = "";
> // NEW
> throw new IllegalStateException("No tags found for resource ...");
> } else {
> logger.info("Found instances with tag for " + resourceName + " " +
> instanceNames);
> }
> rebalance(clusterName, resourceName, replica, keyPrefix, instanceNames,
> group);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HELIX-372) 0.7 cleanup
[ https://issues.apache.org/jira/browse/HELIX-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-372: - Sprint: Scrumban #1, Scrumban #2 (was: Scrumban #1) > 0.7 cleanup > --- > > Key: HELIX-372 > URL: https://issues.apache.org/jira/browse/HELIX-372 > Project: Apache Helix > Issue Type: Improvement >Reporter: Kanak Biscuitwala > > This is an umbrella issue for cleanup tasks related to 0.7 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HELIX-504) Controller should avoid resetting watches on removed paths
[ https://issues.apache.org/jira/browse/HELIX-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson reassigned HELIX-504: Assignee: Zhen Zhang > Controller should avoid resetting watches on removed paths > -- > > Key: HELIX-504 > URL: https://issues.apache.org/jira/browse/HELIX-504 > Project: Apache Helix > Issue Type: Bug >Reporter: Kanak Biscuitwala >Assignee: Zhen Zhang > > Right now, if a participant has a session change, the old current state will > be removed, but the controller despite unregistering the listener, still > reset the watch on the path deleted event. We should avoid resetting this > path on delete and let the controller explicitly set watches/listeners on new > sessions. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-508) Write a test for monitoring controller lifecycle
[ https://issues.apache.org/jira/browse/HELIX-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-508: - Sprint: Scrumban #2 > Write a test for monitoring controller lifecycle > > > Key: HELIX-508 > URL: https://issues.apache.org/jira/browse/HELIX-508 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala >Assignee: Kanak Biscuitwala > > It's important to make sure that controller lifecycles are sufficiently > expressible so that controller nodes can do extra work when becoming leaders. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-504) Controller should avoid resetting watches on removed paths
[ https://issues.apache.org/jira/browse/HELIX-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-504: - Sprint: Scrumban #2 > Controller should avoid resetting watches on removed paths > -- > > Key: HELIX-504 > URL: https://issues.apache.org/jira/browse/HELIX-504 > Project: Apache Helix > Issue Type: Bug >Reporter: Kanak Biscuitwala > > Right now, if a participant has a session change, the old current state will > be removed, but the controller despite unregistering the listener, still > reset the watch on the path deleted event. We should avoid resetting this > path on delete and let the controller explicitly set watches/listeners on new > sessions. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-416) Make the task framework more extensible
[ https://issues.apache.org/jira/browse/HELIX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-416: - Sprint: Scrumban #1 (was: Scrumban #1, Scrumban #2) > Make the task framework more extensible > --- > > Key: HELIX-416 > URL: https://issues.apache.org/jira/browse/HELIX-416 > Project: Apache Helix > Issue Type: Improvement >Reporter: Kanak Biscuitwala >Assignee: Kanak Biscuitwala > > The current task framework is good for the use case where we want to run > identical tasks according to a target resource's assignment. However, > realistically, we want things like: > - Each task partition can correspond to a different task > - Some task groups shouldn't have a status corresponding to them; they should > be able to take on additional task partitions dynamically > - There should be some notion of independence, in that a target resource (or > lack thereof) can say that arbitrary task partitions can be assigned to > arbitrary live participants > This is a pretty involved undertaking, so this will encompass some subtasks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-372) 0.7 cleanup
[ https://issues.apache.org/jira/browse/HELIX-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-372: - Sprint: Scrumban #1 (was: Scrumban #1, Scrumban #2) > 0.7 cleanup > --- > > Key: HELIX-372 > URL: https://issues.apache.org/jira/browse/HELIX-372 > Project: Apache Helix > Issue Type: Improvement >Reporter: Kanak Biscuitwala > > This is an umbrella issue for cleanup tasks related to 0.7 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-478) Validate robustness of Helix-YARN integration
[ https://issues.apache.org/jira/browse/HELIX-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-478: - Sprint: Scrumban #1 (was: Scrumban #1, Scrumban #2) > Validate robustness of Helix-YARN integration > - > > Key: HELIX-478 > URL: https://issues.apache.org/jira/browse/HELIX-478 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > > This involves running Helix on a real YARN cluster and evaluating the > following: > - All basic provisioner methods: allocate, deallocate, start, stop > - Defining and finalizing an API for an app master and app launcher that > Helix provide (and how they should be configured) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-416) Make the task framework more extensible
[ https://issues.apache.org/jira/browse/HELIX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-416: - Sprint: Scrumban #1, Scrumban #2 (was: Scrumban #1) > Make the task framework more extensible > --- > > Key: HELIX-416 > URL: https://issues.apache.org/jira/browse/HELIX-416 > Project: Apache Helix > Issue Type: Improvement >Reporter: Kanak Biscuitwala >Assignee: Kanak Biscuitwala > > The current task framework is good for the use case where we want to run > identical tasks according to a target resource's assignment. However, > realistically, we want things like: > - Each task partition can correspond to a different task > - Some task groups shouldn't have a status corresponding to them; they should > be able to take on additional task partitions dynamically > - There should be some notion of independence, in that a target resource (or > lack thereof) can say that arbitrary task partitions can be assigned to > arbitrary live participants > This is a pretty involved undertaking, so this will encompass some subtasks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-372) 0.7 cleanup
[ https://issues.apache.org/jira/browse/HELIX-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-372: - Sprint: Scrumban #1, Scrumban #2 (was: Scrumban #1) > 0.7 cleanup > --- > > Key: HELIX-372 > URL: https://issues.apache.org/jira/browse/HELIX-372 > Project: Apache Helix > Issue Type: Improvement >Reporter: Kanak Biscuitwala > > This is an umbrella issue for cleanup tasks related to 0.7 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-478) Validate robustness of Helix-YARN integration
[ https://issues.apache.org/jira/browse/HELIX-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-478: - Sprint: Scrumban #1, Scrumban #2 (was: Scrumban #1) > Validate robustness of Helix-YARN integration > - > > Key: HELIX-478 > URL: https://issues.apache.org/jira/browse/HELIX-478 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > > This involves running Helix on a real YARN cluster and evaluating the > following: > - All basic provisioner methods: allocate, deallocate, start, stop > - Defining and finalizing an API for an app master and app launcher that > Helix provide (and how they should be configured) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HELIX-499) Helix controller should listen for resource config changes
[ https://issues.apache.org/jira/browse/HELIX-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson reassigned HELIX-499: Assignee: Zhen Zhang (was: John Francis Unson) > Helix controller should listen for resource config changes > -- > > Key: HELIX-499 > URL: https://issues.apache.org/jira/browse/HELIX-499 > Project: Apache Helix > Issue Type: Sub-task >Reporter: Kanak Biscuitwala >Assignee: Zhen Zhang > > This may not be 100% backwards compatible, but it's the right thing to do, as > right now people have to touch ideal states just to trigger a resource config > change update. This is particularly relevant for the task framework, as we > will be able to avoid reading the job/workflow configs repeatedly in the > controller. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-372) 0.7 cleanup
[ https://issues.apache.org/jira/browse/HELIX-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-372: - Sprint: Scrumban #1 > 0.7 cleanup > --- > > Key: HELIX-372 > URL: https://issues.apache.org/jira/browse/HELIX-372 > Project: Apache Helix > Issue Type: Improvement >Reporter: Kanak Biscuitwala > > This is an umbrella issue for cleanup tasks related to 0.7 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HELIX-482) Support "smarter" task failure strategies
[ https://issues.apache.org/jira/browse/HELIX-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson reassigned HELIX-482: Assignee: Kanak Biscuitwala (was: John Francis Unson) > Support "smarter" task failure strategies > - > > Key: HELIX-482 > URL: https://issues.apache.org/jira/browse/HELIX-482 > Project: Apache Helix > Issue Type: Sub-task >Reporter: Kanak Biscuitwala >Assignee: Kanak Biscuitwala > > It would be interesting to support exponential backoff on task failures, and > even take containers away if the tasks are being backed off. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-416) Make the task framework more extensible
[ https://issues.apache.org/jira/browse/HELIX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-416: - Sprint: Scrumban #1 > Make the task framework more extensible > --- > > Key: HELIX-416 > URL: https://issues.apache.org/jira/browse/HELIX-416 > Project: Apache Helix > Issue Type: Improvement >Reporter: Kanak Biscuitwala >Assignee: Kanak Biscuitwala > > The current task framework is good for the use case where we want to run > identical tasks according to a target resource's assignment. However, > realistically, we want things like: > - Each task partition can correspond to a different task > - Some task groups shouldn't have a status corresponding to them; they should > be able to take on additional task partitions dynamically > - There should be some notion of independence, in that a target resource (or > lack thereof) can say that arbitrary task partitions can be assigned to > arbitrary live participants > This is a pretty involved undertaking, so this will encompass some subtasks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-329) HelixAutoController isn't a very clear name, consider renaming
[ https://issues.apache.org/jira/browse/HELIX-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-329: - Remaining Estimate: 24h Original Estimate: 24h > HelixAutoController isn't a very clear name, consider renaming > -- > > Key: HELIX-329 > URL: https://issues.apache.org/jira/browse/HELIX-329 > Project: Apache Helix > Issue Type: Improvement >Reporter: Kanak Biscuitwala > Original Estimate: 24h > Remaining Estimate: 24h > > In 0.7.0 Helix introduced new role classes, of which HelixAutoController is > one, representing CONTROLLER_PARTICIPANT. This name doesn't really describe > what the role represents, so it might be best to rename. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-497) Support named queues of jobs
[ https://issues.apache.org/jira/browse/HELIX-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-497: - Remaining Estimate: 96h Original Estimate: 96h > Support named queues of jobs > > > Key: HELIX-497 > URL: https://issues.apache.org/jira/browse/HELIX-497 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala >Assignee: Kanak Biscuitwala > Original Estimate: 96h > Remaining Estimate: 96h > > This is effectively a way to dynamically grow workflow DAGs. Workflow is a > non-essential concept, and we should be able to support alternative > organizations of jobs. Here, we just need a way to persist a queue, add work > to it, and process that work. Then the cleanup should be at job level rather > than workflow level. Some other things that are useful are returning the > current queue, and (optionally) removing from the queue. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-485) Remove controller leader election duplicate code
[ https://issues.apache.org/jira/browse/HELIX-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-485: - Remaining Estimate: 24h Original Estimate: 24h > Remove controller leader election duplicate code > > > Key: HELIX-485 > URL: https://issues.apache.org/jira/browse/HELIX-485 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala >Assignee: Zhen Zhang > Labels: kanban > Original Estimate: 24h > Remaining Estimate: 24h > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-487) Remove ClusterAccessor/HelixAdmin code duplication
[ https://issues.apache.org/jira/browse/HELIX-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-487: - Sprint: (was: Scrumban #1) > Remove ClusterAccessor/HelixAdmin code duplication > -- > > Key: HELIX-487 > URL: https://issues.apache.org/jira/browse/HELIX-487 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala >Assignee: Zhen Zhang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HELIX-485) Remove controller leader election duplicate code
[ https://issues.apache.org/jira/browse/HELIX-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson reassigned HELIX-485: Assignee: Zhen Zhang (was: John Francis Unson) > Remove controller leader election duplicate code > > > Key: HELIX-485 > URL: https://issues.apache.org/jira/browse/HELIX-485 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala >Assignee: Zhen Zhang > Labels: kanban > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-329) HelixAutoController isn't a very clear name, consider renaming
[ https://issues.apache.org/jira/browse/HELIX-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-329: - Sprint: Scrumban #1 > HelixAutoController isn't a very clear name, consider renaming > -- > > Key: HELIX-329 > URL: https://issues.apache.org/jira/browse/HELIX-329 > Project: Apache Helix > Issue Type: Improvement >Reporter: Kanak Biscuitwala > > In 0.7.0 Helix introduced new role classes, of which HelixAutoController is > one, representing CONTROLLER_PARTICIPANT. This name doesn't really describe > what the role represents, so it might be best to rename. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HELIX-497) Support named queues of jobs
[ https://issues.apache.org/jira/browse/HELIX-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson reassigned HELIX-497: Assignee: Kanak Biscuitwala (was: John Francis Unson) > Support named queues of jobs > > > Key: HELIX-497 > URL: https://issues.apache.org/jira/browse/HELIX-497 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala >Assignee: Kanak Biscuitwala > > This is effectively a way to dynamically grow workflow DAGs. Workflow is a > non-essential concept, and we should be able to support alternative > organizations of jobs. Here, we just need a way to persist a queue, add work > to it, and process that work. Then the cleanup should be at job level rather > than workflow level. Some other things that are useful are returning the > current queue, and (optionally) removing from the queue. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HELIX-484) Remove CallbackHandler/ZkCallbackHandler code duplication
[ https://issues.apache.org/jira/browse/HELIX-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson reassigned HELIX-484: Assignee: Zhen Zhang > Remove CallbackHandler/ZkCallbackHandler code duplication > - > > Key: HELIX-484 > URL: https://issues.apache.org/jira/browse/HELIX-484 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala >Assignee: Zhen Zhang > Labels: kanban > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HELIX-485) Remove controller leader election duplicate code
[ https://issues.apache.org/jira/browse/HELIX-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson reassigned HELIX-485: Assignee: Zhen Zhang > Remove controller leader election duplicate code > > > Key: HELIX-485 > URL: https://issues.apache.org/jira/browse/HELIX-485 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala >Assignee: Zhen Zhang > Labels: kanban > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HELIX-497) Support named queues of jobs
[ https://issues.apache.org/jira/browse/HELIX-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson reassigned HELIX-497: Assignee: Kanak Biscuitwala > Support named queues of jobs > > > Key: HELIX-497 > URL: https://issues.apache.org/jira/browse/HELIX-497 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala >Assignee: Kanak Biscuitwala > > This is effectively a way to dynamically grow workflow DAGs. Workflow is a > non-essential concept, and we should be able to support alternative > organizations of jobs. Here, we just need a way to persist a queue, add work > to it, and process that work. Then the cleanup should be at job level rather > than workflow level. Some other things that are useful are returning the > current queue, and (optionally) removing from the queue. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HELIX-486) Remove StateModelFactory/HelixStateModelFactory code duplication
[ https://issues.apache.org/jira/browse/HELIX-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson reassigned HELIX-486: Assignee: Zhen Zhang > Remove StateModelFactory/HelixStateModelFactory code duplication > > > Key: HELIX-486 > URL: https://issues.apache.org/jira/browse/HELIX-486 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala >Assignee: Zhen Zhang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HELIX-487) Remove ClusterAccessor/HelixAdmin code duplication
[ https://issues.apache.org/jira/browse/HELIX-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson reassigned HELIX-487: Assignee: Zhen Zhang > Remove ClusterAccessor/HelixAdmin code duplication > -- > > Key: HELIX-487 > URL: https://issues.apache.org/jira/browse/HELIX-487 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala >Assignee: Zhen Zhang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-486) Remove StateModelFactory/HelixStateModelFactory code duplication
[ https://issues.apache.org/jira/browse/HELIX-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-486: - Issue Type: Task (was: Sub-task) Parent: (was: HELIX-372) > Remove StateModelFactory/HelixStateModelFactory code duplication > > > Key: HELIX-486 > URL: https://issues.apache.org/jira/browse/HELIX-486 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-486) Remove StateModelFactory/HelixStateModelFactory code duplication
[ https://issues.apache.org/jira/browse/HELIX-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-486: - Sprint: Scrumban #1 > Remove StateModelFactory/HelixStateModelFactory code duplication > > > Key: HELIX-486 > URL: https://issues.apache.org/jira/browse/HELIX-486 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-484) Remove CallbackHandler/ZkCallbackHandler code duplication
[ https://issues.apache.org/jira/browse/HELIX-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-484: - Sprint: Scrumban #1 > Remove CallbackHandler/ZkCallbackHandler code duplication > - > > Key: HELIX-484 > URL: https://issues.apache.org/jira/browse/HELIX-484 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > Labels: kanban > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-484) Remove CallbackHandler/ZkCallbackHandler code duplication
[ https://issues.apache.org/jira/browse/HELIX-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-484: - Issue Type: Task (was: Sub-task) Parent: (was: HELIX-372) > Remove CallbackHandler/ZkCallbackHandler code duplication > - > > Key: HELIX-484 > URL: https://issues.apache.org/jira/browse/HELIX-484 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > Labels: kanban > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-487) Remove ClusterAccessor/HelixAdmin code duplication
[ https://issues.apache.org/jira/browse/HELIX-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-487: - Issue Type: Task (was: Sub-task) Parent: (was: HELIX-372) > Remove ClusterAccessor/HelixAdmin code duplication > -- > > Key: HELIX-487 > URL: https://issues.apache.org/jira/browse/HELIX-487 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-487) Remove ClusterAccessor/HelixAdmin code duplication
[ https://issues.apache.org/jira/browse/HELIX-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-487: - Sprint: Scrumban #1 > Remove ClusterAccessor/HelixAdmin code duplication > -- > > Key: HELIX-487 > URL: https://issues.apache.org/jira/browse/HELIX-487 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-485) Remove controller leader election duplicate code
[ https://issues.apache.org/jira/browse/HELIX-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-485: - Sprint: Scrumban #1 > Remove controller leader election duplicate code > > > Key: HELIX-485 > URL: https://issues.apache.org/jira/browse/HELIX-485 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > Labels: kanban > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-485) Remove controller leader election duplicate code
[ https://issues.apache.org/jira/browse/HELIX-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-485: - Issue Type: Task (was: Sub-task) Parent: (was: HELIX-372) > Remove controller leader election duplicate code > > > Key: HELIX-485 > URL: https://issues.apache.org/jira/browse/HELIX-485 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > Labels: kanban > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-497) Support named queues of jobs
[ https://issues.apache.org/jira/browse/HELIX-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-497: - Sprint: Scrumban #1 > Support named queues of jobs > > > Key: HELIX-497 > URL: https://issues.apache.org/jira/browse/HELIX-497 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > > This is effectively a way to dynamically grow workflow DAGs. Workflow is a > non-essential concept, and we should be able to support alternative > organizations of jobs. Here, we just need a way to persist a queue, add work > to it, and process that work. Then the cleanup should be at job level rather > than workflow level. Some other things that are useful are returning the > current queue, and (optionally) removing from the queue. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-497) Support named queues of jobs
[ https://issues.apache.org/jira/browse/HELIX-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-497: - Issue Type: Task (was: Sub-task) Parent: (was: HELIX-416) > Support named queues of jobs > > > Key: HELIX-497 > URL: https://issues.apache.org/jira/browse/HELIX-497 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > > This is effectively a way to dynamically grow workflow DAGs. Workflow is a > non-essential concept, and we should be able to support alternative > organizations of jobs. Here, we just need a way to persist a queue, add work > to it, and process that work. Then the cleanup should be at job level rather > than workflow level. Some other things that are useful are returning the > current queue, and (optionally) removing from the queue. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-485) Remove controller leader election duplicate code
[ https://issues.apache.org/jira/browse/HELIX-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-485: - Labels: kanban (was: ) > Remove controller leader election duplicate code > > > Key: HELIX-485 > URL: https://issues.apache.org/jira/browse/HELIX-485 > Project: Apache Helix > Issue Type: Sub-task >Reporter: Kanak Biscuitwala > Labels: kanban > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-484) Remove CallbackHandler/ZkCallbackHandler code duplication
[ https://issues.apache.org/jira/browse/HELIX-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-484: - Labels: kanban (was: ) > Remove CallbackHandler/ZkCallbackHandler code duplication > - > > Key: HELIX-484 > URL: https://issues.apache.org/jira/browse/HELIX-484 > Project: Apache Helix > Issue Type: Sub-task >Reporter: Kanak Biscuitwala > Labels: kanban > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-373) Make it easier to do crud operations on high-level config classes
[ https://issues.apache.org/jira/browse/HELIX-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-373: - Labels: kanban (was: ) > Make it easier to do crud operations on high-level config classes > - > > Key: HELIX-373 > URL: https://issues.apache.org/jira/browse/HELIX-373 > Project: Apache Helix > Issue Type: Sub-task >Reporter: Kanak Biscuitwala > Labels: kanban > > Right now there is a massive amount of code duplication in the config and > snapshot classes. Really these classes should be implemented in such a way > that they can still leverage the physical model underneath, but provide a > high-level logical aggregation of these to the user. That way we can have > ease of use while keeping the implementation simple. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-376) Remove HelixConnection/HelixManager duplicate code
[ https://issues.apache.org/jira/browse/HELIX-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-376: - Labels: kanban (was: ) > Remove HelixConnection/HelixManager duplicate code > -- > > Key: HELIX-376 > URL: https://issues.apache.org/jira/browse/HELIX-376 > Project: Apache Helix > Issue Type: Sub-task >Reporter: Kanak Biscuitwala > Labels: kanban > > Use an adaptor where the removed one is required. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-483) Simplify logical config classes
[ https://issues.apache.org/jira/browse/HELIX-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-483: - Labels: kanban (was: ) > Simplify logical config classes > --- > > Key: HELIX-483 > URL: https://issues.apache.org/jira/browse/HELIX-483 > Project: Apache Helix > Issue Type: Sub-task >Reporter: Kanak Biscuitwala >Assignee: Kanak Biscuitwala > Labels: kanban > > There is a large amount of code duplication in the config classes and that > makes everything harder to maintain. We should keep these classes small and > just be essentially wrappers on the physical model, but with the benefit of > being an aggregation of multiple physical model classes. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-374) Rebalancer config should be a complete user-specified concept
[ https://issues.apache.org/jira/browse/HELIX-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-374: - Labels: kanban (was: ) > Rebalancer config should be a complete user-specified concept > - > > Key: HELIX-374 > URL: https://issues.apache.org/jira/browse/HELIX-374 > Project: Apache Helix > Issue Type: Sub-task >Reporter: Kanak Biscuitwala > Labels: kanban > > Ideal state and rebalancer config are 1:1 right now so rebalancer config > isn't really adding any more value. Ideally, the rebalancer config should be > more of a supplement in that it's something that the user can provide along > with a resource, much like a state model definition. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (HELIX-474) Backup, Load & Purge
[ https://issues.apache.org/jira/browse/HELIX-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson closed HELIX-474. Resolution: Invalid Sorry - was trying to create epics on this board, but apparently I can't. Closing this for now. > Backup, Load & Purge > > > Key: HELIX-474 > URL: https://issues.apache.org/jira/browse/HELIX-474 > Project: Apache Helix > Issue Type: Wish >Reporter: John Francis Unson >Assignee: John Francis Unson > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-474) Backup, Load & Purge
[ https://issues.apache.org/jira/browse/HELIX-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-474: - Issue Type: Bug (was: New Feature) > Backup, Load & Purge > > > Key: HELIX-474 > URL: https://issues.apache.org/jira/browse/HELIX-474 > Project: Apache Helix > Issue Type: Bug >Reporter: John Francis Unson >Assignee: John Francis Unson > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-474) Backup, Load & Purge
[ https://issues.apache.org/jira/browse/HELIX-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-474: - Issue Type: Wish (was: Bug) > Backup, Load & Purge > > > Key: HELIX-474 > URL: https://issues.apache.org/jira/browse/HELIX-474 > Project: Apache Helix > Issue Type: Wish >Reporter: John Francis Unson >Assignee: John Francis Unson > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HELIX-474) Backup, Load & Purge
John Francis Unson created HELIX-474: Summary: Backup, Load & Purge Key: HELIX-474 URL: https://issues.apache.org/jira/browse/HELIX-474 Project: Apache Helix Issue Type: New Feature Reporter: John Francis Unson Assignee: John Francis Unson -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HELIX-253) Implement common code for language-agnostic participant
[ https://issues.apache.org/jira/browse/HELIX-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Francis Unson updated HELIX-253: - Issue Type: Task (was: Sub-task) Parent: (was: HELIX-251) > Implement common code for language-agnostic participant > --- > > Key: HELIX-253 > URL: https://issues.apache.org/jira/browse/HELIX-253 > Project: Apache Helix > Issue Type: Task >Reporter: Kanak Biscuitwala > -- This message was sent by Atlassian JIRA (v6.2#6252)
