Sorry for the email format isn’t very polished, I’m still learning how to format it properly :P
More usage details can be found in the IoTDB user documentation: - https://iotdb.apache.org/UserGuide/latest/User-Manual/Maintennance.html#region-migration - https://iotdb.apache.org/zh/UserGuide/latest/User-Manual/Maintennance.html#region-%E8%BF%81%E7%A7%BB > 2024年12月10日 15:42，liyuheng <liyuheng55...@126.com> 写道： > > Hello everyone, > I am Li Yuheng, a contributor to the IoTDB community. I am proud to share > with you an exciting feature in IoTDB: Region Migration. > As a distributed database, IoTDB uses regions as the base unit for > distributed data storage. The distribution of regions across the cluster > determines the allocation of write load and disk usage among DataNodes. With > the region migration feature, IoTDB users can flexibly allocate storage > resources within the cluster: > After adding a new DataNode, migrate regions to the new node to balance write > load and disk space. > Before removing an old DataNode, migrate all regions on it to other DataNodes. > The frame for region migration was initially implemented in 2022. This year, > after significant contributions from multiple community members (including > Deng Chao, Hu Xiangpeng, Liu Zhen, Tan Xinyu, and I), we have brought this > feature to a practical and usable state. > Now, region migration has the following characteristics: > Solid stability and performance. > The cluster can continue to handle reads and writes during region migration. > Any issues that interrupt the migration process can be addressed and resolved > without permanent impact. > As of the recently released IoTDB 1.3.3, the region migration feature is > generally available. We are continuing to iterate and optimize it, and even > better performance will be provided in versions 2.0 and 1.3.4. If you have > any feedback, please feel free to share with us. > We look forward to you exploring and enjoying this feature! > Best regards, > Li Yuheng
