[jira] [Commented] (YARN-9586) [QA] Need more doc for yarn.federation.policy-manager-params when LoadBasedRouterPolicy is used
[
https://issues.apache.org/jira/browse/YARN-9586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767779#comment-17767779
]
ASF GitHub Bot commented on YARN-9586:
--
hadoop-yetus commented on PR #6085:
URL: https://github.com/apache/hadoop/pull/6085#issuecomment-1730713344
:confetti_ball: **+1 overall**
| Vote | Subsystem | Runtime | Logfile | Comment |
|::|--:|:|::|:---:|
| +0 :ok: | reexec | 0m 38s | | Docker mode activated. |
_ Prechecks _ |
| +1 :green_heart: | dupname | 0m 0s | | No case conflicting files
found. |
| +0 :ok: | codespell | 0m 1s | | codespell was not available. |
| +0 :ok: | detsecrets | 0m 1s | | detect-secrets was not available.
|
| +0 :ok: | xmllint | 0m 1s | | xmllint was not available. |
| +0 :ok: | markdownlint | 0m 1s | | markdownlint was not available.
|
| +1 :green_heart: | @author | 0m 0s | | The patch does not contain
any @author tags. |
| +1 :green_heart: | test4tests | 0m 0s | | The patch appears to
include 3 new or modified test files. |
_ trunk Compile Tests _ |
| +0 :ok: | mvndep | 14m 34s | | Maven dependency ordering for branch |
| +1 :green_heart: | mvninstall | 31m 35s | | trunk passed |
| +1 :green_heart: | compile | 8m 0s | | trunk passed with JDK
Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 |
| +1 :green_heart: | compile | 7m 16s | | trunk passed with JDK
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05 |
| +1 :green_heart: | checkstyle | 2m 6s | | trunk passed |
| +1 :green_heart: | mvnsite | 1m 43s | | trunk passed |
| +1 :green_heart: | javadoc | 1m 42s | | trunk passed with JDK
Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 |
| +1 :green_heart: | javadoc | 1m 34s | | trunk passed with JDK
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05 |
| +0 :ok: | spotbugs | 0m 44s | |
branch/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site no spotbugs output file
(spotbugsXml.xml) |
| +1 :green_heart: | shadedclient | 34m 3s | | branch has no errors
when building and testing our client artifacts. |
_ Patch Compile Tests _ |
| +0 :ok: | mvndep | 0m 45s | | Maven dependency ordering for patch |
| +1 :green_heart: | mvninstall | 0m 42s | | the patch passed |
| +1 :green_heart: | compile | 7m 2s | | the patch passed with JDK
Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 |
| +1 :green_heart: | javac | 7m 2s | | the patch passed |
| +1 :green_heart: | compile | 7m 14s | | the patch passed with JDK
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05 |
| +1 :green_heart: | javac | 7m 14s | | the patch passed |
| +1 :green_heart: | blanks | 0m 0s | | The patch has no blanks
issues. |
| +1 :green_heart: | checkstyle | 1m 53s | | the patch passed |
| +1 :green_heart: | mvnsite | 1m 29s | | the patch passed |
| +1 :green_heart: | javadoc | 1m 23s | | the patch passed with JDK
Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 |
| +1 :green_heart: | javadoc | 1m 21s | | the patch passed with JDK
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05 |
| +0 :ok: | spotbugs | 0m 38s | |
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site has no data from spotbugs |
| +1 :green_heart: | shadedclient | 34m 22s | | patch has no errors
when building and testing our client artifacts. |
_ Other Tests _ |
| +1 :green_heart: | unit | 0m 50s | | hadoop-yarn-server-router in
the patch passed. |
| +1 :green_heart: | unit | 0m 40s | | hadoop-yarn-site in the patch
passed. |
| +1 :green_heart: | asflicense | 1m 6s | | The patch does not
generate ASF License warnings. |
| | | 174m 13s | | |
| Subsystem | Report/Notes |
|--:|:-|
| Docker | ClientAPI=1.43 ServerAPI=1.43 base:
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6085/4/artifact/out/Dockerfile
|
| GITHUB PR | https://github.com/apache/hadoop/pull/6085 |
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets xmllint
markdownlint |
| uname | Linux 11200cad1371 4.15.0-212-generic #223-Ubuntu SMP Tue May 23
13:09:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/bin/hadoop.sh |
| git revision | trunk / cad81ca702930bd8bc48213d254b7bcace134cce |
| Default Java | Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05 |
| Multi-JDK versions |
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04
/usr/lib/jvm/java-8-openjdk-amd64:Private
Build-1.8.0_382-8u382-ga-1~20.04.1-b05 |
| Test Results |
[jira] [Commented] (YARN-9048) Add znode hierarchy in Federation ZK State Store
[
https://issues.apache.org/jira/browse/YARN-9048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767698#comment-17767698
]
ASF GitHub Bot commented on YARN-9048:
--
hadoop-yetus commented on PR #6016:
URL: https://github.com/apache/hadoop/pull/6016#issuecomment-1730197958
:confetti_ball: **+1 overall**
| Vote | Subsystem | Runtime | Logfile | Comment |
|::|--:|:|::|:---:|
| +0 :ok: | reexec | 0m 38s | | Docker mode activated. |
_ Prechecks _ |
| +1 :green_heart: | dupname | 0m 0s | | No case conflicting files
found. |
| +0 :ok: | codespell | 0m 0s | | codespell was not available. |
| +0 :ok: | detsecrets | 0m 0s | | detect-secrets was not available.
|
| +0 :ok: | xmllint | 0m 0s | | xmllint was not available. |
| +1 :green_heart: | @author | 0m 0s | | The patch does not contain
any @author tags. |
| +1 :green_heart: | test4tests | 0m 0s | | The patch appears to
include 3 new or modified test files. |
_ trunk Compile Tests _ |
| +0 :ok: | mvndep | 14m 45s | | Maven dependency ordering for branch |
| +1 :green_heart: | mvninstall | 32m 15s | | trunk passed |
| +1 :green_heart: | compile | 2m 34s | | trunk passed with JDK
Ubuntu-11.0.20.1+1-post-Ubuntu-0ubuntu120.04 |
| +1 :green_heart: | compile | 2m 26s | | trunk passed with JDK
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05 |
| +1 :green_heart: | checkstyle | 1m 21s | | trunk passed |
| +1 :green_heart: | mvnsite | 1m 50s | | trunk passed |
| +1 :green_heart: | javadoc | 1m 43s | | trunk passed with JDK
Ubuntu-11.0.20.1+1-post-Ubuntu-0ubuntu120.04 |
| +1 :green_heart: | javadoc | 1m 33s | | trunk passed with JDK
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05 |
| +1 :green_heart: | spotbugs | 3m 30s | | trunk passed |
| +1 :green_heart: | shadedclient | 35m 31s | | branch has no errors
when building and testing our client artifacts. |
_ Patch Compile Tests _ |
| +0 :ok: | mvndep | 0m 32s | | Maven dependency ordering for patch |
| +1 :green_heart: | mvninstall | 1m 22s | | the patch passed |
| +1 :green_heart: | compile | 2m 28s | | the patch passed with JDK
Ubuntu-11.0.20.1+1-post-Ubuntu-0ubuntu120.04 |
| +1 :green_heart: | javac | 2m 28s | | the patch passed |
| +1 :green_heart: | compile | 2m 15s | | the patch passed with JDK
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05 |
| +1 :green_heart: | javac | 2m 15s | | the patch passed |
| +1 :green_heart: | blanks | 0m 0s | | The patch has no blanks
issues. |
| -0 :warning: | checkstyle | 1m 12s |
[/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server.txt](https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6016/11/artifact/out/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server.txt)
| hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server: The patch generated 1
new + 23 unchanged - 0 fixed = 24 total (was 23) |
| +1 :green_heart: | mvnsite | 1m 32s | | the patch passed |
| +1 :green_heart: | javadoc | 1m 22s | | the patch passed with JDK
Ubuntu-11.0.20.1+1-post-Ubuntu-0ubuntu120.04 |
| +1 :green_heart: | javadoc | 1m 19s | | the patch passed with JDK
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05 |
| +1 :green_heart: | spotbugs | 3m 31s | | the patch passed |
| +1 :green_heart: | shadedclient | 34m 13s | | patch has no errors
when building and testing our client artifacts. |
_ Other Tests _ |
| +1 :green_heart: | unit | 3m 34s | | hadoop-yarn-server-common in
the patch passed. |
| +1 :green_heart: | unit | 100m 55s | |
hadoop-yarn-server-resourcemanager in the patch passed. |
| +1 :green_heart: | asflicense | 0m 42s | | The patch does not
generate ASF License warnings. |
| | | 256m 24s | | |
| Subsystem | Report/Notes |
|--:|:-|
| Docker | ClientAPI=1.43 ServerAPI=1.43 base:
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6016/11/artifact/out/Dockerfile
|
| GITHUB PR | https://github.com/apache/hadoop/pull/6016 |
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets xmllint |
| uname | Linux 78fcacc94f6e 4.15.0-212-generic #223-Ubuntu SMP Tue May 23
13:09:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/bin/hadoop.sh |
| git revision | trunk / d928dd2a07fb986893d5a7e67146b5134ded7343 |
| Default Java | Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05 |
| Multi-JDK versions |
[jira] [Updated] (YARN-11575) the connection of resourcemanager with datanode cannot close after executing the command yarn application -status ats-hbase
[ https://issues.apache.org/jira/browse/YARN-11575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhixing updated YARN-11575: --- Description: I encountered a yarn bug where executing the command "yarn application -status ats-hbase" leads to a connection leak between the resourcemanager and datanode. The resourcemanager does not close the connections with the datanode, and on the resourcemanager node, many TCP connections with the datanode are in the CLOSE_WAIT state The relevant issue and log screenshots are as follows. The tcpdump log capturing port 1019 is shown below this is the resourcemanager log !微信图片_20230827102251.png! this is the resourcemanager process !微信图片_20230827102340.png! This is the tcpdump package info of resourcemanager with datanode 1019 port !微信图片_20230827103545.png! this is the tcp connection of resoucemanager with datanode, after rm running a period of time will leave many close_wait state connection. !image-2023-09-21-23-51-01-583.png! my service version is amabri: 3.1.1.3.1.0.0-78 HDFS: 3.1.1.3.1 yarn: 3.1.0 was: I encountered a yarn bug where executing the command "yarn application -status ats-hbase" leads to a connection leak between the resourcemanager and datanode. The resourcemanager does not close the connections with the datanode, and on the resourcemanager node, many TCP connections with the datanode are in the CLOSE_WAIT state The relevant issue and log screenshots are as follows. The tcpdump log capturing port 1019 is shown below This is the tcpdump package of resourcemanager with datanode 1019 port this is the resourcemanager log !微信图片_20230827102251.png! this is the resourcemanager process !微信图片_20230827102340.png! This is the tcpdump package info of resourcemanager with datanode 1019 port !微信图片_20230827103545.png! this is the tcp connection of resoucemanager with datanode, after rm running a period of time will leave many close_wait state connection. !image-2023-09-21-23-51-01-583.png! my service version is amabri: 3.1.1.3.1.0.0-78 HDFS: 3.1.1.3.1 yarn: 3.1.0 > the connection of resourcemanager with datanode cannot close after executing > the command yarn application -status ats-hbase > --- > > Key: YARN-11575 > URL: https://issues.apache.org/jira/browse/YARN-11575 > Project: Hadoop YARN > Issue Type: Bug > Components: ATSv2, resourcemanager >Affects Versions: 3.1.0 >Reporter: zhixing >Priority: Major > Attachments: 5B985F102FAF4EECA0CAD1D20019D181.PNG-1.crdownload, > 5B985F102FAF4EECA0CAD1D20019D181.PNG.crdownload, > image-2023-09-21-23-51-01-583.png, 微信图片_20230827102251.png, > 微信图片_20230827102340.png, 微信图片_20230827103545.png > > > I encountered a yarn bug where executing the command "yarn application > -status ats-hbase" leads to a connection leak between the resourcemanager and > datanode. The resourcemanager does not close the connections with the > datanode, and on the resourcemanager node, many TCP connections with the > datanode are in the CLOSE_WAIT state > The relevant issue and log screenshots are as follows. The tcpdump log > capturing port 1019 is shown below > > this is the resourcemanager log > !微信图片_20230827102251.png! > > this is the resourcemanager process > !微信图片_20230827102340.png! > > > This is the tcpdump package info of resourcemanager with datanode 1019 port > !微信图片_20230827103545.png! > > this is the tcp connection of resoucemanager with datanode, after rm running > a period of time will leave many close_wait state connection. > !image-2023-09-21-23-51-01-583.png! > > > my service version is > amabri: 3.1.1.3.1.0.0-78 > HDFS: 3.1.1.3.1 > yarn: 3.1.0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11575) the connection of resourcemanager with datanode cannot close after executing the command yarn application -status ats-hbase
[ https://issues.apache.org/jira/browse/YARN-11575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhixing updated YARN-11575: --- Description: I encountered a yarn bug where executing the command "yarn application -status ats-hbase" leads to a connection leak between the resourcemanager and datanode. The resourcemanager does not close the connections with the datanode, and on the resourcemanager node, many TCP connections with the datanode are in the CLOSE_WAIT state The relevant issue and log screenshots are as follows. The tcpdump log capturing port 1019 is shown below This is the tcpdump package of resourcemanager with datanode 1019 port this is the resourcemanager log !微信图片_20230827102251.png! this is the resourcemanager process !微信图片_20230827102340.png! This is the tcpdump package info of resourcemanager with datanode 1019 port !微信图片_20230827103545.png! this is the tcp connection of resoucemanager with datanode, after rm running a period of time will leave many close_wait state connection. !image-2023-09-21-23-51-01-583.png! my service version is amabri: 3.1.1.3.1.0.0-78 HDFS: 3.1.1.3.1 yarn: 3.1.0 was: I encountered a yarn bug where executing the command "yarn application -status ats-hbase" leads to a connection leak between the resourcemanager and datanode. The resourcemanager does not close the connections with the datanode, and on the resourcemanager node, many TCP connections with the datanode are in the CLOSE_WAIT state The relevant issue and log screenshots are as follows. The tcpdump log capturing port 1019 is shown below This is the tcpdump package of resourcemanager with datanode 1019 port this is the resourcemanager log !微信图片_20230827102251.png! this is the resourcemanager process !微信图片_20230827102340.png! This is the tcpdump package info of resourcemanager with datanode 1019 port !微信图片_20230827103545.png! this is the tcp connection of resoucemanager with datanode, after rm running a period of time will leave many close_wait state connection. !image-2023-09-21-23-51-01-583.png! my service version is amabri: 3.1.1.3.1.0.0-78 HDFS: 3.1.1.3.1 yarn: 3.1.0 > the connection of resourcemanager with datanode cannot close after executing > the command yarn application -status ats-hbase > --- > > Key: YARN-11575 > URL: https://issues.apache.org/jira/browse/YARN-11575 > Project: Hadoop YARN > Issue Type: Bug > Components: ATSv2, resourcemanager >Affects Versions: 3.1.0 >Reporter: zhixing >Priority: Major > Attachments: 5B985F102FAF4EECA0CAD1D20019D181.PNG-1.crdownload, > 5B985F102FAF4EECA0CAD1D20019D181.PNG.crdownload, > image-2023-09-21-23-51-01-583.png, 微信图片_20230827102251.png, > 微信图片_20230827102340.png, 微信图片_20230827103545.png > > > I encountered a yarn bug where executing the command "yarn application > -status ats-hbase" leads to a connection leak between the resourcemanager and > datanode. The resourcemanager does not close the connections with the > datanode, and on the resourcemanager node, many TCP connections with the > datanode are in the CLOSE_WAIT state > The relevant issue and log screenshots are as follows. The tcpdump log > capturing port 1019 is shown below > > This is the tcpdump package of resourcemanager with datanode 1019 port > > this is the resourcemanager log > !微信图片_20230827102251.png! > > this is the resourcemanager process > !微信图片_20230827102340.png! > > > This is the tcpdump package info of resourcemanager with datanode 1019 port > !微信图片_20230827103545.png! > > this is the tcp connection of resoucemanager with datanode, after rm running > a period of time will leave many close_wait state connection. > !image-2023-09-21-23-51-01-583.png! > > > my service version is > amabri: 3.1.1.3.1.0.0-78 > HDFS: 3.1.1.3.1 > yarn: 3.1.0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11575) the connection of resourcemanager with datanode cannot close after executing the command yarn application -status ats-hbase
[ https://issues.apache.org/jira/browse/YARN-11575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhixing updated YARN-11575: --- Attachment: image-2023-09-21-23-51-01-583.png 5B985F102FAF4EECA0CAD1D20019D181.PNG-1.crdownload 5B985F102FAF4EECA0CAD1D20019D181.PNG.crdownload 微信图片_20230827103545.png 微信图片_20230827102340.png 微信图片_20230827102251.png Component/s: ATSv2 resourcemanager Affects Version/s: 3.1.0 Description: I encountered a yarn bug where executing the command "yarn application -status ats-hbase" leads to a connection leak between the resourcemanager and datanode. The resourcemanager does not close the connections with the datanode, and on the resourcemanager node, many TCP connections with the datanode are in the CLOSE_WAIT state The relevant issue and log screenshots are as follows. The tcpdump log capturing port 1019 is shown below This is the tcpdump package of resourcemanager with datanode 1019 port this is the resourcemanager log !微信图片_20230827102251.png! this is the resourcemanager process !微信图片_20230827102340.png! This is the tcpdump package info of resourcemanager with datanode 1019 port !微信图片_20230827103545.png! this is the tcp connection of resoucemanager with datanode, after rm running a period of time will leave many close_wait state connection. !image-2023-09-21-23-51-01-583.png! my service version is amabri: 3.1.1.3.1.0.0-78 HDFS: 3.1.1.3.1 yarn: 3.1.0 Summary: the connection of resourcemanager with datanode cannot close after executing the command yarn application -status ats-hbase (was: resourcemanager connection with datanode leak) > the connection of resourcemanager with datanode cannot close after executing > the command yarn application -status ats-hbase > --- > > Key: YARN-11575 > URL: https://issues.apache.org/jira/browse/YARN-11575 > Project: Hadoop YARN > Issue Type: Bug > Components: ATSv2, resourcemanager >Affects Versions: 3.1.0 >Reporter: zhixing >Priority: Major > Attachments: 5B985F102FAF4EECA0CAD1D20019D181.PNG-1.crdownload, > 5B985F102FAF4EECA0CAD1D20019D181.PNG.crdownload, > image-2023-09-21-23-51-01-583.png, 微信图片_20230827102251.png, > 微信图片_20230827102340.png, 微信图片_20230827103545.png > > > I encountered a yarn bug where executing the command "yarn application > -status ats-hbase" leads to a connection leak between the resourcemanager and > datanode. The resourcemanager does not close the connections with the > datanode, and on the resourcemanager node, many TCP connections with the > datanode are in the CLOSE_WAIT state > The relevant issue and log screenshots are as follows. The tcpdump log > capturing port 1019 is shown below > > This is the tcpdump package of resourcemanager with datanode 1019 port > > this is the resourcemanager log > !微信图片_20230827102251.png! > > this is the resourcemanager process > !微信图片_20230827102340.png! > > > This is the tcpdump package info of resourcemanager with datanode 1019 port > !微信图片_20230827103545.png! > > this is the tcp connection of resoucemanager with datanode, after rm running > a period of time will leave many close_wait state connection. > !image-2023-09-21-23-51-01-583.png! > > > my service version is > amabri: 3.1.1.3.1.0.0-78 > HDFS: 3.1.1.3.1 > yarn: 3.1.0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11575) resourcemanager connection with datanode leak
zhixing created YARN-11575: -- Summary: resourcemanager connection with datanode leak Key: YARN-11575 URL: https://issues.apache.org/jira/browse/YARN-11575 Project: Hadoop YARN Issue Type: Bug Reporter: zhixing -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9586) [QA] Need more doc for yarn.federation.policy-manager-params when LoadBasedRouterPolicy is used
[
https://issues.apache.org/jira/browse/YARN-9586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767610#comment-17767610
]
ASF GitHub Bot commented on YARN-9586:
--
slfan1989 commented on code in PR #6085:
URL: https://github.com/apache/hadoop/pull/6085#discussion_r1333252911
##
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router/src/test/java/org/apache/hadoop/yarn/server/router/subcluster/fair/TestYarnFederationWithFairScheduler.java:
##
@@ -71,5 +71,6 @@ public void testGetClusterInfo() throws InterruptedException,
IOException {
assertNotNull(clusterInfo);
assertTrue(subClusters.contains(clusterInfo.getSubClusterId()));
}
+Thread.sleep(2000);
Review Comment:
Thank you very much for your help in reviewing the code! I introduced this
code during local testing and started a small cluster. I will fix it.
> [QA] Need more doc for yarn.federation.policy-manager-params when
> LoadBasedRouterPolicy is used
> ---
>
> Key: YARN-9586
> URL: https://issues.apache.org/jira/browse/YARN-9586
> Project: Hadoop YARN
> Issue Type: Wish
> Components: federation
>Reporter: Shen Yinjie
>Assignee: Shilun Fan
>Priority: Major
> Labels: pull-request-available
>
> We picked LoadBasedRouterPolicy for YARN federation, but had no idea what to
> set to yarn.federation.policy-manager-params. Is there a demo config or more
> detailed description for this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11468) Zookeeper SSL/TLS support
[ https://issues.apache.org/jira/browse/YARN-11468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ferenc Erdelyi updated YARN-11468: -- Description: Zookeeper 3.5.5 server can operate with SSL/TLS secure connection with its clients. [https://cwiki.apache.org/confluence/display/ZOOKEEPER/ZooKeeper+SSL+User+Guide] The SSL communication should be possible in the different parts of YARN, where it communicates with Zookeeper servers. The Zookeeper clients are used in the following places: * ResourceManager * ZKConfigurationStore * ZKRMStateStore The yarn.resourcemanager.zk-client-ssl.enabled flag to enable SSL communication should be provided in the yarn-default.xml and the required parameters for the keystore and truststore should be picked up from the core-default.xml (HADOOP-18709) yarn.resourcemanager.ha.curator-leader-elector.enabled has to set to true via yarn-site.xml to make sure Curator is used, otherwise we can't enable SSL. was: Zookeeper 3.5.5 server can operate with SSL/TLS secure connection with its clients. [https://cwiki.apache.org/confluence/display/ZOOKEEPER/ZooKeeper+SSL+User+Guide] The SSL communication should be possible in the different parts of YARN, where it communicates with Zookeeper servers. The Zookeeper clients are used in the following places: * ResourceManager * ZKConfigurationStore * ZKRMStateStore The yarn.resourcemanager.zk-client-ssl.enabled flag to enable SSL communication should be provided in the yarn-default.xml and the required parameters for the keystore and truststore should be picked up from the core-default.xml (HADOOP-18709) > Zookeeper SSL/TLS support > - > > Key: YARN-11468 > URL: https://issues.apache.org/jira/browse/YARN-11468 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Ferenc Erdelyi >Assignee: Ferenc Erdelyi >Priority: Critical > > Zookeeper 3.5.5 server can operate with SSL/TLS secure connection with its > clients. > [https://cwiki.apache.org/confluence/display/ZOOKEEPER/ZooKeeper+SSL+User+Guide] > The SSL communication should be possible in the different parts of YARN, > where it communicates with Zookeeper servers. The Zookeeper clients are used > in the following places: > * ResourceManager > * ZKConfigurationStore > * ZKRMStateStore > The yarn.resourcemanager.zk-client-ssl.enabled flag to enable SSL > communication should be provided in the yarn-default.xml and the required > parameters for the keystore and truststore should be picked up from the > core-default.xml (HADOOP-18709) > yarn.resourcemanager.ha.curator-leader-elector.enabled has to set to true via > yarn-site.xml to make sure Curator is used, otherwise we can't enable SSL. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
