-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] "info deleteOldIndices" labeled as ERROR instead of INFO #1303
Comments
@opensearch-project/admin -- Can we please move this to opensearch-project/alerting? |
Just to add, it looks like this was resolved in this ticket here, but the backport to 2.x failed here and was never resolved: opensearch-project/security-analytics#534 |
Should be resolved now in opensearch-project/security-analytics#833 as this has been successfully merged and backported |
This issue was merged and backported in these PRs |
@jowg-amazon Even with OpenSearch 2.13 and 2.14 I get the same behavior. Is it possible that the bug still hasn't been fully fixed? |
There were two near-identical issues in different places in OpenSearch. The one at opensearch-project/security-analytics#203 was fixed and had the 'info deleteOldIndices' message printed in logs every 12 hours from 'o.o.s.i.DetectorIndexManagementService'. This is what has been merged and is in currently released OpenSearch versions. There was another source of the 'info deleteOldIndices' message from "o.o.a.a.AlertIndices". This is the one you reported and are still seeing. It has finally been successfully backported to 2.x as of #1230 so this error message should no longer be reported from OpenSearch 2.15! |
Thank you so much for the insight! |
Describe the bug
The official OpenSearch 2.11.0 docker container logs the following messages as ERROR messages:
To Reproduce
I have a pretty vanilla installation of OpenSearch 2.11.0 running in the official Docker image (deployed with Helm). Logging is configured to output in JSON:
Expected behavior
It should be logged as INFO.
The text was updated successfully, but these errors were encountered: