You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@iotdb.apache.org by "Yongzao Dan (Jira)" <ji...@apache.org> on 2023/03/06 08:12:00 UTC

[jira] [Reopened] (IOTDB-5385) Optimize the DataRegion leader calculation policy when ConfigNode leader changes

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

Yongzao Dan reopened IOTDB-5385:
--------------------------------

> Optimize the DataRegion leader calculation policy when ConfigNode leader changes
> --------------------------------------------------------------------------------
>
>                 Key: IOTDB-5385
>                 URL: https://issues.apache.org/jira/browse/IOTDB-5385
>             Project: Apache IoTDB
>          Issue Type: Improvement
>            Reporter: Jinrui Zhang
>            Assignee: Yongzao Dan
>            Priority: Major
>
> We found a phenomenon in recent testing.
> That is, the leaders of DataRegions will be updated by new elected ConfigNode leader.  It adds unstable risks to our system sometimes and it will be optimized.
> See this doc for detials. https://apache-iotdb.feishu.cn/docx/ZTlkdiPwRoXGi0xs2cacYpSlnYb?from=space_persnoal_filelist&pre_pathname=%2Fdrive%2Ffolder%2Ffldcnf4szpemAst96rw3XajU5jb



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