[SERVER-55036] Initial sync on start without reason Created: 08/Mar/21 Updated: 07/Sep/21 Resolved: 07/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benaissa El KHATTAR | Assignee: | Pavithra Vetriselvan |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2021-08-09, Execution Team 2021-08-23, Execution Team 2021-09-06, Execution Team 2021-09-20 | ||||
| Participants: | |||||
| Description |
|
I have a relicaSet with 3 data-bearing nodes and 2 arbiters. During an incomplete index build with problems we decided stop one secondary and do an initial sync for the other secondary. The primary has crushed during a logRotate, but when we tried to restart it he decides to do an initial sync with the message "No recovery needed. Initial sync flag set". Do you have any idea ? Mongo version : 4.2.11 Plateforme : CentOS release 6.3 (Final) Storage Engine : WiredTiger Data volume > 1T bytes
Best regards Benaissa El Khattar
|
| Comments |
| Comment by Pavithra Vetriselvan [ 07/Sep/21 ] |
|
Closing this ticket since there hasn't been a response recently. Feel free to re-open if there is more information, thank you. |
| Comment by Pavithra Vetriselvan [ 04/Aug/21 ] |
|
Hi elkhattarbenaissa@gmail.com, I have a few questions regarding your cluster set up to aid in diagnosing the issue: 1. Is the cluster using enableMajorityReadConcern=false? Thanks! |
| Comment by Eric Sedor [ 15/Mar/21 ] |
|
Thanks elkhattarbenaissa@gmail.com. I can see the restart of mongodb1-node at 2021-03-07T17:34:49.076+0100, as logged in logs-mongodb1-node/mongodb.log.4. I will pass this on to an appropriate team to take a look. |
| Comment by Benaissa El KHATTAR [ 11/Mar/21 ] |
|
Hi Eric, I uploaded the differents logs of the three data-bearing nodes. The collect of diagnostic data was unfortunatelly inactive for us because of production environnement. Thanks Benaissa |
| Comment by Eric Sedor [ 10/Mar/21 ] |
|
Hello, I've created a secure upload portal for you. Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. For each node in the replica set spanning a time period that includes the incident, would you please archive (tar or zip) and upload to that link:
Thanks, |