Our DAX got latent and context started getting deadline exceeded. Below is the message which we were logging in our server:
error ddb/de_entity_generic_get.go:99 couldn't get item {"id": "b1ace8e8-7f7a-4e44-af2a-4a4378ee1816", "table": "de-entity-map", "pk": "DE#9109356", "sk": "DE#9109356", "error": "RequestCanceled: request context canceled\ncaused by: context deadline exceeded”}
Breaking down the error log:
context deadline exceeded - This is received from DAX server
RequestCanceled: request context canceled - This is generated by aws-dax-go client.
We can see that the error log is misleading.
Description of changes:
ctx.Err() can return either Canceled or DeadlineExceeded, generating error message based on the error type.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Overview:
Our DAX got latent and context started getting deadline exceeded. Below is the message which we were logging in our server:
error ddb/de_entity_generic_get.go:99 couldn't get item {"id": "b1ace8e8-7f7a-4e44-af2a-4a4378ee1816", "table": "de-entity-map", "pk": "DE#9109356", "sk": "DE#9109356", "error": "RequestCanceled: request context canceled\ncaused by: context deadline exceeded”}Breaking down the error log:
context deadline exceeded- This is received from DAX serverRequestCanceled: request context canceled- This is generated by aws-dax-go client.We can see that the error log is misleading.
Description of changes:
ctx.Err() can return either
CanceledorDeadlineExceeded, generating error message based on the error type.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.