Red cluster and don't come green all the night

(Ruslan Zaytsev) #1

Good day
I was install plugin yesterday. with manual about rolling upgrade i do next things:

PUT _cluster/settings
"transient": {
"cluster.routing.allocation.enable": "none"

POST _flush/synced

systemctl stop elasticsearch

/usr/share/elasticsearch/bin/elasticsearch-plugin install repository-s3

systemctl start elasticsearch

curl -XPUT localhost:9322/_cluster/settings -d '{
"transient": {
"cluster.routing.allocation.enable": "all"

Before all i do { "number_of_replicas" :0 } due to lack of space.

Now i have:

"version" : {
"number" : "5.0.0",
"build_hash" : "253032b",
"build_date" : "2016-10-26T04:37:51.531Z",
"build_snapshot" : false,
"lucene_version" : "6.2.0"

cluster           status shards  pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
backup-itest01log red             4         3   3355 3348    0    0      783             0                  -                 81.1%

heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name
          60          82   6    1.01    0.47     0.28 -         -      kibana01
          18          86   9    0.50    0.66     1.00 mdi       -      node02
          56          88   8    0.04    0.40     0.81 mdi       *      node01
          22          91   9    0.15    0.40     0.71 mdi       -      node03

shards disk.indices disk.used disk.avail disk.percent  node
  1118      592.9gb     935gb    813.2gb      1.7tb           53  node02
  1119      629.9gb     723gb        1tb      1.7tb           41  node01
  1118      631.5gb   964.8gb    783.4gb      1.7tb           55  node03
   783                                                            UNASSIGNED

And it dont't change all the night. node01(master) and client node(kibana01) i don't touch yet. only node02 and 03

Help me please!

(Ruslan Zaytsev) #2

for all unassigned nodes


(Ruslan Zaytsev) #3

May i somehow delete shard number 2 without data loss?

(Pjanzen) #4

If I am not mistaken you need to install repository-s3 on all ES nodes and restart the cluster.

Also if you delete that shard you will loose data (I think).

(Ruslan Zaytsev) #5

Thank you for answer!
i am afraid to restart master node due to red cluster.
and don't know how to assigne problematic shards

(Pjanzen) #6

I think when you look at the logs from elasticsearch you will find that ES cannot connect to each other due to config changes. You NEED to install the plugin on all ES nodes.

For the restart, the cluster is RED, the worst thing that can happen after a restart is the things start working...

As long as you do not do a rm -rf on any dir your data will be safe, it will be a bitch to recover but it will be there...

(Ruslan Zaytsev) #7

i delete some old indices, and turn on replicas. wait now for they assign to nodes, then will restart master node

(Ruslan Zaytsev) #8

plug-in on all nodes now. shards still unassigned

(system) #9

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.