Aborting a Running File-Level Tiering Job

You can abort an ongoing offload or recall of a file using the CLI. Aborting a running:

  • Offload operation does not prevent future offloads; if a schedule is associated with the volume, data that is still on the cluster is automatically offloaded based on the rules as per schedule. You can also manually offload data again at any time by running the file offload or hadoop mfs command.
  • Recall operation does not prevent future recalls; you can run the recall command again to recall the remaining data on the tier. Based on the expiry time set on the volume (associated with the recalled data), recalled data is offloaded if there are changes or purged if there are no changes. See Recalling a Volume to filesystem for more information.

For information on aborting a running offload or recall operation using (loopbacknfs or FUSE-based) POSIX or NFS clients when maprcli or hadoop commands are not available, see Running Tiering Commands when maprcli and hadoop Commands are not Available. For information on aborting a running volume-level job, see Aborting a Running Volume-Level Tiering Job.

Aborting a Running File-Level Offload or Recall Operation Using the CLI and REST API

Run the following command to abort a currently running file-level offload or recall operation:
maprcli file tierjobabort -name <filePath>
For more information, see file tierjobabort.
Send a request of type POST. For example:
curl -k -X POST 'https://<host>:8443/rest/file/tierjobabort?name=<filePath>' --user mapr:mapr