You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Elek, Marton (JIRA)" <ji...@apache.org> on 2018/08/22 15:32:00 UTC

[jira] [Updated] (HDDS-363) Faster datanode registration during the first startup

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

Elek, Marton updated HDDS-363:
------------------------------
    Attachment: HDDS-363.001.patch

> Faster datanode registration during the first startup
> -----------------------------------------------------
>
>                 Key: HDDS-363
>                 URL: https://issues.apache.org/jira/browse/HDDS-363
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: Ozone Datanode
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Minor
>             Fix For: 0.2.1
>
>         Attachments: HDDS-363.001.patch
>
>
> During the first startup usually we need to wait about 30 s to find the scm usable. The datanode registration is a multiple step process (request/response + request/response) and we need to wait the next HB to finish the registration.
> I propose to use a more higher HB frequency at startup (let's say 2 seconds) and set the configured HB only at the end of the registration.
> It also helps for the first users as it could be less confusing (the datanode can be seen almost immediately on the UI)
> Also it would help a lot for me during the testing (yes, I can decrease the HB frequency but in that case it's harder the follow the later HBs)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org