-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid sending cluster manifest to client if client already has the latest version #8728
Conversation
@dotnet-policy-service agree |
Sorry, we found that there was a code omission when submitting the PR. We will submit another PR later.
|
I find bug, every silo address need compare clusterManifest version,new patch is commit. |
@ReubenBond There are two items that have not passed the test. Could you please check them? |
I pushed a change, I think this is the right approach and should achieve the behavior you're looking for. |
The key point of this issue is comparing versions of the same SiloHost.So it is necessary to update the version according to Silohost. |
@HermesNew the current version in this PR should accomplish that - do you see issues with the implementation here? |
@HermesNew @453873, please take a look at the current version and let me know if you have any issues with it. I will merge and we can include it in the next set of releases (7.2.5 & 8.0.0) |
@ReubenBond Sorry, I've been very busy these past few days. Tomorrow we will release a version ourselves to verify whether this issue has been resolved. |
No problem at all, thank you @HermesNew! |
@ReubenBond I don't see any code for this issue in the 7. x branch. We are using. net7.0, so we can only release this version. My fork is the main code, and the. net SDK is already .net8.0. |
@HermesNew We can backport this to the 7.x branch - usually, we would do that after merging the PR |
updateIncludesAllActiveServers may be null.
…test version (dotnet#8728) Co-authored-by: Reuben Bond <[email protected]> Co-authored-by: ReubenBond <[email protected]> Co-authored-by: HermesNew <[email protected]>
* Avoid sending cluster manifest to client if client already has the latest version (#8728) Co-authored-by: Reuben Bond <[email protected]> Co-authored-by: ReubenBond <[email protected]> Co-authored-by: HermesNew <[email protected]> * No newer cluster manifest handle There was no newer cluster manifest, so wait for the next refresh interval and try again. * PR feedback --------- Co-authored-by: swam <[email protected]> Co-authored-by: HermesNew <[email protected]>
Fixes #8722
Microsoft Reviewers: Open in CodeFlow