[SERVER-1629] Geospatial indexing Assertion error Created: 13/Aug/10 Updated: 30/Mar/12 Resolved: 25/Jan/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 1.6.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yu You | Assignee: | Greg Studer |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu X86-64, 2.6.31-16-server |
||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Participants: | |||||||||
| Description |
|
Server: running on a single local server node (mongod) To benchmark the geospatial indexing, I generated a collection containing 9M elements. The element contains randomly generated geo-coordinates (lat/long). ).limit(2) } } } The error happens when issuing the indexing command at the shell: ) for mrs.Content , name: "location_" } |
| Comments |
| Comment by Greg Studer [ 25/Jan/11 ] |
|
See duplication comment above. |
| Comment by Greg Studer [ 25/Jan/11 ] |
|
The default geospatial bounds are -180 to 180, and currently adding points at exactly the boundary limits is unsupported. The error telling you this isn't very helpful, however, as seen in |
| Comment by Aditya Gaur [ 20/Jan/11 ] |
|
I am running on Single server mode : mongod > db.locations.find() } } } } } } and following was the result when I tried to index the collection: ) The db.system.indexes also does not contain the entry for the created index and following was the log generated: Thu Jan 20 15:56:14 building new index on { coordinates: "2d" } for test.locations , name: "coordinates_" } Has this issue been resolved yet. If yes, please post the solution. |
| Comment by Chris Chandler [ 26/Nov/10 ] |
|
I'm also seeing this on the OS X build for 1.7.3 Fri Nov 26 16:00:22 [conn1] building new index on { geo: "2d" } for heater_development.points |