MigrateJobRequest

AutoManager → Manager: initiate a migration. Phase E. The named job’s existing instance keeps its role; AutoManager launches a second instance on target_node_id with role="migrationTarget" and drives the four-step handshake. migration_id is generated by AutoManager and carried in lifecycle events so consumers can correlate.

Field

Type

Repeated

Description

job_id

JobId

target_node_id

NodeId

migration_id

string

Argument of

Method

Description

MigrateJob

Phase E — operator-initiated migration of a running job from its current node to a target node. AutoManager drives the protocol state machine; Manager is pure pass-through, routing cutover signals between source and target workers.