changxue created IOTDB-5019: ------------------------------- Summary: [write]data region leader write less file after restarting datanode on it Key: IOTDB-5019 URL: https://issues.apache.org/jira/browse/IOTDB-5019 Project: Apache IoTDB Issue Type: Bug Reporter: changxue Assignee: Jinrui Zhang Attachments: image-2022-11-22-16-30-27-046.png
[write]data region leader write less file after restarting datanode on it environment: 3C3D cluster, Nov. 21 reproduction: 1. Using iotdb-benchmarks write data to iotdb cluster for more than 6 hours, only 1 device 1 sensor with double values. 2 replicas. 2. The 46 node failed to writing data, so I restart data node of it, and it's the data region leader 3. Continue writing data to the same timeseries for about 8 hours. I find that most of data lay on 44 node show regions(2 replicas): |RegionId|Type|Status|Database|SeriesSlotId|TimeSlotId|DataNodeId|Host|RpcPort|Role| |10|SchemaRegion|Running|root.aggr.g_0|1|0|1|172.20.70.44|6667|Follower| |10|SchemaRegion|Running|root.aggr.g_0|1|0|5|172.20.70.46|6667|Leader| |11|DataRegion|Running|root.aggr.g_0|1|10|1|172.20.70.44|6667|Follower| |11|DataRegion|Running|root.aggr.g_0|1|10|5|172.20.70.46|6667|Leader| iotdb-1: 44 iotdb-2: 45 iotdb-3: 46 files: {code} atmos@i-rh6m726k root.aggr.g_0]$ ansible allnodes -m shell -a "find $IOTDB_HOME/data/datanode/data/sequence/root.aggr.g_0 -type f |wc -l" iotdb-1 | CHANGED | rc=0 >> 1694 iotdb-2 | CHANGED | rc=0 >> 966 iotdb-3 | CHANGED | rc=0 >> 183 {code} monitor: !image-2022-11-22-16-30-27-046.png|thumbnail! -- This message was sent by Atlassian Jira (v8.20.10#820010)