jhipster-curator: Skipping action "delete_indices" due to empty list

[somejavadev]

Hi, I am running the jhipster stack in Kubernetes and have added the jhipster-curator as a sidecar container to run every 5 days to clean up my jhipster-elasticsearch-master to get rid of all the old entries on the logstash-* index. However when the cron job kicks off the following is displayed although I have indices older than 20 days. I have passed the environment variables: UNIT_COUNT as 5 and UNIT as days to my container

Preparing Action ID: 1, "delete_indices" 2018-08-01 08:26:19,774 INFO Trying Action ID: 1, "delete_indices": Delete indices older than ${UNIT_COUNT:1} ${UNIT:months} (based on index name), for logstash- prefixed indices. Ignore the error if the filter does not result in an actionable list of indices (ignore_empty_list) and exit cleanly. 2018-08-01 08:26:41,500 INFO Skipping action "delete_indices" due to empty list: <class 'curator.exceptions.NoIndices'> 2018-08-01 08:26:41,500 INFO Action ID: 1, "delete_indices" completed. 2018-08-01 08:26:41,500 INFO Preparing Action ID: 2, "delete_indices" 2018-08-01 08:26:41,512 INFO Trying Action ID: 2, "delete_indices": Delete indices older than ${UNIT_COUNT:1} ${UNIT:months} (based on index name), for zipkin- prefixed indices. Ignore the error if the filter does not result in an actionable list of indices (ignore_empty_list) and exit cleanly. 2018-08-01 08:26:53,489 INFO Skipping action "delete_indices" due to empty list: <class 'curator.exceptions.NoIndices'> 2018-08-01 08:26:53,490 INFO Action ID: 2, "delete_indices" completed. 2018-08-01 08:26:53,490 INFO Job completed.

Perhaps you could assist, I am using jhipster/jhipster-curator:v3.0.1 and jhipster/jhipster-elasticsearch:v3.0.1

Is this the correct way of specifying the time units? I can definitely see the logstash-* index exists as seen here in Kibana

Regards

[PierreBesson]

@somejavadev Can you confirm that the curator works well for you, and this issue is only to warn about the error message ?

[lmbai]

@somejavadev , the jhipster-curator will delete the logstash-* index and zipkin-* index too. in your case, i guess you don't have the zipkin-* index. that's why there is warn log......

@PierreBesson but, even with the zipkin-* index, the current curator will fail to delete it too due the name format issue.

yellow open .kibana             dgdAgEuyRvqfbmMcbuoVhg 5 1       30  4 118.2kb 118.2kb
yellow open elastalert_status   YTpHYvL4RZ60CaY2MInBdw 5 1   745150  0 200.2mb 200.2mb
yellow open logstash-2018.07.20 GcenODrTRAeYkHmz0xpoKA 5 1  9890986  0   3.9gb   3.9gb
yellow open logstash-2018.07.21 6znxyiX_RbyO3A0mCwYYrw 5 1  7579460  0     3gb     3gb
yellow open logstash-2018.07.22 s8Vi9IHMRPq-iSfVshDw_w 5 1  6252454  0   2.6gb   2.6gb
yellow open logstash-2018.07.23 tZl3WdmMTSuXGezu2-MuKg 5 1 18604128  0   6.7gb   6.7gb
yellow open logstash-2018.07.24 hMlxewk4SBa7yoJUsqB6Lg 5 1 22312329  0   7.6gb   7.6gb
yellow open logstash-2018.07.25 j8-ozKDjRWG79zlrVBP--g 5 1 23549610  0   8.2gb   8.2gb
yellow open logstash-2018.07.26 NpkYiSQFQLKoULMi4MGomg 5 1 30825793  0    11gb    11gb
yellow open logstash-2018.07.27 xuOD9olfSLyP5Iv0efDr4g 5 1 28835084  0   8.9gb   8.9gb
yellow open logstash-2018.07.28 2HH-Tx2CRyqzWH7DXUY7Dw 5 1 15299459  0   4.7gb   4.7gb
yellow open logstash-2018.07.29 GAwGEX_ZQXyWCLPFQRjN3w 5 1 14577551  0   4.6gb   4.6gb
yellow open logstash-2018.07.30 2R22BGSvQ6iri6NOI6wDrA 5 1 23181243  0   6.9gb   6.9gb
yellow open logstash-2018.07.31 _1LGjpEISByOPxVDlCImsQ 5 1 22872191  0   6.8gb   6.8gb
yellow open logstash-2018.08.01 ytC-IjxoQrabgLEmViqf7w 5 1 29451436  0   8.4gb   8.4gb
yellow open logstash-2018.08.02 yPfY7nuATmGD22d8YIHRlw 5 1 29008480  0   8.3gb   8.3gb
yellow open logstash-2018.08.03 r4bbRwJ5Q-KLmhbHGTW9lg 5 1 33993763  0   9.7gb   9.7gb
yellow open logstash-2018.08.04 8p2V8ed3RHSZ9p-2cz9c9Q 5 1 20971657  0   6.5gb   6.5gb
yellow open logstash-2018.08.05 MFfqJsgQTiSMeYm2Kg1dGA 5 1 14776195  0   4.6gb   4.6gb
yellow open logstash-2018.08.06 FO1RqfKFRcuEbXQFqqfT3w 5 1 33682980  0   9.6gb   9.6gb
yellow open logstash-2018.08.07 vY2P8rpVRMyl0tp7j82uGA 5 1 30025369  0   8.6gb   8.6gb
yellow open logstash-2018.08.08 W6q2w7PBQRGIHMvCEVV24g 5 1 27290497  0   7.9gb   7.9gb
yellow open logstash-2018.08.09 YFYUMP-zTFGVfIYooG7sSw 5 1 24906807  0   7.1gb   7.1gb
yellow open logstash-2018.08.10 0e85zMy6QYObvsaAiWPgOw 5 1  4257474  0   1.2gb   1.2gb
yellow open zipkin-2018-08-01   nnQ9cNQNRhejUtK5fMl2yA 5 1   281027 17    16mb    16mb
yellow open zipkin-2018-08-02   eAjyyV0VQR-ybMEtc-xkKQ 5 1   249138 22  14.4mb  14.4mb
yellow open zipkin-2018-08-03   udwLVfOBTEehA2QkNoPWhA 5 1   196426  6  11.4mb  11.4mb
yellow open zipkin-2018-08-04   uoaMrSWLTkWx0ij5M7_Crg 5 1   161442 11   9.5mb   9.5mb
yellow open zipkin-2018-08-05   Jou2lfO5SWWb4xdTkklINw 5 1   198559  8  11.5mb  11.5mb
yellow open zipkin-2018-08-06   A4MbvbWmS5inIlcANpSWiA 5 1   272576  5  15.6mb  15.6mb
yellow open zipkin-2018-08-07   0aNez8xbS6-nos7s0l1sWw 5 1   260404  4  14.9mb  14.9mb
yellow open zipkin-2018-08-08   xAqrYc_RR46rCHcP4ve8pg 5 1   244651  9  14.2mb  14.2mb
yellow open zipkin-2018-08-09   Laj9pMhAQA-Zz528j2uaSQ 5 1   221614 11  12.9mb  12.9mb
yellow open zipkin-2018-08-10   -OuAn4RzS1Kaa-MW5ukUsA 5 1    38649  8   2.4mb   2.4mb

99 will fix this.

[PierreBesson]

Fixed by#99

[somejavadev]

Excellent, thanks @PierreBesson @lmbai.