[Maps] Error seen in maps while uploading a geoJSON - Uncaught (in promise) TypeError: Invalid attempt to spread non-iterable instance

[rashmivkulkarni]

Kibana version: 7.6.2

Elasticsearch version: 7.6.2

Server OS version: Mac OSX

Browser version: Chrome latest

Browser OS version: NA

Original install method (e.g. download page, yum, from source, etc.): BC1 build of 7.6.2

Describe the bug: When uploading a geoJSON file in maps , encountered this error

commons.bundle.js:3 Uncaught (in promise) TypeError: Invalid attempt to spread non-iterable instance
    at _nonIterableSpread (commons.bundle.js:3)
    at _toConsumableArray (commons.bundle.js:3)
    at chunkDataAndWriteToIndex$ (commons.bundle.js:3)
    at s (kbn-ui-shared-deps.js:338)
    at Generator._invoke (kbn-ui-shared-deps.js:338)
    at Generator.forEach.e.<computed> [as next] (kbn-ui-shared-deps.js:338)
    at s (kbn-ui-shared-deps.js:338)
    at t (kbn-ui-shared-deps.js:338)
    at kbn-ui-shared-deps.js:338
_nonIterableSpread @ commons.bundle.js:3
_toConsumableArray @ commons.bundle.js:3
chunkDataAndWriteToIndex$ @ commons.bundle.js:3
s @ kbn-ui-shared-deps.js:338
(anonymous) @ kbn-ui-shared-deps.js:338
forEach.e.<computed> @ kbn-ui-shared-deps.js:338
s @ kbn-ui-shared-deps.js:338
t @ kbn-ui-shared-deps.js:338
(anonymous) @ kbn-ui-shared-deps.js:338

Steps to reproduce:

1. Deployed BC1 of 7.6.2 on cloud.
2. Navigated to Dashboard>create new dashboard> maps> upload geoJSON attached.
3. It took long time to upload ( unsuccessful) but gave an error in the console :
   as shown in screenshot.

This could be for various reasons, first being it is on cloud with default settings while spinning an instance

THIS DEPLOYMENT INCLUDES
2 × 1 GB RAM instances of aws.coordinating.m5
Optional
2 × 8 GB RAM / 240 GB storage instances of aws.data.highio.i3
3 × 1 GB RAM instances of aws.master.r4
Optional
1 × 1 GB RAM instance of aws.ml.m5
Optional
1 × 1 GB RAM instance of aws.kibana.r4
1 × 512 MB RAM instance of aws.apm.r4

or the big JSON file. ( renamed the JSON to txt file for gh to upload it)

burnsidetrees.geojson.txt

[rashmivkulkarni]

cc @aaronjcaldwell

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[kindsun]

Working with @Rasroh, I was able to reproduce this issue. The failure had the following characteristics:

• Occurred under higher memory load (other memory-consumptive apps running)
• Occurs during indexing stage
• Browser freezes before the error is created
• Error changed (race condition?) between when @Rasroh ran it and got a 504 and I ran it getting a 408
• An index was created, but the index pattern was not

I believe the issue is likely to be resolved by "consolidating the streaming logic", an optimization identified in #46376. Until this work is in place, it's somewhat rare, but clearly still possible to exhaust memory resources by uploading files under certain circumstances, such as low available memory.

[nreese]

closed by #92620