[JBoss JIRA] (ISPN-5078) RHQ Server Rebalancing value doesn't display properly
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-5078?page=com.atlassian.jira.plugin.... ]
William Burns commented on ISPN-5078:
-------------------------------------
So the read-resourece operation by default does not include runtime only attributes. Unfortunately RHQ does not allow an easy way to override what values are passed to the operation is ran without implementing the logic ourselves. It appears I will need to copy the ConfigurationLoadDelegate class and tweak it to allow for include-runtime.
> RHQ Server Rebalancing value doesn't display properly
> -----------------------------------------------------
>
> Key: ISPN-5078
> URL: https://issues.jboss.org/browse/ISPN-5078
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 7.0.2.Final
> Reporter: William Burns
>
> The rebalancing for a distributed/replicated cache is always displayed as undefined in RHQ even if the server has a value. This appears to be because the :read-resource operation always returns it as undefined. Using the ls command in jboss-cli.sh properly shows the value though.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (ISPN-5078) RHQ Server Rebalancing value doesn't display properly
by William Burns (JIRA)
William Burns created ISPN-5078:
-----------------------------------
Summary: RHQ Server Rebalancing value doesn't display properly
Key: ISPN-5078
URL: https://issues.jboss.org/browse/ISPN-5078
Project: Infinispan
Issue Type: Bug
Affects Versions: 7.0.2.Final
Reporter: William Burns
The rebalancing for a distributed/replicated cache is always displayed as undefined in RHQ even if the server has a value. This appears to be because the :read-resource operation always returns it as undefined. Using the ls command in jboss-cli.sh properly shows the value though.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (ISPN-5077) Custom remote events can be slightly inefficient
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-5077:
--------------------------------------
Summary: Custom remote events can be slightly inefficient
Key: ISPN-5077
URL: https://issues.jboss.org/browse/ISPN-5077
Project: Infinispan
Issue Type: Enhancement
Components: hot, Remote Protocols
Affects Versions: 7.0.2.Final
Reporter: Galder Zamarreño
Fix For: 8.0.0.Final
Something we might want to improve for Hot Rod 3.0 protocol:
[16:40] <galderz> i've been thinking further about converters, and I think i've found a slight mismatch between what converter means for embedded listeners vs remote listeners
[16:40] <wburns> oh yeah?
[16:40] <galderz> for embedded listeners, it essentially transforms what you see as `value`
[16:41] <galderz> with the knowledge that key and metadata information will be shipped
[16:41] <galderz> the way i mapped converter to remote listeners is that whatever the converter returns, we ship that, as is, to the client
[16:41] <galderz> so, if a remote listener wants a custom event that includes key + value
[16:41] <galderz> it needs to develop a converter impl that returns bytes containing key + value
[16:41] <galderz> which is inefficient because you are passing around the key twice
[16:42] <galderz> once as part of the event itself, and again inside the converted value
[16:42] <galderz> inefficient from the POV of shipping stuff around from other nodes to where the cluster listener is located
[16:44] <wburns> yeah makes sense
[16:44] <galderz> not a major issue but not easy to fix without changing semantics or public protocol
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (ISPN-5076) Pessimistic transactions can lose their locks when the primary owner changes
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5076?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-5076:
-------------------------------
Status: Open (was: New)
> Pessimistic transactions can lose their locks when the primary owner changes
> ----------------------------------------------------------------------------
>
> Key: ISPN-5076
> URL: https://issues.jboss.org/browse/ISPN-5076
> Project: Infinispan
> Issue Type: Bug
> Components: Core, State Transfer
> Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 7.1.0.Final
>
>
> In a pessimistic cache, if a transaction {{T1}} has a {{put(k, v})}} operation and the primary owner of the key is the originator, the lock is acquired on the originator but it is not replicated to on the backup(s).
> If one of the backup owners becomes the primary owner, it will allow another transaction {{T2}} to lock (and update) key {{k}} before it receives the one-phase prepare command from the originator of {{T1}}.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (ISPN-5076) Pessimistic transactions can lose their locks when the primary owner changes
by Dan Berindei (JIRA)
Dan Berindei created ISPN-5076:
----------------------------------
Summary: Pessimistic transactions can lose their locks when the primary owner changes
Key: ISPN-5076
URL: https://issues.jboss.org/browse/ISPN-5076
Project: Infinispan
Issue Type: Bug
Components: Core, State Transfer
Affects Versions: 7.1.0.Alpha1, 7.0.2.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Critical
Fix For: 7.1.0.Final
In a pessimistic cache, if a transaction {{T1}} has a {{put(k, v})}} operation and the primary owner of the key is the originator, the lock is acquired on the originator but it is not replicated to on the backup(s).
If one of the backup owners becomes the primary owner, it will allow another transaction {{T2}} to lock (and update) key {{k}} before it receives the one-phase prepare command from the originator of {{T1}}.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (ISPN-4949) Split brain: inconsistent data after merge
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4949?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4949:
-----------------------------------------------
Radim Vansa <rvansa(a)redhat.com> changed the Status of [bug 1161214|https://bugzilla.redhat.com/show_bug.cgi?id=1161214] from ON_QA to VERIFIED
> 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.11#6341)
11 years, 4 months