On 12/13/18 9:52 AM, Egoitz Aurrekoetxea wrote:
Egoitz, As long as you've followed all of the various steps needed to account for version changes, as outlined in the Release Notes for all intermediary releases, then the last step should be the updating of the indexes. Rather than running "reconstruct -V max" on all mailboxes at once, simply run it on subsets. We've done this on large installations without ill effect. You can have the service on line during the reconstruct, and, as you note, have most all functionality present. We build a list of users (mboxlist.txt), and then run a cron job, during off-peak hours, using the 'parallel' command like so (from 'crontab -e -u cyrus'): Cheers,### ## Start a batch of recursive reconstruct jobs at 7PM and discontinue ## at 6:53AM. 0 19 * * * parallel -j 5 --resume --joblog /var/lib/imap/reconstruct.log cyrus reconstruct -G -V max -r -u {} < /var/lib/imap/mboxlist.txt 53 06 * * * kill -TERM `ps ax | grep [p]arallel | awk '{print $1}'` -nic -- Nic Bernstein nic@xxxxxxxxxxx Onlight Inc. www.onlight.com 6525 W Bluemound Rd., Ste 24 v. 414.272.4477 Milwaukee, Wisconsin 53213-4073 f. 414.290.0335 |
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus