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

I was fine before, but suddenly there was an error message #1474

Open
ysq5202121 opened this issue Dec 21, 2023 · 4 comments
Open

I was fine before, but suddenly there was an error message #1474

ysq5202121 opened this issue Dec 21, 2023 · 4 comments

Comments

@ysq5202121
Copy link

Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 409 from: POST /prod-stacks/_update/658199c3faa36116cce8a02a. ServerError: Type: version_conflict_engine_exception Reason: "[658199c3faa36116cce8a02a]: version conflict, required seqNo [126049116], primary term [69]. current document has seqNo [126120946] and primary term [69]"
image

@niemyjski
Copy link
Member

niemyjski commented Dec 22, 2023

How many jobs do you have running in parallel? Looking at this code it does get retried once and it's for stack usage. It also happens via a script update to stack. What does your elasticsearch cpu usage look like?

@ysq5202121
Copy link
Author

ysq5202121 commented Dec 25, 2023

Two assignments,elasticsearch normal

@niemyjski
Copy link
Member

So you have two jobs running in parallel? Is there high usage for a given error occurrence. What does your elasticsearch cpu usage look like?

@ysq5202121
Copy link
Author

There are two ways to speed up the execution of assignments, as sometimes they may fail

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants