Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1178965 - Fail fast when using two phase commit with ASYNC backup strategy
Fail fast when using two phase commit with ASYNC backup strategy
Status: MODIFIED
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan (Show other bugs)
6.4.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 6.4.1
Assigned To: Tristan Tarrant
Martin Gencur
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-01-05 14:27 EST by Matej Čimbora
Modified: 2018-02-07 19:23 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
In Red Hat JBoss Data Grid, using the two phase commit with the ASYNC backup strategy results in one phase commit unexpectedly being used instead. This is a known issue in JBoss Data Grid 6.4 and no workaround is currently available for this issue.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker ISPN-5119 Major Resolved Fail fast when using two phase commit with ASYNC backup strategy 2018-02-07 19:35 EST

  None (edit)
Description Matej Čimbora 2015-01-05 14:27:05 EST
Example:
<backup site="LON" useTwoPhaseCommit="true" strategy="ASYNC"/>

From xsd (two-phase-commit):
Whether a backup will use a 2PC cycle for SYNC backups. Defaults to "false". NOTE: Not used for ASYNC backup strategies.
Comment 2 Martin Gencur 2015-01-08 04:29:53 EST
Hi Matej, could you please rephrase the description? It is not very clear what the problem is and what you want to achieve. Thanks
Comment 3 Matej Čimbora 2015-01-08 04:35:39 EST
Hi Martin, my idea was to throw an exception, whenever given example configuration combination is used (as the values do not get replicated to remote site in that case). Currently, user gets no feedback, so it might be pretty confusing.

Note You need to log in before you can comment on or make changes to this bug.