[SAMZA-1203] Use ProcessorId instead of Zk node Id in JobModel generation

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Duplicate
• Affects Version/s: 0.13.0
• Fix Version/s: 0.13.0
• Assignee: Navina Ramesh
• Reporter: Xinyu Liu
• Created: 10/Apr/17 19:18
• Updated: 17/Apr/17 02:55
• Resolved: 13/Apr/17 23:51

Description

when ZkJobCoordinator generates the jobModel, it's using Zk node Ids instead of the processorIds, as the code below: ZkJobCoordinator: 215-220:
List<String> containerIds = new ArrayList<>();
for (String processor : currentProcessors)

{ String zkProcessorId = ZkKeyBuilder.parseIdFromPath(processor); containerIds.add(zkProcessorId); }

log.info("generate new job model: processorsIds: " + Arrays.toString(containerIds.toArray()));

Later the StreamProcessor gets the containerModel, it's null. We need to use the processorId in the JobModel so StreamProcessors will work correctly.

Issue Links

• is depended upon by: SAMZA-1064 Standalone Samza with Zookeeper for Coordination
• is depended upon by: SAMZA-1130 ApplicationRunner for running StreamApplication