Details
-
Bug
-
Resolution: Fixed
-
Critical
-
4.0.0
-
Security Level: Public
-
None
Description
Right now mutation queue size can be controlled only based on the length. This is not very accurate. Implement a more accurate memory based mechanism so queue size can be limited in a better way.
Attachments
Issue Links
- is triggering
-
MB-18475 GSI: Very high indexer RAM usage under heavy load
- Closed
For Gerrit Dashboard: MB-17848 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
61401,7 | MB-17848 Memory based accounting for Mutation Queue | unstable | indexing | Status: MERGED | +2 | +1 |
61402,6 | MB-17848 Add stat for mutation queue memory | unstable | indexing | Status: MERGED | +2 | +1 |
62045,4 | MB-17848 Add separate queue config for MOI | unstable | indexing | Status: MERGED | +2 | +1 |
63423,3 | MB-17848 Reduce log messages for node alloc wait | unstable | indexing | Status: MERGED | +2 | +1 |
63424,3 | MB-17848 Add minimum size for mutation queue | unstable | indexing | Status: MERGED | +2 | +1 |
63602,2 | MB-17848 Log bucket name in mutation queue logs | unstable | indexing | Status: MERGED | +2 | +1 |
63603,2 | MB-17848 Fix unit tests for mutation queue | unstable | indexing | Status: MERGED | +2 | +1 |
63679,1 | MB-17848 Change minVbQueueLength default to 250 | unstable | indexing | Status: MERGED | +2 | +1 |
63782,3 | MB-17848 Improve memory accounting for queued items | unstable | indexing | Status: MERGED | +2 | +1 |