anchor.diff:  
   `took`::
   
  -The number of milliseconds from start to end of the whole operation.
  +The total milliseconds the entire operation took.
   
   `timed_out`::
   
   This flag is set to `true` if any of the requests executed during the
  -reindex has timed out.
  +reindex timed out.
   
   `total`::
   
  
positive.code: --------------------------------------------------
  // CONSOLE
  
  But you don't like the name `flag` and want to replace it with `tag`.
  `_reindex` can create the other index for you:
  
  [source,js]
  
negative.code: shards to become available. Both work exactly how they work in the
  <<docs-bulk,Bulk API>>. As `_reindex` uses scroll search, you can also specify
  the `scroll` parameter to control how long it keeps the "search context" alive,
  (e.g. `?scroll=10m`). The default value is 5 minutes.
  
  `requests_per_second` can be set to any positive decimal number (`1.4`, `6`,
  `1000`, etc) and throttles the rate at which `_reindex` issues batches of index
  operations by padding each batch with a wait time. The throttling can be
  disabled by setting `requests_per_second` to `-1`.
  
  The throttling is done by waiting between batches so that the `scroll` which `_reindex`
  uses internally can be given a timeout that takes into account the padding.
  The padding time is the difference between the batch size divided by the
  `requests_per_second` and the time spent writing. By default the batch size is
  