Bug 1702271 - Memory accounting information is not always accurate
Summary: Memory accounting information is not always accurate
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: 6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Xavi Hernandez
QA Contact:
URL:
Whiteboard:
Depends On: 1659334 1702268
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-23 11:35 UTC by Xavi Hernandez
Modified: 2019-05-22 18:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1702268
Environment:
Last Closed: 2019-05-08 13:55:13 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22607 0 None Merged core: handle memory accounting correctly 2019-05-08 13:55:12 UTC

Description Xavi Hernandez 2019-04-23 11:35:31 UTC 
+++ This bug was initially created as a clone of Bug #1702268 +++

Description of problem:

When a translator is terminated, its memory accounting information is not destroyed as there could be some memory blocks referencing it still in use. However the mutexes that protect updates of the memory accounting are destroyed.

This causes that future updates of the accounting data may contend and do concurrent updates, causing corruption of the counters.

Additionally, accounting of reallocs is not correctly computed.

Version-Release number of selected component (if applicable): mainline


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Worker Ant 2019-04-23 11:55:22 UTC 
REVIEW: https://review.gluster.org/22607 (core: handle memory accounting correctly) posted (#2) for review on release-6 by Xavi Hernandez
Comment 2 Worker Ant 2019-05-08 13:55:13 UTC 
REVIEW: https://review.gluster.org/22607 (core: handle memory accounting correctly) merged (#2) on release-6 by Xavi Hernandez
Note You need to log in before you can comment on or make changes to this bug.