On 02/27/2018 03:05 PM, Eric Blake wrote: > On 02/23/2018 05:51 PM, John Snow wrote: >> For jobs utilizing the new manual workflow, we intend to prohibit >> them from modifying the block graph until the management layer provides >> an explicit ACK via block-job-finalize to move the process forward. >> >> To distinguish this runstate from "ready" or "waiting," we add a new >> "pending" event. >> >> For now, the transition from PENDING to CONCLUDED/ABORTING is automatic, >> but a future commit will add the explicit block-job-finalize step. >> >> Transitions: >> Waiting -> Pending: Normal transition. >> Pending -> Concluded: Normal transition. >> Pending -> Aborting: Late transactional failures and cancellations. >> >> Removed Transitions: >> Waiting -> Concluded: Jobs must go to PENDING first. >> >> Verbs: >> Cancel: Can be applied to a pending job. >> > >> +## >> +# @BLOCK_JOB_PENDING: >> +# >> +# Emitted when a block job is awaiting explicit authorization to >> finalize graph >> +# changes via @block-job-finalize. If this job is part of a >> transaction, it will >> +# not emit this event until the transaction has converged first. > > Same question of whether this new event is always emitted (and older > clients presumably ignore it), or only emitted for clients that > requested new-style state management. >
Old style jobs will skip the broadcast of the event, but will still transition to the state. However, since transition is synchronous, you likely won't see this state show up in a query for old style jobs. That was the intent, anyway. I wanted to be nonintrusive, and felt that this event was likely not useful in any way unless we were using the new state management scheme. In the old style, this event will be fully synchronous with COMPLETED or CANCELLED, for instance. --js
