We have a few SDHs that seem to indicate that xpack.reporting.queue.pollEnabled is no longer working - setting it to false still allows reports to be generated.
As a work-around, you can exclude the task via task manager config:
xpack.task_manager.unsafe.exclude_task_types: ['report:execute']
I have a hunch this may be related to our change from the ubq task claimer to mget task claimer. Here's some code in reporting that sets task maxConcurrency:
|
protected getMaxConcurrency() { |
|
return this.opts.config.queue.pollEnabled ? 1 : 0; |
|
} |
|
|
So this sets the value to 0 (when the setting is false), which may be something the mget task claimer doesn't deal with correctly. As the author of that code many moons ago, I can believe it :-)
We have a few SDHs that seem to indicate that
xpack.reporting.queue.pollEnabledis no longer working - setting it tofalsestill allows reports to be generated.As a work-around, you can exclude the task via task manager config:
I have a hunch this may be related to our change from the ubq task claimer to mget task claimer. Here's some code in reporting that sets task maxConcurrency:
kibana/x-pack/platform/plugins/private/reporting/server/lib/tasks/run_report.ts
Lines 198 to 201 in 4de079d
So this sets the value to 0 (when the setting is false), which may be something the mget task claimer doesn't deal with correctly. As the author of that code many moons ago, I can believe it :-)