dlg99 commented on a change in pull request #1088: ISSUE #1086 (@bug
W-4146427@) Client-side backpressure in netty (Fixes:
io.netty.util.internal.OutOfDirectMemoryError under continuous heavy load)
URL: https://github.com/apache/bookkeeper/pull/1088#discussion_r183539951
##########
File path:
bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerHandleAdv.java
##########
@@ -211,6 +211,11 @@ public String toString() {
return;
}
+ if (!waitForWritable(distributionSchedule.getWriteSet(op.getEntryId()),
+ op.getEntryId(), 0, waitForWriteSetMs)) {
Review comment:
@jvrao there is an option to set waitTimeoutOnBackpressureMs=0 and get this
behavior (immediate fail/ensemble change).
I'd argue that in case of spiky traffic it is ok for netty to switch channel
in non-writable state and back so to avoid frequent ensemble changes I'd wait a
little. Ensemble changes aren't exactly free (takes time + more data in zk)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
