-
Notifications
You must be signed in to change notification settings - Fork 574
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
Tile38 unable to write and getting crash #747
Comments
What do you mean "high writes for location"? Do you happen to be writing lots of points to the same coordinates? |
Sometimes yes, but number of location write to tile38 is high (writing lots of points) to db. How & why will that cause an issue ? |
Its been noted before that if you put tons of points at the same coordinates (ex, 0,0) it causes an imbalance in the internal indexing in tile38 that causes performance to degrade dramatically and eventually crash. Solution is to just not use placeholder coordinates in most cases. |
Okay but I am a bit confused, Am I bound to get this issue even if this is done for different entities, which each has its own coordinate but that gets written multiple times |
Describe the bug
Tile 38 logs ->
To Reproduce
High writes for locations to database
Expected behavior
I expected it to handle all these writes and not give this following error in tile38 client ->
Code in client ->
Operating System (please complete the following information):
Additional context
What should be my next step to fix this.
On restart it starting working as expected again as I got these logs ->
Looks like the connection is not closing ?
The text was updated successfully, but these errors were encountered: