On Monday, March 20, 2017 at 7:23:57 PM UTC-7, James Brown wrote: > > It would be nice if there were a way to cause Sequel's ConnectionPool to > recycle connections after a certain lifetime (to limit long TCP sessions > when using layer 4 load balancers, or for other > administrative/infrastructural purposes). This is fairly common feature of > connection pooling libraries (for example, it's found in python's > sqlalchemy > <http://docs.sqlalchemy.org/en/latest/core/pooling.html#setting-pool-recycle>, > > and in the ezpool <https://github.com/EasyPost/ezpool> library that we > maintain internally). > > Our particular use case is that we have multiple Galera (multi-master > MySQL) servers behind a load balancer; in the event that one of them is > adminstratively removed from the load balancer for maintenance (or a new > one is added), it would be nice for applications using Sequel to "notice" > the change in a bounded amount of time without having to be explicitly > restarted (or without having to suffer a flurry of > Sequel::DatabaseDisconnectedErrors). > > Right now, I have a hack in place which calls `disconnect` on the > ConnectionPool every so often, which works (technically), but isn't very > elegant. > > I believe the connection_validator or connection_expiration extensions that ship with Sequel may do what you want. If not, can you please let me know why neither would meet your needs?
Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
