I agree with you. Maybe you should report this to the developers and see
if they can do something about or what they suggest (not that some of
them are not following this list, but they seem busy in following their
dedicated list as I noticed in the last days it was pretty busy with the
voting of 1.1.1 and now it seems a little bit of calm period there).
Cheers,
CGS
On 10/26/2011 11:12 AM, Paolo Negri wrote:
On Wed, Oct 26, 2011 at 10:48 AM, CGS<[email protected]> wrote:
Just for my curiosity, is this behavior sporadic or it is continuous for the
full period of compaction?
It's sporadic, we poll the db status every 60 seconds, and we observe
this happening only occasionally my guess is that it depends by the io
load at the exact point in time of the call (io load varies much
during compaction).
On 10/26/2011 10:18 AM, Paolo Negri wrote:
I just wanted to add some more information about this behavior, the
problem happens not just after triggering compaction but can happen at
any point while compaction is in progress, tonight we got the same
error 20 minutes after launching compaction.
Thanks,
Paolo
