26 June,2020 by Rambler
A bug on MongoDB 4.2.7 has been identified- and a fix is included in 4.2.8 .Certain conditions are required for the bug to appear - detailed below. Based on the supporting documentation for the MongoDB 4.2.7 bug to occur:
If these conditions are met , there is a possibility that MongoDB will improperly overwrite memory.
Read here for greater detail supplied by MongoDB
To fix you will need to upgrade the Replica Set version from 4.2.7 to 4.2.8 . The upgrade does require a host restart - so ensure all checks are made regarding data recovery points and any existing users connected which which you can get using How to list MongoDB connections - client ip and port
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |