Bug 1033045

Summary:	Move "Message Replication" to "High Availability"
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Jochen Cordes <jcordes>
Component:	Documentation	Assignee:	Scott Mumford <smumford>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Russell Dickenson <rdickens>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.1	CC:	mnovak, nziakova, sgilda, smumford, twells
Target Milestone:	GA	Keywords:	Documentation, EasyFix, Triaged
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Build: CSProcessor Builder Version 1.12 Build Name: 19233, Administration and Configuration Guide-6.1-1 Build Date: 05-09-2013 10:36:48 Topic ID: 13565-377003 [Specified]
Last Closed:	2014-08-06 14:34:47 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 Jochen Cordes 2013-11-21 13:19:08 UTC

Title: HornetQ Message Replication

Describe the issue:

The section "Message Replication" belongs to the "High Availability" section as it is a second option besides using shared storage.



Suggestions for improvement:

It should go between

17.8.1. About HornetQ Shared Stores

and

17.8.2. About High-availability (HA) Failover

Also the introduction in "17.9.1. HornetQ Message Replication" saying

"HornetQ supports the ability to continue functioning after failure of one or more of the servers. Part of this is achieved through failover support where client connections migrate from the live server to a backup server in the event of the live server failing. To keep the backup server current, messages are replicated from the live server to the backup server continuously through two strategies: shared store and replication. This section covers the replication strategy.

Warning
Only persistent messages are replicated. Any non-persistent messages do not survive failover. "

would make a perfect candidate to go into a intro section of "17.8. High Availability" (and removed from "17.9.1. HornetQ Message Replication") in a slightly modified version in a sense that the last sentence should be

"The following two sections cover both strategies."

Additional information:

Comment 1 Scott Mumford 2014-02-17 03:58:05 UTC

The above changes have been made.

The updated version of the book is available for review at [1] immediately.

This bug will be moved to ON_QA once the update has been pushed to the docs stage.


1: http://docbuilder.usersys.redhat.com/22508/

Comment 2 Scott Mumford 2014-02-26 05:14:10 UTC

Moving to ON_QA.

The changes should be available for review on the documentation stage within an hour or so from this comment.

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/

Comment 3 Scott Mumford 2014-02-26 05:15:57 UTC

Moving to ON_QA.

The changes should be available for review on the documentation stage within an hour or so from this comment.

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/

Comment 4 Miroslav Novak 2014-02-26 15:12:18 UTC

Hi Scott,

I can still see chapter "17.9. Message Replication" in: 
http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/

Can you check it, please?

Thanks,
Mirek

Comment 5 Scott Mumford 2014-02-26 21:03:01 UTC

Miroslav,

The section in question appears to have been moved as requested when I view the book: 

17.8. High Availability
17.8.1. High Availability Introduction
17.8.2. About HornetQ Shared Stores
17.8.3. HornetQ Message Replication    <==
17.8.4. About High-availability (HA) Failover
17.8.5. Deployments on HornetQ Backup Servers
17.9. Message Replication
17.9.1. Configuring the HornetQ Servers for Replication
18. Transaction Subsystem

Can you ensure you're reviewing version 6.3.0-2	built on Wednesday Feb 26 and do a hard refresh of your browser to ensure you pick up the changes.

Comment 6 Miroslav Novak 2014-02-27 08:29:18 UTC

Hi Scott,

it seems that I've already seen updated version. There are still chapters:
17.9. Message Replication
17.9.1. Configuring the HornetQ Servers for Replication

which I believe should be also in 17.8. High Availability.

Thanks,
Mirek

Comment 7 Scott Mumford 2014-02-27 22:56:38 UTC

Oh, my apologies Miroslav, I misunderstood that you were asking that the entire "Message Replication" chapter be moved, rather than just the "HornetQ Message Replication" section.

I've moved "Configuring the HornetQ Servers for Replication" section to beneath the "HornetQ Message Replication" section in the 'High Availability' chapter. 

There is no 'Message Replication' chapter any longer.

The new ToC looks like this:
17.8. High Availability
17.8.1. High Availability Introduction
17.8.2. About HornetQ Shared Stores
17.8.3. HornetQ Message Replication
17.8.4. Configuring the HornetQ Servers for Replication
17.8.5. About High-availability (HA) Failover
17.8.6. Deployments on HornetQ Backup Servers
18. Transaction Subsystem

The change is available for perusal at:
http://docbuilder.usersys.redhat.com/22508/

Moving this ticket to MODIFIED until the book is republished to the docs stage for verification.

Sorry again for the misunderstanding, Miroslav.

Comment 8 Scott Mumford 2014-03-10 03:14:31 UTC

The above changes are available for review on the documentation stage at:
http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Administration_and_Configuration_Guide/index.html#sect-High_Availability

Comment 9 Miroslav Novak 2014-04-02 12:16:25 UTC

Hi Scott,

thanks for updates and don't worry about it. We'll have to rewrite this 17.8 chapter almost from scratch anyway as it appears to be missing configuration examples and deeper description of behaviour dedicated/colocated topology with shared/replicated journal. There are other BZs which should address this. 

I'm setting this BZ as verified since the reported issue is fixed.

Thanks,
Mirek