The Job Manager maintains request ordering across the nodes in your Kinetica cluster at the cost of some performance. All read requests (/show/table, /get/records, etc.) are processed simultaneously. When a write request (/insert/records, /delete/records, etc.) is made, all subsequent read and write requests are blocked until the current write request is finished.
Because read requests are processed simultaneously, read jobs can only be cancelled while a preceding write request is being processed, which is also referred to as a checkpoint.
Insert, update, and delete requests cannot be cancelled. Otherwise, most user-facing non-admin jobs are cancellable.
When using any endpoint, you can specify a name, number, or other tag to help identify a particular job using the job_user_data options parameter; e.g., (in Python):