[CONF] Apache Samza > Host affinity in standalone.

[Shanthoosh Venkataraman (Confluence)]

Title: Message Title

Shanthoosh Venkataraman edited a page

Host affinity in standalone. ... Every stream application in samza has many task instances which contains a custom user-defined function for processing events from a stream. Each task instance will have one to many associated local stores. Local store of a task instance is backed up by an log compacted kafka topic referred to as change-log. When a task instance commits, incremental local task store updates are flushed to the kafka topic. When a task instance runs on a host that doesn’t have latest local store, it’s restored by replaying messages from the change-log stream. For large stateful jobs, this restoration phase takes longer time, thus preventing the application from starting up and processing events from the input streams. Host affinity is a feature that maintains stickiness between a task and physical host and offers best-effort guarantees that a task instance will be assigned to run on the same physical it had ran before. This document discusses some potential approaches to support this feature in standalone deployment model. Requirements ... Goals Support stateful stream processing in standalone stream applications. Minimize partition movements amongst stateless stateful processors in the rebalance phase. ... View page • Add comment • Like

Stop watching space • Manage notifications This message was sent by Atlassian Confluence 5.8.17