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
Is your feature request related to a problem? Please describe.
Tuning activity timeouts in workflows involves rebuilding and deploying an application, which can be an unacceptably long turnaround time depending on the urgency of the timeout change (e.g. in response to an incident). Some workers may also have a long startup / awaitTermination cycle, so the current methodology of updating a dynamic config and then redeploying is also too long of a loop.
Describe the solution you'd like ActivityOptions provided via WorkerImplementationOptions to support a Supplier<ActivityOptions> would help allow us to plugin a dynamic config store to update workers' activity options, specifically the timeouts, on a faster cycle.
Describe alternatives you've considered
Changing the configs in code, redeploying
Changing configs and then restarting the workers
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Tuning activity timeouts in workflows involves rebuilding and deploying an application, which can be an unacceptably long turnaround time depending on the urgency of the timeout change (e.g. in response to an incident). Some workers may also have a long startup / awaitTermination cycle, so the current methodology of updating a dynamic config and then redeploying is also too long of a loop.
Describe the solution you'd like
ActivityOptions
provided viaWorkerImplementationOptions
to support aSupplier<ActivityOptions>
would help allow us to plugin a dynamic config store to update workers' activity options, specifically the timeouts, on a faster cycle.Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: