[SERVER-51803] Please backport SERVER-43641 Created: 22/Oct/20 Updated: 10/Nov/20 Resolved: 10/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 4.0.20, 4.2.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Юрий Соколов | Assignee: | Spencer Jackson |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Security 2020-11-16 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We have many mongos (v4.0.20) instances running in a pod in kubernetes. And there is a lot of such pods in every node. Occasionally we got strange error:
(Sometimes it is [conn-nnn] instead of [TaskExecutorPool-0]) Looks like there some kernel bug or limitation concerning too many openings of /dev/urandom (probably, in conjunction with lxc environment). Looks like patch for https://jira.mongodb.org/browse/SERVER-43641 fixes it by opening /dev/urandom just once in a process (while it was not main intention of a patch) Could you backport this patch to 4.0.x and 4.2.x, please? Or just make similar thing: open /dev/urandom once per process. |
| Comments |
| Comment by Spencer Jackson [ 10/Nov/20 ] |
|
Unfortunately, I do not believe backporting |
| Comment by Eric Sedor [ 26/Oct/20 ] |
|
Hello, We do have |