Page History

...

GET: http://{jm_rest_address:port}/blocklist

Request: {}

Response:

{
  /** This group only contains directly blocked task managers */
  "blockedTaskManagers": [
      {
          "id" : "container1",
          "action" : "MARK_BLOCKED",
          "startTimestamp" : "1652313600000",
          "endTimestamp" : "1652317200000",
          "cause" : "Hot machine"
      },
      {
          "id" : "container2",
          "action" : "MARK_BLOCKED_AND_EVACUATE_TASKS",
          "startTimestamp" : "1652315400000",
          "endTimestamp" : "1652319000000",
          "cause" : "No space left on device"
      }, 
      ...
  ],
  "blockedNodes": [
      {
          "id" : "node1",
          "action" : "MARK_BLOCKED",
          "startTimestamp" : "1652313600000",
          "endTimestamp" : "1652317200000",
          "cause" : "Hot machine",
          /** The task managers on this blocked node */
          "taskManagers" : ["container3", "container4"]
      },
      ...
  ]
} 

...

POST: http://{jm_rest_address:port}/blocklist/taskmanagers

Request

...

Code Block
title Request Example
{ [ { "id" : "node1/container1", "action" : "MARK_BLOCKED", "endTimestamp" : "1652317200000", "cause" : "Hot machine", "mergeOnConflict" : "true" }, { "id" : "node2/container2", "action" : "MARK_BLOCKED_AND_EVACUATE_TASKS", "timeout" : "3600000", "cause" : "No space left on device", }, ... ] }

...

}

Field meanings in requests:

1. id: A string value that specifies the identifier of the blocked task manager or node.
2. action: An enum value(MARK_BLOCKED or MARK_BLOCKED_AND_EVACUATE_TASKS) that specifies the block action when a task manager/node is marked as blocked.
3. timeout(optional): A long value that specifies the timeout (milliseconds).
4. endTimestamp(optional): A long value that specifies the unix timestamp(milliseconds) at which the item should be removed.cause: A string value that represents the cause for blocking this task manager or node. Note that only one of timeout and endTimestamp can be specified. If neither is specified, it means that the blocked item is permanent and will not be removed. If both are specified, will return error.
5. cause: A string value that specifies the cause for blocking this task manager or node.
6. mergeOnConflict(optional): A boolean value that specifies whether to merge when a conflict occurs. The default value is false. 

When trying to add a taskmanager or node, if the corresponding taskmanager/node already exists in blocklist, we propose to introduce two processing behaviors:

1. If mergeOnConflict is false, return error. 
2. If mergeOnConflict is true. The newly added item and the existing item will be merged into one. Regarding the 3 fields, the merging algorithm:
   1. For action, merge(MARK_BLOCKED, MARK_BLOCKED_AND_EVACUATE_TASKS) = MARK_BLOCKED_AND_EVACUATE_TASKS
   2. For endTimestamp, merge(endTimestampA, endTimestampB) = max(endTimestampA, endTimestampB)
   3. For cause, we will combine all causes, merge("causeA", "causeB") = "causeA,causeB"

Response

Remove

DELETE: http://{jm_rest_address:port}/blocklist/node/<id>

...