Skip to:

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

ReplicaSet Summary does not show node that is down

Description

The ReplicaSet Summary dashboard shows ReplSet States and MongoDB Versions. It works fine when all nodes are available, but when a node is down:

  1. The node disappears from ReplSet States when it goes past the selected metrics window

  2. It disappears from the MongoDB Versions list. It should still be visible there (last version information available). For this point 2, for MongoS, a spin-off ticket has been created: .

 Possible help for implementation here:

See the screenshots for more details

How to test

FB ->

This FB includes the changes from so both can eb tested together


Run an instance with replicaset and cluster
Check replicaset and cluster summary dashboard for replset states panels
Now bring down any one node (down means db.shutdownserver() or any other command)

Check the panel if the Down State is showing in the panel. (color should be red)

Check cluster summary dashboard → versions panel, version of the down node should be visible
(currently Excluding MongoS versions from this story)

How to document

Update the replicaset summary dashboard images if any.
To be confirmed if any other documentation required.

AFFECTED CS IDs

CS0047232

Attachments

6

Smart Checklist

hide

Activity

Show:

Catalina Adam January 9, 2025 at 10:29 AM

Nailya Kutlubaeva December 16, 2024 at 8:26 AM

should I create the ticket for fixing Replete on Summary dashboard? Or Maybe you will create the ticket for refactoring MongoDB Summary dashboard?

Nailya Kutlubaeva December 4, 2024 at 3:26 PM

I see that there is no any status displayed on Summary dashboard if the node is down. Should the fix include Summary dashboard?

Done

Details

Assignee

Reporter

Priority

Components

Labels

Needs QA

Yes

Needs Doc

Yes

Planned Version/s

Fix versions

Story Points

Affects versions

Smart Checklist Progress

Due date

Smart Checklist

Created September 12, 2024 at 9:51 AM
Updated February 3, 2025 at 10:04 AM
Resolved January 9, 2025 at 10:41 AM