Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-24946

Support for detecting container memory limits in ns_server

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 5.5.0
    • 5.0.0
    • ns_server
    • None
    • Untriaged
    • No

    Description

      By default, docker engine presents the entire system memory to a container. Hard limits can be set with -m command, however, it doesn't look like ns_server (or some related process) is able to detect this limit. Part of the problem is even the 'free' command will return the enter amount of memory of the docker engine, but checking the cgroup/memory dir shows that the container limits has been set:

      ie.. 4GB limit
      cat /sys/fs/cgroup/memory/memory.limit_in_bytes
      3999997952

      couchbase has it at 8GB
      curl http://192.168.99.100:8091/nodes/self
      "memoryTotal":8263184384,"memoryFree":7493025792,"mcdMemoryReserved":6304,"mcdMemoryAllocated":6304,

      Would be great if we can have couchbase detect that these limits has been set as we are currently looking to verify some DGM tests, and I suspect eviction will not occur unless we hit watermarks which are being set too high.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              tommie Tommie McAfee (Inactive)
              tommie Tommie McAfee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty