RetryOptions changed in new Java SDK release or a new bug introduced?

Community Support
,
1

Hello

With java sdk 1.17.0 below code fragment was leading to unlimited number of retries with the activity, however upgrading to 1.19.1 i see that has changed. Not declaring .setMaximumAttempts or declaring and setting it to zero doesn’t do any retries. Is that on purpose or is it a bug? If thats on purpose then javadoc needs updating because default is not unlimited then.

LocalActivityOptions.newBuilder()
.setRetryOptions(RetryOptions.newBuilder()
.setInitialInterval(Duration.ofMillis(250))
.setBackoffCoefficient(2.0)
.setMaximumInterval(Duration.ofSeconds(10))
.setDoNotRetry(IllegalArgumentException.class.getName())
.build())
.setStartToCloseTimeout(Duration.ofSeconds(10))
.build());

2

1.18.1 release did include a rework of local activities, from release note:

### Comprehensive rework of Local Activity Worker implementation

* Local Activities now respect all the timeouts set on `LocalActivityOptions`.
* Lower ScheduleToStart latencies for Local Activities and a backpressure that prefers retries over new executions
* `LocalActivityOptions` got `scheduleToStart` timeout
* Bugfix for OpenTelemetry/OpenTracing incorrectly showing exaggerated scheduleToStart latency for Local Activities ([#1573](https://github.com/temporalio/sdk-java/pull/1573))

.setStartToCloseTimeout(Duration.ofSeconds(10))

local activities are meant for very fast operations that do not exceed workflow task timeout (10s), they are not meant for “infinite retries”, see more here. Can you share use case please?