Bug 690285

Summary: RFE: QMF Object publishing interval scoped to type
Product: Red Hat Enterprise MRG Reporter: Matthew Farrellee <matt>
Component: qpid-qmfAssignee: Ted Ross <tross>
Status: CLOSED EOL QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 1.3CC: jross, tross
Target Milestone: ---Keywords: FutureFeature, Improvement
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-21 14:52:56 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:

Description Matthew Farrellee 2011-03-23 19:32:46 UTC 
QMFv1 (and v2) as of 0.9.1079953-2, supports controlling the frequency at which an agent will broadcast updates to a broker (qpid::management::ManagementAgent::init(..., intervalSeconds, ...)). The frequency is scoped to the agent.

In a Grid deployment, a single agent will be publishing multiple types. For instance, the Schedd agent will publish classes Scheduler, Submitter, JobServer and Submission. See bug 689785.

Different types may have different freshness requirements. For instance, Submission data with an SLA of 15 seconds from condor_submit to visibility in Cumin, and Submitter data with a 30 second SLA.

Furthermore, in a scaled up system it becomes important to adjust the update intervals, often based on consumer performance.

The ability to specify the interval on a per class basis, at runtime, will satisfy this RFE.