Re: Database select failure with > max_idle connections

[Jan Kneschke]

r220 hopefully fixes this issue too.

------------------------------------------------------------------------
r220 | jkneschke | 2007-09-06 17:41:10 +0200 (Thu, 06 Sep 2007) | 27 lines

reworked the connection pool to have one pool for user (fixes #....)

before we had one connection pool which stored idling connections for
all users. In disconnect_client() we tried to shrink the pool to
max-idle and could specify for which user we want to close connections

Now this mgmt is move into the core and only the configuration is
external. To reflect this internal change the scripting-API changes too:

proxy.backend[ndx].
idling_connections

is replaced by

proxy.backend[ndx].
pool.
min_idle_connections (rw)
max_idle_connections (rw)
users[username].
cur_idle_connections (ro)

Another important change handles the order of getting connections from
the pool. Before we picked one randomly, now we pick the oldest in the
pool to reduce the impact of wait_timeout killing old, idling
connections

--
Jan Kneschke, MySQL Enterprise Tools