[
https://issues.apache.org/jira/browse/YARN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655616#comment-13655616
]
Vinod Kumar Vavilapalli commented on YARN-499:
--
bq. Is there a reason we have
Sandy Ryza created YARN-675:
---
Summary: In YarnClient, pull AM logs on AM container failure
Key: YARN-675
URL: https://issues.apache.org/jira/browse/YARN-675
Project: Hadoop YARN
Issue Type:
[
https://issues.apache.org/jira/browse/YARN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655619#comment-13655619
]
Sandy Ryza commented on YARN-499:
-
bq. So that answers it?
Yeah, it does. Thanks Vinod.
bq.
[
https://issues.apache.org/jira/browse/YARN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza resolved YARN-499.
-
Resolution: Won't Fix
On container failure, surface logs to client
[
https://issues.apache.org/jira/browse/YARN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza updated YARN-499:
Summary: On container failure, include logs in diagnostics (was: On
container failure, surface logs to
[
https://issues.apache.org/jira/browse/YARN-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza updated YARN-675:
Description: Similar to MAPREDUCE-4362, when an AM container fails, it
would be helpful to pull its logs
[
https://issues.apache.org/jira/browse/YARN-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-675:
-
Issue Type: Sub-task (was: Improvement)
Parent: YARN-522
In
[
https://issues.apache.org/jira/browse/YARN-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jian He updated YARN-638:
-
Attachment: YARN-638.6.patch
The new patch:
1. adds the real FileSystemStore for recovering RMDelegationTokens.
2.
[
https://issues.apache.org/jira/browse/YARN-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-307:
-
Labels: usability (was: )
NodeManager should log container launch command.
[
https://issues.apache.org/jira/browse/YARN-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-615:
-
Attachment: YARN-615-20130512.txt
Patch against latest trunk
[
https://issues.apache.org/jira/browse/YARN-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655661#comment-13655661
]
Bikas Saha commented on YARN-674:
-
Looks like we might have to resurrect the remaining
of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12582870/YARN-615-20130512.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4
[
https://issues.apache.org/jira/browse/YARN-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655689#comment-13655689
]
Bikas Saha commented on YARN-422:
-
Rename onExceptionRaisedWhenStartingContainer() to
[
https://issues.apache.org/jira/browse/YARN-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655691#comment-13655691
]
Hadoop QA commented on YARN-638:
{color:green}+1 overall{color}. Here are the results of
[
https://issues.apache.org/jira/browse/YARN-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu resolved YARN-307.
---
Resolution: Invalid
Resolving as wont invalid
NodeManager should log
[
https://issues.apache.org/jira/browse/YARN-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-502:
-
Issue Type: Sub-task (was: Bug)
Parent: YARN-676
RM crash with NPE
Vinod Kumar Vavilapalli created YARN-676:
Summary: [Umbrella] Daemons crashing because of invalid state
transitions
Key: YARN-676
URL: https://issues.apache.org/jira/browse/YARN-676
Project:
[
https://issues.apache.org/jira/browse/YARN-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-245:
-
Issue Type: Sub-task (was: Bug)
Parent: YARN-676
Node Manager gives
[
https://issues.apache.org/jira/browse/YARN-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-296:
-
Issue Type: Sub-task (was: Bug)
Parent: YARN-676
Resource Manager
[
https://issues.apache.org/jira/browse/YARN-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-346:
-
Issue Type: Sub-task (was: Bug)
Parent: YARN-676
I will be out of the office starting 05/12/2013 and will not return until
05/16/2013.
I will be out of office at a customer site with limitted ot no internet
access. For urgent matters, please contact my manager Mohamed Obide
(mob...@eg.ibm.com)
[
https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655767#comment-13655767
]
Steve Loughran commented on YARN-530:
-
will look at this on monday. Off the top of my
22 matches
Mail list logo