[CONF] Apache Samza > SEP-22: Container Placements in Samza

[Prateek Maheshwari (Confluence)]

Title: Message Title

There's 11 new inline comments on this page

SEP-22: Container Placements in Samza Prateek Maheshwari request-expiry-timeout Why does this need to be specified / overridden by the client? View comment • Like Prateek Maheshwari CREATED What's the difference b/w created and accepted? View comment • Like Prateek Maheshwari processorId processorId or uuid? Incomplete statement. View comment • Like Prateek Maheshwari user application-version. Users don't come with versions  View comment • Like Prateek Maheshwari UNAUTHORIZED No Bad request? E.g., what if one of the ids is invalid? Why is this status needed btw? Is this request async as well? View comment • Like Prateek Maheshwari registerContainerPlacementAction placeContainer View comment • Like Prateek Maheshwari processor-id: No appId / uuid? View comment • Like Prateek Maheshwari ACCEPTED Same as above. View comment • Like Prateek Maheshwari Control Plane as described plane above the job Can you clarify this sentence? Not clear what this means. View comment • Like Prateek Maheshwari handler registered to control plane What does this mean? View comment • Like Prateek Maheshwari maintaining some in-memory state with Container Placement Service Who's responsibility is it to dedup requests? CPH or CPS? If CPH, why is the state kept in CPS? View comment • Like View page

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