Red Hat Bugzilla – Bug 1017707
6 hour and 24 hour metrics expire too soon
Last modified: 2014-04-23 08:31:25 EDT
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):
Steps to Reproduce:
Fix pushed to master.
commit hash: c115ca0dc5d1
Previous commit missed the the 6 hour ttl. It has been fixed and committed to master.
commit hash: fc05a8514
verified the mehtod in of source diff. .
please get attached the screen-shot
Created attachment 810973 [details]
Bulk closing of 4.10 issues.
If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.