[GitHub] dlg99 opened a new issue #1239: PendingReadOp can use writability state of netty channel to pick bookie to send request to.

[GitBox <gi...@apache.org>]

dlg99 opened a new issue #1239: PendingReadOp can use writability state of netty channel to pick bookie to send request to.
URL: https://github.com/apache/bookkeeper/issues/1239
 
 
   **FEATURE REQUEST**
   
   1. Please describe the feature you are requesting.
   
   PendingReadOp picks bookie to send first request to in round-robin fashion. 
   It can use writability state of corresponding netty channel to decide on the first bookie to send request to. 
   
   2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
   
   Nice to have at this moment. 
   
   3. Provide any additional detail on your proposed use case for this feature.
   
   This will help reduce tail latency and reduce number of speculative reads as client won't spend time waiting for clearly unresponsive bookie.
   
   4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
   - [ ] [1086](https://github.com/apache/bookkeeper/issues/1086): io.netty.util.internal.OutOfDirectMemoryError under continuous heavy load.
   
   
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services