Bug 1357535 - RFE: Move throttling code to libglusterfs from bitrot
Summary: RFE: Move throttling code to libglusterfs from bitrot
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: bitrot
Version: 3.8
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: Kotresh HR
QA Contact:
bugs@gluster.org
URL:
Whiteboard:
Depends On: 1352019 1357514
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-18 13:11 UTC by Kotresh HR
Modified: 2017-11-07 10:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1357514
Environment:
Last Closed: 2017-11-07 10:40:31 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Kotresh HR 2016-07-18 13:11:56 UTC
+++ This bug was initially created as a clone of Bug #1357514 +++

+++ This bug was initially created as a clone of Bug #1352019 +++

Description of problem:
Throttling is feature by itself which any component can consume, hence it more suitable to be part of libglusterfs than to be of bitrot.

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

How reproducible:
NA

Steps to Reproduce:
NA

Actual results:
Throttling code is part of bitrot

Expected results:
Throttling code should be part of libglusterfs

--- Additional comment from Vijay Bellur on 2016-07-18 08:27:41 EDT ---

REVIEW: http://review.gluster.org/14944 (features/bitrot: Move throttling code to libglusterfs) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)

Comment 1 Vijay Bellur 2016-07-18 13:13:11 UTC
REVIEW: http://review.gluster.org/14945 (features/bitrot: Move throttling code to libglusterfs) posted (#1) for review on release-3.8 by Kotresh HR (khiremat)

Comment 2 Niels de Vos 2016-09-12 05:37:20 UTC
All 3.8.x bugs are now reported against version 3.8 (without .x). For more information, see http://www.gluster.org/pipermail/gluster-devel/2016-September/050859.html

Comment 3 Niels de Vos 2017-11-07 10:40:31 UTC
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.


Note You need to log in before you can comment on or make changes to this bug.