[jira] [Work logged] (GOBBLIN-1500) Support gobblin on yarn to be able to run on clusters with robin enabled

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 30/Jul/21 00:13
            Start Date: 30/Jul/21 00:13
    Worklog Time Spent: 10m 
      Work Description: ZihanLi58 opened a new pull request #3345:
URL: https://github.com/apache/gobblin/pull/3345


   
   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
   
   
   ### JIRA
   - [ ] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-1500
   
   
   ### Description
   - [ ] Here are some details about my PR, including screenshots (if applicable):
   Previously we always check with one default yarn client, but if the cluster is enabled with Robin and can connect to different RM, it will ends up we cannot find existing application and submit duplicate tasks. So now we need to check against different potential yarn cluster, and also make sure when submitting yarn application, we only have one RM token.
   
   Options
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   Test start a new application can work, test reconnect can work 
   
   ### Commits
   - [ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   


-- 
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.

To unsubscribe, e-mail: dev-unsubscribe@gobblin.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 631401)
    Remaining Estimate: 0h
            Time Spent: 10m

> Support gobblin on yarn to be able to run on clusters with robin enabled
> ------------------------------------------------------------------------
>
>                 Key: GOBBLIN-1500
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1500
>             Project: Apache Gobblin
>          Issue Type: New Feature
>            Reporter: Zihan Li
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Previously we always check with one default yarn client, but if the cluster is enabled with Robin and can connect to different RM, it will ends up we cannot find existing application and submit duplicate tasks. So now we need to check against different potential yarn cluster, and also make sure when submitting yarn application, we only have one RM token.



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