Procedure for Using OpenSearch
Category |
Operation |
Details |
|
---|---|---|---|
Use |
Planning a cluster |
Before creating an OpenSearch cluster, develop a plan for it, such as whether to deploy the cluster across multiple AZs to improve availability; the node quantity and specifications; the cluster version and security mode; and index sharding, in order to ensure the desired performance and reliability. |
|
Creating a cluster |
Create an OpenSearch cluster based on the plan. |
||
Accessing a cluster |
There are many ways to access an OpenSearch cluster, such as Kibana, Cerebro, open-source APIs, Java, Python, and Go clients, as well as multiple network configurations over an intranet and the public network. You can select the most appropriate access method based on the programming language you prefer as well as your network environment. |
||
Importing data |
There are many ways to import data to an OpenSearch cluster, including Logstash, open-source Elasticsearch APIs, Cloud Data Migration (CDM), and Data Replication Service (DRS), with support for different data sources and formats, as well as real-time synchronization for relational databases. You can select the best way for yourself based on your use case and the characteristics of your data. |
||
Searching for data |
With CSS, you are advised to use DSL for data search in OpenSearch clusters. You may also use SQL. |
||
Enhancing the cluster's search capability |
On top of the open-source version, CSS's OpenSearch clusters offer a range of enhanced features, including vector search, storage-compute decoupling, flow control, large query isolation, aggregation enhancement, read/write splitting, switchover between hot and cold data storage classes, and index recycle bin. These features help you meet performance and cost optimization requirements for different use cases, while enhancing the service's cluster stability and search capability. |
||
O&M |
Backup and restoration |
Snapshots can be created to back up the data of an OpenSearch cluster, so that data can be quickly restored in the case of accidental data loss or in case historical data is needed, improving cluster data availability. |
Creating a Snapshot to Back Up the Data of an OpenSearch Cluster |
Scaling a cluster |
CSS provides flexible scale-out and scale-in options, using which you can add or reduce nodes (either randomly or with specified nodes), add node types, and increase or reduce node specifications. This allows you to dynamically adjust cluster resources to meet changing demand and optimize costs. |
||
Managing clusters |
CSS provides comprehensive cluster management functions. Users can view cluster information, authorize cluster access, change the cluster's security mode, manage tags, replace nodes, bind clusters with enterprise projects, switches AZs, and configure custom word dictionaries for OpenSearch clusters. They help users efficiently manage OpenSearch clusters and ensure cluster security, high availability, and optimized performance. |
||
Managing cluster index policies |
The Index State Management (ISM) plugin of OpenSearch can be used to create and manage index lifecycle policies. These policies help automate index rollovers and deletions, helping optimize cluster performance and cut storage costs. |
||
Monitoring and log management |
CSS provides comprehensive monitoring and log management functions. Users can configure and check monitoring metrics for clusters and nodes, configure alarm rules, and back up and view logs. Intelligent O&M tools help users efficiently monitor, analyze, and maintain OpenSearch clusters and ensure cluster stability and performance. |
Monitoring Metrics for OpenSearch Clusters in Cloud Eye Using Cloud Eye to Monitor OpenSearch Clusters Setting Alarm Alerting via SMN for an OpenSearch Cluster |
|
Audit logs |
Cloud Trace Service (CTS) can be used to log mission-critical operations related to OpenSearch clusters. Used for auditing and accountability purposes, these log records are retained for seven days on the management console. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot