PetaSAN distributed cluster
Serg
4 Posts
October 7, 2018, 8:15 amQuote from Serg on October 7, 2018, 8:15 amHello
Can PetaSAN work as a distributed cluster over three datacenters with L3-network connectivity?
Hello
Can PetaSAN work as a distributed cluster over three datacenters with L3-network connectivity?
admin
2,930 Posts
October 7, 2018, 12:19 pmQuote from admin on October 7, 2018, 12:19 pmYes it can. In version 2.1 you can create datacenters and specify storage pools to place a replica in each, or even a different combination if needed.
Some points to note:
- You would need an odd number of datacenters (3 as you stated), so in case of 1 datacenter goes down, you still have a quorum between datacenter monitors.
- The primary issue you have is the L3 link: not just bandwidth but more important is the latency. Since all replicas are written synchronously, your io will be affected a lot by this: this is specially true if your workload does many small block size io operations (such as a database applications rather than a video streaming or backup applications), latency and hence iops would be a deciding factor.
- Though the above is do-able, a more common approach is to do separate datacenter installations and divide the load among them, then do asynchronous replication between them so in case one fails, its load will fail over the others (basically a disaster recovery setup). Asynchronous replication is planed for PetaSAN v 2.3 and 2.4.
Yes it can. In version 2.1 you can create datacenters and specify storage pools to place a replica in each, or even a different combination if needed.
Some points to note:
- You would need an odd number of datacenters (3 as you stated), so in case of 1 datacenter goes down, you still have a quorum between datacenter monitors.
- The primary issue you have is the L3 link: not just bandwidth but more important is the latency. Since all replicas are written synchronously, your io will be affected a lot by this: this is specially true if your workload does many small block size io operations (such as a database applications rather than a video streaming or backup applications), latency and hence iops would be a deciding factor.
- Though the above is do-able, a more common approach is to do separate datacenter installations and divide the load among them, then do asynchronous replication between them so in case one fails, its load will fail over the others (basically a disaster recovery setup). Asynchronous replication is planed for PetaSAN v 2.3 and 2.4.
Last edited on October 7, 2018, 12:25 pm by admin · #2
PetaSAN distributed cluster
Serg
4 Posts
October 7, 2018, 8:15 am
Quote from Serg on October 7, 2018, 8:15 amHello
Can PetaSAN work as a distributed cluster over three datacenters with L3-network connectivity?
Hello
Can PetaSAN work as a distributed cluster over three datacenters with L3-network connectivity?
admin
2,930 Posts
October 7, 2018, 12:19 pm
Quote from admin on October 7, 2018, 12:19 pmYes it can. In version 2.1 you can create datacenters and specify storage pools to place a replica in each, or even a different combination if needed.
Some points to note:
- You would need an odd number of datacenters (3 as you stated), so in case of 1 datacenter goes down, you still have a quorum between datacenter monitors.
- The primary issue you have is the L3 link: not just bandwidth but more important is the latency. Since all replicas are written synchronously, your io will be affected a lot by this: this is specially true if your workload does many small block size io operations (such as a database applications rather than a video streaming or backup applications), latency and hence iops would be a deciding factor.
- Though the above is do-able, a more common approach is to do separate datacenter installations and divide the load among them, then do asynchronous replication between them so in case one fails, its load will fail over the others (basically a disaster recovery setup). Asynchronous replication is planed for PetaSAN v 2.3 and 2.4.
Yes it can. In version 2.1 you can create datacenters and specify storage pools to place a replica in each, or even a different combination if needed.
Some points to note:
- You would need an odd number of datacenters (3 as you stated), so in case of 1 datacenter goes down, you still have a quorum between datacenter monitors.
- The primary issue you have is the L3 link: not just bandwidth but more important is the latency. Since all replicas are written synchronously, your io will be affected a lot by this: this is specially true if your workload does many small block size io operations (such as a database applications rather than a video streaming or backup applications), latency and hence iops would be a deciding factor.
- Though the above is do-able, a more common approach is to do separate datacenter installations and divide the load among them, then do asynchronous replication between them so in case one fails, its load will fail over the others (basically a disaster recovery setup). Asynchronous replication is planed for PetaSAN v 2.3 and 2.4.
Last edited on October 7, 2018, 12:25 pm by admin · #2