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

Memory growth when processing many metadata operations

    XMLWordPrintable

    Details

    • Triage:
      Untriaged
    • Story Points:
      1
    • Is this a Regression?:
      No

      Description

      There is growth of jemalloc resident memory when indexer performs many metadata operations. Steps to reproduce:

      1. setup 1 node cluster with kv+n1ql+index with MOI and large memory quota.
      2. create 30 indexes with defer build (no need to build indexes).
      3. delete 30 indexes.

      After repeating steps (2) and (3) ~50 times, jemalloc resident memory reaches ~220MB. The attached jemalloc profile (jemalloc-101.prof.svg) shows that most of the memory is allocated by fdb_iterator_init() and fdb_snapshot_open().

        Attachments

          Issue Links

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

            Activity

            Hide
            build-team Couchbase Build Team added a comment -

            Build couchbase-server-7.0.0-2458 contains gometa commit d8b06db with commit message:
            MB-39751: Memory growth when processing many metadata operations

            Show
            build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.0-2458 contains gometa commit d8b06db with commit message: MB-39751 : Memory growth when processing many metadata operations
            Hide
            bhargava.yadavalli Bhargava Yadavalli (Inactive) added a comment - - edited

            On 6.6.0-7909 has large growth: ~5MB(5263360) -> ~500MB(520568832)
            On 6.6.1-9126 does not have much growth: ~5MB(4874240) -> ~30MB(31920128) fix is working fine

            On 7.0.0-3490 does not have much growth: ~6MB(4874240) -> ~36MB(36007936) fix is working fine

             

            Show
            bhargava.yadavalli Bhargava Yadavalli (Inactive) added a comment - - edited On 6.6.0-7909 has large growth: ~5MB(5263360) -> ~500MB(520568832) On 6.6.1-9126 does not have much growth: ~5MB(4874240) -> ~30MB(31920128) fix is working fine On 7.0.0-3490 does not have much growth: ~6MB(4874240) -> ~36MB(36007936) fix is working fine  

              People

              Assignee:
              bhargava.yadavalli Bhargava Yadavalli (Inactive)
              Reporter:
              akhil.mundroy Akhil Mundroy
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Gerrit Reviews

                    PagerDuty