Lakshmi Manasa Gaduputi created SAMZA-2607:
----------------------------------------------
Summary: Tech debt in AM HA - remove persisting yarn id mapping in
state + move config to correct space
Key: SAMZA-2607
URL: https://issues.apache.org/jira/browse/SAMZA-2607
Project: Samza
Issue Type: New Feature
Reporter: Lakshmi Manasa Gaduputi
Assignee: Lakshmi Manasa Gaduputi
New feature AM HA code - has a couple of tech debt
# Current impl persists the processor id to yarn id mapping in the
SamzaApplicationState throughout the life cycle of the AM. remove this as this
mapping is needed only during the start of new AM and not needed later. Ideas
for this below
# new config for AM HA is in JobConfig. move this to ClusterManagerConfig
Ideas for not persisting yarn id mapping in state
# pass around metadata store all the way down to SamzaAppMasterLifeCycle where
it can read from store only when needed. Or read in CPM/YarnResourceManager and
pass map to Lifecycle.
# Internal config which is populated with the mapping - needs serialization
and deserialization.
# Provider - passed into resource manager factory - this provider gives state,
job model, config. use this route to pass in the mapping/store itself.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
