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

Bug 1077274

Summary:	Move baselines out of the RDMBS and into Cassandra
Product:	[JBoss] JBoss Operations Network	Reporter:	John Sanda <jsanda>
Component:	Core Server, Database, Storage Node	Assignee:	Michael Burman <miburman>
Status:	CLOSED EOL	QA Contact:	Mike Foley <mfoley>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	fbrychta, hrupp, myarboro
Target Milestone:	---
Target Release:	JON 4.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1066515	Environment:
Last Closed:	2019-08-05 14:49:28 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:
Bug Depends On:	1066515
Bug Blocks:

Description John Sanda 2014-03-17 15:46:39 UTC

+++ This bug was initially created as a clone of Bug #1066515 +++

Description of problem:
Calculating baselines can be a write-intensive operation. With numeric metrics already in Cassandra, we can really take advantage of Cassandra's wide row support in order to efficiently store, retrieve, and calculate baselines. We can also utilize the Time To Live (TTL) feature for expiring old baseline data.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 John Sanda 2014-08-27 21:12:05 UTC

I am bumping this to JON 4.0. It definitely is not going into 3.3, and I think it is unlikely to be a priority in any other 3.x releases.

Comment 3 Filip Brychta 2019-08-05 14:49:28 UTC

JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.