ons?
>
> ** **
>
> Thanks,
>
> Amir
>
> ** **
>
> ** **
>
> *From:* OJ Reeves [mailto:o...@buffered.io]
> *Sent:* 11 July 2013 17:31
> *To:* Amir Halatzi
> *Cc:* Jeremiah Peschka; riak-users@lists.basho.com
>
> *Subject:* Re: CorrugatedIron & Idl
users@lists.basho.com
Subject: Re: CorrugatedIron & Idle Connection
This is a discussion we really need to have. Thanks for opening the Github
issue.
In the short term, you can "turn off" pooling by setting the pool size to zero.
This will mean all the connections are done "on the fly
n on ‘network failure’?
>
> ** **
>
> BR,
>
> Amir
>
> ** **
>
> *From:* Jeremiah Peschka [mailto:jeremiah.pesc...@gmail.com]
> *Sent:* 11 July 2013 17:11
> *To:* Amir Halatzi
> *Cc:* riak-users@lists.basho.com
> *Subject:* Re: CorrugatedIron &
From: Jeremiah Peschka [mailto:jeremiah.pesc...@gmail.com]
Sent: 11 July 2013 17:11
To: Amir Halatzi
Cc: riak-users@lists.basho.com
Subject: Re: CorrugatedIron & Idle Connection
We're in the process of figuring out how to best handle killing off idle
connections inside of CorrugatedIron.
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 be
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 t
