Fix DDOS of Office.com #4872
Merged
Fix DDOS of Office.com #4872
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
christiango
approved these changes
Jan 21, 2021
|
We see a ton of blob request to SPO and SPO starts throttling and eventually they throttle whole app, so Office.com is going down. |
wes-carlson
pushed a commit
to wes-carlson/FluidFramework
that referenced
this pull request
Jan 22, 2021
We see a ton of blob request to SPO and SPO starts throttling and eventually they throttle whole app, so Office.com is going down. We do see requests for blobs (and failures) as far history of Kusto allows, but volume increased last 3 days and we are getting a lot of 429s Being able to debug one case, it's obvious that cache is empty for summarizing client and we start to fetch all blobs from storage, which brings things down. Disabling cache eviction to work around problem
wes-carlson
added a commit
that referenced
this pull request
Jan 22, 2021
We see a ton of blob request to SPO and SPO starts throttling and eventually they throttle whole app, so Office.com is going down. We do see requests for blobs (and failures) as far history of Kusto allows, but volume increased last 3 days and we are getting a lot of 429s Being able to debug one case, it's obvious that cache is empty for summarizing client and we start to fetch all blobs from storage, which brings things down. Disabling cache eviction to work around problem Co-authored-by: Vlad Sudzilouski <vlad@sudzilouski.com>
wes-carlson
pushed a commit
to wes-carlson/FluidFramework
that referenced
this pull request
Jan 22, 2021
We see a ton of blob request to SPO and SPO starts throttling and eventually they throttle whole app, so Office.com is going down. We do see requests for blobs (and failures) as far history of Kusto allows, but volume increased last 3 days and we are getting a lot of 429s Being able to debug one case, it's obvious that cache is empty for summarizing client and we start to fetch all blobs from storage, which brings things down. Disabling cache eviction to work around problem
vladsud
added a commit
to vladsud/FluidFramework
that referenced
this pull request
Jan 22, 2021
We see a ton of blob request to SPO and SPO starts throttling and eventually they throttle whole app, so Office.com is going down. We do see requests for blobs (and failures) as far history of Kusto allows, but volume increased last 3 days and we are getting a lot of 429s Being able to debug one case, it's obvious that cache is empty for summarizing client and we start to fetch all blobs from storage, which brings things down. Disabling cache eviction to work around problem
wes-carlson
added a commit
that referenced
this pull request
Jan 22, 2021
We see a ton of blob request to SPO and SPO starts throttling and eventually they throttle whole app, so Office.com is going down. We do see requests for blobs (and failures) as far history of Kusto allows, but volume increased last 3 days and we are getting a lot of 429s Being able to debug one case, it's obvious that cache is empty for summarizing client and we start to fetch all blobs from storage, which brings things down. Disabling cache eviction to work around problem Co-authored-by: Vlad Sudzilouski <vlad@sudzilouski.com>
vladsud
added a commit
that referenced
this pull request
Feb 1, 2021
Follow up to #4872 Due to evicting blobs from cache, we force summarizer to read most of the blobs from storage without hitting driver cache As result, SPO starts to throttle requests and app, i.e. it results in self-made DDOS attack. Reworking cache layer and disabling cache eviction for now.
This was referenced Oct 17, 2022
This was referenced Oct 18, 2022
This was referenced Oct 18, 2022
This was referenced Oct 20, 2022
This was referenced Oct 20, 2022
This was referenced Oct 31, 2022
This was referenced Oct 31, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We see a ton of blob request to SPO and SPO starts throttling and eventually they throttle whole app, so Office.com is going down.
We do see requests for blobs (and failures) as far history of Kusto allows, but volume increased last 3 days and we are getting a lot of 429s