%3CLINGO-SUB%20id%3D%22lingo-sub-1466517%22%20slang%3D%22en-US%22%3EAzure%20Service%20Fabric%207.1%20First%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1466517%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Azure%20Service%20Fabric%207.1%20first%20refresh%20release%20includes%20bug%20fixes%2C%20and%20performance%20enhancements%20for%20standalone%2C%20and%20Azure%20environments%20has%20started%20rolling%20out%20to%20the%20various%20Azure%20regions.%20The%20updates%20for%20.NET%20SDK%2C%20Java%20SDK%20and%20Service%20Fabric%20Runtime%20is%20available%20through%20Web%20Platform%20Installer%2C%20NuGet%20packages%20and%20Maven%20repositories%20in%207-10%20days%20within%20all%20regions.%3C%2FP%3E%3CUL%3E%3CLI%3EService%20Fabric%20Runtime%3CUL%3E%3CLI%3EWindows%20%E2%80%93%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3E7.1.417.9590%3C%2FEM%3E%3C%2FLI%3E%3CLI%3EUbuntu%20-%26nbsp%3B%3CEM%3E%26nbsp%3B7.1.418.1%3C%2FEM%3E%3C%2FLI%3E%3CLI%3EService%20Fabric%20for%20Windows%20Server%20Service%20Fabric%20Standalone%20Installer%20Package%20-%26nbsp%3B7.1.417.9590%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3C%2FUL%3E%3CUL%3E%3CLI%3E.NET%20SDK%3CUL%3E%3CLI%3EWindows%20.NET%20SDK%20-%26nbsp%3B%26nbsp%3B%3CEM%3E4.1.416%3C%2FEM%3E%3C%2FLI%3E%3CLI%3EMicrosoft.ServiceFabric%20-%26nbsp%3B%3CEM%3E%26nbsp%3B7.1.417%3C%2FEM%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%3C%2FLI%3E%3CLI%3EReliable%20Services%20and%20Reliable%20Actors%20-%26nbsp%3B%26nbsp%3B4.1.417%3C%2FLI%3E%3CLI%3EASP.NET%20Core%20Service%20Fabric%20integration%20-%26nbsp%3B%3CEM%3E%26nbsp%3B4.1.417%3C%2FEM%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3EJava%20SDK%20%E2%80%93%26nbsp%3B%201.0.6%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CSTRONG%3EKey%20Announcements%3C%2FSTRONG%3E%3C%2FP%3E%3CUL%3E%3CLI%3EAutomatic%20upgrades%20will%20resume%20as%20of%20this%20release.%20Any%20clusters%20set%20to%20automatic%20upgrades%20will%20pick%20up%207.1CU1%20as%20soon%20it%20becomes%20available%20in%20the%20region.%20Clusters%20that%20have%20not%20already%20upgraded%20from%207.0%20to%207.1%20will%20upgrade%20directly%20to%207.1CU1.%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fservice-fabric%2Fservice-fabric-application-upgrade-advanced%23avoid-connection-drops-during-planned-downtime-of-stateless-services%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EGeneral%20Availability%20of%20Request%20Drain%3C%2FA%3E%3A%20During%20planned%20service%20maintenance%2C%20such%20as%20service%20upgrades%20or%20node%20deactivation%2C%20you%20would%20like%20to%20allow%20the%20services%20to%20gracefully%20drain%20connections.%20This%20feature%20adds%20an%20instance%20close%20delay%20duration%20in%20the%20service%20configuration.%20During%20planned%20operations%2C%20SF%20will%20remove%20the%20Service's%20address%20from%20discovery%20and%20then%20wait%20this%20duration%20before%20shutting%20down%20the%20service.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EFor%20more%20details%2C%20please%20read%20the%26nbsp%3B%3CA%20title%3D%22SF%2070CU4%20release%20notes%22%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fservice-fabric%2Fblob%2Fmaster%2Frelease_notes%2FService-Fabric-71CU1-releasenotes.md%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Erelease%20notes%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1466517%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Azure%20Service%20Fabric%207.1%20first%20refresh%20release%20includes%20bug%20fixes%2C%20and%20performance%20enhancements%20for%20standalone%2C%20and%20Azure%20environments%20has%20started%20rolling%20out%20to%20the%20various%20Azure%20regions.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1470060%22%20slang%3D%22fr-FR%22%3ERe%3A%20Azure%20Service%20Fabric%207.1%20First%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1470060%22%20slang%3D%22fr-FR%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20links%20attached%20to%20the%20release%20note%20seems%20broken%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F8%2F3%2F6%2F836E3E99-A300-4714-8278-96BC3E8B5528%2F7.1.416.9590%2FMicrosoft.Azure.ServiceFabric.WindowsServer.7.1.416.9590.zip%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F8%2F3%2F6%2F836E3E99-A300-4714-8278-96BC3E8B5528%2F7.1.416.9590%2FMicrosoft.Azure.ServiceFabric.WindowsServer.7.1.416.9590.zip%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eand%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdownload.microsoft.com%2Fdownload%2FB%2F0%2FB%2FB0BCCAC5-65AA-4BE3-AB13-D5FF5890F4B5%2F7.1.416.9590%2FMicrosoftAzureServiceFabric.7.1.416.9590.cab%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdownload.microsoft.com%2Fdownload%2FB%2F0%2FB%2FB0BCCAC5-65AA-4BE3-AB13-D5FF5890F4B5%2F7.1.416.9590%2FMicrosoftAzureServiceFabric.7.1.416.9590.cab%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGilles%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1474631%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Service%20Fabric%207.1%20First%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1474631%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20trying%20to%20understand%20what%20the%20actual%20version%20number%20is%20for%20the%207.1%20CU1.%26nbsp%3B%20According%20to%20this%20blog%20article%20it%20says%26nbsp%3B%3CSPAN%3E7.1.417.9590%2C%20but%20then%20when%20you%20read%20the%20release%20notes%20it%20says%26nbsp%3B7.1.416.9590.%26nbsp%3B%20Since%20the%20Azure%20portal%20is%20showing%207.1.417.9590%20in%20the%20upgrade%20blade%2C%20I'm%20assuming%20that%20is%20correct%2C%20but%20it%20would%20be%20really%20nice%20if%20documentation%20matched%20reality%20and%20vice%2Fversa.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Senior Member

The Azure Service Fabric 7.1 first refresh release includes bug fixes, and performance enhancements for standalone, and Azure environments has started rolling out to the various Azure regions. The updates for .NET SDK, Java SDK and Service Fabric Runtime is available through Web Platform Installer, NuGet packages and Maven repositories in 7-10 days within all regions.

  • Service Fabric Runtime
    • Windows – 7.1.417.9590
    • Ubuntu -  7.1.418.1
    • Service Fabric for Windows Server Service Fabric Standalone Installer Package - 7.1.417.9590           
  • .NET SDK
    • Windows .NET SDK -  4.1.416
    • Microsoft.ServiceFabric -  7.1.417       
    • Reliable Services and Reliable Actors -  4.1.417
    • ASP.NET Core Service Fabric integration -  4.1.417
  • Java SDK –  1.0.6

Key Announcements

  • Automatic upgrades will resume as of this release. Any clusters set to automatic upgrades will pick up 7.1CU1 as soon it becomes available in the region. Clusters that have not already upgraded from 7.0 to 7.1 will upgrade directly to 7.1CU1. 
  • General Availability of Request Drain: During planned service maintenance, such as service upgrades or node deactivation, you would like to allow the services to gracefully drain connections. This feature adds an instance close delay duration in the service configuration. During planned operations, SF will remove the Service's address from discovery and then wait this duration before shutting down the service.

For more details, please read the release notes.

2 Comments
Occasional Visitor
Occasional Visitor

Just trying to understand what the actual version number is for the 7.1 CU1.  According to this blog article it says 7.1.417.9590, but then when you read the release notes it says 7.1.416.9590.  Since the Azure portal is showing 7.1.417.9590 in the upgrade blade, I'm assuming that is correct, but it would be really nice if documentation matched reality and vice/versa.