[SERVER-55521] Mongo 3.6.17+ support on RHEL 8.0 support gaps Created: 25/Mar/21  Updated: 31/Mar/21  Resolved: 31/Mar/21

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: venkataramans rama Assignee: Edwin Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Hi Team,

In SERVER-54805, we explained the issue where we are seeing frequent issue with SECONDARY member getting unresponsive. 
 
Since we are not having clue why it worked in CentOS7 and not working well in centOS8, we have been trying hard to check what could be the differences.  we upgraded the glibc package and it delayed the issue in 2 runs. we used to see SEC issue in 6-12 hrs of run but with the latest glibc we see its holding good for 2 days but it didnt solve the problem. 
 
But as part of the RHEL 8.0 support, mongo has changed the evergreen.yaml and added scons_cache_scope: shared instead of use_scons_cache: true. But i dont see any reference of scons_cache_scope in the mongo 3.6 build code/script that parses. The scons_cache_scope relevent code are only in 4.x releases. 
 
So wondering if there are any gaps in the compilation of the mongo in RHEL itself.  please see the code-diff.
https://github.com/mongodb/mongo/commit/76dc06194037bee31b6eedb168f553be354b1a3c
 
 



 Comments   
Comment by Edwin Zhou [ 31/Mar/21 ]

Hi veramasu@hcl.com,

The use of scons_cache_scope on MongoDB 3.6 is to enable functionality that doesn't actually exist in MongoDB 3.6, so we expect that flag to be harmless and should have no effect on the build.

I've also noticed that you're already engaged in a discussion with our community. As this ticket does not appear to be a bug report, I will now close it and I encourage you to continue your discussion with our community.

We will find it extremely helpful if you're able to reproduce the behavior described in SERVER-54805 in MongoDB 4.0. If you are able to upgrade, we invite you to share your findings in SERVER-54805, and we will be happy to reopen that ticket and resume our investigation.

Kindly,
Edwin

Generated at Thu Feb 08 05:36:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.