We're in the process of figuring out how to best handle killing off idle connections inside of CorrugatedIron. If you can head over to https://github.com/DistributedNonsense/CorrugatedIron/issues and file a new bug report, that would be fantastic.
We've avoided killing off connections until now because we don't want to introduce locking into our connection management. Truthfully, we haven't run into a bug report where the network team was killing off connections. So, anyway, if you can submit a bug report we'll get on it. It won't make it out for the 1.4.0 release, but we can put that in a point release. --- Jeremiah Peschka - Founder, Brent Ozar Unlimited MCITP: SQL Server 2008, MVP Cloudera Certified Developer for Apache Hadoop On Thu, Jul 11, 2013 at 6:59 AM, Amir Halatzi <[email protected]>wrote: > Hi all, > > Trying to optimize our application connection pool, we encountered and > issue with Corrugated Iron and identifying idle/reset connections. Namely, > if our network infrastructure (firewall/proxy/etc) closes an idle > connection - we're getting a 'cluster is offline' error code. > > I saw that this is a feature in the making (for the past 8 months), but I > was wondering if any of you found a way around it? > > Thank you, > Amir Halatzi, > ooVoo > > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
