ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3796) .NET: Platforms system cache
Date Sun, 11 Sep 2016 04:55:21 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15481039#comment-15481039

Vladimir Ozerov commented on IGNITE-3796:

I performed several private discussions with Pavel Tupitsyn, Alexey Goncharuk and Semen Boikov.
1) Adding new cache doesn't seem to be a good idea for several purposes:
- It increases start time and memory footprint
- Marshaller metadata handling is tough thing as it easily lead to various deadlock. For this
reason current Java marshaller cache has separate thread pool.
2) There is alternative solution - use custom discovery events. However, this mechanism appears
to be pretty complex to implement, and it can break compatibility.
3) Instead of introducing a new cache, we decided to re-use existing marshaller cache. This
appears to be the most sensible solution for now.

Closing this ticket as "Won't Fix".

> .NET: Platforms system cache
> ----------------------------
>                 Key: IGNITE-3796
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3796
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache, platforms
>    Affects Versions: 1.8
>            Reporter: Pavel Tupitsyn
>            Assignee: Vladimir Ozerov
>              Labels: .net
>             Fix For: 1.8
> Create a new system cache (similar to ignite-sys-cache and others) for platforms.
> The need for such cache emerged in two tickets: IGNITE-1915, IGNITE-2703
> * Cache (and listener) should be started even if there is no platform
> * Different purpose keys should be clearly separated (different class)

This message was sent by Atlassian JIRA

View raw message