Infrastructure Management

While you can view general information about your ElasticSearch cluster on the Account Info tab, use the Infrastructure page of the Qrvey Admin Center to monitor and manage its configuration.

From the Admin Center, you can open the page by selecting the Infrastructure icon in the left navigation panel.

Storage Distribution and Configuration Dependencies

Storage usage distribution depends on the configuration of its indices when the dataset was loaded. If an index uses more than one shard, the data is distributed equally among the nodes. Storage allocation can be configured specifically for each node, depending on the volume attachment. As a cloud operations engineer, check your specific configuration.

Change the OpenSearch Server

The OpenSearch Server Details section displays the server name, status, and OpenSearch server instance type. If you use an AWS OpenSearch service, you can change the OpenSearch server on this page.

1. From the OpenSearch Server Type dropdown, select an available instance type. You can also search by keywords.

   Tip: For AWS-managed OpenSearch, use this field to change the instance size. This applies only to AWS-managed services.

2. Select Apply Changes.

   Changes to the server type implements all configurations for that server.

Perform Manual Adjustments

The Manual Adjustments section displays your total available storage and the percentage of storage used. You can modify the number of Elasticsearch servers (nodes) as well as the storage capacity.

Before You Begin

Changing your Elasticsearch configuration can affect both the data and the cost of your AWS services. Before making any changes, review the following AWS documentation about Elasticsearch sizing, instance types, and limits:

• Amazon Elasticsearch Service
• AWS Pricing Calculator
• Amazon Elasticsearch Service Developer Guide
• Sizing Amazon ES Domains
• Choosing Instance Types and Testing
• Amazon Elasticsearch Service Limits

Change the Number of Servers

For an Elasticsearch cluster administered by Qrvey, the process depends on the configuration. Before changing the number of servers (Elasticsearch nodes), take time to understand how the change affects your Elasticsearch configuration.

1. To change the number of ElasticSearch nodes, enter a value in the # of Servers field.
2. Select Apply Changes.

Entering incorrect values can result in errors, depending on the type of AWS validation you have in place.

Change Storage Capacity

Before changing the storage capacity for your nodes, take time to understand how the change affects your Elasticsearch configuration.

For AWS-managed OpenSearch, increases to actual storage must be performed manually. For more information, see Entity Management

1. Review the current storage capacity:

   • Total Storage: Global storage (GB) for all nodes in the Elasticsearch cluster. Total storage should equal storage per node multiplied by the number of nodes.
   • Used Storage: The storage value (GB) is also used in the Health Dashboard.

2. Enter a value in the Storage (GB) field.

3. Select Apply Changes.

Automatic Adjustments

In the Automatic Adjustments section, you can schedule a daily check for the amount of available storage. You can also enable automated increases to your storage if it falls below a defined threshold, adding a server of the same instance type and storage capacity.

Automatically Adjust Storage Capacity

Use the Automatic Adjustments section to schedule automated changes the servers (nodes) in the ElasticSearch cluster.

1. To enable automatic updates, select Perform Automatic Storage Increments.

2. Under Scheduling Daily at, select the time (GMT) when the system checks the amount of available storage.

   Note: Select a different time from any snapshots and other scheduled processes, such as Dataset Data Syncing.

3. Specify the threshold that determines when to add capacity. In the Add one server of the same type and storage if free storage is less or equal than (%) field, enter the desired percentage (%) of free space remaining. This value can be between 10% and 30%. When the free storage is less than or equal to this percentage, the process adds capacity.

4. Specify the Max. number of servers allowed to be automatically added in the field provided. Depending on the instance type, AWS has defined the limits for the quantity of instances and storage capacity for each one. For more information, see Amazon Elasticsearch Service Limits.

5. Select one or more email Notifications.

6. Select Apply Changes.

To determine whether any servers have been automatically added, record the value under Number of servers automatically added. To determine how many more servers are available, compare this value to the Max. number of servers allowed to be automatically added value.

When a manual or automatic adjustment process is running, the values, calculations, and indicators displayed in the Infrastructure page can change. In some cases, the number of nodes (servers) in the Elasticsearch cluster can temporarily increase while the update occurs. For more information, see the following:

• Configuration Changes
• Charges for Configuration Changes

Email Notifications

In the Email Notifications section, you can enable email notifications for events related to changes in Elasticsearch settings. To provide an email target, enter a valid email address or alias in the field provided. You are limited to one entry.

• The Manual Adjustments configuration settings have been modified. Sends an email each time the Elasticsearch cluster settings are modified and changes have been applied. This notification does not indicate that the adjustment process has already begun or that the Elasticsearch cluster has been successfully modified.
• The Automatic Adjustments configuration settings have been modified. Sends an email each time an automatic change is modified and applied. This notification does not indicate that the adjustment process has already begun or that the Elasticsearch cluster has been successfully modified.
• A Manual Adjustment or Automatic Adjustment process has started. Sends an email each time a manual or automatic adjustment process starts. This notification does not indicate that the Elasticsearch cluster has been successfully modified.
• A Manual Adjustment or Automatic Adjustment completed or failed. Sends an email each time a manual or automatic adjustment process has been completed, indicating if it succeeded or failed.
• Free storage threshold has been reached and automatic adjustments are not enabled or not allowed. Sends an email each time the Automatic Adjustments process determines that the free storage threshold has been reached, but Automatic Adjustments are not enabled or the number of servers allowed has reached the maximum number specified.

Note: The act of changing a notification setting changes the notification workflow. It does not trigger any additional notifications.