<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<p>thank you thank you... I would like to see that in IBM
documentation somewhere.<br>
</p>
<div class="moz-cite-prefix">On 3/25/20 11:50 AM, Venkateswara R
Puvvada wrote:<br>
</div>
<blockquote type="cite" cite="mid:OF40FC49E1.030DA199-ON65258536.004C764C-65258536.005C87D3@notes.na.collabserv.com">
<font size="2" face="sans-serif">Matt,</font><br>
<br>
<font size="2" face="sans-serif">It is recommended to have
dedicated
AFM gateway nodes. Memory and CPU requirements for AFM gateway
node depends
on the number of filesets handled by the node and the inode
usage of those
filesets. Since AFM keeps track of changes in the memory, any
network disturbance
can cause the memory utilization to go high and which eventually
leads
to in-memory queue to be dropped. After the queue is dropped,
AFM runs
recovery to recover the lost operations which is expensive as it
involves
creating the snapshot, running policy scan, doing readdir from
home/secondary
and build the list of lost operations. When the gateway node
goes
down, all the filesets handled by that node distributed to the
remaining
active gateway nodes. After the gateway node comes back,
filesets are transferred
back to the original gateway node. When designing the gateway
node, make
sure that it have enough memory , CPU resources for handling the
incoming
and outgoing data based on the bandwidth. Limit the filesets per
gateway(ex.
less than 20 filesets per gateway) so that number of AFM
recoveries
triggered will be minimal when the queues are lost. Also limit
the total
number of inodes handled by the gateway node across all the
filesets (ex.
less than 400 million inodes per gateway). AFM gateway nodes
are
licensed as server nodes.</font><br>
<br>
<br>
<font size="2" face="sans-serif">~Venkat (<a class="moz-txt-link-abbreviated" href="mailto:vpuvvada@in.ibm.com">vpuvvada@in.ibm.com</a>)</font><br>
<br>
<br>
<br>
<font size="1" face="sans-serif" color="#5f5f5f">From:
</font><font size="1" face="sans-serif">Matt Weil
<a class="moz-txt-link-rfc2396E" href="mailto:mweil@wustl.edu"><mweil@wustl.edu></a></font><br>
<font size="1" face="sans-serif" color="#5f5f5f">To:
</font><font size="1" face="sans-serif"><a class="moz-txt-link-abbreviated" href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.org</a></font><br>
<font size="1" face="sans-serif" color="#5f5f5f">Date:
</font><font size="1" face="sans-serif">03/23/2020 11:39 PM</font><br>
<font size="1" face="sans-serif" color="#5f5f5f">Subject:
</font><font size="1" face="sans-serif">[EXTERNAL]
[gpfsug-discuss]
AFM gateway node scaling</font><br>
<font size="1" face="sans-serif" color="#5f5f5f">Sent by:
</font><font size="1" face="sans-serif"><a class="moz-txt-link-abbreviated" href="mailto:gpfsug-discuss-bounces@spectrumscale.org">gpfsug-discuss-bounces@spectrumscale.org</a></font><br>
<hr noshade="noshade"><br>
<br>
<br>
<tt><font size="2">Hello all,<br>
<br>
Is there any guide and or recommendation as to how to scale
this.<br>
<br>
filesets per gateway node? Is it necessary to separate NSD
server
and<br>
gateway roles. Are dedicated gateway nodes licensed as
clients?<br>
<br>
Thanks for any guidance.<br>
<br>
Matt<br>
<br>
_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at spectrumscale.org<br>
</font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" moz-do-not-send="true"><tt><font size="2">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size="2"><br>
<br>
</font></tt><br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
<a class="moz-txt-link-freetext" href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a>
</pre>
</blockquote>
</body>
</html>