You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are seeing an issue with hanging dynamo queries when using the ClusterDaxAsyncClient.
I do not have steps to reproduce or much in the way of specific additional information because we are still in the early stages of addressing this issue. It is fairly complex and difficult to isolate and reproduce. However I am not looking for specific help with this bug at this time. I am really just looking for some clarification here: is it possible that this bug we are facing, similar to the one seen in this older ticket, might be happening because the dax library is using an older dynamodb dependency?
Apparently, in order to use a dax cluster for dynamo queries in Java, one cannot just use the aws sdk. Instead one must use a largely (completely?) undocumented Amazon Dax Java Client, which I have found here: https://mvnrepository.com/artifact/software.amazon.dax/amazon-dax-client. The latest release for this library is 2.0.4, released a little over a year ago. There appears to be no documentation of any kind that I can see online for this client. However it appears that this library is using dynamoDB version 2.16.91, whereas the ticket above indicates that the hanging request issue was fixed in version 2.20.68.
Is there a better place to request help information on this issue, given that this dax library is not, for some reason, part of the aws sdk? Does anyone know if this dax library is still supported? Will it receive updates to use more recent versions of the sdk? Also, if someone knows where documentation for it might exist, I would be very grateful.
Expected Behavior
I'm not sure.
Current Behavior
Also not sure.
Reproduction Steps
Not currently sure.
Possible Solution
Boy, I sure wish I knew.
Additional Information/Context
No response
AWS Java SDK version used
2.25.63
JDK version used
Java 17, aws lambda
Operating System and version
Amazon Linux 2, the one used in aws lambda Java 17
The text was updated successfully, but these errors were encountered:
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Describe the bug
We are seeing an issue with hanging dynamo queries when using the ClusterDaxAsyncClient.
I do not have steps to reproduce or much in the way of specific additional information because we are still in the early stages of addressing this issue. It is fairly complex and difficult to isolate and reproduce. However I am not looking for specific help with this bug at this time. I am really just looking for some clarification here: is it possible that this bug we are facing, similar to the one seen in this older ticket, might be happening because the dax library is using an older dynamodb dependency?
#3652
Apparently, in order to use a dax cluster for dynamo queries in Java, one cannot just use the aws sdk. Instead one must use a largely (completely?) undocumented Amazon Dax Java Client, which I have found here: https://mvnrepository.com/artifact/software.amazon.dax/amazon-dax-client. The latest release for this library is 2.0.4, released a little over a year ago. There appears to be no documentation of any kind that I can see online for this client. However it appears that this library is using dynamoDB version 2.16.91, whereas the ticket above indicates that the hanging request issue was fixed in version 2.20.68.
Is there a better place to request help information on this issue, given that this dax library is not, for some reason, part of the aws sdk? Does anyone know if this dax library is still supported? Will it receive updates to use more recent versions of the sdk? Also, if someone knows where documentation for it might exist, I would be very grateful.
Expected Behavior
I'm not sure.
Current Behavior
Also not sure.
Reproduction Steps
Not currently sure.
Possible Solution
Boy, I sure wish I knew.
Additional Information/Context
No response
AWS Java SDK version used
2.25.63
JDK version used
Java 17, aws lambda
Operating System and version
Amazon Linux 2, the one used in aws lambda Java 17
The text was updated successfully, but these errors were encountered: