[infinispan-issues] [JBoss JIRA] (ISPN-8860) Lazy start counter's caches
Katia Aresti (JIRA)
issues at jboss.org
Mon Mar 19 14:02:00 EDT 2018
[ https://issues.jboss.org/browse/ISPN-8860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katia Aresti updated ISPN-8860:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
integrated, thanks !
> Lazy start counter's caches
> ---------------------------
>
> Key: ISPN-8860
> URL: https://issues.jboss.org/browse/ISPN-8860
> Project: Infinispan
> Issue Type: Enhancement
> Components: Clustered Counter
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
>
> Goal: if counter's are used, there is no need to start counter's caches!
> Main change:
> * remove {{__counter_configuration}} and use the {{state-cache}} to store counter's configuration
> Summary:
> * When the first counter is defined and stored in the {{state-cache}}, the {{__counter}} cache is started.
> * When a node joins, it starts the {{__counter}} cache if it finds a counter's configured stored
> * We need to persist the counter's configuration (for persisted counters only!) manually since the {{state-cache}} isn't persisted
> Issues
> * the {{state-cache}} is available during partitions! same counter can be defined with different configuration :(
> users have to deal with it while I can't find a way to resolve a conflict.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the infinispan-issues
mailing list