# Data Indices are recovery **URL:** \ **Category:** Kibana\ **Created:** [October 18, 2022, 12:27pm UTC](https://discuss.elastic.co/t/data-indices-are-recovery/316887 "2022-10-18T12:27:26Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Ravi\_S1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_s1/32/99235_2.png) [@Ravi\_S1](https://discuss.elastic.co/u/Ravi_S1)\ **Post date:** [October 18, 2022, 12:27pm UTC](https://discuss.elastic.co/t/data-indices-are-recovery/316887/1 "2022-10-18T12:27:26Z")
I would like to check with community on recovery state of indices... after upgrading the ELK stack to 8.4.1, i could see that data indices are recovering very often.. Is there any reason for this behavior. GET \_cat/recovery?v&h=t,ty,i,f,tnode,start,to&s=start:desc t ty i f tnode start to 745ms peer data\_catalogue\_dashboard 0 quickstart-es-data-nodes-1 2022-10-18T12:20:47.044Z 0 841ms peer catalogue\_for\_field\_level 0 quickstart-es-data-nodes-1 2022-10-18T12:20:46.914Z 0 1s peer ecommerce\_source 0 quickstart-es-data-nodes-1 2022-10-18T12:20:44.445Z 0 2.1s peer audit\_logs\_itg\_data 0 quickstart-es-data-nodes-1 2022-10-18T12:20:42.444Z 0 1.9s peer calculations-itg-todate-01 0 quickstart-es-data-nodes-1 2022-10-18T12:20:38.654Z 0 1.7s peer api\_performance\_itgdiagnostic\_logs 0 quickstart-es-data-nodes-1 2022-10-18T12:20:35.305Z 0 7.8s peer ccs\_count\_data\_index 0 quickstart-es-data-nodes-1 2022-10-18T12:20:35.202Z 0 1s peer ccs-hive-count-index 0 quickstart-es-data-nodes-1 2022-10-18T12:20:32.326Z 0 774ms peer cr\_service\_data\_src\_redis\_check 0 quickstart-es-data-nodes-1 2022-10-18T12:20:24.072Z 0 1s peer measurements-itg-aug 0 quickstart-es-data-nodes-1 2022-10-18T12:20:23.929Z 0 1.4s peer cr\_service\_completeness\_result\_redis\_check 0 quickstart-es-data-nodes-1 2022-10-18T12:20:20.440Z 0 448ms peer data\_catalogue\_dashboard 0 quickstart-es-data-nodes-2 2022-10-18T11:36:36.516Z 0 723ms peer catalogue\_for\_field\_level 0 quickstart-es-data-nodes-2 2022-10-18T11:36:33.195Z 0 610ms peer ecommerce\_source 0 quickstart-es-data-nodes-2 2022-10-18T11:36:33.098Z 0 1s peer audit\_logs\_itg\_data 0 quickstart-es-data-nodes-2 2022-10-18T11:36:29.828Z 0 640ms peer cr\_service\_data\_src 0 quickstart-es-data-nodes-2 2022-10-18T11:36:29.743Z 0 1.2s peer api\_performance\_itgdiagnostic\_logs 0 quickstart-es-data-nodes-2 2022-10-18T11:36:26.484Z 0 721ms peer ccsdataingestionapi-itg-2022.05.27 0 quickstart-es-data-nodes-2 2022-10-18T11:36:26.363Z 0 394ms peer metrics-endpoint.metadata\_current\_default 0 quickstart-es-data-nodes-2 2022-10-18T11:36:18.946Z 0 578ms peer measurements-itg-aug 0 quickstart-es-data-nodes-2 2022-10-18T11:36:15.884Z 0 472ms peer cr\_service\_completeness\_result\_redis\_check 0 quickstart-es-data-nodes-2 2022-10-18T11:36:13.554Z 0 1s peer catalogue\_for\_field\_level 0 quickstart-es-data-nodes-0 2022-10-18T11:21:08.918Z 0 454ms peer data\_catalogue\_dashboard 0 quickstart-es-data-nodes-0 2022-10-18T11:21:05.625Z 0 491ms peer ccsdataingestionapi-itg-2022.05.27 0 quickstart-es-data-nodes-0 2022-10-18T11:21:02.460Z 0 688ms peer cr\_service\_data\_src 0 quickstart-es-data-nodes-0 2022-10-18T11:21:02.374Z 0 802ms peer calculations-itg-todate-01 0 quickstart-es-data-nodes-0 2022-10-18T11:20:59.193Z 0 458ms peer cr\_service\_data\_src\_redis\_check 0 quickstart-es-data-nodes-0 2022-10-18T11:20:53.921Z 0 392ms peer metrics-endpoint.metadata\_current\_default 0 quickstart-es-data-nodes-0 2022-10-18T11:20:53.831Z 0 569ms existing\_store ccs\_count\_data\_index 0 quickstart-es-data-nodes-0 2022-10-18T11:20:39.218Z 0 516ms existing\_store ccs-hive-count-index 0 quickstart-es-data-nodes-0 2022-10-18T11:20:39.120Z 0 ---
**Author:** ![Ravi\_S1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_s1/32/99235_2.png) [@Ravi\_S1](https://discuss.elastic.co/u/Ravi_S1)\ **Post date:** [October 19, 2022, 5:03am UTC](https://discuss.elastic.co/t/data-indices-are-recovery/316887/2 "2022-10-19T05:03:09Z")
One key important information is, this cluster build out K8S environment and did not even see a single restart on each container level.. but still recoveries are happening each data node level.. quickstart-es-data-nodes-0 2/2 Running 0 4d3h quickstart-es-data-nodes-1 2/2 Running 0 4d3h quickstart-es-data-nodes-2 2/2 Running 0 4d3h quickstart-es-master-nodes-0 2/2 Running 0 4d3h quickstart-es-master-nodes-1 2/2 Running 0 4d3h quickstart-es-master-nodes-2 2/2 Running 0 4d3h ---
**Author:** ![drewdaemon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drewdaemon/32/97779_2.png) [@drewdaemon](https://discuss.elastic.co/u/drewdaemon)\ **Post date:** [October 19, 2022, 6:17pm UTC](https://discuss.elastic.co/t/data-indices-are-recovery/316887/3 "2022-10-19T18:17:06Z")
Hi @Ravi_S1 . From the logs it looks like this is something to do with your Elasticsearch nodes. Is there a reason you think this is related to Kibana? ---
**Author:** ![Ravi\_S1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_s1/32/99235_2.png) [@Ravi\_S1](https://discuss.elastic.co/u/Ravi_S1)\ **Post date:** [October 20, 2022, 2:08am UTC](https://discuss.elastic.co/t/data-indices-are-recovery/316887/4 "2022-10-20T02:08:40Z")
@drewdaemon, I feel not.. i am trying to apply some mitigation steps and will post the results. ---
**Author:** ![Ravi\_S1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_s1/32/99235_2.png) [@Ravi\_S1](https://discuss.elastic.co/u/Ravi_S1)\ **Post date:** [October 31, 2022, 5:55pm UTC](https://discuss.elastic.co/t/data-indices-are-recovery/316887/5 "2022-10-31T17:55:05Z")
@ [Andrew\_Tate](https://discuss.elastic.co/u/Andrew_Tate) Even i applied the following recovery steps.. but still i can find recoveries happen on data indices.. PUT \_cluster/settings{"transient":{"cluster.routing.allocation.node\_concurrent\_recoveries":3}} PUT \_all/\_settings{"settings":{"index.unassigned.node\_left.delayed\_timeout":"6m"}} PUT \_cluster/settings{"transient":{"indices.recovery.max\_bytes\_per\_sec":"100mb"}} And also all POD's are stable .. as per below quickstart-es-data-nodes-0 2/2 Running 0 17d quickstart-es-data-nodes-1 2/2 Running 0 17d quickstart-es-data-nodes-2 2/2 Running 0 17d quickstart-es-master-nodes-0 2/2 Running 0 17d quickstart-es-master-nodes-1 2/2 Running 0 17d quickstart-es-master-nodes-2 2/2 Running 0 17d Why indices are participating on recovery stage as below.. t ty i 1.7s peer ecommerce\_data\_src\_redis\_check 1.5s peer calculations-itg-todate-01 1.3s peer myacct\_orders\_service\_data\_src\_redis\_check 1.3s peer sc\_service\_data\_src\_redis\_check 1.3s peer sr\_service\_data\_src\_redis\_check 1.2s existing\_store ccs\_count\_data\_index 1.2s peer cr\_service\_data\_src\_redis\_check 1.2s peer api\_performance\_itgdiagnostic\_logs Do we need any specific configuration on recovery side that should stop recovery on data indices by default. ---
**Author:** ![Ravi\_S1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_s1/32/99235_2.png) [@Ravi\_S1](https://discuss.elastic.co/u/Ravi_S1)\ **Post date:** [November 8, 2022, 5:19am UTC](https://discuss.elastic.co/t/data-indices-are-recovery/316887/6 "2022-11-08T05:19:52Z")
Any data that required to be interested for us on this issue.. i am ready to provide.. any inputs will help us alot. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 6, 2022, 5:20am UTC](https://discuss.elastic.co/t/data-indices-are-recovery/316887/7 "2022-12-06T05:20:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.