[
https://issues.apache.org/jira/browse/GEODE-8800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259980#comment-17259980
]
ASF GitHub Bot commented on GEODE-8800:
---------------------------------------
jinmeiliao commented on pull request #5879:
URL: https://github.com/apache/geode/pull/5879#issuecomment-755507388
As far as I know, we rarely do multi-property cross validation at startup,
i.e, we don't check if property A is set then property B can't be set. Initial
validation is usually based on one property only (i.e integer is between a
number and string is only a certain values etc.). Multi-property conflict is
usually handled by ignoring one property (if A is set, then B has no effect). I
wonder if we should take this route instead.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
>
> 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)
