You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "QiangShaowei (Jira)" <ji...@apache.org> on 2022/09/30 07:57:00 UTC

[jira] [Assigned] (IOTDB-4566) If a DataNode is down, then remove other DataNode may failed

     [ https://issues.apache.org/jira/browse/IOTDB-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

QiangShaowei reassigned IOTDB-4566:
-----------------------------------

    Assignee: QiangShaowei

> If a DataNode is down, then remove other DataNode may failed
> ------------------------------------------------------------
>
>                 Key: IOTDB-4566
>                 URL: https://issues.apache.org/jira/browse/IOTDB-4566
>             Project: Apache IoTDB
>          Issue Type: Improvement
>          Components: Core/Cluster
>            Reporter: QiangShaowei
>            Assignee: QiangShaowei
>            Priority: Major
>
> In the current logic, if remove a DataNode X,  we will exec regions migrate on DataNode  Y or DataNode  Z,   (X, Y, Z has  same region replica) 
> But before  move DataNode X, if DataNode Y or DataNode Z  is down,  maybe ConfigNode will  send regioin migrate task to the down node,  will cause remove DataNode X failed.
> {*}solution{*}:  filter online DataNode to exec region migrate



--
This message was sent by Atlassian Jira
(v8.20.10#820010)