[jira] [Updated] (YARN-2038) Revisit how AMs learn of containers from previous attempts

2015-11-27 Thread Steve Loughran (JIRA)

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

Steve Loughran updated YARN-2038:
-
Target Version/s:   (was: 2.6.3, 2.7.3)

> Revisit how AMs learn of containers from previous attempts
> --
>
> Key: YARN-2038
> URL: https://issues.apache.org/jira/browse/YARN-2038
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: resourcemanager
>Affects Versions: 2.4.0
>Reporter: Karthik Kambatla
>
> Based on YARN-556, we need to update the way AMs learn about containers 
> allocation previous attempts. 



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


[jira] [Updated] (YARN-2038) Revisit how AMs learn of containers from previous attempts

2015-11-03 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli updated YARN-2038:
--
Target Version/s: 2.6.3, 2.7.3  (was: 2.7.2, 2.6.3)

Moving out all non-critical / non-blocker issues that didn't make it out of 
2.7.2 into 2.7.3.

> Revisit how AMs learn of containers from previous attempts
> --
>
> Key: YARN-2038
> URL: https://issues.apache.org/jira/browse/YARN-2038
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: resourcemanager
>Affects Versions: 2.4.0
>Reporter: Karthik Kambatla
>
> Based on YARN-556, we need to update the way AMs learn about containers 
> allocation previous attempts. 



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


[jira] [Updated] (YARN-2038) Revisit how AMs learn of containers from previous attempts

2015-11-02 Thread Sangjin Lee (JIRA)

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

Sangjin Lee updated YARN-2038:
--
Target Version/s: 2.7.2, 2.6.3  (was: 2.7.2, 2.6.2)

Targeting 2.6.3 now that 2.6.2 has shipped.

> Revisit how AMs learn of containers from previous attempts
> --
>
> Key: YARN-2038
> URL: https://issues.apache.org/jira/browse/YARN-2038
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: resourcemanager
>Affects Versions: 2.4.0
>Reporter: Karthik Kambatla
>
> Based on YARN-556, we need to update the way AMs learn about containers 
> allocation previous attempts. 



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


[jira] [Updated] (YARN-2038) Revisit how AMs learn of containers from previous attempts

2015-08-11 Thread Sangjin Lee (JIRA)

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

Sangjin Lee updated YARN-2038:
--
Target Version/s: 2.7.2, 2.6.2  (was: 2.6.1, 2.7.2)

> Revisit how AMs learn of containers from previous attempts
> --
>
> Key: YARN-2038
> URL: https://issues.apache.org/jira/browse/YARN-2038
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: resourcemanager
>Affects Versions: 2.4.0
>Reporter: Karthik Kambatla
>
> Based on YARN-556, we need to update the way AMs learn about containers 
> allocation previous attempts. 



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


[jira] [Updated] (YARN-2038) Revisit how AMs learn of containers from previous attempts

2015-08-11 Thread Sangjin Lee (JIRA)

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

Sangjin Lee updated YARN-2038:
--

Unless the patch is ready to go and the JIRA is a critical fix, we'll defer it 
to 2.6.2. Let me know if you have comments. Thanks!

> Revisit how AMs learn of containers from previous attempts
> --
>
> Key: YARN-2038
> URL: https://issues.apache.org/jira/browse/YARN-2038
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: resourcemanager
>Affects Versions: 2.4.0
>Reporter: Karthik Kambatla
>
> Based on YARN-556, we need to update the way AMs learn about containers 
> allocation previous attempts. 



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


[jira] [Updated] (YARN-2038) Revisit how AMs learn of containers from previous attempts

2015-06-29 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli updated YARN-2038:
--
Target Version/s: 2.6.1, 2.7.2  (was: 2.6.0)

Moving all tickets targeted for the already closed release 2.6.0 into 
2.6.1/2.7.2.

> Revisit how AMs learn of containers from previous attempts
> --
>
> Key: YARN-2038
> URL: https://issues.apache.org/jira/browse/YARN-2038
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: resourcemanager
>Affects Versions: 2.4.0
>Reporter: Karthik Kambatla
>
> Based on YARN-556, we need to update the way AMs learn about containers 
> allocation previous attempts. 



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


[jira] [Updated] (YARN-2038) Revisit how AMs learn of containers from previous attempts

2014-07-02 Thread Karthik Kambatla (JIRA)

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

Karthik Kambatla updated YARN-2038:
---

Target Version/s: 2.6.0  (was: 2.5.0)

> Revisit how AMs learn of containers from previous attempts
> --
>
> Key: YARN-2038
> URL: https://issues.apache.org/jira/browse/YARN-2038
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: resourcemanager
>Affects Versions: 2.4.0
>Reporter: Karthik Kambatla
>
> Based on YARN-556, we need to update the way AMs learn about containers 
> allocation previous attempts. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)