Last updated on
backend_tablets
Overview
View the information of talbet on Backends.(added by doris 3.0.7)
Database
information_schema
Table Information
| Column Name | Type | Description |
|---|---|---|
| BE_ID | bigint | The ID of the Backend |
| TABLET_ID | bigint | The ID of the Tablet |
| REPLICA_ID | bigint | The ID of the replica |
| PARTITION_ID | bigint | The ID of the partition |
| TABLET_PATH | varchar(256) | The Path of the tablet |
| TABLET_LOCAL_SIZE | bigint | The Size of the tablet on local |
| TABLET_REMOTE_SIZE | bigint | The Size of the tablet on remote |
| VERSION_COUNT | bigint | The number of version |
| SEGMENT_COUNT | bigint | The size of segment |
| NUM_COLUMNS | bigint | The number of columns |
| ROW_SIZE | bigint | The size of row |
| COMPACTION_SCORE | int | Compaction Score |
| COMPRESS_KIND | varchar(256) | The Kind of Compression |
| IS_USED | bool | Is the tablet datadir opened |
| IS_ALTER_FAILED | bool | Whether the alter operate failed |
| CREATE_TIME | datetime | Tablet Create Time |
| UPDATE_TIME | datetime | Last Tablet Writted Time |
| IS_OVERLAP | bool | Whether tablets overlap |
Data size semantics in compute-storage decoupled mode
This table is reported directly by the BE. TABLET_LOCAL_SIZE and TABLET_REMOTE_SIZE are split by where the rowsets actually live: rowsets stored in remote storage are counted into TABLET_REMOTE_SIZE. In compute-storage decoupled mode data lives in remote storage, so the data size shows up in TABLET_REMOTE_SIZE.
Starting from version 4.0.8, SHOW TABLETS and information_schema.partitions are aligned with this table: in decoupled mode, data size is consistently reported as remote size. Before 4.0.8, the three could contradict each other.