Closed yoori closed 4 years ago
On socket failure, the old connection is closed, set to NULL and a retry is signaled. A new change was made to wait one event loop iteration before executing retry. This means a timeout can occur between retry signal and actual retry. The regular connection timeout logic handles NULL connections, but the pipeline connection timeout logic does not.
We are investigating a fix.
C client 4.6.16 has been released:
https://www.aerospike.com/download/client/c/4.6.16/
Let us know if it fixes your crash.
C Library periodically crash on high load (50K rps) with stack:
At frame 0, cmd->conn is null pointer cmd variable content from other core file (with same stack):