[SAMZA-1147] ZkJobCoordinator does not honor the interface contract of JobCoordinator

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Fix Version/s: 0.13.0
• Assignee: Navina Ramesh
• Reporter: Navina Ramesh
• Created: 15/Mar/17 23:44
• Updated: 09/May/17 00:48
• Resolved: 09/May/17 00:48

Description

There is a mismatch in how StandaloneJobCoordinator and ZkJobCoordinator handle the start/stop/awaitStart semantics of JobCoordinator.
This impacts the StreamProcessor API behavior as well since the guarantees on the semantics of start / stop of the processors are broken in different runtime environments. This is weird and we need to revisit the how the components interact - StreamProcessor, JobCoordinator and SamzaContainer.

Issue Links

• is depended upon by: SAMZA-1064 Standalone Samza with Zookeeper for Coordination
• relates to: SAMZA-1084 User thread does not see errors from the processor thread when using the StreamProcessor API