March 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8838) Upgrade to Hibernate ORM 5.2.12.Final

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8838?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-8838: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/5766, https://github.com/infinispan/infinispan/pull/5862 (was: https://github.com/infinispan/infinispan/pull/5766) > Upgrade to Hibernate ORM 5.2.12.Final > ------------------------------------- > > Key: ISPN-8838 > URL: https://issues.jboss.org/browse/ISPN-8838 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Query > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.2.0.CR3, 9.2.0.Final > > > This upgrade is required to complete the upgrade of Hibernate Search ISPN-8779 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8903) Conflict resolution not initiated if node rejoins with same topology

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8903?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8903: ------------------------------- Description: The current logic in PreferAvailabilityStrategy and PreferConsistencyStrategy assumes that when a split brain occurs, the two partitions will continue to operate independently before a merge occurs. Consider a cluster \{A,B\} which partitions into P1 \{A\} and P2 \{B\}. P1 continues to operate and update cache entries, however P2 makes no progress (possibly down to a long GC pause). When P2 merges into P1, no conflict resolution occurs as the maxTopology contains all of the possible owners. Conflict resolution should be attempted in this scenario, as it's possible that entries have been put to P1 during the partition and therefore P2 will have stale values. This can be reproduced by creating two nodes, pausing one process, wait for split and then resuming the process. No CR will occur. was: The current logic in PreferAvailabilityStrategy and PreferConsistencyStrategy assumes that when a split brain occurs, the two partitions will continue to operate independently before a merge occurs. Consider a cluster \{A,B\} which partitions into P1 \{A\} and P2 \{C\}. P1 continues to operate and update cache entries, however P2 makes no progress (possibly down to a long GC pause). When P2 merges into P1, no conflict resolution occurs as the maxTopology contains all of the possible owners. Conflict resolution should be attempted in this scenario, as it's possible that entries have been put to P1 during the partition and therefore P2 will have stale values. This can be reproduced by creating two nodes, pausing one process, wait for split and then resuming the process. No CR will occur. > Conflict resolution not initiated if node rejoins with same topology > -------------------------------------------------------------------- > > Key: ISPN-8903 > URL: https://issues.jboss.org/browse/ISPN-8903 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Final, 9.2.1.Final > > > The current logic in PreferAvailabilityStrategy and PreferConsistencyStrategy assumes that when a split brain occurs, the two partitions will continue to operate independently before a merge occurs. > Consider a cluster \{A,B\} which partitions into P1 \{A\} and P2 \{B\}. P1 continues to operate and update cache entries, however P2 makes no progress (possibly down to a long GC pause). When P2 merges into P1, no conflict resolution occurs as the maxTopology contains all of the possible owners. Conflict resolution should be attempted in this scenario, as it's possible that entries have been put to P1 during the partition and therefore P2 will have stale values. > This can be reproduced by creating two nodes, pausing one process, wait for split and then resuming the process. No CR will occur. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8868) Expose force unlock with JMX

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8868?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8868: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.1.Final Resolution: Done > Expose force unlock with JMX > ---------------------------- > > Key: ISPN-8868 > URL: https://issues.jboss.org/browse/ISPN-8868 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > Fix For: 9.2.1.Final > > > Expose a way with JMX to force the release of a lock -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8951) LevelDB store parser should not exist past version 8.0

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8951?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8951: ---------------------------------- Fix Version/s: 9.3.0.Alpha1 > LevelDB store parser should not exist past version 8.0 > ------------------------------------------------------ > > Key: ISPN-8951 > URL: https://issues.jboss.org/browse/ISPN-8951 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Fix For: 9.3.0.Alpha1 > > > The LevelDB config parser should refuse to parse schemas newer than 8.0. Namespace-less XMLs should fail to parse with 9.x+ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8951) LevelDB store parser should not exist past version 8.0

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8951?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8951: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5865 > LevelDB store parser should not exist past version 8.0 > ------------------------------------------------------ > > Key: ISPN-8951 > URL: https://issues.jboss.org/browse/ISPN-8951 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > > The LevelDB config parser should refuse to parse schemas newer than 8.0. Namespace-less XMLs should fail to parse with 9.x+ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8953) Do not keep old schemas around in the source tree/distribution

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8953?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8953: ---------------------------------- Status: Open (was: New) > Do not keep old schemas around in the source tree/distribution > -------------------------------------------------------------- > > Key: ISPN-8953 > URL: https://issues.jboss.org/browse/ISPN-8953 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 9.2.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Alpha1 > > > We should only keep current schema files in the source tree. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8953) Do not keep old schemas around in the source tree/distribution

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8953?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8953: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5865 > Do not keep old schemas around in the source tree/distribution > -------------------------------------------------------------- > > Key: ISPN-8953 > URL: https://issues.jboss.org/browse/ISPN-8953 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 9.2.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Alpha1 > > > We should only keep current schema files in the source tree. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8952) Parser namespaces should support version wildcards

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8952?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8952: ---------------------------------- Status: Open (was: New) > Parser namespaces should support version wildcards > -------------------------------------------------- > > Key: ISPN-8952 > URL: https://issues.jboss.org/browse/ISPN-8952 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Final, 9.3.0.Alpha1 > > > The namespace annotations require a maintenance burden when bumping schema versions. By adding support for version wildcards with support boundaries (since, until) we can simplify maintenance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8952) Parser namespaces should support version wildcards

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8952?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8952: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5865 > Parser namespaces should support version wildcards > -------------------------------------------------- > > Key: ISPN-8952 > URL: https://issues.jboss.org/browse/ISPN-8952 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Final, 9.3.0.Alpha1 > > > The namespace annotations require a maintenance burden when bumping schema versions. By adding support for version wildcards with support boundaries (since, until) we can simplify maintenance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8951) LevelDB store parser should not exist past version 8.0

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8951?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8951: ---------------------------------- Status: Open (was: New) > LevelDB store parser should not exist past version 8.0 > ------------------------------------------------------ > > Key: ISPN-8951 > URL: https://issues.jboss.org/browse/ISPN-8951 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > > The LevelDB config parser should refuse to parse schemas newer than 8.0. Namespace-less XMLs should fail to parse with 9.x+ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2018