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

[Sanil Jain (Confluence)]

Title: Message Title

There's 5 reopened inline comments and 2 new edits on this page

SEP-22: Container Placements in Samza 5 reopened inline comments Sanil Jain reopened No need to build Authentication since AM runs on hosts which are blacklisted for anyone except the Samza Team LI specific detail, not true in general. View comment • Like Sanil Jain reopened individual namespaces Are requests and responses separate namespaces? If so, why? View comment • Like Sanil Jain reopened processorId Where is UUID and deployment ID? In the payload?  Can you document the message structure (key and value). View comment • Like Sanil Jain reopened delete messages Who does this? View comment • Like Sanil Jain reopened References Remove references to internal docs. View comment • Like 2 new edits Sanil Jain edited this page Here's what changed: ... Current state: [ UNDER DISCUSSION ] Discussion thread: <link to mailing list DISCUSS thread> http://mail-archives.apache.org/mod_mbox/samza-dev/202001.mbox/browser JIRA: SAMZA-2373 Released: TBD ... One way to delete stale ContainerPlacementMessages is to delete request/responses from the previous incarnation of the job in the metastore on job restarts, this is the responsibility of ContainerPlacementService  Once the request is complete, ContainerPlacementService can issue an async delete to clean up the request from the metastore Request/response message can be externally cleaned by a tool ... Go to page history View page

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