Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

PetaSAN 2.2 Released!

Pages: 1 2 3 4

Happy to announce PetaSAN 2.2 with the following main additions:

  • Erasure Coded Pools for lower storage overhead.
  • VLAN tagging support.
  • SMART disk health monitoring and notifications.

The installer allows upgrade from version 2.1.

Great news !!!!!!!!!!!

Nice - so i can reinstall my broken/misconfigured cluster 🙂

Thanks for the new release.

 

I am installing the cluster now. I do not see the replica option, only 2 and 3 . ?

 

is there something I am misssing.

 

Thanks

During initial deployment/cluster creation, we create a default replicated pool named "rbd",  you can choose it to be either 2x or 3x replicas.

Once the cluster is built, in the management interface you can go to the Pools page and add/delete/edit both replicated and EC pools. You can delete the default pool or increase its replica size if you wish.

Hello Admin,

 

I have finished creating the cluster. https://ibb.co/cEoBOV

Can you please let me know which of these options will give us EC. and if you can tell us if there is a calculator that would give me a proper sizing. now I have 3 nodes and the size is  218.30 TB (0.01%) - which is raw. with EC what would it be. and I will be putting 3 mode nodes ( total of six ) - let me know if that would change the size or number of nodes we can lose without loosing the cluster.

Thanks

this is the edit pool page, you cannot change the pool type of an existing pool. what you need is to add a new pool, from the Pools page there is an add button. You will also need first create an EC rule from the rules page, you can pick from existing templates.

for six nodes: you should use the k=4 m=2 profile, this is a recommended profile, its overhead is 6/4= 1.5 so if you write 100 GB it will use 150 GB raw. If you use compression, you will get lower usage. This setup allows 2 nodes with their disks to be destroyed without loss of data.

You also need a replicated pool in addition to the EC pool to create rbd images/iSCSI disks, the first to store metadata. so with the above profile you should have your replicated pool 3x to also sustain 2 node losses.

Thanks for the reply

Can I start with the same setup with 3 and just add the nodes later.  I just want to testit before I addthe other nodes

Thanks

You need k+m nodes/racks to run EC

For 3  nodes you can use the k=2 m=1 profile for testing but this is not recommended for real production. for testing you can set the min pool size to 2 (we set it to k+1 = 3) so your io will still be active if 1 node fails..again this is not safe and not recommended as you would be writing to a pool which now has no redundancy.

Thanks Admin,

Do you have any docs or notes that you can share with us. Just to give scenarios, and different types of setups. in addition to a description of K , M etc.

 

Thanks

Pages: 1 2 3 4