[
https://issues.apache.org/jira/browse/YARN-9788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015021#comment-17015021
]
Szilard Nemeth commented on YARN-9788:
--------------------------------------
Hi [~prabhujoseph],
Latest patch LGTM, committed to trunk.
Thanks [~pbacsko] for the review.
Resolving jira.
> Queue Management API does not support parallel updates
> ------------------------------------------------------
>
> Key: YARN-9788
> URL: https://issues.apache.org/jira/browse/YARN-9788
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler
> Affects Versions: 3.3.0
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Major
> Attachments: YARN-9788-001.patch, YARN-9788-002.patch,
> YARN-9788-003.patch, YARN-9788-004.patch, YARN-9788-005.patch,
> YARN-9788-006.patch, YARN-9788-007.patch, YARN-9788-008.patch,
> YARN-9788-009.patch, YARN-9788-010.patch, YARN-9788-011.patch
>
>
> Queue Management API - does not support parallel updates. When there are two
> parallel schedule conf updates (logAndApplyMutation), the first update is
> overwritten by the second one.
> Currently the logAndApplyMutation creates LogMutation and stores it in a
> variable pendingMutation. This way at any given time there will be only one
> LogMutation. And so the two parallel logAndApplyMutation will override the
> pendingMutation and the later one only will be present.
> The fix is to return LogMutation object by logAndApplyMutation which can be
> passed during confirmMutation. This fixes the parallel updates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
