number of open files limit

Bug #1283007 reported by Simon Wilkins
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mongodb (Ubuntu)
Fix Released
James Page
Fix Released
James Page

Bug Description

The recommended open files limit for mongoDB is 64000 - currently it defaults to 1024/4096.

[mongod #1022 -- limits]
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 31455 31455 processes
Max open files 1024 4096 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 31455 31455 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us

Could this be modified in the upstart script

Tags: patch
Revision history for this message
Simon Wilkins (s-wilkins) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "mongodb.conf.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Simon Wilkins (s-wilkins) wrote :

Please ignore and set to invalid - I've just discovered I was using a puppet managed mongodb.conf

Revision history for this message
Simon Wilkins (s-wilkins) wrote :

I take it all back - the mongodb.conf wasn't puppet-managed after all, so I think it is valid. I'm so sorry!

Robie Basak (racb)
Changed in mongodb (Ubuntu):
importance: Undecided → Medium
James Page (james-page)
Changed in mongodb (Ubuntu Trusty):
assignee: nobody → James Page (james-page)
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mongodb - 1:2.4.9-1ubuntu1

mongodb (1:2.4.9-1ubuntu1) trusty; urgency=medium

  * Enable ppc64el build (LP: #1288633):
    - d/control: Add ppc64el to target architectures.
    - d/control: Use google-perftools on ppc64el.
    - d/p/0004-Support-ppc64el-builds.patch: Detect ppc64 as 64 bit platform.
  * Enable javascript-less arm64 build (LP: #1288634):
    - d/control: Add arm64 to target architectures, ignore libv8-dev for arm64.
    - d/p/0002-SERVER-12065-Support-ARM-and-AArch64-builds.patch: Add support
      for arm64.
    - d/p/0001-Add-option-to-disable-javascript.patch: Add option to disable
      javascript engine.
    - d/rules: Disable scripting and drop mongo binary for arm64.
  * General non-x86 enablement:
    - d/p/0005-ARM-support-for-ASM-operations-in-MongoDB.patch: dropped in
      preference to upstream accepted patch from Robie Basak:
    - d/p/0001-SERVER-12064-Atomic-operations-for-gcc-non-Intel-arc.patch: Use
      gcc provided atomic operations for non-Intel archs.
  * d/mongodb-server.mongodb.upstart: Bump nofile limit to 64000 (LP: #1283007).
  * d/control: Use google-perftools on armhf.
 -- James Page <email address hidden> Thu, 06 Mar 2014 11:08:10 +0000

Changed in mongodb (Ubuntu Trusty):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers