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

Posted to commits@samza.apache.org by "Xinyu Liu (JIRA)" <ji...@apache.org> on 2016/07/20 20:25:20 UTC

[jira] [Resolved] (SAMZA-958) Make store/cache thread safe

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

Xinyu Liu resolved SAMZA-958.
-----------------------------
    Resolution: Fixed

committed as part of SAMZA-863.

> Make store/cache thread safe
> ----------------------------
>
>                 Key: SAMZA-958
>                 URL: https://issues.apache.org/jira/browse/SAMZA-958
>             Project: Samza
>          Issue Type: Sub-task
>            Reporter: Xinyu Liu
>            Assignee: Xinyu Liu
>
> All the existing stores/cache need to be thread safe in order to be used by multithreaded tasks. The following changes are made to ensure the thread safety of the stores:
> - For CachedStore, use sychronized lock for each public function;
> - For current InMemoryKeyValueStore, use ConcurrentSkipListMap as underlying map for thread safety.
> - For store Iterator, do not support remove functionality (throw UnsupportedOperationException like RocksDb does today).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)