2023-03-30
|
Modified the following sections:
diff --git a/docs/dis/umn/dis_01_0076.html b/docs/dis/umn/dis_01_0076.html
new file mode 100644
index 00000000..a3dcdec1
--- /dev/null
+++ b/docs/dis/umn/dis_01_0076.html
@@ -0,0 +1,31 @@
+
+
+Managing Applications
+An application is a program identifier. Multiple applications can access data in the same stream. Checkpoints generated for each application are used to record the consumed data in the stream by each application.
+ You can create applications and view details about existing application on the DIS console.
+ Creating an Application- Use the account to log in to the DIS console.
- Click
 in the upper left corner of the page and select a region and project. - In the navigation tree, select App Management.
On the Applications page, click Create App and enter an application name.
+
+
+ Viewing an Application- Use the account to log in to the DIS console.
- Click
 in the upper left corner of the page and select a region and project. - In the navigation tree on the left, choose Stream Management.
- Click the name of a stream that you want to view.
- Click Applications to view all applications that access the stream.
You can view the names, IDs, and creation time of the applications that access the stream.
+After you click Remove All Checkpoints, all checkpoints of the application will be deleted.
+ When an application consumes data, the latest SN of the consumed data is recorded as a checkpoint. When the data is reconsumed, the consumption can be continued based on this checkpoint.
+ Figure 1 Viewing applications
+ - Click a specific application to view its consumption details about the stream.
Figure 2 Viewing stream consumption details
+
+
+ Scaling Up/Down a Stream
+After a stream is created successfully, you can scale up or down a stream by adding or reducing partitions to meet capacity change requirements. Streams can be scaled automatically or manually.
+ Constraints- A maximum of 10 automatic scale-up, 10 manual scale-up, and 1 scale-down operations can be performed for each stream within one hour.
- After scaling up or down a stream, pay attention to the following:
- When uploading data, you are not advised to set PartitionKey. DIS automatically uploads data to multiple partitions based on the number of partitions in the stream. If you set PartitionKey, data skew and throttling may occur in the stream.
- When downloading data, you need to periodically use the descriptStream API to check the partition quantity change so that DIS can download data from all partitions.
+
+
+ Auto ScalingAuto Scaling Mechanism- If throttling is triggered in the last minute (that is, the maximum throughput of the partitions in the stream has been reached) and the upload traffic of the stream is greater than 80% of the stream bandwidth, an automatic scale-up is triggered. The number of target partitions is equal to the number of current partitions divided by 0.6 and rounded up.
For example, a stream has five common partitions, and the upload bandwidth of the stream is 5 Mbit/s. If throttling is triggered in the last minute and the upload traffic of the stream exceeds 4 Mbit/s, an automatic scale-up is triggered to add four more partitions. The number of target partitions is 8.3 (5/0.6), which is rounded up to 9.
+ - If the upload traffic and download traffic of a stream are both less than 30% of the stream bandwidth, an auto scale-down is triggered. The number of target partitions is equal to the number of current partitions divided by 2 and rounded down.
For example, a stream has five common partitions, and its upload and download bandwidth is 5 Mbit/s and 10 Mbit/s, respectively. If the upload traffic of the stream is less than 1.5 Mbit/s and the download traffic is less than 3 Mbit/s, an automatic scale-down is triggered to remove three partitions. The number of target partitions is 2.5 (5/2), which is rounded down to 2.
+
+
+ Auto Scaling Rules- The interval between performing automatic scale-up and scale-down must be greater than 1 minute. Automatic scale-down cannot be triggered within 2 minutes after automatic or manual scale-up is performed, and meanwhile automatic scale-up cannot be triggered within 2 minutes after automatic or manual scale-down is performed.
- When scaling up a stream, restore the DELETED and EXPIRED partitions to the ACTIVE partitions to make the partitions accessible. If the stream capacity is still insufficient, the system will create new partitions.
- The partitions that have been scaled down will not be charged or occupy the quota. Data on those partitions is readable but is not writable during Data Retention configured in Step 1: Creating a DIS Stream. Once Data Retention is expired, the data will become inaccessible.
+
+ Enabling Auto Scaling
+ - Use the account to log in to the DIS console.
- Click
 in the upper left corner of the page and select a region and project. - Perform the following steps to automatically scale up or down a stream:
In the navigation tree on the left, choose Stream Management. - On the Stream Management page, click the name of the stream to be scaled.
- Click
 next to Auto Scaling. - In the displayed Edit Auto-Scaling Parameter dialog box, enable Auto-Scaling.
Figure 1 Edit Auto-Scaling Parameter
+ - Set the upper and lower thresholds for automatic scaling and click OK.
+
+
+ Manual ScalingManual Scaling Rules- When scaling up a stream, ensure that the number of target partitions is greater than the number of the current partitions but is not greater than the total number of the remaining quotas and current partitions.
- When scaling up a stream, restore the DELETED and EXPIRED partitions to the ACTIVE partitions to make the partitions accessible. If the stream capacity is still insufficient, the system will create new partitions.
- When scaling down a stream, ensure that the number of target partitions is smaller than the number of current partitions but is not smaller than 1.
- The partitions that have been scaled down will not be charged or occupy the quota. Data on those partitions is readable but is not writable during Data Retention configured in Step 1: Creating a DIS Stream. Once Data Retention is expired, the data will become inaccessible.
+
+ Manually Scaling Up/Down a Stream
+ - Use the account to log in to the DIS console.
- Click
 in the upper left corner of the page and select a region and project. - Perform either of the following operations to manually scale up or down a stream:
- In the navigation tree on the left, choose Stream Management.
- On the Stream Management page, click the name of the stream to be scaled.
- In the upper right corner of the displayed page, click Scale Up/Down. The Scale Up/Down Stream dialog box is displayed.
- Change the number of target partitions and click Yes.
+
+- In the navigation tree on the left, choose Stream Management.
- In the Operation column of the stream to be scaled, click More and choose Scale Up/Down from the drop-down list.
- The Scale Up/Down Partition dialog box is displayed.
- Change the number of target partitions and click Yes.
+
+
+
+ Viewing Scale-Up/Down Logs- Use the account to log in to the DIS console.
- Click
 in the upper left corner of the page and select a region and project. - In the navigation tree on the left, choose Stream Management.
- Click the name of a stream to access its details page.
- On the displayed page, click the Scale-Up/Down Logs tab. View the scaling details of the stream.
+
+ Step 1: Creating a DIS Stream
You can create a DIS stream on the DIS management console.
- Procedure- Use the account to log in to the DIS console.
Figure 1 DIS management console
+Procedure- Use the account to log in to the DIS console.
Figure 1 DIS management console
- Click
 in the upper left corner of the page and select a region and project. - Click Create Stream and set related parameters.
Table 1 Stream parametersParameter
|
@@ -102,3 +102,10 @@
+
+
\ No newline at end of file
diff --git a/docs/dis/umn/en-us_image_0000001402769822.gif b/docs/dis/umn/en-us_image_0000001402769822.gif
deleted file mode 100644
index 7a96de25..00000000
Binary files a/docs/dis/umn/en-us_image_0000001402769822.gif and /dev/null differ
diff --git a/docs/dis/umn/en-us_image_0000001403080926.gif b/docs/dis/umn/en-us_image_0000001403080926.gif
deleted file mode 100644
index c1bf5de6..00000000
Binary files a/docs/dis/umn/en-us_image_0000001403080926.gif and /dev/null differ
diff --git a/docs/dis/umn/en-us_image_0000001403086902.gif b/docs/dis/umn/en-us_image_0000001403086902.gif
deleted file mode 100644
index f351d438..00000000
Binary files a/docs/dis/umn/en-us_image_0000001403086902.gif and /dev/null differ
diff --git a/docs/dis/umn/en-us_image_0000001453010069.gif b/docs/dis/umn/en-us_image_0000001453010069.gif
deleted file mode 100644
index cf29c245..00000000
Binary files a/docs/dis/umn/en-us_image_0000001453010069.gif and /dev/null differ
diff --git a/docs/dis/umn/en-us_image_0000001453327325.gif b/docs/dis/umn/en-us_image_0000001453327325.gif
deleted file mode 100644
index 51d5523b..00000000
Binary files a/docs/dis/umn/en-us_image_0000001453327325.gif and /dev/null differ
diff --git a/docs/dis/umn/en-us_image_0000001623208020.png b/docs/dis/umn/en-us_image_0000001623208020.png
new file mode 100644
index 00000000..cd0b130a
Binary files /dev/null and b/docs/dis/umn/en-us_image_0000001623208020.png differ
diff --git a/docs/dis/umn/en-us_image_0000001671447933.png b/docs/dis/umn/en-us_image_0000001671447933.png
new file mode 100644
index 00000000..c3abb84b
Binary files /dev/null and b/docs/dis/umn/en-us_image_0000001671447933.png differ
diff --git a/docs/dis/umn/en-us_image_0000001671647961.png b/docs/dis/umn/en-us_image_0000001671647961.png
new file mode 100644
index 00000000..55b527a7
Binary files /dev/null and b/docs/dis/umn/en-us_image_0000001671647961.png differ
diff --git a/docs/dis/umn/en-us_image_0000001788900822.png b/docs/dis/umn/en-us_image_0000001788900822.png
new file mode 100644
index 00000000..54599e0d
Binary files /dev/null and b/docs/dis/umn/en-us_image_0000001788900822.png differ
diff --git a/docs/dis/umn/en-us_image_0000001788903274.png b/docs/dis/umn/en-us_image_0000001788903274.png
new file mode 100644
index 00000000..440c3803
Binary files /dev/null and b/docs/dis/umn/en-us_image_0000001788903274.png differ
diff --git a/docs/dis/umn/en-us_image_0000001835382181.png b/docs/dis/umn/en-us_image_0000001835382181.png
new file mode 100644
index 00000000..121cfbc1
Binary files /dev/null and b/docs/dis/umn/en-us_image_0000001835382181.png differ
diff --git a/docs/dis/umn/en-us_image_0000001835503737.png b/docs/dis/umn/en-us_image_0000001835503737.png
new file mode 100644
index 00000000..5b41f00d
Binary files /dev/null and b/docs/dis/umn/en-us_image_0000001835503737.png differ
diff --git a/docs/dis/umn/en-us_image_0120396589.png b/docs/dis/umn/en-us_image_0120396589.png
new file mode 100644
index 00000000..cd0b130a
Binary files /dev/null and b/docs/dis/umn/en-us_image_0120396589.png differ
diff --git a/docs/dis/umn/en-us_image_0127307205.jpg b/docs/dis/umn/en-us_image_0127307205.jpg
new file mode 100644
index 00000000..27ea31b7
Binary files /dev/null and b/docs/dis/umn/en-us_image_0127307205.jpg differ
diff --git a/docs/dis/umn/en-us_image_0165093532.png b/docs/dis/umn/en-us_image_0165093532.png
new file mode 100644
index 00000000..cd0b130a
Binary files /dev/null and b/docs/dis/umn/en-us_image_0165093532.png differ
diff --git a/docs/dis/umn/en-us_image_0165094364.png b/docs/dis/umn/en-us_image_0165094364.png
new file mode 100644
index 00000000..cd0b130a
Binary files /dev/null and b/docs/dis/umn/en-us_image_0165094364.png differ
diff --git a/docs/dis/umn/en-us_image_0165229968.jpg b/docs/dis/umn/en-us_image_0165229968.jpg
new file mode 100644
index 00000000..8ab69d9d
Binary files /dev/null and b/docs/dis/umn/en-us_image_0165229968.jpg differ
diff --git a/docs/dis/umn/en-us_image_0165286917.jpg b/docs/dis/umn/en-us_image_0165286917.jpg
new file mode 100644
index 00000000..f6f79322
Binary files /dev/null and b/docs/dis/umn/en-us_image_0165286917.jpg differ
|---|
|
