Replica Set / Sharding Status

What it is

A workspace tab fed by rs.status(), sh.status(), and config.* collections. Renders a topology view per replica set, lists every member with its state, and lets you broadcast a command (e.g. db.serverStatus() / db.fsyncLock()) to all members at once with the result aggregated into a single response panel.

When to use

Open before a planned election or maintenance to confirm member health. Open during incident response when one member misbehaves. Use the broadcast for chained operations like setting feature compatibility version or fsync-locking before snapshot.

How to open

1. In the NoSqlStudio desktop app, open the Tools menu → Server / Replica / Sharding Status, or press Ctrl+Alt+R.
2. The workspace renders the topology of every replica set you can reach via the active connection.
3. Click a member to see its full rs.status() entry. Right-click to invoke targeted commands (step down, freeze, etc.).

Working with it

• Topology view — primary in center, secondaries around, arbiters / hidden shown as separate badges.
• Replication lag — visualized as a number + color (green < 1s, yellow < 5s, red > 5s).
• Broadcast — type a single command in the broadcast bar, click Run. The engine fans out the command to every reachable member in parallel and aggregates the result. Every broadcast emits an rs-broadcast.execute audit line.
• Sharding view — when active connection is a mongos, an additional pane shows shards, chunk distribution, balancer state.

Limitations (v1)

• Broadcast targets reachable members only — unreachable members are flagged in the result with a connection error.
• Atlas managed clusters — some admin commands are blocked by Atlas RBAC. The workspace surfaces the access-denied error inline.
• Sharding pane requires connecting via mongos. Connecting to a single shard skips the sharding view (replica set view still works).