Restoring with wildcards in double-quoted strings does not succeed cleanly
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 627
- PR merge metrics
- No merged PRs in 30d
Description
## To submit a bug or report an issue
As requested, a new report for this issue.
I attempted to restore a days worth of logs by submitting a restore with ["index_*_2018.12.27"] as my list of indices. This should behave properly. However, It does the restore, but does not exit cleanly.
### Expected Behavior
All the indices with the name **index_<*anything that existed that day*>_2018.1227** would be restored and curator should exit.
### Actual Behavior
The indices are restored, but curator does not exit until it times out
### Steps to Reproduce the Problem
1. Attempt to restore an index with a wildcard in it. The index name must be enclosed in double quotes
1.Wait until the timeout period
1.Read the logs
### Specifications
- Version: ES 6.5.4, Curator 5.5.4
- Platform:Ubuntu
I have attached a sanitized snippet of the debug log which contains the last curator checkup on the restoration process and the final error.
[extract.txt](https://github.com/elastic/curator/files/2735289/extract.txt)
Contributor guide
Research direction
Start by reviewing the attached extract.txt debug log and reproducing the restore with the quoted wildcard index pattern on the stated Curator and Elasticsearch versions. Done means the matching indices are restored and Curator exits cleanly instead of timing out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100