Skip to content

Disable cluster node membership validation by default #3250

Open
@tishun

Description

@tishun

Feature Request

Is your feature request related to a problem? Please describe

The validateClusterNodeMembership setting is enabled by default for clustered connections. When adding new nodes to the topology, especially in cases like node upgrade, this setting causes problems as typically the topology update happens later than the first MOVED / ASK responses are received, causing

UnknownPartitionException: Connection to <node> not allowed. This partition is not known in the cluster view.

Describe the solution you'd like

Similar to #3249 this setting is disabled in the recommended connection options of most cloud providers and the Redis documentation.
It was introduced years ago, so it is also a breaking change to swap the default, so we should be targeting major release.
We should change the default of the validateClusterNodeMembership to false and update the documentation

Describe alternatives you've considered

Same as with #3249 educating the user was an approach that did not seem to help much.

Teachability, Documentation, Adoption, Migration Strategy

Users that depend on the node validation should manually enable it using the ClusterClientOptions

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions