Hi, i have some problems expiring the BAyes DB. Here is the --force-expire output. The output is always the same. SA 3.0 rc2 version.
First: There's some bayes related bugs fixed between rc2 and SA 3.0 final. You really should consider upgrading... RC's aren't intended for real production use...
Second, That output looks fairly normal.
SA isn't willing to run expire on your system because there's not enough time between expiry runs. Looking at that debug output there's only a few seconds since the last expire. You can re-run expire back-to-back, but SA will ignore the subsequent runs as mistakes. (This is largely a safety mechanism to prevent excessive CPU consumption)
Also from the looks of it, most of your tokens are all the same age.. SA isn't willing to expire them, because doing an expiry will kill too few, or too many, with little in-between ground. Let your bayes DB get some age to it, with training spanning a wider variety of time and try running expire again.
SA's looking to trim off 60k tokens, but the smallest batch it could find would reduce off nearly 90k, which is half your bayes database.
This output here is SA trading off age vs number of tokens expired:
debug: bayes: 172800 171668 debug: bayes: 345600 171158 debug: bayes: 691200 168585 debug: bayes: 1382400 168546 debug: bayes: 2764800 168546 debug: bayes: 5529600 153967 debug: bayes: 11059200 119250 debug: bayes: 22118400 90253
So it looks like SA is facing a situation where half the bayes database was all created at the same time, and it doesn't want to kill all of that in one shot.
