How to delete only unassigned replica shard? many indices created automatically and my node goes down

ysunil702 · January 30, 2020, 5:58am

(1)Currently in my settings action.auto_create_index is true. if i will set to false so is it stop to create following indices?

(2)How to delete Unassigned replica shard?

Following indices are created automatically.

apm-7.3.1-span-000061           0 p STARTED
apm-7.3.1-span-000061           0 r UNASSIGNED
apm-7.3.1-error-000029          0 p STARTED
apm-7.3.1-error-000029          0 r UNASSIGNED
apm-7.3.1-error-000137          0 r STARTED
apm-7.3.1-error-000137          0 p STARTED
apm-7.3.1-span-000091           0 p STARTED
apm-7.3.1-span-000091           0 r UNASSIGNED
apm-7.3.1-span-000114           0 r STARTED
apm-7.3.1-span-000114           0 p STARTED
apm-7.3.1-error-000042          0 p STARTED
apm-7.3.1-error-000042          0 r UNASSIGNED
apm-7.3.1-error-000087          0 p STARTED
apm-7.3.1-error-000087          0 r UNASSIGNED
apm-7.3.1-transaction-000012    0 p STARTED
apm-7.3.1-transaction-000012    0 r UNASSIGNED
apm-7.3.1-error-000037          0 p STARTED
apm-7.3.1-error-000037          0 r UNASSIGNED
apm-7.3.1-span-000097           0 p STARTED
apm-7.3.1-span-000097           0 r STARTED
apm-7.3.1-error-000103          0 r STARTED
apm-7.3.1-error-000103          0 p STARTED
apm-7.3.1-error-000004          0 p STARTED
apm-7.3.1-error-000004          0 r UNASSIGNED
apm-7.3.1-error-000079          0 p STARTED
apm-7.3.1-error-000079          0 r STARTED
apm-7.3.1-span-000045           0 p STARTED
apm-7.3.1-span-000045           0 r UNASSIGNED
apm-7.3.1-metric-000004         0 p STARTED
apm-7.3.1-metric-000004         0 r UNASSIGNED
apm-7.3.1-span-000026           0 p STARTED
apm-7.3.1-span-000026           0 r UNASSIGNED
apm-7.3.1-error-000146          0 p STARTED
apm-7.3.1-error-000146          0 r UNASSIGNED
apm-7.3.1-transaction-000010    0 p STARTED
apm-7.3.1-transaction-000010    0 r UNASSIGNED
.monitoring-es-7-2020.01.30     0 p STARTED
.monitoring-es-7-2020.01.30     0 r UNASSIGNED
apm-7.3.1-span-000078           0 p STARTED
apm-7.3.1-span-000078           0 r UNASSIGNED
apm-7.3.1-error-000002          0 p STARTED
apm-7.3.1-error-000002          0 r UNASSIGNED
apm-7.3.1-error-000012          0 p STARTED
apm-7.3.1-error-000012          0 r UNASSIGNED
apm-7.3.1-transaction-000005    0 p STARTED
apm-7.3.1-transaction-000005    0 r UNASSIGNED
apm-7.3.1-metric-000016         0 r STARTED
apm-7.3.1-metric-000016         0 p STARTED
apm-7.3.1-metric-000009         0 p STARTED
apm-7.3.1-metric-000009         0 r UNASSIGNED
apm-7.3.1-span-000042           0 p STARTED
apm-7.3.1-span-000042           0 r UNASSIGNED
apm-7.3.1-metric-000011         0 p STARTED
apm-7.3.1-metric-000011         0 r UNASSIGNED
apm-7.3.1-span-000120           0 r STARTED
apm-7.3.1-span-000120           0 p STARTED
.monitoring-beats-7-2020.01.29  0 p STARTED
.monitoring-beats-7-2020.01.29  0 r UNASSIGNED
apm-7.3.1-span-000092           0 p STARTED
apm-7.3.1-span-000092           0 r UNASSIGNED
apm-7.3.1-span-000116           0 r STARTED
apm-7.3.1-span-000116           0 p STARTED
apm-7.3.1-span-000141           0 p STARTED
apm-7.3.1-span-000141           0 r UNASSIGNED
.kibana_task_manager            0 p STARTED
.kibana_task_manager            0 r UNASSIGNED
apm-7.3.1-error-000070          0 p STARTED
apm-7.3.1-error-000070          0 r STARTED
conversations                   1 p STARTED
conversations                   0 p STARTED
apm-7.3.1-transaction-000018    0 r STARTED
apm-7.3.1-transaction-000018    0 p STARTED
.monitoring-kibana-7-2020.01.29 0 p STARTED
.monitoring-kibana-7-2020.01.29 0 r UNASSIGNED
apm-7.3.1-metric-000018         0 p STARTED
apm-7.3.1-metric-000018         0 r UNASSIGNED
apm-7.3.1-span-000118           0 r STARTED
apm-7.3.1-span-000118           0 p STARTED
apm-7.3.1-error-000017          0 p STARTED
apm-7.3.1-error-000017          0 r UNASSIGNED
apm-7.3.1-error-000109          0 r STARTED
apm-7.3.1-error-000109          0 p STARTED
apm-7.3.1-error-000019          0 p STARTED
apm-7.3.1-error-000019          0 r UNASSIGNED
apm-7.3.1-span-000005           0 p STARTED
apm-7.3.1-span-000005           0 r UNASSIGNED
apm-7.3.1-error-000024          0 p STARTED
apm-7.3.1-error-000024          0 r UNASSIGNED
apm-7.3.1-span-000099           0 r STARTED
apm-7.3.1-span-000099           0 p STARTED
apm-7.3.1-span-000015           0 p STARTED
apm-7.3.1-span-000015           0 r UNASSIGNED
apm-7.3.1-error-000128          0 r STARTED
apm-7.3.1-error-000128          0 p STARTED
apm-7.3.1-span-000069           0 p STARTED
apm-7.3.1-span-000069           0 r UNASSIGNED
apm-7.3.1-span-000125           0 r STARTED
apm-7.3.1-span-000125           0 p STARTED
apm-7.3.1-error-000096          0 p STARTED
apm-7.3.1-error-000096          0 r UNASSIGNED
apm-7.3.1-span-000111           0 r STARTED
apm-7.3.1-span-000111           0 p STARTED
apm-7.3.1-span-000144           0 r STARTED

dadoonet · January 30, 2020, 6:10am

What is the output of:

GET /
GET /_cat/nodes?v
GET /_cat/health?v
GET /_cat/indices?v

If some outputs are too big, please share them on gist.github.com and link them here.

ysunil702 · January 30, 2020, 6:24am

gist.github.com

https://gist.github.com/ysunil702/ad6b6bcd2b94b208cc3c3804efa3b049

gistfile1.txt

GET /

{
  "cluster_name": "6cea47edc70143f2baf46d5bfedf81aa",
  "cluster_uuid": "kzLBcdOlQ6KO-xm8WUwgrg",
  "version": {
    "build_date": "2019-08-19T20:19:25.651794Z",
    "minimum_wire_compatibility_version": "6.8.0",
    "build_hash": "4749ba6",
    "number": "7.3.1",

This file has been truncated. show original

dadoonet · January 30, 2020, 7:06am

Lots of APM related shards here. I'm moving your question to #apm so experts can tell if it's expected.

If you are not really using APM, I'd drop the indices. Most of them are empty but they consume resources.
Reducing the replicas to 0 will fix the problem maybe but not for a long time.

ysunil702 · January 30, 2020, 7:32am

Thanks @dadoonet

(1)Yes, i am not use APM and i want to drop all APM related indices.
while i am going to delete APM it is give an error 'Sorry, looks like an error occurred'.

(2)If i am going to set "number_of_replicas" : 0 that time all shard of replicas state change unassigned to started but still that shard consume resources.

(3)Currently in my settings action.auto_create_index is true. if i will set to false so is it stop to create APM related indices?

(4)I want delete all indices except 'conversations' and 'last_async_date'. is it possible? if yes hows?

ysunil702 · January 31, 2020, 5:59am

I am waiting for reply...

system · February 28, 2020, 6:13am

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

Topic		Replies	Views
Unassigned replica Elasticsearch	9	2845	June 19, 2020
Problems with Number of replicas and UNASSIGNED errors Elastic Agent	10	345	October 3, 2023
Unassigned replica shards with reason as INDEX_CREATED Elasticsearch	5	9124	July 22, 2020
Deleting unassigned shard replicas Elasticsearch	5	567	June 22, 2020
Delete UNASSIGNED replica shards in elasticsearch 6.8.23 Elasticsearch docker	2	371	March 14, 2023

How to delete only unassigned replica shard? many indices created automatically and my node goes down

Related topics