[jira] [Updated] (YARN-10820) Make GetClusterNodesRequestPBImpl thread safe
[
https://issues.apache.org/jira/browse/YARN-10820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma updated YARN-10820:
Fix Version/s: 3.2.4
3.3.3
> Make GetClusterNodesRequestPBImpl thread safe
> -
>
> Key: YARN-10820
> URL: https://issues.apache.org/jira/browse/YARN-10820
> Project: Hadoop YARN
> Issue Type: Task
> Components: client
>Affects Versions: 3.1.0, 3.3.0
>Reporter: Prabhu Joseph
>Assignee: SwathiChandrashekar
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.2.4, 3.3.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> yarn node list intermittently fails with below
> {code:java}
> 2021-06-13 11:26:42,316 WARN client.RequestHedgingRMFailoverProxyProvider:
> Invocation returned exception: java.lang.ArrayIndexOutOfBoundsException: 1 on
> [resourcemanager-1], so propagating back to caller.
> Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 1
> at java.util.ArrayList.add(ArrayList.java:465)
> at
> org.apache.hadoop.yarn.proto.YarnServiceProtos$GetClusterNodesRequestProto$Builder.addAllNodeStates(YarnServiceProtos.java:28009)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.mergeLocalToBuilder(GetClusterNodesRequestPBImpl.java:124)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.mergeLocalToProto(GetClusterNodesRequestPBImpl.java:82)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.getProto(GetClusterNodesRequestPBImpl.java:56)
> at
> org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getClusterNodes(ApplicationClientProtocolPBClientImpl.java:329)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:422)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeMethod(RetryInvocationHandler.java:165)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invoke(RetryInvocationHandler.java:157)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:95)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:359)
> at com.sun.proxy.$Proxy8.getClusterNodes(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider$RMRequestHedgingInvocationHandler$1.call(RequestHedgingRMFailoverProxyProvider.java:159)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 2021-06-13 11:27:58,415 WARN client.RequestHedgingRMFailoverProxyProvider:
> Invocation returned exception: java.lang.UnsupportedOperationException on
> [resourcemanager-0], so propagating back to caller.
> Exception in thread "main" java.lang.UnsupportedOperationException
> at
> java.util.Collections$UnmodifiableCollection.add(Collections.java:1057)
> at
> org.apache.hadoop.yarn.proto.YarnServiceProtos$GetClusterNodesRequestProto$Builder.addAllNodeStates(YarnServiceProtos.java:28009)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.mergeLocalToBuilder(GetClusterNodesRequestPBImpl.java:124)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.mergeLocalToProto(GetClusterNodesRequestPBImpl.java:82)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.getProto(GetClusterNodesRequestPBImpl.java:56)
> at
> org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getClusterNodes(ApplicationClientProtocolPBClientImpl.java:329)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(
[jira] [Commented] (YARN-10820) Make GetClusterNodesRequestPBImpl thread safe
[
https://issues.apache.org/jira/browse/YARN-10820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453788#comment-17453788
]
Takanobu Asanuma commented on YARN-10820:
-
We confirmed that 3.3.1 with this commit worked out. I cherry-picked it to
branch-3.3 and branch-3.2. Thanks.
> Make GetClusterNodesRequestPBImpl thread safe
> -
>
> Key: YARN-10820
> URL: https://issues.apache.org/jira/browse/YARN-10820
> Project: Hadoop YARN
> Issue Type: Task
> Components: client
>Affects Versions: 3.1.0, 3.3.0
>Reporter: Prabhu Joseph
>Assignee: SwathiChandrashekar
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> yarn node list intermittently fails with below
> {code:java}
> 2021-06-13 11:26:42,316 WARN client.RequestHedgingRMFailoverProxyProvider:
> Invocation returned exception: java.lang.ArrayIndexOutOfBoundsException: 1 on
> [resourcemanager-1], so propagating back to caller.
> Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 1
> at java.util.ArrayList.add(ArrayList.java:465)
> at
> org.apache.hadoop.yarn.proto.YarnServiceProtos$GetClusterNodesRequestProto$Builder.addAllNodeStates(YarnServiceProtos.java:28009)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.mergeLocalToBuilder(GetClusterNodesRequestPBImpl.java:124)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.mergeLocalToProto(GetClusterNodesRequestPBImpl.java:82)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.getProto(GetClusterNodesRequestPBImpl.java:56)
> at
> org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getClusterNodes(ApplicationClientProtocolPBClientImpl.java:329)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:422)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeMethod(RetryInvocationHandler.java:165)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invoke(RetryInvocationHandler.java:157)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:95)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:359)
> at com.sun.proxy.$Proxy8.getClusterNodes(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider$RMRequestHedgingInvocationHandler$1.call(RequestHedgingRMFailoverProxyProvider.java:159)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 2021-06-13 11:27:58,415 WARN client.RequestHedgingRMFailoverProxyProvider:
> Invocation returned exception: java.lang.UnsupportedOperationException on
> [resourcemanager-0], so propagating back to caller.
> Exception in thread "main" java.lang.UnsupportedOperationException
> at
> java.util.Collections$UnmodifiableCollection.add(Collections.java:1057)
> at
> org.apache.hadoop.yarn.proto.YarnServiceProtos$GetClusterNodesRequestProto$Builder.addAllNodeStates(YarnServiceProtos.java:28009)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.mergeLocalToBuilder(GetClusterNodesRequestPBImpl.java:124)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.mergeLocalToProto(GetClusterNodesRequestPBImpl.java:82)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.getProto(GetClusterNodesRequestPBImpl.java:56)
> at
> org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getClusterNodes(ApplicationClientProtocolPBClientImpl.java:329)
> at sun.reflect.Nat
[jira] [Commented] (YARN-10820) Make GetClusterNodesRequestPBImpl thread safe
[
https://issues.apache.org/jira/browse/YARN-10820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17447217#comment-17447217
]
Takanobu Asanuma commented on YARN-10820:
-
Hi [~prabhujoseph], could you backport it to branch-3.3 and branch-3.2? We
recently faced this issue in 3.3.1.
> Make GetClusterNodesRequestPBImpl thread safe
> -
>
> Key: YARN-10820
> URL: https://issues.apache.org/jira/browse/YARN-10820
> Project: Hadoop YARN
> Issue Type: Task
> Components: client
>Affects Versions: 3.1.0, 3.3.0
>Reporter: Prabhu Joseph
>Assignee: SwathiChandrashekar
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> yarn node list intermittently fails with below
> {code:java}
> 2021-06-13 11:26:42,316 WARN client.RequestHedgingRMFailoverProxyProvider:
> Invocation returned exception: java.lang.ArrayIndexOutOfBoundsException: 1 on
> [resourcemanager-1], so propagating back to caller.
> Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 1
> at java.util.ArrayList.add(ArrayList.java:465)
> at
> org.apache.hadoop.yarn.proto.YarnServiceProtos$GetClusterNodesRequestProto$Builder.addAllNodeStates(YarnServiceProtos.java:28009)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.mergeLocalToBuilder(GetClusterNodesRequestPBImpl.java:124)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.mergeLocalToProto(GetClusterNodesRequestPBImpl.java:82)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.getProto(GetClusterNodesRequestPBImpl.java:56)
> at
> org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getClusterNodes(ApplicationClientProtocolPBClientImpl.java:329)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:422)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeMethod(RetryInvocationHandler.java:165)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invoke(RetryInvocationHandler.java:157)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:95)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:359)
> at com.sun.proxy.$Proxy8.getClusterNodes(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider$RMRequestHedgingInvocationHandler$1.call(RequestHedgingRMFailoverProxyProvider.java:159)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 2021-06-13 11:27:58,415 WARN client.RequestHedgingRMFailoverProxyProvider:
> Invocation returned exception: java.lang.UnsupportedOperationException on
> [resourcemanager-0], so propagating back to caller.
> Exception in thread "main" java.lang.UnsupportedOperationException
> at
> java.util.Collections$UnmodifiableCollection.add(Collections.java:1057)
> at
> org.apache.hadoop.yarn.proto.YarnServiceProtos$GetClusterNodesRequestProto$Builder.addAllNodeStates(YarnServiceProtos.java:28009)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.mergeLocalToBuilder(GetClusterNodesRequestPBImpl.java:124)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.mergeLocalToProto(GetClusterNodesRequestPBImpl.java:82)
> at
> org.apache.hadoop.yarn.api.protocolrecords.impl.pb.GetClusterNodesRequestPBImpl.getProto(GetClusterNodesRequestPBImpl.java:56)
> at
> org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getClusterNodes(ApplicationClientProtocolPBClientImpl.java:329)
> at sun.reflect.Na
[jira] [Resolved] (YARN-10805) Replace Guava Lists usage by Hadoop's own Lists in hadoop-yarn-project
[ https://issues.apache.org/jira/browse/YARN-10805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takanobu Asanuma resolved YARN-10805. - Fix Version/s: 3.4.0 Resolution: Fixed > Replace Guava Lists usage by Hadoop's own Lists in hadoop-yarn-project > -- > > Key: YARN-10805 > URL: https://issues.apache.org/jira/browse/YARN-10805 > Project: Hadoop YARN > Issue Type: Task >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > -- 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
[jira] [Updated] (YARN-9279) Remove the old hamlet package
[ https://issues.apache.org/jira/browse/YARN-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takanobu Asanuma updated YARN-9279: --- Hadoop Flags: Incompatible change,Reviewed (was: Incompatible change) > Remove the old hamlet package > - > > Key: YARN-9279 > URL: https://issues.apache.org/jira/browse/YARN-9279 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Attachments: YARN-9279.01.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > > The old hamlet package was deprecated in HADOOP-11875. Let's remove this to > improve the maintenability. -- 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
[jira] [Created] (YARN-10407) Add phantomjsdriver.log to gitignore
Takanobu Asanuma created YARN-10407:
---
Summary: Add phantomjsdriver.log to gitignore
Key: YARN-10407
URL: https://issues.apache.org/jira/browse/YARN-10407
Project: Hadoop YARN
Issue Type: Improvement
Reporter: Takanobu Asanuma
Assignee: Takanobu Asanuma
After testing hadoop-yarn-applications-catalog-webapp, it genrates
phantomjsdriver.log.
{noformat}
$ mvn test --projects org.apache.hadoop:hadoop-yarn-applications-catalog-webapp
{noformat}
--
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
[jira] [Commented] (YARN-10120) In Federation Router Nodes/Applications/About pages throws 500 exception when https is enabled
[
https://issues.apache.org/jira/browse/YARN-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074197#comment-17074197
]
Takanobu Asanuma commented on YARN-10120:
-
Hi [~BilwaST] and [~prabhujoseph],
* This commit seems to break {{mvn javadoc:javadoc}}. Could you fix it?
{noformat}
[ERROR]
/.../hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/main/java/org/apache/hadoop/yarn/server/webapp/WebServiceClient.java:50:
error: @param name not found
{noformat}
* trunk is targeting 3.4.0 now. If you want to merge it to 3.3.0, please
commit to branch-3.3.
[https://lists.apache.org/thread.html/r344f50b41798565ceb78ecf0b1fc423eab91e11361f6b2bd5173303b%40%3Ccommon-dev.hadoop.apache.org%3E]
Thanks.
> In Federation Router Nodes/Applications/About pages throws 500 exception when
> https is enabled
> --
>
> Key: YARN-10120
> URL: https://issues.apache.org/jira/browse/YARN-10120
> Project: Hadoop YARN
> Issue Type: Bug
> Components: federation
>Reporter: Sushanta Sen
>Assignee: Bilwa S T
>Priority: Critical
> Fix For: 3.3.0
>
> Attachments: YARN-10120.001.patch, YARN-10120.002.patch
>
>
> In Federation Router Nodes/Applications/About pages throws 500 exception when
> https is enabled.
> yarn.router.webapp.https.address =router ip:8091
> {noformat}
> 2020-02-07 16:38:49,990 ERROR org.apache.hadoop.yarn.webapp.Dispatcher: error
> handling URI: /cluster/apps
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.yarn.webapp.Dispatcher.service(Dispatcher.java:166)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
> at
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
> at
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
> at
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:941)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:875)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:829)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
> at
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
> at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
> at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
> at
> com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
> at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at
> org.apache.hadoop.security.http.XFrameOptionsFilter.doFilter(XFrameOptionsFilter.java:57)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:644)
> at
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:592)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at
> org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1622)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> at
>
[jira] [Updated] (YARN-10120) In Federation Router Nodes/Applications/About pages throws 500 exception when https is enabled
[
https://issues.apache.org/jira/browse/YARN-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma updated YARN-10120:
Fix Version/s: (was: 3.3.0)
3.4.0
> In Federation Router Nodes/Applications/About pages throws 500 exception when
> https is enabled
> --
>
> Key: YARN-10120
> URL: https://issues.apache.org/jira/browse/YARN-10120
> Project: Hadoop YARN
> Issue Type: Bug
> Components: federation
>Reporter: Sushanta Sen
>Assignee: Bilwa S T
>Priority: Critical
> Fix For: 3.4.0
>
> Attachments: YARN-10120.001.patch, YARN-10120.002.patch
>
>
> In Federation Router Nodes/Applications/About pages throws 500 exception when
> https is enabled.
> yarn.router.webapp.https.address =router ip:8091
> {noformat}
> 2020-02-07 16:38:49,990 ERROR org.apache.hadoop.yarn.webapp.Dispatcher: error
> handling URI: /cluster/apps
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.yarn.webapp.Dispatcher.service(Dispatcher.java:166)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
> at
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
> at
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
> at
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:941)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:875)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:829)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
> at
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
> at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
> at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
> at
> com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
> at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at
> org.apache.hadoop.security.http.XFrameOptionsFilter.doFilter(XFrameOptionsFilter.java:57)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:644)
> at
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:592)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at
> org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1622)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
> at
> org.ecl
[jira] [Commented] (YARN-9081) Update jackson from 1.9.13 to 2.x in hadoop-yarn-services-core
[ https://issues.apache.org/jira/browse/YARN-9081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824690#comment-16824690 ] Takanobu Asanuma commented on YARN-9081: +1. Will commit it. > Update jackson from 1.9.13 to 2.x in hadoop-yarn-services-core > -- > > Key: YARN-9081 > URL: https://issues.apache.org/jira/browse/YARN-9081 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Labels: newbie > Attachments: YARN-9081.01.patch > > -- 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
[jira] [Commented] (YARN-9081) Update jackson from 1.9.13 to 2.x in hadoop-yarn-services-core
[ https://issues.apache.org/jira/browse/YARN-9081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824052#comment-16824052 ] Takanobu Asanuma commented on YARN-9081: [~ajisakaa] Sorry for late review. The patch looks good. I'd like to see another result of Jenkins since it's been a long time. > Update jackson from 1.9.13 to 2.x in hadoop-yarn-services-core > -- > > Key: YARN-9081 > URL: https://issues.apache.org/jira/browse/YARN-9081 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Labels: newbie > Attachments: YARN-9081.01.patch > > -- 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
[jira] [Commented] (YARN-8943) Upgrade JUnit from 4 to 5 in hadoop-yarn-api
[ https://issues.apache.org/jira/browse/YARN-8943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818508#comment-16818508 ] Takanobu Asanuma commented on YARN-8943: Thanks for your explanation, [~ajisakaa]. bq. TestYarnConfigurationFields extends TestConfigurationFieldsBase and it uses JUnit 4 API. Indeed, we still need to keep it. bq. Yes, we may use AssertJ. Let's use it in a separate jira. Got it. Now I'm +1 for the latest patch. Will commit it later. > Upgrade JUnit from 4 to 5 in hadoop-yarn-api > > > Key: YARN-8943 > URL: https://issues.apache.org/jira/browse/YARN-8943 > Project: Hadoop YARN > Issue Type: Sub-task > Components: test >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Attachments: YARN-8943.01.patch, YARN-8943.02.patch > > -- 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
[jira] [Commented] (YARN-8943) Upgrade JUnit from 4 to 5 in hadoop-yarn-api
[
https://issues.apache.org/jira/browse/YARN-8943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817812#comment-16817812
]
Takanobu Asanuma commented on YARN-8943:
I'd like to review the latest patch.
* Should we remove {{org.junit.vintage}} dependency in pom.xml since we don't
consider JUnit4 here?
* As we discussed in the thread, we may use AssertJ.
> Upgrade JUnit from 4 to 5 in hadoop-yarn-api
>
>
> Key: YARN-8943
> URL: https://issues.apache.org/jira/browse/YARN-8943
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: test
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
> Attachments: YARN-8943.01.patch, YARN-8943.02.patch
>
>
--
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
[jira] [Commented] (YARN-8943) Upgrade JUnit from 4 to 5 in hadoop-yarn-api
[ https://issues.apache.org/jira/browse/YARN-8943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817807#comment-16817807 ] Takanobu Asanuma commented on YARN-8943: Thanks for working on this Jira and the discussion in dev MLs, [~ajisakaa] and [~snemeth]. This is a summary form Akira in the thread. * Let's upgrade the existing tests to JUnit 5. * It's good to make the new tests using JUnit 5. * We may use AssertJ and update the version. I created HADOOP-16253 about updating AsserJ. > Upgrade JUnit from 4 to 5 in hadoop-yarn-api > > > Key: YARN-8943 > URL: https://issues.apache.org/jira/browse/YARN-8943 > Project: Hadoop YARN > Issue Type: Sub-task > Components: test >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Attachments: YARN-8943.01.patch, YARN-8943.02.patch > > -- 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
[jira] [Commented] (YARN-8866) Fix a parsing error for crossdomain.xml
[
https://issues.apache.org/jira/browse/YARN-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677909#comment-16677909
]
Takanobu Asanuma commented on YARN-8866:
Committed to branch-3.0, branch-3.1, branch-3.2, trunk.
> Fix a parsing error for crossdomain.xml
> ---
>
> Key: YARN-8866
> URL: https://issues.apache.org/jira/browse/YARN-8866
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, yarn-ui-v2
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8866.1.patch
>
>
> [QBT|https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/] reports
> a parsing error for crossdomain.xml in hadoop-yarn-ui.
> {noformat}
> Parsing Error(s):
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/public/crossdomain.xml
>
> {noformat}
--
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
[jira] [Commented] (YARN-8866) Fix a parsing error for crossdomain.xml
[
https://issues.apache.org/jira/browse/YARN-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677901#comment-16677901
]
Takanobu Asanuma commented on YARN-8866:
Thanks for the review, [~leftnoteasy]! I'd like to commit it now.
> Fix a parsing error for crossdomain.xml
> ---
>
> Key: YARN-8866
> URL: https://issues.apache.org/jira/browse/YARN-8866
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, yarn-ui-v2
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8866.1.patch
>
>
> [QBT|https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/] reports
> a parsing error for crossdomain.xml in hadoop-yarn-ui.
> {noformat}
> Parsing Error(s):
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/public/crossdomain.xml
>
> {noformat}
--
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
[jira] [Commented] (YARN-8866) Fix a parsing error for crossdomain.xml
[
https://issues.apache.org/jira/browse/YARN-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664706#comment-16664706
]
Takanobu Asanuma commented on YARN-8866:
Sorry for pinging you again, [~leftnoteasy]. The file is created by YARN-4849.
> Fix a parsing error for crossdomain.xml
> ---
>
> Key: YARN-8866
> URL: https://issues.apache.org/jira/browse/YARN-8866
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, yarn-ui-v2
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8866.1.patch
>
>
> [QBT|https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/] reports
> a parsing error for crossdomain.xml in hadoop-yarn-ui.
> {noformat}
> Parsing Error(s):
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/public/crossdomain.xml
>
> {noformat}
--
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
[jira] [Commented] (YARN-8939) Javadoc build fails in hadoop-yarn-csi
[
https://issues.apache.org/jira/browse/YARN-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662113#comment-16662113
]
Takanobu Asanuma commented on YARN-8939:
Thanks [~cheersyang] for the patch, and thanks [~ajisakaa] for the review!
> Javadoc build fails in hadoop-yarn-csi
> --
>
> Key: YARN-8939
> URL: https://issues.apache.org/jira/browse/YARN-8939
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Assignee: Weiwei Yang
>Priority: Major
> Fix For: 3.3.0
>
> Attachments: YARN-8939.1.patch, YARN-8939.2.patch
>
>
> {noformat}
> $ mvn javadoc:javadoc --projects
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi
> ...
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi/src/main/java/org/apache/hadoop/yarn/csi/client/CsiGrpcClient.java:92:
> error: exception not thrown: java.lang.InterruptedException
> [ERROR]* @throws InterruptedException
> {noformat}
--
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
[jira] [Commented] (YARN-8941) Findbugs warnings in hadoop-yarn-csi
[ https://issues.apache.org/jira/browse/YARN-8941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662039#comment-16662039 ] Takanobu Asanuma commented on YARN-8941: Hi [~sunilg], please see: [https://builds.apache.org/job/PreCommit-YARN-Build/22323/artifact/out/branch-findbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-csi-warnings.html] They are for the target directory. We should exclude it. > Findbugs warnings in hadoop-yarn-csi > > > Key: YARN-8941 > URL: https://issues.apache.org/jira/browse/YARN-8941 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Takanobu Asanuma >Priority: Major > -- 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
[jira] [Commented] (YARN-8939) Javadoc build fails in hadoop-yarn-csi
[
https://issues.apache.org/jira/browse/YARN-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662032#comment-16662032
]
Takanobu Asanuma commented on YARN-8939:
The findbugs issue is not related to the patch. I filed it in YARN-8941.
> Javadoc build fails in hadoop-yarn-csi
> --
>
> Key: YARN-8939
> URL: https://issues.apache.org/jira/browse/YARN-8939
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Assignee: Weiwei Yang
>Priority: Major
> Attachments: YARN-8939.1.patch, YARN-8939.2.patch
>
>
> {noformat}
> $ mvn javadoc:javadoc --projects
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi
> ...
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi/src/main/java/org/apache/hadoop/yarn/csi/client/CsiGrpcClient.java:92:
> error: exception not thrown: java.lang.InterruptedException
> [ERROR]* @throws InterruptedException
> {noformat}
--
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
[jira] [Created] (YARN-8941) Findbugs warnings in hadoop-yarn-csi
Takanobu Asanuma created YARN-8941: -- Summary: Findbugs warnings in hadoop-yarn-csi Key: YARN-8941 URL: https://issues.apache.org/jira/browse/YARN-8941 Project: Hadoop YARN Issue Type: Bug Reporter: Takanobu Asanuma -- 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
[jira] [Commented] (YARN-8939) Javadoc build fails in hadoop-yarn-csi
[
https://issues.apache.org/jira/browse/YARN-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661834#comment-16661834
]
Takanobu Asanuma commented on YARN-8939:
Thanks [~ajisakaa] and [~cheersyang]! I'd like to assign this jira to
[~cheersyang].
> Javadoc build fails in hadoop-yarn-csi
> --
>
> Key: YARN-8939
> URL: https://issues.apache.org/jira/browse/YARN-8939
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8939.1.patch, YARN-8939.2.patch
>
>
> {noformat}
> $ mvn javadoc:javadoc --projects
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi
> ...
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi/src/main/java/org/apache/hadoop/yarn/csi/client/CsiGrpcClient.java:92:
> error: exception not thrown: java.lang.InterruptedException
> [ERROR]* @throws InterruptedException
> {noformat}
--
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
[jira] [Assigned] (YARN-8939) Javadoc build fails in hadoop-yarn-csi
[
https://issues.apache.org/jira/browse/YARN-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma reassigned YARN-8939:
--
Assignee: Weiwei Yang (was: Takanobu Asanuma)
> Javadoc build fails in hadoop-yarn-csi
> --
>
> Key: YARN-8939
> URL: https://issues.apache.org/jira/browse/YARN-8939
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Assignee: Weiwei Yang
>Priority: Major
> Attachments: YARN-8939.1.patch, YARN-8939.2.patch
>
>
> {noformat}
> $ mvn javadoc:javadoc --projects
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi
> ...
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi/src/main/java/org/apache/hadoop/yarn/csi/client/CsiGrpcClient.java:92:
> error: exception not thrown: java.lang.InterruptedException
> [ERROR]* @throws InterruptedException
> {noformat}
--
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
[jira] [Updated] (YARN-8939) Javadoc build fails in hadoop-yarn-csi
[
https://issues.apache.org/jira/browse/YARN-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma updated YARN-8939:
---
Attachment: YARN-8939.1.patch
> Javadoc build fails in hadoop-yarn-csi
> --
>
> Key: YARN-8939
> URL: https://issues.apache.org/jira/browse/YARN-8939
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8939.1.patch
>
>
> {noformat}
> $ mvn javadoc:javadoc --projects
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi
> ...
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi/src/main/java/org/apache/hadoop/yarn/csi/client/CsiGrpcClient.java:92:
> error: exception not thrown: java.lang.InterruptedException
> [ERROR]* @throws InterruptedException
> {noformat}
--
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
[jira] [Created] (YARN-8939) Javadoc build fails in hadoop-yarn-csi
Takanobu Asanuma created YARN-8939:
--
Summary: Javadoc build fails in hadoop-yarn-csi
Key: YARN-8939
URL: https://issues.apache.org/jira/browse/YARN-8939
Project: Hadoop YARN
Issue Type: Bug
Reporter: Takanobu Asanuma
Assignee: Takanobu Asanuma
{noformat}
$ mvn javadoc:javadoc --projects hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi
...
[ERROR]
/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-csi/src/main/java/org/apache/hadoop/yarn/csi/client/CsiGrpcClient.java:92:
error: exception not thrown: java.lang.InterruptedException
[ERROR]* @throws InterruptedException
{noformat}
--
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
[jira] [Commented] (YARN-8919) Some tests fail due to NoClassDefFoundError for OperatorCreationException
[
https://issues.apache.org/jira/browse/YARN-8919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661531#comment-16661531
]
Takanobu Asanuma commented on YARN-8919:
Thanks for the reviews and the commit, [~rkanter] and [~eyang]!
> Some tests fail due to NoClassDefFoundError for OperatorCreationException
> -
>
> Key: YARN-8919
> URL: https://issues.apache.org/jira/browse/YARN-8919
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Critical
> Fix For: 3.3.0
>
> Attachments: YARN-8919.2.patch, YARN-8919.WIP.1.patch
>
>
> These tests still fail due to {{NoClassDefFoundError:
> org/bouncycastle/operator/OperatorCreationException}}.
> {noformat}
> hadoop.streaming.TestFileArgs
> hadoop.streaming.TestMultipleCachefiles
> hadoop.streaming.TestStreamingBadRecords
> hadoop.streaming.TestSymLink
> hadoop.streaming.TestMultipleArchiveFiles
> hadoop.mapred.gridmix.TestGridmixSubmission
> hadoop.mapred.gridmix.TestDistCacheEmulation
> hadoop.mapred.gridmix.TestLoadJob
> hadoop.mapred.gridmix.TestSleepJob
> hadoop.tools.TestDistCh
> {noformat}
> See:
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/931/#showFailuresLink
--
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
[jira] [Commented] (YARN-8919) Some tests fail due to NoClassDefFoundError for OperatorCreationException
[
https://issues.apache.org/jira/browse/YARN-8919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659872#comment-16659872
]
Takanobu Asanuma commented on YARN-8919:
Thanks [~rkanter] and [~eyang] for the discussion and the investigation.
Uploaded the 2nd patch.
> Some tests fail due to NoClassDefFoundError for OperatorCreationException
> -
>
> Key: YARN-8919
> URL: https://issues.apache.org/jira/browse/YARN-8919
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Priority: Critical
> Attachments: YARN-8919.2.patch, YARN-8919.WIP.1.patch
>
>
> These tests still fail due to {{NoClassDefFoundError:
> org/bouncycastle/operator/OperatorCreationException}}.
> {noformat}
> hadoop.streaming.TestFileArgs
> hadoop.streaming.TestMultipleCachefiles
> hadoop.streaming.TestStreamingBadRecords
> hadoop.streaming.TestSymLink
> hadoop.streaming.TestMultipleArchiveFiles
> hadoop.mapred.gridmix.TestGridmixSubmission
> hadoop.mapred.gridmix.TestDistCacheEmulation
> hadoop.mapred.gridmix.TestLoadJob
> hadoop.mapred.gridmix.TestSleepJob
> hadoop.tools.TestDistCh
> {noformat}
> See:
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/931/#showFailuresLink
--
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
[jira] [Updated] (YARN-8919) Some tests fail due to NoClassDefFoundError for OperatorCreationException
[
https://issues.apache.org/jira/browse/YARN-8919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma updated YARN-8919:
---
Attachment: YARN-8919.2.patch
> Some tests fail due to NoClassDefFoundError for OperatorCreationException
> -
>
> Key: YARN-8919
> URL: https://issues.apache.org/jira/browse/YARN-8919
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Priority: Critical
> Attachments: YARN-8919.2.patch, YARN-8919.WIP.1.patch
>
>
> These tests still fail due to {{NoClassDefFoundError:
> org/bouncycastle/operator/OperatorCreationException}}.
> {noformat}
> hadoop.streaming.TestFileArgs
> hadoop.streaming.TestMultipleCachefiles
> hadoop.streaming.TestStreamingBadRecords
> hadoop.streaming.TestSymLink
> hadoop.streaming.TestMultipleArchiveFiles
> hadoop.mapred.gridmix.TestGridmixSubmission
> hadoop.mapred.gridmix.TestDistCacheEmulation
> hadoop.mapred.gridmix.TestLoadJob
> hadoop.mapred.gridmix.TestSleepJob
> hadoop.tools.TestDistCh
> {noformat}
> See:
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/931/#showFailuresLink
--
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
[jira] [Commented] (YARN-8919) Some tests fail due to NoClassDefFoundError for OperatorCreationException
[
https://issues.apache.org/jira/browse/YARN-8919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658458#comment-16658458
]
Takanobu Asanuma commented on YARN-8919:
Hi [~rkanter] and [~eyang], could you please check it?
> Some tests fail due to NoClassDefFoundError for OperatorCreationException
> -
>
> Key: YARN-8919
> URL: https://issues.apache.org/jira/browse/YARN-8919
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Priority: Critical
> Attachments: YARN-8919.WIP.1.patch
>
>
> These tests still fail due to {{NoClassDefFoundError:
> org/bouncycastle/operator/OperatorCreationException}}.
> {noformat}
> hadoop.streaming.TestFileArgs
> hadoop.streaming.TestMultipleCachefiles
> hadoop.streaming.TestStreamingBadRecords
> hadoop.streaming.TestSymLink
> hadoop.streaming.TestMultipleArchiveFiles
> hadoop.mapred.gridmix.TestGridmixSubmission
> hadoop.mapred.gridmix.TestDistCacheEmulation
> hadoop.mapred.gridmix.TestLoadJob
> hadoop.mapred.gridmix.TestSleepJob
> hadoop.tools.TestDistCh
> {noformat}
> See:
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/931/#showFailuresLink
--
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
[jira] [Updated] (YARN-8919) Some tests fail due to NoClassDefFoundError for OperatorCreationException
[
https://issues.apache.org/jira/browse/YARN-8919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma updated YARN-8919:
---
Description:
These tests still fail due to {{NoClassDefFoundError:
org/bouncycastle/operator/OperatorCreationException}}.
{noformat}
hadoop.streaming.TestFileArgs
hadoop.streaming.TestMultipleCachefiles
hadoop.streaming.TestStreamingBadRecords
hadoop.streaming.TestSymLink
hadoop.streaming.TestMultipleArchiveFiles
hadoop.mapred.gridmix.TestGridmixSubmission
hadoop.mapred.gridmix.TestDistCacheEmulation
hadoop.mapred.gridmix.TestLoadJob
hadoop.mapred.gridmix.TestSleepJob
hadoop.tools.TestDistCh
{noformat}
See:
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/931/#showFailuresLink
was:
These tests still fail due to {{NoClassDefFoundError:
org/bouncycastle/operator/OperatorCreationException}}.
{noformat}
hadoop.streaming.TestFileArgs
hadoop.streaming.TestMultipleCachefiles
hadoop.streaming.TestStreamingBadRecords
hadoop.streaming.TestSymLink
hadoop.streaming.TestMultipleArchiveFiles
hadoop.mapred.gridmix.TestGridmixSubmission
hadoop.mapred.gridmix.TestDistCacheEmulation
hadoop.mapred.gridmix.TestLoadJob
hadoop.mapred.gridmix.TestSleepJob
hadoop.tools.TestDistCh
{noformat}
> Some tests fail due to NoClassDefFoundError for OperatorCreationException
> -
>
> Key: YARN-8919
> URL: https://issues.apache.org/jira/browse/YARN-8919
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Priority: Critical
> Attachments: YARN-8919.WIP.1.patch
>
>
> These tests still fail due to {{NoClassDefFoundError:
> org/bouncycastle/operator/OperatorCreationException}}.
> {noformat}
> hadoop.streaming.TestFileArgs
> hadoop.streaming.TestMultipleCachefiles
> hadoop.streaming.TestStreamingBadRecords
> hadoop.streaming.TestSymLink
> hadoop.streaming.TestMultipleArchiveFiles
> hadoop.mapred.gridmix.TestGridmixSubmission
> hadoop.mapred.gridmix.TestDistCacheEmulation
> hadoop.mapred.gridmix.TestLoadJob
> hadoop.mapred.gridmix.TestSleepJob
> hadoop.tools.TestDistCh
> {noformat}
> See:
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/931/#showFailuresLink
--
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
[jira] [Commented] (YARN-8919) Some tests fail due to NoClassDefFoundError for OperatorCreationException
[
https://issues.apache.org/jira/browse/YARN-8919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657127#comment-16657127
]
Takanobu Asanuma commented on YARN-8919:
Uploaded the wip patch. It seems fix the tests in local though I'm not sure if
it is the right solution.
> Some tests fail due to NoClassDefFoundError for OperatorCreationException
> -
>
> Key: YARN-8919
> URL: https://issues.apache.org/jira/browse/YARN-8919
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Priority: Critical
> Attachments: YARN-8919.WIP.1.patch
>
>
> These tests still fail due to {{NoClassDefFoundError:
> org/bouncycastle/operator/OperatorCreationException}}.
> {noformat}
> hadoop.streaming.TestFileArgs
> hadoop.streaming.TestMultipleCachefiles
> hadoop.streaming.TestStreamingBadRecords
> hadoop.streaming.TestSymLink
> hadoop.streaming.TestMultipleArchiveFiles
> hadoop.mapred.gridmix.TestGridmixSubmission
> hadoop.mapred.gridmix.TestDistCacheEmulation
> hadoop.mapred.gridmix.TestLoadJob
> hadoop.mapred.gridmix.TestSleepJob
> hadoop.tools.TestDistCh
> {noformat}
--
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
[jira] [Updated] (YARN-8919) Some tests fail due to NoClassDefFoundError for OperatorCreationException
[
https://issues.apache.org/jira/browse/YARN-8919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma updated YARN-8919:
---
Attachment: YARN-8919.WIP.1.patch
> Some tests fail due to NoClassDefFoundError for OperatorCreationException
> -
>
> Key: YARN-8919
> URL: https://issues.apache.org/jira/browse/YARN-8919
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Priority: Critical
> Attachments: YARN-8919.WIP.1.patch
>
>
> These tests still fail due to {{NoClassDefFoundError:
> org/bouncycastle/operator/OperatorCreationException}}.
> {noformat}
> hadoop.streaming.TestFileArgs
> hadoop.streaming.TestMultipleCachefiles
> hadoop.streaming.TestStreamingBadRecords
> hadoop.streaming.TestSymLink
> hadoop.streaming.TestMultipleArchiveFiles
> hadoop.mapred.gridmix.TestGridmixSubmission
> hadoop.mapred.gridmix.TestDistCacheEmulation
> hadoop.mapred.gridmix.TestLoadJob
> hadoop.mapred.gridmix.TestSleepJob
> hadoop.tools.TestDistCh
> {noformat}
--
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
[jira] [Commented] (YARN-8919) Some tests fail due to NoClassDefFoundError for OperatorCreationException
[
https://issues.apache.org/jira/browse/YARN-8919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657104#comment-16657104
]
Takanobu Asanuma commented on YARN-8919:
They don't depend on hadoop-minicluster so YARN-8899 didn't fix the regressions.
> Some tests fail due to NoClassDefFoundError for OperatorCreationException
> -
>
> Key: YARN-8919
> URL: https://issues.apache.org/jira/browse/YARN-8919
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Takanobu Asanuma
>Priority: Critical
>
> These tests still fail due to {{NoClassDefFoundError:
> org/bouncycastle/operator/OperatorCreationException}}.
> {noformat}
> hadoop.streaming.TestFileArgs
> hadoop.streaming.TestMultipleCachefiles
> hadoop.streaming.TestStreamingBadRecords
> hadoop.streaming.TestSymLink
> hadoop.streaming.TestMultipleArchiveFiles
> hadoop.mapred.gridmix.TestGridmixSubmission
> hadoop.mapred.gridmix.TestDistCacheEmulation
> hadoop.mapred.gridmix.TestLoadJob
> hadoop.mapred.gridmix.TestSleepJob
> hadoop.tools.TestDistCh
> {noformat}
--
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
[jira] [Created] (YARN-8919) Some tests fail due to NoClassDefFoundError for OperatorCreationException
Takanobu Asanuma created YARN-8919:
--
Summary: Some tests fail due to NoClassDefFoundError for
OperatorCreationException
Key: YARN-8919
URL: https://issues.apache.org/jira/browse/YARN-8919
Project: Hadoop YARN
Issue Type: Bug
Reporter: Takanobu Asanuma
These tests still fail due to {{NoClassDefFoundError:
org/bouncycastle/operator/OperatorCreationException}}.
{noformat}
hadoop.streaming.TestFileArgs
hadoop.streaming.TestMultipleCachefiles
hadoop.streaming.TestStreamingBadRecords
hadoop.streaming.TestSymLink
hadoop.streaming.TestMultipleArchiveFiles
hadoop.mapred.gridmix.TestGridmixSubmission
hadoop.mapred.gridmix.TestDistCacheEmulation
hadoop.mapred.gridmix.TestLoadJob
hadoop.mapred.gridmix.TestSleepJob
hadoop.tools.TestDistCh
{noformat}
--
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
[jira] [Commented] (YARN-8866) Fix a parsing error for crossdomain.xml
[
https://issues.apache.org/jira/browse/YARN-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654519#comment-16654519
]
Takanobu Asanuma commented on YARN-8866:
Hi [~leftnoteasy]. Could you review this issue?
> Fix a parsing error for crossdomain.xml
> ---
>
> Key: YARN-8866
> URL: https://issues.apache.org/jira/browse/YARN-8866
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, yarn-ui-v2
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8866.1.patch
>
>
> [QBT|https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/] reports
> a parsing error for crossdomain.xml in hadoop-yarn-ui.
> {noformat}
> Parsing Error(s):
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/public/crossdomain.xml
>
> {noformat}
--
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
[jira] [Updated] (YARN-8866) Fix a parsing error for crossdomain.xml
[
https://issues.apache.org/jira/browse/YARN-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma updated YARN-8866:
---
Attachment: YARN-8866.1.patch
> Fix a parsing error for crossdomain.xml
> ---
>
> Key: YARN-8866
> URL: https://issues.apache.org/jira/browse/YARN-8866
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, yarn-ui-v2
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8866.1.patch
>
>
> [QBT|https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/] reports
> a parsing error for crossdomain.xml in hadoop-yarn-ui.
> {noformat}
> Parsing Error(s):
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/public/crossdomain.xml
>
> {noformat}
--
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
[jira] [Created] (YARN-8866) Fix a parsing error for crossdomain.xml
Takanobu Asanuma created YARN-8866:
--
Summary: Fix a parsing error for crossdomain.xml
Key: YARN-8866
URL: https://issues.apache.org/jira/browse/YARN-8866
Project: Hadoop YARN
Issue Type: Bug
Components: build, yarn-ui-v2
Reporter: Takanobu Asanuma
Assignee: Takanobu Asanuma
[QBT|https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/] reports a
parsing error for crossdomain.xml in hadoop-yarn-ui.
{noformat}
Parsing Error(s):
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/public/crossdomain.xml
{noformat}
--
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
[jira] [Commented] (YARN-8492) ATSv2 HBase tests are failing with ClassNotFoundException
[
https://issues.apache.org/jira/browse/YARN-8492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534497#comment-16534497
]
Takanobu Asanuma commented on YARN-8492:
[~rohithsharma] Sorry for generating the bug by YARN-8363, and thanks for
analyzing and fixing it.
> ATSv2 HBase tests are failing with ClassNotFoundException
> -
>
> Key: YARN-8492
> URL: https://issues.apache.org/jira/browse/YARN-8492
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Rohith Sharma K S
>Assignee: Rohith Sharma K S
>Priority: Major
> Attachments: YARN-8492.01.patch, YARN-8492.02.patch
>
>
> It is seen in recent QA report that ATSv2 Hbase tests are failing with
> ClassNotFoundException.
> This looks to be regression from hadoop common patch or any other patch. We
> need to figure out which JIRA broke this and fix tests failure.
> hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRun
>
> hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageSchema
>
> hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageEntities
> hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageApps
> hadoop.yarn.server.timelineservice.storage.TestTimelineReaderHBaseDown
>
> hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRunCompaction
>
> hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageDomain
>
> hadoop.yarn.server.timelineservice.reader.TestTimelineReaderWebServicesHBaseStorage
>
> hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowActivity
>
> {noformat}
> ERROR]
> org.apache.hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageApps
> Time elapsed: 0.102 s <<< ERROR!
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/crypto/key/KeyProviderTokenIssuer
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageApps.setupBeforeClass(TestHBaseTimelineStorageApps.java:97)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.crypto.key.KeyProviderTokenIssuer
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> {noformat}
--
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
[jira] [Commented] (YARN-8363) Upgrade commons-lang version to 3.7 in hadoop-yarn-project
[ https://issues.apache.org/jira/browse/YARN-8363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509781#comment-16509781 ] Takanobu Asanuma commented on YARN-8363: Thank you very much for your review and commit, [~ajisakaa]! > Upgrade commons-lang version to 3.7 in hadoop-yarn-project > -- > > Key: YARN-8363 > URL: https://issues.apache.org/jira/browse/YARN-8363 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Takanobu Asanuma >Assignee: Takanobu Asanuma >Priority: Major > Fix For: 3.2.0 > > Attachments: YARN-8363.1.patch, YARN-8363.2.patch > > > commons-lang 2.6 is widely used. Let's upgrade to 3.6. > This jira is separated from HADOOP-10783. -- 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
[jira] [Commented] (YARN-8363) Upgrade common-langs version to 3.7 in hadoop-yarn-project
[ https://issues.apache.org/jira/browse/YARN-8363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509325#comment-16509325 ] Takanobu Asanuma commented on YARN-8363: The findbugs warning is already filed by YARN-8391 and isn't related to the patch. The failed error also seems not related. Kindly help to review it. Thanks. > Upgrade common-langs version to 3.7 in hadoop-yarn-project > -- > > Key: YARN-8363 > URL: https://issues.apache.org/jira/browse/YARN-8363 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Takanobu Asanuma >Assignee: Takanobu Asanuma >Priority: Major > Attachments: YARN-8363.1.patch, YARN-8363.2.patch > > > commons-lang 2.6 is widely used. Let's upgrade to 3.6. > This jira is separated from HADOOP-10783. -- 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
[jira] [Resolved] (YARN-8420) Multithreaded correctness Warning occurs in AllocationFileLoaderService
[
https://issues.apache.org/jira/browse/YARN-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma resolved YARN-8420.
Resolution: Duplicate
> Multithreaded correctness Warning occurs in AllocationFileLoaderService
> ---
>
> Key: YARN-8420
> URL: https://issues.apache.org/jira/browse/YARN-8420
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
>Reporter: Takanobu Asanuma
>Priority: Critical
>
> This is reported by findbugs. See:
> [https://builds.apache.org/job/PreCommit-YARN-Build/21007/artifact/out/branch-findbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-warnings.html]
> {noformat}
> Inconsistent synchronization of
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AllocationFileLoaderService.reloadListener;
> locked 75% of time
> {noformat}
--
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
[jira] [Commented] (YARN-8420) Multithreaded correctness Warning occurs in AllocationFileLoaderService
[
https://issues.apache.org/jira/browse/YARN-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509319#comment-16509319
]
Takanobu Asanuma commented on YARN-8420:
[~snemeth] Sorry I didn't find that jira. Thanks for letting me know!
> Multithreaded correctness Warning occurs in AllocationFileLoaderService
> ---
>
> Key: YARN-8420
> URL: https://issues.apache.org/jira/browse/YARN-8420
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
>Reporter: Takanobu Asanuma
>Priority: Critical
>
> This is reported by findbugs. See:
> [https://builds.apache.org/job/PreCommit-YARN-Build/21007/artifact/out/branch-findbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-warnings.html]
> {noformat}
> Inconsistent synchronization of
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AllocationFileLoaderService.reloadListener;
> locked 75% of time
> {noformat}
--
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
[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart
[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509316#comment-16509316 ] Takanobu Asanuma commented on YARN-8191: Thanks for working on this, but it may create a findbugs warning. Please see YARN-8420. > Fair scheduler: queue deletion without RM restart > - > > Key: YARN-8191 > URL: https://issues.apache.org/jira/browse/YARN-8191 > Project: Hadoop YARN > Issue Type: Improvement > Components: fairscheduler >Affects Versions: 3.0.1 >Reporter: Gergo Repas >Assignee: Gergo Repas >Priority: Major > Fix For: 3.2.0 > > Attachments: Queue Deletion in Fair Scheduler.pdf, > YARN-8191.000.patch, YARN-8191.001.patch, YARN-8191.002.patch, > YARN-8191.003.patch, YARN-8191.004.patch, YARN-8191.005.patch, > YARN-8191.006.patch, YARN-8191.007.patch, YARN-8191.008.patch, > YARN-8191.009.patch, YARN-8191.010.patch, YARN-8191.011.patch, > YARN-8191.012.patch, YARN-8191.013.patch, YARN-8191.014.patch, > YARN-8191.015.patch, YARN-8191.016.patch, YARN-8191.017.patch > > > The Fair Scheduler never cleans up queues even if they are deleted in the > allocation file, or were dynamically created and are never going to be used > again. Queues always remain in memory which leads to two following issues. > # Steady fairshares aren’t calculated correctly due to remaining queues > # WebUI shows deleted queues, which is confusing for users (YARN-4022). > We want to support proper queue deletion without restarting the Resource > Manager: > # Static queues without any entries that are removed from fair-scheduler.xml > should be deleted from memory. > # Dynamic queues without any entries should be deleted. > # RM Web UI should only show the queues defined in the scheduler at that > point in time. -- 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
[jira] [Created] (YARN-8420) Multithreaded correctness Warning occurs in AllocationFileLoaderService
Takanobu Asanuma created YARN-8420:
--
Summary: Multithreaded correctness Warning occurs in
AllocationFileLoaderService
Key: YARN-8420
URL: https://issues.apache.org/jira/browse/YARN-8420
Project: Hadoop YARN
Issue Type: Bug
Components: fairscheduler
Reporter: Takanobu Asanuma
This is reported by findbugs. See:
[https://builds.apache.org/job/PreCommit-YARN-Build/21007/artifact/out/branch-findbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-warnings.html]
{noformat}
Inconsistent synchronization of
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AllocationFileLoaderService.reloadListener;
locked 75% of time
{noformat}
--
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
[jira] [Commented] (YARN-8363) Upgrade common-langs version to 3.7 in hadoop-yarn-project
[ https://issues.apache.org/jira/browse/YARN-8363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509059#comment-16509059 ] Takanobu Asanuma commented on YARN-8363: Uploaded the 2nd patch addressing the whitespace issue. Javac warnings are that StringEscapeUtils becomes deprecated in commons-lang3. I will work on it as a follow-on task. I filed it as HADOOP-15531. The findbug warning seems not to be related. > Upgrade common-langs version to 3.7 in hadoop-yarn-project > -- > > Key: YARN-8363 > URL: https://issues.apache.org/jira/browse/YARN-8363 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Takanobu Asanuma >Assignee: Takanobu Asanuma >Priority: Major > Attachments: YARN-8363.1.patch, YARN-8363.2.patch > > > commons-lang 2.6 is widely used. Let's upgrade to 3.6. > This jira is separated from HADOOP-10783. -- 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
[jira] [Updated] (YARN-8363) Upgrade common-langs version to 3.7 in hadoop-yarn-project
[ https://issues.apache.org/jira/browse/YARN-8363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takanobu Asanuma updated YARN-8363: --- Attachment: YARN-8363.2.patch > Upgrade common-langs version to 3.7 in hadoop-yarn-project > -- > > Key: YARN-8363 > URL: https://issues.apache.org/jira/browse/YARN-8363 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Takanobu Asanuma >Assignee: Takanobu Asanuma >Priority: Major > Attachments: YARN-8363.1.patch, YARN-8363.2.patch > > > commons-lang 2.6 is widely used. Let's upgrade to 3.6. > This jira is separated from HADOOP-10783. -- 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
[jira] [Commented] (YARN-8416) YARN in HA not failing over to a new resource manager.
[
https://issues.apache.org/jira/browse/YARN-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509015#comment-16509015
]
Takanobu Asanuma commented on YARN-8416:
Moved this jira to YARN project.
> YARN in HA not failing over to a new resource manager.
> --
>
> Key: YARN-8416
> URL: https://issues.apache.org/jira/browse/YARN-8416
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Danil Serdyuchenko
>Priority: Major
>
> We are running YARN in HA mode. (rm1 and rm2) We hit an issue when recreating
> one of the RMs.
> # Recreated a standby RM (rm2), which gave it a new IP
> # Stopped the active RM (rm1)
> # NMs tried to failover to rm2, but were timing out because of the old ip.
> # NMs reach the configured 30 failover retries and shutdown.
> We get the following logs.
> {noformat}
> 18/06/06 15:36:32 WARN ipc.Client: Address change detected. Old:
> yarnrm2/x.x.x.x:8031 New: yarnrm2/y.y.y.y:8031
> 18/06/06 15:36:32 INFO retry.RetryInvocationHandler: Exception while invoking
> nodeHeartbeat of class ResourceTrackerPBClientImpl over rm2 after 25 fail
> over attempts. Trying to fail over after sleeping for 37191ms.
> org.apache.hadoop.net.ConnectTimeoutException: Call From ip-a-a-a-a/a.a.a.a
> to yarnrm2:8031 failed on socket timeout exception:
> org.apache.hadoop.net.ConnectTimeoutException: 2 millis timeout while
> waiting for channel to be ready for connect. ch :
> java.nio.channels.SocketChannel[connection-pending
> remote=yarnrm2/x.x.x.x:8031]; For more details see:
> http://wiki.apache.org/hadoop/SocketTimeout
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at org.apache.hadoop.net.NetUtils.wrapWithMessage(NetUtils.java:792)
> at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:751)
> at org.apache.hadoop.ipc.Client.call(Client.java:1480)
> at org.apache.hadoop.ipc.Client.call(Client.java:1407)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
> at com.sun.proxy.$Proxy28.nodeHeartbeat(Unknown Source)
> at
> org.apache.hadoop.yarn.server.api.impl.pb.client.ResourceTrackerPBClientImpl.nodeHeartbeat(ResourceTrackerPBClientImpl.java:80)
> at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:187)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
> at com.sun.proxy.$Proxy29.nodeHeartbeat(Unknown Source)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl$1.run(NodeStatusUpdaterImpl.java:596)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.hadoop.net.ConnectTimeoutException: 2 millis
> timeout while waiting for channel to be ready for connect. ch :
> java.nio.channels.SocketChannel[connection-pending
> remote=yarnrm2/x.x.x.x:8031]
> at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:534)
> at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
> at
> org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:609)
> at
> org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:707)
> at
> org.apache.hadoop.ipc.Client$Connection.access$2800(Client.java:370)
> at org.apache.hadoop.ipc.Client.getConnection(Client.java:1529)
> at org.apache.hadoop.ipc.Client.call(Client.java:1446)
> ... 12 more{noformat}
> We get this and failover back to rm1 30 times until:
> {noformat}
> 18/06/06 15:39:44 WARN retry.RetryInvocationHandler: Exception while invoking
> class
> org.apache.hadoop.yarn.server.api.impl.pb.client.ResourceTrackerPBClientImpl.nodeHeartbeat
> over rm1. Not retrying because failovers (30) exceeded maximum allowed
> (30){noformat}
> From the logs it appears that the timeouts happen because it's trying to
> connect to the old ip (x.x.x.x in the logs). Looking at the code of the
> Client class, following the updateAddress method call we should expect a
> retry with the new server ip ("Retrying connect to server ..." log) up to
> ipc.client.connect.max.retries.on.timeouts times. However we neve
[jira] [Moved] (YARN-8416) YARN in HA not failing over to a new resource manager.
[
https://issues.apache.org/jira/browse/YARN-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma moved HDFS-13669 to YARN-8416:
---
Affects Version/s: (was: 2.7.1)
2.7.1
Key: YARN-8416 (was: HDFS-13669)
Project: Hadoop YARN (was: Hadoop HDFS)
> YARN in HA not failing over to a new resource manager.
> --
>
> Key: YARN-8416
> URL: https://issues.apache.org/jira/browse/YARN-8416
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Danil Serdyuchenko
>Priority: Major
>
> We are running YARN in HA mode. (rm1 and rm2) We hit an issue when recreating
> one of the RMs.
> # Recreated a standby RM (rm2), which gave it a new IP
> # Stopped the active RM (rm1)
> # NMs tried to failover to rm2, but were timing out because of the old ip.
> # NMs reach the configured 30 failover retries and shutdown.
> We get the following logs.
> {noformat}
> 18/06/06 15:36:32 WARN ipc.Client: Address change detected. Old:
> yarnrm2/x.x.x.x:8031 New: yarnrm2/y.y.y.y:8031
> 18/06/06 15:36:32 INFO retry.RetryInvocationHandler: Exception while invoking
> nodeHeartbeat of class ResourceTrackerPBClientImpl over rm2 after 25 fail
> over attempts. Trying to fail over after sleeping for 37191ms.
> org.apache.hadoop.net.ConnectTimeoutException: Call From ip-a-a-a-a/a.a.a.a
> to yarnrm2:8031 failed on socket timeout exception:
> org.apache.hadoop.net.ConnectTimeoutException: 2 millis timeout while
> waiting for channel to be ready for connect. ch :
> java.nio.channels.SocketChannel[connection-pending
> remote=yarnrm2/x.x.x.x:8031]; For more details see:
> http://wiki.apache.org/hadoop/SocketTimeout
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at org.apache.hadoop.net.NetUtils.wrapWithMessage(NetUtils.java:792)
> at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:751)
> at org.apache.hadoop.ipc.Client.call(Client.java:1480)
> at org.apache.hadoop.ipc.Client.call(Client.java:1407)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
> at com.sun.proxy.$Proxy28.nodeHeartbeat(Unknown Source)
> at
> org.apache.hadoop.yarn.server.api.impl.pb.client.ResourceTrackerPBClientImpl.nodeHeartbeat(ResourceTrackerPBClientImpl.java:80)
> at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:187)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
> at com.sun.proxy.$Proxy29.nodeHeartbeat(Unknown Source)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl$1.run(NodeStatusUpdaterImpl.java:596)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.hadoop.net.ConnectTimeoutException: 2 millis
> timeout while waiting for channel to be ready for connect. ch :
> java.nio.channels.SocketChannel[connection-pending
> remote=yarnrm2/x.x.x.x:8031]
> at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:534)
> at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
> at
> org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:609)
> at
> org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:707)
> at
> org.apache.hadoop.ipc.Client$Connection.access$2800(Client.java:370)
> at org.apache.hadoop.ipc.Client.getConnection(Client.java:1529)
> at org.apache.hadoop.ipc.Client.call(Client.java:1446)
> ... 12 more{noformat}
> We get this and failover back to rm1 30 times until:
> {noformat}
> 18/06/06 15:39:44 WARN retry.RetryInvocationHandler: Exception while invoking
> class
> org.apache.hadoop.yarn.server.api.impl.pb.client.ResourceTrackerPBClientImpl.nodeHeartbeat
> over rm1. Not retrying because failovers (30) exceeded maximum allowed
> (30){noformat}
> From the logs it appears that the timeouts happen because it's trying to
> connect to the old ip (x.x.x.x in the logs). Looking at the code of the
> Client class, following the updateAddress method call we should expect a
> retry with the new server ip ("R
[jira] [Commented] (YARN-8363) Upgrade common-langs version to 3.7 in hadoop-yarn-project
[
https://issues.apache.org/jira/browse/YARN-8363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507900#comment-16507900
]
Takanobu Asanuma commented on YARN-8363:
Uploaded the 1st patch. I've confirmed that the native package build succeeds
with the patch.
In most cases, I just renamed classes and methods. I'd like to explain the
other modifications.
* 0-argument constructor in NotImplementedException is removed. The patch
specify a message to keep the compatibility.
[https://github.com/apache/commons-lang/blob/LANG_2_6/src/main/java/org/apache/commons/lang/NotImplementedException.java#L82]
* {{StringUtils.isAlpha}} breaks compatibility when the argument is an empty
string. The regression test is {{TestResourceUtils.testGetResourceInformation.}}
{code:java}
org.apache.commons.lang.StringUtils.isAlpha("") // true
org.apache.commons.lang3.StringUtils.isAlpha("") // false
{code}
* Since {{Range}} classes become a generic class, an additional logic is
needed in {{BasePBImplRecordsTest}}. The regression test is
{{TestPBImplRecords.testGetApplicationsRequestPBImpl}}.
> Upgrade common-langs version to 3.7 in hadoop-yarn-project
> --
>
> Key: YARN-8363
> URL: https://issues.apache.org/jira/browse/YARN-8363
> Project: Hadoop YARN
> Issue Type: Improvement
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8363.1.patch
>
>
> commons-lang 2.6 is widely used. Let's upgrade to 3.6.
> This jira is separated from HADOOP-10783.
--
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
[jira] [Updated] (YARN-8363) Upgrade common-langs version to 3.7 in hadoop-yarn-project
[ https://issues.apache.org/jira/browse/YARN-8363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takanobu Asanuma updated YARN-8363: --- Attachment: YARN-8363.1.patch > Upgrade common-langs version to 3.7 in hadoop-yarn-project > -- > > Key: YARN-8363 > URL: https://issues.apache.org/jira/browse/YARN-8363 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Takanobu Asanuma >Assignee: Takanobu Asanuma >Priority: Major > Attachments: YARN-8363.1.patch > > > commons-lang 2.6 is widely used. Let's upgrade to 3.6. > This jira is separated from HADOOP-10783. -- 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
[jira] [Created] (YARN-8408) Upgrade common-langs version to 3.7 in HDDS and Ozone
Takanobu Asanuma created YARN-8408: -- Summary: Upgrade common-langs version to 3.7 in HDDS and Ozone Key: YARN-8408 URL: https://issues.apache.org/jira/browse/YARN-8408 Project: Hadoop YARN Issue Type: Improvement Reporter: Takanobu Asanuma Assignee: Takanobu Asanuma commons-lang 2.6 is widely used. Let's upgrade to 3.6. This jira is separated from HADOOP-10783. -- 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
[jira] [Commented] (YARN-8389) Improve the description of machine-list property in Federation docs
[ https://issues.apache.org/jira/browse/YARN-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501106#comment-16501106 ] Takanobu Asanuma commented on YARN-8389: Thanks for reviewing and committing it, [~giovanni.fumarola] and [~elgoiri]! > Improve the description of machine-list property in Federation docs > --- > > Key: YARN-8389 > URL: https://issues.apache.org/jira/browse/YARN-8389 > Project: Hadoop YARN > Issue Type: Improvement > Components: documentation, federation >Affects Versions: 3.2.0, 3.1.1 >Reporter: Takanobu Asanuma >Assignee: Takanobu Asanuma >Priority: Major > Fix For: 3.2.0, 3.1.1 > > Attachments: YARN-8389.1.patch > > > The current example and the description for machine-list property seem to be > a bit ambiguous. > http://hadoop.apache.org/docs/r3.1.0/hadoop-yarn/hadoop-yarn-site/Federation.html#Optional: -- 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
[jira] [Commented] (YARN-8389) Improve the description of machine-list property in Federation docs
[ https://issues.apache.org/jira/browse/YARN-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500170#comment-16500170 ] Takanobu Asanuma commented on YARN-8389: Uploaded the 1st patch. > Improve the description of machine-list property in Federation docs > --- > > Key: YARN-8389 > URL: https://issues.apache.org/jira/browse/YARN-8389 > Project: Hadoop YARN > Issue Type: Improvement > Components: documentation, federation >Affects Versions: 3.2.0, 3.1.1 >Reporter: Takanobu Asanuma >Assignee: Takanobu Asanuma >Priority: Major > Attachments: YARN-8389.1.patch > > > The current example and the description seem to be a bit ambiguous. > http://hadoop.apache.org/docs/r3.1.0/hadoop-yarn/hadoop-yarn-site/Federation.html#Optional: -- 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
[jira] [Updated] (YARN-8389) Improve the description of machine-list property in Federation docs
[ https://issues.apache.org/jira/browse/YARN-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takanobu Asanuma updated YARN-8389: --- Attachment: YARN-8389.1.patch > Improve the description of machine-list property in Federation docs > --- > > Key: YARN-8389 > URL: https://issues.apache.org/jira/browse/YARN-8389 > Project: Hadoop YARN > Issue Type: Improvement > Components: documentation, federation >Affects Versions: 3.2.0, 3.1.1 >Reporter: Takanobu Asanuma >Assignee: Takanobu Asanuma >Priority: Major > Attachments: YARN-8389.1.patch > > > The current example and the description seem to be a bit ambiguous. > http://hadoop.apache.org/docs/r3.1.0/hadoop-yarn/hadoop-yarn-site/Federation.html#Optional: -- 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
[jira] [Created] (YARN-8389) Improve the description of machine-list property in Federation docs
Takanobu Asanuma created YARN-8389: -- Summary: Improve the description of machine-list property in Federation docs Key: YARN-8389 URL: https://issues.apache.org/jira/browse/YARN-8389 Project: Hadoop YARN Issue Type: Improvement Components: documentation, federation Affects Versions: 3.2.0, 3.1.1 Reporter: Takanobu Asanuma Assignee: Takanobu Asanuma The current example and the description seem to be a bit ambiguous. http://hadoop.apache.org/docs/r3.1.0/hadoop-yarn/hadoop-yarn-site/Federation.html#Optional: -- 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
[jira] [Commented] (YARN-8377) Javadoc build failed in hadoop-yarn-server-nodemanager
[
https://issues.apache.org/jira/browse/YARN-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495945#comment-16495945
]
Takanobu Asanuma commented on YARN-8377:
Thanks for reviewing and committing it, [~eepayne]!
> Javadoc build failed in hadoop-yarn-server-nodemanager
> --
>
> Key: YARN-8377
> URL: https://issues.apache.org/jira/browse/YARN-8377
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, docs
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Critical
> Fix For: 3.2.0, 3.1.1
>
> Attachments: YARN-8377.1.patch
>
>
> This is the same cause as YARN-8369.
> {code}
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/container/SlidingWindowRetryPolicy.java:88:
> error: bad use of '>'
> [ERROR]* When failuresValidityInterval is > 0, it also removes time
> entries from
> [ERROR] ^
> {code}
--
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
[jira] [Commented] (YARN-8369) Javadoc build failed due to "bad use of '>'"
[
https://issues.apache.org/jira/browse/YARN-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494678#comment-16494678
]
Takanobu Asanuma commented on YARN-8369:
Sorry, there is one more same error. Filed it in YARN-8377.
> Javadoc build failed due to "bad use of '>'"
>
>
> Key: YARN-8369
> URL: https://issues.apache.org/jira/browse/YARN-8369
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, docs
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Critical
> Fix For: 3.2.0, 3.1.1
>
> Attachments: YARN-8369.1.patch, YARN-8369.2.patch
>
>
> {noformat}
> $ mvn javadoc:javadoc --projects
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
> ...
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:263:
> error: bad use of '>'
> [ERROR]* included) has a >0 value.
> [ERROR] ^
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:266:
> error: bad use of '>'
> [ERROR]* @return returns true if any resource is >0
> [ERROR] ^
> {noformat}
--
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
[jira] [Commented] (YARN-8377) Javadoc build failed in hadoop-yarn-server-nodemanager
[
https://issues.apache.org/jira/browse/YARN-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494672#comment-16494672
]
Takanobu Asanuma commented on YARN-8377:
I'm sorry that I didn't find the error in YARN-8369.
Uploaded the 1st patch. I've just confirmed that {{mvn clean package
-Pdist,native -Dtar -DskipTests}} succeeded with the patch.
> Javadoc build failed in hadoop-yarn-server-nodemanager
> --
>
> Key: YARN-8377
> URL: https://issues.apache.org/jira/browse/YARN-8377
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, docs
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Critical
> Attachments: YARN-8377.1.patch
>
>
> This is the same cause as YARN-8369.
> {code}
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/container/SlidingWindowRetryPolicy.java:88:
> error: bad use of '>'
> [ERROR]* When failuresValidityInterval is > 0, it also removes time
> entries from
> [ERROR] ^
> {code}
--
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
[jira] [Updated] (YARN-8377) Javadoc build failed in hadoop-yarn-server-nodemanager
[
https://issues.apache.org/jira/browse/YARN-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma updated YARN-8377:
---
Attachment: YARN-8377.1.patch
> Javadoc build failed in hadoop-yarn-server-nodemanager
> --
>
> Key: YARN-8377
> URL: https://issues.apache.org/jira/browse/YARN-8377
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, docs
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Critical
> Attachments: YARN-8377.1.patch
>
>
> This is the same cause as YARN-8369.
> {code}
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/container/SlidingWindowRetryPolicy.java:88:
> error: bad use of '>'
> [ERROR]* When failuresValidityInterval is > 0, it also removes time
> entries from
> [ERROR] ^
> {code}
--
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
[jira] [Created] (YARN-8377) Javadoc build failed in hadoop-yarn-server-nodemanager
Takanobu Asanuma created YARN-8377:
--
Summary: Javadoc build failed in hadoop-yarn-server-nodemanager
Key: YARN-8377
URL: https://issues.apache.org/jira/browse/YARN-8377
Project: Hadoop YARN
Issue Type: Bug
Components: build, docs
Reporter: Takanobu Asanuma
Assignee: Takanobu Asanuma
This is the same cause as YARN-8369.
{code}
[ERROR]
/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/container/SlidingWindowRetryPolicy.java:88:
error: bad use of '>'
[ERROR]* When failuresValidityInterval is > 0, it also removes time entries
from
[ERROR] ^
{code}
--
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
[jira] [Commented] (YARN-8369) Javadoc build failed due to "bad use of '>'"
[
https://issues.apache.org/jira/browse/YARN-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494441#comment-16494441
]
Takanobu Asanuma commented on YARN-8369:
Thanks for committing it, [~leftnoteasy]!
> Javadoc build failed due to "bad use of '>'"
>
>
> Key: YARN-8369
> URL: https://issues.apache.org/jira/browse/YARN-8369
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, docs
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Critical
> Fix For: 3.2.0, 3.1.1
>
> Attachments: YARN-8369.1.patch, YARN-8369.2.patch
>
>
> {noformat}
> $ mvn javadoc:javadoc --projects
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
> ...
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:263:
> error: bad use of '>'
> [ERROR]* included) has a >0 value.
> [ERROR] ^
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:266:
> error: bad use of '>'
> [ERROR]* @return returns true if any resource is >0
> [ERROR] ^
> {noformat}
--
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
[jira] [Commented] (YARN-8369) Javadoc build failed due to "bad use of '>'"
[
https://issues.apache.org/jira/browse/YARN-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492596#comment-16492596
]
Takanobu Asanuma commented on YARN-8369:
Thanks for the review, [~sunilg], and thanks for reporting the further issue,
[~rohithsharma]!
Uploaded the 2nd patch addressing it.
> Javadoc build failed due to "bad use of '>'"
>
>
> Key: YARN-8369
> URL: https://issues.apache.org/jira/browse/YARN-8369
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, docs
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8369.1.patch, YARN-8369.2.patch
>
>
> {noformat}
> $ mvn javadoc:javadoc --projects
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
> ...
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:263:
> error: bad use of '>'
> [ERROR]* included) has a >0 value.
> [ERROR] ^
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:266:
> error: bad use of '>'
> [ERROR]* @return returns true if any resource is >0
> [ERROR] ^
> {noformat}
--
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
[jira] [Updated] (YARN-8369) Javadoc build failed due to "bad use of '>'"
[
https://issues.apache.org/jira/browse/YARN-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma updated YARN-8369:
---
Attachment: YARN-8369.2.patch
> Javadoc build failed due to "bad use of '>'"
>
>
> Key: YARN-8369
> URL: https://issues.apache.org/jira/browse/YARN-8369
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, docs
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8369.1.patch, YARN-8369.2.patch
>
>
> {noformat}
> $ mvn javadoc:javadoc --projects
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
> ...
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:263:
> error: bad use of '>'
> [ERROR]* included) has a >0 value.
> [ERROR] ^
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:266:
> error: bad use of '>'
> [ERROR]* @return returns true if any resource is >0
> [ERROR] ^
> {noformat}
--
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
[jira] [Updated] (YARN-8369) Javadoc build failed due to "bad use of '>'"
[
https://issues.apache.org/jira/browse/YARN-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma updated YARN-8369:
---
Component/s: build
> Javadoc build failed due to "bad use of '>'"
>
>
> Key: YARN-8369
> URL: https://issues.apache.org/jira/browse/YARN-8369
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, docs
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8369.1.patch
>
>
> {noformat}
> $ mvn javadoc:javadoc --projects
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
> ...
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:263:
> error: bad use of '>'
> [ERROR]* included) has a >0 value.
> [ERROR] ^
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:266:
> error: bad use of '>'
> [ERROR]* @return returns true if any resource is >0
> [ERROR] ^
> {noformat}
--
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
[jira] [Commented] (YARN-8369) Javadoc build failed due to "bad use of '>'"
[
https://issues.apache.org/jira/browse/YARN-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491478#comment-16491478
]
Takanobu Asanuma commented on YARN-8369:
Uploaded the 1st patch.
> Javadoc build failed due to "bad use of '>'"
>
>
> Key: YARN-8369
> URL: https://issues.apache.org/jira/browse/YARN-8369
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, docs
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8369.1.patch
>
>
> {noformat}
> $ mvn javadoc:javadoc --projects
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
> ...
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:263:
> error: bad use of '>'
> [ERROR]* included) has a >0 value.
> [ERROR] ^
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:266:
> error: bad use of '>'
> [ERROR]* @return returns true if any resource is >0
> [ERROR] ^
> {noformat}
--
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
[jira] [Updated] (YARN-8369) Javadoc build failed due to "bad use of '>'"
[
https://issues.apache.org/jira/browse/YARN-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma updated YARN-8369:
---
Attachment: YARN-8369.1.patch
> Javadoc build failed due to "bad use of '>'"
>
>
> Key: YARN-8369
> URL: https://issues.apache.org/jira/browse/YARN-8369
> Project: Hadoop YARN
> Issue Type: Bug
> Components: docs
>Reporter: Takanobu Asanuma
>Assignee: Takanobu Asanuma
>Priority: Major
> Attachments: YARN-8369.1.patch
>
>
> {noformat}
> $ mvn javadoc:javadoc --projects
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
> ...
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:263:
> error: bad use of '>'
> [ERROR]* included) has a >0 value.
> [ERROR] ^
> [ERROR]
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:266:
> error: bad use of '>'
> [ERROR]* @return returns true if any resource is >0
> [ERROR] ^
> {noformat}
--
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
[jira] [Created] (YARN-8369) Javadoc build failed due to "bad use of '>'"
Takanobu Asanuma created YARN-8369:
--
Summary: Javadoc build failed due to "bad use of '>'"
Key: YARN-8369
URL: https://issues.apache.org/jira/browse/YARN-8369
Project: Hadoop YARN
Issue Type: Bug
Components: docs
Reporter: Takanobu Asanuma
Assignee: Takanobu Asanuma
{noformat}
$ mvn javadoc:javadoc --projects
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
...
[ERROR]
/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:263:
error: bad use of '>'
[ERROR]* included) has a >0 value.
[ERROR] ^
[ERROR]
/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceCalculator.java:266:
error: bad use of '>'
[ERROR]* @return returns true if any resource is >0
[ERROR] ^
{noformat}
--
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
[jira] [Created] (YARN-8363) Upgrade common-langs version to 3.7 in hadoop-yarn-project
Takanobu Asanuma created YARN-8363: -- Summary: Upgrade common-langs version to 3.7 in hadoop-yarn-project Key: YARN-8363 URL: https://issues.apache.org/jira/browse/YARN-8363 Project: Hadoop YARN Issue Type: Improvement Reporter: Takanobu Asanuma Assignee: Takanobu Asanuma commons-lang 2.6 is widely used. Let's upgrade to 3.6. This jira is separated from HADOOP-10783. -- 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
[jira] [Commented] (YARN-8123) Skip compiling old hamlet package when the Java version is 10 or upper
[
https://issues.apache.org/jira/browse/YARN-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475163#comment-16475163
]
Takanobu Asanuma commented on YARN-8123:
Thanks for the patch, [~dineshchitlangia]!
I have confirmed that the below command with applying the patch succeeds
through jdk9 and jdk10. +1 (non-binding).
{noformat}
mvn clean javadoc:javadoc --projects
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
{noformat}
> Skip compiling old hamlet package when the Java version is 10 or upper
> --
>
> Key: YARN-8123
> URL: https://issues.apache.org/jira/browse/YARN-8123
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: webapp
> Environment: Java 10 or upper
>Reporter: Akira Ajisaka
>Assignee: Dinesh Chitlangia
>Priority: Major
> Labels: newbie
> Attachments: YARN-8123.001.patch
>
>
> HADOOP-11423 skipped compiling old hamlet package when the Java version is 9,
> however, it is not skipped with Java 10+. We need to fix it.
--
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
[jira] [Commented] (YARN-8123) Skip compiling old hamlet package when the Java version is 10 or upper
[ https://issues.apache.org/jira/browse/YARN-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471362#comment-16471362 ] Takanobu Asanuma commented on YARN-8123: [~dineshchitlangia] Sure, please go ahead! [~ajisakaa] Could you assign this jira to [~dineshchitlangia] and give the right to contribution? (BTW, it looks like I also don't have the permission to contribute to YARN too. I appreciate if you could give it to me too.) > Skip compiling old hamlet package when the Java version is 10 or upper > -- > > Key: YARN-8123 > URL: https://issues.apache.org/jira/browse/YARN-8123 > Project: Hadoop YARN > Issue Type: Improvement > Components: webapp > Environment: Java 10 or upper >Reporter: Akira Ajisaka >Priority: Major > Labels: newbie > > HADOOP-11423 skipped compiling old hamlet package when the Java version is 9, > however, it is not skipped with Java 10+. We need to fix it. -- 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
[jira] [Commented] (YARN-8123) Skip compiling old hamlet package when the Java version is 10 or upper
[ https://issues.apache.org/jira/browse/YARN-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429930#comment-16429930 ] Takanobu Asanuma commented on YARN-8123: Thanks for filing this issue [~ajisakaa], and thanks for your thought [~dineshchitlangia]. I think we should also include java9 at this stage. > Skip compiling old hamlet package when the Java version is 10 or upper > -- > > Key: YARN-8123 > URL: https://issues.apache.org/jira/browse/YARN-8123 > Project: Hadoop YARN > Issue Type: Improvement > Components: webapp > Environment: Java 10 or upper >Reporter: Akira Ajisaka >Priority: Major > Labels: newbie > > HADOOP-11423 skipped compiling old hamlet package when the Java version is 9, > however, it is not skipped with Java 10+. We need to fix it. -- 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
[jira] [Commented] (YARN-7735) Fix typo in YARN documentation
[ https://issues.apache.org/jira/browse/YARN-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16321793#comment-16321793 ] Takanobu Asanuma commented on YARN-7735: Thanks for reviewing and committing it, [~ajisakaa]! > Fix typo in YARN documentation > -- > > Key: YARN-7735 > URL: https://issues.apache.org/jira/browse/YARN-7735 > Project: Hadoop YARN > Issue Type: Bug > Components: documentation >Reporter: Takanobu Asanuma >Assignee: Takanobu Asanuma >Priority: Minor > Fix For: 3.1.0, 2.10.0, 2.9.1, 3.0.1 > > Attachments: HADOOP-15165.1.patch > > > The link of "YARN Federation" is wrong. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
