Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[Bug] [1.2.2] Search fails due to IndexClosedException #1533
When performing a query that crosses an index range with one or more closed indices, Graylog throws this exception. The easiest way to recreate this is to close any index and then perform a "Search in all messages" query.
added a commit
Nov 9, 2015
referenced this issue
Nov 9, 2015
I believe I noticed this as well with the update to 1.2.2 reverting back to MongoDB managed index ranges, so I'll add information here for my experience rather than opening a new issue:
I had a few reopened indices (and normally opened indices) that I closed manually prior to the index retention job by hitting a limit.
The ES indices closed and the Recalculate Range jobs triggered like normal, but the closed indices were still present in MongoDB in the index_ranges collection. When any search in that range happened, they were in the indices list to search, which triggered the index closed exception.
I had to go in manually and remove the closed indices from MongoDB's index_ranges collection to fix.
(FYI indices were created prior to 1.2.1, some reopened during 1.2.1, all closed during 1.2.2).