anomaly-detection-dashboards-plugin icon indicating copy to clipboard operation
anomaly-detection-dashboards-plugin copied to clipboard

[BUG] HC detector falsely labeled as "initializing" instead of "running"

Open amitgalitz opened this issue 3 years ago • 0 comments

What is the bug? After restarting Opensearch backend and frontend high cardinality detectors will sometimes show as initializing instead of running. This doesn't happen in single entity detectors and doesn't always happen for all running high cardinality detectors. However when using Profile API for the relevant detector is shown as "running".

How can one reproduce the bug? Steps to reproduce the behavior:

  1. Start Opensearch cluster and Opensearch Dashboards
  2. Create HCAD and wait for it to start running and displaying anomalies
  3. Stop Opensearch cluster and dashboard and then start cluster and dashboard again
  4. HCAD which was previously displayed as running now displays as initializing. This doesn't happen for single entity detectors and if you have multiple HCAD not all of them will go back to initializing
  5. HCAD will go back to running after receiving anomaly results

UPDATE: This also appears to sometimes happen when just restarting the backend cluster and detector starts initializing again.

What is the expected behavior? HCAD should show correctly as either running or initializing and shouldn't go back to showing as "initializing" after restarting backend and frontend for opensearch. Profile API correctly displays the detector as "running" so this is most likely a frontend issue. Will need to dive deeper into this.

What is your host/environment?

  • Running on Linux
  • Opensearch 2.0.0-alpha1-SNAPSHOT (4/12/22)

amitgalitz avatar Apr 13 '22 15:04 amitgalitz