You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// In best-effort retry mode a missing/unreachable bucket surfaces as a timeout rather than an
1067
+
// auth failure. Classify it as a connection error so callers translate it to a 502 instead of a
1068
+
// generic 500, mirroring the per-database connection path (see db.connectToBucketErrorHandling).
1069
+
if!cc.useGOCBFastFailRetry {
1070
+
returnnil, nil, HTTPErrorf(http.StatusBadGateway,
1071
+
"Unable to connect to Couchbase Server. Please ensure it is running and reachable, and that bucket %q exists. Error: %s", MD(bucketName).Redact(), err)
Copy file name to clipboardExpand all lines: docs/api/components/schemas.yaml
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -2493,6 +2493,10 @@ Startup-config:
2493
2493
description: Store database configurations in system xattrs
2494
2494
type: boolean
2495
2495
default: false
2496
+
use_gocb_fast_fail_retry:
2497
+
description: When true, errors on initial connection to Couchbase Server will fail instantaneously. Enabling this will surface authentication errors quickly, but can cause some Sync Gateway operations to shut down databases with intermittent Couchbase Server connection errors.
2498
+
type: boolean
2499
+
default: false
2496
2500
readOnly: true
2497
2501
couchbase_keepalive_interval:
2498
2502
description: TCP keep-alive interval between SG and Couchbase server. This is unused.
0 commit comments