Cluster

The Cluster tab in the SearchBlox Admin page allows you to configure and manage the cluster setup for your SearchBlox deployment. Below is a detailed guide on how to configure the cluster setup, including single-node and multi-node configurations.

Cluster Configuration Options

1. Single Node Setup:

Default Configuration: By default, SearchBlox is set up as a single node, which represents a standalone instance.
Use Case: Suitable for small-scale deployments or testing environments where high availability and scalability are not critical.
Configuration:

1. No additional nodes are required.
2. All operations (indexing, searching, etc.) are handled by a single server.

2. Multi-Node Setup:

Use Case: Ideal for large-scale deployments requiring high availability, load balancing, and fault tolerance.
Configuration:
You need to specify the details of multiple nodes (servers) that will form the cluster. Each node in the cluster works together to distribute the workload, ensuring better performance and reliability.

Steps to Configure:

1. Access the Cluster Tab:
   Log in to the SearchBlox Admin interface.
   Navigate to Menu -> Admin -> Cluster.
2. Select Cluster Type:
   Choose between Single Node or Multi-Node setup.
   For Single Node, no further configuration is needed (default).
   For Multi-Node, proceed to the next steps.
3. Add Nodes:
   Specify the IP addresses or hostnames of the nodes that will be part of the cluster.
   Ensure all nodes are reachable and properly configured (e.g., same SearchBlox version, network connectivity).
4. Save and Apply Configuration:
   Save the cluster configuration.
   Restart the SearchBlox instances for the changes to take effect.
5. Verify Cluster Status:
   After configuration, check the cluster status to ensure all nodes are connected and functioning correctly.

For detailed instructions, refer to the SearchBlox Cluster Setup documentation. If you encounter any issues during configuration, contact SearchBlox support for assistance.

Switching from Multinode cluster to Single Node

Switching from a Multi-Node cluster setup to a Single Node setup is not recommended and can lead to significant issues, including the search functionality stopping altogether.

Why Changing to Single Node is Not Recommended

• Data Distribution:
  In a multi-node setup, data is distributed across multiple nodes. Switching to a single node may result in data loss or corruption if the data is not properly consolidated.
• Search Functionality:
  The search functionality relies on the distributed index across multiple nodes. Removing nodes without proper reconfiguration can cause the search to stop working.
• Configuration Complexity:
  Multi-node setups involve complex configurations (e.g., replication, load balancing). Reverting to a single node requires careful handling to avoid breaking the system.
• Performance Impact:
  A single node may not handle the load previously distributed across multiple nodes, leading to performance degradation or system crashes.

What to Do Instead

If you need to change your cluster setup or are facing issues with your multi-node configuration, follow these steps:

• Contact SearchBlox Support:
  Reach out to the SearchBlox support team for guidance. They can provide step-by-step instructions tailored to your specific setup. Explain your requirements and the issues you’re facing to get the best possible solution.
• Backup Your Data:
  Before making any changes, ensure you have a complete backup of your data and configurations. This will help you restore the system if something goes wrong.
• Evaluate Your Needs:
  If you’re considering switching to a single node due to reduced workload or other reasons, discuss this with the support team. They can help you determine if it’s feasible and guide you through the process safely.
• Reconfigure Gradually:
  If switching to a single node is absolutely necessary, the support team can help you reconfigure the system gradually to minimize risks.

🚧

Important Information:

SearchBlox License: A valid SearchBlox license must be applied to all servers in the cluster.