Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory utilization on storage nodes goes high due to tendrl-gluster-integration #681

Closed
shtripat opened this issue Jul 11, 2018 · 1 comment
Milestone

Comments

@shtripat
Copy link
Member

Due to in-memory calls if gfapi while volume utilization calculation, this happens. There seems to be some memory leak issues in gfapi and to avoid that we should make gfapi call as subprocess (as it was earlier) and instead of callin it volume by volume, pass the list of volumes to the exe for utilization calculation.

shtripat pushed a commit to shtripat/gluster_bridge that referenced this issue Jul 11, 2018
There seems to be some meory leaks in gfapi and due to that if we
make in-memory calls to gfapi, the memory utilization on the nodes
keeps increasing slowly. If we make subprocess call this increase would
be eventual and no overall increase happens to the memory utilization
of the node.

tendrl-bug-id: Tendrl#681
bugzilla: 1599987
Signed-off-by: Shubhendu <shtripat@redhat.com>
shtripat pushed a commit to shtripat/gluster_bridge that referenced this issue Jul 12, 2018
There seems to be some meory leaks in gfapi and due to that if we
make in-memory calls to gfapi, the memory utilization on the nodes
keeps increasing slowly. If we make subprocess call this increase would
be eventual and no overall increase happens to the memory utilization
of the node.

tendrl-bug-id: Tendrl#681
bugzilla: 1599987
Signed-off-by: Shubhendu <shtripat@redhat.com>
shtripat pushed a commit to shtripat/gluster_bridge that referenced this issue Jul 12, 2018
There seems to be some meory leaks in gfapi and due to that if we
make in-memory calls to gfapi, the memory utilization on the nodes
keeps increasing slowly. If we make subprocess call this increase would
be eventual and no overall increase happens to the memory utilization
of the node.

tendrl-bug-id: Tendrl#681
bugzilla: 1599987
Signed-off-by: Shubhendu <shtripat@redhat.com>
shtripat pushed a commit to shtripat/gluster_bridge that referenced this issue Jul 13, 2018
There seems to be some meory leaks in gfapi and due to that if we
make in-memory calls to gfapi, the memory utilization on the nodes
keeps increasing slowly. If we make subprocess call this increase would
be eventual and no overall increase happens to the memory utilization
of the node.

tendrl-bug-id: Tendrl#681
bugzilla: 1599987
Signed-off-by: Shubhendu <shtripat@redhat.com>
@shtripat shtripat added this to the Milestone 8 milestone Jul 27, 2018
@shtripat
Copy link
Member Author

Closing as required changes merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant