disable message batching for Azure customers #11568
Conversation
github-actions
bot
added
area: loader
There was a problem hiding this comment.
I'm not sure if this is the direction we want to go here. We have work tracking for this problem at https://dev.azure.com/fluidframework/internal/_workitems/edit/465
github-actions
bot
removed
public api change
|
A better solution would be explicitly setting the value of |
github-actions
bot
added
the
area: framework
|
Scoped down the fix to a single line change in |
alpaix
changed the title
|
This commit is queued for merging with the |
* Add e2e test to demo use of flush mode * override flush mode for azure clients * disable new test for local driver * PR feedback
* Add e2e test to demo use of flush mode * override flush mode for azure clients * disable new test for local driver * PR feedback
The problem
The problem reported by a customer via IcM. Attempting to sync a large data set consisting of batched multiple messages (less than 768kb each) will hit Socket.io buffer max size and the connection will close. The reason is the delta manager flushes batched messages periodically without enforcing the max op size. The max op size is only honored by the container runtime per each message submitted as imposed by the initial design.
The solution
Disable the message batching by setting
flushModetoIntermediatefor Azure customers. The workaround should be reconsidered when the original batching problem is resolved.