July 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-12102) Validate configuration before storing it

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12102?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12102: ----------------------------------- Fix Version/s: 12.0.0.Dev02 (was: 12.0.0.Dev01) > Validate configuration before storing it > ---------------------------------------- > > Key: ISPN-12102 > URL: https://issues.redhat.com/browse/ISPN-12102 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 11.0.1.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 12.0.0.Dev02 > > > Although {{ConfigurationBuilder}} does some validation, sometimes it needs something more. As an example, the cross-site replication needs a running {{Transport}} to check if xsite is really supported. > As a side effect, the console is broken when you try to define the following cache without {{RELAY2}} being present in the JGroups stack. > {code:xml} > <infinispan> > <cache-container> > <distributed-cache name="xsite"> > <backups> > <backup site="site2"/> > </backups> > </distributed-cache> > </cache-container> > </infinispan> > {code} > This happens because the {{Configuration}} is stored and the {{Cache}} with the exception is stored as well. > The fix proposed it adds a method to {{ModuleLifecyle}} where the {{Configuration}} can be validated before it is store in the "global state". -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11802) Create SPI for Cross-Site Replication conflict resolution

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11802?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11802: ----------------------------------- Fix Version/s: 12.0.0.Dev02 (was: 12.0.0.Dev01) > 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 > Fix For: 12.0.0.Dev02 > > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7166) WriteSkewConsistencyTest.testValidationOnlyInPrimaryOwner[DIST_SYNC] random failures

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-7166?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-7166: ---------------------------------- Fix Version/s: 12.0.0.Dev02 (was: 12.0.0.Dev01) > WriteSkewConsistencyTest.testValidationOnlyInPrimaryOwner[DIST_SYNC] random failures > ------------------------------------------------------------------------------------ > > Key: ISPN-7166 > URL: https://issues.redhat.com/browse/ISPN-7166 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 9.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 11.0.2.Final, 12.0.0.Dev02 > > > The test requires a key to have a specific primary owner and backup owner, but because is uses the default {{SynchronizedConsistentHashFactory}}, sometimes there's no segment meeting that requirement. > {noformat} > 16:52:02,516 ERROR (testng-WriteSkewConsistencyTest[DIST_SYNC]:[]) [TestSuiteProgress] Test failed: org.infinispan.container.versioning.WriteSkewConsistencyTest.testValidationOnlyInPrimaryOwner[DIST_SYNC] > java.lang.IllegalStateException: Could not find any segment owned by Cache '___defaultcache'@WriteSkewConsistencyTest[DIST_SYNC]-NodeB-47455, [Cache '___defaultcache'@WriteSkewConsistencyTest[DIST_SYNC]-NodeA-21455], primary segments: [33, 2, 3, 5, 37, 6, 41, 10, 45, 15, 48, 18, 50, 25, 59, 29], backup segments: {Cache '___defaultcache'@WriteSkewConsistencyTest[DIST_SYNC]-NodeA-21455=[35, 8, 40, 12, 14, 52, 21, 53, 22, 24, 57, 58, 27, 31]} > at org.infinispan.distribution.MagicKey.<init>(MagicKey.java:85) ~[test-classes/:?] > at org.infinispan.distribution.MagicKey.<init>(MagicKey.java:136) ~[test-classes/:?] > at org.infinispan.container.versioning.WriteSkewConsistencyTest.testValidationOnlyInPrimaryOwner(WriteSkewConsistencyTest.java:58) ~[test-classes/:?] > {noformat} > The test should either use a fixed key and accept random owners, or use a {{ControlledConsistentHashFactory}} to pin the owners. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12167) Remove the already deprecated ProtostreamSerializationContextInitializer

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12167?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12167: ----------------------------------- Fix Version/s: 12.0.0.Dev02 (was: 12.0.0.Dev01) > Remove the already deprecated ProtostreamSerializationContextInitializer > ------------------------------------------------------------------------ > > Key: ISPN-12167 > URL: https://issues.redhat.com/browse/ISPN-12167 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Affects Versions: 12.0.0.Dev01 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 12.0.0.Final, 12.0.0.Dev02 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12153) Anchored keys: make clustered/client listeners work

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12153?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12153: ----------------------------------- Fix Version/s: 12.0.0.Dev02 (was: 12.0.0.Dev01) > Anchored keys: make clustered/client listeners work > --------------------------------------------------- > > Key: ISPN-12153 > URL: https://issues.redhat.com/browse/ISPN-12153 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Affects Versions: 11.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Dev02 > > > Make sure the new value and the previous value available to listeners on the primary owner and that clustered/client listeners are notified correctly on updates. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12152) Remove the Kryo and Protostuff Marshallers

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12152?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12152: ----------------------------------- Fix Version/s: 12.0.0.Dev02 (was: 12.0.0.Dev01) > Remove the Kryo and Protostuff Marshallers > ------------------------------------------ > > Key: ISPN-12152 > URL: https://issues.redhat.com/browse/ISPN-12152 > Project: Infinispan > Issue Type: Sub-task > Components: Marshalling > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.0.0.Dev02 > > > We should remove the Kryo and Protostuff marsallers as they are no longer actively maintained and are seemingly not used by the community. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12151) Add error count metric

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12151?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12151: ----------------------------------- Fix Version/s: 12.0.0.Dev02 (was: 12.0.0.Dev01) > Add error count metric > ---------------------- > > Key: ISPN-12151 > URL: https://issues.redhat.com/browse/ISPN-12151 > Project: Infinispan > Issue Type: Feature Request > Components: Analytics > Affects Versions: 11.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Final, 12.0.0.Dev02 > > > {{CacheMgmtInterceptor}} has metrics for the different kind of key operations, but errors are not tracked. We should add a metric to count errors, and perhaps a histogram for the duration of failed invocations as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11924) Protostream Processor Dependency XML is incorrect

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11924?page=com.atlassian.jira.plugi... ] Nistor Adrian commented on ISPN-11924: -------------------------------------- Same for 11.0.x https://github.com/infinispan/infinispan/pull/8596 > Protostream Processor Dependency XML is incorrect > ------------------------------------------------- > > Key: ISPN-11924 > URL: https://issues.redhat.com/browse/ISPN-11924 > Project: Infinispan > Issue Type: Bug > Components: Documentation > Affects Versions: 11.0.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.Final > > > Currently the docs instruct the user to add {{protostream-processor}} to their {{dependenciesManagement}} section as a provided dependency. Instead it should be listed as a normal dependency on the modules required. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12154) Upgrade console to 0.8.Final

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12154?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12154: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 12.0.0.Dev01 Resolution: Done > Upgrade console to 0.8.Final > ---------------------------- > > Key: ISPN-12154 > URL: https://issues.redhat.com/browse/ISPN-12154 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Affects Versions: 11.0.1.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 12.0.0.Dev01 > > > Upgrade to latest release -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10249) Upgrade to Hibernate Search 6 and Lucene 8

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-10249?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-10249: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 12.0.0.Dev01 Resolution: Done > Upgrade to Hibernate Search 6 and Lucene 8 > ------------------------------------------ > > Key: ISPN-10249 > URL: https://issues.redhat.com/browse/ISPN-10249 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 11.0.0.Dev04 > Reporter: Nistor Adrian > Assignee: Fabio Massimo Ercoli > Priority: Major > Labels: SearchNG > Fix For: 12.0.0.Final, 12.0.0.Dev01 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2020