-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Today in Samza we do not guarantee that a container gets deployed on the same machine upon a job upgrade/restart. Hence, the co-located data needs to restored every time a container restarts. Restoring data each time can be expensive, especially for applications that have a large data set.
If we can enable restarting containers on the same machine, we can re-use available local state.
- depends upon
-
SAMZA-618 Add container-to-host mapping messages to config stream
-
- Resolved
-
-
SAMZA-619 Modify Samza AppMaster to enable host-affinity
-
- Resolved
-
-
SAMZA-656 Script to periodically clean-up store directories that are persisted outside YARN
-
- Resolved
-
-
SAMZA-668 Document YARN host affinity in the website
-
- Resolved
-
- duplicates
-
SAMZA-335 Locality for Samza containers
-
- Resolved
-
- relates to
-
SAMZA-557 Reuse local state in SamzaContainer on clean shutdown
-
- Resolved
-
-
SAMZA-598 Provide a tool to debug state stores
-
- Resolved
-
-
SAMZA-670 Allow easier access to JMX port
-
- Resolved
-