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.

Sign up for GitHub

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

Jump to bottom

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

Merged
merged 3 commits into from
Jun 16, 2021
Merged

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

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c49f3a8
[Reporting/Docs] Add section to troubleshooting guide to explain the …
tsullivan Jun 15, 2021
fb9ff89
Update docs/user/reporting/reporting-troubleshooting.asciidoc
tsullivan Jun 16, 2021
18e36d8
use script formatting around error message block
tsullivan Jun 16, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions docs/user/reporting/reporting-troubleshooting.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,31 @@ 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 Kibana in a cluster, they share the work of executing report jobs to evenly distribute
tsullivan marked this conversation as resolved.
Show resolved Hide resolved
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:

```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use formatting here so that code is in a black box. See the section of this page called "Verbose logs" for an example.

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:
Expand Down