GitHub user vjagadish opened a pull request:
https://github.com/apache/samza/pull/504
Fix NPE in ClusterResourceManager
When the ClusterResourcedManager receives a notification that a container
is started, it moves the container from the "pending queue" to its "running
queue".
In the meanwhile, it's possible for another thread to remove the mapping
for the key. Here's an example:
NMCallbackThread-1:```
pendingYarnContainers.remove(key);```
NMCallbackThread-2:
```
for (String key : pendingYarnContainers.keySet()) {
yarnContainer = pendingYarnContainers.get(key); <-- could be null
depending on whether the removal happened before it.
}```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vjagadish1989/samza npe-fix-async
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/samza/pull/504.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 #504
----
commit bc11712ad090e93b8dc767659fff628e8b9ccd8f
Author: Jagadish <jvenkatraman@...>
Date: 2018-05-04T20:59:01Z
Fix NPE in ClusterResourceManager
----
---
