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

Set environment variable GODEBUG=madvdontneed=1 for indexer

    XMLWordPrintable

Details

    • Untriaged
    • 1
    • Unknown

    Description

      Due to the issues seen in MB-47600 and MB-44731, the indexer's golang version upgrade(go1.13.7->go1.16.5) for 7.0.2 has been reverted.

      The golang upgrade was also required to address the high memory usage issue seen in MB-46323.

      As the upgrade is not possible now, the high memory usage issue needs to be addressed via setting the following environment variable when indexer is started on command line.

      GODEBUG=madvdontneed=1

      As ns-server spawns the indexer process, this change needs to be done in ns-server code.

      For reference, ns-server already has the code to set the GOTRACEBACK env variable for indexer:
      https://github.com/couchbase/ns_server/blob/master/src/ns_ports_setup.erl

      Attachments

        Issue Links

          backports to

          Bug - A problem which impairs or prevents the functions of the product. MB-49843 [Backport MB-48190 to 6.6.4] Set environment variable GODEBUG=madvdontneed=1 for indexer

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MB-47600 [System Test] Rebalance failed with service_rebalance_failed : ServiceAPI.GetTaskList

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MB-44731 [System Test] Rebalance failed as indexer on a node crashed with status 133 - Disable Breakpad integration in ForestDB

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MB-46323 [System Test] Index rebalance took 23h to complete

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              timofey.barmin Timofey Barmin
              deepkaran.salooja Deepkaran Salooja
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty