[
https://issues.apache.org/jira/browse/GOBBLIN-1043?focusedWorklogId=383753&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-383753
]
ASF GitHub Bot logged work on GOBBLIN-1043:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Feb/20 17:40
Start Date: 07/Feb/20 17:40
Worklog Time Spent: 10m
Work Description: sv2000 commented on pull request #2883: GOBBLIN-1043:
Implement a Helix assigned participant check as a Commi…
URL: https://github.com/apache/incubator-gobblin/pull/2883#discussion_r376518540
##########
File path:
gobblin-cluster/src/main/java/org/apache/gobblin/cluster/GobblinClusterConfigurationKeys.java
##########
@@ -183,4 +185,11 @@
public static final boolean DEFAULT_IS_HELIX_CLUSTER_MANAGED = false;
public static final String HADOOP_CONFIG_OVERRIDES_PREFIX =
GOBBLIN_CLUSTER_PREFIX + "hadoop.inject";
+
+ //Configuration keys that will be set dynamically.
+ public static final String HELIX_JOB_ID_KEY = GOBBLIN_CLUSTER_PREFIX +
"helixJobId";
Review comment:
Changed.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 383753)
Time Spent: 1h 50m (was: 1h 40m)
> Implement a Helix assigned participant check as a CommitStep
> ------------------------------------------------------------
>
> Key: GOBBLIN-1043
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1043
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-cluster
> Affects Versions: 0.15.0
> Reporter: Sudarshan Vasudevan
> Assignee: Hung Tran
> Priority: Major
> Fix For: 0.15.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> In Gobblin Helix cluster, we encounter scenarios where a participant
> continues to work on a Helix partition even after the partition has been
> assigned by Helix to a different participant leading to duplicate
> consumption. We implement a check where each Helix task checks if it is
> indeed the currently assigned participant for the Helix partition. This check
> is implemented as a CommitStep and can be used as an assertion before data
> publish occurs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
