You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Damian Guy (JIRA)" <ji...@apache.org> on 2018/01/10 10:25:00 UTC

[jira] [Resolved] (KAFKA-6412) Improve synchronization in CachingKeyValueStore methods

     [ https://issues.apache.org/jira/browse/KAFKA-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Damian Guy resolved KAFKA-6412.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.0

Issue resolved by pull request 4372
[https://github.com/apache/kafka/pull/4372]

> Improve synchronization in CachingKeyValueStore methods
> -------------------------------------------------------
>
>                 Key: KAFKA-6412
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6412
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Ted Yu
>             Fix For: 1.1.0
>
>         Attachments: 6412-jmh.v1.txt, k-6412.v1.txt
>
>
> Currently CachingKeyValueStore methods are synchronized at method level.
> It seems we can use read lock for getter and write lock for put / delete methods.
> For getInternal(), if the underlying thread is streamThread, the getInternal() may trigger eviction. This can be handled by obtaining write lock at the beginning of the method for streamThread.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)