Azure-Samples / Azure-Samples/AnomalyDetector

InferenceLostConnection error for detect step with more than 5000 data points using Multivariate Anomaly Detection API in Python

Open
#48 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
110
Forks
161
PR merge metrics
No merged PRs in 30d

Description

> Please provide us with the following information:
> ---------------------------------------------------------------

### This issue is for a: (mark with an `x`)
```
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```

### Minimal steps to reproduce
When I submit more than 5,000 data points for the multivariate anomaly detector `detect` API call [https://{endpoint}/multivariate/models/{model_id}/detect](https://%7Bendpoint%7D/multivariate/models/%7bmodel_id%7d/detect)), I consistently get the following error. According to the documentation, the maximum number of data points per inference call is 20,000. There is no error when I use less than 5,000 data points for the API call.

Supplying at most 5,000 data points is much more time-consuming because any single detect API call takes around the same time to complete (regardless of the number of data points) in my experience.

### Any log messages given by the failure
> Error code: InferenceLostConnection. Message: Lost connection with the worker that processed the inference work. This may be caused by service upgrade. Re-trigger inference should help resolve this.

### Expected/desired behavior
> No error when I supply at most 20,000 data points for a single detect API call.

### Mention any other details that might be useful

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.