You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Setrakyan (JIRA)" <ji...@apache.org> on 2015/03/27 19:10:52 UTC
[jira] [Commented] (IGNITE-180) Use dynamic cache start for queue
and set
[ https://issues.apache.org/jira/browse/IGNITE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384269#comment-14384269 ]
Dmitriy Setrakyan commented on IGNITE-180:
------------------------------------------
Even though the caches should be started dynamically, we also need a way to reuse a cache. For example, in case of collocated queues or sets, you may end up with many queues or sets deployed in the system. Having a separate cache for all of them may be overwhelming for the system.
> Use dynamic cache start for queue and set
> -----------------------------------------
>
> Key: IGNITE-180
> URL: https://issues.apache.org/jira/browse/IGNITE-180
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
> Reporter: Semen Boikov
> Assignee: Sergey Evdokimov
> Priority: Blocker
> Fix For: sprint-3
>
>
> When IGNITE-45 is implemented need to use dynamic cache start for caches used by IgniteQueue and IgniteSet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)