<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
comments are inline.<br>
<br>
<div class="moz-cite-prefix">On 05/02/2016 05:06 PM, Lindsay
Mathieson wrote:<br>
</div>
<blockquote
cite="mid:66c04e3b-ca35-0698-69c5-0f9129ec8682@gmail.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 2/05/2016 2:29 PM, Mohammed Rafi K
C wrote:<br>
</div>
<blockquote cite="mid:5726D7B6.7040104@redhat.com" type="cite">Hi
Lindsay,<br>
<br>
Volume level data tiering was made fully supported in latest 3.7
releases, though an active effort is still going on to increase
the small file performance. You can find a starting point
through the blog post by Dan [1].<br>
<br>
Let me know if you have any additional questions.<br>
<br>
[1] : <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://blog.gluster.org/2016/03/automated-tiering-in-gluster/">http://blog.gluster.org/2016/03/automated-tiering-in-gluster/</a></blockquote>
<br>
<p><br>
</p>
<p><br>
</p>
<p>Thanks Mohammed, an informative read. When things have settled
down a bit at work I'l setup a test volume to attach tiers to.
Ironically, now we've migrated the production env to gluster, my
ability to test is lessened - can't tweak it arbitrarily now :)</p>
</blockquote>
<br>
I understand that, and I know the effort you put to achieve it :). I
really appreciate it .<br>
<br>
In fact , tiering is for an eventual performance boost, so no hurry,
we can start eventually ;). just kidding. :)<br>
<br>
<blockquote
cite="mid:66c04e3b-ca35-0698-69c5-0f9129ec8682@gmail.com"
type="cite">
<p><br>
</p>
<p>Some questions:</p>
<p>- Does the hot tier replication level have to match the cold
tier? i.e brick for brick?</p>
</blockquote>
Nop. To understand it easily, You can consider hot tier and cold
tier as a separate volume which clubbed together as a single volume.
Which means you can create a different configuration in both tiers.
In fact there are some volume configuration we are not supporting on
hot tier, like disperse. There is no point of configuring a high
performance ssd for ec, right ? <br>
<br>
You can use supported volume configuration in any magnitude.<br>
<br>
<br>
<blockquote
cite="mid:66c04e3b-ca35-0698-69c5-0f9129ec8682@gmail.com"
type="cite">
<p>- I presume the files are promoted across all bricks. i.e you
can't have different files promoted per brick.</p>
</blockquote>
<br>
I didn't get your question correctly. But I will try to answer
generically . File movement happens from one tier to another tier,
as I mentioned earlier, you can consider this as moving one file
from one volume to another volume. <br>
<br>
As an example, let us assume, you are moving a file from hot tier
(replica configuration) to a cold tier which is a distributed
disperse configuration, then the file will be hashed to any of the
distribute set, then the file will be created with ec meta data
(data and parity).<br>
<br>
I'm not sure, I made it more complicated ;).<br>
<br>
<blockquote
cite="mid:66c04e3b-ca35-0698-69c5-0f9129ec8682@gmail.com"
type="cite">
<p>- With sharded volumes its the individual shards that are
promoted?</p>
</blockquote>
<br>
Since shardes are stored as a separate files in backend, the
movement will be based on shardes.<br>
<br>
Please feel free to ask if you have any other question of if you
need more clarification on given answers.<br>
<br>
Regards<br>
Rafi KC<br>
<br>
<blockquote
cite="mid:66c04e3b-ca35-0698-69c5-0f9129ec8682@gmail.com"
type="cite">
<p><br>
</p>
<p><br>
</p>
<p>thanks,<br>
</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Lindsay Mathieson</pre>
</blockquote>
<br>
</body>
</html>