[SERVER-27274] db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } ) on replicaset primary gives no feedback, appears to hang Created: 05/Dec/16 Updated: 07/Dec/16 Resolved: 07/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Networking, Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael Brenden | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux Debian 7, 8 |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Running db.adminCommand({ setFeatureCompatibilityVersion: "3.4" }) on replicaset primary gives no feedback, appears to hang. Possibly related to causing replication failure? Entry from primary server log after replication cessation:
Corresponding entries from one secondary log after replication cessation:
|
| Comments |
| Comment by Kelsey Schubert [ 07/Dec/16 ] | |
|
Hi michaelbrenden, Thanks for the update, I'm glad your team was able to identify the root cause of these issues. Kind regards, | |
| Comment by Michael Brenden [ 07/Dec/16 ] | |
|
Please scratch this entire thread / bug report — our network team uncovered a serious misconfiguration in the network. | |
| Comment by Kelsey Schubert [ 06/Dec/16 ] | |
|
Hi michaelbrenden, I suspect that this behavior is occcuring because
I've opened Thank you, | |
| Comment by Kelsey Schubert [ 05/Dec/16 ] | |
|
I've created a secure portal for you to use. Files uploaded to this portal are only visible to MongoDB employees investigating this issue and are routinely deleted after sometime. | |
| Comment by Kelsey Schubert [ 05/Dec/16 ] | |
|
Hi michaelbrenden, Would you please upload the complete logs from the nodes in the replica set so we can continue to investigate this issue? Thank you, |