translate hive doc article to english #14333
Conversation
| ⚪ |
✅ Documentation buildRevision built successfully |
| ⚪ |
| ⚪ Test history | Ya make output | Test bloat
🟢 |
| ⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
github-actions bot added documentation 
Co-authored-by: Ivan Blinkov <ivan@blinkov.ru>
| ⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
| ⚪ Test history | Ya make output | Test bloat
🟢 |
ydb/docs/en/core/contributor/hive.md Outdated
| | ||
| To distribute tablets across nodes, Hive takes resource usage into account. For each tablet, the usage of four types of resources is tracked: | ||
| | ||
| 1. *CPU* — processor consumption, calculated as the number of microseconds spent on tablet work in the last second and converted to fractions of a core for visualization. |
There was a problem hiding this comment.
Converted to fractions of a core -- не понятно. Может сказать, что one second corresponds to 100% load of a single core?
ydb/docs/en/core/contributor/hive.md Outdated
| 3. *Network* — the amount of traffic generated by the tablet. | ||
| 4. *Counter* — a fake resource used to implement even distribution of tablets. If a tablet has a nonzero consumption of any other resource, its Counter value is 0; otherwise, it is 1. This way, Counter is used for any tablets for which there is no data on real consumption, as well as for tablets where real consumption tracking is disabled. By default, this applies only to [columnar tables](../concepts/datamodel/table.md#column-oriented-tables). | ||
| | ||
| Additionally, to determine overloaded nodes, metrics of resource usage for the node as a whole are used: memory consumption and processor resources in the actor system thread pools. These values are converted into a relative value (a number from 0 to 1), and their maximum is used as the node's overall resource consumption value—*Node usage*. Hive also applies aggregation over a window to all metrics to account for load spikes. |
There was a problem hiding this comment.
| Additionally, to determine overloaded nodes, metrics of resource usage for the node as a whole are used: memory consumption and processor resources in the actor system thread pools. These values are converted into a relative value (a number from 0 to 1), and their maximum is used as the node's overall resource consumption value—*Node usage*. Hive also applies aggregation over a window to all metrics to account for load spikes. | |
| Additionally, to determine overloaded nodes, YDB uses memory consumption and processor resources in the actor system thread pools on each node. These values are converted into relative values (a number from 0 to 1). The sum of these relative values is used as the node's overall resource consumption value — *Node usage*. Hive also applies aggregation over a window to all metrics to account for load spikes. |
ydb/docs/en/core/contributor/hive.md Outdated
| | ||
| The creation and deletion of tablets is initiated by the [SchemeShard](../concepts/glossary.md#scheme-shard) tablet. When a tablet is created, Hive assigns it a unique TabletId, fills in [TabletStorageInfo](general-schema.md#history), selects the most suitable node, and sends a command to start the tablet on that node. In some abnormal situations, a tablet may interrupt its operation, in which case the node on which it was running sends a message to Hive. Hive also assumes that if the connection with a certain node is lost, the tablets running on it have stopped. In such cases, Hive restarts the tablets on other nodes, increasing the generation. | ||
| | ||
| In a {{ ydb-short-name }} cluster, there is a root Hive responsible for the [system tablets](../concepts/glossary.md#tablet-types) of all databases in the cluster. The Hive of a specific database, in turn, is responsible for the tablets servicing the user load of that database. All nodes in the cluster are registered in the root Hive, while only the compute nodes of a specific database are registered in that database's Hive. When a node registers, it informs Hive of the types of tablets and the number of tablets that can be run on it. |
There was a problem hiding this comment.
Попробовал разбить на 2 пункта:
A {{ ydb-short-name }} cluster runs multiple Hives:
- A single root Hive is responsible for the system tablets of all databases in the cluster. All nodes in the cluster are registered in the root Hive.
- A database Hive (one per database) is responsible for the tablets servicing the user load of a specific database. Only the compute nodes of a specific database are registered in that database Hive.
When a new node registers, it informs [какой именно??] Hive of the types of tablets and the number of tablets that can be run on it.
ydb/docs/en/core/contributor/hive.md Outdated
| 1. *CPU* — processor consumption, calculated as the number of microseconds spent on tablet work in the last second and converted to fractions of a core for visualization. | ||
| 2. *Memory* — the amount of RAM consumed by the tablet. | ||
| 3. *Network* — the amount of traffic generated by the tablet. | ||
| 4. *Counter* — a fake resource used to implement even distribution of tablets. If a tablet has a nonzero consumption of any other resource, its Counter value is 0; otherwise, it is 1. This way, Counter is used for any tablets for which there is no data on real consumption, as well as for tablets where real consumption tracking is disabled. By default, this applies only to [columnar tables](../concepts/datamodel/table.md#column-oriented-tables). |
There was a problem hiding this comment.
| 4. *Counter* — a fake resource used to implement even distribution of tablets. If a tablet has a nonzero consumption of any other resource, its Counter value is 0; otherwise, it is 1. This way, Counter is used for any tablets for which there is no data on real consumption, as well as for tablets where real consumption tracking is disabled. By default, this applies only to [columnar tables](../concepts/datamodel/table.md#column-oriented-tables). | |
| 4. *Counter* — a fake resource used to implement even distribution of tablets. If a tablet has a nonzero consumption of any other resource, its Counter value is 0; otherwise, it is 1. This way, Counter is used for any tablets for which there is no data on CPU, memory, and network consumption. This resource type is also used for tablets, in which resource consumption tracking is disabled. By default, this applies only to [column-oriented tables](../concepts/datamodel/table.md#column-oriented-tables). |
Co-authored-by: anton-bobkov <anton-bobkov@ydb.tech>
| ⚪ Test history | Ya make output | Test bloat
🟢 |
| ⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
Co-authored-by: anton-bobkov <anton-bobkov@ydb.tech>
| ⚪ Test history | Ya make output | Test bloat
🟢 |
| ⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
❌ Documentation buildRevision build failed Build logsErrors (1)❌ /en/contributor/hive.md: 14: MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "* A single root Hive respons..."] |
| ⚪ Test history | Ya make output | Test bloat
🟢 |
| ⚪ Test history | Ya make output | Test bloat
🟢 |
| ⚪ Test history | Ya make output | Test bloat
🟢 |
| ⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
Co-authored-by: Ivan Blinkov <ivan@ydb.tech> Co-authored-by: anton-bobkov <anton-bobkov@ydb.tech>
Co-authored-by: Ivan Blinkov <ivan@ydb.tech> Co-authored-by: anton-bobkov <anton-bobkov@ydb.tech>
4 participants
Changelog entry
...
Changelog category
Additional information
...