[JBoss JIRA] (ISPN-11845) SingleFileStore location validation should be skipped when global state is disabled
by Paul Ferraro (Jira)
Paul Ferraro created ISPN-11845:
-----------------------------------
Summary: SingleFileStore location validation should be skipped when global state is disabled
Key: ISPN-11845
URL: https://issues.redhat.com/browse/ISPN-11845
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 10.1.8.Final
Reporter: Paul Ferraro
If global state is disabled, SingleFileStore should be allowed to be located anywhere. Currently, WF fails to start if launched from, say, /tmp - since the persistence location default to ~/, even though WF disables global state.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11842) Upgrade to 2.3 Spring-Boot and Spring dependencies
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-11842?page=com.atlassian.jira.plugi... ]
Katia Aresti updated ISPN-11842:
--------------------------------
Description:
Spring-Boot 2.3 has been released
Align to the latest versions
Spring 5, 5.2.3.RELEASE
Spring Session 2.3.0.RELEASE
was:
Spring-Boot 2.3 has been released
Align to the latest versions
Spring Security 5.3.2.RELEASE
Spring Integration 5.3.0.RELEASE
Spring Session 2.3.0.RELEASE
> Upgrade to 2.3 Spring-Boot and Spring dependencies
> --------------------------------------------------
>
> Key: ISPN-11842
> URL: https://issues.redhat.com/browse/ISPN-11842
> Project: Infinispan
> Issue Type: Component Upgrade
> Components: Spring Integration
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
>
> Spring-Boot 2.3 has been released
> Align to the latest versions
> Spring 5, 5.2.3.RELEASE
> Spring Session 2.3.0.RELEASE
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11424) Deprecate StorageType Configuration in favour of MediaType
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11424?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-11424:
-------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/8240, https://github.com/infinispan/infinispan/pull/8333 (was: https://github.com/infinispan/infinispan/pull/8240)
> Deprecate StorageType Configuration in favour of MediaType
> ----------------------------------------------------------
>
> Key: ISPN-11424
> URL: https://issues.redhat.com/browse/ISPN-11424
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 11.0.0.Alpha2
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 11.0.0.CR1
>
>
> Currently caches have configuration to specify memory storing aspects that affects eviction, e.g.
> {code:xml}
> <memory>
> <object size="20000"/>
> </memory>
> {code}
> {code:xml}
> <memory>
> <off-heap size="10000000" eviction="MEMORY"/>
> </memory>
> {code}
> {code:xml}
> <memory>
> <binary strategy="EXCEPTION" eviction="MEMORY" size="5000"/>
> </memory>
> {code}
> Each of those configurations affect the format that the data will be stored, being {{object}} the default on-heap storage, {{off-heap}} the {{byte[]}} out of heap storage and {{binary}} an on-heap format that mix {{byte[]}}, {{String}} and primitives.
> This ticket proposes to have the {{MediaType}} of the keys and values to dictate the storage format, and let the {{<memory>}} element to be responsible to choose between on-heap and off-heap storage, eliminating the {{Binary}} option altogether. The configuration would be something like:
> {code:xml}
> <!-- Default configuration, heap storage with POJOs -->
> <memory storage="heap">
> <eviction size="20000"/>
> </memory>
> {code}
> {code:xml}
> <!-- Storing java serialized objects, on-heap -->
> <encoding>
> <key media-type="application/x-java-serialized-object"/>
> <value media-type="application/x-java-serialized-object"/>
> </encoding>
> <memory storage="heap">
> <eviction size="20000"/>
> </memory>
> {code}
> {code:xml}
> <!-- Off-heap configuration, in protobuf format -->
> <encoding>
> <key media-type="application/x-protostream"/>
> <value media-type="application/x-protostream"/>
> </encoding>
> <memory storage="off-heap">
> <eviction size="10000000" eviction="MEMORY"/>
> </memory>
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11802) Create SPI for Cross-Site Replication conflict resolution
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-11802?page=com.atlassian.jira.plugi... ]
Pedro Ruivo updated ISPN-11802:
-------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8332
> Create SPI for Cross-Site Replication conflict resolution
> ---------------------------------------------------------
>
> Key: ISPN-11802
> URL: https://issues.redhat.com/browse/ISPN-11802
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Cross-Site Replication
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
>
> A conflict happens if 2 sites try to update the same key (put/remove) concurrently.
> With async Cross-Site Replication (aka IRAC) when a conflict is detected, we use the site name to pick the winning update.
> h2. Interface
> {code:java}
> interface ABC<V> { // or concrete class
> String site(); //the site name which wrote this value
> V value(); // the value. can be null if the key was removed
> Metadata metadata(); //can be null
> }
> interface Resolve<K, V> {
> ABC<V> resolve(K key, ABC<V> entry1, ABC<V> entry2);
> }
> {code}
> h2. Configuration
> Set the class name to use. Can be a {{Class}} object (as shown above) or a {{String}} with the class name.
> For server mode, you need to add your jar with the classes required to {{server/lib}}.
> The configuration fails to validate if the conflict resolution class is set with {{SYNC}} strategy.
> {code:java}
> ConfigurationBuilder.sites().addBackup()
> .site("S")
> .strategy(BackupConfiguration.BackupStrategy.ASYNC)
> .conflictResolution(MyResover.class);
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11843) Upgrade SB starter to 2.3
by Katia Aresti (Jira)
Katia Aresti created ISPN-11843:
-----------------------------------
Summary: Upgrade SB starter to 2.3
Key: ISPN-11843
URL: https://issues.redhat.com/browse/ISPN-11843
Project: Infinispan
Issue Type: Component Upgrade
Components: Spring Integration
Reporter: Katia Aresti
Assignee: Katia Aresti
once 11.x and 10.x next versions are ready, upgrade the starter and the SB version targeted
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months