[jira] [Resolved] (GOBBLIN-1043) Implement a Helix assigned participant check as a CommitStep

["Sudarshan Vasudevan (Jira)" <ji...@apache.org>]

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

Sudarshan Vasudevan resolved GOBBLIN-1043.
------------------------------------------
    Resolution: Fixed

> 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: 2h 10m
>  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)