9.2 KiB
Microsoft Azure Service Fabric 8.1 Third Refresh Release Notes
This release includes the bug fixes described in this document. This release includes runtime, SDKs, and Windows Server Standalone deployments to run on-premises.
The following packages and versions are part of this release:
| Service | Platform | Version |
|---|---|---|
| Service Fabric Runtime | Ubuntu 16 Ubuntu 18 Windows |
8.1.334.1 8.1.334.1 8.1.335.9590 |
| Service Fabric for Windows Server | Service Fabric Standalone Installer Package | 8.1.335.9590 |
| .NET SDK | Windows .NET SDK Microsoft.ServiceFabric Reliable Services and Reliable Actors ASP.NET Core Service Fabric integration |
5.1.335 8.1.335 8.1.335 8.1.335 |
| Java SDK | Java for Linux SDK | 1.0.6 |
| Service Fabric PowerShell and CLI | AzureRM PowerShell Module SFCTL |
0.3.15 11.1.0 |
Contents
Microsoft Azure Service Fabric 8.1 Third Refresh Release Notes
- Current And Upcoming Breaking Changes
- Service Fabric Common Bug Fixes
- Repositories and Download Links
Current Breaking Changes
-
Service Fabric 7.2 and higher runtime drops support for .NET Core Service Fabric apps running with .NET Core 2.2 runtime. .NET Core runtime 2.2 is out of support from Dec 2019. Service Fabric runtime will not install .NET Core runtime 2.2 as part of its dependency. Customers should upgrade their .NET 2.2 runtime SF apps to the next .NET Core LTS version 3.1.
-
Guest executable and container applications created or upgraded in SF clusters with runtime versions 7.1+ are incompatible with prior SF runtime versions (e.g. SF 7.0).
Following scenarios are impacted:- An application with guest executables or containers is created or upgraded in an SF 7.1+ cluster.
The cluster is then downgraded to a previous SF runtime version (e.g. SF 7.0).
The application fails to activate. - A cluster upgrade from pre-SF 7.1 version to SF 7.1+ version is in progress.
In parallel with the SF runtime upgrade, an application with guest executables or containers is created or upgraded.
The SF runtime upgrade starts rolling back (due to any reason) to the pre-SF 7.1 version.
The application fails to activate.
To avoid issues when upgrading from a pre-SF 7.1 runtime version to an SF 7.1+ runtime version, do not create or upgrade applications with guest executables or containers while the SF runtime upgrade is in progress.
- The simplest mitigation, when possible, is to delete and recreate the application in SF 7.0.
- The other option is to upgrade the application in SF 7.0 (for example, with a version only change).
If the application is stuck in rollback, the rollback has to be first completed before the application can be upgraded again.
- An application with guest executables or containers is created or upgraded in an SF 7.1+ cluster.
-
.NET Core runtime LTS 2.1 runtime is now out of support as of Aug 21, 2021. Service Fabric releases after that date will drop support for Service Fabric apps running with .NET Core 2.1 runtime. This includes the following release versions and beyond - 8.0 CU4 and above, 8.1 CU2 and above and 8.2 RTO release and above. Current apps running on .NET Core 2.1 runtime will continue to work, but requests for investigations or request for changes will no longer receive support. Service Fabric .NET SDK will take a dependency on .NET runtime 3.x features to support Service Fabric .NET Core apps. This has no impact on Service Fabric .NET Framework SDK.
-
Ubuntu 16.04 LTS reached it's 5-year end-of-life window on April 30, 2021 and is no longer supported by it's vendors. Service Fabric runtime will drop support for Ubuntu 16.04 after that date as well. Current applications running on it will continue to work, but requests for investigations or requests for change will no longer receive support. We recommend moving your applications to Ubuntu 18.04.
Service Fabric Common Bug Fixes
| Versions | IssueType | Description | Resolution |
|---|---|---|---|
| Windows - 8.1.321.9590 Ubuntu 16 - 8.1.323.1 Ubuntu 18 - 8.1.323.1 |
Bug | File leak in Service Fabric Runtime for Ubuntu | Brief desc: When an application package uploaded in compressed mode is upgraded, the code, data and config packages are extracted into service instance path. The compressed file handle is not closed on Linux system. The leaked handle accumulates to inhibit further file operation after long time. Impact: The leaked file handle limits the system's file operation. Fix: The leaked handle is reclaimed. Workaround: Restarting Fabric process releases leaked handles for a workaround. |
| Windows - 8.1.321.9590 Ubuntu 16 - 8.1.323.1 Ubuntu 18 - 8.1.323.1 |
Bug | Placement and Load Balancing behavior change of config value for Auxiliary Replicas | Brief desc: This fix is to make sure that the placement & load balancer reacts dynamically in response to changes to the config value of IncludeAuxiliaryInFDTree. Impact: The impact is limited to the Auxiliary Replica feature. |
| Windows - 8.1.321.9590 Ubuntu 16 - 8.1.323.1 Ubuntu 18 - 8.1.323.1 |
Bug | StandBy IdleAuxiliary replica transitioning to Idle role | Brief desc: StandBy Auxiliary replicas were incorrectly transformed into Idle replicas instead to IdleAuxiliary replicas. Impact: Customer expects to receive IdleAuxiliary role, but receives Idle role, making their API throw an error. Fix: Updated code on SF side to properly assign role for StandBy replicas. |
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: