Description of problem:
SSL infra spawns a thread per client. This poses a performance problem when multiple fops are to be processed concurrently.
SSL infra should piggy back on the regular epoll infra for better performance and scalability.
REVIEW: https://review.gluster.org/19308 (rpc: merge ssl infra with epoll infra) posted (#7) for review on master by Milind Changire
REVIEW: https://review.gluster.org/19786 (rpc: merge ssl infra with epoll infra - DO NOT MERGE) posted (#2) for review on master by Milind Changire
COMMIT: https://review.gluster.org/19308 committed in master by "Raghavendra G" <firstname.lastname@example.org> with a commit message- rpc: merge ssl infra with epoll infra
Patch attempts to use the epoll infra for handling SSL connections
as well instead of the socket_poller() thread func.
This essentially makes priv->own_thread flag redundant.
SSL_connect()/SSL_accept() is now non-blocking which has done away
with the localised poll() in ssl_do(). So, ssl_do() has been updated
own_thread and coincidently socket_poller() thread for SSL processing
is now deprecated.
Signed-off-by: Milind Changire <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.
glusterfs-5.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.
*** Bug 1408101 has been marked as a duplicate of this bug. ***