-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault (core dumped) when adding GeoJSON polygon in Aerospike #172
Comments
Hi, Thanks for reporting this, we are looking into the causes of the issue. I've been able to reproduce this for versions up to 2.0.8 of the Python Client, but have been unable to reproduce it after that. Are you still experiencing it for the current version: 2.0.13 ? Is that stack trace from the Python Client version 2.0.5? Also if you could let us know what version of Python your are using it would be helpful. Thank you again for letting us know about the issue and sending the code which triggers the problem; it is very useful! |
1: The issue was happening in 2.0.13 also but not as consistent. |
Here is a stack trace from 2.0.13.
|
@aerospikerobertmarks Any fix for this? |
@anuranjita We believe that we have identified the issue, and will have a new release with a fix later today, or tomorrow. |
@anuranjit Version 2.1.0 of the Python client fixes that issue. If you continue to see it after that release please let us know. Thank you again for reporting the issue and providing the stack traces, and code examples. |
I am getting Segmentation fault (core dumped) when i am trying to put GeoJSON in aerospike in persistent namspace. It happens very frequently.
I also create an Index on the bbox field.
Below is the sample code ( This runs in a loop of 300000)
I am using aerospike server 3.8.3 There is no error in aerospike log. This just fails without any error information.
{'city': 1L, 'max_lng': 12.66811406299999, 'min_lng': 77.229080252800131, 'bbox': '{"type": "Polygon", "coordinates": [[[77.229080252800131, 12.66811406299999], [77.239080252800136, 12.66811406299999], [77.239080252800136, 12.65811406299999], [77.229080252800131, 12.65811406299999], [77.229080252800131, 12.66811406299999]]]}', 'max_lat': 12.66811406299999, 'min_lat': 12.65811406299999, 'col': 26, 'row': 46}
This is the bin for which it crashes (client)
If I limit the float precision to 6 decimal places it works.
Using python client version 2.0.5
GDB stack trace
The text was updated successfully, but these errors were encountered: