[SERVER-40136] The background key generator can remain disabled on FCV upgrade after a downgrade Created: 14/Mar/19 Updated: 29/Oct/23 Resolved: 18/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.11 |
| Fix Version/s: | 3.6.13 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Misha Tyulenev |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | SWCW | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||
| Sprint: | Sharding 2019-04-08, Sharding 2019-04-22 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
The background key generator thread is what generates signature keys for cluster time validation. The lifetime of the key generator is like this:
The following problems exist with these transitions:
|
| Comments |
| Comment by Vinicius Grippa [ 28/Oct/19 ] | |||||||||||||||||
|
Just for future reference. The issue is not present anymore on 3.6.13. I repeated the tests and the thing is that it takes a while but the key generator is started:
Thanks for your time. | |||||||||||||||||
| Comment by Kaloian Manassiev [ 21/Oct/19 ] | |||||||||||||||||
|
vgrippa@gmail.com, would it be possible to create a new SERVER ticket with the exact steps that you went through and the symptoms that you experienced? This will help us evaluate whether this is a different manifestation of the same bug or a different problem altogether. Also, please include information on what environment did you run these steps agains. Thank you in advance. Best regards, | |||||||||||||||||
| Comment by Vinicius Grippa [ 17/Oct/19 ] | |||||||||||||||||
|
Hi,
I tested version 3.6.13 and the issue still persists. The steps used are on the description of the issue:
FCV change sequence from 3.6 -> 3.4 -> 3.6 . | |||||||||||||||||
| Comment by Githook User [ 18/Apr/19 ] | |||||||||||||||||
|
Author: {'name': 'Misha Tyulenev', 'username': 'mikety', 'email': 'misha@mongodb.com'}Message: | |||||||||||||||||
| Comment by Kaloian Manassiev [ 18/Apr/19 ] | |||||||||||||||||
|
The second bullet in the description applies to 4.2 as well, doesn't it (that the key generator will continue running on secondaries)? Will this result in unnecessary log spam with NotMaster errors for example? | |||||||||||||||||
| Comment by Misha Tyulenev [ 18/Apr/19 ] | |||||||||||||||||
|
The issue affects only 3.6 as its on the 3.4 downgrade path |