anchor.diff:  // CONSOLE
   // TEST[setup:twitter]
   
  -The response of this request will be something like:
  +The API returns the following response:
   
   [source,txt]
   ---------------------------------------------------------------------------
  
positive.code: // TESTRESPONSE[s/13ms/[0-9.]+m?s/]
  // TESTRESPONSE[s/13/\\d+/ non_json]
  
  In the above case, the source and target nodes are the same because the recovery
  type was store, i.e. they were read from local storage on node start.
  
  Now let's see what a live recovery looks like. By increasing the replica count
  of our index and bringing another node online to host the replicas, we can see
  what a live shard recovery looks like.
  
  [source,js]
  ----------------------------------------------------------------------------
  
negative.code: // CONSOLE
  // TEST[skip:no need to execute snapshot/restore here]
  
  The API returns the following response with a recovery type of `snapshot`:
  
  [source,txt]
  --------------------------------------------------------------------------------
  i       s t      ty       st    rep     snap   f  fp   b     bp
  twitter 0 1978ms snapshot done  twitter snap_1 79 8.0% 12086 9.0%
  --------------------------------------------------------------------------------
  // TESTRESPONSE[non_json]