Bug 765215 (GLUSTER-3483) - Introduce new priority and priority-thread-limits
Summary: Introduce new priority and priority-thread-limits
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3483
Product: GlusterFS
Classification: Community
Component: io-threads
Version: mainline
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-25 12:23 UTC by Pranith Kumar K
Modified: 2011-12-16 10:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: master

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Pranith Kumar K 2011-08-25 12:23:42 UTC 
We want the rchecksum to perform with the least priority and the maximum threads that can operate on a priority queue should be configurable.
Comment 1 Anand Avati 2011-08-31 06:39:47 UTC 
CHANGE: http://review.gluster.com/318 (Change-Id: I7b4e7c467b833bc5896808e6e1d1b1a0322c4fdb) merged in master by Vijay Bellur (vijay)
Comment 2 Pranith Kumar K 2011-09-01 06:07:44 UTC 
-ve pid of the frame in io-threads denotes a request from parent xlators to put the fop in least priority queue. We need the change in io-threads to accommodate this.
Comment 3 Pranith Kumar K 2011-09-02 07:37:29 UTC 
(In reply to comment #2)
> -ve pid of the frame in io-threads denotes a request from parent xlators to put
> the fop in least priority queue. We need the change in io-threads to
> accommodate this.

This is committed as part of 3502 as one of the users hit the case. resolving this bug.
Comment 4 Rahul C S 2011-09-07 10:33:06 UTC 
Getting priority logs as per enhancement made.
Note You need to log in before you can comment on or make changes to this bug.