[ https://issues.apache.org/jira/browse/SAMZA-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jagadish updated SAMZA-1699: ---------------------------- Fix Version/s: 0.14.1 0.15.0 > NPE in ClusterResourceManager > ----------------------------- > > Key: SAMZA-1699 > URL: https://issues.apache.org/jira/browse/SAMZA-1699 > Project: Samza > Issue Type: Bug > Reporter: Jagadish > Assignee: Jagadish > Priority: Major > Fix For: 0.15.0, 0.14.1 > > > 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. > } -- This message was sent by Atlassian JIRA (v7.6.3#76005)