bugGluster - Bugs: bug #26579, option autoscaling on in...

 
 

bug #26579: option autoscaling on in performance/io-threads creates problems

Submitted by:  None
Submitted on:  Thu 14 May 2009 06:04:17 PM UTC  
 
Category: GlusterFSSeverity: 3 - Normal
Priority: 5 - NormalItem Group: Improper behaviour
Status: FixedPrivacy: Public
Assigned to: Shehjar Tikoo <shehjart>Originator Name: anonymous
Originator Email: -unavailable-Open/Closed: Closed
Release: Operating System: GNU/Linux
Reproducibility: Every Time

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Mon 22 Jun 2009 02:01:22 PM UTC, comment #2:

fixed in 2.0.2.

--
Gowda

Basavanagowda Kanur <gowda>
Project Member
Thu 14 May 2009 06:30:18 PM UTC, comment #1:

You can continue to use autoscaling while placing an upper and lower limit on the number of threads. We provide two options in the io-threads translator specifically because we understand that the default value for any option does not work well for all configurations.

This can be done using the min-threads and max-threads options.
See http://www.gluster.org/docs/index.php/Translators_options#performance.2Fio-threads

The intention of having an upper limit on the thread count is because threads do consume memory which could be used for other programs, if most threads are just sitting idle.

The thread-count option is supposed to be used when autoscaling is off and the user wants to specify a non-default yet static number of threads.

Hope that helps.

Shehjar Tikoo <shehjart>
Project MemberIn charge of this item.
Thu 14 May 2009 06:04:17 PM UTC, original submission:

v2.0.1.
Just the use of "option autoscaling on" (see volfile below) makes gluster use ~250 threads (the default limi) even with little to medium load.

After about 10 hours it proceed to lock and drop connections after using ~3GiB of VSS and ~500MiB of RSS on a 32bit machine with 8 gigs of RAM.

I got a

[2009-05-14 17:48:11] W [io-threads.c:2206:init] export-homes: 'thread-count' is specified with 'autoscaling' on. Ignoring'thread-count' option.

because of the conflicting options, but I think it's not relevant.

volume brick-homes
type storage/posix
option directory /srv/data/homes
end-volume

volume locks
type features/posix-locks
subvolumes brick-homes
end-volume

volume export-homes
type performance/io-threads
option autoscaling on
option thread-count 16 # default is 16
subvolumes locks
end-volume

### Add network serving capability to above brick.
volume server
type protocol/server
option transport-type tcp/server # For TCP/IP transport
option listen-port 6997
subvolumes export-homes
option auth.addr.locks.allow 192.168.3.2 # AFR, turing2
option auth.addr.export-homes.allow * # Clients
end-volume

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by gowda (Posted a comment)
  • -unavailable- added by shehjart (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 6 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Mon 22 Jun 2009 02:01:22 PM UTCgowdaStatusIn Progress=>Fixed
      Open/ClosedOpen=>Closed
    Thu 14 May 2009 06:30:18 PM UTCshehjartStatusNone=>In Progress
      Assigned toNone=>shehjart
      Originator Name=>anonymous
      Originator Email=>anonymous@anon,com

    Back to the top


    Powered by Savane 3.1-cleanup1