You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "Mate Szalay-Beko (Jira)" <ji...@apache.org> on 2022/01/27 10:19:00 UTC

[jira] [Resolved] (ZOOKEEPER-4453) NettyServerCnxnFactory: allow to configure the early TLS connection drop feature

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mate Szalay-Beko resolved ZOOKEEPER-4453.
-----------------------------------------
    Resolution: Fixed

Thanks Enrico for the fix!
The commit was pushed to master and to branch-3.7, it will be released in 3.7.1 and 3.8.0

> NettyServerCnxnFactory: allow to configure the early TLS connection drop feature
> --------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-4453
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4453
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.6.3
>            Reporter: Enrico Olivelli
>            Assignee: Enrico Olivelli
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 3.8.0, 3.7.1
>
>          Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> Follow up of ZOOKEEPER-3988.
> We should introduce a flag to disable the feature introduced by ZOOKEEPER-3682.
> *Implementation*
>  * Add new flag netty.server.earlyDropSecureConnectionHandshakes to control the ZOOKEEPER-3682 feature.
>  * Disable ZOOKEEPER-3682 by default, it is advanced feature, for very large clusters
>  * Add docs
>  * Add tests (also ZOOKEEPER-3682 missed tests, now we will have some)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)