[
https://issues.apache.org/jira/browse/HDDS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton moved HDFS-13203 to HDDS-329:
------------------------------------------
Affects Version/s: (was: 3.1.0)
Target Version/s: (was: HDFS-7240)
Component/s: (was: HDFS-7240)
SCM
Ozone Manager
Workflow: patch-available, re-open possible (was:
no-reopen-closed, patch-avail)
Key: HDDS-329 (was: HDFS-13203)
Project: Hadoop Distributed Data Store (was: Hadoop HDFS)
> Ozone: dozone: auto-bootstrap SCM/KSM in containerized environment
> ------------------------------------------------------------------
>
> Key: HDDS-329
> URL: https://issues.apache.org/jira/browse/HDDS-329
> Project: Hadoop Distributed Data Store
> Issue Type: New Feature
> Components: Ozone Manager, SCM
> Reporter: Elek, Marton
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
