>> Is any plan to move to ClientCnxnSocketNetty but default ? The plan was to replace NIO engine. See ZOOKEEPER-733. For some features (like client-server SSL) it is a requirement to switch to Netty. Netty socket implementation is less mature comparing to NIO (there are bugs reported overtime and some of those have not been fixed still), so it would take a while for it to be the default option.
Would be interested to hear if anyone here is using Netty socket and / or client-server SSL in prod and what their feedback is. On Thu, Jul 20, 2017 at 4:07 AM, Enrico Olivelli <eolive...@gmail.com> wrote: > Hi, > I see that ClientCnxnSocketNIO is the default socket type for 3.5. > Does anyone know if ClientCnxnSocketNetty is "better", given that I am not > interested in SSL for my project ? > Is any plan to move to ClientCnxnSocketNetty but default ? > > for 'better' I mean: > - better resource usage > - better latency/throughput > > b.q. I got into https://issues.apache.org/jira/browse/ZOOKEEPER-823 which > is marked for 3.5.4 and 3.6.0, but Netty support is already in > > Thanks > Enrico > -- Cheers Michael.
