<div dir="ltr">ok<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 3, 2013 at 5:51 PM, Loïc Hoguin <span dir="ltr"><<a href="mailto:essen@ninenines.eu" target="_blank">essen@ninenines.eu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Existing acceptors were using the old options for the next connection and then switched to the new options. But that has been fixed a long time ago. Ranch doesn't have that issue.<div class="im">
<br>
<br>
On 01/03/2013 02:32 PM, Max Lapshin wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
I mean situation that after cowboy:update_options existing acceptors are<br>
still working with old routes.<br>
Currently it is useless API, so I have to stop cowboy and start it back.<br>
<br>
<br>
On Thu, Jan 3, 2013 at 4:46 PM, Loïc Hoguin <<a href="mailto:essen@ninenines.eu" target="_blank">essen@ninenines.eu</a><br></div><div class="im">
<mailto:<a href="mailto:essen@ninenines.eu" target="_blank">essen@ninenines.eu</a>>> wrote:<br>
<br>
  Haven't had any stability issue. What we did here is ensure that<br>
  when any process gets killed for any reason, especially reasons we<br>
  can't foresee, Ranch continues to work as expected.<br>
<br>
  Ranch not updating protocol options for existing connections isn't a<br>
  problem, it won't be "fixed". Ranch can't guess how connection<br>
  processes are implemented. It's up to you to allow this if you need<br>
  it. The upgrade updates the options for all acceptors and all future<br>
  connections, that's it.<br>
<br>
<br>
  On 01/03/2013 10:30 AM, Max Lapshin wrote:<br>
<br>
    Loic, it would be great to hear a bit, what problems have you<br>
    met with.<br>
<br>
    What issues with stability can be in acceptor pool?<br>
<br>
    Also I have question about updating protocol options: have you done<br>
    something with the problem that after updating protocol options<br>
    existing<br>
    workers are running with old config?<br>
<br>
    On Tuesday, December 25, 2012, Loïc Hoguin wrote:<br>
<br>
       Ho ho ho!<br>
<br>
       I have just tagged version 0.6.0 of the Ranch project!<br>
<br>
       Ranch is a socket acceptor pool for TCP protocols.<br>
<br></div>
    <a href="https://github.com/extend/____ranch" target="_blank">https://github.com/extend/____<u></u>ranch</a><br>
    <<a href="https://github.com/extend/__ranch" target="_blank">https://github.com/extend/__<u></u>ranch</a>><div class="im"><br>
    <<a href="https://github.com/extend/__ranch" target="_blank">https://github.com/extend/__<u></u>ranch</a><br>
    <<a href="https://github.com/extend/ranch" target="_blank">https://github.com/extend/<u></u>ranch</a>>><br>
<br>
<br>
       Ranch is used by the next version of Cowboy, 0.8.0, set to be<br>
       released early February, but also in Basho's Riak<br>
    multi-data center<br>
       replication amongst others.<br>
<br>
       All tickets have been resolved. A significant contribution<br>
    was made<br>
       by Andrew Majorov to improve the fault tolerance<br>
    capabilities of the<br>
       application, making sure it always restarts properly when<br>
    things go<br>
       wrong. This has been made possible thanks to the amazing<br>
    project<br>
       from Daniel Luna, chaos_monkey<br></div>
       (<a href="https://github.com/dluna/____chaos_monkey" target="_blank">https://github.com/dluna/____<u></u>chaos_monkey</a><br>
    <<a href="https://github.com/dluna/__chaos_monkey" target="_blank">https://github.com/dluna/__<u></u>chaos_monkey</a>><div class="im"><br>
       <<a href="https://github.com/dluna/__chaos_monkey" target="_blank">https://github.com/dluna/__<u></u>chaos_monkey</a><br>
    <<a href="https://github.com/dluna/chaos_monkey" target="_blank">https://github.com/dluna/<u></u>chaos_monkey</a>>>).<br>
<br>
<br>
       The guide has also been improved and completed.<br>
<br></div>
    <a href="http://ninenines.eu/docs/en/____ranch/HEAD/guide/introduction" target="_blank">http://ninenines.eu/docs/en/__<u></u>__ranch/HEAD/guide/<u></u>introduction</a><br>
    <<a href="http://ninenines.eu/docs/en/__ranch/HEAD/guide/introduction" target="_blank">http://ninenines.eu/docs/en/_<u></u>_ranch/HEAD/guide/introduction</a><u></u>><div><div class="h5"><br>
<br>
<br>
    <<a href="http://ninenines.eu/docs/en/__ranch/HEAD/guide/introduction" target="_blank">http://ninenines.eu/docs/en/_<u></u>_ranch/HEAD/guide/introduction</a><br>
    <<a href="http://ninenines.eu/docs/en/ranch/HEAD/guide/introduction" target="_blank">http://ninenines.eu/docs/en/<u></u>ranch/HEAD/guide/introduction</a>><u></u>><br>
<br>
       If the guide isn't enough, drop by our new IRC channel<br>
    dedicated to<br>
       Cowboy, Ranch and all our other projects! #ninenines on<br>
    Freenode.<br>
<br>
       Following is the list of change since last time:<br>
<br>
        *  Improve fault tolerance thanks to chaos_monkey testing<br>
        *  Add 'nodelay' option to transports<br>
        *  Add 'verify' option to ranch_ssl transport<br>
        *  Add 'socket' option to pass an already open socket to<br>
    the listener<br>
        *  Add Transport:sendfile/2 function (uses a fallback if<br>
    unavailable)<br>
        *  Allow IP tuples in Transport:connect/3<br>
        *  Add ranch:set_max_connections/2 to update the value live<br>
        *  Add ranch:get_max_connections/1 to retrieve it<br>
<br>
       We are always looking for feedback, especially now that<br>
    there is no<br>
       ticket left open on this project. If you are using Ranch<br>
    and have<br>
       questions or needs that it doesn't cover, please send them<br>
    to us.<br>
<br>
       Commercial support will be available starting from January,<br>
    ping me<br>
       if you are interested. Details will be announced at a later<br>
    time on<br>
       the <a href="http://ninenines.eu" target="_blank">ninenines.eu</a> <<a href="http://ninenines.eu" target="_blank">http://ninenines.eu</a>><br>
    <<a href="http://ninenines.eu" target="_blank">http://ninenines.eu</a>> mailing list.<br>
<br>
<br>
       I want to thank all contributors for helping this project<br>
    by opening<br>
       tickets, sending patches and offering feedback. I am as<br>
    always very<br>
       grateful for any and all contributions. I wouldn't have<br>
    made it this<br>
       far without the tremendous help I receive everyday.<br>
<br>
       Thanks to all and have a nice holiday!<br>
<br>
       --<br>
       Loïc Hoguin<br>
       Erlang Santa<br>
       Nine Nines<br>
    <a href="http://ninenines.eu" target="_blank">http://ninenines.eu</a><br></div></div>
       ______________________________<u></u>_____________________<br>
       erlang-questions mailing list<br>
    <a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a> <mailto:<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@<u></u>erlang.org</a>><br>
    <a href="http://erlang.org/mailman/____listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/____<u></u>listinfo/erlang-questions</a><br>
    <<a href="http://erlang.org/mailman/__listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/__<u></u>listinfo/erlang-questions</a>><div class="im"><br>
       <<a href="http://erlang.org/mailman/__listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/__<u></u>listinfo/erlang-questions</a><br>
    <<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/<u></u>listinfo/erlang-questions</a>>><br>
<br>
<br>
<br>
  --<br>
  Loïc Hoguin<br>
  Erlang Cowboy<br>
  Nine Nines<br>
  <a href="http://ninenines.eu" target="_blank">http://ninenines.eu</a><br>
<br>
<br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
-- <br>
Loïc Hoguin<br>
Erlang Cowboy<br>
Nine Nines<br>
<a href="http://ninenines.eu" target="_blank">http://ninenines.eu</a><br>
</div></div></blockquote></div><br></div>