[ 
https://issues.apache.org/jira/browse/GOBBLIN-1016?focusedWorklogId=371971&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-371971
 ]

ASF GitHub Bot logged work on GOBBLIN-1016:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Jan/20 23:15
            Start Date: 14/Jan/20 23:15
    Worklog Time Spent: 10m 
      Work Description: asfgit commented on pull request #2863: GOBBLIN-1016: 
Allow Gobblin Application Master to join Helix cluster …
URL: https://github.com/apache/incubator-gobblin/pull/2863
 
 
   
 
----------------------------------------------------------------
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: 371971)
    Time Spent: 1.5h  (was: 1h 20m)

> Allow Gobblin Application Master to join Helix cluster in PARTICIPANT mode 
> when Helix cluster is managed
> --------------------------------------------------------------------------------------------------------
>
>                 Key: GOBBLIN-1016
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1016
>             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: 1.5h
>  Remaining Estimate: 0h
>
> In the managed cluster mode, the Gobblin Yarn Application Master joins Helix 
> cluster in the ADMINISTRATOR role. However, Helix does not support messaging 
> for instances which are not CONTROLLER or PARTICIPANT. To properly handle 
> shutdown and token file update messages, the AppMaster should connect to the 
> Helix cluster as a PARTICIPANT, these message types need to be destined to 
> PARTICIPANT instead of CONTROLLER as is the case today.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to