[SERVER-415] Increasing slave lagging Created: 12/Nov/09 Updated: 12/Jul/16 Resolved: 12/Nov/09 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 1.0.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Erwan Arzur | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
processor : 0 processor : 1 Linux ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:34:28 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
2x256GB EBS volumes, stripped. 80% used.
4x420GB (local, ephemeral) stripped, 26% used |
||
| Attachments: |
|
| Participants: |
| Description |
|
Just posted a message on the group with a complete description: http://groups.google.com/group/mongodb-user/browse_frm/thread/2fd21b8791de910c Basically, we're witnessing increasing lag, up to 30 hours on our slaves, with no particular reason (no heavy concurrent updates, not much reading, etc ...) Trying to upgrade to a bigger hardware platform, but data migration is a very big issue for us ... |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 12/Nov/09 ] |
|
Ok. |
| Comment by Erwan Arzur [ 12/Nov/09 ] |
|
No, slave is 1.0.1. Master was 1.0.0, now updated to 1.0.1. |
| Comment by Eliot Horowitz (Inactive) [ 12/Nov/09 ] |
|
so the slave is on 1.1.3 and the master on 1.0.1 |
| Comment by Erwan Arzur [ 12/Nov/09 ] |
|
Right, i just did the upgrade, and the slave seems to catch up, but at a slower rate than what i would expect. Thu Nov 12 15:17:33 repl: end sync_pullOpLog syncedTo: Wed Nov 11 21:08:04 2009 4afb27b4:6 |
| Comment by Eliot Horowitz (Inactive) [ 12/Nov/09 ] |
|
You found this bug: |
| Comment by Erwan Arzur [ 12/Nov/09 ] |
|
Mongod output ... |
| Comment by Eliot Horowitz (Inactive) [ 12/Nov/09 ] |
|
can you attach the entire log file? |