[jira] [Commented] (YARN-5721) NPE at AMRMClientImpl.getMatchingRequests
[
https://issues.apache.org/jira/browse/YARN-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15632529#comment-15632529
]
Zoltán Zvara commented on YARN-5721:
Thanks [~templedf], great to see that JIRA & Github help us to duplicate
efforts.
> NPE at AMRMClientImpl.getMatchingRequests
> -
>
> Key: YARN-5721
> URL: https://issues.apache.org/jira/browse/YARN-5721
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api
> Environment: Tested on Windows 10, in Dockerized Linux containers &
> Ubuntu 16.04 with Java 7, Java 8.
>Reporter: Zoltán Zvara
>Priority: Blocker
>
> The following NPE was thrown using a Spark 2.1.0-SNAPSHOT (as client) by
> changing Hadoop dependency to the latest (by the time the ERROR has been
> generated).
> {{2016-10-10 11:33:53,392 ERROR yarn.ApplicationMaster: Uncaught exception:
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.getMatchingRequests(AMRMClientImpl.java:668)
> at
> org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.getMatchingRequests(AMRMClientImpl.java:651)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.getPendingAtLocation(YarnAllocator.scala:210)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.getPendingAllocate(YarnAllocator.scala:203)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.updateResourceRequests(YarnAllocator.scala:318)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.allocateResources(YarnAllocator.scala:278)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.registerAM(ApplicationMaster.scala:350)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.runExecutorLauncher(ApplicationMaster.scala:418)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.run(ApplicationMaster.scala:250)}}
> We've also pulled the latest code (1 hour ago) from the repository, and ran a
> test for {{getMatchingRequests}}. Same NPE has been encountered.
> {{getMatchingRequests}} should never throw an NPE even if it has been called
> right after the client has been started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5721) NPE at AMRMClientImpl.getMatchingRequests
[
https://issues.apache.org/jira/browse/YARN-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15582577#comment-15582577
]
ASF GitHub Bot commented on YARN-5721:
--
Github user zzvara commented on the issue:
https://github.com/apache/hadoop/pull/139
Looks good and fixes the problem.
> NPE at AMRMClientImpl.getMatchingRequests
> -
>
> Key: YARN-5721
> URL: https://issues.apache.org/jira/browse/YARN-5721
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api
> Environment: Tested on Windows 10, in Dockerized Linux containers &
> Ubuntu 16.04 with Java 7, Java 8.
>Reporter: Zoltán Zvara
>Priority: Blocker
>
> The following NPE was thrown using a Spark 2.1.0-SNAPSHOT (as client) by
> changing Hadoop dependency to the latest (by the time the ERROR has been
> generated).
> {{2016-10-10 11:33:53,392 ERROR yarn.ApplicationMaster: Uncaught exception:
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.getMatchingRequests(AMRMClientImpl.java:668)
> at
> org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.getMatchingRequests(AMRMClientImpl.java:651)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.getPendingAtLocation(YarnAllocator.scala:210)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.getPendingAllocate(YarnAllocator.scala:203)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.updateResourceRequests(YarnAllocator.scala:318)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.allocateResources(YarnAllocator.scala:278)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.registerAM(ApplicationMaster.scala:350)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.runExecutorLauncher(ApplicationMaster.scala:418)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.run(ApplicationMaster.scala:250)}}
> We've also pulled the latest code (1 hour ago) from the repository, and ran a
> test for {{getMatchingRequests}}. Same NPE has been encountered.
> {{getMatchingRequests}} should never throw an NPE even if it has been called
> right after the client has been started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5721) NPE at AMRMClientImpl.getMatchingRequests
[
https://issues.apache.org/jira/browse/YARN-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565431#comment-15565431
]
ASF GitHub Bot commented on YARN-5721:
--
GitHub user szape opened a pull request:
https://github.com/apache/hadoop/pull/139
YARN-5721. NPE at AMRMClientImpl.getMatchingRequests
The following NPE was thrown using a Spark 2.1.0-SNAPSHOT (as client) by
changing Hadoop dependency to the latest (by the time the ERROR has been
generated).
{{2016-10-10 11:33:53,392 ERROR yarn.ApplicationMaster: Uncaught exception:
java.lang.NullPointerException
at
org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.getMatchingRequests(AMRMClientImpl.java:668)
at
org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.getMatchingRequests(AMRMClientImpl.java:651)
at
org.apache.spark.deploy.yarn.YarnAllocator.getPendingAtLocation(YarnAllocator.scala:210)
at
org.apache.spark.deploy.yarn.YarnAllocator.getPendingAllocate(YarnAllocator.scala:203)
at
org.apache.spark.deploy.yarn.YarnAllocator.updateResourceRequests(YarnAllocator.scala:318)
at
org.apache.spark.deploy.yarn.YarnAllocator.allocateResources(YarnAllocator.scala:278)
at
org.apache.spark.deploy.yarn.ApplicationMaster.registerAM(ApplicationMaster.scala:350)
at
org.apache.spark.deploy.yarn.ApplicationMaster.runExecutorLauncher(ApplicationMaster.scala:418)
at
org.apache.spark.deploy.yarn.ApplicationMaster.run(ApplicationMaster.scala:250)}}
We've also pulled the latest code (1 hour ago) from the repository, and ran
a test for getMatchingRequests. Same NPE has been encountered.
getMatchingRequests should never throw an NPE even if it has been called
right after the client has been started.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/szape/hadoop YARN-5721
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hadoop/pull/139.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #139
commit 6070305ff126ff947055e9c4ce4f624e08b09e03
Author: szape
Date: 2016-10-11T13:19:29Z
YARN-5721. Fixed NullPointerException in AMRMClientImpl.getMatchingRequests
> NPE at AMRMClientImpl.getMatchingRequests
> -
>
> Key: YARN-5721
> URL: https://issues.apache.org/jira/browse/YARN-5721
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api
> Environment: Tested on Windows 10, in Dockerized Linux containers &
> Ubuntu 16.04 with Java 7, Java 8.
>Reporter: Zoltán Zvara
>Priority: Blocker
>
> The following NPE was thrown using a Spark 2.1.0-SNAPSHOT (as client) by
> changing Hadoop dependency to the latest (by the time the ERROR has been
> generated).
> {{2016-10-10 11:33:53,392 ERROR yarn.ApplicationMaster: Uncaught exception:
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.getMatchingRequests(AMRMClientImpl.java:668)
> at
> org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.getMatchingRequests(AMRMClientImpl.java:651)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.getPendingAtLocation(YarnAllocator.scala:210)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.getPendingAllocate(YarnAllocator.scala:203)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.updateResourceRequests(YarnAllocator.scala:318)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.allocateResources(YarnAllocator.scala:278)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.registerAM(ApplicationMaster.scala:350)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.runExecutorLauncher(ApplicationMaster.scala:418)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.run(ApplicationMaster.scala:250)}}
> We've also pulled the latest code (1 hour ago) from the repository, and ran a
> test for {{getMatchingRequests}}. Same NPE has been encountered.
> {{getMatchingRequests}} should never throw an NPE even if it has been called
> right after the client has been started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5721) NPE at AMRMClientImpl.getMatchingRequests
[
https://issues.apache.org/jira/browse/YARN-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565375#comment-15565375
]
Péter Szabó commented on YARN-5721:
---
In AMRMClientImpl.java line 668, remoteRequestsTable can be null. Critical
change was introduced with commit 19c743c1bbcaf3df8f1d63e557143c960a538c42.
> NPE at AMRMClientImpl.getMatchingRequests
> -
>
> Key: YARN-5721
> URL: https://issues.apache.org/jira/browse/YARN-5721
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api
> Environment: Tested on Windows 10, in Dockerized Linux containers &
> Ubuntu 16.04 with Java 7, Java 8.
>Reporter: Zoltán Zvara
>Priority: Blocker
>
> The following NPE was thrown using a Spark 2.1.0-SNAPSHOT (as client) by
> changing Hadoop dependency to the latest (by the time the ERROR has been
> generated).
> {{2016-10-10 11:33:53,392 ERROR yarn.ApplicationMaster: Uncaught exception:
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.getMatchingRequests(AMRMClientImpl.java:668)
> at
> org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.getMatchingRequests(AMRMClientImpl.java:651)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.getPendingAtLocation(YarnAllocator.scala:210)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.getPendingAllocate(YarnAllocator.scala:203)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.updateResourceRequests(YarnAllocator.scala:318)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.allocateResources(YarnAllocator.scala:278)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.registerAM(ApplicationMaster.scala:350)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.runExecutorLauncher(ApplicationMaster.scala:418)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.run(ApplicationMaster.scala:250)}}
> We've also pulled the latest code (1 hour ago) from the repository, and ran a
> test for {{getMatchingRequests}}. Same NPE has been encountered.
> {{getMatchingRequests}} should never throw an NPE even if it has been called
> right after the client has been started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5721) NPE at AMRMClientImpl.getMatchingRequests
[
https://issues.apache.org/jira/browse/YARN-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565340#comment-15565340
]
Péter Szabó commented on YARN-5721:
---
I'm working on it.
> NPE at AMRMClientImpl.getMatchingRequests
> -
>
> Key: YARN-5721
> URL: https://issues.apache.org/jira/browse/YARN-5721
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api
> Environment: Tested on Windows 10, in Dockerized Linux containers &
> Ubuntu 16.04 with Java 7, Java 8.
>Reporter: Zoltán Zvara
>Priority: Blocker
>
> The following NPE was thrown using a Spark 2.1.0-SNAPSHOT (as client) by
> changing Hadoop dependency to the latest (by the time the ERROR has been
> generated).
> {{2016-10-10 11:33:53,392 ERROR yarn.ApplicationMaster: Uncaught exception:
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.getMatchingRequests(AMRMClientImpl.java:751)
> at
> org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.getMatchingRequests(AMRMClientImpl.java:734)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.getPendingAtLocation(YarnAllocator.scala:210)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.getPendingAllocate(YarnAllocator.scala:203)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.updateResourceRequests(YarnAllocator.scala:318)
> at
> org.apache.spark.deploy.yarn.YarnAllocator.allocateResources(YarnAllocator.scala:278)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.registerAM(ApplicationMaster.scala:350)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.runExecutorLauncher(ApplicationMaster.scala:418)
> at
> org.apache.spark.deploy.yarn.ApplicationMaster.run(ApplicationMaster.scala:250)}}
> We've also pulled the latest code (1 hour ago) from the repository, and ran a
> test for {{getMatchingRequests}}. Same NPE has been encountered.
> {{getMatchingRequests}} should never throw an NPE even if it has been called
> right after the client has been started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
