Skip to content

Maintenance-commands_timecho.md

Latest commit

 

History

History
713 lines (522 loc) · 21.8 KB

Maintenance-commands_timecho.md

File metadata and controls

713 lines (522 loc) · 21.8 KB
Raw

Maintenance Statement

1. Status Checking

1.1 Viewing the Connected Model

Description: Returns the current SQL dialect model (Tree or Table).

Syntax:

showCurrentSqlDialectStatement
    : SHOW CURRENT_SQL_DIALECT
    ;

Example:

IoTDB> SHOW CURRENT_SQL_DIALECT;

Result：

+-----------------+
|CurrentSqlDialect|
+-----------------+
|            TABLE|
+-----------------+

1.2 Viewing the Logged-in Username

Description: Returns the currently logged-in username.

Syntax:

showCurrentUserStatement
    : SHOW CURRENT_USER
    ;

Example:

IoTDB> SHOW CURRENT_USER;

Result:

+-----------+
|CurrentUser|
+-----------+
|       root|
+-----------+

1.3 Viewing the Connected Database Name

Description: Returns the name of the currently connected database. If no USE statement has been executed, it returns null.

Syntax:

showCurrentDatabaseStatement
    : SHOW CURRENT_DATABASE
    ;

Example:

IoTDB> SHOW CURRENT_DATABASE;
IoTDB> USE test;
IoTDB> SHOW CURRENT_DATABASE;

Result:

+---------------+
|CurrentDatabase|
+---------------+
|           null|
+---------------+
+---------------+
|CurrentDatabase|
+---------------+
|           test|
+---------------+

1.4 Viewing the Cluster Version

Description: Returns the current cluster version.

Syntax:

showVersionStatement
    : SHOW VERSION
    ;

Example:

IoTDB> SHOW VERSION;

Result:

+-------+---------+
|Version|BuildInfo|
+-------+---------+
|2.0.1.2|  1ca4008|
+-------+---------+

1.5 Viewing Cluster Key Parameters

Description: Returns key parameters of the current cluster.

Syntax:

showVariablesStatement
    : SHOW VARIABLES
    ;

Key Parameters:

  1. ClusterName: The name of the current cluster.
  2. DataReplicationFactor: Number of data replicas per DataRegion.
  3. SchemaReplicationFactor: Number of schema replicas per SchemaRegion.
  4. DataRegionConsensusProtocolClass: Consensus protocol class for DataRegions.
  5. SchemaRegionConsensusProtocolClass: Consensus protocol class for SchemaRegions.
  6. ConfigNodeConsensusProtocolClass: Consensus protocol class for ConfigNodes.
  7. TimePartitionOrigin: The starting timestamp of database time partitions.
  8. TimePartitionInterval: The interval of database time partitions (in milliseconds).
  9. ReadConsistencyLevel: The consistency level for read operations.
  10. SchemaRegionPerDataNode: Number of SchemaRegions per DataNode.
  11. DataRegionPerDataNode: Number of DataRegions per DataNode.
  12. SeriesSlotNum: Number of SeriesSlots per DataRegion.
  13. SeriesSlotExecutorClass: Implementation class for SeriesSlots.
  14. DiskSpaceWarningThreshold: Disk space warning threshold (in percentage).
  15. TimestampPrecision: Timestamp precision.

Example:

IoTDB> SHOW VARIABLES;

Result:

+----------------------------------+-----------------------------------------------------------------+
|                          Variable|                                                            Value|
+----------------------------------+-----------------------------------------------------------------+
|                       ClusterName|                                                   defaultCluster|
|             DataReplicationFactor|                                                                1|
|           SchemaReplicationFactor|                                                                1|
|  DataRegionConsensusProtocolClass|                      org.apache.iotdb.consensus.iot.IoTConsensus|
|SchemaRegionConsensusProtocolClass|                  org.apache.iotdb.consensus.ratis.RatisConsensus|
|  ConfigNodeConsensusProtocolClass|                  org.apache.iotdb.consensus.ratis.RatisConsensus|
|               TimePartitionOrigin|                                                                0|
|             TimePartitionInterval|                                                        604800000|
|              ReadConsistencyLevel|                                                           strong|
|           SchemaRegionPerDataNode|                                                                1|
|             DataRegionPerDataNode|                                                                0|
|                     SeriesSlotNum|                                                             1000|
|           SeriesSlotExecutorClass|org.apache.iotdb.commons.partition.executor.hash.BKDRHashExecutor|
|         DiskSpaceWarningThreshold|                                                             0.05|
|                TimestampPrecision|                                                               ms|
+----------------------------------+-----------------------------------------------------------------+

1.6 Viewing the Cluster ID

Description: Returns the ID of the current cluster.

Syntax:

showClusterIdStatement
    : SHOW (CLUSTERID | CLUSTER_ID)
    ;

Example:

IoTDB> SHOW CLUSTER_ID;

Result:

+------------------------------------+
|                           ClusterId|
+------------------------------------+
|40163007-9ec1-4455-aa36-8055d740fcda|
+------------------------------------+

1.7 Viewing the Timestamp of the Connected DataNode

Description: Returns the current timestamp of the DataNode process directly connected to the client.

Syntax:

showCurrentTimestampStatement
    : SHOW CURRENT_TIMESTAMP
    ;

Example:

IoTDB> SHOW CURRENT_TIMESTAMP;

Result:

+-----------------------------+
|             CurrentTimestamp|
+-----------------------------+
|2025-02-17T11:11:52.987+08:00|
+-----------------------------+

1.8 Viewing Executing Queries

Description: Displays information about all currently executing queries.

For more details on how to use system tables, please refer to System Tables

Syntax:

showQueriesStatement
    : SHOW (QUERIES | QUERY PROCESSLIST)
        (WHERE where=booleanExpression)?
        (ORDER BY sortItem (',' sortItem)*)?
        limitOffsetClause
    ;

Parameters:

  1. WHERE Clause: Filters the result set based on specified conditions.
  2. ORDER BY Clause: Sorts the result set based on specified columns.
  3. limitOffsetClause: Limits the number of rows returned.
    1. Format: LIMIT <offset>, <row_count>.

Columns in QUERIES Table:

  • query_id: Unique ID of the query.
  • start_time: Timestamp when the query started.
  • datanode_id: ID of the DataNode executing the query.
  • elapsed_time: Time elapsed since the query started (in seconds).
  • statement: The SQL statement being executed.
  • user: The user who initiated the query.

Example:

IoTDB> SHOW QUERIES WHERE elapsed_time > 30;

Result:

+-----------------------+-----------------------------+-----------+------------+------------+----+
|               query_id|                   start_time|datanode_id|elapsed_time|   statement|user|
+-----------------------+-----------------------------+-----------+------------+------------+----+
|20250108_101015_00000_1|2025-01-08T18:10:15.935+08:00|          1|      32.283|show queries|root|
+-----------------------+-----------------------------+-----------+------------+------------+----+

1.9 Viewing Region Information

Description: Displays regions' information of the current cluster.

Syntax:

showRegionsStatement
    : SHOW REGIONS
    ;

Example:

IoTDB> SHOW REGIONS

Result:

+--------+------------+-------+----------+-------------+-----------+----------+----------+-------+---------------+------+-----------------------+----------+
|RegionId|        Type| Status|  Database|SeriesSlotNum|TimeSlotNum|DataNodeId|RpcAddress|RpcPort|InternalAddress|  Role|             CreateTime|TsFileSize|
+--------+------------+-------+----------+-------------+-----------+----------+----------+-------+---------------+------+-----------------------+----------+
|       6|SchemaRegion|Running|tcollector|          670|          0|         1|   0.0.0.0|   6667|      127.0.0.1|Leader|2025-08-01T17:37:01.194|          |
|       7|  DataRegion|Running|tcollector|          335|        335|         1|   0.0.0.0|   6667|      127.0.0.1|Leader|2025-08-01T17:37:01.196| 169.85 KB|
|       8|  DataRegion|Running|tcollector|          335|        335|         1|   0.0.0.0|   6667|      127.0.0.1|Leader|2025-08-01T17:37:01.198| 161.63 KB|
+--------+------------+-------+----------+-------------+-----------+----------+----------+-------+---------------+------+-----------------------+----------+

1.10 Viewing Available Nodes

Description: Returns the RPC addresses and ports of all available DataNodes in the current cluster. Note: A DataNode is considered "available" if it is not in the REMOVING state.

This feature is supported starting from v2.0.8.

Syntax:

showAvailableUrlsStatement
    : SHOW AVAILABLE URLS
    ;

Example:

IoTDB> SHOW AVAILABLE URLS

Result:

+----------+-------+
|RpcAddress|RpcPort|
+----------+-------+
|   0.0.0.0|   6667|
+----------+-------+

1.11 View Service Information

Description: Returns service information (MQTT service, REST service) on all active DataNodes (in RUNNING or READ-ONLY state) in the current cluster.

Supported since V2.0.8.2

Syntax:

showServicesStatement
    : SHOW SERVICES <ON dataNodeId>
    ;

Examples:

IoTDB> SHOW SERVICES
IoTDB> SHOW SERVICES ON 1

Execution result:

+--------------+-------------+---------+
| Service Name | DataNode ID | State   |
+--------------+-------------+---------+
| MQTT         | 1           | STOPPED |
| REST         | 1           | RUNNING |
+--------------+-------------+---------+

2. Status Setting

2.1 Setting the Connected Model

Description: Sets the current SQL dialect model to Tree or Table which can be used in both tree and table models.

Syntax:

SET SQL_DIALECT = (TABLE | TREE);

Example:

IoTDB> SET SQL_DIALECT=TABLE;
IoTDB> SHOW CURRENT_SQL_DIALECT;

Result:

+-----------------+
|CurrentSqlDialect|
+-----------------+
|            TABLE|
+-----------------+

2.2 Updating Configuration Items

Description: Updates configuration items. Changes take effect immediately without restarting if the items support hot modification.

Syntax:

setConfigurationStatement
    : SET CONFIGURATION propertyAssignments (ON INTEGER_VALUE)?
    ;

propertyAssignments
    : property (',' property)*
    ;
    
property
    : identifier EQ propertyValue
    ;

propertyValue
    : DEFAULT
    | expression
    ;

Parameters:

  1. propertyAssignments: A list of properties to update.
    1. Format: property (',' property)*.
    2. Values:
      • DEFAULT: Resets the configuration to its default value.
      • expression: A specific value (must be a string).
  2. ON INTEGER_VALUE (Optional): Specifies the node ID to update.
    1. If not specified or set to a negative value, updates all ConfigNodes and DataNodes.

Example:

IoTDB> SET CONFIGURATION disk_space_warning_threshold='0.05',heartbeat_interval_in_ms='1000' ON 1;

2.3 Loading Manually Modified Configuration Files

Description: Loads manually modified configuration files and hot-loads the changes. Configuration items that support hot modification take effect immediately.

Syntax:

loadConfigurationStatement
    : LOAD CONFIGURATION localOrClusterMode?
    ;
    
localOrClusterMode
    : (ON (LOCAL | CLUSTER))
    ;

Parameters:

  1. localOrClusterMode (Optional):
    1. Specifies the scope of configuration loading.
    2. Default: CLUSTER.
    3. Values:
      • LOCAL: Loads configuration only on the DataNode directly connected to the client.
      • CLUSTER: Loads configuration on all DataNodes in the cluster.

Example:

IoTDB> LOAD CONFIGURATION ON LOCAL;

2.4 Setting the System Status

Description: Sets the system status to either READONLY or RUNNING.

Syntax:

setSystemStatusStatement
    : SET SYSTEM TO (READONLY | RUNNING) localOrClusterMode?
    ;    
    
localOrClusterMode
    : (ON (LOCAL | CLUSTER))
    ;

Parameters:

  1. RUNNING | READONLY:
    1. RUNNING: Sets the system to running mode, allowing both read and write operations.
    2. READONLY: Sets the system to read-only mode, allowing only read operations and prohibiting writes.
  2. localOrClusterMode (Optional):
    1. LOCAL: Applies the status change only to the DataNode directly connected to the client.
    2. CLUSTER: Applies the status change to all DataNodes in the cluster.
    3. Default: ON CLUSTER.

Example:

IoTDB> SET SYSTEM TO READONLY ON CLUSTER;

3. Data Management

3.1 Flushing Data from Memory to Disk

Description: Flushes data from the memory table to disk.

Syntax:

flushStatement
    : FLUSH identifier? (',' identifier)* booleanValue? localOrClusterMode?
    ;

booleanValue
    : TRUE | FALSE
    ;

localOrClusterMode
    : (ON (LOCAL | CLUSTER))
    ;

Parameters:

  1. identifier (Optional):
    1. Specifies the name of the database to flush.
    2. If not specified, all databases are flushed.
    3. Multiple Databases: Multiple database names can be specified, separated by commas (e.g., FLUSH test_db1, test_db2).
  2. booleanValue (Optional):
    1. Specifies the type of data to flush.
    2. TRUE: Flushes only the sequential memory table.
    3. FALSE: Flushes only the unsequential MemTable.
    4. Default: Flushes both sequential and unsequential memory tables.
  3. localOrClusterMode (Optional):
    1. ON LOCAL: Flushes only the memory tables on the DataNode directly connected to the client.
    2. ON CLUSTER: Flushes memory tables on all DataNodes in the cluster.
    3. Default: ON CLUSTER.

Example:

IoTDB> FLUSH test_db TRUE ON LOCAL;

4. Data Repair

4.1 Starting Background Scan and Repair of TsFiles

Description: Starts a background task to scan and repair TsFiles, fixing issues such as timestamp disorder within data files.

Syntax:

startRepairDataStatement
    : START REPAIR DATA localOrClusterMode?
    ;
    
localOrClusterMode
    : (ON (LOCAL | CLUSTER))
    ;

Parameters:

  1. localOrClusterMode（Optional）:
    1. ON LOCAL: Executes the repair task only on the DataNode directly connected to the client.
    2. ON CLUSTER: Executes the repair task on all DataNodes in the cluster.
    3. Default: ON CLUSTER.

Example:

IoTDB> START REPAIR DATA ON CLUSTER;

4.2 Pausing Background TsFile Repair Task

Description: Pauses the background repair task. The paused task can be resumed by executing the START REPAIR DATA command again.

Syntax:

stopRepairDataStatement
    : STOP REPAIR DATA localOrClusterMode?
    ;
    
localOrClusterMode
    : (ON (LOCAL | CLUSTER))
    ;

Parameters:

  1. localOrClusterMode (Optional):
    1. ON LOCAL: Executes the pause command only on the DataNode directly connected to the client.
    2. ON CLUSTER: Executes the pause command on all DataNodes in the cluster.
    3. Default: ON CLUSTER.

Example:

IoTDB> STOP REPAIR DATA ON CLUSTER;

5. Query Termination

5.1 Terminating Queries

Description: Terminates one or more running queries.

Syntax:

killQueryStatement
    : KILL (QUERY queryId=string | ALL QUERIES)
    ;

Parameters:

  1. QUERY queryId: Specifies the ID of the query to terminate.
  • To obtain the queryId, use the SHOW QUERIES command.
  1. ALL QUERIES: Terminates all currently running queries.

Example:

Terminate a specific query:

IoTDB> KILL QUERY 20250108_101015_00000_1;

Terminate all queries:

IoTDB> KILL ALL QUERIES;

6. Query Debugging

6.1 DEBUG SQL

Definition: Add the DEBUG keyword at the beginning of an SQL query statement. During execution, debug logs will be output, including the underlying file scan information involved in the query.

Supported since V2.0.9

Syntax:

debugSQLStatement
    : DEBUG ? query
    ;

Description:

  • Log output path: logs/log_datanode_query_debug.log

Example:

  1. Execute the following SQL for DEBUG query
DEBUG SELECT * FROM table3;
  1. Check the log content in log_datanode_query_debug.log to view the file scan information involved in the query.
2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2864/1769139940009-1-0-0.tsfile is not satisfied because of no device! 
2026-03-24 10:10:41,515 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.d.t.TsFileResource:1098 - Path: table3.d1 file /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2865/1769139940010-1-0-0.tsfile is not satisfied because of no device! 
2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.b.TimeSeriesMetadataCache:159 - Cache miss: table3.d1. in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile 
2026-03-24 10:10:41,516 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.b.TimeSeriesMetadataCache:160 - Device: table3.d1, all sensors: [, temperature] 
2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.b.BloomFilterCache:110 - get bloomFilter from cache where filePath is: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile 
2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1.  metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile  from cache: TimeseriesMetadata{timeSeriesMetadataType=-128, chunkMetaDataListDataSize=8, measurementId='', dataType=VECTOR, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2, modified=false, isSeq=true, chunkMetadataList=[measurementId: , datatype: VECTOR, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2, deleteIntervalList: null]}. 
2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.b.TimeSeriesMetadataCache:227 - Get timeseries: table3.d1.temperature  metadata in file: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile  from cache: TimeseriesMetadata{timeSeriesMetadataType=64, chunkMetaDataListDataSize=8, measurementId='temperature', dataType=FLOAT, statistics=startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], modified=false, isSeq=true, chunkMetadataList=[measurementId: temperature, datatype: FLOAT, version: 0, Statistics: startTime: 1747065600001 endTime: 1747065601002 count: 2 [minValue:85.0,maxValue:90.0,firstValue:90.0,lastValue:85.0,sumValue:175.0], deleteIntervalList: null]}. 
2026-03-24 10:10:41,517 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:110 - Modifications size is 1 for file Path: /home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile  
2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:114 - [] 
2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:125 - After modification Chunk meta data list is:  
2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.d.r.r.c.m.DiskAlignedChunkMetadataLoader:126 - org.apache.tsfile.file.metadata.TableDeviceChunkMetadata@2e11291f 
2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=19} 
2026-03-24 10:10:41,518 [Query-Worker-Thread-0$20260324_021041_00068_1.1.0.0] INFO  o.a.i.d.s.b.ChunkCache:167 - get chunk from cache whose key is: ChunkCacheKey{filePath='/home/iotdb/timechodb/data/datanode/data/sequence/database1/4/2888/1774247880109-1-0-0.tsfile', regionId=4, timePartitionId=2888, tsFileVersion=1, compactionVersion=0, offsetOfChunkHeader=46} 
2026-03-24 10:10:41,519 [pool-69-IoTDB-ClientRPC-Processor-1$20260324_021041_00068_1] INFO  o.a.i.d.q.p.Coordinator:902 - debug select * from table3