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

(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

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.

1 Like

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.

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?

I am waiting for reply...

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