anchor.diff:  }
   --------------------------------------------------
   <1> Node the shard is currently assigned to
  -<2> The decision is "CURRENTLY_ASSIGNED" because the shard is currently assigned to this node
  +<2> The decision is "ALREADY_ASSIGNED" because the shard is currently assigned to this node
   
   You can also have Elasticsearch explain the allocation of the first unassigned
   shard it finds by sending an empty body, such as:
  
positive.code:         "bar" : "baz",
          "foo" : "bar"
        },
        "final_decision" : "NO",
        "weight" : -1.3833332,
        "decisions" : [ {
          "decider" : "same_shard",
  
negative.code:         "bar" : "baz",
          "foo" : "bar"
        },
        "store" : {
          "shard_copy" : "AVAILABLE"
        },
        "final_decision" : "ALREADY_ASSIGNED",        <2>
        "final_explanation" : "the shard is already assigned to this node",
        "weight" : 0.0,
        "decisions" : [ {
          "decider" : "same_shard",
  