<div dir="ltr">Thanks for the info!<div><br></div><div>Regards,</div><div><br></div><div>Leander</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 3, 2013 at 7:08 PM, Samuel Merritt <span dir="ltr"><<a href="mailto:sam@swiftstack.com" target="_blank">sam@swiftstack.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 1/3/13 7:07 AM, Leander Bessa Beernaert wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Hello all,<br>
<br>
Could some please confirm my analysis of the ring creation in swift?<br>
<br>
I need to run a few benchmarks on a set of data (200GB) total and need<br>
it to be replicated at least 3 times.<br>
<br></div>
From the Swift docs [1], I understood that the command below create the<div class="im"><br>
ring for a partition sized 2^18 and 3 replicas.<br>
<br>
swift-ring-builder account.builder create 18 3 1<br>
# swift-ring-builder container.builder create 18 3 1<br>
# swift-ring-builder object.builder create 18 3 1<br>
<br>
Now, in my case i should use the values 28 3 1 right, or should i factor<br>
in the replication and instead use 30 3 1?<br>
</div></blockquote>
<br>
Neither one. The partitions in the Swift ring are subsets of the range of a hash function; they don't have anything to do with the number of bytes of storage in your cluster.<br>
<br>
General rule of thumb is to figure out how many drives your cluster will ever have at its largest, and then choose the smallest part_power that gives you ~100 partitions per drive.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have at the moment 1 proxy node and 5 storage nodes with a 200GB<br>
storage partition. This won't be enough to accomodate everything right?<br>
</blockquote>
<br></div>
I don't see why not. You've got 200GB stored data * 3 replicas = 600GB raw data used, and you've got 1000GB of disk. Even with a little bit of overhead for accounts and containers, that's still plenty of disk.<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~<u></u>openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~<u></u>openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/<u></u>ListHelp</a><br>
</blockquote></div><br></div>