[SERVER-595] restarting replication - making finding first object fast Created: 02/Feb/10 Updated: 12/Jul/16 Resolved: 02/Feb/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.2 |
| Type: | Improvement | Priority: | Critical - P2 |
| Reporter: | Eliot Horowitz (Inactive) | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Scanning backwards can be really slow if replication was paused for significant time. Theory: scanning backwards is horribly slow because every 4k have to seek Solution:
If we can do this simply - might be worth backporting to 1.2.x |
| Comments |
| Comment by auto [ 06/Feb/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by Aaron Staple [ 02/Feb/10 ] |
|
I can't do the backport w/o some instructions. Let me know if you want me to work on that. Might want to test new code in your production environment first though. |
| Comment by auto [ 02/Feb/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by auto [ 02/Feb/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by auto [ 02/Feb/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by Eliot Horowitz (Inactive) [ 02/Feb/10 ] |
|
yes - we should still release the mutex like we do now |
| Comment by Aaron Staple [ 02/Feb/10 ] |
|
Do we still want to release the mutex while doing this or not? |