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.

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

kibana use discover search 'error' occur error 'The content length (1026706026) is bigger than the maximum allowed string (536870888)' #173346

Closed
lishuaisky opened this issue Dec 14, 2023 · 3 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Search Querying infrastructure in Kibana Feature:Unified search Unified search related tasks feedback_needed Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph)
Projects

Comments

@lishuaisky
Copy link

**Kibana version: 7.17.8 7.17.15 7.17.16

**Elasticsearch version: 7.17.8

**Server OS version: aws linux 2023

**Browser version: chrome 119.0.6045.200 64 bit

**Browser OS version: window 11

**Original install method (e.g. download page, yum, from source, etc.): download
https://artifacts.elastic.co/downloads/kibana/kibana-7.17.8-linux-x86_64.tar.gz
https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.17.8-linux-x86_64.tar.gz
**Describe the bug:
In kibana discover UI,search 'error' keyword. it occur error 'The content length (1026706026) is bigger than the maximum allowed string (536870888)'. But search other keyword,such as 'info' 'warn', it works

Steps to reproduce:
1.Open kibana url in browser
2.launch discover and search 'error'
3. It occur error 'The content length (1026706026) is bigger than the maximum allowed string (536870888)'

**Expected behavior:
search works

Screenshots (if relevant):
屏幕截图 2023-12-14 113455

Errors in browser console (if relevant):
kibana-1702525043083.log

Provide logs and/or server output (if relevant):
elasticsearch and kibana have no error log
**Any additional context:
elasticsearch config:
cluster.name: es-log-cluster
node.name: log-es-node-1
path.data: /data/elasticsearch
path.logs: /var/log/elasticsearch
http.port: 9200
network.host: 0.0.0.0
discovery.zen.ping.unicast.hosts: ["log-es-node-1","log-es-node-2","log-es-node-3"]
cluster.initial_master_nodes: ["log-es-node-1","log-es-node-2","log-es-node-3"]
node.data: true
node.master: true
http.cors.enabled: true
http.cors.allow-origin: "*"
cluster.routing.allocation.enable: "all"
cluster.routing.rebalance.enable: "all"
cluster.routing.allocation.disk.watermark.high: "90%"
cluster.routing.allocation.disk.watermark.low: "85%"
ingest.geoip.downloader.enabled: false
path.repo: /data/es_snapshot
kibana config:
i18n.locale: "zh-CN"
migrations.batchSize: 100000
migrations.maxBatchSizeBytes: 1000000000
savedObjects.maxImportExportSize: 100000
savedObjects.maxImportPayloadBytes: 10000000000
server.maxPayload: 10000000000

@lishuaisky lishuaisky added the bug Fixes for quality problems that affect the customer experience label Dec 14, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Dec 14, 2023
@dej611 dej611 added Feature:Search Querying infrastructure in Kibana Feature:Unified search Unified search related tasks Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph) labels Dec 20, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 20, 2023
@kibanamachine kibanamachine added this to Inbox in Discover Dec 20, 2023
@jughosta
Copy link
Contributor

Most probably some of the documents, which match "error" query, have large field values.

Would it help to add such fields as "Field filter" from Stack Management > Index Patterns > "broker-server*" page ("Field filters" tab)? Then Discover would not request them.

@davismcphee
Copy link
Contributor

Thanks for reporting, but I'm going to close this issue since it isn't directly related to Discover and results from having very large field values in documents. The workaround suggested by @jughosta can be applied to filter out the oversized fields in Kibana, and should prevent the error from occurring in Discover.

Also linking to a related issue #98497, although it was put in our icebox for now as it seems unlikely we will make any changes related to this in the near term.

@davismcphee davismcphee closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Search Querying infrastructure in Kibana Feature:Unified search Unified search related tasks feedback_needed Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph)
Projects
No open projects
Development

No branches or pull requests

6 participants