[
https://issues.apache.org/jira/browse/GEODE-8800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260123#comment-17260123
]
ASF subversion and git services commented on GEODE-8800:
--------------------------------------------------------
Commit 17b7911f521c20087591853f1bfb0417cc7047e2 in geode's branch
refs/heads/develop from Xiaojian Zhou
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=17b7911 ]
GEODE-8800: Slower receiver is not allowed with cluster TLS/SSL (#5879)
Co-authored-by: Xiaojian Zhou <zho...@vmware.com>
Co-authored-by: Bill Burcham <bill.burc...@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, pull-request-available
> Fix For: 1.14.0
>
>
> 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)
