[SERVER-1577] when adding arbiter the PRIMARY fails to SECONDARY immediately Created: 05/Aug/10 Updated: 12/Jul/16 Resolved: 24/Aug/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 1.6.0 |
| Fix Version/s: | 1.6.3, 1.7.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Kenny Gorman | Assignee: | Dwight Merriman |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux x64 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
When adding arbiter, immediately the PRIMARY goes to SECONDARY. Steps:
here is a log of the action: |
| Comments |
| Comment by auto [ 15/Sep/10 ] |
|
Author: {'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}Message: |
| Comment by auto [ 15/Sep/10 ] |
|
Author: {'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}Message: towards |
| Comment by auto [ 15/Sep/10 ] |
|
Author: {'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}Message: towards |
| Comment by auto [ 09/Aug/10 ] |
|
Author: {'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}Message: |
| Comment by auto [ 08/Aug/10 ] |
|
Author: {'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}Message: towards |
| Comment by auto [ 07/Aug/10 ] |
|
Author: {'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}Message: towards |
| Comment by Dwight Merriman [ 06/Aug/10 ] |
|
yes - this is as planned for 1.6.0. when the config changes there is a new negotiation of who is primary. this results in 20 seconds or so of rediscovery. some of these things will be better in 1.6.1 and 1.6.2. the plan with 1.6.0 was to avoid mistakes with edge cases, as config changes will be very rare anyway, and there are some edge cases where the primary actually should change with a new arbiter in place (unusual). working on it. |