[SERVER-34075] powercycle_replication* must run replication recovery to observe canary documents Created: 22/Mar/18 Updated: 29/Oct/23 Resolved: 01/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.6, 4.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Jonathan Abrahams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | rollback-non-functional | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||||||||||||||||||
| Sprint: | TIG 2018-04-23, TIG 2018-05-07 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 80 | ||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||
| Description |
|
Specifically, after The powercycle tests bring a node back up to check for the canary document in standalone mode and the node is brought up on a different port than is used when running as a replica set member. We suspect |
| Comments |
| Comment by Githook User [ 22/May/18 ] | |||||
|
Author: {'username': 'hptabster', 'name': 'Jonathan Abrahams', 'email': 'jonathan@mongodb.com'}Message: (cherry picked from commit 0c242bc59fd1db69a891c73dc82a29c69f13a400) | |||||
| Comment by Githook User [ 01/May/18 ] | |||||
|
Author: {'email': 'jonathan@mongodb.com', 'name': 'Jonathan Abrahams', 'username': 'hptabster'}Message: | |||||
| Comment by Jonathan Abrahams [ 11/Apr/18 ] | |||||
|
Starting mongod up in recovery (standalone) with noIdexBuildRetry fails with the following:
| |||||
| Comment by Eric Milkie [ 11/Apr/18 ] | |||||
|
| |||||
| Comment by Jonathan Abrahams [ 11/Apr/18 ] | |||||
|
max.hirschhorn We cannot use --noIndexBuildRetry option in a replicaSet and would have to start it up as a standalone node:
| |||||
| Comment by Max Hirschhorn [ 10/Apr/18 ] | |||||
|
jonathan.abrahams, it doesn't appear that | |||||
| Comment by Jonathan Abrahams [ 10/Apr/18 ] | |||||
|
Replication tests are failing, need to wait for the fix in | |||||
| Comment by Jonathan Abrahams [ 09/Apr/18 ] | |||||
|
The powercycle test does not start the recovery node, on the secret port, as a single node replica set. I do not recall why this was done this way. I'll make a patch build to try always starting replication tests with the node as a replica set member. | |||||
| Comment by Max Hirschhorn [ 27/Mar/18 ] | |||||
|
We should see if the mongod isn't being restarted as a replica set member when started on the secret port as there is already logic to do a reconfig so the node and identify itself in the configuration. |