Skip to content

[6.x] bump reporting timeout (#20833) #21173

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

Merged
stacey-gammon merged 1 commit into from
Jul 25, 2018
Merged

[6.x] bump reporting timeout (#20833) #21173

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions docs/reporting/report-intervals.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,8 @@ takes to generate the reports--otherwise, the report queue can back up. To
avoid this, increase the time between report requests.

By default, report generation times out if the report cannot be generated
within 30 seconds. If you are generating reports that contain complex
within two minutes. If you are generating reports that contain many complex
visualizations or your machine is slow or under constant heavy load, it
might take longer than 30 seconds to generate a report. You can increase
might take longer than two minutes to generate a report. You can increase
the timeout by setting `xpack.reporting.queue.timeout` in `kibana.yml`.
===================
2 changes: 1 addition & 1 deletion docs/settings/reporting-settings.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ How often idle workers poll the index for pending jobs. Defaults to `3000` (3 se
`xpack.reporting.queue.timeout`::
How long each worker has to produce a report. If your machine is slow or under
heavy load, you might need to increase this timeout. Specified in milliseconds.
Defaults to `30000` (30 seconds).
Defaults to `120000` (two minutes).

[float]
[[reporting-capture-settings]]
Expand Down
2 changes: 1 addition & 1 deletion x-pack/plugins/reporting/index.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ export const reporting = (kibana) => {
indexInterval: Joi.string().default('week'),
pollInterval: Joi.number().integer().default(3000),
pollIntervalErrorMultiplier: Joi.number().integer().default(10),
timeout: Joi.number().integer().default(30000),
timeout: Joi.number().integer().default(120000),
}).default(),
capture: Joi.object({
record: Joi.boolean().default(false),
Expand Down
3 changes: 0 additions & 3 deletions x-pack/test/reporting/configs/chromium_api.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,6 @@ export default async function ({ readConfigFile }) {
serverArgs: [
...reportingApiConfig.kbnTestServer.serverArgs,
`--xpack.reporting.capture.browser.type=chromium`,
// Jenkins agents take about 30 seconds to spin up chromium on a first run because of some fontconfig cache
// generation.
`--xpack.reporting.queue.timeout=60000`,
`--logging.verbose=true`,
],
},
Expand Down
3 changes: 0 additions & 3 deletions x-pack/test/reporting/configs/chromium_functional.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,6 @@ export default async function ({ readConfigFile }) {
serverArgs: [
...functionalConfig.kbnTestServer.serverArgs,
`--xpack.reporting.capture.browser.type=chromium`,
// Jenkins agents take about 30 seconds to spin up chromium on a first run because of some fontconfig cache
// generation.
`--xpack.reporting.queue.timeout=60000`,
`--logging.verbose=true`,
],
},
Expand Down