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 2022/06/19 01:44:00 UTC

[jira] [Commented] (IOTDB-3528) Filter DataNode which may not be ready in ConfigNode

    [ https://issues.apache.org/jira/browse/IOTDB-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556021#comment-17556021 ] 

Yongzao Dan commented on IOTDB-3528:
------------------------------------

This issue should be fixed by IOTDB-3509 and IOTDB-3510

> Filter DataNode which may not be ready in ConfigNode
> ----------------------------------------------------
>
>                 Key: IOTDB-3528
>                 URL: https://issues.apache.org/jira/browse/IOTDB-3528
>             Project: Apache IoTDB
>          Issue Type: Improvement
>            Reporter: Yuan Tian
>            Assignee: Yongzao Dan
>            Priority: Major
>
> If data structure in DataNode A has not been initialized，but it has registered itself into ConfigNode，and meanwhile its Internal RPC Service has been set up. At this time if someone send request through another DataNode B，then the request is dispatched to DataNode A，it will cause NPE.
> So we should filter dataNodes which may not be ready in ConfigNode



--
This message was sent by Atlassian Jira
(v8.20.7#820007)