[BUG] Creating anomaly detector stucks at initializing state

[eslam-gomaa]

Describe the bug Hi I believe that this is not a bug, I'm just asking for guidance

When creating anomaly detector, it stuck at the initializing state for many days ! (some stuck for infinity) After a bit of investigation I found that this only happens when the index pattern used with the detector has very few events steam (due to the filter used with the detector)

Is there specific configuration I need to consider in my case ? 🤔

GET _opendistro/_anomaly_detection/detectors/vmwCWoEBNq3GYhZRwdMX/_profile?_all

{
  "state" : "INIT",
  "total_size_in_bytes" : 0,
  "init_progress" : {
    "percentage" : "0%",
    "estimated_minutes_left" : 256,
    "needed_shingles" : 128
  },
  "total_entities" : 911,
  "active_entities" : 0
}

To Reproduce Create an anomaly detectors on index pattern that has few events steam.

Expected behavior The detector to finish initialization successfully and becomes "running"

Plugins anomaly detection

GET _opendistro/_anomaly_detection/stats

{
  "anomaly_detectors_index_status" : "green",
  "anomaly_detection_state_status" : "green",
  "detector_count" : 19,
  "anomaly_detection_job_index_status" : "green",
  "models_checkpoint_index_status" : "green",
.....

Screenshots

sometimes to gets up to 2% and back to 0 again

Host/Environment (please complete the following information):

• AWS Opensearch service with Elasticsearch 7.10.2

---

If more information is needed pls let me know

Thanks in advance