Respectfully, I would disagree, if dovecot offers the capability to use two host='s then you should be able to configure the order, remember, earlier dovecot did this but you claimed it was broken shouldnt have and fixed it, which is why not only myself but another at the time suggested when you were fixing it, to make it a configurable option, it makes little sense to use two hosts otherwise in an ordinary network, where you have nanoseconds response from localhost, but milliseconds, to maybe more if there are network issues when on a second query second database server with network latency.
otherwise, might as well delete the second host, I've seen the network lag affect logins, only to disappear once I only change to use only one box, the localhost replicated copy.
I ask you reconsider, or, at least put it out there to see how many others agree or disagree with hte feature
On Wed, 2013-05-29 at 03:52 +0300, Timo Sirainen wrote:
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.
Regards Daniel