[
https://issues.apache.org/jira/browse/BOOKKEEPER-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659641#comment-15659641
]
Hudson commented on BOOKKEEPER-961:
-----------------------------------
FAILURE: Integrated in Jenkins build bookkeeper-master #1563 (See
[https://builds.apache.org/job/bookkeeper-master/1563/])
BOOKKEEPER-961: Assign read/write requests for same ledger to a single (mmerli:
rev 7673febb6519fedb96320ec98db71601826a63b1)
* (edit)
bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/PacketProcessorBase.java
* (edit)
bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieRequestProcessor.java
* (edit)
bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/PacketProcessorBaseV3.java
* (edit)
bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/ReadEntryProcessorV3.java
* (edit)
bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/WriteEntryProcessorV3.java
> Assing read/write request for same ledger to a single thread
> ------------------------------------------------------------
>
> Key: BOOKKEEPER-961
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-961
> Project: Bookkeeper
> Issue Type: Improvement
> Affects Versions: 4.4.0
> Reporter: Matteo Merli
> Assignee: Matteo Merli
> Fix For: 4.5.0
>
>
> When entries for the same ledger are processed by the bookie we should avoid
> the reordering of the request. Currently, if multiple read/write threads are
> configured, the requests will be passed to the executor and writes for same
> ledger will be spread across multiple threads.
> This poses 2 issues:
> # Mutex contention to access the LedgerDescriptor
> # If the client receives add-entry acks out of order it has anyway to wait
> for the acks of previous entries before acknowledging the whole sequence
> to the application. In practice, the reordering is increasing the
> latency
> experienced by the application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
