[
https://issues.apache.org/jira/browse/YARN-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10557:
---
Affects Version/s: 3.2.1
> Application may be leaked in state store when resourcemanager failover.
>
zhengchenyu created YARN-10557:
--
Summary: Application may be leaked in state store when
resourcemanager failover.
Key: YARN-10557
URL: https://issues.apache.org/jira/browse/YARN-10557
Project: Hadoop YAR
[
https://issues.apache.org/jira/browse/YARN-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10557:
---
Fix Version/s: 3.3.1
> Application may be leaked in state store when resourcemanager failover.
>
[
https://issues.apache.org/jira/browse/YARN-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10557:
---
Component/s: RM
> Application may be leaked in state store when resourcemanager failover.
> -
[
https://issues.apache.org/jira/browse/YARN-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu reassigned YARN-10557:
--
Assignee: zhengchenyu
> Application may be leaked in state store when resourcemanager failover
[
https://issues.apache.org/jira/browse/YARN-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10557:
---
Labels: resourcemanager (was: )
> Application may be leaked in state store when resourcemanager fail
[
https://issues.apache.org/jira/browse/YARN-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10557:
---
Component/s: (was: RM)
resourcemanager
> Application may be leaked in state stor
[
https://issues.apache.org/jira/browse/YARN-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10557:
---
Description:
In resourceManager log, I found amount of log like below:
{code}
2020-12-30 19:18:48,12
[
https://issues.apache.org/jira/browse/YARN-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu resolved YARN-10557.
Release Note: YARN-9848
Resolution: Duplicate
I think it duplicate with YARN-9848.
> Applica
zhengchenyu created YARN-10642:
--
Summary: ResourceManager may keep stuck, because AsyncDispatcher's
printEventQueueDetails method stuck in an endless loop
Key: YARN-10642
URL: https://issues.apache.org/jira/browse/YA
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Description:
In our cluster, ResouceManager stuck twice within twenty days. Yarn client
can't submit
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Description:
In our cluster, ResouceManager stuck twice within twenty days. Yarn client
can't submit
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Attachment: put.png
> ResourceManager may keep stuck, because AsyncDispatcher's
> printEventQueueDet
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Attachment: take.png
> ResourceManager may keep stuck, because AsyncDispatcher's
> printEventQueueDe
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Attachment: debugfornode.png
> ResourceManager may keep stuck, because AsyncDispatcher's
> printEven
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Attachment: deadloop.png
> ResourceManager may keep stuck, because AsyncDispatcher's
> printEventQue
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Attachment: MockForDeadLoop.java
> ResourceManager may keep stuck, because AsyncDispatcher's
> print
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287685#comment-17287685
]
zhengchenyu commented on YARN-10642:
If you feel description is too long, you only ne
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Attachment: YARN-10642.001.patch
> ResourceManager may keep stuck, because AsyncDispatcher's
> print
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287713#comment-17287713
]
zhengchenyu commented on YARN-10642:
YARN-10221 is the same problem, but no real reas
[
https://issues.apache.org/jira/browse/YARN-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10643:
---
Attachment: YARN-10643.001.patch
> Fix the race condition introduced by YARN-8995.
>
[
https://issues.apache.org/jira/browse/YARN-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287714#comment-17287714
]
zhengchenyu edited comment on YARN-10643 at 2/20/21, 3:27 PM:
-
[
https://issues.apache.org/jira/browse/YARN-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287714#comment-17287714
]
zhengchenyu commented on YARN-10643:
Just use Iterator() could solve this problem. Yo
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287713#comment-17287713
]
zhengchenyu edited comment on YARN-10642 at 2/20/21, 3:28 PM:
-
[
https://issues.apache.org/jira/browse/YARN-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu reassigned YARN-10643:
--
Assignee: zhengchenyu (was: Qi Zhu)
> Fix the race condition introduced by YARN-8995.
> -
[
https://issues.apache.org/jira/browse/YARN-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287723#comment-17287723
]
zhengchenyu commented on YARN-10643:
I think you need to konw why stuck. Please discu
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287728#comment-17287728
]
zhengchenyu commented on YARN-10642:
[~zhuqi] That's OK. I also found, but sorry for
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Attachment: YARN-10642.002.patch
> ResourceManager may keep stuck, because AsyncDispatcher's
> print
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Summary: AsyncDispatcher will stuck introduced by YARN-8995. (was:
ResourceManager may keep stuck, b
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Attachment: YARN-10642.003.patch
> ResourceManager may keep stuck, because AsyncDispatcher's
> print
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288223#comment-17288223
]
zhengchenyu commented on YARN-10642:
I add a uni-test in YARN-10642.003.patch which r
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288223#comment-17288223
]
zhengchenyu edited comment on YARN-10642 at 2/22/21, 7:38 AM:
-
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288223#comment-17288223
]
zhengchenyu edited comment on YARN-10642 at 2/22/21, 7:40 AM:
-
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Description:
In our cluster, ResouceManager stuck twice within twenty days. Yarn client
can't submit
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Attachment: YARN-10642.004.patch
> AsyncDispatcher will stuck introduced by YARN-8995.
>
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294982#comment-17294982
]
zhengchenyu commented on YARN-10642:
Okay, I submit YARN-10642.004.patch which repair
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294982#comment-17294982
]
zhengchenyu edited comment on YARN-10642 at 3/4/21, 4:15 AM:
-
[
https://issues.apache.org/jira/browse/YARN-10221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294988#comment-17294988
]
zhengchenyu commented on YARN-10221:
Please follow YARN-10642 which explain the reaso
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Attachment: YARN-10642.005.patch
> AsyncDispatcher will stuck introduced by YARN-8995.
>
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295286#comment-17295286
]
zhengchenyu commented on YARN-10642:
[~pbacsko] Okay, work done in YARN-10642.005.pat
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296075#comment-17296075
]
zhengchenyu commented on YARN-10642:
[~pbacsko] Yes, I think it's Java's bug. Then I
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296077#comment-17296077
]
zhengchenyu commented on YARN-10642:
[~pbacsko] Okay, I will submit pathes for branch
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Attachment: YARN-10642-branch-3.2.001.patch
> Race condition: AsyncDispatcher can get stuck by the ch
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10642:
---
Attachment: YARN-10642-branch-3.3.001.patch
> Race condition: AsyncDispatcher can get stuck by the ch
[
https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296075#comment-17296075
]
zhengchenyu edited comment on YARN-10642 at 3/5/21, 4:01 PM:
-
[
https://issues.apache.org/jira/browse/YARN-6202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17310564#comment-17310564
]
zhengchenyu commented on YARN-6202:
---
[~yufeigu] I agree that exitOnDispatchException sho
[
https://issues.apache.org/jira/browse/YARN-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630300#comment-17630300
]
zhengchenyu commented on YARN-11183:
[~goiri] Hi, can you please review this PR? the
zhengchenyu created YARN-11549:
--
Summary: Add MiniRouterYarnCluster for test
Key: YARN-11549
URL: https://issues.apache.org/jira/browse/YARN-11549
Project: Hadoop YARN
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/YARN-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11153:
---
Parent Issue: YARN-5597 (was: YARN-10775)
> Make proxy server support YARN federation.
> ---
[
https://issues.apache.org/jira/browse/YARN-11154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11154:
---
Parent Issue: YARN-5597 (was: YARN-10775)
> Make router support proxy server.
>
[
https://issues.apache.org/jira/browse/YARN-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11153:
---
Description:
I setup a yarn federation cluster, I can't connect the running app web, but the
complet
[
https://issues.apache.org/jira/browse/YARN-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11153:
---
Attachment: YARN-10775-design-doc.001.pdf
> Make proxy server support YARN federation.
>
[
https://issues.apache.org/jira/browse/YARN-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11153:
---
Description:
I setup a yarn federation cluster, I can't connect the running app web, but the
complet
[
https://issues.apache.org/jira/browse/YARN-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu reassigned YARN-8980:
-
Assignee: zhengchenyu (was: Shilun Fan)
> Mapreduce application container start fail after AM r
zhengchenyu created YARN-11564:
--
Summary: The default value of sub cluster cleaner interval was
converted unexpectedly
Key: YARN-11564
URL: https://issues.apache.org/jira/browse/YARN-11564
Project: Hadoo
[
https://issues.apache.org/jira/browse/YARN-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11564:
---
Description: yarn.router.subcluster.cleaner.interval.time is duplicated in
yarn-default.xml (was: So
[
https://issues.apache.org/jira/browse/YARN-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11564:
---
Summary: Fix wrong config in yarn-default.xml (was: The default value of
sub cluster cleaner interva
zhengchenyu created YARN-11565:
--
Summary: Container logs are missing when
yarn.app.container.log.filesize is set to default value 0.
Key: YARN-11565
URL: https://issues.apache.org/jira/browse/YARN-11565
[
https://issues.apache.org/jira/browse/YARN-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11565:
---
Description:
Since HADOOP-18649, log4j.appender.\{APPENDER}.MaxFileSize is set to
${yarn.app.contain
[
https://issues.apache.org/jira/browse/YARN-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11565:
---
Description:
Since HADOOP-18649, log4j.appender.\{APPENDER}.MaxFileSize is set to
${yarn.app.contain
[
https://issues.apache.org/jira/browse/YARN-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11565:
---
Description:
Since HADOOP-18649, in container-log4j.properties,
log4j.appender.\{APPENDER}.MaxFileSi
[
https://issues.apache.org/jira/browse/YARN-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11565:
---
Description:
Since HADOOP-18649, in container-log4j.properties,
log4j.appender.\{APPENDER}.MaxFileSi
[
https://issues.apache.org/jira/browse/YARN-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11565:
---
Description:
Since HADOOP-18649, in container-log4j.properties,
log4j.appender.\{APPENDER}.MaxFileSi
[
https://issues.apache.org/jira/browse/YARN-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11565:
---
Description:
Since HADOOP-18649, in container-log4j.properties,
log4j.appender.\{APPENDER}.MaxFileSi
[
https://issues.apache.org/jira/browse/YARN-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu resolved YARN-11565.
Resolution: Duplicate
This Jira should be in mapreduce module.
> Container logs are missing when y
[
https://issues.apache.org/jira/browse/YARN-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11565:
---
Labels: (was: pull-request-available)
> Container logs are missing when yarn.app.container.log.file
[
https://issues.apache.org/jira/browse/YARN-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11565:
---
Target Version/s: (was: 3.4.0)
> Container logs are missing when yarn.app.container.log.filesize is
[
https://issues.apache.org/jira/browse/YARN-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763087#comment-17763087
]
zhengchenyu edited comment on YARN-11565 at 9/8/23 1:34 PM:
T
zhengchenyu created YARN-11566:
--
Summary: Yarn app kill command can not kill the application in
secondary sub cluster.
Key: YARN-11566
URL: https://issues.apache.org/jira/browse/YARN-11566
Project: Hadoo
[
https://issues.apache.org/jira/browse/YARN-11566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11566:
---
Description: When AMRMProxy is enable, the application may allocate
container among multi sub cluster
[
https://issues.apache.org/jira/browse/YARN-11566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11566:
---
Description: When AMRMProxy is enable, the application may allocate
container among multi sub cluster
[
https://issues.apache.org/jira/browse/YARN-11566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764465#comment-17764465
]
zhengchenyu commented on YARN-11566:
There are two ways to solve this problem:
(1) C
[
https://issues.apache.org/jira/browse/YARN-11566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764465#comment-17764465
]
zhengchenyu edited comment on YARN-11566 at 9/13/23 10:00 AM:
-
[
https://issues.apache.org/jira/browse/YARN-11566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11566:
---
Description:
When AMRMProxy is enable, the application may allocate container among multi
sub cluste
[
https://issues.apache.org/jira/browse/YARN-11566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764465#comment-17764465
]
zhengchenyu edited comment on YARN-11566 at 9/14/23 10:54 AM:
-
[
https://issues.apache.org/jira/browse/YARN-11566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11566:
---
Issue Type: Bug (was: Improvement)
> Yarn app kill command can not kill the application in secondary
[
https://issues.apache.org/jira/browse/YARN-10174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766228#comment-17766228
]
zhengchenyu commented on YARN-10174:
I think [~youchen] means that we can get weights
[
https://issues.apache.org/jira/browse/YARN-10174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769401#comment-17769401
]
zhengchenyu commented on YARN-10174:
[~slfan1989] Thanks for your reply. Adjusting pa
zhengchenyu created YARN-10775:
--
Summary: Federation: Yarn running app web can't be unable to
connect, because AppMaster can't redirect to the right address.
Key: YARN-10775
URL: https://issues.apache.org/jira/brows
[
https://issues.apache.org/jira/browse/YARN-10775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu reassigned YARN-10775:
--
Assignee: zhengchenyu
> Federation: Yarn running app web can't be unable to connect, because
zhengchenyu created YARN-10776:
--
Summary: Make ConfiguredRMFailoverProxyProvider select
ResourceManager or Router randomly
Key: YARN-10776
URL: https://issues.apache.org/jira/browse/YARN-10776
Project: H
[
https://issues.apache.org/jira/browse/YARN-10776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu reassigned YARN-10776:
--
Assignee: zhengchenyu
> Make ConfiguredRMFailoverProxyProvider select ResourceManager or Route
[
https://issues.apache.org/jira/browse/YARN-10775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354290#comment-17354290
]
zhengchenyu commented on YARN-10775:
I think maybe we need to construct a proxy serve
[
https://issues.apache.org/jira/browse/YARN-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354292#comment-17354292
]
zhengchenyu commented on YARN-10786:
I don't think it's a good way to solve this prob
[
https://issues.apache.org/jira/browse/YARN-10775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10775:
---
Comment: was deleted
(was: I think maybe we need to construct a proxy server in nm to proxy am's web
zhengchenyu created YARN-11127:
--
Summary: Potential deadlock in AsyncDispatcher caused by
RMNodeImpl, SchedulerApplicationAttempt and RMAppImpl's lock contention.
Key: YARN-11127
URL: https://issues.apache.org/jira/b
[
https://issues.apache.org/jira/browse/YARN-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11127:
---
Description:
I found rm deadlock in our cluster. It's a low probability event. some critical
jstack
[
https://issues.apache.org/jira/browse/YARN-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11127:
---
Description:
I found rm deadlock in our cluster. It's a low probability event. some critical
jstack
[
https://issues.apache.org/jira/browse/YARN-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11127:
---
Description:
I found rm deadlock in our cluster. It's a low probability event. some critical
jstack
[
https://issues.apache.org/jira/browse/YARN-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532824#comment-17532824
]
zhengchenyu commented on YARN-11127:
aggregateLogReport introduce by YARN-1376 then t
[
https://issues.apache.org/jira/browse/YARN-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532824#comment-17532824
]
zhengchenyu edited comment on YARN-11127 at 5/6/22 12:07 PM:
-
[
https://issues.apache.org/jira/browse/YARN-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532828#comment-17532828
]
zhengchenyu commented on YARN-11127:
[~vinodkv] [~bteke] [~pbacsko] [~bilwa_st] [~z
zhengchenyu created YARN-11132:
--
Summary: RM failover may fail when Dispatcher stuck.
Key: YARN-11132
URL: https://issues.apache.org/jira/browse/YARN-11132
Project: Hadoop YARN
Issue Type: Impro
[
https://issues.apache.org/jira/browse/YARN-11132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533203#comment-17533203
]
zhengchenyu commented on YARN-11132:
I think we could watch the head element of event
[
https://issues.apache.org/jira/browse/YARN-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533204#comment-17533204
]
zhengchenyu commented on YARN-11127:
Another problem is that When dispatcher thread s
[
https://issues.apache.org/jira/browse/YARN-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11127:
---
Description:
I found rm deadlock in our cluster. It's a low probability event. some critical
jstack
[
https://issues.apache.org/jira/browse/YARN-10775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-10775:
---
Description:
I setup a yarn federation cluster, I can't connect the running app web, but the
complet
zhengchenyu created YARN-11148:
--
Summary: In federation and security mode, nm recover may fail.
Key: YARN-11148
URL: https://issues.apache.org/jira/browse/YARN-11148
Project: Hadoop YARN
Issue T
[
https://issues.apache.org/jira/browse/YARN-11148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11148:
---
Description:
Exception stack
{code:java}
2022-05-08 00:44:11,536 WARN org.apache.hadoop.ipc.Client: E
[
https://issues.apache.org/jira/browse/YARN-11148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-11148:
---
Description:
Exception stack
{code:java}
2022-05-08 00:44:11,536 WARN org.apache.hadoop.ipc.Client: E
1 - 100 of 253 matches
Mail list logo
