Skip to content

Commit e7f8394

Browse files
Merge branch 'release/3.8' into tutorial-student-record
2 parents 3e8829a + ce8d31c commit e7f8394

1 file changed

Lines changed: 15 additions & 3 deletions

File tree

modules/concept-docs/pages/best-practices.adoc

Lines changed: 15 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,18 @@ xref:ref:client-settings.adoc#constrained-network-environments[best timeout opti
9494
or at least set a xref:ref:client-settings.adoc#wan-development[WAN development Configuration Profile].
9595

9696

97+
// Something on longer timeouts and fewer retries?
98+
// ... reading the logs to find the pattern?
99+
100+
101+
// & Something on polling rate the SDK uses to fetch an updated cluster map whenever a topology change occurs.
102+
////
103+
By default the Java SDK polls every 2.5 seconds, regardless of server version or SDK version.
104+
This interval is configurable via the io.configPollInterval client setting.
105+
https://docs.couchbase.com/java-sdk/current/ref/client-settings.html#io.configPollInterval
106+
When Java SDK 3.5.0 or later is used with Couchbase Server 7.6 or later, the SDK also listens for config change notifications from the server. In this case the polling acts as a failsafe, so it's probably okay to set it significantly higher than 2.5 seconds.
107+
////
108+
97109
// write after more LZA added
98110
////
99111
=== Read From Replica
@@ -113,9 +125,9 @@ See the xref:howtos:concurrent-async-apis.adoc[Async & Reactive APIs page] for d
113125

114126
== Error Handling
115127

116-
Best practices for error handling in Scala depend somewhat upon your choice of API:
117-
blocking, asynchronous, or reactive, as covered in the xref:concurrent-async-apis.adoc[async and reactive API guide].
118-
That guide also covers how errors are actually returned (e.g. via `Try`, `Future`, or `Mono`) and handled.
128+
Best practices for error handling in Java depend somewhat upon your choice of API:
129+
blocking, asynchronous, or reactive, as covered in the xref:howtos:concurrent-async-apis.adoc[async and reactive API guide].
130+
// That guide also covers how errors are actually returned (e.g. via `Try`, `Future`, or `Mono`) and handled.
119131
See also the xref:howtos:error-handling.adoc[error handling guide],
120132
which covers specific errors, along with a broader look at error handling strategies.
121133

0 commit comments

Comments
 (0)