You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ayush Saxena (Jira)" <ji...@apache.org> on 2020/12/21 16:00:00 UTC
[jira] [Resolved] (HDDS-4449) Rename config
ozone.datanode.pipeline.limit
[ https://issues.apache.org/jira/browse/HDDS-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ayush Saxena resolved HDDS-4449.
--------------------------------
Fix Version/s: 1.1.0
Resolution: Fixed
> Rename config ozone.datanode.pipeline.limit
> -------------------------------------------
>
> Key: HDDS-4449
> URL: https://issues.apache.org/jira/browse/HDDS-4449
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: SCM
> Affects Versions: 0.5.0
> Reporter: Wei-Chiu Chuang
> Assignee: YI-CHEN WANG
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.1.0
>
>
> I'm trying to enable multi-raft. But the naming of the config property "ozone.datanode.pipeline.limit" is confusing to me. I would have thought this is a DN side configuration because of the "ozone.data" prefix. Turns out it's a SCM config. Can we move it to ozone.scm.*?
--
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