Handle partial failure in ISR revalidation #410
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.
This PR improve ISR revalidation.
Right now if a revalidation of a page fails for any reason, the page will have to wait for the 5 min deduplication window before attempting any revalidation again. And in a batch if the first one fails with an exception, all the other route in the batch will also have to wait for this 5 min dedup window.
This PR handles partial failures, and if properly set in IAC, the failed route will automatically retry every 30 seconds.
This also fix an issue with HEAD request not having the fix applied for all the ISR headers in non streaming and so revalidation ISR request were cached in the CDN, which could also cause the 5 min dedup window issue