December 2018 - infinispan-issues

[JBoss JIRA] (ISPN-4806) Provide server configuration for the Soft Index File Store

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-4806?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-4806: ------------------------------- Status: Open (was: New) > Provide server configuration for the Soft Index File Store > ---------------------------------------------------------- > > Key: ISPN-4806 > URL: https://issues.jboss.org/browse/ISPN-4806 > Project: Infinispan > Issue Type: Task > Affects Versions: 9.4.3.Final > Reporter: Gustavo Fernandes > Assignee: Ryan Emerson > Priority: Major > Labels: hackathon > Fix For: 10.0.0.Alpha2 > > > Soft index file store was introduced on ISPN-3921 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4806) Provide server configuration for the Soft Index File Store

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-4806?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-4806: ------------------------------- Component/s: Server > Provide server configuration for the Soft Index File Store > ---------------------------------------------------------- > > Key: ISPN-4806 > URL: https://issues.jboss.org/browse/ISPN-4806 > Project: Infinispan > Issue Type: Task > Components: Server > Affects Versions: 9.4.3.Final > Reporter: Gustavo Fernandes > Assignee: Ryan Emerson > Priority: Major > Labels: hackathon > Fix For: 10.0.0.Alpha2 > > > Soft index file store was introduced on ISPN-3921 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4806) Provide server configuration for the Soft Index File Store

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-4806?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-4806: ------------------------------- Affects Version/s: 9.4.3.Final > Provide server configuration for the Soft Index File Store > ---------------------------------------------------------- > > Key: ISPN-4806 > URL: https://issues.jboss.org/browse/ISPN-4806 > Project: Infinispan > Issue Type: Task > Affects Versions: 9.4.3.Final > Reporter: Gustavo Fernandes > Assignee: Ryan Emerson > Priority: Major > Labels: hackathon > Fix For: 10.0.0.Alpha2 > > > Soft index file store was introduced on ISPN-3921 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4806) Provide server configuration for the Soft Index File Store

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-4806?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-4806: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6503 > Provide server configuration for the Soft Index File Store > ---------------------------------------------------------- > > Key: ISPN-4806 > URL: https://issues.jboss.org/browse/ISPN-4806 > Project: Infinispan > Issue Type: Task > Affects Versions: 9.4.3.Final > Reporter: Gustavo Fernandes > Assignee: Ryan Emerson > Priority: Major > Labels: hackathon > Fix For: 10.0.0.Alpha2 > > > Soft index file store was introduced on ISPN-3921 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9714) Update CacheNotifier to return CompletionStage

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9714?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-9714: ------------------------------------ (n) to invoke all current listeners on the notification thread pool, I think it would be better to assume that they do not block and keep executing them synchronously. > Update CacheNotifier to return CompletionStage > ---------------------------------------------- > > Key: ISPN-9714 > URL: https://issues.jboss.org/browse/ISPN-9714 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Listeners > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Alpha2 > > > We need to update CacheNotifier to return CompletionStage for all its appropriate methods. We also need to update all the internals to use these appropriately. > Not all notification usages may provide support non blocking, but our listener internals should support non blocking listeners for all. > The simplest way internally is to treat all current listeners as "alien" and invoke them in the notification thread pool. If it is sync we would wait for this task to complete. We would also now allow a listener to return a CompletionStage. If this is returned we will use this operate in a non blocking way. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9795) Make the elasticsearch modules optional in the server

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9795?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9795: ---------------------------------- Sprint: Sprint 10.0.0.Alpha2 > Make the elasticsearch modules optional in the server > ----------------------------------------------------- > > Key: ISPN-9795 > URL: https://issues.jboss.org/browse/ISPN-9795 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 10.0.0.Alpha1, 9.4.3.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Alpha2, 9.4.4.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9795) Make the elasticsearch modules optional in the server

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-9795: ------------------------------------- Summary: Make the elasticsearch modules optional in the server Key: ISPN-9795 URL: https://issues.jboss.org/browse/ISPN-9795 Project: Infinispan Issue Type: Enhancement Components: Server Affects Versions: 9.4.3.Final, 10.0.0.Alpha1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.Alpha2, 9.4.4.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9794) Allow Cache flushes to stores on demand via JMX trigger

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9794?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9794: ------------------------------- Description: We should introduce a {code}flush(Publisher<MarshalledEntry<K, V>>){code} method to the AdvancedCacheWriter interface. This will simply iterate over the cache on a best-effort basis (concurrent updates to the cache may be missed) and write it's contents to the underlying store(s). The flush method should be called by the PersistenceManager when an appropriate trigger has been manually called by the user, for example JMX or REST. Adding this capability will allow for use-cases where users don't want to write to the underlying store during normal operation, however in certain circumstances they want to persist the data. To achieve this, the user can configure a store as normal, whilst setting the SKIP_CACHE_LOAD and SKIP_CACHE_STORE flags via AdvancedCache::withFlags. Alternatively, we could introduce a new attribute to store's which ensures that the store is always skipped except when flushing, e.g. "flush-only". This has the advantage of not requiring users to utilise flags and it will be possible to have multiple stores, some flush-only and other write-through/write-behind. was: We should introduce a {code}flush(Publisher<MarshalledEntry<K, V>>){code} method to the AdvancedCacheWriter interface. This will simply iterate over the cache on a best-effort basis (concurrent updates to the cache may be missed) and write it's contents to the underlying store(s). The flush method should be called by the PersistenceManager when an appropriate trigger has been manually called by the user, for example JMX or REST. Adding this capability will allow for use-cases where users don't want to write to the underlying store during normal operation, however in certain circumstances they want to persist the data. To achieve this, the user can configure a store as normal, whilst setting the SKIP_CACHE_LOAD and SKIP_CACHE_STORE flags via AdvancedCache::withFlags. Alternatively, we could also introduce a new attribute to store's which ensures that the store is always skipped except when flushing, e.g. "flush-only". > Allow Cache flushes to stores on demand via JMX trigger > ------------------------------------------------------- > > Key: ISPN-9794 > URL: https://issues.jboss.org/browse/ISPN-9794 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Final > > > We should introduce a {code}flush(Publisher<MarshalledEntry<K, V>>){code} method to the AdvancedCacheWriter interface. This will simply iterate over the cache on a best-effort basis (concurrent updates to the cache may be missed) and write it's contents to the underlying store(s). > The flush method should be called by the PersistenceManager when an appropriate trigger has been manually called by the user, for example JMX or REST. > Adding this capability will allow for use-cases where users don't want to write to the underlying store during normal operation, however in certain circumstances they want to persist the data. To achieve this, the user can configure a store as normal, whilst setting the SKIP_CACHE_LOAD and SKIP_CACHE_STORE flags via AdvancedCache::withFlags. > Alternatively, we could introduce a new attribute to store's which ensures that the store is always skipped except when flushing, e.g. "flush-only". This has the advantage of not requiring users to utilise flags and it will be possible to have multiple stores, some flush-only and other write-through/write-behind. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9794) Allow Cache flushes to stores on demand via JMX trigger

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9794?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9794: ------------------------------- Description: We should introduce a {code}flush(Publisher<MarshalledEntry<K, V>>){code} method to the AdvancedCacheWriter interface. This will simply iterate over the cache on a best-effort basis (concurrent updates to the cache may be missed) and write it's contents to the underlying store(s). The flush method should be called by the PersistenceManager when an appropriate trigger has been manually called by the user, for example JMX or REST. Adding this capability will allow for use-cases where users don't want to write to the underlying store during normal operation, however in certain circumstances they want to persist the data. To achieve this, the user can configure a store as normal, whilst setting the SKIP_CACHE_LOAD and SKIP_CACHE_STORE flags via AdvancedCache::withFlags. Alternatively, we could also introduce a new attribute to store's which ensures that the store is always skipped except when flushing, e.g. "flush-only". was: We should introduce a {code}flush(Publisher<MarshalledEntry<K, V>>){code} method to the AdvancedCacheWriter interface. This will simply iterate over the cache on a best-effort basis (concurrent updates to the cache may be missed) and write it's contents to the underlying store(s). The flush method should be called by the PersistenceManager when an appropriate trigger has been manually called by the user, for example JMX or REST. Adding this capability will allow for use-cases where users don't want to write to the underlying store during normal operation, however in certain circumstances they want to persist the data. To achieve this, the user can configure a store as normal, whilst setting the SKIP_CACHE_LOAD and SKIP_CACHE_STORE flags via AdvancedCache::withFlags. > Allow Cache flushes to stores on demand via JMX trigger > ------------------------------------------------------- > > Key: ISPN-9794 > URL: https://issues.jboss.org/browse/ISPN-9794 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Final > > > We should introduce a {code}flush(Publisher<MarshalledEntry<K, V>>){code} method to the AdvancedCacheWriter interface. This will simply iterate over the cache on a best-effort basis (concurrent updates to the cache may be missed) and write it's contents to the underlying store(s). > The flush method should be called by the PersistenceManager when an appropriate trigger has been manually called by the user, for example JMX or REST. > Adding this capability will allow for use-cases where users don't want to write to the underlying store during normal operation, however in certain circumstances they want to persist the data. To achieve this, the user can configure a store as normal, whilst setting the SKIP_CACHE_LOAD and SKIP_CACHE_STORE flags via AdvancedCache::withFlags. Alternatively, we could also introduce a new attribute to store's which ensures that the store is always skipped except when flushing, e.g. "flush-only". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9794) Allow Cache flushes to stores on demand via JMX trigger

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-9794: ---------------------------------- Summary: Allow Cache flushes to stores on demand via JMX trigger Key: ISPN-9794 URL: https://issues.jboss.org/browse/ISPN-9794 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Affects Versions: 10.0.0.Alpha1 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.Final We should introduce a {code}flush(Publisher<MarshalledEntry<K, V>>){code} method to the AdvancedCacheWriter interface. This will simply iterate over the cache on a best-effort basis (concurrent updates to the cache may be missed) and write it's contents to the underlying store(s). The flush method should be called by the PersistenceManager when an appropriate trigger has been manually called by the user, for example JMX or REST. Adding this capability will allow for use-cases where users don't want to write to the underlying store during normal operation, however in certain circumstances they want to persist the data. To achieve this, the user can configure a store as normal, whilst setting the SKIP_CACHE_LOAD and SKIP_CACHE_STORE flags via AdvancedCache::withFlags. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2018