Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.0.4, 6.5.0, Cheshire-Cat
-
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
For Gerrit Dashboard: MB-39751 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
131234,1 | MB-39751: Memory growth when processing many metadata operations | master | gometa | Status: MERGED | +2 | +1 |
137091,1 | MB-40127: Memory growth when processing many metadata operations | mad-hatter | gometa | Status: MERGED | +2 | +1 |
141166,2 | MB-42947: Memory growth when processing many metadata operations | alice | gometa | Status: MERGED | +2 | +1 |
142857,1 | MB-43039: Memory growth when processing many metadata operations | 6.5.2 | gometa | Status: MERGED | +2 | +1 |