github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 17:59:23 -04:00
Code Issues Projects Releases Packages Wiki Activity

[Reporting/Docs] Add section to troubleshooting guide to explain the StatusCodeError logs (#102278) (#102412)

Browse source 
* [Reporting/Docs] Add section to troubleshooting guide to explain the StatusCodeError logs

* Update docs/user/reporting/reporting-troubleshooting.asciidoc

Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>

* use script formatting around error message block

Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>

Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
This commit is contained in:
Tim Sullivan 2021-06-16 14:05:18 -07:00 • committed by GitHub
parent 5f94276574
commit ae8a5fea35
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 26 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

26
docs/user/reporting/reporting-troubleshooting.asciidoc
View file

@ -91,6 +91,32 @@ the first time Kibana starts when verbose logging is enabled.
Whenever possible, a Reporting error message tries to be as self-explanatory as possible. Here are some error messages you might encounter,
along with the solution.
[float]
==== `StatusCodeError: [version_conflict_engine_exception]`
If you are running multiple instances of {kib} in a cluster, the instances share the work of executing report jobs to evenly distribute
the work load. Each instance searches the reporting index for "pending" jobs that the user has requested. It is possible for
multiple instances to find the same job in these searches. Only the instance that successfully updated the job status to
"processing" will actually execute the report job. The other instances that unsuccessfully tried to make the same update will log
something similar to this:
[source]
--------------------------------------------------------------------------------
StatusCodeError: [version_conflict_engine_exception] [...]: version conflict, required seqNo [6124], primary term [1]. current document has seqNo [6125] and primary term [1], with { ... }
status: 409,
displayName: 'Conflict',
path: '/.reporting-...',
body: {
error: {
type: 'version_conflict_engine_exception',
reason: '[...]: version conflict, required seqNo [6124], primary term [1]. current document has seqNo [6125] and primary term [1]',
},
},
statusCode: 409
}
--------------------------------------------------------------------------------
These messages alone don't indicate a problem. They show normal events that happen in a healthy system.
[float]
==== Max attempts reached
There are two primary causes of this error: