-
Notifications
You must be signed in to change notification settings - Fork 199
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
Client v6 occasionally crushes with concurrent map read and map write #399
Comments
Thanks for your feedback, I've been working on it since yesterday. Can you provide a bit more information regarding your cluster? How many nodes do you have and what usually prompts the issue (nodes departing the cluster, etc.) |
Also, could you please paste the whole panic message so that I can see where the concurrent reads and writes are occurring? The current panic message does not include the part where the write is happening. |
Hi @khaf! Cluster: Here are all 4 aerospike-related goroutines from panic log
Below are two logs with some events and timestamps surrounding the crush
aerospike.log
|
Just a heads up that I think I have identified the root cause of this issue, and the potential fix is coming with the next release early next week. |
hi, @khaf! Could you give any updates, please? |
@Gaudeamus Sorry to have been unresponsive, I thought I had replied to you. I just don't know how I've managed to miss your message. We were dealing with a few other issues and releasing the Go client kind of fell of the cracks. I will release the fix this week. |
Sorry that this issue has fallen though the cracks. I just went through the client code, and it is not immediately clear to me how this issue can happen outside of constantly closing and opening a new client object. @Gaudeamus Are you creating a new |
Hello,
working with remote cluster on slow network I'm facing with a regular problem causing entire app to crush
client version v6.12.0
the same issue was with v5
The text was updated successfully, but these errors were encountered: