How Do I Determine Whether a Cluster Uses the x86 or Arm Architecture?
Procedure
- Log in to the GaussDB(DWS) management console.
- Choose Clusters > Dedicated Cluster. All clusters will be displayed by default.
- In the cluster list, click the name of a cluster to go to the Cluster Information page. In the Basic Information area, check the node specifications of the cluster.
- Determine the cluster architecture based on the node specifications. The following table describes the specifications.
Table 1 Flavor description Node
vCPU Cores
Memory (GB)
Architecture
Type
dws2.olap.4xlarge.m6
16
128
x86
ECS/storage-compute decoupling EVS
dws2.olap.8xlarge.m6
32
256
x86
ECS/storage-compute decoupling EVS
dws2.olap.16xlarge.m6
64
512
x86
ECS/storage-compute decoupling EVS
dws2.olap.4xlarge.kc1
16
64
Arm
ECS/storage-compute decoupling EVS
dws2.olap.4xlarge.km1
16
128
Arm
ECS/storage-compute decoupling EVS
dws2.olap.6xlarge.km1
24
192
Arm
ECS/storage-compute decoupling EVS
dws2.olap.8xlarge.km1
32
256
Arm
ECS/storage-compute decoupling EVS
dws2.olap.12xlarge.km1
48
384
Arm
ECS/storage-compute decoupling EVS
dws2.m6.4xlarge.8
16
128
x86
ECS/EVS
dws2.m6.8xlarge.8
32
256
x86
ECS/EVS
dws2.m6.16xlarge.8
64
512
x86
ECS/EVS
dws2.km1.4xlarge.8
16
128
Arm
ECS/EVS
dws2.km1.6xlarge.8
24
192
Arm
ECS/EVS
dws2.km1.8xlarge.8
32
256
Arm
ECS/EVS
dws2.km1.12xlarge.8
48
384
Arm
ECS/EVS
dws2.km1.xlarge
4
32
Arm
ECS/EVS
dws2.kc1.4xlarge
16
64
Arm
ECS/EVS
dws2.olap.4xlarge.i3
16
128
x86
ECS/Local passthrough
dws2.olap.8xlarge.i3
32
256
x86
ECS/Local passthrough
dws2.olap.16xlarge.i3
64
512
x86
ECS/Local passthrough
dws2.olap.4xlarge.ki1
16
64
Arm
ECS/Local passthrough
dws2.olap.8xlarge.ki1
32
128
Arm
ECS/Local passthrough
dws2.olap.16xlarge.ki1
64
228
Arm
ECS/Local passthrough
dws2.physical.ki1ne.4xlarge
128
512
Arm
BMS
dws2.physical.ki1ne.4xlarge.a
128
512
Arm
BMS
dws2.physical.c6sd.6xlarge
104
768
x86
BMS
dws2.physical.c6sd.6xlarge.7
104
768
x86
BMS
dws2.physical.c6sd.6xlarge.7.cbg
104
768
x86
BMS
dws2.physical.c6sd.6xlarge.a.7
104
768
x86
BMS
dws2.physical.io6.3xlarge.4a
104
384
x86
BMS
dws2.physical.c6d.6xlarge.3a.cbg
88
768
x86
BMS
dws2.physical.c6sd.6xlarge.a.7.cbg
104
768
x86
BMS
dws2.physical.c6sd.6xlarge.1.cbg
104
768
x86
BMS
Cluster Management FAQs
- What Do I Do If Creating a GaussDB(DWS) Cluster Failed?
- How Can I Clear and Reclaim the Storage Space?
- Can I Switch My Cluster Nodes to Another Region After Purchase?
- Why Did the Used Storage Shrink After Scale-out?
- How Do I View Node Metrics (CPU, Memory, and Disk Usage)?
- Does GaussDB(DWS) Support a Single Node for a Learning Environment?
- Does GaussDB(DWS) Support BMS?
- How Is the Disk Space or Capacity of GaussDB(DWS) Calculated?
- What Are the gaussdb and postgres Databases of GaussDB(DWS)?
- How Do I Set the Maximum Number of Sessions When Adding an Alarm Rule on Cloud Eye?
- How Do I Determine Whether a Cluster Uses the x86 or Arm Architecture?
- What Should I Do If the Scale-out Check Fails?
- When Should I Add CNs or Scale out a cluster?
- What Are the Scenarios of Resizing a Cluster, Changing the Node Flavor, Scale-out, and Scale-in?
- How Should I Select from a Small-Flavor Many-Node Cluster and a Large-Flavor Three-Node Cluster with Same CPU Cores and Memory?
- What Are the Differences Between Cloud SSDs and Local SSDs?
- What Are the Differences Between Hot Data Storage and Cold Data Storage?
- What Do I do if the Scale-in Button Is Dimmed?
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.
Chatbotmore
