Replica-set Status of All Members
Feature Summary and Revision History
|
Applicable Product(s) or Functional Area |
CPS |
|
Applicable Platform(s) |
Not Applicable |
|
Default Setting |
Enabled - Always-on |
|
Related Changes in This Release |
Not Applicable |
|
Related Documentation |
CPS Operations Guide |
|
Revision Details |
Release |
|---|---|
|
First introduced |
19.3.0 |
Feature Description
CPS now provides the status from all the defined members of replica-set instead of only first ONLINE member using diagnostics.sh --get_replica_status command.
-
If there is no issue in connectivity or network then replica-set status looks like:
|----------------------------------------------------------------------------------------------------------------------------------------| |----------------------------------------------------------------------------------------------------------------------------------------| | SESSION:set01 | | Status via arbitervip:27717 sessionmgr01:27717 sessionmgr02:27717 | | Member-1 - 27717 : 221.1.1.38 - SECONDARY - sessionmgr02 - ON-LINE - 0 sec - 2 | | Member-2 - 27717 : 221.1.1.37 - PRIMARY - sessionmgr01 - ON-LINE - -------- - 3 | | Member-3 - 27717 : 221.1.1.40 - ARBITER - arbitervip - ON-LINE - -------- - 0 | |----------------------------------------------------------------------------------------------------------------------------------------| |----------------------------------------------------------------------------------------------------------------------------------------|
Note
Two horizontal line separators are added between different members of replica sets.
-
If there is an issue in connectivity or network then replica-set status looks like:
|----------------------------------------------------------------------------------------------------------------------------------------| |----------------------------------------------------------------------------------------------------------------------------------------| | SESSION:set07 | | Status via arbitervip:27727 sessionmgr01:27727 | | Member-1 - 27727 : 221.1.1.37 - SECONDARY - sessionmgr01 - ON-LINE - 0 sec - 2 | | Member-2 - 27727 : 221.1.1.38 - PRIMARY - sessionmgr02 - ON-LINE - -------- - 3 | | Member-3 - 27727 : 221.1.1.40 - ARBITER - arbitervip - ON-LINE - -------- - 0 | | Member-4 - 27727 : 221.1.1.59 - UNKNOWN - sessionmgr03 - OFF-LINE - 0 sec - 1 | | Member-5 - 27727 : 221.1.1.60 - UNKNOWN - sessionmgr04 - OFF-LINE - 18015 days - 1 | |----------------------------------------------------------------------------------------------------------------------------------------| | Status via sessionmgr02:27727 sessionmgr03:27727 | | Member-1 - 27727 : 221.1.1.37 - SECONDARY - sessionmgr01 - ON-LINE - 0 sec - 2 | | Member-2 - 27727 : 221.1.1.38 - PRIMARY - sessionmgr02 - ON-LINE - -------- - 3 | | Member-3 - 27727 : 221.1.1.40 - ARBITER - arbitervip - ON-LINE - -------- - 0 | | Member-4 - 27727 : 221.1.1.59 - SECONDARY - sessionmgr03 - ON-LINE - 0 sec - 1 | | Member-5 - 27727 : 221.1.1.60 - UNKNOWN - sessionmgr04 - OFF-LINE - 18015 days - 1 | |----------------------------------------------------------------------------------------------------------------------------------------| | Status via sessionmgr04:27727 sessionmgr05:27727 | | Mongodb Daemon or Host is down | |----------------------------------------------------------------------------------------------------------------------------------------|
Note
One horizontal line separator is added between different members of replica-set.
For more information, see diagnostics.sh section in the CPS Operations Guide.
Feedback