Search

Top 60 Oracle Blogs

Recent comments

#Exasol Fail-Safety explained

The building blocks of an Exasol cluster are commodity Intel servers like e.g. Dell PowerEdge R740 with 96 GB RAM,12 x 1.2 TB SAS Hot-plug hard-drives and 2 x 10Gb Ethernet Cards for the private network. That’s sufficient to deliver outstanding performance combined with high availability. The picture below shows a 4+1 cluster, one of our most popular configurations:

Exasol 4+1 Clusterhttps://uhesse.files.wordpress.com/2018/07/failsafe1.png?w=1240&h=908 1240w, https://uhesse.files.wordpress.com/2018/07/failsafe1.png?w=150&h=110 150w, https://uhesse.files.wordpress.com/2018/07/failsafe1.png?w=300&h=220 300w, https://uhesse.files.wordpress.com/2018/07/failsafe1.png?w=768&h=562 768w, https://uhesse.files.wordpress.com/2018/07/failsafe1.png?w=1024&h=750 1024w" sizes="(max-width: 620px) 100vw, 620px" />

Exasol 4+1 Cluster: Shared Nothing Architecture

Each active node hosts one database instance that works on its part of the database (A,B,C,D) in an MPP way. The instances communicate over the private network. Optionally, the private network can be separated into one database network and one storage network. In this case, the instances communicate over the database network. Notice that the instances access their part of the database directly on their local hard drives, they do not need the private network respectively the storage network for that. The reserve node becomes relevant only if one of the active nodes fails. The local hard drives are being setup in RAID 1 pairs, so single disk failures can be tolerated without losing database availability. Not listed is the license node that is required to boot the cluster initially. After that, the license node is no longer required to keep the cluster running.

If data volumes with redundancy 2 are in use – which is the most common case – then each node holds a copy of the data operated on by a neighbor node:

Exasol 4+1 Cluster: Redundancy 2https://uhesse.files.wordpress.com/2018/07/failsafe2.png?w=1240&h=892 1240w, https://uhesse.files.wordpress.com/2018/07/failsafe2.png?w=150&h=108 150w, https://uhesse.files.wordpress.com/2018/07/failsafe2.png?w=300&h=216 300w, https://uhesse.files.wordpress.com/2018/07/failsafe2.png?w=768&h=552 768w, https://uhesse.files.wordpress.com/2018/07/failsafe2.png?w=1024&h=736 1024w" sizes="(max-width: 620px) 100vw, 620px" />

Exasol 4+1 Cluster: Redundancy 2

If a Master-Segment like A is modified, the Slave-Segment (A’) is synchronized accordingly over the private network respectively the storage network.

Availability comes with a price: The raw disk capacity is reduced by half because of the RAID 1 mirroring and again by half because of the redundancy 2, so you remain with approximately (Linux OS and database software also require a small amount of disk space) 1/4 of your raw disk capacity. But since we are running on commodity hardware – no storage servers, no SAN, no SSDs required etc. – this is actually a very competitive price.

Now what if one node fails?

Exasol 4+1 Cluster: Node failurehttps://uhesse.files.wordpress.com/2018/07/failsafe3.png?w=1240&h=892 1240w, https://uhesse.files.wordpress.com/2018/07/failsafe3.png?w=150&h=108 150w, https://uhesse.files.wordpress.com/2018/07/failsafe3.png?w=300&h=216 300w, https://uhesse.files.wordpress.com/2018/07/failsafe3.png?w=768&h=552 768w, https://uhesse.files.wordpress.com/2018/07/failsafe3.png?w=1024&h=737 1024w" sizes="(max-width: 620px) 100vw, 620px" />

Exasol 4+1 Cluster: Node failure

ExaClusterOS – Exasols Clusterware – will detect the node failure within seconds and shutdown all remaining database instances in order to preserve a consistent state of the database. Then it restarts them again on the still available 3 nodes and also on the Reserve node that now becomes an Active node too. The database itself becomes available again with the node n15 now immediately working with segment B’.

The downtime of the system caused by the node failure is below 30 seconds typically. The restart of the database triggers a threshold called Restore Delay which defaults to 10 Minutes. If within that time the failed node becomes available again, we will just re-synchronize the segments (A’ and B in the example) which can be done fast. The instance on n15 will then work with the segment B as a Master-Segment until the database is manually restarted. Then n15 becomes a reserve node again and n12 is active with an instance running there.

If the failed node doesn’t come back within Restore Delay:

Exasol 4+1 Cluster: Restore Delay is overhttps://uhesse.files.wordpress.com/2018/07/failsafe41.png?w=1240&h=904 1240w, https://uhesse.files.wordpress.com/2018/07/failsafe41.png?w=150&h=109 150w, https://uhesse.files.wordpress.com/2018/07/failsafe41.png?w=300&h=219 300w, https://uhesse.files.wordpress.com/2018/07/failsafe41.png?w=768&h=559 768w, https://uhesse.files.wordpress.com/2018/07/failsafe41.png?w=1024&h=746 1024w" sizes="(max-width: 620px) 100vw, 620px" />

Exasol 4+1 Cluster: Restore Delay is over

We will then create new segments on node n15: A’ is copied from n11 and B is copied from n13. This activity is time-consuming and puts a significant load on the private network, which is why configuring a dedicated storage network may be beneficial to avoid a drop in performance during that period. A new reserve node should now be added to the cluster, replacing the crashed n12.