kibana/config
Tim Sullivan 03da0c92a4
[8.14] [Reporting/CSV] Resolve max_concurrent_shard_requests issue (#182536) (#182742)
# Backport

This will backport the following commits from `main` to `8.14`:
- [[Reporting/CSV] Resolve max_concurrent_shard_requests issue
(#182536)](https://github.com/elastic/kibana/pull/182536)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Tim
Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-05-03T14:30:45Z","message":"[Reporting/CSV]
Resolve max_concurrent_shard_requests issue (#182536)\n\n##
Summary\r\n\r\nThere has been a consistent failure in a Discover-related
test set in\r\nthe kibana-ES-serverless verification job, meaning that
ES-Kibana\r\ncompatibility has drifted.\r\n\r\nError details:\r\n```\r\n
+ \"Encountered an unknown error: status_exception\r\n + \tRoot
causes:\r\n + \t\tstatus_exception: Parameter validation failed for
[/_search]: The http parameter [max_concurrent_shard_requests] (with
value [5]) is not permitted when running in serverless mode\"\r\n +
\"Encountered an error with the number of CSV rows generated fromthe
search: expected rows were indeterminable, received 0.\"\r\n at
Context.<anonymous> (reporting.ts:182:33)\r\n at
processTicksAndRejections (node:internal/process/task_queues:95:5)\r\n
at Object.apply (wrap_function.js:73:16)\r\n```\r\n\r\nThis tracked back
to a feature added for reporting awhile back, which\r\ncreated a config
schema field for the `max_concurrent_shard_requests`\r\nparameter in the
search
queries:\r\nhttps://github.com/elastic/kibana/pull/170344/files#diff-7bceb37eef3761e1161cf04f41668dd9195bfac9fea36e734a230b5ed878a974\r\n\r\nMost
of the changes in this PR are in test code. I created \"Test\"
which\r\nextend protected methods in the original classes. This was done
to\r\nremove the `@ts-expect-errors` lines of
code.","sha":"f51c5c92bcc13686119ddf215eaa083ffac8e517","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Feature:Reporting","release_note:skip","backport:skip","Team:SharedUX","v8.15.0"],"number":182536,"url":"https://github.com/elastic/kibana/pull/182536","mergeCommit":{"message":"[Reporting/CSV]
Resolve max_concurrent_shard_requests issue (#182536)\n\n##
Summary\r\n\r\nThere has been a consistent failure in a Discover-related
test set in\r\nthe kibana-ES-serverless verification job, meaning that
ES-Kibana\r\ncompatibility has drifted.\r\n\r\nError details:\r\n```\r\n
+ \"Encountered an unknown error: status_exception\r\n + \tRoot
causes:\r\n + \t\tstatus_exception: Parameter validation failed for
[/_search]: The http parameter [max_concurrent_shard_requests] (with
value [5]) is not permitted when running in serverless mode\"\r\n +
\"Encountered an error with the number of CSV rows generated fromthe
search: expected rows were indeterminable, received 0.\"\r\n at
Context.<anonymous> (reporting.ts:182:33)\r\n at
processTicksAndRejections (node:internal/process/task_queues:95:5)\r\n
at Object.apply (wrap_function.js:73:16)\r\n```\r\n\r\nThis tracked back
to a feature added for reporting awhile back, which\r\ncreated a config
schema field for the `max_concurrent_shard_requests`\r\nparameter in the
search
queries:\r\nhttps://github.com/elastic/kibana/pull/170344/files#diff-7bceb37eef3761e1161cf04f41668dd9195bfac9fea36e734a230b5ed878a974\r\n\r\nMost
of the changes in this PR are in test code. I created \"Test\"
which\r\nextend protected methods in the original classes. This was done
to\r\nremove the `@ts-expect-errors` lines of
code.","sha":"f51c5c92bcc13686119ddf215eaa083ffac8e517"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.15.0","labelRegex":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/182536","number":182536,"mergeCommit":{"message":"[Reporting/CSV]
Resolve max_concurrent_shard_requests issue (#182536)\n\n##
Summary\r\n\r\nThere has been a consistent failure in a Discover-related
test set in\r\nthe kibana-ES-serverless verification job, meaning that
ES-Kibana\r\ncompatibility has drifted.\r\n\r\nError details:\r\n```\r\n
+ \"Encountered an unknown error: status_exception\r\n + \tRoot
causes:\r\n + \t\tstatus_exception: Parameter validation failed for
[/_search]: The http parameter [max_concurrent_shard_requests] (with
value [5]) is not permitted when running in serverless mode\"\r\n +
\"Encountered an error with the number of CSV rows generated fromthe
search: expected rows were indeterminable, received 0.\"\r\n at
Context.<anonymous> (reporting.ts:182:33)\r\n at
processTicksAndRejections (node:internal/process/task_queues:95:5)\r\n
at Object.apply (wrap_function.js:73:16)\r\n```\r\n\r\nThis tracked back
to a feature added for reporting awhile back, which\r\ncreated a config
schema field for the `max_concurrent_shard_requests`\r\nparameter in the
search
queries:\r\nhttps://github.com/elastic/kibana/pull/170344/files#diff-7bceb37eef3761e1161cf04f41668dd9195bfac9fea36e734a230b5ed878a974\r\n\r\nMost
of the changes in this PR are in test code. I created \"Test\"
which\r\nextend protected methods in the original classes. This was done
to\r\nremove the `@ts-expect-errors` lines of
code.","sha":"f51c5c92bcc13686119ddf215eaa083ffac8e517"}}]}] BACKPORT-->
2024-05-07 16:14:16 -03:00
..
kibana.yml [browser logging] allow to configure root level (#176397) 2024-02-12 05:26:57 -07:00
node.options [node] Enable openssl legacy provider (#163190) 2023-08-30 11:51:10 -07:00
README.md Fix config stacking order (#158827) 2023-06-05 15:15:07 +02:00
serverless.es.yml [8.14] [Playground] Adding TECH PREVIEW badge for Playground (#182019) (#182065) 2024-04-29 18:40:06 -07:00
serverless.oblt.yml [Search] Introduced Notebooks view for console (#180400) 2024-04-15 11:10:28 -05:00
serverless.security.yml [8.14] [Security Solution] - Security solution ES|QL configurable via advanced setting (#181616) (#182517) 2024-05-02 14:46:12 -07:00
serverless.yml [8.14] [Reporting/CSV] Resolve max_concurrent_shard_requests issue (#182536) (#182742) 2024-05-07 16:14:16 -03:00

as work on serverless picks up we will add config values to these files that define how Kibana will run in "serverless" modes. To start Kibana locally with this configuration, pass --serverless={mode} or run yarn serverless-{mode}

valid modes are currently: es, oblt, and security

configuration is applied in the following order, later values override

  1. serverless.yml (serverless configs go first)
  2. serverless.{mode}.yml (serverless configs go first)
  3. base config, in this preference order:
  • my-config.yml(s) (set by --config)
  • env-config.yml (described by env.KBN_CONFIG_PATHS)
  • kibana.yml (default @ env.KBN_PATH_CONF/kibana.yml)
  1. kibana.dev.yml
  2. serverless.dev.yml
  3. serverless.{mode}.dev.yml