The page has been translated by Gen AI.

How-to guides

The user can enter the necessary information of the Search Engine through the Samsung Cloud Platform Console and create the service by selecting detailed options.

Creating Search Engine

You can create and use the Search Engine service in the Samsung Cloud Platform Console.

Notice

Please configure the Subnet type of VPC to General before creating the service.

  • If the Subnet type is Local, the creation of the corresponding Database service is not possible.

To create a Search Engine, follow the next procedure.

Notice
The following describes the case when you choose the Elasticsearch Enterprise image.
  1. All Services > Database > Search Engine menu, click. It moves to the Service Home page of Search Engine.

  2. On the Service Home page, click the Create Search Engine button. It moves to the Create Search Engine page.

  3. Search Engine Creation page where you enter the information needed to create a service and select detailed options.

    • Image and Version Selection area, please select the necessary information.

      Classification
      Necessity
      Detailed Description
      ImageRequiredSelect the type of image provided
      • Elasticsearch Enterprise, OpenSearch
      Image VersionRequiredSelect the version of the selected image
      • Provide a list of versions of the server image provided
      Fig. Search Engine image and version selection items

    • Enter Service Information area, please enter or select the necessary information.

      Classification
      Necessity
      Detailed Description
      Server Name PrefixRequiredThe name of the server where Elasticsearch will be installed
      • Starts with a lowercase letter, using lowercase letters, numbers, and special characters (-) to input 3 ~ 13 characters
      • A postfix such as 001, 002 is attached based on the server name to create the actual server name
      Cluster NameRequiredName of the cluster that the servers are configured in
      • Enter in English, 3-20 characters
      • The cluster is a unit that bundles multiple servers
      MasterNode separate installation > useessentialWhether to install the Master node separately
      • Use is selected, the Master node is installed separately.
      • If the Master node is not installed separately, the data node also performs the master role.
      MasterNode separate installation > MasterNode countrequiredNumber of Master nodes
      • The master node is installed with a fixed 3 units for failover recovery.
      MasterNode separate installation > Server typeRequiredMaster node server type
      • Standard: Standard specification commonly used
      • High Capacity: High-capacity server with 24vCore or more
      MasterNode separate installation > Planned ComputeselectionCurrent status of resources with Planned Compute set
      • In use: Number of resources in use among those with Planned Compute set
      • Settings: Number of resources with Planned Compute set
      • Coverage preview: Amount applied by resource-based Planned Compute
      • Apply for Planned Compute service: Move to the Planned Compute service application page
      MasterNode separate installation > Block StoragerequiredMaster node block storage type
      • Basic OS: area where the engine is installed
      • DATA: data file storage area
        • After selecting the storage type, enter the capacity. (For more information on each block storage type, see Creating Block Storage)
          • SSD: high-performance general volume
          • HDD: general volume
          • SSD_KMS/HDD_KMS: additional encrypted volume using KMS (Key Management System) encryption key
        • Capacity can be entered in multiples of 8 in the range of 16 to 5,120
      • Add Disk: data storage area
        • After selecting Use, enter the Capacity of the storage
        • To add storage, click the + button, and to delete, click the x button. Up to 9 can be added.
        • Capacity can be entered in multiples of 8 in the range of 16 to 5,120, and up to 9 can be created
      Number of NodesRequiredNumber of Data Nodes
      • In cases where the Master node is installed separately, 2 or more nodes are required, and in other cases, 1 or more nodes must be selected.
      Service Type > Server TypeRequiredData Node Server Type
      • Standard: generally used standard specification
      • High Capacity: high-capacity server with 24vCore or more
      Service Type > Planned ComputeSelectionCurrent status of resources with Planned Compute set
      • In Use: Number of resources with Planned Compute set that are in use
      • Settings: Number of resources with Planned Compute set
      • Coverage Preview: Amount applied by Planned Compute for each resource
      Service Type > Block StorageRequiredType of Block Storage to be used for data node
      • Basic OS: Area where the engine is installed
      • DATA: Data file storage area
        • Please select the storage type and enter the capacity. (For more information on each Block Storage type, refer to Creating Block Storage)
          • SSD: High-performance general volume
          • HDD: General volume
          • SSD_KMS/HDD_KMS: Additional encrypted volume using KMS (Key Management System) encryption key
        • Capacity can be entered in multiples of 8 within the range of 16 to 5,120
      • Disk Add: Additional storage area for data, backup
        • Select Use and enter the Purpose and Capacity of the storage
        • To add storage, click the + button, and to delete, click the x button. Up to 9 can be added.
        • Capacity can be entered in multiples of 8 within the range of 16 to 5,120, and up to 9 can be created
      Kibana > Server TypeRequiredThe type of server where Kibana will be installed
      • Standard: Standard specification commonly used
      Kibana > Planned ComputeSelectionCurrent status of resources with Planned Compute set
      • In use: Number of resources with Planned Compute set that are in use
      • Settings: Number of resources with Planned Compute set
      • Coverage preview: Amount applied by resource-based Planned Compute
      Kibana > Block StoragerequiredThe type of Block Storage to be used on the server where Kibana will be installed
      • Basic OS: The area where the engine is installed
      Network > Common SettingsRequiredNetwork settings for servers created by the service
      • Select if you want to apply the same settings to all servers being installed
      • Select pre-created VPC and Subnet
      • IP: Only automatic creation is possible
      • Public NAT settings are only possible in server-specific settings.
      Network > Server SettingsRequiredNetwork settings for installing servers created by the service
      • Select to apply different settings for each server being installed
      • Select pre-created VPC and Subnet
      • IP: Enter the IP for each server
      • The Public NAT function is available only when the VPC is connected to the Internet Gateway, and if Use is checked, you can select from the reserved IP in the VPC product’s Public IP. For more information, see Creating Public IP
      IP Access ControlSelectSet service access policy
      • Set access policy for IPs entered on the page, so you don’t need to set Security Group policy separately.
      • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32), and click the Add button
      • To delete the entered IP, click the x button next to the entered IP
      Maintenance periodSelectSearch Engine maintenance period
      • Use Selecting the day of the week, start time, and duration
      • It is recommended to set the maintenance period for stable management of the service. Patch work is performed at the set time and service interruption occurs
      • If set to unused, problems that occur due to non-application of patches are not the responsibility of our company.
      Table. Search Engine service information input items

    • Database Configuration Required Information Input area, please enter or select the required information.

      Classification
      Necessity
      Detailed Description
      Backup > UseSelectionWhether to use node backup
      • If node backup is selected, select the storage period and backup start time
      Backup > Retention PeriodSelectBackup Retention Period
      • Please select the backup retention period. The file retention period can be set from 7 to 35 days
      • Backup files may incur additional charges depending on capacity.
      Backup > Backup start timeSelectBackup start time
      • Select the backup start time
      • The minutes when the backup is performed are set randomly, and the backup end time cannot be set
      Cluster Port numberRequiredElasticsearch connection port number
      • 1,024 ~ 65,535 can be entered as one of them, and Elasticsearch internal port 9300 and Kibana port 5301 are not available
      Elastic usernamerequiredElasticsearch username
      • Enter within 2-20 characters using lowercase English letters
      • The following usernames cannot be used.
        • apm_system, beats_system, elastic, kibana, kibana_system, logstash_system, remote_monitoring_user, scp_kibana_system, scp_manager, maxigent_cl
      Elastic passwordrequiredElasticsearch connection password
      • Enter 8-30 characters, including English, numbers, and special characters (excluding " </code>)
      Elastic password confirmationrequiredConfirm Elasticsearch connection password
      • Re-enter the Elasticsearch connection password identically
      License KeyrequiredElasticsearch License Key
      • Enter the entire contents of the issued license file (.json)
      • If the entered license key is not valid, service creation may not be possible.
      • OpenSearch does not require a License Key.
      Time ZoneSelectionStandard Time Zone where the service will be used
      Fig. Search Engine Database Configuration Required Information Input Items

    • Enter Additional Information Enter or select the required information in the area.

      Classification
      Necessity
      Detailed Description
      TagSelectAdd Tag
      • Add Tag button to create and add a tag or add an existing tag
      • Up to 50 tags can be added
      • Newly added tags will be applied after service creation is complete
      Fig. Search Engine service additional information input items

  4. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.

    • Once creation is complete, check the created resource on the Resource List page.

Search Engine detailed information check

The Search Engine service can check and modify the entire resource list and detailed information. The Search Engine details page consists of detailed information, tags, and work history tabs.

To check the detailed information of the Search Engine service, follow the next procedure.

  1. All services > Data Analytics > Search Engine menu, click. It moves to the Service Home page of Search Engine.
  2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
  3. Search Engine list page, click on the resource to check the detailed information. Move to the Search Engine details page.
    • Search Engine Details The top of the page displays status information and additional features.
ClassificationDetailed Description
Cluster StatusCluster Status
  • Creating: The cluster is being created
  • Editing: The cluster is being changed to an operational state
  • Error: The cluster has failed while performing an operation
    • If this occurs continuously, please contact the administrator
  • Failed: The cluster has failed during the creation process
  • Restarting: The cluster is being restarted
  • Running: The cluster is operating normally
  • Starting: The cluster is being started
  • Stopped: The cluster has been stopped
  • Stopping: The cluster is being stopped
  • Synchronizing: The cluster is being synchronized
  • Terminating: The cluster is being deleted
  • Unknown: The cluster status is unknown
    • If this occurs continuously, please contact the administrator
  • Upgrading: The cluster is being changed to an upgrade state
Cluster ControlButtons that can change the cluster status
  • Start: Starts a stopped cluster.
  • Stop: Stops a running cluster.
  • Restart: Restarts a running cluster
Additional features moreCluster related management buttons
  • Service status synchronization: It is possible to synchronize with Console by inquiring the current server status
  • Backup history: If backup is set, you can check the normal execution of backup and history
  • Cluster recovery: Recovers the cluster based on a specific point in time.
  • Add Node: Adds data nodes.
Service CancellationButton to cancel the service
Fig. Search Engine status information and additional functions

Detailed Information

On the Search Engine List page, you can check the detailed information of the selected resource and modify the information if necessary.

ClassificationDetailed Description
Server InformationServer information configured in the corresponding cluster
  • Category: Server type (Master&Data, Master, Data, Kibana)
  • Server Name: Server name
  • IP:Port: Server IP and port
  • NAT IP: NAT IP
  • Status: Server status
ServiceService Name
Resource TypeService Name
SRNUnique resource ID in Samsung Cloud Platform
  • Means cluster SRN
Resource NameResource Name
  • Means cluster name
Resource IDUnique resource ID in the service
CreatorService creator user
Creation TimeTime when the service was created
ModifierService information modified user
Modified TimeTime when service information was modified
Image/VersionInstalled service image and version information
Cluster NameServer cluster name composed of servers
Planned ComputePlanned Compute status of set resources
Maintenance PeriodMaintenance Period Status
  • If maintenance period setting is required, click the Edit button to set
BackupBackup setting status
  • If backup setting is required, click the Modify button to set
Time ZoneStandard time zone where the service will be used
LicenseElasticsearch license information
  • License update is possible in Kibana > Stack Management > License management
  • If the license expires, the service cannot be used
Elastic usernameElasticsearch user name
Kibana connection informationKibana connection information
NetworkInstalled network information(VPC, Subnet)
IP access controlService access policy setting
  • If IP addition or deletion is required, click the Modify button to set
MasterMaster node’s server type, default OS, additional Disk information
  • If server type modification is required, click the Modify button next to the server type to set
    • Modifying the server type requires a server restart
  • If storage expansion is required, click the Modify button next to the storage capacity to expand
  • If additional storage is required, click the Add Disk button next to the additional Disk to add
DataBroker node’s server type, default OS, additional Disk information
  • In case of modifying the server type, click the Modify button next to the server type to set
    • Modifying the server type requires server restart
  • If additional storage is needed, click the Add Disk button next to the additional Disk to add
KibanaKibana node server type, basic OS information
  • In case server type modification is needed, click the Modify button next to the server type to set
    • Modifying the server type requires server restart
Table. Search Engine detailed information items

Tag

On the Search Engine list page, you can check the tag information of the selected resource, and add, change, or delete it.

ClassificationDetailed Description
Tag ListTag List
  • Check Key, Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, search and select from the existing list of created Key and Value
Fig. Search Engine tags tab items

Work History

You can check the operation history of the resource selected on the Search Engine list page.

ClassificationDetailed Description
Work History ListResource Change History
  • Check work details, work time, resource type, resource ID, resource name, event topic, work result, and worker information
Fig. Search Engine job history tab detailed information items

Search Engine Resource Management

If you need to change the existing setting options of the generated Search Engine resource or manage Parameters, or configure additional Nodes, you can perform the task on the Search Engine details page.

Operating Control

If there are changes to the Search Engine resources in operation, you can start, stop, and restart them.

To control the operation of the Search Engine, follow the next procedure.

  1. Click on the menu of all services > Data Analytics > Search Engine. It moves to the Service Home page of Search Engine.
  2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
  3. Search Engine list page, click the resource to control the operation. Move to the Search Engine details page.
  4. Check the Search Engine status and complete the change through the control button below.
    • Start: The Search Engine service is installed on the server and the Search Engine service is running.
    • Stop: The Search Engine service installed on the server and the Search Engine service will be stopped.
    • Restart: Only the Search Engine service will be restarted.

Synchronizing Service Status

You can query the current server status and synchronize it to the Console.

To synchronize the service status of the Search Engine, follow the next procedure.

  1. Click All Services > Data Analytics > Search Engine menu. It moves to the Service Home page of Search Engine.
  2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
  3. Search Engine list page, click on the resource to check the service status. Move to the Search Engine details page.
  4. Service Status Synchronization button should be clicked. It takes some time to retrieve, and during retrieval, the cluster changes to Synchronizing status.
  5. When the query is complete, the status in the server information item is updated, and the cluster changes to Running status.

Changing Server Type

You can change the configured server type.

To change the server type, follow these steps.

Caution
  • If the server type is configured as Standard, it cannot be changed to High Capacity. If you want to change to High Capacity, please create a new service.
  • Modifying the server type requires a server restart. Please check separately for SW license modifications due to specification changes, as well as SW settings and reflections.
  1. All services > Data Analytics > Search Engine menu is clicked. It moves to the Service Home page of Search Engine.
  2. Service Home page, click the Search Engine menu. Move to the Search Engine list page.
  3. Search Engine list page, click the resource to change the server type. Move to the Search Engine details page.
  4. Click the Edit button of the Server Type you want to change at the bottom of the detailed information. The Edit Server Type popup window opens.
  5. In the Server Type Modification popup window, select the server type and click the Confirm button.

Expanding Storage

The storage added to the data area can be expanded up to a maximum of 5TB based on the initially allocated capacity. Storage can be expanded without stopping the Search Engine, and if configured in a cluster, all nodes are expanded simultaneously.

Notice
  • If encryption is set for the existing Block Storage, encryption will also be applied to the additional Disk. The disk size modification is only possible if it is 16GB or more larger than the current disk size.

To increase the storage capacity, follow the procedure below.

  1. All services > Data Analytics > Search Engine menu is clicked. It moves to the Service Home page of Search Engine.
  2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
  3. Search Engine list page, click the resource to change the server type. It moves to the Search Engine details page.
  4. Click the Modify button of the additional Disk you want to add at the bottom of the detailed information. The Disk Modification popup window opens.
  5. In the Disk Modification popup window, enter the expansion capacity and click the Confirm button.

Adding Storage

If you need more than 5TB of data storage space, you can add storage.

Notice
  • If encryption is set for the existing Block Storage, encryption will also be applied to the additional Disk.

To add storage capacity, follow these steps.

  1. All services > Data Analytics > Search Engine menu is clicked. It moves to the Service Home page of Search Engine.
  2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
  3. Search Engine list page, click the resource to add storage. Move to the Search Engine details page.
  4. Click the Add Disk button at the bottom of the detailed information. The Add Disk popup window opens.
  5. In the Add Disk popup window, enter the purpose and capacity, then click the OK button.

Search Engine Backup

Through the backup settings function, users can set the data retention period and start cycle, and perform backup history inquiry and deletion through the backup history function.

Setting up backup

While creating the Search Engine, the procedure for setting up the backup is to refer to the Search Engine creation guide, and to modify the backup settings of the created resource, follow the following procedure.

Caution
  • If backup is set, backup will be performed at the specified time after the set time, and additional fees will be incurred depending on the backup capacity.
  • If the backup setting is changed to unset, the backup operation will be stopped immediately, and the saved backup data will be deleted and can no longer be used.
  1. All Services > Data Analytics > Search Engine menu is clicked. It moves to the Service Home page of Search Engine.
  2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
  3. Search Engine list page, click the resource to set the backup. Move to the Search Engine details page.
  4. Click the Edit button of the backup item. The Backup Edit popup window opens.
  5. If you set up a backup, click Use in the Backup Modification popup window, select the storage period, backup start time, and Archive backup cycle, and then click the Confirm button.
    • If you want to stop the backup settings, uncheck Use in the Backup Modification popup window and click the OK button.

Check Backup History

To view the backup history, follow these steps.

  1. All Services > Data Analytics > Search Engine menu is clicked. It moves to the Service Home page of Search Engine.
  2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
  3. Search Engine list page, click the resource to check the backup history. Move to the Search Engine details page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.

Deleting backup files

To delete the backup history, follow these steps.

Caution
Please confirm that the data is unnecessary before deleting it, as deleted backup files cannot be restored.
  1. Click on the menu for all services > Data Analytics > Search Engine. It moves to the Service Home page of the Search Engine.
  2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
  3. Search Engine list page, click the resource to check the backup history. Move to the Search Engine details page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. In the backup history popup window, check the file you want to delete and click the Delete button.

Search Engine recovery

In the event of a failure or data loss that requires restoration from a backup file, cluster recovery allows recovery based on a specific point in time.

Caution
To perform recovery, a data type of Disk capacity and at least the same capacity are required. If the disk capacity is insufficient, recovery may fail.

Notice
Cluster recovery is restored with the same configuration as the original. For example, if it is configured with 3 Master nodes and 2 Data nodes, it will be restored with the same configuration.

To restore the Search Engine, follow the following procedure.

  1. All Servives > Data Analytics > Search Engine menu should be clicked. It moves to the Service Home page of Search Engine.
  2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
  3. Search Engine Resource Click on the resource you want to restore from the list page. It moves to the Search Engine Details page.
  4. Click the Cluster Recovery button. It moves to the Cluster Recovery page.
  5. Enter the corresponding information in the Cluster Recovery Configuration area, and then click the Complete button.
Classification
Necessity
Detailed Description
Recovery PointRequiredSet the point in time that the user wants to recover
  • Selected from the list of backup file timestamps displayed in the list
Server Name PrefixRequiredRecovery Server Name
  • Start with lowercase English letters, using lowercase letters, numbers, and special characters(-) to input 3-16 characters
  • A postfix such as 001, 002 is attached based on the server name to create the actual server name
Cluster NameRequiredRecovery Server Cluster Name
  • Enter in English, 3-20 characters
  • The cluster is a unit that bundles multiple servers
Number of NodesRequiredNumber of Data Nodes
  • It will be set the same as the number of nodes set in the original cluster.
Service Type > Server TypeRequiredData Node Server Type
  • It will be set to the same number of nodes as the original cluster.
Service Type > Planned ComputeSelectionCurrent status of resources with Planned Compute set
  • In Use: Number of resources with Planned Compute set that are currently in use
  • Settings: Number of resources with Planned Compute set
  • Coverage Preview: Amount applied by Planned Compute for each resource
Service Type > Block StorageRequiredBlock Storage to be used for data node
  • Base OS: Area where the engine is installed
  • DATA: Data file storage area
    • The storage type set in the original cluster is applied in the same way
    • Capacity can be entered in multiples of 8 in the range of 16 to 5,120
  • Disk Add: Additional storage area for data, backup
    • After selecting Use, enter the purpose and capacity of the storage
    • To add storage, click the + button, and to delete, click the x button
    • Capacity can be entered in multiples of 8 in the range of 16 to 5,120, and up to 9 can be created
MasterNode separate installation > useessentialWhether to install Master node separately
  • Applied equally according to the installation of the original cluster
MasterNode separate installation > Number of MasterNodesrequiredNumber of Master nodes
MasterNode separate installation > Server typeRequiredMaster node server type
  • It will be set to the same number of nodes as the original cluster.
MasterNode separate installation > Planned ComputeselectionPlanned Compute setting resource status
  • In use: The number of resources in use among Planned Compute settings
  • Setting: The number of resources with Planned Compute settings
  • Coverage preview: The amount applied by Planned Compute for each resource
  • Planned Compute service application: Move to the Planned Compute service application page
MasterNode separate installation > Block StoragerequiredBlock Storage to be used for Master Node
  • Basic OS: area where the engine is installed
  • DATA: area for storing data files
    • applied equally to the storage type set in the original cluster
    • capacity can be entered in multiples of 8 in the range of 16 to 5,120
  • Disk addition: additional data storage area
    • select use and enter the storage capacity
    • click the + button to add storage, and click the x button to delete
    • capacity can be entered in multiples of 8 in the range of 16 to 5,120, and up to 9 can be created
Kibana > Server TypeRequiredKibana node server type
  • It will be set to the same number of nodes as the original cluster.
Kibana > Planned ComputeSelectionCurrent status of resources with Planned Compute set
  • In use: Number of resources with Planned Compute set that are in use
  • Settings: Number of resources with Planned Compute set
  • Coverage Preview: Amount applied by Planned Compute for each resource
Kibana > Block StorageRequiredBlock Storage to be used for Kibana nodes
  • Base OS: Area where the engine is installed
Cluster Port numberRequiredElasticsearch connection port number
  • It is set to the same port number as the original cluster.
Licnese KeyEssentialElasticsearch License Key
  • Enter the entire contents of the issued license file (.json)
  • If the entered license key is invalid, service creation may not be possible.
  • OpenSearch does not require a License Key.
IP Access ControlSelectSet service access policy
  • Set access policy for the IP entered on the page, so you don’t need to set Security Group policy separately.
  • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32), and click the Add button
  • To delete the entered IP, click the x button next to the entered IP
Maintenance periodSelectMaintenance period
  • Use is selected, set the day of the week, start time, and duration
  • It is recommended to set the maintenance period for stable management of the service. Patch work is performed at the set time and service interruption occurs
  • If it is set to not in use, problems that occur due to non-application of patches are not the responsibility of our company.
Fig. Search Engine Recovery Configuration Items

Add Node

If Search Engine cluster expansion is needed, you can add nodes with the same specifications as the data node in use.

Notice
  • You can use up to 10 nodes within the cluster. Please note that additional nodes created will be charged extra.
  • The cluster performance may be degraded while adding nodes.

To add a node, follow these steps.

  1. All Services > Data Analytics > Search Engine menu should be clicked. It moves to the Service Home page of Search Engine.
  2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
  3. Search Engines Resource menu should be clicked. It moves to the Search Engine Detail page.
  4. Click the Add Broker Node button. It moves to the Add Broker Node page.
  5. Required Information Input area, enter the corresponding information, and then click the Complete button.
Division
Mandatory
Detailed Description
Server Name PrefixRequiredData Node Server Name
  • It is set to the server name set in the original cluster.
Cluster NameRequiredCluster Name
  • It is set as the cluster name set in the original cluster.
Additional Node countRequiredNumber of additional Nodes to add
  • Up to 10 nodes can be used in a single cluster
Service Type > Server TypeRequiredData Node Server Type
  • It will be set the same as the server type set in the original cluster.
Service Type > Planned ComputeSelectionCurrent status of resources with Planned Compute set
  • In use: Number of resources with Planned Compute set that are in use
  • Settings: Number of resources with Planned Compute set
  • Coverage Preview: Amount applied by Planned Compute for each resource
  • Apply for Planned Compute Service: Move to the Planned Compute service application page
Service Type > Block StorageRequiredBlock Storage settings to be used for data nodes
  • The storage type and capacity set in the original cluster are applied identically
NetworkRequiredThe network where servers are installed
  • Applied the same as the network set in the original cluster
Fig. Search Engine Node Additional Items

Search Engine cancellation

You can cancel the unused Search Engine to reduce operating costs. However, if you cancel the service, the operating service may be stopped immediately, so you should consider the impact of stopping the service sufficiently before proceeding with the cancellation work.

To cancel the Search Engine, follow the next procedure.

  1. All services > Data Analytics > Search Engine menu is clicked. It moves to the Service Home page of Search Engine.
  2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
  3. Search Engine list page, select the resource to be canceled and click the Service Cancellation button.
  4. Once the cancellation is complete, please check if the resource has been cancelled on the Search Engine list page.
Monitoring Metrics
Release Note