No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionCloud 6.3.1.1 Solution Description 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Disk-intensive ECSs

Disk-intensive ECSs

Application Scenarios

Disk-intensive ECSs use local storage, and provide better sequential read and write performance and lower latency by using pass-through HDDs as data disks. They use a vCPU to memory ratio of 1:8 and provide powerful and stable computing performance, ensuring efficient data processing. They provide high intranet performance, including high intranet bandwidth and packets per second (pps), meeting the requirements for data exchange between ECSs during peak hours.

Disk-intensive ECSs are suitable for scenarios that require high I/O performance and rapid data switching and processing to handle massive data sets. Such scenarios include MapReduce computing, distributed Hadoop computing, large data warehouse, distributed file system, data processing, and log processing.

Notes

  • Disk-intensive ECSs do not support live migration, cold migration, VM HA, cloning, or ECS snapshot, but they support memory reuse and user-defined CPU QoS settings. A disk-intensive ECS cannot be changed into another type of ECS by changing its flavor. Disk-intensive ECSs cannot be used in a converged deployment scenario. A converged deployment means that FusionStorage is deployed on compute nodes.
  • Disk-intensive ECSs do not support hot-swapping, snapshot, or backup for pass-through HDDs.
  • Local and EVS disks can both be used to store data, but pass-through HDDs can only be used as data disks.
  • The local disk data of a disk-intensive ECS may be lost due to some events, such as host breakdown or local disk damage. Do not use local disks for persistent storage. Instead, back up data in a timely manner and use a high availability data architecture. If your application cannot provide the desired data reliability, you are advised to use EVS disks to build your ECS and store data persistently on EVS disks.
  • When you delete a disk-intensive ECS, the data on the local disk is automatically deleted.
  • When modifying the flavor of a disk-intensive ECS, you can add more local disks to expand local disk capacity. You cannot expand or reduce the capacity of existing local disks.

Flavors

Table 18-16 Flavors of disk-intensive ECSs

Type

vCPU

Memory (GB)

Flavor Name

Virtualization Type

Local Disks

Capacity of One Local Disk

Disk-intensive ECSs

4

32

d2.xlarge.8

KVM

2

1800 GB

8

64

d2.2xlarge.8

KVM

4

1800 GB

16

128

d2.4xlarge.8

KVM

8

1800 GB

24

192

d2.6xlarge.8

KVM

12

1800 GB

32

256

d2.8xlarge.8

KVM

16

1800 GB

60

540

d2.15xlarge.9

KVM

24

1800 GB

Translation
Download
Updated: 2019-10-23

Document ID: EDOC1100063247

Views: 73702

Downloads: 192

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next