8 Dec
2011
8 Dec
'11
6:15 a.m.
On Wed, 2011-12-07 at 12:02 +0100, Yann Dupont wrote:
Much faster (using all the cores), but dsync still hangs on some accounts. After a certain time dsync exit with an error like that :
Panic: file dsync-worker-local.c: line 1688 (local_worker_save_msg_continue): assertion failed: (ret == -1)
Unfortunately there are still some bugs in dsync.. But you could work around this by checking if dsync returned failure, and if it did just retry the user.
This is on a RUNNNING server.
My aim was to make some pass on the running server, then stop it and make a last pass to finish the process.
That should work.
Is dsync supposed to run only on a stopped server ?
No.