Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Mekanisme kontrol alur di Cloud Data Fusion mencegah Anda mengirimkan terlalu banyak permintaan, yang dapat menyebabkan pipeline macet atau gagal dijalankan. Mekanisme ini
berlaku untuk memulai permintaan (Launch) untuk pipeline dan tugas berikut di semua
edisi Cloud Data Fusion, versi 6.6 dan yang lebih baru:
Pipeline batch
Pipeline real-time
Tugas replikasi
Batas
Untuk mengontrol jumlah permintaan mulai yang tertunda di Cloud Data Fusion, kontrol alur bergantung pada dua nilai minimum:
Nilai minimum peluncuran
Membatasi jumlah permintaan peluncuran yang dibuat. Jika jumlah permintaan peluncuran yang diterima oleh Cloud Data Fusion yang belum dalam status Running lebih besar dari nilai minimum peluncuran (jumlah permintaan peluncuran yang belum berjalan > nilai minimum peluncuran), permintaan akan ditolak. Jumlah tersebut mencakup pipeline batch, pipeline real-time, dan tugas replikasi.
Batas berjalan
Membatasi jumlah permintaan peluncuran yang belum terselesaikan di
sistem. Jika jumlah permintaan peluncuran yang belum selesai yang diterima oleh Cloud Data Fusion lebih besar dari nilai minimum operasi yang ditentukan (jumlah permintaan yang belum selesai > nilai minimum operasi), permintaan akan ditolak.
Permintaan yang ditolak
Jika salah satu nilai minimum terpenuhi, setiap permintaan mulai baru akan ditolak. Misalnya,
pipeline batch yang ditolak memiliki status Rejected dalam log, dan dialog di
UI menjelaskan alasan peluncuran ditolak.
Metrik
Jumlah peluncuran dan pengoperasian pipeline beserta jumlah pipeline yang ditolak
dalam sistem dapat diakses melalui layanan metrik sebagai berikut.
Metrik Launching
Melaporkan jumlah permintaan peluncuran di sistem. Artinya, laporan ini melaporkan
jumlah permintaan peluncuran yang dalam status Provisioning atau Starting.
Nama metrik: flowcontrol.launching.count
POST /v3/metrics/query?metric=system.flowcontrol.launching.count
Metrik Running
Melaporkan jumlah pipeline dan tugas yang berjalan di sistem. Batas
eksekusi didasarkan pada jumlah nilai metrik Launching dan Running.
Nama metrik: flowcontrol.running.count
POST /v3/metrics/query?metric=system.flowcontrol.running.count
Metrik Rejected
Melaporkan jumlah operasi yang ditolak karena mekanisme kontrol alur.
Nama metrik: program.rejected.runs
POST /v3/metrics/query?metric=system.program.rejected.runs
Langkah selanjutnya
Untuk contoh pemberian tag dan agregasi metrik Rejected untuk
pipeline yang berbeda, lihat
Microservice Metrik CDAP.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eCloud Data Fusion employs a flow control mechanism to prevent an excess of start requests, which could lead to pipeline issues.\u003c/p\u003e\n"],["\u003cp\u003eThe flow control mechanism uses a launch threshold that limits the number of launch requests not yet in the "Running" state and a runs threshold that limits the number of outstanding requests not yet finished.\u003c/p\u003e\n"],["\u003cp\u003eWhen either the launch or runs threshold is exceeded, new start requests will be rejected, and the rejection will be noted in the logs and displayed in the UI.\u003c/p\u003e\n"],["\u003cp\u003eMetrics are available to monitor the number of launching requests (\u003ccode\u003eflowcontrol.launching.count\u003c/code\u003e), running pipelines and jobs (\u003ccode\u003eflowcontrol.running.count\u003c/code\u003e), and rejected runs (\u003ccode\u003eprogram.rejected.runs\u003c/code\u003e).\u003c/p\u003e\n"]]],[],null,["# Cloud Data Fusion flow control overview\n\nA flow control mechanism in Cloud Data Fusion prevents you from submitting\ntoo many requests, which can cause stuck or failed pipeline runs. This mechanism\napplies to start (`Launch`) requests for the following pipelines and jobs in all\neditions of Cloud Data Fusion, versions 6.6 and later:\n\n- Batch pipelines\n- Real-time pipelines\n- Replication jobs\n\nThresholds\n----------\n\nTo control the number of outstanding start requests in Cloud Data Fusion,\nflow control relies on two thresholds:\n\nLaunch threshold\n: Limits the number of launch requests being made. If the\n number of launch requests received by Cloud Data Fusion that are not yet in\n `Running` state is greater than the launch threshold (number of launch requests\n that aren't running yet \\\u003e launch threshold), the request is rejected. The\n number includes batch pipelines, real-time pipelines, and\n replication jobs.\n\nRuns threshold\n: Limits the number of outstanding launch requests in\n the system. If the number of outstanding launch requests received by\n Cloud Data Fusion that have not yet finished is greater than a specified\n runs threshold (number of outstanding requests that aren't finished yet \\\u003e runs\n threshold), the request is rejected.\n\nRejected requests\n-----------------\n\nIf either threshold is met, every new start request gets rejected. For example,\na rejected batch pipeline has a `Rejected` status in the logs, and a dialog in\nthe UI describes why the launch was rejected.\n\nMetrics\n-------\n\nThe number of launching and running pipelines along with the number of rejected\npipelines in the system can be accessed through the metrics service as follows.\n\n### `Launching` metric\n\nReports the number of launching requests in the system. That is, it reports the\nnumber of launch requests that are in `Provisioning` or `Starting` states.\n\nMetrics name: `flowcontrol.launching.count` \n\n POST /v3/metrics/query?metric=system.flowcontrol.launching.count\n\n### `Running` metric\n\nReports the number of running pipelines and jobs in the system. The run\nthreshold is based on the sum of the `Launching` and `Running` metrics values.\n\nMetrics name: `flowcontrol.running.count` \n\n POST /v3/metrics/query?metric=system.flowcontrol.running.count\n\n### `Rejected` metric\n\nReports the number of rejected runs due to the flow control mechanism.\n\nMetrics name: `program.rejected.runs` \n\n POST /v3/metrics/query?metric=system.program.rejected.runs\n\nWhat's next\n-----------\n\n- For examples of providing tags and aggregating the `Rejected` metric for different pipelines, see [CDAP Metrics Microservices](https://cdap.atlassian.net/wiki/spaces/DOCS/pages/477692194/Metrics+Microservices#Querying-a-Metric)."]]
