Hi, I am trying to cleanup the old records in the mysql DB which is present from Oct 2015.
I used below settings in the slurmdbd.conf file, but didn't get cleaned up any records last night. May be due to huge no:of records its not able to purge? How can we handle this situation? We want to keep only the records for one month. Whether we can able to delete it manually? *DB Size: * -rwxr-xr-x 1 mysql mysql *25813843968 *May 25 10:10 ibdata1 *slurmdbd.conf:* PurgeEventAfter=550days PurgeJobAfter=550days PurgeResvAfter=550days PurgeStepAfter=550days PurgeSuspendAfter=550days *Slurmdbd.log:* [2017-05-24T18:00:11.429] error: We have more allocated time than is possible (857310 > 417600) for cluster cluster(116) from 2017-05-24T17:00:00 - 2017-05-24T18:00:00 tres 1 [2017-05-24T18:00:11.446] Warning: Note very large processing time from hourly_rollup for cluster: usec=11415496 began=18:00:00.030 [2017-05-24T19:00:11.355] error: We have more allocated time than is possible (838571 > 417600) for cluster cluster(116) from 2017-05-24T18:00:00 - 2017-05-24T19:00:00 tres 1 [2017-05-24T19:00:11.369] Warning: Note very large processing time from hourly_rollup for cluster: usec=10920415 began=19:00:00.448 [2017-05-24T20:00:11.218] error: We have more allocated time than is possible (860964 > 417600) for cluster cluster(116) from 2017-05-24T19:00:00 - 2017-05-24T20:00:00 tres 1 [2017-05-24T20:00:11.239] Warning: Note very large processing time from hourly_rollup for cluster: usec=10867720 began=20:00:00.372 [2017-05-24T21:00:11.192] error: We have more allocated time than is possible (803602 > 417600) for cluster cluster(116) from 2017-05-24T20:00:00 - 2017-05-24T21:00:00 tres 1 [2017-05-24T21:00:11.207] Warning: Note very large processing time from hourly_rollup for cluster: usec=10964810 began=21:00:00.243 [2017-05-24T22:00:11.394] error: We have more allocated time than is possible (799539 > 417600) for cluster cluster(116) from 2017-05-24T21:00:00 - 2017-05-24T22:00:00 tres 1 [2017-05-24T22:00:11.408] Warning: Note very large processing time from hourly_rollup for cluster: usec=11197730 began=22:00:00.211 [2017-05-24T23:00:11.715] error: We have more allocated time than is possible (787641 > 417600) for cluster cluster(116) from 2017-05-24T22:00:00 - 2017-05-24T23:00:00 tres 1 [2017-05-24T23:00:11.727] Warning: Note very large processing time from hourly_rollup for cluster: usec=11315195 began=23:00:00.412 [2017-05-25T00:00:11.617] error: We have more allocated time than is possible (794632 > 417600) for cluster cluster(116) from 2017-05-24T23:00:00 - 2017-05-25T00:00:00 tres 1 [2017-05-25T00:00:11.632] Warning: Note very large processing time from hourly_rollup for cluster: usec=10902982 began=00:00:00.729 [2017-05-25T00:01:14.089] Warning: Note very large processing time from daily_rollup for cluster: usec=62456333 began=00:00:11.632 [2017-05-25T01:00:11.357] error: We have more allocated time than is possible (772316 > 417600) for cluster cluster(116) from 2017-05-25T00:00:00 - 2017-05-25T01:00:00 tres 1 [2017-05-25T01:00:11.374] Warning: Note very large processing time from hourly_rollup for cluster: usec=11281362 began=01:00:00.092 Thanks & Regards, Balaji
