Graylog2 / Graylog2/graylog2-server

Index Range lost when index is closed

Open
#1,975 3 comments 0 reactions 0 assignees View on GitHub
improvement Low Prio search to-verify
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

### Problem description

When an index is closed, there is no index range available anymore afterwards. This makes it hard for users to determine, which "historic" index they need to reopen to have data for a specific time range available again.

A proposed solution would be to merge old index ranges into newly calculated ones for closed indices, to keep old index ranges for closed indices (which should not change anymore) around.
### Steps to reproduce the problem
1. Go to indices page on web interface
2. Close an arbitrary index
3. See that "Time range of index is unknown, because index range is not available. Please recalculate index ranges manually."

Optional:
4. Click Maintenance -> Recalculate Index Ranges
5. See that nothing changes
### Environment
- Graylog Version: Graylog 2.0.0-beta.2-SNAPSHOT (9c0846cf71b96735239488523d8f65863c219145e)
- Elasticsearch Version:
- MongoDB Version:
- Operating System:
- Browser version:

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.