Skip to:

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

.NET SDK fails to connect to correct node in custom port (cluster_run) multi-node setup

Description

Summary

When testing a .NET application against a development CB Server running multiple nodes via cluster_run, the .NET SDK fails to connect to the correct node, eventually giving up:

Steps to reproduce

  1. Compile and run CB Server with multiple nodes on the same machine - e.g.

  2. Setup at least 2 nodes

  3. Attempt to perform some operations against the cluster where the key is not on the first node - for example reproducer from .

Environment

None

Gerrit Reviews

None

Release Notes Description

None

Attachments

1

Activity

Show:

Jeffry Morris April 5, 2022 at 7:05 PM

This is fixed by .

Dave Rigby April 5, 2022 at 11:45 AM

Confirmed that the same repro test from on a two-node cluster_run cluster now works correctly.

Jeffry Morris April 4, 2022 at 10:22 PM

I believe this is fixed on HEAD of master. Can you confirm?

Jeff

Dave Rigby March 24, 2022 at 3:46 PM

Attached packet capture of problem:

. We can see that the SDK repeatedly tries the first node (port 12000), even when NotMyVBucket is sent it doesn't try the correct node on port 12002:

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

Details

Assignee

Reporter

Story Points

Components

Fix versions

Affects versions

Priority

Parent

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created March 24, 2022 at 3:43 PM
Updated April 5, 2022 at 7:05 PM
Resolved April 5, 2022 at 11:45 AM
Instabug