anchor.diff:  Just like when setting it on the Reindex API, `requests_per_second`
   can be either `-1` to disable throttling or any decimal number
   like `1.7` or `12` to throttle to that level. Rethrottling that speeds up the
  -query takes effect immediately but rethrotting that slows down the query will
  -take effect on after completing the current batch. This prevents scroll
  +query takes effect immediately, but rethrottling that slows down the query will
  +take effect after completing the current batch. This prevents scroll
   timeouts.
   
   [float]
  
positive.code: [[docs-reindex-cancel-task-api]]
  === Works with the Cancel Task API
  
  Any Reindex can be canceled using the <<task-cancellation,Task Cancel API>>. For 
  example:
  
  [source,js]
  
negative.code: 
  In addition to the standard parameters like `pretty`, the Reindex API also
  supports `refresh`, `wait_for_completion`, `wait_for_active_shards`, `timeout`,
  `scroll`, and `requests_per_second`.
  
  Sending the `refresh` url parameter will cause all indexes to which the request
  wrote to be refreshed. This is different than the Index API's `refresh`
  