Issues
- Unable to add secondary nodePSMDB-1609Resolved issue: PSMDB-1609radoslaw.szulgo
- issue with Audit filter parameterPSMDB-214Resolved issue: PSMDB-214
- mongodb cant set 3.4 features after upgrade from 3.2PSMDB-213Resolved issue: PSMDB-213
- Mongos are shown in the "QPS for Config servers" graphPMM-13239Resolved issue: PMM-13239
- Dashboard: Datasize Dashboard Shows Non-Cluster DataPMM-10435Resolved issue: PMM-10435Anton Bystrov
- mongodb_exporter Crashing while db goes downPMM-9348
- mongodb_up metrics gives no data when db goes down? it should respond with zeroPMM-8954Resolved issue: PMM-8954
- Refactor/cleanup qan-mongodb-profilerPMM-3950Resolved issue: PMM-3950Nurlan Moldomurov
- Add support to specify retention period while taking backupsPBM-774Resolved issue: PBM-774
- Request to add custom replicaset tagsK8SPSMDB-1093Resolved issue: K8SPSMDB-1093natalia.marukovich
- Support ClusterIssuer for MongoDB ReplicaSet Cluster with TLS and Let's EncryptK8SPSMDB-928
11 of 11
Unable to add secondary node
Cannot Reproduce
General
Escalation
General
Escalation
Description
Environment
None
Details
Security Level Help
NoneAssignee
radoslaw.szulgoradoslaw.szulgoReporter
bhavik mistrybhavik mistryLabels
Needs QA
YesStart date
Feb 18, 2025Components
Sprint
Affects versions
Priority
Medium
Details
Details
Security Level Help
None
Assignee
radoslaw.szulgo
radoslaw.szulgo
Reporter
bhavik mistry
bhavik mistry
Labels
Needs QA
Yes
Start date
Feb 18, 2025
Components
Sprint
Affects versions
Priority
MediumSmart Checklist
Smart Checklist
Smart Checklist
Created February 19, 2025 at 3:48 AM
Updated March 11, 2025 at 1:34 PM
Resolved March 11, 2025 at 1:34 PM
Activity
Show:
radoslaw.szulgoMarch 11, 2025 at 1:34 PM
Thanks , we’re unable to tell the root cause as provided logs don’t reveal much. I’m happy the issue is gone. In case you need some further assistance - let us know.
bhavik mistryFebruary 25, 2025 at 6:21 AM
Issue got resolved after promote another node as primary..But still not sure about root cause
Hi Team,
We have a 3-node MongoDB replica setup running Percona Mongo 7.0.15. As part of the Ubuntu kernel upgrade, we rebooted one of the nodes. However, after the reboot, it is unable to catch up with the primary and is throwing the following error:
[Include error message here]
Please advise on the next steps to resolve this issue.