Yi Pan (Data Infrastructure) created SAMZA-816:
--------------------------------------------------
Summary: LocalityManager.register() should not register
coordinator stream SystemConsumer in SamzaContainer context
Key: SAMZA-816
URL: https://issues.apache.org/jira/browse/SAMZA-816
Project: Samza
Issue Type: Bug
Affects Versions: 0.10.0
Reporter: Yi Pan (Data Infrastructure)
In current code, LocalityManager.register() is invoked under SamzaContainer
context as well, which results in a false positive in the metrics
messages_behind_high_watermark: it include the lag the container has on the
coordinator stream as well, while there is no logic in the container to consume
the coordinator stream. It would be better to make two versions of
LocalityManager, one is used by JobCoordinator that reads the locality data,
while the other is used by SamzaContainer to write the locality data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)