[SERVER-10999] Weird log messages " [rsGhostSync] couldn't percolate slave 4fe7016e911012a1eb33aa1f no entry" Created: 02/Oct/13 Updated: 11/Jul/16 Resolved: 04/Nov/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.5, 2.4.6 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Vitaly Karasik | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | replicaset | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
RHEL5/6 |
||
| Participants: |
| Description |
|
I have a dataset from 3 MongoDB 2.0 nodes, yesterday I added two new secondaries (Mongo 2.4.6). On one of them I see many log messages likes this: [rsGhostSync] couldn't percolate slave 4fe7016e911012a1eb33aa1f no entry
TIA, |
| Comments |
| Comment by Vitaly Karasik [ 02/Oct/13 ] |
|
Scott, |
| Comment by Scott Hernandez (Inactive) [ 02/Oct/13 ] |
|
Please finish your upgrade to 2.4.6 on all your nodes, to see if the message goes away. Running with 2.0.x nodes and 2.4.6 in the same replica set is not stable nor a supported configuration. Please follow the upgrade process for 2.0.x -> 2.2.x -> 2.4.x as described here: In the future please use the mongodb-user forum (https://groups.google.com/forum/#!forum/mongodb-user) to ask questions and look for answers, which will include the community. This jira project is for filing bugs and feature requests. |