[jira] [Commented] (YARN-2372) There are Chinese Characters in the FairScheduler's document
[ https://issues.apache.org/jira/browse/YARN-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150543#comment-14150543 ] Hudson commented on YARN-2372: -- FAILURE: Integrated in Hadoop-Yarn-trunk #693 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/693/]) YARN-2372. There are Chinese Characters in the FairScheduler's document (Fengdong Yu via aw) (aw: rev 32870db0fb91e115b5e44edb7b313368e8e81b1e) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/FairScheduler.apt.vm > There are Chinese Characters in the FairScheduler's document > > > Key: YARN-2372 > URL: https://issues.apache.org/jira/browse/YARN-2372 > Project: Hadoop YARN > Issue Type: Improvement > Components: documentation >Affects Versions: 2.4.1 >Reporter: Fengdong Yu >Assignee: Fengdong Yu >Priority: Minor > Fix For: 2.6.0 > > Attachments: YARN-2372.patch, YARN-2372.patch, YARN-2372.patch, > YARN-2372.patch, YARN-2372.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-668) TokenIdentifier serialization should consider Unknown fields
[ https://issues.apache.org/jira/browse/YARN-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150552#comment-14150552 ] Hudson commented on YARN-668: - FAILURE: Integrated in Hadoop-Yarn-trunk #693 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/693/]) YARN-668. Changed NMTokenIdentifier/AMRMTokenIdentifier/ContainerTokenIdentifier to use protobuf object as the payload. Contributed by Junping Du. (jianhe: rev 5391919b09ce9549d13c897aa89bb0a0536760fe) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/pom.xml * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/security/ContainerTokenIdentifier.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/proto/server/yarn_security_token.proto * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/container/TestContainer.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/pom.xml * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/proto/test_amrm_token.proto * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/ContainerManagerImpl.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/ContainerTokenIdentifierForTest.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/TestContainerManagerSecurity.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/pom.xml * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/api/impl/AMRMTokenIdentifierForTest.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/security/NMTokenIdentifier.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/api/impl/TestAMRMClient.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/security/AMRMTokenIdentifier.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/proto/test_token.proto * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/security/TestYARNTokenIdentifier.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/NMTokenIdentifierNewForTest.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestApplicationMasterService.java * hadoop-yarn-project/CHANGES.txt > TokenIdentifier serialization should consider Unknown fields > > > Key: YARN-668 > URL: https://issues.apache.org/jira/browse/YARN-668 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Siddharth Seth >Assignee: Junping Du >Priority: Blocker > Fix For: 2.6.0 > > Attachments: YARN-668-demo.patch, YARN-668-v10.patch, > YARN-668-v2.patch, YARN-668-v3.patch, YARN-668-v4.patch, YARN-668-v5.patch, > YARN-668-v6.patch, YARN-668-v7.patch, YARN-668-v8.patch, YARN-668-v9.patch, > YARN-668.patch > > > This would allow changing of the TokenIdentifier between versions. The > current serialization is Writable. A simple way to achieve this would be to > have a Proto object as the payload for TokenIdentifiers, instead of > individual fields. > TokenIdentifier continues to implement Writable to work with the RPC layer - > but the payload itself is serialized using PB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2577) Clarify ACL delimiter and how to configure ACL groups only
[ https://issues.apache.org/jira/browse/YARN-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150549#comment-14150549 ] Hudson commented on YARN-2577: -- FAILURE: Integrated in Hadoop-Yarn-trunk #693 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/693/]) YARN-2577. Clarify ACL delimiter and how to configure ACL groups only (Mikos Christine via aw) (aw: rev ac70c27473251b389f32f4a33085d6a9ee3a0b3c) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/FairScheduler.apt.vm * hadoop-yarn-project/CHANGES.txt > Clarify ACL delimiter and how to configure ACL groups only > -- > > Key: YARN-2577 > URL: https://issues.apache.org/jira/browse/YARN-2577 > Project: Hadoop YARN > Issue Type: Improvement > Components: documentation, fairscheduler >Affects Versions: 2.5.1 >Reporter: Miklos Christine >Assignee: Miklos Christine >Priority: Trivial > Labels: newbie > Fix For: 2.6.0 > > Attachments: YARN-2577.patch > > > Reading through the Fair Scheduler documentation, it would be great to > explicitly state that the delimiter for the fair scheduler ACLs is the space > character. > If specifying only ACL groups, users should begin the value with the space > character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-2280) Resource manager web service fields are not accessible
[ https://issues.apache.org/jira/browse/YARN-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Horvath updated YARN-2280: Priority: Trivial (was: Minor) > Resource manager web service fields are not accessible > -- > > Key: YARN-2280 > URL: https://issues.apache.org/jira/browse/YARN-2280 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0, 2.4.1 >Reporter: Krisztian Horvath >Assignee: Krisztian Horvath >Priority: Trivial > Fix For: 2.6.0 > > Attachments: YARN-2280.patch > > > Using the resource manager's rest api > (org.apache.hadoop.yarn.server.resourcemanager.webapp.RMWebServices) some > rest call returns a class where the fields after the unmarshal cannot be > accessible. For example SchedulerTypeInfo -> schedulerInfo. Using the same > classes on client side these fields only accessible via reflection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2577) Clarify ACL delimiter and how to configure ACL groups only
[ https://issues.apache.org/jira/browse/YARN-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150604#comment-14150604 ] Hudson commented on YARN-2577: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1884 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1884/]) YARN-2577. Clarify ACL delimiter and how to configure ACL groups only (Mikos Christine via aw) (aw: rev ac70c27473251b389f32f4a33085d6a9ee3a0b3c) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/FairScheduler.apt.vm * hadoop-yarn-project/CHANGES.txt > Clarify ACL delimiter and how to configure ACL groups only > -- > > Key: YARN-2577 > URL: https://issues.apache.org/jira/browse/YARN-2577 > Project: Hadoop YARN > Issue Type: Improvement > Components: documentation, fairscheduler >Affects Versions: 2.5.1 >Reporter: Miklos Christine >Assignee: Miklos Christine >Priority: Trivial > Labels: newbie > Fix For: 2.6.0 > > Attachments: YARN-2577.patch > > > Reading through the Fair Scheduler documentation, it would be great to > explicitly state that the delimiter for the fair scheduler ACLs is the space > character. > If specifying only ACL groups, users should begin the value with the space > character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2372) There are Chinese Characters in the FairScheduler's document
[ https://issues.apache.org/jira/browse/YARN-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150598#comment-14150598 ] Hudson commented on YARN-2372: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1884 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1884/]) YARN-2372. There are Chinese Characters in the FairScheduler's document (Fengdong Yu via aw) (aw: rev 32870db0fb91e115b5e44edb7b313368e8e81b1e) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/FairScheduler.apt.vm * hadoop-yarn-project/CHANGES.txt > There are Chinese Characters in the FairScheduler's document > > > Key: YARN-2372 > URL: https://issues.apache.org/jira/browse/YARN-2372 > Project: Hadoop YARN > Issue Type: Improvement > Components: documentation >Affects Versions: 2.4.1 >Reporter: Fengdong Yu >Assignee: Fengdong Yu >Priority: Minor > Fix For: 2.6.0 > > Attachments: YARN-2372.patch, YARN-2372.patch, YARN-2372.patch, > YARN-2372.patch, YARN-2372.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-668) TokenIdentifier serialization should consider Unknown fields
[ https://issues.apache.org/jira/browse/YARN-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150607#comment-14150607 ] Hudson commented on YARN-668: - SUCCESS: Integrated in Hadoop-Hdfs-trunk #1884 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1884/]) YARN-668. Changed NMTokenIdentifier/AMRMTokenIdentifier/ContainerTokenIdentifier to use protobuf object as the payload. Contributed by Junping Du. (jianhe: rev 5391919b09ce9549d13c897aa89bb0a0536760fe) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/pom.xml * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/proto/test_amrm_token.proto * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/proto/test_token.proto * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/pom.xml * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/security/NMTokenIdentifier.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/container/TestContainer.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/ContainerManagerImpl.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestApplicationMasterService.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/api/impl/AMRMTokenIdentifierForTest.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/api/impl/TestAMRMClient.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/ContainerTokenIdentifierForTest.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/pom.xml * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/proto/server/yarn_security_token.proto * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/security/TestYARNTokenIdentifier.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/security/ContainerTokenIdentifier.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/security/AMRMTokenIdentifier.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/TestContainerManagerSecurity.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/NMTokenIdentifierNewForTest.java > TokenIdentifier serialization should consider Unknown fields > > > Key: YARN-668 > URL: https://issues.apache.org/jira/browse/YARN-668 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Siddharth Seth >Assignee: Junping Du >Priority: Blocker > Fix For: 2.6.0 > > Attachments: YARN-668-demo.patch, YARN-668-v10.patch, > YARN-668-v2.patch, YARN-668-v3.patch, YARN-668-v4.patch, YARN-668-v5.patch, > YARN-668-v6.patch, YARN-668-v7.patch, YARN-668-v8.patch, YARN-668-v9.patch, > YARN-668.patch > > > This would allow changing of the TokenIdentifier between versions. The > current serialization is Writable. A simple way to achieve this would be to > have a Proto object as the payload for TokenIdentifiers, instead of > individual fields. > TokenIdentifier continues to implement Writable to work with the RPC layer - > but the payload itself is serialized using PB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2372) There are Chinese Characters in the FairScheduler's document
[ https://issues.apache.org/jira/browse/YARN-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150624#comment-14150624 ] Hudson commented on YARN-2372: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1909 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1909/]) YARN-2372. There are Chinese Characters in the FairScheduler's document (Fengdong Yu via aw) (aw: rev 32870db0fb91e115b5e44edb7b313368e8e81b1e) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/FairScheduler.apt.vm > There are Chinese Characters in the FairScheduler's document > > > Key: YARN-2372 > URL: https://issues.apache.org/jira/browse/YARN-2372 > Project: Hadoop YARN > Issue Type: Improvement > Components: documentation >Affects Versions: 2.4.1 >Reporter: Fengdong Yu >Assignee: Fengdong Yu >Priority: Minor > Fix For: 2.6.0 > > Attachments: YARN-2372.patch, YARN-2372.patch, YARN-2372.patch, > YARN-2372.patch, YARN-2372.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-668) TokenIdentifier serialization should consider Unknown fields
[ https://issues.apache.org/jira/browse/YARN-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150633#comment-14150633 ] Hudson commented on YARN-668: - FAILURE: Integrated in Hadoop-Mapreduce-trunk #1909 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1909/]) YARN-668. Changed NMTokenIdentifier/AMRMTokenIdentifier/ContainerTokenIdentifier to use protobuf object as the payload. Contributed by Junping Du. (jianhe: rev 5391919b09ce9549d13c897aa89bb0a0536760fe) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/NMTokenIdentifierNewForTest.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/security/NMTokenIdentifier.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/TestContainerManagerSecurity.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/proto/server/yarn_security_token.proto * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/proto/test_token.proto * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/ContainerTokenIdentifierForTest.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestApplicationMasterService.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/pom.xml * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/security/ContainerTokenIdentifier.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/proto/test_amrm_token.proto * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/api/impl/AMRMTokenIdentifierForTest.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/security/AMRMTokenIdentifier.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/ContainerManagerImpl.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/container/TestContainer.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/security/TestYARNTokenIdentifier.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/api/impl/TestAMRMClient.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/pom.xml * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/pom.xml > TokenIdentifier serialization should consider Unknown fields > > > Key: YARN-668 > URL: https://issues.apache.org/jira/browse/YARN-668 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Siddharth Seth >Assignee: Junping Du >Priority: Blocker > Fix For: 2.6.0 > > Attachments: YARN-668-demo.patch, YARN-668-v10.patch, > YARN-668-v2.patch, YARN-668-v3.patch, YARN-668-v4.patch, YARN-668-v5.patch, > YARN-668-v6.patch, YARN-668-v7.patch, YARN-668-v8.patch, YARN-668-v9.patch, > YARN-668.patch > > > This would allow changing of the TokenIdentifier between versions. The > current serialization is Writable. A simple way to achieve this would be to > have a Proto object as the payload for TokenIdentifiers, instead of > individual fields. > TokenIdentifier continues to implement Writable to work with the RPC layer - > but the payload itself is serialized using PB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2577) Clarify ACL delimiter and how to configure ACL groups only
[ https://issues.apache.org/jira/browse/YARN-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150630#comment-14150630 ] Hudson commented on YARN-2577: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1909 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1909/]) YARN-2577. Clarify ACL delimiter and how to configure ACL groups only (Mikos Christine via aw) (aw: rev ac70c27473251b389f32f4a33085d6a9ee3a0b3c) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/FairScheduler.apt.vm * hadoop-yarn-project/CHANGES.txt > Clarify ACL delimiter and how to configure ACL groups only > -- > > Key: YARN-2577 > URL: https://issues.apache.org/jira/browse/YARN-2577 > Project: Hadoop YARN > Issue Type: Improvement > Components: documentation, fairscheduler >Affects Versions: 2.5.1 >Reporter: Miklos Christine >Assignee: Miklos Christine >Priority: Trivial > Labels: newbie > Fix For: 2.6.0 > > Attachments: YARN-2577.patch > > > Reading through the Fair Scheduler documentation, it would be great to > explicitly state that the delimiter for the fair scheduler ACLs is the space > character. > If specifying only ACL groups, users should begin the value with the space > character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-2606) Application History Server tries to access hdfs before doing secure login
[ https://issues.apache.org/jira/browse/YARN-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated YARN-2606: Attachment: YARN-2606.patch [~zjshen], [~jeagles] : Attaching the new patch that modifies the serviceInit() to not do any FS operations > Application History Server tries to access hdfs before doing secure login > - > > Key: YARN-2606 > URL: https://issues.apache.org/jira/browse/YARN-2606 > Project: Hadoop YARN > Issue Type: Bug > Components: timelineserver >Affects Versions: 2.6.0 >Reporter: Mit Desai >Assignee: Mit Desai > Attachments: YARN-2606.patch, YARN-2606.patch > > > While testing the Application Timeline Server, the server would not come up > in a secure cluster, as it would keep trying to access hdfs without having > done the secure login. It would repeatedly try authenticating and finally hit > stack overflow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2606) Application History Server tries to access hdfs before doing secure login
[
https://issues.apache.org/jira/browse/YARN-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150691#comment-14150691
]
Hadoop QA commented on YARN-2606:
-
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12671659/YARN-2606.patch
against trunk revision 5f16c98.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/5164//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5164//console
This message is automatically generated.
> Application History Server tries to access hdfs before doing secure login
> -
>
> Key: YARN-2606
> URL: https://issues.apache.org/jira/browse/YARN-2606
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Affects Versions: 2.6.0
>Reporter: Mit Desai
>Assignee: Mit Desai
> Attachments: YARN-2606.patch, YARN-2606.patch
>
>
> While testing the Application Timeline Server, the server would not come up
> in a secure cluster, as it would keep trying to access hdfs without having
> done the secure login. It would repeatedly try authenticating and finally hit
> stack overflow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-2613) NMClient doesn't have retries for supporting rolling-upgrades
[ https://issues.apache.org/jira/browse/YARN-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2613: -- Attachment: YARN-2613.2.patch Refactored the previous patch a bit and changed RpcClientFactoryPBImpl#stopClient accordingly so that in case RetryProxy is used, RetryInvocationHandler#close can be invoked properly to stop the proxy. > NMClient doesn't have retries for supporting rolling-upgrades > - > > Key: YARN-2613 > URL: https://issues.apache.org/jira/browse/YARN-2613 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Jian He >Assignee: Jian He > Attachments: YARN-2613.1.patch, YARN-2613.2.patch > > > While NM is rolling upgrade, client should retry NM until it comes up. This > jira is to add a NMProxy (similar to RMProxy) with retry implementation to > support rolling upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2613) NMClient doesn't have retries for supporting rolling-upgrades
[
https://issues.apache.org/jira/browse/YARN-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150839#comment-14150839
]
Hadoop QA commented on YARN-2613:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12671673/YARN-2613.2.patch
against trunk revision 7f300bc.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/5165//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5165//console
This message is automatically generated.
> NMClient doesn't have retries for supporting rolling-upgrades
> -
>
> Key: YARN-2613
> URL: https://issues.apache.org/jira/browse/YARN-2613
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Jian He
>Assignee: Jian He
> Attachments: YARN-2613.1.patch, YARN-2613.2.patch
>
>
> While NM is rolling upgrade, client should retry NM until it comes up. This
> jira is to add a NMProxy (similar to RMProxy) with retry implementation to
> support rolling upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
