Spring boot starter behavior changes on app startup

[parinmaru2]

Expected Behavior

Old SDK versions (older than v1.22.0)

• If temporal server is unavailable, the worker service would still be able to startup successfully though it would have errors in the logs about the server being unavailable.

Actual Behavior

New SDK versions (>= v1.22.0)

• Worker service wouldn't come up if the temporal server is unavailable.

Desired Behavior

• It's fine to keep the default behavior where worker wouldn't be able to startup if the temporal server is unavailable. However, it would be good if a config is provided that customers can override if they want the older behavior where the worker service wouldn't crash in case the server is unavailable.

More details can be found in this conversation: https://community.temporal.io/t/spring-boot-starter-behavior-changes-on-app-startup/12239

[Quinn-With-Two-Ns]

To start a worker the Temporal service must be up and reachable, this is a requirement across all of our SDKs including Java. There was not change to this requirement in v1.22.0. In Springboot if you don't want to start a worker on application start up you can set start-workers: false. See the readme for more details

[parinmaru2]

@Quinn-With-Two-Ns If you looked at the attached link, there are screenshots about the before/after behavior.

Before (on v1.21.2):

After (on v1.23.2):

I believe @mfateev commented on that thread that this change was done in v1.22.0.

[Quinn-With-Two-Ns]

#1837 changes when a worker we exactly started, but workers have always required a connection to Temporal to start. If you would like to control worker start you can set start-workers: false as I described above.

[parinmaru2]

@Quinn-With-Two-Ns I am not sure how start-workers: false will help us here.

My goal is to be able to start my temporal workflow worker even if the upstream temporal server isn't available. How will start-workers: false help here? Apologize if I am missing something.

[Quinn-With-Two-Ns]

You should only start your worker if the temporal service is available. Why is your Temporal service not avaialbe when you are trying to start a worker?

[parinmaru2]

Totally agree with you @Quinn-With-Two-Ns . However, we provide self-hosted Temporal servers within our company as a managed-service. And one of our customers has this very peculiar use case where they want the worker to startup successfully even if Temporal service is not available.

[Quinn-With-Two-Ns]

If a worker cannot connect to the Temporal service the worker cannot successfully start. I would recommend fixing the issue causing the worker to start before the Temporal service is up.

If you are okay with the worker start blocking until it connects to the Temporal server you can increase the time for the first connection request by increasing WorkflowServiceStubsOptions.Builder.setSystemInfoTimeout and start the worker manually.

[parinmaru2]

Thanks @Quinn-With-Two-Ns