Skip to content

Commit 6881d60

Browse files
authored
Merge pull request #38310 from windsonsea/flowcy
[zh] sync flow-control.md
2 parents 4f57cb6 + 4e2ff40 commit 6881d60

File tree

1 file changed

+43
-106
lines changed

1 file changed

+43
-106
lines changed

content/zh-cn/docs/concepts/cluster-administration/flow-control.md

Lines changed: 43 additions & 106 deletions
Original file line numberDiff line numberDiff line change
@@ -954,42 +954,22 @@ poorly-behaved workloads that may be harming system health.
954954
(该量保存了最后一个窗口中,正在处理的请求数量的高水位线)。
955955

956956
<!--
957-
* `apiserver_flowcontrol_read_vs_write_request_count_samples` is a
958-
histogram vector of observations of the then-current number of
959-
requests, broken down by the labels `phase` (which takes on the
960-
values `waiting` and `executing`) and `request_kind` (which takes on
961-
the values `mutating` and `readOnly`). The observations are made
962-
periodically at a high rate. Each observed value is a ratio,
963-
between 0 and 1, of a number of requests divided by the
964-
corresponding limit on the number of requests (queue length limit
965-
for waiting and concurrency limit for executing).
966-
-->
967-
* `apiserver_flowcontrol_read_vs_write_request_count_samples` 是一个直方图向量,
968-
记录当前请求数量的观察值,
969-
由标签 `phase`(取值为 `waiting``executing`)和 `request_kind`
970-
(取值 `mutating``readOnly`)区分。定期以高速率观察该值。
957+
* `apiserver_flowcontrol_read_vs_write_current_requests` is a
958+
histogram vector of observations, made at the end of every
959+
nanosecond, of the number of requests broken down by the labels
960+
`phase` (which takes on the values `waiting` and `executing`) and
961+
`request_kind` (which takes on the values `mutating` and
962+
`readOnly`). Each observed value is a ratio, between 0 and 1, of a
963+
number of requests divided by the corresponding limit on the number
964+
of requests (queue volume limit for waiting and concurrency limit
965+
for executing).
966+
-->
967+
* `apiserver_flowcontrol_read_vs_write_current_requests` 是一个直方图向量,
968+
在每个纳秒结束时记录请求数量的观察值,由标签 `phase`(取值为 `waiting``executing`
969+
`request_kind`(取值为 `mutating``readOnly`)区分。
971970
每个观察到的值是一个介于 0 和 1 之间的比值,计算方式为请求数除以该请求数的对应限制
972971
(等待的队列长度限制和执行所用的并发限制)。
973972

974-
<!--
975-
* `apiserver_flowcontrol_read_vs_write_request_count_watermarks` is a
976-
histogram vector of high or low water marks of the number of
977-
requests (divided by the corresponding limit to get a ratio in the
978-
range 0 to 1) broken down by the labels `phase` (which takes on the
979-
values `waiting` and `executing`) and `request_kind` (which takes on
980-
the values `mutating` and `readOnly`); the label `mark` takes on
981-
values `high` and `low`. The water marks are accumulated over
982-
windows bounded by the times when an observation was added to
983-
`apiserver_flowcontrol_read_vs_write_request_count_samples`. These
984-
water marks show the range of values that occurred between samples.
985-
-->
986-
* `apiserver_flowcontrol_read_vs_write_request_count_watermarks`
987-
是请求数量的高或低水位线的直方图向量(除以相应的限制,得到介于 0 至 1 的比率),
988-
由标签 `phase`(取值为 `waiting``executing`)和 `request_kind`
989-
(取值为 `mutating``readOnly`)区分;标签 `mark` 取值为 `high``low`
990-
`apiserver_flowcontrol_read_vs_write_request_count_samples` 向量观察到有值新增,
991-
则该向量累积。这些水位线显示了样本值的范围。
992-
993973
<!--
994974
* `apiserver_flowcontrol_current_inqueue_requests` is a gauge vector
995975
holding the instantaneous number of queued (not executing) requests,
@@ -1018,84 +998,41 @@ poorly-behaved workloads that may be harming system health.
1018998
包含占用座位的瞬时数量,由标签 `priority_level``flow_schema` 进一步区分。
1019999

10201000
<!--
1021-
* `apiserver_flowcontrol_priority_level_request_count_samples` is a
1022-
histogram vector of observations of the then-current number of
1023-
requests broken down by the labels `phase` (which takes on the
1024-
values `waiting` and `executing`) and `priority_level`. Each
1025-
histogram gets observations taken periodically, up through the last
1026-
activity of the relevant sort. The observations are made at a high
1027-
rate. Each observed value is a ratio, between 0 and 1, of a number
1028-
of requests divided by the corresponding limit on the number of
1029-
requests (queue length limit for waiting and concurrency limit for
1030-
executing).
1001+
* `apiserver_flowcontrol_priority_level_request_utilization` is a
1002+
histogram vector of observations, made at the end of each
1003+
nanosecond, of the number of requests broken down by the labels
1004+
`phase` (which takes on the values `waiting` and `executing`) and
1005+
`priority_level`. Each observed value is a ratio, between 0 and 1,
1006+
of a number of requests divided by the corresponding limit on the
1007+
number of requests (queue volume limit for waiting and concurrency
1008+
limit for executing).
10311009
-->
1032-
* `apiserver_flowcontrol_priority_level_request_count_samples` 是一个直方图向量,
1033-
记录当前请求的观测值,由标签 `phase`(取值为`waiting``executing`)和
1034-
`priority_level` 进一步区分。
1035-
每个直方图都会定期进行观察,直到相关类别的最后活动为止。观察频率高。
1036-
所观察到的值都是请求数除以相应的请求数限制(等待的队列长度限制和执行的并发限制)的比率,
1037-
介于 0 和 1 之间。
1038-
1039-
<!--
1040-
* `apiserver_flowcontrol_priority_level_request_count_watermarks` is a
1041-
histogram vector of high or low water marks of the number of
1042-
requests (divided by the corresponding limit to get a ratio in the
1043-
range 0 to 1) broken down by the labels `phase` (which takes on the
1044-
values `waiting` and `executing`) and `priority_level`; the label
1045-
`mark` takes on values `high` and `low`. The water marks are
1046-
accumulated over windows bounded by the times when an observation
1047-
was added to
1048-
`apiserver_flowcontrol_priority_level_request_count_samples`. These
1049-
water marks show the range of values that occurred between samples.
1050-
-->
1051-
* `apiserver_flowcontrol_priority_level_request_count_watermarks`
1052-
是请求数量的高或低水位线的直方图向量(除以相应的限制,得到 0 到 1 的范围内的比率),
1053-
由标签 `phase`(取值为 `waiting``executing`)和 `priority_level` 区分;
1054-
标签 `mark` 取值为 `high``low`
1055-
`apiserver_flowcontrol_priority_level_request_count_samples` 向量观察到有值新增,
1056-
则该向量累积。这些水位线显示了样本值的范围。
1057-
1058-
<!--
1059-
* `apiserver_flowcontrol_priority_level_seat_count_samples` is a
1060-
histogram vector of observations of the utilization of a priority
1061-
level's concurrency limit, broken down by `priority_level`. This
1062-
utilization is the fraction (number of seats occupied) /
1063-
(concurrency limit). This metric considers all stages of execution
1064-
(both normal and the extra delay at the end of a write to cover for
1065-
the corresponding notification work) of all requests except WATCHes;
1066-
for those it considers only the initial stage that delivers
1067-
notifications of pre-existing objects. Each histogram in the vector
1068-
is also labeled with `phase: executing` (there is no seat limit for
1069-
the waiting phase). Each histogram gets observations taken
1070-
periodically, up through the last activity of the relevant sort.
1071-
The observations
1072-
are made at a high rate.
1073-
-->
1074-
* `apiserver_flowcontrol_priority_level_seat_count_samples`
1075-
是观察某优先级并发限制利用率的直方图向量,由 `priority_level` 区分。
1010+
* `apiserver_flowcontrol_priority_level_request_utilization` 是一个直方图向量,
1011+
在每个纳秒结束时记录请求数量的观察值,
1012+
由标签 `phase`(取值为 `waiting``executing`)和 `priority_level` 区分。
1013+
每个观察到的值是一个介于 0 和 1 之间的比值,计算方式为请求数除以该请求数的对应限制
1014+
(等待的队列长度限制和执行所用的并发限制)。
1015+
1016+
<!--
1017+
* `apiserver_flowcontrol_priority_level_seat_utilization` is a
1018+
histogram vector of observations, made at the end of each
1019+
nanosecond, of the utilization of a priority level's concurrency
1020+
limit, broken down by `priority_level`. This utilization is the
1021+
fraction (number of seats occupied) / (concurrency limit). This
1022+
metric considers all stages of execution (both normal and the extra
1023+
delay at the end of a write to cover for the corresponding
1024+
notification work) of all requests except WATCHes; for those it
1025+
considers only the initial stage that delivers notifications of
1026+
pre-existing objects. Each histogram in the vector is also labeled
1027+
with `phase: executing` (there is no seat limit for the waiting
1028+
phase).
1029+
-->
1030+
* `apiserver_flowcontrol_priority_level_seat_utilization` 是一个直方图向量,
1031+
在每个纳秒结束时记录某个优先级并发度限制利用率的观察值,由标签 `priority_level` 区分。
10761032
此利用率是一个分数:(占用的席位数)/(并发限制)。
10771033
此指标考虑了除 WATCH 之外的所有请求的所有执行阶段(包括写入结束时的正常延迟和额外延迟,
10781034
以覆盖相应的通知操作);对于 WATCH 请求,只考虑传递预先存在对象通知的初始阶段。
10791035
该向量中的每个直方图也带有 `phase: executing`(等待阶段没有席位限制)的标签。
1080-
每个直方图都会定期获取观察值,遍历至相关类别的最后一个活动。观测值的生成速率很高。
1081-
1082-
<!--
1083-
* `apiserver_flowcontrol_priority_level_seat_count_watermarks` is a
1084-
histogram vector of high or low water marks of the utilization of a
1085-
priority level's concurrency limit, broken down by `priority_level`
1086-
and `mark` (which takes on values `high` and `low`). Each histogram
1087-
in the vector is also labeled with `phase: executing` (there is no
1088-
seat limit for the waiting phase). The water marks are accumulated
1089-
over windows bounded by the times when an observation was added to
1090-
`apiserver_flowcontrol_priority_level_seat_count_samples`. These
1091-
water marks show the range of values that occurred between samples.
1092-
-->
1093-
* `apiserver_flowcontrol_priority_level_seat_count_watermarks`
1094-
是优先级并发限制利用率的高或低水位线的直方图向量,由 `priority_level``mark`
1095-
(取值为 `high``low`)区分。向量中的每个直方图也带有 `phase: executing`
1096-
(等待阶段没有席位限制)的标签。当观察值被添加到
1097-
`apiserver_flowcontrol_priority_level_seat_count_samples` 时,
1098-
水位线在以时间为界的窗口上累加。这些水位线表明了样本之间出现的值的范围。
10991036

11001037
<!--
11011038
* `apiserver_flowcontrol_request_queue_length_after_enqueue` is a

0 commit comments

Comments
 (0)