[
https://issues.apache.org/jira/browse/BOOKKEEPER-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630423#comment-15630423
]
ASF GitHub Bot commented on BOOKKEEPER-961:
-------------------------------------------
GitHub user merlimat opened a pull request:
https://github.com/apache/bookkeeper/pull/69
BOOKKEEPER-961 - Assing read/write requests for same ledger to a single
thread
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:
1. Mutex contention to access the LedgerDescriptor
2. 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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/merlimat/bookkeeper bk-fixed-ledger-thread
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bookkeeper/pull/69.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #69
----
commit 580917c7f132abf274fe91919e33b5cd3eb8edf3
Author: Matteo Merli <[email protected]>
Date: 2016-11-02T20:32:40Z
BOOKKEEPER-961 - Assing read/write requests for same ledger to a single
thread
----
> 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)
