You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (Commented) (JIRA)" <ji...@apache.org> on 2011/11/06 03:56:52 UTC
[jira] [Commented] (KAFKA-191) Investigate removing the
synchronization in Log.flush
[ https://issues.apache.org/jira/browse/KAFKA-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144897#comment-13144897 ]
Neha Narkhede commented on KAFKA-191:
-------------------------------------
I'm interested in investigating this and run some perf tests to see change in IO performance
> 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
>
> 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