Config only update on Service Fabric 10.1 using --force-restart does not restart applications

Steve Sherwood 0

All of my applications in my service fabric cluster read configuration directly from Azure KeyVault on start up. To change the configuration we do a config only update of a deployed application changing a "timestamp" value in the service's parameters, and then do a config only update using the SFCTL command line tool with --force-restart to restart the underlying apps on each node. The cluster seems to go through the motions, but the underlying applications are not restarted. This seems to have started since v10 of service fabric. Is there a work around for this without having to deploy a complete new version of the software?

Sai Krishna Katakam 1,510 Reputation points Microsoft Vendor

2024-12-16T21:22:12.8+00:00

Hi Steve Sherwood,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

We understand the issue you’re experiencing with --force-restart not restarting applications during a config-only update on Service Fabric 10.1.

We are currently looking into the issue and will get back to you as soon as possible with more information. In the meantime, if you have any additional information or logs that could assist in the investigation, please feel free to share them.

Thank you for your patience and understanding.
Prrudram-MSFT 27,251 Reputation points

2024-12-17T09:05:07.07+00:00
Hello @Steve Sherwood

I have reviewed your issue, It sounds like you're encountering a known issue with Service Fabric v10 where the --force-restart flag in the SFCTL command line tool doesn't restart the underlying applications as expected. This issue has been reported by other users as well

One workaround you can try is to manually trigger a rolling upgrade of your application with the same version but with a different configuration. This can be done using the Start-ServiceFabricApplicationUpgrade PowerShell cmdlet or the equivalent REST API. Here's a basic example using PowerShell:

Start-ServiceFabricApplicationUpgrade -ApplicationName fabric:/YourAppName -ApplicationTypeVersion 1.0.0 -ApplicationParameter @{"timestamp"="new_timestamp_value"} -Mode Monitored

This approach forces the cluster to apply the new configuration and restart the services without needing to deploy a new version of the software.

Additionally, you might want to check the Service Fabric release notes and GitHub issues for any updates or patches that address this specific problem

If the issue persists, consider reaching out to Microsoft support for more detailed assistance. They might have more insights or a hotfix available for this problem.

Let me know if you need further assistance or have any other questions!
Steve Sherwood 0 Reputation points

2024-12-17T11:36:20.94+00:00

It is the configuration only upgrade that I am already doing

sfctl application upgrade --application-id AppId --application-version 8.0.1250 --mode Monitored --health-check-stable-duration PT0H0M30S --force-restart true --failure-action Manual --parameters "{"DeployTimestamp":"20241217_113248"}"

In the Service Fabric explorer I can see the Parameter "DeployTimestamp" being changed, but the underlying process is not restarted.
Steve Sherwood 0 Reputation points

2024-12-17T11:38:30.04+00:00

Is there an ETA for a fix?
Prrudram-MSFT 27,251 Reputation points

2024-12-17T17:45:31.76+00:00

@Steve Sherwood I am checking with the product team, I will update you once I hear from them.

Share via

Config only update on Service Fabric 10.1 using --force-restart does not restart applications

Your answer