elk11
September 30, 2019, 11:59am
1
Hi,
when i search for on an index pattern for data through discover tab, the browser waits for some time and then just crashes with 'Aw snap!' message. No error in either Kibana or Elasticsearch logs.
This is happening when i increased node js heap to 4GB to solve 'javaScript heap out of memory' error in Kibana logs.
Version: 7.3.1
The search on other index pattern seems to go through fine.
elk11
September 30, 2019, 12:11pm
2
And sometimes Kibana just restarts with following error in logs:
tusCode":200,"responseTime":130,"contentLength":9},"message":"POST /api/monitoring/v1/clusters/B80d8UrYSbypYhtxP38vBg/kibana 200 130ms - 9.0B"}
2019-09-30T12:07:45.555505118Z /usr/share/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:188
2019-09-30T12:07:45.555600816Z response += d;
2019-09-30T12:07:45.555616313Z ^
2019-09-30T12:07:45.555629390Z
2019-09-30T12:07:45.555642906Z RangeError: Invalid string length
2019-09-30T12:07:45.555656095Z at IncomingMessage.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:188:19)
2019-09-30T12:07:45.555672786Z at IncomingMessage.emit (events.js:189:13)
2019-09-30T12:07:45.555688128Z at addChunk (_stream_readable.js:284:12)
2019-09-30T12:07:45.555701346Z at readableAddChunk (_stream_readable.js:261:13)
2019-09-30T12:07:45.555715619Z at IncomingMessage.Readable.push (_stream_readable.js:220:10)
2019-09-30T12:07:45.555729647Z at HTTPParser.parserOnBody (_http_common.js:122:22)
2019-09-30T12:07:45.555852506Z at Socket.socketOnData (_http_client.js:442:20)
2019-09-30T12:07:45.555953753Z at Socket.emit (events.js:189:13)
2019-09-30T12:07:45.555969007Z at addChunk (_stream_readable.js:284:12)
2019-09-30T12:07:45.555983538Z at readableAddChunk (_stream_readable.js:265:11)
2019-09-30T12:07:45.555997629Z at Socket.Readable.push (_stream_readable.js:220:10)
2019-09-30T12:07:45.556011820Z at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
I'm confused. it shows 'timeout error' when this happends in Kibana UI.
elk11
September 30, 2019, 12:25pm
3
The above mentioned 'RangeError: Invalid string length' error is consistently occurring for a index pattern.
I have 'NODE_OPTIONS=--max_old_space_size=4096'
elk11
September 30, 2019, 1:08pm
4
I increased heap to 8GB. Still getting same error.
jbudz
(Jon Budzenski)
September 30, 2019, 10:12pm
5
Do you have any fields with extremely long strings? The discover page is fairly sensitive to rendering large amounts of data.
If that is the case we can truncate these or exclude them on the index patterns page.
elk11
October 1, 2019, 4:29pm
6
I did have a extremely long field. I added it to source filter in that index pattern. It seems to have fixed the issue. Thanks!
system
(system)
Closed
October 29, 2019, 4:29pm
7
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.