[
https://issues.apache.org/jira/browse/YARN-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748602#comment-17748602
]
ASF GitHub Bot commented on YARN-7402:
--------------------------------------
slfan1989 opened a new pull request, #5901:
URL: https://github.com/apache/hadoop/pull/5901
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
JIRA: YARN-7402. BackPort [GPG] Fix potential connection leak in GPGUtils.
### How was this patch tested?
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Federation V2: Global Optimizations
> -----------------------------------
>
> Key: YARN-7402
> URL: https://issues.apache.org/jira/browse/YARN-7402
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: federation
> Reporter: Carlo Curino
> Assignee: Carlo Curino
> Priority: Major
>
> YARN Federation today requires manual configuration of queues within each
> sub-cluster, and each RM operates "in isolation". This has few issues:
> # Preemption is computed locally (and might far exceed the global need)
> # Jobs within a queue are forced to consume their resources "evenly" based on
> queue mapping
> This umbrella JIRA tracks a new feature that leverages the
> FederationStateStore as a synchronization mechanism among RMs, and allows for
> allocation and preemption decisions to be based on a (close to up-to-date)
> global view of the cluster allocation and demand. The JIRA also tracks
> algorithms to automatically generate policies for Router and AMRMProxy to
> shape the traffic to each sub-cluster, and general "maintenance" of the
> FederationStateStore.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
