You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "mingchao zhao (Jira)" <ji...@apache.org> on 2020/05/11 02:48:00 UTC
[jira] [Updated] (HDDS-3563) Make /s3v volume configurable instead
of constant.
[ https://issues.apache.org/jira/browse/HDDS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
mingchao zhao updated HDDS-3563:
--------------------------------
Description:
HDDS-3385 has a big change to s3g for creating buckets. At present, the volume is fixed as s3v. This should be user-configurable to better accommodate the older cluster (0.5).
Our production cluster will encounter the problem that the old volume could not find after rebase master. So we are very eager to solve this problem.
was:HDDS-3385 has a big change to s3g for creating buckets. At present, the volume is fixed as s3v. This should be user-configurable to better accommodate the older cluster (0.5).
> Make /s3v volume configurable instead of constant.
> ---------------------------------------------------
>
> Key: HDDS-3563
> URL: https://issues.apache.org/jira/browse/HDDS-3563
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: mingchao zhao
> Priority: Major
>
> HDDS-3385 has a big change to s3g for creating buckets. At present, the volume is fixed as s3v. This should be user-configurable to better accommodate the older cluster (0.5).
> Our production cluster will encounter the problem that the old volume could not find after rebase master. So we are very eager to solve this problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org