Search

Top 60 Oracle Blogs

Recent comments

How to add a reserve node to an existing 2+0 #Exasol Cluster

After having installed a 2+0 Cluster in Hyper-V, now let’s expand that to a 2+1 Cluster.

Add the node as a VM first

Add another VM in Hyper-V with the same attributes as the existing two data nodes n11 and n12 and name it n13:

  • 2500 MB memory, not dynamically extending
  • Legacy network adapter, connected to edu-cluster-interconnect
  • Network adapter, connected to edu-public-network
  • Boot order with legacy network adapter first
  • Two hard disk of type VHDX with max. size 100 GB

Give it a static MAC for the Legacy Network Adapter 08:00:27:58:03:21 and a static MAC for normal Network Adapter 08:00:27:71:27:26 and make sure they do not conflict with other existing MAC addresses in your environment.

Copy an existing node in EXAoperation

Go to the nodes branch and click on the link under n11:

https://uhesse.files.wordpress.com/2019/09/addnode1.png?w=150&h=66 150w, https://uhesse.files.wordpress.com/2019/09/addnode1.png?w=300&h=133 300w, https://uhesse.files.wordpress.com/2019/09/addnode1.png?w=768&h=340 768w, https://uhesse.files.wordpress.com/2019/09/addnode1.png 930w" sizes="(max-width: 620px) 100vw, 620px" />

On the nodes detail page, click on Copy:

https://uhesse.files.wordpress.com/2019/09/addnode2.png?w=141&h=150 141w, https://uhesse.files.wordpress.com/2019/09/addnode2.png?w=282&h=300 282w, https://uhesse.files.wordpress.com/2019/09/addnode2.png 677w" sizes="(max-width: 620px) 100vw, 620px" />

Enter 13 as the node numbers and change the MAC addresses as listed above, then click on Copy Node:

https://uhesse.files.wordpress.com/2019/09/addnode3.png?w=150 150w, https://uhesse.files.wordpress.com/2019/09/addnode3.png?w=300 300w" sizes="(max-width: 387px) 100vw, 387px" />

Click on the n0013(13) link and check the disk configuration of the new node. It should look like this:

https://uhesse.files.wordpress.com/2019/09/addnode4.png?w=150&h=23 150w, https://uhesse.files.wordpress.com/2019/09/addnode4.png?w=300&h=46 300w, https://uhesse.files.wordpress.com/2019/09/addnode4.png?w=768&h=118 768w, https://uhesse.files.wordpress.com/2019/09/addnode4.png 967w" sizes="(max-width: 620px) 100vw, 620px" />

Don’t forget to set the install flag

On the nodes branch, tick the checkbox of node n13 and Execute the action Set install flag for it:

https://uhesse.files.wordpress.com/2019/09/addnode5.png?w=150&h=65 150w, https://uhesse.files.wordpress.com/2019/09/addnode5.png?w=300&h=131 300w, https://uhesse.files.wordpress.com/2019/09/addnode5.png?w=768&h=335 768w, https://uhesse.files.wordpress.com/2019/09/addnode5.png 907w" sizes="(max-width: 620px) 100vw, 620px" />

The state changes to Unknown To install. Now power on n13 in Hyper-V.

After a while the logservice should display the new node getting installed:

https://uhesse.files.wordpress.com/2019/09/addnode6.png?w=150&h=46 150w, https://uhesse.files.wordpress.com/2019/09/addnode6.png?w=300&h=92 300w, https://uhesse.files.wordpress.com/2019/09/addnode6.png?w=768&h=235 768w, https://uhesse.files.wordpress.com/2019/09/addnode6.png?w=1024&h=314 1024w, https://uhesse.files.wordpress.com/2019/09/addnode6.png 1135w" sizes="(max-width: 620px) 100vw, 620px" />

This can be time consuming (took me more than 30 Minutes on my notebook ) but in the end, it lists: Boot process finished after x seconds. When you refresh the nodes branch then, the state of the node n13 changes to Running To Install.

Now tick the checkbox of n13 again and Execute the action Set active flag:

https://uhesse.files.wordpress.com/2019/09/addnode7.png?w=150&h=82 150w, https://uhesse.files.wordpress.com/2019/09/addnode7.png?w=300&h=164 300w, https://uhesse.files.wordpress.com/2019/09/addnode7.png 715w" sizes="(max-width: 620px) 100vw, 620px" />

The state changes to Running Active for n13, same as for the other nodes. Notice that you can’t tell from this page if a node is an active node or a reserve node.

Add the disk capacity of the new node to the storage service

On the Storage branch, tick the checkbox for n13 and click on Add Unused Disks:

https://uhesse.files.wordpress.com/2019/09/addnode8.png?w=150&h=55 150w, https://uhesse.files.wordpress.com/2019/09/addnode8.png?w=300&h=109 300w, https://uhesse.files.wordpress.com/2019/09/addnode8.png?w=768&h=280 768w, https://uhesse.files.wordpress.com/2019/09/addnode8.png?w=1024&h=373 1024w, https://uhesse.files.wordpress.com/2019/09/addnode8.png 1035w" sizes="(max-width: 620px) 100vw, 620px" />

Add the new node as reserve node to the running database

On the database detail pages, click Edit and add n13 as a Reserve node, then click Apply:

https://uhesse.files.wordpress.com/2019/09/addnode9.png?w=73 73w, https://uhesse.files.wordpress.com/2019/09/addnode9.png?w=145 145w" sizes="(max-width: 503px) 100vw, 503px" />

The database should look like this now:

https://uhesse.files.wordpress.com/2019/09/addnode10.png?w=150&h=31 150w, https://uhesse.files.wordpress.com/2019/09/addnode10.png?w=300&h=62 300w, https://uhesse.files.wordpress.com/2019/09/addnode10.png?w=768&h=160 768w, https://uhesse.files.wordpress.com/2019/09/addnode10.png 898w" sizes="(max-width: 620px) 100vw, 620px" />

Notice that you didn’t need to shutdown the database to add a reserve node to it.

Now your cluster has been extended to a 2+1 Cluster. Next article will explain how you can enlarge the database and make this a 3+0 Cluster.

Stay tuned </p />
</p></div>

    	  	<div class=