Sync Gateway 2.8.1: DCP feed connections now support connstr ?network=auto/default/external option

Description

Hi Docs,

 

In SG 2.8.1, we improved the handling for a network override specified via the connection string to allow customers to override the automatic "external alternate address" heuristic ()

 

This option is already implemented in SDKs for KV and Query operations from Sync Gateway, but was not used for DCP connections, which meant in some network configurations, customers may be running their DCP connections over an unexpected network interface (see linked CBSE for more detail).

 

The network option can be configured in the server connection string as a query parameter, like so:

 

The default value for this, if not specified is "auto", which uses the same automatic heuristic prior to 2.8.1 - which is based on the host specified in the server option.
The option can be set to "external" to explicitly force the DCP connections to use the configured external alternate address,
Or "default", to force the use of the default internal networking.

Environment

None

Release Notes Description

None

Activity

Show:

Ian Bridge February 2, 2021 at 10:27 AM

 does this change cover the issue? https://github.com/couchbase/docs-sync-gateway/pull/413

 

Ian Bridge January 27, 2021 at 3:32 PM

EG –  For more information on using alternate addresses – see Couchbase Server's xref:server:learn:clusters-and-availability/connectivity.adoc#alternate-addresses[Alternate Addresses] documentation.

Ben Brooks January 27, 2021 at 3:29 PM

Forgot to mention the ticket in the description. This was done in

Unresolved
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Story Points

Components

Fix versions

Due date

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created January 27, 2021 at 12:46 PM
Updated February 17, 2021 at 5:48 PM
Instabug