Excerpts from wietse's message of Tue Nov 10 15:45:38 -0500 2009: > micah anderson: > > > If anything should retry the query, then it would be the mysql > > > client. The proxymap can't make such decisions (for example, it > > > makes no sense to retry after a read error from a local file). > > > > > > And in fact, the mysql client does implement retry logic. It retries > > > if you have more than one mysql server configured. Perhaps you > > > can specify the same server multiple times. > > > > Interesting idea. Do you mean specify it twice in the main.cf > > configuration such as: > > > > alias_maps = mysql:/etc/postfix/mysql_aliases.cf, > > mysql:/etc/postfix/mysql_aliases.cf > > transport_maps = proxy:mysql:/etc/postfix/mysql_transport.cf, > > proxy:mysql:/etc/postfix/mysql_transport.cf > > Ugh. That means twice the work when a query is "not found".
Yeah, ugh, not a good solution there. > > Or do you mean two times in the host field in those files, such as the > > following in the mysql_transport.cf: > > > > hosts = mysql-cluster1 mysql-cluster1 > > This repeats the query only if the session breaks. However, the > hosts are tried without delay, so this is unlikely to be a solution > for kernel panics. > > Consider configuring more than one mysql server. Actually that was the point of my original message. I setup a mysql cluster, so there are multiple mysql servers in a cluster fail-over scenario. The fail-over is pretty fast, maybe 1 or two seconds, but that may not be fast enough for the above mechanism for repeating the query when the session breaks... hence the question about tunables. micah
