doc-exports/docs/ecs/umn/en-us_topic_0035470099.html

Disk-intensive ECSs

Overview

D2 ECSs are developed based on KVM virtualization. They use local storage and provide high storage performance and intranet bandwidth for distributed Hadoop computing, large data warehouse, distributed file system, and log/data processing.

Specifications

Table 1 D2 ECS specifications

Flavor	vCPUs	Memory (GiB)	Max./Assured Network Bandwidth (Gbit/s)	Max. Network PPS (10,000)	Max. NIC Queues	Virtualization	Local Disks (GiB)	Hardware
d2.xlarge.8	4	32	4/1.4	40	2	KVM	2 × 1675	CPU: Intel® Xeon® Gold 6151
d2.2xlarge.8	8	64	6/2.8	80	4	KVM	4 × 1675
d2.4xlarge.8	16	128	10/5.6	160	6	KVM	8 × 1675
d2.6xlarge.8	24	192	15/8.5	250	8	KVM	12 × 1675
d2.8xlarge.8	32	256	17/11	320	8	KVM	16 × 1675
d2.15xlarge.9	60	540	17/17	500	16	KVM	24 × 1675

Scenarios

• Applications

  Disk-intensive ECSs are suitable for applications that require large volumes of data to process, high I/O performance, and rapid data switching and processing, such as MapReduce, Hadoop, and data-intensive computing.

• Application scenarios

  Big data computing, network file systems, data processing, MapReduce, Hadoop, and data-intensive computing

D2 ECS Features

• D2 ECSs use local disks to provide high sequential read/write performance and low latency, improving file read/write performance.
• D2 ECSs provide powerful and stable computing capabilities, ensuring efficient data processing.
• D2 ECSs with a vCPU/memory ratio of 1:8 process large volumes of data.
• D2 ECSs provide high intranet performance, including high intranet bandwidth and packets per second (PPS), meeting requirements for data exchange between ECSs during peak hours.
• Each D2 ECS supports a maximum configuration of 24 local disks, 60 vCPUs, and 540 GiB memory.

Table 2 Specifications of a Single SAS HDD Disk Attached to a D2 ECS

Metric	Performance
Disk capacity	1,675 GiB
Maximum throughput	230 MB/s
Access latency	Within milliseconds

Notes

• Table 3 lists the OSs supported by disk-intensive ECSs.

  Table 3 Supported OS versions

  OS	Version
  Alma	Alma 8 64bit
  CentOS	CentOS Stream 9.6 64bit CentOS Stream 8.6 64bit CentOS 8.5 64bit CentOS 8.4 64bit CentOS 8.3 64bit CentOS 8.2 64bit CentOS 8.1 64bit CentOS 7.9 64bit CentOS 7.7 64bit
  Debian	Debian GNU/Linux 12.0.0 64bit Debian GNU/Linux 11.7.0 64bit Debian GNU/Linux 11.6.0 64bit Debian GNU/Linux 11.5.0 64bit Debian GNU/Linux 11.4.0 64bit Debian GNU/Linux 11.3.0 64bit Debian GNU/Linux 11.2.0 64bit Debian GNU/Linux 11.1.0 64bit Debian GNU/Linux 11.0.0 64bit Debian GNU/Linux 10.13.0 64bit Debian GNU/Linux 10.12.0 64bit Debian GNU/Linux 10.11.0 64bit Debian GNU/Linux 10.10.0 64bit Debian GNU/Linux 10.9.0 64bit Debian GNU/Linux 10.8.0 64bit Debian GNU/Linux 10.7.0 64bit Debian GNU/Linux 10.6.0 64bit Debian GNU/Linux 10.5.0 64bit Debian GNU/Linux 10.4.0 64bit Debian GNU/Linux 10.3.0 64bit Debian GNU/Linux 10.2.0 64bit Debian GNU/Linux 10.1.0 64bit Debian GNU/Linux 10 64bit
  EulerOS	EulerOS 2.12 64bit EulerOS 2.11 64bit EulerOS 2.10 64bit EulerOS 2.8 64bit EulerOS 2.7 64bit EulerOS 2.5 64bit
  Fedora	Fedora 39 64bit Fedora 38 64bit Fedora 37 64bit Fedora 36 64bit Fedora 35 64bit Fedora 34 64bit Fedora 33 64bit Fedora 32 64bit Fedora 31 64bit
  OpenSUSE	OpenSUSE 15.5 64bit OpenSUSE 15.4 64bit OpenSUSE 15.3 64bit OpenSUSE 15.2 64bit
  Oracle Linux	Oracle Linux Server release 8.4 64bit Oracle Linux Server release 7.6 64bit
  Red Hat	Red Hat Enterprise Linux 9.1 64bit Red Hat Enterprise Linux 9.0 64bit Red Hat Enterprise Linux 8.7 64bit Red Hat Enterprise Linux 8.6 64bit Red Hat Enterprise Linux 8.5 64bit Red Hat Enterprise Linux 8.4 64bit Red Hat Enterprise Linux 8.3 64bit Red Hat Enterprise Linux 8.2 64bit Red Hat Enterprise Linux 8.1 64bit Red Hat Enterprise Linux 7.9 64bit Red Hat Enterprise Linux 6.10 64bit
  Rocky	9.2 64bit 9.1 64bit 9.0 64bit 8.8 64bit 8.7 64bit 8.6 64bit 8.5 64bit 8.4 64bit 8.3 64bit 8 64bit
  SUSE	Novell SUSE Linux Enterprise Server 15 SP5 64bit Novell SUSE Linux Enterprise Server 15 SP4 64bit Novell SUSE Linux Enterprise Server 15 SP3 64bit Novell SUSE Linux Enterprise Server 15 SP2 64bit Novell SUSE Linux Enterprise Server 15 SP1 64bit Novell SUSE Linux Enterprise Server 15 64bit Novell SUSE Linux Enterprise Server 12 SP5 64bit Novell SUSE Linux Enterprise Server 12 SP4 64bit Novell SUSE Linux Enterprise Server 12 SP3 64bit
  Ubuntu	Ubuntu 24.04 server 64bit Ubuntu 22.04 Server 64bit Ubuntu 20.04 server 64bit Ubuntu 18.04 server 64bit
  Windows	Windows Server 2025 Standard 64bit Windows Server 2022 Standard 64bit Windows Server 2022 Datacenter 64bit Windows Server 2019 Datacenter 64bit Windows Server 2019 Standard 64bit Windows Server 2016 Standard 64bit Windows Server 2012 R2 Standard 64bit
  openEuler	openEuler 22.03 SP1 64bit openEuler 22.03 64bit openEuler 20.03 SP3 64bit openEuler 20.03 SP2 64bit openEuler 20.03 SP1 64bit openEuler 20.03 64bit

• If the host where a D2 ECS is deployed becomes faulty, the ECS cannot be migrated.
• To improve network performance, you can set the NIC MTU of a D2 ECS to 8888.
• D2 ECSs do not support specification modification.
• D2 ECSs do not support local disk snapshots or backups.
• D2 ECSs do not support OS reinstallation or change.
• D2 ECSs can use both local disks and EVS disks to store data. In addition, they can have EVS disks attached to provide a larger storage size. Note the following when using the two types of storage media:
  • Only an EVS disk, not a local disk, can be used as the system disk of a D2 ECS.
  • Both EVS disks and local disks can be used as data disks of a D2 ECS.
  • A maximum of 60 disks (including VBD, SCSI, and local disks) can be attached to a D2 ECS. Among the 60 disks, the maximum number of SCSI disks is 30, and the VBD disks (including the system disk) is 24. For details, see Can I Attach Multiple Disks to an ECS?
    

    The maximum number of disks attached to an existing D2 ECS remains unchanged.

  • You are advised to use World Wide Names (WWNs), but not drive letters, in applications to perform operations on local disks to prevent drive letter drift (low probability) on Linux. Take local disk attachment as an example:

    If the local disk WWN is wwn-0x50014ee2b14249f6, run the mount /dev/disk/by-id/wwn-0x50014ee2b14249f6 command.

    

    How can I view the local disk WWN?

    1. Log in to the ECS.
    2. Run the following command:

       ll /dev/disk/by-id

• The local disk data of a D2 ECS may be lost if an exception occurs, such as physical server breakdown or local disk damage. If your application does not use the data reliability architecture, it is a good practice to use EVS disks to build your ECS.
• When a D2 ECS is deleted, its local disk data will also be automatically deleted. Back up data in advance. Deleting local disk data will increase the time needed to release resources compared with ECSs without local disks.
• Do not store service data in local disks for a long time. Instead, store it in EVS disks. To improve data security, use a high availability architecture and back up data in a timely manner.
• Local disks can only be purchased during D2 ECS creation. The quantity and capacity of your local disks are determined according to the specifications of your ECS.

Parent topic: ECS Specifications