BUILD-UNSTABLE: Job 'IoTDB/IoTDB-Pipe/master [master] [624]':
Check console output at "https://ci-builds.apache.org/job/IoTDB/job/IoTDB-Pipe/job/master/624/";>IoTDB/IoTDB-Pipe/master
[master] [624]"
Maybe this function could support query conditions like sg or device. Thus,
users could locate the data. And show storageGroup/devices may link with
regions too.
| |
cmlmakahts
|
|
邮箱：cmlmaka...@126.com
|
回复的原邮件
| 发件人 | 李思佳 |
| 日期 | 2022年06月14日 17:42 |
| 收件人 | dev@iotdb.apache.or
Hi, merged, welcome!
—
Jialin Qiao
Apache IoTDB PMC
王安阳 于2022年6月13日周一 20:42写道：
> First PR to IOTDB, Glad to join the community. Thanks.
>
Hi,
Good point!
We could add a status column, which may contain the following enums:
Up,
Moving to {DataNodeId}
Deleting
Besides, how many slots a region contains may also be helpful:
Status, RegionID, RegionType, Slots, DataNodeID, RPCAddress, RPCPort
There may need to reconsider some concept
That sounds like a nice feature.
By the way, if my region is migrating or not ready, can I see its status?
As you said, can I see which regions are moving when my datanode has changed or
in rebalanced? For example, Region a is moving from node A to node B?
BR,
---
If one region is under migration, what the output will be? Do we need a
state/status field?
在 2022/6/14 17:31，“Jialin Qiao” 写入:
Hi,
I created an issue to query the region distribution [1].
This could be used in some scenarios:
(1) To see if the region migration is successful a
Hi,
I created an issue to query the region distribution [1].
This could be used in some scenarios:
(1) To see if the region migration is successful after removing a datanode
(2) To see if the region is well-distributed in datanodes
The query result could contain 5 columns:
RegionID, RegionType,
