[
https://issues.apache.org/jira/browse/YARN-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529943#comment-16529943
]
rangjiaheng commented on YARN-8435:
-----------------------------------
Thanks [~tanujnay] for testing, it's a very good suggestion, I have fixed it in
the new patch.
Thanks [~giovanni.fumarola] for review, a new patch YARN-8435.v6.patch solved
that problem. Along with a similar bug fixed:
A client request found _userPipelineMap_ contains a user key, but get nothing
out because another client request initialize and expire the first user key.
Of course, one suggestion is to set a large yarn.router.pipeline.cache-max-size
value such as 250, to decrease initialize since LRU expiration, for a large
hadoop cluster.
> NPE when the same client simultaneously contact for the first time Yarn Router
> ------------------------------------------------------------------------------
>
> Key: YARN-8435
> URL: https://issues.apache.org/jira/browse/YARN-8435
> Project: Hadoop YARN
> Issue Type: Bug
> Components: router
> Affects Versions: 2.9.0, 3.0.2
> Reporter: rangjiaheng
> Priority: Critical
> Attachments: YARN-8435.v1.patch, YARN-8435.v2.patch,
> YARN-8435.v3.patch, YARN-8435.v4.patch, YARN-8435.v5.patch, YARN-8435.v6.patch
>
>
> When Two client process (with the same user name and the same hostname) begin
> to connect to yarn router at the same time, to submit application, kill
> application, ... and so on, then a java.lang.NullPointerException may throws
> from yarn router.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
