anchor.diff:  ---------------------------------------------------------------------------
   // TESTRESPONSE[non_json]
   
  -If a shard cannot be assigned, for example you've overallocated the
  -number of replicas for the number of nodes in the cluster, the shard
  -will remain `UNASSIGNED` with the <<reason-unassigned,reason code>> `ALLOCATION_FAILED`.
  -
  -You can use the shards API to find out that reason.
  +===== Example with reasons for unassigned shards
  +
  +The following request returns the `unassigned.reason` column, which indicates
  +why a shard is unassigned. 
  +
   
   [source,js]
   ---------------------------------------------------------------------------
  
positive.code: ---------------------------------------------------------------------------
  // TESTRESPONSE[non_json]
  
  [float]
  [[states]]
  ==== Shard states
  
  Before a shard can be used, it goes through an `INITIALIZING` state.
  `shards` can show you which ones.
  
  [source,js]
  ---------------------------------------------------------------------------
  
negative.code: // CONSOLE
  // TEST[setup:twitter]
  
  The API returns the following response:
  
  [source,txt]
  ---------------------------------------------------------------------------
  