Stopping ES during initial indexing leaves orphaned indexes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Searchlight |
New
|
Undecided
|
Unassigned |
Bug Description
Need to determine if this is desired or not, but if you do not have any indexes created and start a bulk indexing job e.g.:
searchlight-manage index sync --force
Then in the middle of indexing stop elasticsearch, this will result in an error and leave orphaned index and aliases (-listener and -search).
Please note, that doing any recovery here is questionable (since ES is offline). I do wonder if there is anything we can do about this like tying into the orphaned-es-indexs [0] blueprint and publish information about starting an index job (e.g. into .searchlight index) at the beginning of a job and then doing something smart the next time it runs.
]0] https:/
Here is the error:
2016-05-16 10:55:08.763 CRITICAL searchlight [^[[00;36m-] ^[[01;35mConnec
^[[00m
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m File "/Users/
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m sys.exit(main())
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m File "/Users/
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m return CONF.command.
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m File "/Users/
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m plugin_
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m File "/Users/
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m self.setup_
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m File "/Users/
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m index=index)
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m File "/Users/
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m actions=
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m File "/Users/
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m for ok, item in streaming_
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m File "/Users/
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m for result in _process_
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m File "/Users/
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m raise e
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^
2016-05-16 10:55:08.763 TRACE searchlight ^[[01;35m^[[00m
description: | updated |
Has this been resolved?