Detail
KB INCOMPLETE - DO NOT PUBLISH
When subscribed to Aerospike Client logging, you may see an error message which has been generated as a result of the client having some kind of issue performing a transaction. These error messages can be in slightly different formats depending on the exact client in use, but they all contain the same set of information
Answer
The following different types of errors can occur:
errMsg=Server timeout: iteration=1 socket=30000 total=0 maxRetries=0 node=A1 10.0.10.0 3000 inDoubt=true
errMsg=Error -8,1,30000,0,0,B1 10.0.10.0 3000: java.net.ConnectException: Connection refused (Connection refused)
errMsg=Error -8,1,30000,0,0,inDoubt,B1 10.0.10.0 3000: java.io.EOFException
errMsg=Error -8,1,30000,0,0,inDoubt,B1 10.0.10.0 3000: java.net.SocketException: Connection reset
As
- Error -8 - error code, where positive numbers mean server generated errors and negative numbers mean client generated errors. Server error codes here: https://aerospike.com/docs/database/reference/error-codes
- 1 - Iteration/attempt number
- 0 - Connection Timeout value (ms)
- 30000 - Socket Timeout value (ms)
- 1000 - Total Timeout value (ms)
- 2 - Max Retries configured
- inDoubt - Whether there is any doubt about data integrity on the node (i.e. we are unsure whether a write has happened)
- BB92D1CF40A0142 - Node ID of the node generating the error
- 10.244.28.45 - IP address of the node generating the error
- 3000 - Port of the node generating the error
- Client timeout - Text description of error
Notes
- Error 9,1,0,30000,1000,2,inDoubt,BB92D1CF40A0142 10.244.28.45 3000: Client timeout