You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/01/06 06:54:00 UTC

[jira] [Commented] (GEODE-8800) SSL is supposed to disable slower receiver feature

    [ https://issues.apache.org/jira/browse/GEODE-8800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259452#comment-17259452 ] 

ASF subversion and git services commented on GEODE-8800:
--------------------------------------------------------

Commit fec44adfdf573c5dac8f319c1f3e97eb71596fca in geode's branch refs/heads/feature/GEODE-8800 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=fec44ad ]

GEODE-8800: Slower receiver is not allowed with cluster TLS/SSL

    Co-authored-by: Xiaojian Zhou <zh...@vmware.com>
    Co-authored-by: Bill Burcham <bi...@gmail.com>


> SSL is supposed to disable slower receiver feature
> --------------------------------------------------
>
>                 Key: GEODE-8800
>                 URL: https://issues.apache.org/jira/browse/GEODE-8800
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Xiaojian Zhou
>            Assignee: Xiaojian Zhou
>            Priority: Major
>              Labels: GeodeOperationAPI
>
> According to document, slow receiver options are disabled in systems using SSL (https://geode.apache.org/docs/guide/12/managing/monitor_tune/slow_receivers_managing.html). 
> But TLS tests found it did not. If the cluster specified async-distribution-timeout to 1 aggressively, it will cause SSL test to hang. When distribution took longer than async-distribution-timeout, even d-ack region will be using async message queue, which conflicts with SSL. 
>  
> There're 2 alternatives to fix: 
> (1) if SSL is enabled, and detected asyncDistributionTimeout>0, throw exception. 
> (2) if SSL is enabled, force asyncDistributionTimeout to be 0 even it configed >0. 
> We decide to take alternative-(1).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)