Bug #39083 | Falcon chill thresholds for indexes and records should be > 1 | ||
---|---|---|---|
Submitted: | 28 Aug 2008 0:39 | Modified: | 9 Apr 2009 14:58 |
Reporter: | Kevin Lewis | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Falcon storage engine | Severity: | S3 (Non-critical) |
Version: | 6.0.7 | OS: | Any |
Assigned to: | Christopher Powers | CPU Architecture: | Any |
Tags: | F_CHILL THAW |
[28 Aug 2008 0:39]
Kevin Lewis
[28 Aug 2008 0:58]
Kevin Lewis
Verified in code. Severity is D2 since this may be an unavoidable source of some crashes. There are several other bugs associated with extremely small chill values. (Bug#38566, Bug#38567, Bug#38569, Bug#38541) If it turns out that there is a very practical reason to raise this minimum value, then this bug will be valid. But if all crashes can be avoided, and a chill value of 1 can be supported for both index and record, then this can be closed.
[9 Apr 2009 14:58]
Kevin Lewis
After all this time, we have not had problems specifically with the mechanism of chilling as often as possible. So falcon_record_chill_threshold=1 is a fine way to make that happen. And it has continued to allow us to find bugs. So we will leave this value ridiculously low so that our tests can continue to assure that chilling often in a highly concurrent environment works.