shenhong created YARN-1062:
--
Summary: MRAppMaster take a long time to init taskAttempt
Key: YARN-1062
URL: https://issues.apache.org/jira/browse/YARN-1062
Project: Hadoop YARN
Issue Type: Bug
[
https://issues.apache.org/jira/browse/YARN-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1062:
---
Description:
In our cluster, MRAppMaster take a long time to init taskAttempt, the following
log last one
[
https://issues.apache.org/jira/browse/YARN-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738596#comment-13738596
]
shenhong commented on YARN-1062:
Thanks Vinod Kumar Vavilapalli, I think YARN-435 is okay
[
https://issues.apache.org/jira/browse/YARN-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong resolved YARN-1062.
Resolution: Duplicate
MRAppMaster take a long time to init taskAttempt
[
https://issues.apache.org/jira/browse/YARN-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738647#comment-13738647
]
shenhong commented on YARN-435:
---
Firstly, if AM get all nodes in the cluster including their
[
https://issues.apache.org/jira/browse/YARN-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong reassigned YARN-149:
-
Assignee: shenhong (was: Bikas Saha)
ResourceManager (RM) High-Availability (HA)
[
https://issues.apache.org/jira/browse/YARN-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-149:
--
Assignee: (was: shenhong)
ResourceManager (RM) High-Availability (HA)
[
https://issues.apache.org/jira/browse/YARN-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13541336#comment-13541336
]
shenhong commented on YARN-271:
---
I found this patch will result to a infinite loop when
shenhong created YARN-300:
-
Summary: After yarn-271, when yarn.scheduler.fair.max.assign=0,
fairscheduler will infinite loop and not schedule any application.
Key: YARN-300
URL:
[
https://issues.apache.org/jira/browse/YARN-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-300:
--
Summary: After yarn-271, when yarn.scheduler.fair.max.assign=-1,
fairscheduler will infinite loop and not
[
https://issues.apache.org/jira/browse/YARN-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13541590#comment-13541590
]
shenhong commented on YARN-300:
---
At FairScheduler#nodeUpdate() the code is:
if
[
https://issues.apache.org/jira/browse/YARN-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-300:
--
Description: After yarn-271, when yarn.scheduler.fair.max.assign=0, when a
node was been reserved, fairScheduler
shenhong created YARN-301:
-
Summary: Fairscheduler appear to concurrentModificationException
and RM crash
Key: YARN-301
URL: https://issues.apache.org/jira/browse/YARN-301
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13541592#comment-13541592
]
shenhong commented on YARN-301:
---
The reason is when the thread SchedulerEventDispatche
[
https://issues.apache.org/jira/browse/YARN-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-301:
--
Attachment: YARN-301.patch
add a patch to solve this problem
Fairscheduler appear to
[
https://issues.apache.org/jira/browse/YARN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-319:
--
Attachment: YARN-319.patch
Submit a job to a queue that not allowed in fairScheduler, client will hold
[
https://issues.apache.org/jira/browse/YARN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552142#comment-13552142
]
shenhong commented on YARN-319:
---
Of course, Our version already includes this patch.
[
https://issues.apache.org/jira/browse/YARN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552143#comment-13552143
]
shenhong commented on YARN-319:
---
Here is the log of yarn client:
13/01/13 13:18:26 ERROR
[
https://issues.apache.org/jira/browse/YARN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552144#comment-13552144
]
shenhong commented on YARN-319:
---
Here is the log of ResourceManager:
2013-01-13 13:18:26,922
[
https://issues.apache.org/jira/browse/YARN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-319:
--
Attachment: YARN-319-1.patch
add a testcast
Submit a job to a queue that not allowed in
[
https://issues.apache.org/jira/browse/YARN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13557932#comment-13557932
]
shenhong commented on YARN-319:
---
Thanks for you help, Sandy Ryza.
Submit a
[
https://issues.apache.org/jira/browse/YARN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-319:
--
Attachment: YARN-319-2.patch
fix
Submit a job to a queue that not allowed in fairScheduler,
[
https://issues.apache.org/jira/browse/YARN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13560312#comment-13560312
]
shenhong commented on YARN-319:
---
Would it be possible to use a synchronous event handler in
shenhong created YARN-622:
-
Summary: Many deprecated warn messages in hadoop 2.0 when running
sleepJob
Key: YARN-622
URL: https://issues.apache.org/jira/browse/YARN-622
Project: Hadoop YARN
Issue
[
https://issues.apache.org/jira/browse/YARN-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643880#comment-13643880
]
shenhong commented on YARN-622:
---
My mapred-site.xml is empty.
I thank the reason is in
[
https://issues.apache.org/jira/browse/YARN-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643881#comment-13643881
]
shenhong commented on YARN-622:
---
When set a property, if the property has deprecated name, it
shenhong created YARN-647:
-
Summary: historyServer can show container's log when aggregation
is not enabled
Key: YARN-647
URL: https://issues.apache.org/jira/browse/YARN-647
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-647:
--
Description:
Since we don't want to aggregate the container's log, because it will be a
pressure to namenode.
[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-647:
--
Description:
When yarn.log-aggregation-enable was seted to false, after a MR_App complete,
we can't view the
[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-647:
--
Description:
When yarn.log-aggregation-enable was seted to false, after a MR_App complete,
we can't view the
[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-647:
--
Environment:
When yarn.log-aggregation-enable was seted to false, after a MR_App complete,
we can't view the
[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-647:
--
Environment:
yarn.log-aggregation-enable=false , HistoryServer will show like this:
Aggregation is not
[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-647:
--
Environment:
yarn.log-aggregation-enable=false
Aggregation is not enabled. Try the nodemanager at
[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-647:
--
Summary: historyServer can't show container's log when aggregation is not
enabled (was: historyServer can show
[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-647:
--
Attachment: yarn-647.patch
add a patch
historyServer can't show container's log when
[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-647:
--
Description:
When yarn.log-aggregation-enable is seted to false, after a MR_App complete, we
can't view the
shenhong created YARN-1786:
--
Summary: TestRMAppTransitions occasionally fail
Key: YARN-1786
URL: https://issues.apache.org/jira/browse/YARN-1786
Project: Hadoop YARN
Issue Type: Bug
[
https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1786:
---
Description:
{code}
[
https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1786:
---
Description:
{code}
[
https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1786:
---
Description:
TestRMAppTransitions often fail with application finish time is not greater
then 0, following
[
https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920410#comment-13920410
]
shenhong commented on YARN-1786:
Here is the code:
{code}
private void
[
https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong reassigned YARN-1786:
--
Assignee: shenhong
TestRMAppTransitions occasionally fail
--
[
https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1786:
---
Attachment: YARN-1786.patch
Add a patch to fix the bug!
TestRMAppTransitions occasionally fail
[
https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1786:
---
Description:
TestRMAppTransitions often fail with application finish time is not greater
then 0, following
[
https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1786:
---
Attachment: (was: YARN-1786.patch)
TestRMAppTransitions occasionally fail
[
https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1786:
---
Attachment: YARN-1786.patch
TestRMAppTransitions occasionally fail
--
[
https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920624#comment-13920624
]
shenhong commented on YARN-1786:
{code}
@Test
public void testAppAcceptedKill() throws
[
https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922006#comment-13922006
]
shenhong commented on YARN-1786:
Thanks Jian He. The code I used is from
shenhong created YARN-1313:
--
Summary: userlog not delete at NodeManager start
Key: YARN-1313
URL: https://issues.apache.org/jira/browse/YARN-1313
Project: Hadoop YARN
Issue Type: Bug
[
https://issues.apache.org/jira/browse/YARN-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1313:
---
Summary: userlog hadn't delete at NodeManager start (was: userlog not
delete at NodeManager start)
userlog
[
https://issues.apache.org/jira/browse/YARN-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1313:
---
Summary: Userlog hadn't delete at NodeManager start (was: userlog hadn't
delete at NodeManager start)
[
https://issues.apache.org/jira/browse/YARN-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1313:
---
Description: At present, userlog should be delete at NodeManager start,
userlog hadn't delete at
[
https://issues.apache.org/jira/browse/YARN-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1313:
---
Description: At present, userlog hadn't delete at NodeManager start,
should we delete then? (was: At
[
https://issues.apache.org/jira/browse/YARN-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1313:
---
Description: At present, userlog are hadn't delete at NodeManager start,
should we delete then? (was: At
[
https://issues.apache.org/jira/browse/YARN-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1313:
---
Component/s: nodemanager
Userlog hadn't delete at NodeManager start
[
https://issues.apache.org/jira/browse/YARN-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1313:
---
Affects Version/s: 2.2.0
Userlog hadn't delete at NodeManager start
[
https://issues.apache.org/jira/browse/YARN-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1313:
---
Description: At present, userlog hadn't delete at NodeManager start, I
thank we should delete userlog before
shenhong created YARN-1472:
--
Summary: TestCase failed at username with “.”
Key: YARN-1472
URL: https://issues.apache.org/jira/browse/YARN-1472
Project: Hadoop YARN
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/YARN-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1472:
---
Description:
When I run a testcase by user yuling.sh :
mvn test
[
https://issues.apache.org/jira/browse/YARN-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1472:
---
Description:
When I run a testcase by user yuling.sh :
{code}
mvn test
[
https://issues.apache.org/jira/browse/YARN-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13838669#comment-13838669
]
shenhong commented on YARN-1472:
The reason is at
[
https://issues.apache.org/jira/browse/YARN-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840024#comment-13840024
]
shenhong commented on YARN-1472:
It will couse username with '.' failed this testcase. It
shenhong created YARN-1537:
--
Summary: TestLocalResourcesTrackerImpl.testLocalResourceCache
often failed
Key: YARN-1537
URL: https://issues.apache.org/jira/browse/YARN-1537
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-1537:
---
Description:
Here is the error log
{code}
Results :
Failed tests:
[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13857414#comment-13857414
]
shenhong commented on YARN-647:
---
Thanks Zhijie!
Like caolong, we also set
[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-647:
--
Attachment: yarn-647-2.patch
add a new patch
historyServer can't show container's log when aggregation is not
66 matches
Mail list logo
