[LUCENE-5056] Indexing non-point shapes close to the poles doesn't scale

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.3
• Fix Version/s: 4.9, 6.0
• Component/s: modules/spatial
• Lucene Fields: New
• Assignee: David Smiley
• Reporter: Hal Deadman
• Created: 13/Jun/13 23:23
• Updated: 28/Aug/22 13:48

Description

From: hdeadman
We are seeing an issue where certain shapes are causing Solr to use up all available heap space when a record with one of those shapes is indexed. We were indexing polygons where we had the points going clockwise instead of counter-clockwise and the shape would be so large that we would run out of memory. We fixed those shapes but we are seeing this circle eat up about 700MB of memory before we get an OutOfMemory error (heap space) with a 1GB JVM heap.
Circle(3.0 90 d=0.0499542757922153)
Google Earth can't plot that circle either, maybe it is invalid or too close to the north pole due to the latitude of 90, but it would be nice if there was a way for shapes to be validated before they cause an OOM error.
The objects (4.5 million) are all GeohashPrefixTree$GhCell objects in an ArrayList owned by PrefixTreeStrategy$CellTokenStream.
Is there anyway to have a max number of cells in a shape before it is considered too large and is not indexed? Is there a geo library that could validate the shape as being reasonably sized and bounded before it is processed?
We are currently using Solr 4.1.
<fieldType name="location_rpt" class="solr.SpatialRecursivePrefixTreeFieldType"
spatialContextFactory="com.spatial4j.core.context.jts.JtsSpatialContextFactory"
geo="true" distErrPct="0.025" maxDistErr="0.000009" units="degrees" />

Issue Links

• is duplicated by: SOLR-5429 Point collapsed Rectangle at Poles resulting in GC OutOfMemory Exception