Prateek Maheshwari created SAMZA-1628:
-----------------------------------------
Summary: LocalityManager should handle null locality values
correctly
Key: SAMZA-1628
URL: https://issues.apache.org/jira/browse/SAMZA-1628
Project: Samza
Issue Type: Bug
Reporter: Prateek Maheshwari
Writing a null value for the "set-container-host-mapping" key in the
coordinator stream (e.g., to clear locality information for jobs with host
affinity), causes subsequent Job start to fail with the following exception in
the ClusterBasedJobCoordinator.
{code:java}
Exception in thread "main" java.lang.NullPointerException
at
org.apache.samza.coordinator.stream.messages.CoordinatorStreamMessage.getMessageValues(CoordinatorStreamMessage.java:190)
at
org.apache.samza.coordinator.stream.messages.CoordinatorStreamMessage.getMessageValue(CoordinatorStreamMessage.java:194)
at
org.apache.samza.coordinator.stream.messages.SetContainerHostMapping.getHostLocality(SetContainerHostMapping.java:71)
at
org.apache.samza.container.LocalityManager.readContainerLocality(LocalityManager.java:72)
at
org.apache.samza.job.model.JobModel.populateContainerLocalityMappings(JobModel.java:125)
at org.apache.samza.job.model.JobModel.<init>(JobModel.java:69)
at
org.apache.samza.coordinator.JobModelManager$.readJobModel(JobModelManager.scala:214)
at
org.apache.samza.coordinator.JobModelManager$.getJobModelManager(JobModelManager.scala:97)
at org.apache.samza.coordinator.JobModelManager$.apply(JobModelManager.scala:83)
at org.apache.samza.coordinator.JobModelManager.apply(JobModelManager.scala)
at
org.apache.samza.clustermanager.ClusterBasedJobCoordinator.<init>(ClusterBasedJobCoordinator.java:174)
at
org.apache.samza.clustermanager.ClusterBasedJobCoordinator.main(ClusterBasedJobCoordinator.java:331){code}
LocalityManager should handle null locality values correctly (i.e., treat them
as deletes).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
