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

Memory growth when processing many metadata operations

    XMLWordPrintable

Details

    • Untriaged
    • 1
    • 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

            akhil.mundroy Akhil Mundroy created issue -
            akhil.mundroy Akhil Mundroy made changes -
            Field Original Value New Value
            Link This issue is triggered by CBSE-8408 [ CBSE-8408 ]
            srinath.duvuru Srinath Duvuru made changes -
            Link This issue relates to MB-40127 [ MB-40127 ]

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

            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
            srinath.duvuru Srinath Duvuru made changes -
            Labels forestDB forestDB sec
            srinath.duvuru Srinath Duvuru made changes -
            Labels forestDB sec forestDB
            srinath.duvuru Srinath Duvuru made changes -
            Labels forestDB forestDB secondary-index
            srinath.duvuru Srinath Duvuru made changes -
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]
            wayne Wayne Siu made changes -
            Link This issue backports to MB-40127 [ MB-40127 ]
            wayne Wayne Siu made changes -
            Link This issue relates to MB-40127 [ MB-40127 ]
            wayne Wayne Siu made changes -
            Assignee Srinath Duvuru [ srinath.duvuru ] Ritam Sharma [ ritam.sharma ]
            mihir.kamdar Mihir Kamdar (Inactive) made changes -
            Assignee Ritam Sharma [ ritam.sharma ] Mihir Kamdar [ mihir.kamdar ]
            hemant.rajput Hemant Rajput made changes -
            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()}}.
            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()}}.
            bhargava.yadavalli Bhargava Yadavalli (Inactive) made changes -
            Attachment idx_insertion_deletion_6.6.1-9126 .log [ 112564 ]
            Attachment idx_insertion_deletion_6.6.0-7909.log [ 112565 ]

            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

             

            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  
            bhargava.yadavalli Bhargava Yadavalli (Inactive) made changes -
            Assignee Mihir Kamdar [ mihir.kamdar ] Bhargava Yadavalli [ JIRAUSER25133 ]
            Status Resolved [ 5 ] Closed [ 6 ]
            bhargava.yadavalli Bhargava Yadavalli (Inactive) made changes -
            Attachment test [ 112566 ]
            bhargava.yadavalli Bhargava Yadavalli (Inactive) made changes -
            Attachment idx_insertion_deletion_6.6.0-7909.log [ 112565 ]
            bhargava.yadavalli Bhargava Yadavalli (Inactive) made changes -
            Attachment idx_insertion_deletion_6.6.1-9126 .log [ 112564 ]
            bhargava.yadavalli Bhargava Yadavalli (Inactive) made changes -
            Attachment test [ 112566 ]
            srinath.duvuru Srinath Duvuru made changes -
            Link This issue backports to MB-42947 [ MB-42947 ]
            srinath.duvuru Srinath Duvuru made changes -
            Link This issue backports to MB-43039 [ MB-43039 ]
            lynn.straus Lynn Straus made changes -
            Fix Version/s 7.0.0 [ 17233 ]
            lynn.straus Lynn Straus made changes -
            Fix Version/s Cheshire-Cat [ 15915 ]

            People

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

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  PagerDuty