[JBoss JIRA] (ISPN-8921) KeyStream stream operations use entrySet on remote nodes
by William Burns (JIRA)
William Burns created ISPN-8921:
-----------------------------------
Summary: KeyStream stream operations use entrySet on remote nodes
Key: ISPN-8921
URL: https://issues.jboss.org/browse/ISPN-8921
Project: Infinispan
Issue Type: Bug
Components: Streams
Affects Versions: 9.2.0.Final
Reporter: William Burns
Assignee: William Burns
Fix For: 9.3.0.Final
Currently when a remote stream operation is performed it is always done using an entrySet. This causes a lot of overhead for keySet operations - especially if there is a store! We should support key based streams for remote nodes in addition to entry set.
There is nothing stopping this currently, all we should need is an additional argument for StreamIteratorRequestCommand to say if it is keyset or entry set. Then the LocalStreamManaterImpl and IteratorHandler need very minor tweaks. This should help operations such as size when using a store quite a bit depending on the store implementation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (ISPN-8860) Lazy start counter's caches
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-8860?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-8860:
------------------------------
Status: Open (was: New)
> 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)
6 years, 3 months
[JBoss JIRA] (ISPN-8860) Lazy start counter's caches
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-8860?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-8860:
------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/5822
> 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)
6 years, 3 months