[SERVER-27588] Warning to disable defrag of transparent_hugepages when thp is disabled Created: 05/Jan/17  Updated: 08/Jan/24  Resolved: 06/Sep/18

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 3.4.1
Fix Version/s: 4.0.3, 4.1.3

Type: Bug Priority: Minor - P4
Reporter: Jonas Gustavsson Assignee: Benjamin Caimano (Inactive)
Resolution: Done Votes: 1
Labels: dev_tools, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Red Hat Enterprise Linux Server release 7.2 (Maipo)


Issue Links:
Backports
Depends
Related
is related to SERVER-16643 extend existing THP warning to THP de... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Steps To Reproduce:

disable transparent hugepages and start mongod

Sprint: Platforms 2018-09-10
Participants:
Case:

 Description   

A warning advising to disable defrag of transparent_hugepages is displayed even though transparent hugepages is disabled
--------------------------------------------------------

    • WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'.
    • We suggest setting it to 'never'
      --------------------------------------------------------


 Comments   
Comment by Githook User [ 07/Sep/18 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-27588 Warning to disable defrag of transparent_hugepages when thp is disabled

(cherry picked from commit a54264b53097556622e5e8e823bfacabd39ee1e7)
Branch: v4.0
https://github.com/mongodb/mongo/commit/1398498bff7148438be8fc74ea43f3469cad9569

Comment by Benjamin Caimano (Inactive) [ 06/Sep/18 ]

jonas, I've pushed the change here to master. I'll be backporting to 4.0 this Friday.

Comment by Githook User [ 06/Sep/18 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-27588 Warning to disable defrag of transparent_hugepages when thp is disabled
Branch: master
https://github.com/mongodb/mongo/commit/a54264b53097556622e5e8e823bfacabd39ee1e7

Comment by Mark Agarunov [ 10/Jan/17 ]

Hi jonas ,

Thanks for reporting this, we were able to reproduce this and are investigating further, please continue to watch for updates.

Thanks,
Mark

Generated at Thu Feb 08 04:15:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.