Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Handle removed buckets in background persistent config update polling

Description

Removed database configuration documents are handled by SG in 3.0, which closes the associated database once detected.
We don't detect when the entire bucket has been removed, which leaves the database running with DCP stuck in a retry loop, and all SDK operations failing due to the removed bucket.

Proposed Solution

ServerContext.fetchAndLoadConfigs() should iterate over its copy of databases/buckets, and remove any databases that are no longer present in the set returned by the server.

Activity

Show:

CB robot May 9, 2022 at 7:44 PM

Build sync_gateway-3.0.1-16 contains sync_gateway commit 24116e7 with commit message:
: 3.0.1 Backport - : Improved persistent config handling for dropped buckets (#5497) (#5512)

CB robot April 20, 2022 at 12:10 AM

Build sync_gateway-3.1.0-116 contains sync_gateway commit 8f24e48 with commit message:
: Improved persistent config handling for dropped buckets (#5497)

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

Details

Assignee

Reporter

Labels

Story Points

Components

Sprint

Fix versions

Affects versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created April 1, 2022 at 4:00 PM
Updated August 31, 2024 at 10:59 AM
Resolved April 13, 2023 at 11:01 PM
Instabug