<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div><br>
Replies inline.<br>
<br>
Hi,<br>
<br>
I had the following doubts about the functioning of lustre.<br>
<br>
1. Whenever a file creation request is sent from the client, the request is sent to MDS from where a list of OSTs, file metadata etc is received.<br>
After this point does the data flow through the OSS to the OST or does the client communicate with the OST directly?<br>
<br>
That question doesn't quite make sense. The OST is just a disk volume. The clients send data to the OSS (a server) that the OST in question is connected to, then the server writes that data to the OST. This is done without involving the metadata server (MDS)
except when opening and closing the file.<br>
<br>
2. If a lustre system has more than one MDS will the client always send its requests to the same MDS or how is this decided?<br>
An individual file is always on a particular single MDS. So for a given file, the requests always go to the same MDS. Deciding which files are put on which MDS is more complicated. (This feature is known as distributed namespace or DNE, more info can be
found online)<br>
<br>
3. How does the MDS decide which OSTs have to be allocated whenever a file request has been made?<br>
There are a number of different policies available. I believe the default is a mix of round robin and space usage optimization to keep particular OSTs from filling up.<br>
<br>
4. How many OSTs can an OSS have? How is this upper limit decided if at all?<br>
I don't know what the upper limit is (it is at least 16), but the software limit is not the main concern. The OSS (the server) has to be able to move enough data to keep the OSTs fed. So while you can put many, many OSTs on one server, in practice, you would
not.<br>
<br>
5. How many clients can an application have?<br>
There is no limit. Real systems exist with tens of thousands of client nodes connected to one Lustre file system. The practical limit is not client count, it is performance of the servers, disks, and network.
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> lustre-discuss <lustre-discuss-bounces@lists.lustre.org> on behalf of Sangeetha Banavathi Srinivasa <bsangee@vt.edu><br>
<b>Sent:</b> Tuesday, June 28, 2016 7:58:03 PM<br>
<b>To:</b> lustre-discuss@lists.lustre.org<br>
<b>Subject:</b> [lustre-discuss] Query regarding MDS and OSS functions</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi,<br>
<br>
I had the following doubts about the functioning of lustre.<br>
<br>
1. Whenever a file creation request is sent from the client, the request is sent to MDS from where a list of OSTs, file metadata etc is received.<br>
After this point does the data flow through the OSS to the OST or does the client communicate with the OST directly?<br>
<br>
2. If a lustre system has more than one MDS will the client always send its requests to the same MDS or how is this decided?<br>
<br>
3. How does the MDS decide which OSTs have to be allocated whenever a file request has been made?<br>
<br>
4. How many OSTs can an OSS have? How is this upper limit decided if at all?<br>
<br>
5. How many clients can an application have?<br>
<br>
<br>
Thanks,<br>
Sangeetha<br>
_______________________________________________<br>
lustre-discuss mailing list<br>
lustre-discuss@lists.lustre.org<br>
<a href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org">http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org</a><br>
</div>
</span></font>
</body>
</html>