so better remove the option to specify more than one host instead let people run over years in troubles until they find out that a logical behavior like for postfix is not given for dovecot's mysql-connections - yes i was one of the who thought "hey both works the same way" until i realized that dovecot has no fun at reboot the replication slave which was intented only as failover and used regulary
*it is* dovecots job if it offers more than one host to handle this in a useful way or not support more than one host, but you can't seriously say "it's not dovecots job" after having a half-baken support implemented
Am 29.05.2013 02:52, schrieb Timo Sirainen:
I haven't replied to most of the threads recently. Anyway, after thinking about this, I'm thinking this kind of connection fallback handling isn't really Dovecot's job. A load balancer could be configured to do it just as well (whereas LB couldn't do actual load balancing for multiple sql servers, because Dovecot uses long running TCP connections).
On 29.5.2013, at 2.09, Noel Butler noel.butler@ausics.net wrote:
But each additional link added to the chain, is one more point of failure, unless he's replied to OP privately I'm amazed Timo has ignored this, since its been brought up from time to time before, if he no longer plans on doing it, he should just say so, so people can look at complete alternatives, we are a long way passed early 1.2 series.
On Sun, 2013-05-26 at 17:33 +0200, Daniel Parthey wrote:
Edwardo Garcia wrote:
Yes indeed, so it seem it does not do at all. For now we disable use two hosts, but thiz not optimum for network.
You might try to put mysqlproxy in between dovecot and your mysql cluster and have dovecot connect to the failover proxy (or proxies) instead of connecting the database directly.
mysqlproxy makes use of the lua scripting language, where you might want to implement the failover or filter mechanisms you need