Deploying manager nodes
Manager nodes provide optimized stability and performance for Explore clusters and are required for clusters with six or more nodes. A manager node is dedicated to cluster management tasks and does not store records. This guide provides guidelines for adding three manager nodes to new and existing clusters with six or more data nodes.
|Important:||If your Explore cluster contains fewer than six nodes, you do not need to configure manager nodes.|
Manager nodes are virtual appliances with reduced resource specifications. Explore clusters typically require that all nodes match in both appliance type (virtual or physical) and size (resource specifications). However, manager nodes are the exception: a virtual manager node can be added to a cluster that has physical nodes and different resource specifications. Your data-only nodes should still match.
- Configure a new cluster with six or more data-only nodes and three manager-only nodes
- Convert an existing cluster that already includes one dedicated manager node to a cluster with three manager-only nodes
- Configure an existing cluster with six or more data-only nodes to add three manager-only nodes
Manager node specifications
Depending on your virtual implementation, download the package or instance associated with the smallest Explore node and modify the disk size to match the specifications listed below.
|Important:||For KVM deployments, you must delete the data disk that is preconfigured in the package and then add a new 12 GB disk before first boot.|
|Type||vCPUs||RAM||Boot Disk||Data Disk||Network||Size|
|AWS||4||8 GB||4 GB||25 GB||1 management vNIC||m5.xlarge|
|Azure||4||8 GB||4 GB||25 GB||1 management vNIC||Standard_F4s_v2|
|Hyper-V||4||8 GB||4 GB||12 GB||1 management vNIC||EXA-Hyper-V Package|
|KVM||4||8 GB||4 GB||12 GB||1 management vNIC||5100v Extra-Small Package|
|VMware||4||8 GB||4 GB||12 GB||1 management vNIC||5100v Manager Node|
Thank you for your feedback. Can we contact you to ask follow up questions?