Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Replication
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

The shardedClusterCardinalityForDirectConns parameter is used to determine if direct connections to a shard should be permitted. When we drop clusterParameters in the restore procedure, we lose this parameter value, causing a restored shard node to think it's the only shard in a cluster.

When we drop the cluster parameters in magic restore, we should ensure to keep shardedClusterCardinalityForDirectConns. This ticket should also include a test with multiple shard nodes and authentication to ensure we cannot directly access a newly restored shard node directly.

is duplicated by

SERVER-91950 Preserve approved cluster parameters across magic restore

Closed

is related to

SERVER-91950 Preserve approved cluster parameters across magic restore

Closed

related to

SERVER-91843 Server Ownership of Cluster Parameters to Backup and Restore

Open

Assignee:: Unassigned
Reporter:: Ali Mir
Participants:: Ali Mir
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Jun 17 2024 04:01:19 PM UTC
Updated:: Jul 26 2024 06:08:21 PM UTC
Resolved:: Jul 26 2024 06:08:21 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates