Remove FillETags repair-step. #40996
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Remove FillEtags repair-step.
Motivation and Context
The FillEtags-Repair step runs on each core upgrade and takes a disproportional long time (few hours) on large instances. Otherwise upgrades would only take a few minutes. As we didn't encounter empty etags for a very long time in production-instances we think it is safe to remove this job.
How Has This Been Tested?
Experienced at multiple customers, the job does not repair anything and takes very long to run so support's operating procedure ist now to comment out the step before upgrading.
Types of changes
Checklist: