[SERVER-27918] Restarting oplog query due to error: ExceededTimeLimit: Operation timed out, request was RemoteCommand Created: 05/Feb/17 Updated: 18/Nov/18 Resolved: 21/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vladimir | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 4 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | 1. You need to habe ca. 10 Gb Database in Replica Set with 1 master and no secondaries. |
| Participants: |
| Description |
|
Please help me with this very big replication lag.
Log from secondary member: There are very man these entires:
|
| Comments |
| Comment by Kelsey Schubert [ 18/Nov/18 ] | |
|
For those following along, gen's questions were addressed in | |
| Comment by gen [ 29/Oct/18 ] | |
|
Hi @Kelsey.schubert I have to bring this issue up again. I have been facing this problem a few days, my secondary always stuck in STARTUP2 status, mongod.log shows
I setup replica set from a standalone mode followed doc https://docs.mongodb.com/manual/tutorial/convert-standalone-to-replica-set/ the standalone instance has 10G DB data before I turned it into replica set primary. when I add secondary into this replica set, secondary always stuck in STARTUP2, and logs shows sync failed. I have setup opog size 5120 MB, secondary runs in different machine. mongodb v3.6.8 attached file is secondary [^mongod.log] If you need any further info I would be glad to provide. unable to upload mongod.log I upload it https://send.firefox.com/download/a30ef9a89b/#nw2RcwAeeJg9nyR4sOFBcQ | |
| Comment by Kelsey Schubert [ 27/Jun/17 ] | |
|
Hi salzamt, So we can investigate, would you please open a new ticket with the complete log files and diagnostic.data for each node in the affected replica set? Thank you, | |
| Comment by riccardo salzer [ 27/Jun/17 ] | |
|
having the same issue, as soon as an old replica member switches the sync source to the new member, a lot of
occur in the logs until it switches back to a member which initially had been in the set. for us, after 24 hours we got the first replication lag warning. | |
| Comment by Kelsey Schubert [ 21/Apr/17 ] | |
|
Hi, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Thank you, | |
| Comment by Kelsey Schubert [ 16/Feb/17 ] | |
|
Hi vingrad, Thanks for reporting this behavior. So we can investigate, would you please provide the diagnostic.data of both the primary and secondary nodes? Would you please open a new SERVER ticket and attach diagnostic.data of the primary? It's not expected that the replication lag would increase after upgrading to MongoDB 3.4.2. Thank you for your help, | |
| Comment by Peter Chan [ 15/Feb/17 ] | |
|
One more update: Simply downgrading the Ubuntu secondaries to 3.2.12, with the source of the replication still on 3.4.2, did not work. The error message disappeared after downgrade, but the secondaries on Ubuntu/Mongo 3.2.12 continue to increasingly lag. It was not until the replication source is also downgraded to 3.2.12 that the lagging secondaries catch up with the replication. | |
| Comment by Peter Chan [ 15/Feb/17 ] | |
|
I am seeing a similar error message on my setup, with the following additional information that maybe helpful:
|