[JBoss JIRA] (ISPN-4426) Transaction replayed but not committed
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4426?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-4426:
------------------------------------
[~rvansa] could you add some logs?
> Transaction replayed but not committed
> --------------------------------------
>
> Key: ISPN-4426
> URL: https://issues.jboss.org/browse/ISPN-4426
> Project: Infinispan
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: State Transfer
> Affects Versions: 7.0.0.Alpha4
> Reporter: Radim Vansa
> Assignee: Dan Berindei
> Priority: Critical
> Labels: 63gablocker
>
> Dist TX cache, node C is joining. In previous topology, entry is owned by A (primary) and B (backup). In new topology, primary ownership is transferred to C, B stays backup.
> 1. TX is prepared in old topology and is being committed, when topology changes
> 2. on C (the new owner), the TX info is received and later even the old entry
> 3. C receives the CommitCommand, therefore, it correctly replays the PrepareCommand.
> 4. When the entries are about to be committed, in TxInterceptor the transaction is found to be already completed as it has lower TxID.
> Result: the transaction is not being executed and stale data stay on the node (with my algortihm it eventually led to complete entry loss).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (ISPN-4070) Server plugin for RHQ needs extensions in management/monitoring
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4070?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4070:
-----------------------------------------------
William Burns <wburns(a)redhat.com> changed the Status of [bug 1072349|https://bugzilla.redhat.com/show_bug.cgi?id=1072349] from NEW to POST
> Server plugin for RHQ needs extensions in management/monitoring
> ---------------------------------------------------------------
>
> Key: ISPN-4070
> URL: https://issues.jboss.org/browse/ISPN-4070
> Project: Infinispan
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMX, reporting and management
> Affects Versions: 6.0.1.Final
> Reporter: Tomas Sykora
> Assignee: William Burns
> Labels: 630, 63gablocker
>
> InVM plugin for RHQ is generated automatically. However, the plugin for server is not and those are results of deeper analysis of RHQ ISPN server plugin (missing) possibilities.
> JCONSOLE is showing number of statistics, traits and operations which are not incorporated in RHQ-plugin (*server* plugin). Some are quite important (start and stop ops for cache for example) and some might be only additional, not necessary - but still pleasant, information about a cluster/cache.
> *Missing Cache traits:*
> cacheName
> version
> configurationAsProperties
> statisticsEnabled
> *Missing from Cache statistics:*
> averageRemoveTime
> *Missing cache operations:*
> START and STOP are missing!!
> synchronizeData, disconnectSource, recordKnownGlobalKeyset - rolling upgrades related ops
> *Missing cache manager traits:*
> definedCacheCount
> globalConfigurationAsProperties
> clusterMembers
> createdCacheCounts
> definedCacheNames
> clusterSize
> version
> runningCacheCount
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (ISPN-4426) Transaction replayed but not committed
by Martin Gencur (JIRA)
[ https://issues.jboss.org/browse/ISPN-4426?page=com.atlassian.jira.plugin.... ]
Martin Gencur updated ISPN-4426:
--------------------------------
Labels: 63gablocker (was: )
> Transaction replayed but not committed
> --------------------------------------
>
> Key: ISPN-4426
> URL: https://issues.jboss.org/browse/ISPN-4426
> Project: Infinispan
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: State Transfer
> Affects Versions: 7.0.0.Alpha4
> Reporter: Radim Vansa
> Assignee: Dan Berindei
> Priority: Critical
> Labels: 63gablocker
>
> Dist TX cache, node C is joining. In previous topology, entry is owned by A (primary) and B (backup). In new topology, primary ownership is transferred to C, B stays backup.
> 1. TX is prepared in old topology and is being committed, when topology changes
> 2. on C (the new owner), the TX info is received and later even the old entry
> 3. C receives the CommitCommand, therefore, it correctly replays the PrepareCommand.
> 4. When the entries are about to be committed, in TxInterceptor the transaction is found to be already completed as it has lower TxID.
> Result: the transaction is not being executed and stale data stay on the node (with my algortihm it eventually led to complete entry loss).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months