Bug 634745

Summary:	Need a release note relating to normal time required for Console to process messages on startup
Product:	Red Hat Enterprise MRG	Reporter:	Trevor McKay <tmckay>
Component:	Release_Notes	Assignee:	Lana Brindley <lbrindle>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	medium	Docs Contact:
Priority:	high
Version:	Development	CC:	jross, matt, mhideo, tross
Target Milestone:	1.3
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: There is a large amount of message traffic that the Console needs to process during startup. Consequence: There is a noticeable delay when the Console starts up during which the Console's various displays are not fully populated and during which operations from the Console may fail. Fix: This is normal behaviour. Result: The delay is difficult to quantify, but it is likely that this startup processing time will increase as the size of the total grid increases. On a typical development grid at Red Hat, it is normal for this startup time to be in the order of a minute or two. Depending on the location of the Console host in the overall network topology, this time could be significantly longer.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-10-14 20:44:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	548214

Description Trevor McKay 2010-09-16 21:04:30 UTC

Description of problem:

There is a noticeable period of time when the Console starts up during which the Console's various displays are not fully populated and during which operations from the Console may fail.  This is normal and is due to the amount of message traffic that the Console must process during startup.  The delay is difficult to quantify, but it is likely that this startup processing time will increase as the size of the total grid increases.

On a typical development grid at Red Hat, it is normal for this startup time to be on the order of a minute or two.  Depending on the location of the Console host in the overall network topology, this time could be significantly longer.

We need a release note to this effect for 1.3 so that users do not think there Console is broken if they experience delays during startup of the Console.

Comment 1 Trevor McKay 2010-09-16 21:06:31 UTC

Oh, forgot.

This relates directly to problems originally reported in BZs 621228 and 629316.

Comment 2 Lana Brindley 2010-09-20 20:32:19 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: There is a large amount of message traffic that the Console needs to process during startup.
Consequence: There is a noticeable delay when the Console starts up during which the Console's various displays are not fully populated and during which operations from the Console may fail.
Fix: This is normal behaviour.
Result: The delay is difficult to quantify, but it is likely that this startup processing time will increase as the size of the total grid increases. On a typical development grid at Red Hat, it is normal for this startup time to be in the order of a minute or two.  Depending on the location of the Console host in the overall network topology, this time could be significantly longer.

Comment 3 Lana Brindley 2010-09-23 03:59:42 UTC

Revision 0.1 of the release notes will available for review on the stage shortly.

LKB

Comment 4 Lana Brindley 2010-10-14 20:44:02 UTC

Release Notes have now  been published:
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.3/html/MRG_Release_Notes/index.html

LKB