[Maps] GeoJSON upload fails

[consulthys]

Kibana version:
7.10.0

Elasticsearch version:
7.10.0

Server OS version:
Elastic Cloud

Browser version:
Chrome 89.0.4389.90

Browser OS version:
MacOS Sierra 10.13.6

Describe the bug:
Importing a GeoJSON file into a new map layer fails

Steps to reproduce:

1. Open the Maps application and create a new map
2. Add a new GeoJSON layer
3. Import the following file: https://opendata.arcgis.com/datasets/71cf6ef6467f42dfb87d4d68855e70ce_0.geojson (~14MB)

Expected behavior:
The GeoJSON file should be successfully imported since:

• it's valid
• it's less than 50MB
• the preview shows up correctly on the map

Screenshots (if relevant):
Just after dropping the file, the map displays all the geo points:

However, when clicking on "Import file", the file starts to upload and eventually fails. The right panel doesn't show anything anymore and there's an error in the console (see below)

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:
I tried on another Elastic Cloud deployment running 7.12.0, but I'm hitting a different issue (i.e. HTTP 408 Timeout error instead of HTTP 400)

[elasticmachine]

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

[consulthys]

Thanks for finally looking into this, however, just note that the GeoJSON file doesn't exist anymore. I've used another one and it still fails on 7.17.3, the map gets blank after a few percent into the import process.

[jsanz]

Sorry for missing this issue between the cracks and thanks @mbarretta for catching it 😓

@consulthys could you please update the issue description with a URL pointing to a problematic issue?

[consulthys]

@jsanz I don't know what more to describe here. You can try to upload any GeoJSON file that is a few MB large and you should see this happening, i.e. preview works, upload doesn't

[jsanz]

Just checked with a sample from the Geonames dataset, taking 190.000 features, just below the 100MB limit from Elastic Maps and imported without issues.

Also checked a smaller (34MB) completely different point dataset without isuses.

We really need a dataset that surfaces the error to work on the this issue.

[consulthys]

You can try this one and download the GeoJSON file:
https://hub.arcgis.com/datasets/CalEMA::wfigs-2022-wildland-fire-perimeters-to-date/explore?location=36.855523%2C-119.404277%2C7.00

[jsanz]

I've uploaded it from my browser (Chrome) to a deployment in Elastic Cloud with 7.17.5 without any issues.

I recreated the Index Pattern to select a temporal field and I could play with the dataset.

@nickpeihl do you see anything on the browser console screenshots that ring a bell?

[consulthys]

Thanks for trying it out @jsanz

On my end, it goes up to 4% and then I can see the following error in the Network tab

{"statusCode":408,"error":"Request Time-out","message":"Request Time-out"}

And the map goes blank

PS: Worth noting that the 7.17.3 cluster is not a small one (24 data nodes) and isn't overloaded right now.

[nreese]

This issue sounds like a duplicate of #72985. The original issue was fixed with #93678 which was merged into 7.13.0. The fix for cloud uploads was to chunk the file into 1MB pieces.

I wonder if the issue has more to due with connection speed and connecting to cloud. Maybe 1MB upload chuncking is still too large for poor connections.

[jsanz]

Just checked with a larger cluster (3 Elasticsearch, 3 Kibana) and worked well.

I then enabled the throttling feature on Chrome dev tools to simulate a slow connectivity and then I could replicate the issue so seems you are right @nreese

Tested the same dataset and throttling in 8.3.3 and got the same behavior with a blank screen.

[nreese]

I have opened #139760 to address the issue.

The solution works well for files with small to medium features. However, the solution does not resolve the problem for files with large features. It may never be possible to upload large features on a slow connection.