5.8 KiB
Microsoft Azure Service Fabric 9.1 Cumulative Update 7.0 Release Notes
This release will only be available through manual upgrades. Clusters set to automatic upgrades will not receive this release. For how to configure upgrades, please see classic or managed documentation.
Contents
- Service Fabric Packages and Versions
- Service Fabric Feature and Bug Fixes
- Retirement and Deprecation Path Callouts
Service Fabric Packages and Versions
The following packages and versions are part of this release:
| Service | Platform | Version |
|---|---|---|
| Service Fabric Runtime | Ubuntu 20 Windows |
9.1.1740.1 9.1.1993.9590 |
| Service Fabric for Windows Server | Service Fabric Standalone Installer Package | 9.1.1993.9590 |
| .NET SDK | Windows .NET SDK Microsoft.ServiceFabric Reliable Services and Reliable Actors ASP.NET Core Service Fabric integration |
6.1.1993 9.1.1993 6.1.1993 6.1.1993 |
| Java SDK | Java for Linux SDK | 1.0.6 |
| Service Fabric PowerShell and CLI | AzureRM PowerShell Module SFCTL |
0.3.15 11.0.1 |
Service Fabric Feature and Bug Fixes
| Versions | IssueType | Description | Resolution |
|---|---|---|---|
| Windows - 9.1.1993.9590 Ubuntu 20 - 9.1.1740.1 |
Feature | Key Value Store (KVS) | Brief Description: ESE sessions control access and scope of interactions with the database. Multiple sessions are used at once to support concurrent access to the database. Each active KVS transaction uses its own session. Session depletion is often caused by leaked transactions and will be cleaned up by restarting the replica. Solution: Replica will now fault automatically when sessions are exhausted |
| Windows - 9.1.1993.9590 Ubuntu 20 - 9.1.1740.1 |
Feature | Placement Load Balancing (PLB) | Brief Description: When node comes up during upgrade, all replicas that were on the node come up as StandBy replicas and only small number of replicas, up to throttling limit. This feature postpones placement up to specified period to avoid placing replicas on other nodes, as it leads to longer replica build times and increased resource consumption. |
Retirement and Deprecation Path Callouts
-
Ubuntu 18.04 LTS has reached its 5-year end-of-life window on June-2023. Service Fabric runtime has dropped support for 18.04 LTS after the published date, and we recommend moving your clusters and applications to supported versions listed here: Service Fabric supported Linux versions
-
Service Fabric runtime will soon stop supporting BinaryFormatter based remoting exception serialization by default and move to using Data Contract Serialization (DCS) based remoting exception serialization by default. Current applications using it will continue to work as-is, but Service Fabric strongly recommends moving to using Data Contract Serialization (DCS) based remoting exception instead.
-
Previously communicated, Service Fabric runtime had planned to remove Service Fabric runtime version 6.4 packages and older, as well as SDK version 3.3 packages and older, from the package Download Center in July 2023. We would like to inform you that this timeline has been extended, and the removal will now take place in January 2024.
-
Service Fabric runtime will soon be archiving and removing Service Fabric runtime versions less than 7.2 and older, as well as the corresponding SDK version 4.2 packages and older from the package Download Center. Archiving/Removing will affect application scaling and re-imaging of virtual machines in a Service Fabric Cluster running on unsupported versions. After older versions are removed/archived, this may cause failure while rolling back when the current in-progress upgrade has errors.
- To prevent disruption of workloads, create a new cluster using the following steps:
- Create a Service Fabric cluster using ARM template
- Create a Standalone cluster
- Install the supported version of Service Fabric SDK based on the Runtime version installed on the cluster.
- To prevent disruption of workloads, create a new cluster using the following steps:
Repositories and Download Links
The table below is an overview of the direct links to the packages associated with this release. Follow this guidance for setting up your developer environment: