[
https://issues.apache.org/jira/browse/BOOKKEEPER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268422#comment-13268422
]
Flavio Junqueira commented on BOOKKEEPER-235:
---------------------------------------------
InterleavedLedgerStorage#flush essentially calls LedgerCacheImpl#flushLedger
and EntryLogger#flush. They both have synchronization in some form. Given that
flushLock is kind of dangling in this patch, what if we simply remove the
synchronization block in InterleavedLedgerStorage#flush and drop flushLock?
> Bad syncing in entrylogger degrades performance for many concurrent ledgers
> ---------------------------------------------------------------------------
>
> Key: BOOKKEEPER-235
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-235
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Priority: Blocker
> Fix For: 4.1.0
>
> Attachments: BOOKKEEPER-235.diff
>
>
> EntryLogger flush syncs on the wrong object, which really hurts performance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
