[
https://issues.apache.org/jira/browse/GEODE-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Burcham resolved GEODE-6585.
---------------------------------
Fix Version/s: 1.10.0
Resolution: Fixed
PR here: https://github.com/apache/geode/pull/3388
Merged April 2, 2019
> tuning advice for subscription-ack-interval has multiple problems
> -----------------------------------------------------------------
>
> Key: GEODE-6585
> URL: https://issues.apache.org/jira/browse/GEODE-6585
> Project: Geode
> Issue Type: Bug
> Components: docs
> Reporter: Bill Burcham
> Assignee: Bill Burcham
> Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On this page:
> [https://gemfire.docs.pivotal.io/97/geode/developing/events/limit_server_subscription_queue_size.html]
> the first paragraph under
> {code:java}
> subscription-ack-interval{code}
> has some inconsistencies:
> {quote}Optional: Increase the frequency of queue synchronization. This only
> applies to configurations where server redundancy is used for high
> availability. Increase the client’s pool configuration,
> subscription-ack-interval. The client periodically sends a batch
> acknowledgment of messages to the server, rather than acknowledging each
> message individually. A lower setting speeds message delivery and generally
> reduces traffic between the server and client. A higher setting helps contain
> server queue size.
> {quote}
> Third sentence: “Increase…subscription-ack-interval“—this seems backward to
> me. It certainly disagrees with the first sentence since the interval is
> inversely proportional to the frequency.
> Fifth sentence: “…and generally reduces traffic…“—is that true? I doubt it.
> Last sentence: “A higher setting helps contain server queue size.“—again
> backward.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
