anchor.diff:      "PzdyMZGXQdGhqTJHF_hGgA" : {
         "node_name" : "node3",
         "node_attributes" : { },
  +      "store" : {
  +        "shard_copy" : "NONE"
  +      },
         "final_decision" : "NO",
  +      "final_explanation" : "the shard cannot be assigned because one or more allocation decider returns a 'NO' decision",
         "weight" : 2.3166666,
         "decisions" : [ {
           "decider" : "filter",
  
positive.code: }
  --------------------------------------------------
  <1> Node the shard is currently assigned to
  <2> The decision is "CURRENTLY_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:
  
negative.code:   },
    "assigned" : true,
    "assigned_node_id" : "Qc6VL8c5RWaw1qXZ0Rg57g",      <1>
    "allocation_delay_ms" : 0,
    "remaining_delay_ms" : 0,
    "nodes" : {
      "V-Spi0AyRZ6ZvKbaI3691w" : {
        "node_name" : "Susan Storm",
        "node_attributes" : {
          "bar" : "baz"
        },
        "store" : {
          "shard_copy" : "NONE"
        },
        "final_decision" : "NO",
        "final_explanation" : "the shard cannot be assigned because one or more allocation decider returns a 'NO' decision",
        "weight" : 1.4499999,
        "decisions" : [ {
          "decider" : "filter",
  