Bug 1178965

Summary:	Fail fast when using two phase commit with ASYNC backup strategy
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Matej Čimbora <mcimbora>
Component:	Infinispan	Assignee:	Tristan Tarrant <ttarrant>
Status:	CLOSED UPSTREAM	QA Contact:	Martin Gencur <mgencur>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	chuffman, jdg-bugs
Target Milestone:	---
Target Release:	6.4.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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:	2025-02-10 03:43:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matej Čimbora 2015-01-05 19:27:05 UTC

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 09:29:53 UTC

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 09:35:39 UTC

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.

Comment 6 Red Hat Bugzilla 2025-02-10 03:43:50 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.