Quoting Michael Menge :
If you give me some other names, I might be able to see why...
I will send the to you and not to the list, as some names may contain
non public informations.
on closer inspection one other case proved to be a race condition
in sync_client. Sync_client tried to sync a
Quoting Bron Gondwana :
Since the migration we discovered some small issues and some bugs.
1. usually Cyrus is not CPU bound. One exception is the mupdate master
keeping encrypted connection to all frontends and establishing
new encrypted connections from the backend for every mailbox c
Michael,
I'd like to thank you for having written up such a succinct and
reasonable description of a well thought out murder installation. Lot's
of good information here, especially for people who may be considering a
move like yours. This could be the bones of a good Wiki article.
Cheers,
On Mon, Sep 22, 2014, at 09:20 PM, Michael Menge wrote:
> Hi,
>
> 3 weeks ago we changed our changed cyrus imap servers form stand
> alone systems to a cyrus murder cluster. We have ~44000 accounts,
> ~457000 Mailboxes, and 2x6.5 TB Mails
>
> In our previos setup we had 6 cyrus imap 2.4.17 server
Hi,
3 weeks ago we changed our changed cyrus imap servers form stand
alone systems to a cyrus murder cluster. We have ~44000 accounts,
~457000 Mailboxes, and 2x6.5 TB Mails
In our previos setup we had 6 cyrus imap 2.4.17 servers running as KVM
VMs with 8 GB memory and 4 Cores each, on an HP Blad
