[SERVER-3723] 1.8.3 failover delayed 3 minutes when arbiter 2.0 Created: 30/Aug/11 Updated: 29/Feb/12 Resolved: 30/Aug/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tony Hannan | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
2 member replica set running version 1.8.3 + arbiter running version 2.0. Problem: Secondary does not become primary until 3 minutes later (see log below). No problem if all 1.8.3. Secondary log (primary was 10.182.38.10): Tue Aug 30 17:52:40 [rs Manager] replSet not electing self, not all members up and we have been up less than 5 minutes |
| Comments |
| Comment by Kristina Chodorow (Inactive) [ 30/Aug/11 ] |
|
Phew! Great. |
| Comment by Tony Hannan [ 30/Aug/11 ] |
|
Ah, you're right. With members already up for 5 minutes the failover is fast. |
| Comment by Kristina Chodorow (Inactive) [ 30/Aug/11 ] |
|
Can you retry, waiting until the secondary has been up for at least 5 minutes before killing the primary? This doesn't look like an issue with the arbiter. |