[jira] [Updated] (HDDS-329) Ozone: dozone: auto-bootstrap SCM/KSM in containerized environment

["Ethan Rose (Jira)" <ji...@apache.org>]

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

Ethan Rose updated HDDS-329:
----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> Ozone: dozone: auto-bootstrap SCM/KSM in containerized environment
> ------------------------------------------------------------------
>
>                 Key: HDDS-329
>                 URL: https://issues.apache.org/jira/browse/HDDS-329
>             Project: Apache Ozone
>          Issue Type: New Feature
>          Components: Ozone Manager, SCM
>            Reporter: Marton Elek
>            Priority: Major
>
> Currently to start SCM and KSM in a new environment we need to:
>  1. Initialize scm (/hdfs scm -init)
>  2. Start scm
>  3. hdfs ksm -createObjectStore (connects to the scm, scm should be running)
>  4. Start ksm
> The problematic part is step 3.) as in a containerized environment (docker-compose/kubernetes) the timing couldn't be guaranteed.
> I propose to introduce a new command line flag '--auto-bootstrap' for both KSM and SCM (and maybe for Namenode in the future).
> It will:
>   1. Initilize KSM and SCM *if and only if* the data directories are missing
>   2. In case of KSM retry the initilization in every 10 seconds (in case of SCM is not yet running) in case of connection failure



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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