All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Braam <Peter.Braam@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] How store HSM metadata in MDT ?
Date: Fri, 11 Jul 2008 16:03:18 -0600	[thread overview]
Message-ID: <C49D34C6.63DB%peter.braam@sun.com> (raw)
In-Reply-To: <48776F10.60008@cea.fr>




On 7/11/08 8:32 AM, "Jacques-Charles Lafoucriere" <jc.lafoucriere@cea.fr>
wrote:

> 
> 
> Peter Braam wrote:
>>  
>>>  
>>>>  
>>>> 3. how are multiple coordinators and agents utilized to distribute load so
>>>> that the HSM can keep up with massive small file creation?
>>>>       
>>>>  
>>>  
>>> One coordinator per MDT.
>>>     
>>>  
>>  
>> 
>> No - these must be independent considerations.  A coordinator may be much
>> slower than an MDS node in handling a single file.  I say this because this
>> has been the experience in the industry so far - with small files the HSM
>> can not at all keep up.
>>   
> 
> Why a coordinator should be on a slower node than a MDS ?
> Coordinator is a Lustre service  like other Lustre services so it will be on a
> right hardware
> 
I see no reason whatsoever to couple them to MDT?s.  Keeping them de-coupled
is more flexible and can scale better.  Am I missing issues here?

As for performance the following: a coordinator may have a lot of work to do
to track which files still need to be handled by agents and which are in
progress already and may have a fair amount of interaction with agents (not
with HSM to tape but when a coordinator is handling a re-striping migration
it will). But its interaction with the MDT?s is very limited.  So we could
degrade the performance of an MDS by placing this on the same node.  Let?s
keep this flexible please.

Peter
> 
> 
> Do you mean a coordinator is not part of the Lustre cluster ?
> 
> JC
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20080711/3f45bcee/attachment.htm>

  reply	other threads:[~2008-07-11 22:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 11:43 [Lustre-devel] How store HSM metadata in MDT ? Aurelien Degremont
2008-07-03 21:10 ` Peter Braam
2008-07-04 14:37   ` Aurelien Degremont
2008-07-05 16:50     ` Andreas Dilger
2008-07-06  3:20       ` Peter Braam
2008-07-06  3:24     ` Peter Braam
2008-07-06 19:24       ` Lee Ward
2008-07-06 22:53         ` Peter Braam
2008-07-08 12:06           ` Rick Matthews
2008-07-08  8:52         ` Aurelien Degremont
2008-07-08 17:41           ` Peter Braam
2008-07-09 13:25             ` Aurelien Degremont
2008-07-09 13:49               ` Peter Braam
2008-07-11 14:32                 ` Jacques-Charles Lafoucriere
2008-07-11 22:03                   ` Peter Braam [this message]
2008-07-11 14:37                 ` Jacques-Charles Lafoucriere
2008-07-11 22:12                   ` Peter Braam
2008-07-11 14:31       ` Jacques-Charles Lafoucriere
2008-07-11 21:57         ` Peter Braam
2008-07-16 10:26           ` Jacques-Charles Lafoucriere
2008-07-16 19:00             ` Peter Braam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C49D34C6.63DB%peter.braam@sun.com \
    --to=peter.braam@sun.com \
    --cc=lustre-devel@lists.lustre.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.