Comment 3 for bug 1557003

From: https://review.openstack.org/#/c/277860/12/searchlight/cmd/manage.py

If there are any error in any of the processing anywhere along here, there is no cleanup logic. The indexes will continue to exist and be part of the alias, meaning the listeners will be populating outdated indexes from now until somebody happens to notice.
Just in my testing with stopping and starting at breakpoints a few times, i ended up with multiple dead indices.

I guess this can be handled in the following bug (but this will require discussion):

https://bugs.launchpad.net/searchlight/+bug/1557003

E.g. GET searchlight-listener/_status
 {
   "_shards": {
      "total": 30,
      "successful": 15,
      "failed": 0
   },
   "indices": {
      "searchlight-2016_03_14_18_14_12": {
      },
      "searchlight-2016_03_14_16_39_01": {
      },
      "searchlight-2016_03_14_18_12_06": {
         }
      }
   }
 }