THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
ContainerPlacementRequestMessage:
| Key | Value | Field Description | Field Type |
|---|---|---|---|
| "UUID.subType" | uuid | Unique identifier of a response message | Required |
processorId | Logical processor id 0,1,2 of the container | Required | |
| deploymentId | Unique identifier for a deployment | Required | |
| subType | Type of message here: ContainerPlacementResponseMessage | Required | |
| destinationHost | Destination host where the container is desired to be moved | Required | |
| statusCode | Status of the current action | Required | |
| responseMessage | Response message in conjunction to status | Required | |
| timestamp | The timestamp of the response message | Required | |
| requestExpiry | Eequest expiry which acts as a timeout for any resource request to cluster resource manager | Optional |
Sample KV
| Key | Value |
|---|---|
[1,"samza-place-container-v1","f068175b-c9b6-4f34-982b-ecb5619f21de.ContainerPlacementRequestMessage"] | {"processorId":"1","deploymentId":"app-atttempt-001","subType":"ContainerPlacementRequestMessage","uuid":"f068175b-c9b6-4f34-982b-ecb5619f21de","destinationHost":"ANY_HOST","statusCode":"CREATED","timestamp":1578693870484} |
ContainerPlacementResponseMessage:
...
- 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 the metastore
- Request / response message can be externally cleaned by a tool
...