You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that Bookkeeper client has no timeout for read operations, timeout is a very important part in RPC system
Although there is a field named lastReadCallback in ManagedLedgerImp to check read ops timeout, but from my understanding, it just checks the last read operation: if there is 3 read operations A,B,C, the lastReadCallback will be set to C and just check C even A and B are not finished.
I don't understand why Bookkeeper client has no timeout for read operations and why ManagedLedgerImpl just check the last read operation.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I found that Bookkeeper client has no timeout for read operations, timeout is a very important part in RPC system
Although there is a field named
lastReadCallbackinManagedLedgerImpto check read ops timeout, but from my understanding, it just checks the last read operation: if there is 3 read operationsA,B,C, thelastReadCallbackwill be set toCand just checkCevenAandBare not finished.I don't understand why Bookkeeper client has no timeout for read operations and why
ManagedLedgerImpljust check the last read operation.Your answer is greatly appreciated.
All reactions