Skip to content
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

[Transform] Transform config update conflict gets reported as ResourceAlreadyExistsException #96311

Closed
przemekwitek opened this issue May 24, 2023 · 1 comment · Fixed by #96293
Assignees
Labels
>bug :ml/Transform Transform Team:ML Meta label for the ML team

Comments

@przemekwitek
Copy link
Contributor

Elasticsearch Version

main

Installed Plugins

No response

Java Version

bundled

OS Version

MacOS

Problem Description

When there are 2 or more concurrent _update requests issued, one of them may fail with ResourceAlreadyExistsException exception which is misleading.

Steps to Reproduce

  1. Spawn a number of _update requests at the same time
  2. Look at the results of these requests
  3. Observe ResourceAlreadyExistsException being thrown in the case of conflict

Logs (if relevant)

No response

@przemekwitek przemekwitek self-assigned this May 24, 2023
@elasticsearchmachine elasticsearchmachine added the Team:ML Meta label for the ML team label May 24, 2023
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/ml-core (Team:ML)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :ml/Transform Transform Team:ML Meta label for the ML team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants