Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-18919

TCMalloc failures should redirected to MongoDB log file

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Build
    • Server Security
    • ALL

      Enviroment :
      MongoDb 3.1.4, Windows
      Stand alone , hammer.mongo insert only workload

      During stress test the machine reached to out of memory state and produce allocation errors to the console windows instead to the log file.

      
src\third_party\gperftools-2.2\src\central_freelist.cc:333] tcmalloc: allocation
 failed 32768
src\third_party\gperftools-2.2\src\central_freelist.cc:333] tcmalloc: allocation
 failed 32768
src\third_party\gperftools-2.2\src\central_freelist.cc:333] tcmalloc: allocation
 failed 32768
src\third_party\gperftools-2.2\src\central_freelist.cc:333] tcmalloc: allocation
 failed 32768
src\third_party\gperftools-2.2\src\central_freelist.cc:333] tcmalloc: allocation
 failed 32768
src\third_party\gperftools-2.2\src\central_freelist.cc:333] tcmalloc: allocation
 failed 32768
src\third_party\gperftools-2.2\src\central_freelist.cc:333] tcmalloc: allocation
 failed 32768
src\third_party\gperftools-2.2\src\central_freelist.cc:333] tcmalloc: allocation
 failed 32768

      Per discussion w/ Mark we should call to
      log_message_writer in internal_loggging.h and set our own custom logging function.

            Assignee:
            backlog-server-security [DO NOT USE] Backlog - Security Team
            Reporter:
            eitan.klein Eitan Klein
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: