[jira] [Updated] (YARN-342) RM doesn't retry token renewals

2016-05-10 Thread Kuhu Shukla (JIRA)

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

Kuhu Shukla updated YARN-342:
-
Assignee: (was: Kuhu Shukla)

> RM doesn't retry token renewals
> ---
>
> Key: YARN-342
> URL: https://issues.apache.org/jira/browse/YARN-342
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: resourcemanager
>Affects Versions: 3.0.0, 2.0.0-alpha, 0.23.6
>Reporter: Daryn Sharp
>Priority: Critical
>
> The RM stops trying to renew tokens if any exception occurs during the renew. 
>  This should be changed to abort only if the exception is {{InvalidToken}} to 
> allow resilience to transient network failures, issues associated with 
> aborted connections when the NN is overloaded, cluster upgrades, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org



[jira] [Updated] (YARN-342) RM doesn't retry token renewals

2014-11-09 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli updated YARN-342:
-
Priority: Critical  (was: Major)
Target Version/s: 2.7.0  (was: 3.0.0, 2.1.0-beta)

This one's old but bad. Targeting fix in 2.7.

 RM doesn't retry token renewals
 ---

 Key: YARN-342
 URL: https://issues.apache.org/jira/browse/YARN-342
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Affects Versions: 3.0.0, 2.0.0-alpha, 0.23.6
Reporter: Daryn Sharp
Priority: Critical

 The RM stops trying to renew tokens if any exception occurs during the renew. 
  This should be changed to abort only if the exception is {{InvalidToken}} to 
 allow resilience to transient network failures, issues associated with 
 aborted connections when the NN is overloaded, cluster upgrades, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (YARN-342) RM doesn't retry token renewals

2013-05-06 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli updated YARN-342:
-

Issue Type: Sub-task  (was: Bug)
Parent: YARN-47

 RM doesn't retry token renewals
 ---

 Key: YARN-342
 URL: https://issues.apache.org/jira/browse/YARN-342
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Affects Versions: 3.0.0, 2.0.0-alpha, 0.23.6
Reporter: Daryn Sharp

 The RM stops trying to renew tokens if any exception occurs during the renew. 
  This should be changed to abort only if the exception is {{InvalidToken}} to 
 allow resilience to transient network failures, issues associated with 
 aborted connections when the NN is overloaded, cluster upgrades, etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (YARN-342) RM doesn't retry token renewals

2013-01-16 Thread Thomas Graves (JIRA)

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

Thomas Graves updated YARN-342:
---

Target Version/s: 3.0.0, 2.0.3-alpha, 0.23.7  (was: 3.0.0, 2.0.3-alpha, 
0.23.6)

 RM doesn't retry token renewals
 ---

 Key: YARN-342
 URL: https://issues.apache.org/jira/browse/YARN-342
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Affects Versions: 3.0.0, 2.0.0-alpha, 0.23.6
Reporter: Daryn Sharp

 The RM stops trying to renew tokens if any exception occurs during the renew. 
  This should be changed to abort only if the exception is {{InvalidToken}} to 
 allow resilience to transient network failures, issues associated with 
 aborted connections when the NN is overloaded, cluster upgrades, etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira