Billing methods
OpenSearch Retrieval Engine Edition supports the following billing methods.
Billing methods | Description |
Pay-as-you-go | Also known as postpaid billing. An order is generated each hour, and charges are deducted from your Alibaba Cloud account based on the instance specifications at the time the order is generated. This method is suitable for short-term requirements, such as initial testing. Release the instance when you finish using it to reduce costs. |
Subscription | Also known as prepaid billing. You pay when you create the instance. Subscription offers lower prices than pay-as-you-go. |
Instance pricing components
OpenSearch Retrieval Engine Edition is billed per instance for six components: instance rental, query nodes, data nodes, storage capacity per data node, index storage, and data update resources.
Total fee = Instance rental fee + Query node fee + Data node fee + Storage capacity fee per data node + Index storage fee + Data update resource fee.
Instance rental, query node, and data node fees
Pay-as-you-go
Instance rental fee = Unit price * Number of hours
Query node fee = Unit price * Number of hours * Number of query nodes
Data node fee = Unit price * Number of hours * Number of data nodes
Region | Billable item | Specification family | Available specifications | Unit price | Unit |
China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), and China (Zhangjiakou) | Instance rental | - | - | 0.38 | CNY/hour/unit |
Query node | Local SSD | 2 vCPUs, 8 GB | 0.58 | CNY/hour/unit | |
4 vCPUs, 16 GB | 1.16 | CNY/hour/unit | |||
8 vCPUs, 16 GB (China (Shanghai) only) | 2.03 | CNY/hour/unit | |||
8 vCPUs, 32 GB | 2.31 | CNY/hour/unit | |||
Cloud disk | 2 vCPUs, 8 GB | 0.38 | CNY/hour/unit | ||
4 vCPUs, 16 GB | 0.75 | CNY/hour/unit | |||
8 vCPUs, 32 GB | 1.51 | CNY/hour/unit | |||
Data node | Local SSD | 2 vCPUs, 16 GB | 0.71 | CNY/hour/unit | |
4 vCPUs, 32 GB | 1.42 | CNY/hour/unit | |||
6 vCPUs, 48 GB | 2.13 | CNY/hour/unit | |||
8 vCPUs, 16 GB (China (Shanghai) only) | 2.03 | CNY/hour/unit | |||
8 vCPUs, 64 GB | 2.84 | CNY/hour/unit | |||
10 vCPUs, 80 GB | 3.55 | CNY/hour/unit | |||
12 vCPUs, 96 GB | 4.26 | CNY/hour/unit | |||
14 vCPUs, 112 GB | 4.97 | CNY/hour/unit | |||
16 vCPUs, 128 GB | 5.68 | CNY/hour/unit | |||
Cloud disk | 2 vCPUs, 16 GB | 0.50 | CNY/hour/unit | ||
4 vCPUs, 16 GB | 0.75 | CNY/hour/unit | |||
4 vCPUs, 32 GB | 1.00 | CNY/hour/unit | |||
8 vCPUs, 16 GB | 1.17 | CNY/hour/unit | |||
8 vCPUs, 32 GB | 1.51 | CNY/hour/unit | |||
8 vCPUs, 64 GB | 2.00 | CNY/hour/unit | |||
12 vCPUs, 24 GB | 1.76 | CNY/hour/unit | |||
12 vCPUs, 48 GB | 2.26 | CNY/hour/unit | |||
12 vCPUs, 96 GB | 2.99 | CNY/hour/unit | |||
16 vCPUs, 32 GB | 2.35 | CNY/hour/unit | |||
16 vCPUs, 64 GB | 3.01 | CNY/hour/unit | |||
16 vCPUs, 128 GB | 3.99 | CNY/hour/unit | |||
24 vCPUs, 48 GB | 3.52 | CNY/hour/unit | |||
Singapore and Germany (Frankfurt) | Instance rental | - | - | 0.61 | CNY/hour/unit |
Query node | Local SSD | 2 vCPUs, 8 GB | 0.69 | CNY/hour/unit | |
4 vCPUs, 16 GB | 1.39 | CNY/hour/unit | |||
8 vCPUs, 32 GB | 2.78 | CNY/hour/unit | |||
Cloud disk | 2 vCPUs, 8 GB | 0.60 | CNY/hour/unit | ||
4 vCPUs, 16 GB | 1.21 | CNY/hour/unit | |||
8 vCPUs, 32 GB | 2.41 | CNY/hour/unit | |||
Data node | Local SSD | 2 vCPUs, 16 GB | 0.84 | CNY/hour/unit | |
4 vCPUs, 32 GB | 1.68 | CNY/hour/unit | |||
6 vCPUs, 48 GB | 2.52 | CNY/hour/unit | |||
8 vCPUs, 64 GB | 3.36 | CNY/hour/unit | |||
10 vCPUs, 80 GB | 4.19 | CNY/hour/unit | |||
12 vCPUs, 96 GB | 5.03 | CNY/hour/unit | |||
14 vCPUs, 112 GB | 5.87 | CNY/hour/unit | |||
16 vCPUs, 128 GB | 6.71 | CNY/hour/unit | |||
Cloud disk | 2 vCPUs, 16 GB | 0.74 | CNY/hour/unit | ||
4 vCPUs, 16 GB | 1.21 | CNY/hour/unit | |||
4 vCPUs, 32 GB | 1.49 | CNY/hour/unit | |||
8 vCPUs, 16 GB | 1.88 | CNY/hour/unit | |||
8 vCPUs, 32 GB | 2.41 | CNY/hour/unit | |||
8 vCPUs, 64 GB | 2.97 | CNY/hour/unit | |||
12 vCPUs, 24 GB | 2.81 | CNY/hour/unit | |||
12 vCPUs, 48 GB | 3.62 | CNY/hour/unit | |||
12 vCPUs, 96 GB | 4.46 | CNY/hour/unit | |||
16 vCPUs, 32 GB | 3.75 | CNY/hour/unit | |||
16 vCPUs, 64 GB | 4.83 | CNY/hour/unit | |||
16 vCPUs, 128 GB | 5.94 | CNY/hour/unit | |||
24 vCPUs, 48 GB | 5.63 | CNY/hour/unit | |||
China (Hong Kong) | Instance rental | - | - | 0.61 | CNY/hour/unit |
Query node | Local SSD | 2 vCPUs, 8 GB | 0.97 | CNY/hour/unit | |
4 vCPUs, 16 GB | 1.94 | CNY/hour/unit | |||
8 vCPUs, 32 GB | 3.88 | CNY/hour/unit | |||
Cloud disk | 2 vCPUs, 8 GB | 1.11 | CNY/hour/unit | ||
4 vCPUs, 16 GB | 2.23 | CNY/hour/unit | |||
8 vCPUs, 32 GB | 4.45 | CNY/hour/unit | |||
Data node | Local SSD | 2 vCPUs, 16 GB | 1.34 | CNY/hour/unit | |
4 vCPUs, 32 GB | 2.69 | CNY/hour/unit | |||
6 vCPUs, 48 GB | 4.03 | CNY/hour/unit | |||
8 vCPUs, 64 GB | 5.36 | CNY/hour/unit | |||
10 vCPUs, 80 GB | 6.72 | CNY/hour/unit | |||
12 vCPUs, 96 GB | 8.06 | CNY/hour/unit | |||
14 vCPUs, 112 GB | 9.41 | CNY/hour/unit | |||
16 vCPUs, 128 GB | 10.73 | CNY/hour/unit | |||
Cloud disk | 2 vCPUs, 16 GB | 1.41 | CNY/hour/unit | ||
4 vCPUs, 16 GB | 2.23 | CNY/hour/unit | |||
4 vCPUs, 32 GB | 2.83 | CNY/hour/unit | |||
8 vCPUs, 16 GB | 3.35 | CNY/hour/unit | |||
8 vCPUs, 32 GB | 4.45 | CNY/hour/unit | |||
8 vCPUs, 64 GB | 5.65 | CNY/hour/unit | |||
12 vCPUs, 24 GB | 5.03 | CNY/hour/unit | |||
12 vCPUs, 48 GB | 6.68 | CNY/hour/unit | |||
12 vCPUs, 96 GB | 8.48 | CNY/hour/unit | |||
16 vCPUs, 32 GB | 6.70 | CNY/hour/unit | |||
16 vCPUs, 64 GB | 8.90 | CNY/hour/unit | |||
16 vCPUs, 128 GB | 11.30 | CNY/hour/unit | |||
24 vCPUs, 48 GB | 10.05 | CNY/hour/unit |
Specification family recommendations: Choose local SSDs for low QPS and large indexes. Choose cloud disks for high QPS or when the indexes fit in memory.
Data node allocation: After you purchase data nodes, you can allocate replicas and data shards within the instance. The number of data nodes must be less than the number of replicas multiplied by the number of data shards. Change the replica count in the instance information and the shard count in the basic table information.
System-reserved storage: The system reserves part of the storage on cloud disk data nodes. The approximate amount reserved per node is 2 GB for 2 vCPUs and 16 GB of memory, 2 GB for 4 vCPUs and 32 GB of memory, 3 GB for 8 vCPUs and 64 GB of memory, and 5 GB for 16 vCPUs and 128 GB of memory. This restriction does not apply to local SSD data nodes.
Subscription
Region | Billable item | Specification family | Available specifications | Unit price | Unit |
China (Hangzhou), China (Shanghai), China (Beijing), and China (Shenzhen) | Instance rental | - | - | 248.48 | CNY/month |
Query node | Local SSD | 2 vCPUs, 8 GB | 375.02 | CNY/month | |
4 vCPUs, 16 GB | 750.04 | CNY/month | |||
8 vCPUs, 16 GB (China (Shanghai) only) | 1,318.25 | CNY/month | |||
8 vCPUs, 32 GB | 1,500.08 | CNY/month | |||
Cloud disk | 2 vCPUs, 8 GB | 244.08 | CNY/month | ||
4 vCPUs, 16 GB | 488.16 | CNY/month | |||
8 vCPUs, 32 GB | 976.32 | CNY/month | |||
Data node | Local SSD | 2 vCPUs, 16 GB | 459.68 | CNY/month | |
4 vCPUs, 32 GB | 919.37 | CNY/month | |||
6 vCPUs, 48 GB | 1,379.05 | CNY/month | |||
8 vCPUs, 16 GB (China (Shanghai) only) | 1,318.25 | CNY/month | |||
8 vCPUs, 64 GB | 1,838.74 | CNY/month | |||
10 vCPUs, 80 GB | 2,298.42 | CNY/month | |||
12 vCPUs, 96 GB | 2,758.10 | CNY/month | |||
14 vCPUs, 112 GB | 3,217.79 | CNY/month | |||
16 vCPUs, 128 GB | 3,677.47 | CNY/month | |||
Cloud disk | 2 vCPUs, 16 GB | 323.41 | CNY/month | ||
4 vCPUs, 16 GB | 488.16 | CNY/month | |||
4 vCPUs, 32 GB | 646.81 | CNY/month | |||
8 vCPUs, 16 GB | 760.72 | CNY/month | |||
8 vCPUs, 32 GB | 976.32 | CNY/month | |||
8 vCPUs, 64 GB | 1,293.62 | CNY/month | |||
12 vCPUs, 24 GB | 1,141.07 | CNY/month | |||
12 vCPUs, 48 GB | 1,464.48 | CNY/month | |||
12 vCPUs, 96 GB | 1,940.44 | CNY/month | |||
16 vCPUs, 32 GB | 1,521.43 | CNY/month | |||
16 vCPUs, 64 GB | 1,952.64 | CNY/month | |||
16 vCPUs, 128 GB | 2,587.25 | CNY/month | |||
24 vCPUs, 48 GB | 2,282.15 | CNY/month | |||
Singapore and Germany (Frankfurt) | Instance rental | - | - | 397.47 | CNY/month |
Query node | Local SSD | 2 vCPUs, 8 GB | 449.86 | CNY/month | |
4 vCPUs, 16 GB | 899.73 | CNY/month | |||
8 vCPUs, 32 GB | 1,799.46 | CNY/month | |||
Cloud disk | 2 vCPUs, 8 GB | 391.19 | CNY/month | ||
4 vCPUs, 16 GB | 782.38 | CNY/month | |||
8 vCPUs, 32 GB | 1,564.76 | CNY/month | |||
Data node | Local SSD | 2 vCPUs, 16 GB | 543.59 | CNY/month | |
4 vCPUs, 32 GB | 1,087.17 | CNY/month | |||
6 vCPUs, 48 GB | 1,630.76 | CNY/month | |||
8 vCPUs, 64 GB | 2,174.35 | CNY/month | |||
10 vCPUs, 80 GB | 2,717.93 | CNY/month | |||
12 vCPUs, 96 GB | 3,261.52 | CNY/month | |||
14 vCPUs, 112 GB | 3,805.11 | CNY/month | |||
16 vCPUs, 128 GB | 4,347.68 | CNY/month | |||
Cloud disk | 2 vCPUs, 16 GB | 481.51 | CNY/month | ||
4 vCPUs, 16 GB | 782.38 | CNY/month | |||
4 vCPUs, 32 GB | 963.02 | CNY/month | |||
8 vCPUs, 16 GB | 1,215.36 | CNY/month | |||
8 vCPUs, 32 GB | 1,564.76 | CNY/month | |||
8 vCPUs, 64 GB | 1,926.04 | CNY/month | |||
12 vCPUs, 24 GB | 1,823.03 | CNY/month | |||
12 vCPUs, 48 GB | 2,347.13 | CNY/month | |||
12 vCPUs, 96 GB | 2,889.05 | CNY/month | |||
16 vCPUs, 32 GB | 2,430.71 | CNY/month | |||
16 vCPUs, 64 GB | 3,129.51 | CNY/month | |||
16 vCPUs, 128 GB | 3,852.07 | CNY/month | |||
24 vCPUs, 48 GB | 3,646.07 | CNY/month | |||
China (Hong Kong) | Instance rental | - | - | 12.51 | CNY/month/unit |
Query node | Local SSD | 2 vCPUs, 8 GB | 19.78 | CNY/month/unit | |
4 vCPUs, 16 GB | 39.56 | CNY/month/unit | |||
8 vCPUs, 32 GB | 79.13 | CNY/month/unit | |||
Cloud disk | 2 vCPUs, 8 GB | 22.70 | CNY/month/unit | ||
4 vCPUs, 16 GB | 45.39 | CNY/month/unit | |||
8 vCPUs, 32 GB | 90.78 | CNY/month/unit | |||
Data node | Local SSD | 2 vCPUs, 16 GB | 27.41 | CNY/month/unit | |
4 vCPUs, 32 GB | 54.83 | CNY/month/unit | |||
6 vCPUs, 48 GB | 82.24 | CNY/month/unit | |||
8 vCPUs, 64 GB | 109.40 | CNY/month/unit | |||
10 vCPUs, 80 GB | 137.06 | CNY/month/unit | |||
12 vCPUs, 96 GB | 164.48 | CNY/month/unit | |||
14 vCPUs, 112 GB | 191.89 | CNY/month/unit | |||
16 vCPUs, 128 GB | 218.79 | CNY/month/unit | |||
Cloud disk | 2 vCPUs, 16 GB | 28.82 | CNY/month/unit | ||
4 vCPUs, 16 GB | 45.39 | CNY/month/unit | |||
4 vCPUs, 32 GB | 57.63 | CNY/month/unit | |||
8 vCPUs, 16 GB | 68.34 | CNY/month/unit | |||
8 vCPUs, 32 GB | 90.78 | CNY/month/unit | |||
8 vCPUs, 64 GB | 115.26 | CNY/month/unit | |||
12 vCPUs, 24 GB | 102.51 | CNY/month/unit | |||
12 vCPUs, 48 GB | 136.17 | CNY/month/unit | |||
12 vCPUs, 96 GB | 172.89 | CNY/month/unit | |||
16 vCPUs, 32 GB | 136.68 | CNY/month/unit | |||
16 vCPUs, 64 GB | 181.56 | CNY/month/unit | |||
16 vCPUs, 128 GB | 230.52 | CNY/month/unit | |||
24 vCPUs, 48 GB | 205.02 | CNY/month/unit |
Storage capacity fees per data node
Pay-as-you-go
Storage capacity fee per data node = (Total storage capacity per data node - Free storage capacity per data node) * Unit price * Number of hours * Number of data nodes.
Region | Billable item | Data node specification family | Data node specifications | Free storage capacity | Available storage capacity range | Increment | Unit price | Unit |
China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), and China (Zhangjiakou) | Storage capacity per data node | Local SSD | 2 vCPUs, 16 GB | 100GB | [100GB,200GB] | 50GB | 0.000588 | CNY/hour/GB |
4 vCPUs, 32 GB | 200GB | [200GB,600GB] | ||||||
6 vCPUs, 48 GB | 300GB | [300GB,700GB] | ||||||
8 vCPUs, 16 GB (China (Shanghai) only) | 100GB | [100GB,200GB] | ||||||
8 vCPUs, 64 GB | 400GB | [400GB,800GB] | ||||||
10 vCPUs, 80 GB | 500GB | [500GB,900GB] | ||||||
12 vCPUs, 96 GB | 600GB | [600GB,1000GB] | ||||||
14 vCPUs, 112 GB | 700GB | [700GB,1100GB] | ||||||
16 vCPUs, 128 GB | 800GB | [800GB,1200GB] | ||||||
Cloud disk | 2 vCPUs, 16 GB | 0GB | [100GB,200GB] | 0.0014 | ||||
4 vCPUs, 16 GB | [100GB,200GB] | |||||||
4 vCPUs, 32 GB | [100GB,600GB] | |||||||
8 vCPUs, 16 GB | [100GB,200GB] | |||||||
8 vCPUs, 32 GB | [100GB,600GB] | |||||||
8 vCPUs, 64 GB | [100GB,800GB] | |||||||
12 vCPUs, 24 GB | [100GB,500GB] | |||||||
12 vCPUs, 48 GB | [100GB,700GB] | |||||||
12 vCPUs, 96 GB | [100GB,1000GB] | |||||||
16 vCPUs, 32 GB | [100GB,600GB] | |||||||
16 vCPUs, 64 GB | [100GB,800GB] | |||||||
16 vCPUs, 128 GB | [100GB,1200GB] | |||||||
24 vCPUs, 48 GB | [100GB,700GB] | |||||||
Singapore and Germany (Frankfurt) | Storage capacity per data node | Local SSD | 2 vCPUs, 16 GB | 100GB | [100GB,200GB] | 50GB | 0.000588 | CNY/hour/GB |
4 vCPUs, 32 GB | 200GB | [200GB,600GB] | ||||||
6 vCPUs, 48 GB | 300GB | [300GB,700GB] | ||||||
8 vCPUs, 64 GB | 400GB | [400GB,800GB] | ||||||
10 vCPUs, 80 GB | 500GB | [500GB,900GB] | ||||||
12 vCPUs, 96 GB | 600GB | [600GB,1000GB] | ||||||
14 vCPUs, 112 GB | 700GB | [700GB,1100GB] | ||||||
16 vCPUs, 128 GB | 800GB | [800GB,1200GB] | ||||||
Cloud disk | 2 vCPUs, 16 GB | 0GB | [100GB,200GB] | 0.001421 | ||||
4 vCPUs, 16 GB | [100GB,200GB] | |||||||
4 vCPUs, 32 GB | [100GB,600GB] | |||||||
8 vCPUs, 16 GB | [100GB,200GB] | |||||||
8 vCPUs, 32 GB | [100GB,600GB] | |||||||
8 vCPUs, 64 GB | [100GB,800GB] | |||||||
12 vCPUs, 24 GB | [100GB,500GB] | |||||||
12 vCPUs, 48 GB | [100GB,700GB] | |||||||
12 vCPUs, 96 GB | [100GB,1000GB] | |||||||
16 vCPUs, 32 GB | [100GB,600GB] | |||||||
16 vCPUs, 64 GB | [100GB,800GB] | |||||||
16 vCPUs, 128 GB | [100GB,1200GB] | |||||||
24 vCPUs, 48 GB | [100GB,700GB] | |||||||
China (Hong Kong) | Storage capacity per data node | Local SSD | 2 vCPUs, 16 GB | 100GB | [100GB,200GB] | 50GB | 0.000588 | CNY/hour/GB |
4 vCPUs, 32 GB | 200GB | [200GB,600GB] | ||||||
6 vCPUs, 48 GB | 300GB | [300GB,700GB] | ||||||
8 vCPUs, 64 GB | 400GB | [400GB,800GB] | ||||||
10 vCPUs, 80 GB | 500GB | [500GB,900GB] | ||||||
12 vCPUs, 96 GB | 600GB | [600GB,1000GB] | ||||||
14 vCPUs, 112 GB | 700GB | [700GB,1100GB] | ||||||
16 vCPUs, 128 GB | 800GB | [800GB,1200GB] | ||||||
Cloud disk | 2 vCPUs, 16 GB | 0GB | [100GB,200GB] | 0.001574 | ||||
4 vCPUs, 16 GB | [100GB,200GB] | |||||||
4 vCPUs, 32 GB | [100GB,600GB] | |||||||
8 vCPUs, 16 GB | [100GB,200GB] | |||||||
8 vCPUs, 32 GB | [100GB,600GB] | |||||||
8 vCPUs, 64 GB | [100GB,800GB] | |||||||
12 vCPUs, 24 GB | [100GB,500GB] | |||||||
12 vCPUs, 48 GB | [100GB,700GB] | |||||||
12 vCPUs, 96 GB | [100GB,1000GB] | |||||||
16 vCPUs, 32 GB | [100GB,600GB] | |||||||
16 vCPUs, 64 GB | [100GB,800GB] | |||||||
16 vCPUs, 128 GB | [100GB,1200GB] | |||||||
24 vCPUs, 48 GB | [100GB,700GB] |
Subscription
Region | Billable item | Data node specification family | Unit price | Unit |
China (Hangzhou), China (Shanghai), China (Beijing), and China (Shenzhen) | Storage capacity per data node | Local SSD | 0.380700 | CNY/GB/month |
Cloud disk | 0.907200 | CNY/GB/month | ||
Singapore and Germany (Frankfurt) | Local SSD | 0.380700 | CNY/GB/month | |
Cloud disk | 0.920842 | CNY/GB/month | ||
China (Hong Kong) | Storage capacity per data node | Local SSD | 0.35955 | CNY/GB/month |
Cloud disk | 0.96303 | CNY/GB/month |
Index storage fees
Pay-as-you-go
OpenSearch Retrieval Engine Edition charges for index storage based on the actual index size.
Index storage fee = Unit price * Number of hours * (Index size - 100).
If the total index size in an instance is less than 100 GB, index storage fees are 0. If it exceeds 100 GB, the portion above 100 GB is charged at the unit price.
Region | Billable item | Free storage quota | Unit price | Unit |
China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), and China (Zhangjiakou) | Index storage | 100GB | 0.000415 | CNY/hour/GB |
Singapore and Germany (Frankfurt) | Index storage | 100GB | 0.000358 | CNY/hour/GB |
China (Hong Kong) | Index storage | 100GB | 0.000442 | CNY/hour/GB |
Data update fees
Pay-as-you-go
OpenSearch Retrieval Engine Edition charges data update fees based on the number of resources used to update data.
Each data source or table in an instance receives two free data update resources, each with 4 vCPUs and 8 GB of memory. You can request additional resources and pay for the resources that exceed this free quota.
Data update resource fee = (Total number of data update resources - Number of free data update resources) * Unit price * Number of hours.
Region | Billable item | Unit price | Unit |
China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), and China (Zhangjiakou) | Number of data update resources | 0.67 | CNY/hour/unit |
Singapore and Germany (Frankfurt) | Number of data update resources | 0.74 | CNY/hour/unit |
China (Hong Kong) | Number of data update resources | 0.76 | CNY/hour/unit |
Change instance configurations
Upgrade or downgrade an instance
Item | Category | Description |
When changes take effect | Immediately | Upgrades and downgrades take effect immediately. |
Configurable items | Availability edition | You can switch between the Standard Edition and High-availability Edition.
|
Number of query nodes | You can increase or decrease the number of query nodes. Before you decrease the number of query nodes, make sure the resulting count is greater than or equal to the number of query nodes in use. For example, if an instance has 10 query nodes and four are in use, you can decrease the count to a minimum of four query nodes. | |
Query node specifications | Query nodes currently support only specification upgrades. Both the vCPU count and memory capacity after the change must be greater than or equal to their original values. | |
Number of data nodes | You can increase or decrease the number of data nodes. Before you decrease the number of data nodes, make sure the resulting count is greater than or equal to the number of data nodes in use. For example, if an instance has 10 data nodes and six are in use, you can decrease the count to a minimum of six data nodes. | |
Data node specifications | Data nodes currently support only specification upgrades. Both the vCPU count and memory capacity after the change must be greater than or equal to their original values. | |
Billing rules | Pay-as-you-go | After an upgrade or downgrade takes effect, charges are calculated based on the new specifications. |
Procedure:
On the Instances page, find the instance that you want to upgrade or downgrade. In the Actions column on the right, click Upgrade/Downgrade.
On the configuration change page, select the required values for Availability edition, Number of query nodes, Query node specifications, Number of data nodes, Data node specifications, select the service agreement, and click Buy Now to apply the changes.
For Query node specification family, you can select Cloud disk or Local SSD.
1. Each configuration change can include only upgrades or only downgrades. You cannot upgrade some items and downgrade others in the same operation.
For example, for an instance with two query nodes and two data nodes:
Changing to one query node and three data nodes is not supported.
Changing to one query node and one data node is supported.
Changing to one query node and two data nodes is supported.
Changing to three query nodes and three data nodes is supported, as are similar upgrades.
2. Before you decrease the number of query nodes or data nodes, make sure the resulting count is greater than or equal to the number of corresponding nodes in use. The console checks this and displays a prompt. Increases and decreases in the number of data nodes take effect immediately.
For example, if an instance has 10 query nodes and four are in use, you can decrease the count to a minimum of four query nodes.
3. Changing query node or data node specifications triggers a node change in the background. You cannot perform other configuration changes or editing operations during this process.
4. If you change the number of query nodes or data nodes, you must also manually change the count in the cluster for the change to take effect. For more information, see Deployment management.
5. Number of query nodes in a cluster = Query node count * Number of replicas. Number of data nodes in a cluster = Number of replicas * Number of data shards. When you scale out, add nodes in multiples of the shard count. A data shard is the smallest unit of data.
6. Switching from High-availability Edition to Standard Edition deletes the second cluster in the instance by default. If the two clusters in different zones have different configurations, switching to a single zone may affect your service. Proceed with caution.
7. After a configuration change, the number of data nodes in a zone must be greater than or equal to the number of data nodes currently in use in that zone.
Overdue payments and refunds
Impact of expiration or overdue payments
Instance type | Instance status | Action |
Pay-as-you-go instance | On day 1 after a payment becomes overdue, the system sends SMS and email reminders to top up your account as soon as possible. All services remain available during this period. | Top up your Alibaba Cloud account as soon as possible. |
From day 2 to day 14 after your Alibaba Cloud account has an overdue payment, all pay-as-you-go instances in the account are frozen. | Top up your Alibaba Cloud account to restore the instances immediately. | |
On day 15 after a payment becomes overdue, the system automatically releases the instance and deletes its data. | The instance and its data cannot be recovered. | |
Subscription instance | From day 1 to day 14 after expiration, the instance is frozen and cannot provide services. | Manually renew the instance to restore service immediately. |
On day 15 after expiration, the system automatically releases the instance and deletes its data. | The instance and its data cannot be recovered. |
To avoid service interruptions, renew subscription instances before they expire or enable auto-renewal.
Make sure your account has a sufficient balance.
Refunds
OpenSearch Retrieval Engine Edition pay-as-you-go refund policy: Pay-as-you-go products are consumable services and are not eligible for refunds.
View billing details
You can view billing details for OpenSearch Retrieval Engine Edition instances in the Alibaba Cloud console, including separate charges for instance rental, query nodes, and data nodes.
Procedure
Log on to the Alibaba Cloud console.
In the upper-right corner of the page, choose Expenses>Bills.
In the left-side navigation pane, choose Bill Management>Bill Details.
On the Billing Details tab, search by Instance Name or Instance ID to view detailed bills.