Graylog2 / Graylog2/graylog2-server

More control over shards and indices in elasticsearch

Open
#2,418 0 comments 0 reactions 0 assignees View on GitHub
feature triaged
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

### Problem description

Due to a space problem on one of my elasticsearch nodes the newly created next deflector index could not be allocated and the elasticsearch cluster went in status "red".

I had to use the elasticsearch api endpoints _cat/indices and _cat/shards to find the index/shards that elasticsearch was not able to assign and -XDELETE it. Plus, before deleting some older indices from the graylog server webinterface.

As graylog fully encapsulates the elasticsearch cluster, I wish I had a feature in the graylog webinterface to do such kind of work. Something like the marvel or kopf plugins for elasticsearch.
### Steps to reproduce the problem
1. write your cluster full and then get the deflector index cycled so unallocated shards will render the elasticsearch cluster red.
### Environment
- Graylog Version: 2.0.0
- Elasticsearch Version: latest
- MongoDB Version: latest
- Operating System: CentOS 7.1

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.