This topic describes the d1 big data instance family and d1ne big data instance family with enhanced network performance. It also includes information about the instance types that belong to these instance families.

Description

The d1ne and d1 instance families are designed to deliver cloud computing and massive data storage to support big data-oriented business needs. These instances are suitable for Hadoop distributed computing, massive log processing, large data warehousing, and other scenarios that require offline computing and storage of massive data. The storage performance, storage capacity, internal bandwidth, and other specifications of these instance types can satisfy the requirements of distributed computing businesses that typically use Hadoop.

These instance families are suitable for customers in Internet, finance, and other industries that need to compute, store, and analyze big data. Following the requirements of distributed computing high availability frameworks such as Hadoop, the d1ne and d1 instance families adopt the design of local storage. With only a cost similar to that for building a Hadoop cluster in an Internet data center (IDC), you can guarantee massive storage space and high storage performance.

Features of d1ne and d1 instance families:
  • Enterprise-level computing power that guarantees efficient and stable data processing.
  • Enhanced network performance including maximum internal bandwidth per instance and maximum packet forwarding rate that satisfies the demand for data transfer during peak hours, such as shuffling in Hadoop MapReduce.
  • A sequential read and write performance of 190 MB/s for a single disk (when you create an instance for the first time, disks require time to warm up before they can achieve optimal performance) and a maximum 5 GB/s of storage throughput for a single instance. These features shorten the time of reading data from and writing data to Hadoop Distributed File System (HDFS) files.
  • The cost of local storage is 97% lower than that of SSD disk storage, representing a huge reduction in costs for building Hadoop clusters.
When using d1ne and d1 instance families, note the following:
  • The configurations of instances with local SSDs are fixed. Automatic switchover upon dedicated host failures is not supported for instances with local SSDs.
  • The number and capacity of local disks of an instance vary depending on the instance type. You cannot attach additional local disks to instances with local SSDs because instances with local SSDs can only use default local SSDs. You cannot detach a local disk from an instance with local SSDs and then attach it to another instance.
  • You cannot create a snapshot for local disks. If you need to create an image for the system disk and data disks of an instance with local SSDs, we recommend that you create an image through the snapshots of both the system disk and data disks (data disks must be non-local disks).
  • You cannot create an image for the system disk and data disks of an instance with local SSDs based on the instance ID. Therefore, you cannot use a custom image to create an instance with local SSDs.
  • You can attach an SSD disk to an instance with local SSDs. The capacity of the SSD disk is scalable.
  • A single point of failure (SPOF) may be evident at the application layer due to each local disk being attached to a single host machine, meaning data reliability is dependent on the reliability of the host machine. We recommend that you implement data redundancy at the application layer to guarantee data availability.
    Warning When you use a local disk to store data, there is a risk of data loss (for example, if a hardware fault occurs to the host machine). Therefore, we recommend you do not use a local disk to store any data that you need to keep for a long term. If your applications have no data reliability architecture, we recommend that you use cloud disks or Shared Block Storage in your instances to increase data reliability.
  • Operations made on an instance with local SSDs may affect the data stored on the local disk. For more information, see Local disks.

Big data instance family with enhanced network performance, d1ne

Features:
  • Optimized I/O performance
  • Supports SSDs and ultra disks
  • High-capacity local SATA hard disk drives (SATA HDDs) with high throughput and a maximum of 35 Gbit/s bandwidth among instances
  • 1:4 CPU-to-memory ratio, designed for big data scenarios
  • 2.5 GHz Intel ® Xeon ® E5-2682 v4 (Broadwell) processors
  • Higher network performance along with more computing capacity
  • Scenarios:
    • Hadoop MapReduce, HDFS, Hive, and HBase
    • Spark in-memory computing and MLlib
    • Enterprises in Internet, finance, and other industries that need to compute, store, and analyze large volumes of data
    • Elasticsearch and logging
The following table describes the instance types that belong to the d1ne instance family and specifications of these instance types.
Instance type vCPUs Memory (GiB) Local storage (GiB) Bandwidth (Gbit/s, inbound or outbound) Packet forwarding rate (Kpps, inbound or outbound) Supports IPv6 NIC queues ENIs (including one primary ENI) Private IP addresses for a single ENI
ecs.d1ne.2xlarge 8 32.0 4 × 5,500 6.0 1,000 Yes 4 4 10
ecs.d1ne.4xlarge 16 64.0 8 × 5,500 12.0 1,600 Yes 4 8 20
ecs.d1ne.6xlarge 24 96.0 12 × 5,500 16.0 2,000 Yes 6 8 20
ecs.d1ne-c8d3.8xlarge 32 128.0 12 × 5,500 20.0 2,000 Yes 6 8 20
ecs.d1ne.8xlarge 32 128.0 16 × 5,500 20.0 2,500 Yes 8 8 20
ecs.d1ne-c14d3.14xlarge 56 160.0 12 × 5,500 35.0 4,500 Yes 14 8 20
ecs.d1ne.14xlarge 56 224.0 28 × 5,500 35.0 4,500 Yes 14 8 20
Note

Big data instance family, d1

Features:
  • Optimized I/O performance
  • Supports SSDs and ultra disks
  • High-capacity local SATA HDDs with high throughput and up to 17 Gbit/s of bandwidth among instances
  • 1:4 CPU-to-memory ratio, designed for big data scenarios
  • 2.5 GHz Intel ® Xeon ® E5-2682 v4 (Broadwell) processors
  • Higher network performance along with more computing capacity
  • Scenarios:
    • Hadoop MapReduce, HDFS, Hive, and HBase
    • Spark in-memory computing and MLlib
    • Enterprises in Internet, finance, other industries that need to compute, store, and analyze large volumes of data
    • Elasticsearch and logging
The following table describes the instance types that belong to the d1 instance family and specifications of these instance types.
Instance type vCPUs Memory (GiB) Local storage (GiB) Bandwidth (Gbit/s, inbound or outbound) Packet forwarding rate (Kpps, inbound or outbound) Supports IPv6 NIC queues ENIs (including one primary ENI) Private IP addresses for a single ENI
ecs.d1.2xlarge 8 32.0 4 × 5,500 3.0 300 No 1 4 10
ecs.d1.3xlarge 12 48.0 6 × 5,500 4.0 400 No 1 6 10
ecs.d1.4xlarge 16 64.0 8 × 5,500 6.0 600 No 2 8 20
ecs.d1.6xlarge 24 96.0 12 × 5,500 8.0 800 No 2 8 20
ecs.d1-c8d3.8xlarge 32 128.0 12 × 5,500 10.0 1,000 No 4 8 20
ecs.d1.8xlarge 32 128.0 16 × 5,500 10.0 1,000 No 4 8 20
ecs.d1-c14d3.14xlarge 56 160.0 12 × 5,500 17.0 1,800 No 6 8 20
ecs.d1.14xlarge 56 224.0 28 × 5,500 17.0 1,800 No 6 8 20
Note