Skip to:

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

Agent attempts to fallback to http polling when no http addresses exist

Description

On a CAO cluster with 1 node, using server 7.1, we're failing to connect to the bucket when adding documents. We receive this error from bucket.WaitUntilReady:

This only happens with 1 node (if we change to 3 nodes, the test passes fine), and also only happens on 7.1 (on 7.0.3, the test passes fine.). The bucket is responding to API calls from the operator via /pools/default/buckets... and also appears on the server UI.

I've attached cbopinfo, cbinfo, the operator logs, and the SDK logs from gocb.SetLogger(gocb.VerboseStdioLogger())

Environment

CAO 2.3 CB Server 7.1.0-2434 gocb 2.3

Gerrit Reviews

None

Release Notes Description

None

Attachments

4

Activity

Show:
Fixed

Details

Assignee

Reporter

Story Points

Fix versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created March 7, 2022 at 1:47 PM
Updated March 8, 2022 at 8:57 AM
Resolved March 8, 2022 at 8:57 AM
Loading...