[
https://issues.apache.org/jira/browse/HDDS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDDS-759:
-------------------------------
Description:
Currently SCM, OM and DN all use {{ozone.metadata.dirs}} for storing metadata.
Looking more closely, it appears that SCM and OM have no option to choose
separate locations. We should provide custom config settings. For most
production clusters, admins will want to carefully choose where they place OM
and SCM metadata, similar to how they choose locations for NN metadata.
To avoid disruption, we can have them fallback to {{ozone.metadata.dirs}}.
was:
Currently SCM, OM and DN all use {{ozone.metadata.dirs}} for storing metadata.
Looking more closely, it appears that SCM and OM have no option to choose
separate locations. We should provide custom config settings.
To avoid disruption, we can have them fallback to {{ozone.metadata.dirs}}.
> Create config settings for SCM and OM DB directories
> ----------------------------------------------------
>
> Key: HDDS-759
> URL: https://issues.apache.org/jira/browse/HDDS-759
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Priority: Major
> Attachments: HDDS-759.01.patch
>
>
> Currently SCM, OM and DN all use {{ozone.metadata.dirs}} for storing
> metadata.
> Looking more closely, it appears that SCM and OM have no option to choose
> separate locations. We should provide custom config settings. For most
> production clusters, admins will want to carefully choose where they place OM
> and SCM metadata, similar to how they choose locations for NN metadata.
> To avoid disruption, we can have them fallback to {{ozone.metadata.dirs}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
