Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 928288

Summary:	Replicated Journal - Illegal backup state if network failures present while initial journal replication from live
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Dmytro Pogrebniuk <dpogrebn>
Component:	HornetQ	Assignee:	Clebert Suconic <clebert.suconic>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	csuconic, mnovak, myarboro, nziakova, pslavice, rdickens
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	Cause: Consequence: Workaround (if any): Result: .	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-17 20:46:51 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 Dmytro Pogrebniuk 2013-03-27 10:14:57 UTC

Description of problem:
There is no retry for initial replication.

Version-Release number of selected component (if applicable):
2.3.0.CR1

Steps to Reproduce:
1. starting live
2. sending messages to live
3. simulating network problem
3.a. starting backup
4. receiving some messages from live
5. killing live
6. client unable to switch to backup

Comment 2 Clebert Suconic 2013-05-17 20:46:51 UTC

Of course.. if you failed before replication was synced.. then you're out of data, hence expected to no be able to failover