Project: Azure Service Fabric (Orchestration & Management / Scheduling & Orchestration)
File: Service-Fabric-71CU3-releasenotes.md

This release includes bug fixes and features as described in this document. The following packages and versions are part of this release: | Service | Platform | Version | ||-|| |Service Fabric Runtime| Ubuntu 16 <br> Ubuntu 18 <br> Windows | 7.1.452.1 <br> 7.1.452.1804 <br> 7.1.456.9590 | |Service Fabric for Windows Server|Service Fabric Standalone Installer Package | 7.1.456.9590 | |.NET SDK |Windows .NET SDK <br> Microsoft.ServiceFabric <br> Reliable Services and Reliable Actors <br> ASP.NET Core Service Fabric integration| 4.1.456 <br> 7.1.456 <br> 4.1.456 <br> 4.1.456 | |Java SDK |Java for Linux SDK | 1.0.6 | |Service Fabric PowerShell and CLI | AzureRM PowerShell Module <br> SFCTL | 0.3.15 <br> 10.0.0 | Microsoft Azure Service Fabric 7.1 Third Refresh Release Notes Extended support for 7.0*: Support for all 7.0 based Service Fabric releases will be extended by 3 months until October 1st,2020. We will take measures to ensure support expiration warnings for 7.0 clusters are removed. Please disregard any newsletters regarding support expiration for Service Fabric 7.0, there will be no impact to clusters. SF 7.2 runtime will remove support for dotnet core SF apps build with dotnet core 2.2 runtime. is out of support from Dec 2019. SF runtime 7.2 will remove installation of dotnet core 2.2 as part of its dependency. Customers should upgrade their app to the next dotnet core LTS version 3.1. Dotnet core LTS 2.1 runtime will go out of support from Aug 21, 2021. Service Fabric release after that date will drop support for dotnet core 2.1 SF apps. Service Fabric SDK will take a dependency on dotnet 3. features to support SF dotnet core SDK. | Versions | IssueType | Description | Resolution | |-|-|-|-| | Windows 7.1.456.9590 | Bug |Increase the possibility of finding a solution when moving replicas in PlacementWithMove|Brief desc: When placing new replicas, the Placement and Load Balancer will sometimes move other replicas around to make space for the new replicas during the PlacementWithMove phase. Previously, PlacementWithMove would randomly select any replica and randomly select any target node to move the replica to. However, when the randomly selected replica is part of an affinity relationship with a parent service, only a replica of the parent service will be eligible to be moved, otherwise it will violate the affinity

This problem becomes worse when there are many child services, because the probability of randomly selecting a replica from a child service is very high and this wastes computation cycles that could be spent searching for a valid solution. The solution to this problem is during the partial closure portion of PlacementWithMove, only replicas from the parent service will be chosen as candidates for PlacementWithMove. <br> Impact: Wasted search cycles resulting in an increased probability of PlacementWithMove not finding a valid solution. <br> Workaround: N/A <br> Fix: Only consider replicas of the parent service for candidates of PlacementWithMove during partial closure. | Windows 7.1.456.9590 | Bug |ImageStoreService stops loading every metadata in memory|Brief desc: ImageStoreService loaded metadata in memory for operation in some scenarios. The required resource increased linearly to the number of files in ImageStoreService. The cluster could run such scenario multiple times concurrently and the node could run in low memory or with lots of paged memory. <br> Impact: Provisioning packages to ImageStoreService or downloading images from ImageStoreService could get stuck by sluggish system. <br> Workaround: The complexity is proportion to the number of files in ImageStoreService. The number of files could be reduced significantly with compressed Code/Config/Data package. <br> Fix: The code has changed to utilize transaction enumeration instead of reading all data from replicated store. 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: | Area | Package | Version | Repository | Direct Download Link | |-|-|-|-|-| |Service Fabric Runtime |Ubuntu Developer Set-up | 7.1.452.1 |N/A | Cluster Runtime: https://apt-mo.trafficmanager.net/repos/servicefabric/pool/main/s/servicefabric <br> Service Fabric SDK for local cluster setup: https://apt-mo.trafficmanager.net/repos/servicefabric/pool/main/s/servicefabricsdkcommon/ <br> Container image: https://hub.docker.com/r/microsoft/service-fabric-onebox/ || Windows Developer Set-up| 7.1.456.9590 | N/A | https://download.microsoft.com/download/9/3/0/930f9307-52ef-4597-9ae9-f534415e77eb/MicrosoftServiceFabric.7.1.456.9590.exe | |Service Fabric for Windows Server |Service Fabric Standalone Installer Package |7.1.456.9590 |N/A | https://download.microsoft.com/download/8/3/6/836E3E99-A300-4714-8278-96BC3E8B5528/7.1.456.9590/Microsoft.Azure.ServiceFabric.WindowsServer.7.1.456.9590.zip | ||Service Fabric Standalone Runtime |7.1.456.9590 |N/A | https://download.microsoft.com/download/B/0/B/B0BCCAC5-65AA-4BE3-AB13-D5FF5890F4B5/7.1.456.9590/MicrosoftAzureServiceFabric.7.1.456.9590.cab | |.NET SDK |Windows .NET SDK |4.1.456 |N/A | https://download.microsoft.com/download/9/3/0/930f9307-52ef-4597-9ae9-f534415e77eb/MicrosoftServiceFabricSDK.4.1.456.msi | ||Microsoft.ServiceFabric |7.1.456 |N/A |https://www.nuget.org | ||Reliable Services and Reliable Actors<br>\-Microsoft.ServiceFabric.Services<br>\-Microsoft.ServiceFabric.Services.Remoting<br>\-Microsoft.ServiceFabric.Services.Wcf <br>\-Microsoft.ServiceFabric.Actors <br>\-Microsoft.ServiceFabric.Actors.Wcf |4.1.456|https://github.com/Azure/service-fabric-services-and-actors-dotnet |https://www.nuget.org | ||ASP.NET Core Service Fabric integration<br>\-Microsoft.ServiceFabric.Services.AspNetCore.*|4.1.456 |https://github.com/Azure/service-fabric-aspnetcore |https://www.nuget.org | ||Data, Diagnostics and Fabric transport<br>\-Microsoft.ServiceFabric.Data <br>\-Microsoft.ServiceFabric.Data.Interfaces <br>\-Microsoft.ServiceFabric.Diagnostics.Internal <br>\-Microsoft.ServiceFabric.FabricTransport/Internal |4.1.456 |N/A| https://www.nuget.org | ||Microsoft.ServiceFabric.Data.Extensions |4.1.456 |N/A |https://www.nuget.org | |Java SDK |Java SDK |1.0.6 |N/A | https://mvnrepository.com/artifact/com.microsoft.servicefabric/sf-actors/1.0.6 | |Eclipse |Service Fabric plug-in for Eclipse |2.0.7 | N/A |N/A | |Yeoman |Azure Service Fabric Java generator |1.0.7 |https://github.com/Azure/generator-azuresfjava |N/A | ||Azure Service Fabric C# generator |1.0.9 |https://github.com/Azure/generator-azuresfcsharp |N/A | ||Azure Service Fabric guest executables generator |1.0.1 |https://github.com/Azure/generator-azuresfguest |N/A| ||Azure Service Fabric Container generators |1.0.1 |https://github.com/Azure/generator-azuresfcontainer |N/A | |CLI |Service Fabric CLI |10.0.0 |https://github.com/Azure/service-fabric-cli |https://pypi.python.org/pypi/sfctl | |PowerShell |AzureRM.ServiceFabric |0.3.15 |https://github.com/Azure/azure-powershell/tree/preview/src/ResourceManager/ServiceFabric |https://www.powershellgallery.com/packages/AzureRM.ServiceFabric/0.3.15 |