[JBoss JIRA] (ISPN-4949) Split brain: inconsistent data after merge
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4949?page=com.atlassian.jira.plugin.... ]
Dan Berindei edited comment on ISPN-4949 at 12/10/14 6:30 AM:
--------------------------------------------------------------
The timeout for the `prepare(ABC)` RPC is 4 minutes by default, and it's expected to always be above the time it takes JGroups to suspect a node. In fact, I might make it a full day just to be sure ;)
was (Author: dan.berindei):
The timeout is 4 minutes by default, and it's expected to always be above the time it takes JGroups to suspect a node. In fact, I might make it a full day just to be sure ;)
> Split brain: inconsistent data after merge
> ------------------------------------------
>
> Key: ISPN-4949
> URL: https://issues.jboss.org/browse/ISPN-4949
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 7.0.0.Final
> Reporter: Radim Vansa
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 7.1.0.Alpha1
>
>
> 1) cluster A, B, C, D splits into 2 parts:
> A, B (coord A) finds this out immediately and enters degraded mode with CH [A, B, C, D]
> C, D (coord D) first detects that B is lost, gets view A, C, D and starts rebalance with CH [A, C, D]. Segment X is primary owned by C (it had backup on B but this got lost)
> 2) D detects that A was lost as well, therefore enters degraded mode with CH [A, C, D]
> 3) C inserts entry into X: all owners (only C) is present, therefore the modification is allowed
> 4) cluster is merged and coordinator finds out that the max stable topology has CH [A, B, C, D] (it is the older of the two partitions' topologies, got from A, B) - logs 'No active or unavailable partitions, so all the partitions must be in degraded mode' (yes, all partitions are in degraded mode, but write has happened in the meantime)
> 5) The old CH is broadcast in newest topology, no rebalance happens
> 6) Inconsistency: read in X may miss the update
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4949) Split brain: inconsistent data after merge
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/ISPN-4949?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on ISPN-4949:
--------------------------------
Which timeout ? The timeout to wait for a new (JGroups) view installation ? And if no new view is installed, you're installing the new topology based on the last JGroups view ?
OK, makes sense
> Split brain: inconsistent data after merge
> ------------------------------------------
>
> Key: ISPN-4949
> URL: https://issues.jboss.org/browse/ISPN-4949
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 7.0.0.Final
> Reporter: Radim Vansa
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 7.1.0.Alpha1
>
>
> 1) cluster A, B, C, D splits into 2 parts:
> A, B (coord A) finds this out immediately and enters degraded mode with CH [A, B, C, D]
> C, D (coord D) first detects that B is lost, gets view A, C, D and starts rebalance with CH [A, C, D]. Segment X is primary owned by C (it had backup on B but this got lost)
> 2) D detects that A was lost as well, therefore enters degraded mode with CH [A, C, D]
> 3) C inserts entry into X: all owners (only C) is present, therefore the modification is allowed
> 4) cluster is merged and coordinator finds out that the max stable topology has CH [A, B, C, D] (it is the older of the two partitions' topologies, got from A, B) - logs 'No active or unavailable partitions, so all the partitions must be in degraded mode' (yes, all partitions are in degraded mode, but write has happened in the meantime)
> 5) The old CH is broadcast in newest topology, no rebalance happens
> 6) Inconsistency: read in X may miss the update
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-3561) A joining cache should receive the rebalancedEnabled flag from the coordinator.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3561?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3561:
-----------------------------------------------
Dan Berindei <dberinde(a)redhat.com> changed the Status of [bug 1172550|https://bugzilla.redhat.com/show_bug.cgi?id=1172550] from NEW to ASSIGNED
> A joining cache should receive the rebalancedEnabled flag from the coordinator.
> -------------------------------------------------------------------------------
>
> Key: ISPN-3561
> URL: https://issues.jboss.org/browse/ISPN-3561
> Project: Infinispan
> Issue Type: Feature Request
> Components: State Transfer
> Affects Versions: 5.2.7.Final, 5.3.0.Final, 6.0.0.Beta1
> Reporter: Erik Salter
> Assignee: Erik Salter
> Fix For: 7.1.0.Beta1, 7.1.0.Final
>
>
> There is an issue when starting up a set of nodes in a cluster where the coordinator has told the surviving members that state transfer has been disabled. If rebalancing is disabled while the cluster is running it's disabled on all the
> However, if a new set of nodes join afterwards, they don't know that rebalancing was disabled.
> This has consequences if there is a new coordinator elected (like during a MERGE) from the set of newly-started nodes.
> To prevent this and ensure the greatest probablility of success, a node joining should get the state of this flag from the response from the coordinator.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-3561) A joining cache should receive the rebalancedEnabled flag from the coordinator.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3561?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-3561:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1172550
> A joining cache should receive the rebalancedEnabled flag from the coordinator.
> -------------------------------------------------------------------------------
>
> Key: ISPN-3561
> URL: https://issues.jboss.org/browse/ISPN-3561
> Project: Infinispan
> Issue Type: Feature Request
> Components: State Transfer
> Affects Versions: 5.2.7.Final, 5.3.0.Final, 6.0.0.Beta1
> Reporter: Erik Salter
> Assignee: Erik Salter
> Fix For: 7.1.0.Beta1, 7.1.0.Final
>
>
> There is an issue when starting up a set of nodes in a cluster where the coordinator has told the surviving members that state transfer has been disabled. If rebalancing is disabled while the cluster is running it's disabled on all the
> However, if a new set of nodes join afterwards, they don't know that rebalancing was disabled.
> This has consequences if there is a new coordinator elected (like during a MERGE) from the set of newly-started nodes.
> To prevent this and ensure the greatest probablility of success, a node joining should get the state of this flag from the response from the coordinator.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5048) Relocate some imported packages in uberjars and remove any javax.* classes
by Ion Savin (JIRA)
[ https://issues.jboss.org/browse/ISPN-5048?page=com.atlassian.jira.plugin.... ]
Ion Savin updated ISPN-5048:
----------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Relocate some imported packages in uberjars and remove any javax.* classes
> --------------------------------------------------------------------------
>
> Key: ISPN-5048
> URL: https://issues.jboss.org/browse/ISPN-5048
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Affects Versions: 7.0.2.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 7.1.0.Final, 7.0.3.Final
>
>
> There is a readme in the jar for infinispan-embedded-query which states: "Copyright (c) 2008, 2009 Sun Microsystems, Oracle Corporation. All rights reserved."
> In /META-INF there are notices claiming that all of this is licensed as ASL2 which is not correct.
> we also include things like javax.persistence and javax.servlet, those are going to cause trouble for sure as I don't think it's reasonable to expect the users to not have duplicates of such things in their classpath.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4433) Can not run INFINISPAN testsuite with JDK8
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4433?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4433:
-----------------------------------------------
Roman Macor <rmacor(a)redhat.com> changed the Status of [bug 1084904|https://bugzilla.redhat.com/show_bug.cgi?id=1084904] from ON_QA to ASSIGNED
> Can not run INFINISPAN testsuite with JDK8
> -------------------------------------------
>
> Key: ISPN-4433
> URL: https://issues.jboss.org/browse/ISPN-4433
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Affects Versions: 7.0.0.Alpha4
> Reporter: Vitalii Chepeliuk
> Assignee: Mircea Markus
> Fix For: 7.0.0.Alpha5
>
>
> {noformat}
> [ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (default) on project infinispan-cachestore-jdbc: Execution default of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check failed. IllegalArgumentException -> [Help 1]
> [ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (default) on project infinispan-lucene-v3: Execution default of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check failed. IllegalArgumentException -> [Help 1]
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack (unpack) on project infinispan-lucene-directory: Artifact has not been packaged yet. When used on reactor artifact, unpack should be executed after packaging: see MDEP-98. -> [Help 2]
> [ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (default) on project infinispan-query: Execution default of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check failed. IllegalArgumentException -> [Help 1]
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project infinispan-tools: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/edg-60-ispn-testsuite-rhel/89fa96e5/infinispan/tools/src/main/java/org/infinispan/tools/doclet/jmx/JmxDoclet.java:[67,32] cannot find symbol
> [ERROR] symbol: method getInstance()
> [ERROR] location: class com.sun.tools.doclets.formats.html.ConfigurationImpl
> [ERROR] /mnt/hudson_workspace/workspace/edg-60-ispn-testsuite-rhel/89fa96e5/infinispan/tools/src/main/java/org/infinispan/tools/doclet/jmx/JmxDoclet.java:[80,32] cannot find symbol
> [ERROR] symbol: method getInstance()
> [ERROR] location: class com.sun.tools.doclets.formats.html.ConfigurationImpl
> [ERROR] -> [Help 3]
> {noformat}
> Look on last Jenkins run with JDK8
> * RHEL5
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
> * RHEL6
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5071) No rebalance enabled and suspended messages logged
by Dan Berindei (JIRA)
Dan Berindei created ISPN-5071:
----------------------------------
Summary: No rebalance enabled and suspended messages logged
Key: ISPN-5071
URL: https://issues.jboss.org/browse/ISPN-5071
Project: Infinispan
Issue Type: Bug
Components: Core, State Transfer
Affects Versions: 7.0.2.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 7.1.0.Beta1
{{DefaultRebalancePolicy}} was logging a message at debug level when rebalance was enabled or disabled. We should add a similar message back in {{ClusterTopologyManagerImpl.setRebalancingEnabled}}.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months