[
https://issues.apache.org/jira/browse/KAFKA-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145234#comment-13145234
]
Jun Rao commented on KAFKA-191:
-------------------------------
So, I guess If append and fsync can't run in parallel, the patch won't help
much.
> Investigate removing the synchronization in Log.flush
> -----------------------------------------------------
>
> Key: KAFKA-191
> URL: https://issues.apache.org/jira/browse/KAFKA-191
> Project: Kafka
> Issue Type: New Feature
> Components: core
> Affects Versions: 0.8
> Reporter: Jay Kreps
> Assignee: Neha Narkhede
> Attachments: KAFKA-191.patch
>
>
> Currently we have the following synchronization in Log.scala:
> 1. append, roll, and flush all share a write lock
> 2. read is non-blocking
> Unfortunately this means that flush time latency is added to appends (even if
> the flush is done by a background thread). To fix this we should investigate
> a scheme to make append and flush not block each other.
--
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
