You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@pekko.apache.org by "gindex (via GitHub)" <gi...@apache.org> on 2025/03/14 20:52:15 UTC
[I] [Question] Retry behavior [pekko-persistence-dynamodb]
gindex opened a new issue, #206:
URL: https://github.com/apache/pekko-persistence-dynamodb/issues/206
The plugin implements a [retry bahavior](https://github.com/apache/pekko-persistence-dynamodb/blob/72a20e80451a4666d8623458025bd2f049c02942/src/main/scala/org/apache/pekko/persistence/dynamodb/journal/DynamoDBHelper.scala#L40-L64) in case of some retryable errors (e.g. 5xx, trotteling).
AWS SDK itself supports retry behavior and per default DynamoDB client uses `LEGACY` retry mode with 3 attempts (sdk version `1.12.782`) on numerous exceptions as 5xx errors, throtteling errors, 429, clock skew exceptions and io exceptions.
Could you please help to understand the reason for the need for custom retry behavior on top of the existing AWS SDK retry behavior, which results in retries of retries? Can the configurable AWS SDK retry behavior be extended to support the use case instead of custom retry implementation?
Small sample how the SDK can be configured in case the defaults does not work:
```scala
val config = new ClientConfiguration
val retryBuilder = RetryPolicy.builder()
retryBuilder.setMaxErrorRetry(10)
retryBuilder.setBackoffStrategy(new FullJitterBackoffStrategy(100, 20000))
retryBuilder.setRetryMode(RetryMode.STANDARD)
retryBuilder.setRetryCondition(new SDKDefaultRetryCondition())
config.setRetryPolicy(
retryBuilder.build()
)
```
AWS Retry [documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/retry-strategy.html), unfortunalty It's mostly referring to 2.x SDK version. However, the behavior can be checked in SDK code.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] [Question] Retry behavior [pekko-persistence-dynamodb]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #206:
URL: https://github.com/apache/pekko-persistence-dynamodb/issues/206#issuecomment-2725802515
I'm not sure about the design decisions. The implementors of this module are not very active in the Pekko community at this point. I guess the implementation as is suited their use cases. This is not a widely used module afaics.
There is an alternative project - https://github.com/j5ik2o/pekko-persistence-dynamodb - that appears to use the newer AWS libs. It might be worth trying.
If you want to submit a PR, we would be happy to review it. The key thing is not to throw out the existing code but it would be feasible to support an option to ignore the #11 retry logic to use the AWS retry support instead.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] [Question] Retry behavior [pekko-persistence-dynamodb]
Posted by "gindex (via GitHub)" <gi...@apache.org>.
gindex closed issue #206: [Question] Retry behavior
URL: https://github.com/apache/pekko-persistence-dynamodb/issues/206
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] [Question] Retry behavior [pekko-persistence-dynamodb]
Posted by "gindex (via GitHub)" <gi...@apache.org>.
gindex commented on issue #206:
URL: https://github.com/apache/pekko-persistence-dynamodb/issues/206#issuecomment-2744139200
Thank you very much for the answer and the shred link! I will close this issue for now and in case of a contribution open a new one.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org