Bug 1017710

Summary: 6 hour and 24 hour metrics expire too soon
Product: [JBoss] JBoss Operations Network Reporter: John Sanda <jsanda>
Component: Core Server, Monitoring -- OtherAssignee: John Sanda <jsanda>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: ahovsepy, hrupp
Target Milestone: ER04   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1017707 Environment:
Last Closed: 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: 1017707    
Bug Blocks: 1012435    
Attachments:
Description Flags
storageTablesTTL none

Description John Sanda 2013-10-10 11:22:00 UTC
+++ This bug was initially created as a clone of Bug #1017707 +++

Description of problem:
We use Cassandra's time to live (TTL) feature to let metric data age out automatically without having to explicitly delete it. Both 6 hour and 24 hour data are getting stored with the 1 hour data TTLs. Here are the prepared statements used to store the respective data,

insertSixHourData = storageSession.prepare("INSERT INTO " + MetricsTable.SIX_HOUR + "(schedule_id, time, " +
            "type, value) VALUES (?, ?, ?, ?) USING TTL " + configuration.getOneHourTTL());

insertTwentyFourHourData = storageSession.prepare("INSERT INTO " + MetricsTable.TWENTY_FOUR_HOUR + "(schedule_id, " +
            "time, type, value) VALUES (?, ?, ?, ?) USING TTL " + configuration.getOneHourTTL());


They are both using configuration.getOneHourTTL(), but it should be configuration.getSixHourTTL() and configuration.getTwentyFourHourTTL() respectively.

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 2013-10-10 11:27:56 UTC
Fix pushed to release/jon3.2.x branch.

commit hash: 9eac4656276f

Comment 2 John Sanda 2013-10-10 13:35:26 UTC
Previous commit missed 6 hour ttl. I committed fix for this to release/jon3.2.x branch.

commit hash: 9a3eef65bb2ef6

Comment 3 Simeon Pinder 2013-10-24 04:09:38 UTC
Moving to ON_QA for testing in the next build.

Comment 4 Armine Hovsepyan 2013-11-11 10:07:37 UTC
Created attachment 822339 [details]
storageTablesTTL

Comment 5 Armine Hovsepyan 2013-11-11 10:08:40 UTC
corresponding changes are committed to jon3.2.x branch - see screen-shot attached
thank you