[
https://issues.apache.org/jira/browse/HDDS-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chung En Lee updated HDDS-3080:
-------------------------------
Target Version/s: 2.2.0 (was: 1.2.0)
2.2.0 (was: 2.1.0)
<<Bulk update>>
Apache Ozone 2.1.0 release is in progress. I'm updating all unresolved jiras
targeting 2.1.0 to retarget 2.2.0.
> Configurable container placement policy may not be compatible with pipeline
> placement policy
> --------------------------------------------------------------------------------------------
>
> Key: HDDS-3080
> URL: https://issues.apache.org/jira/browse/HDDS-3080
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM
> Affects Versions: 1.0.0
> Reporter: Stephen O'Donnell
> Priority: Major
>
> New pipelines are created on hosts in a rack aware way using
> PipelinePlacementPolicy, which supports only rack aware and random.
> However the Container Placement Policy used by ReplicationManager can be
> configured between the following using the config option
> ozone.scm.container.placement.impl:
> SCMContainerPlacementRackAware
> SCMContainerPlacementCapacity
> SCMContainerPlacementRandom
> If there is a network topology configured via net.topology.table.file.name,
> then it would be possible to have an incompatible setting for
> ozone.scm.container.placement.impl.
> We need to consider how to ensure the replication manager and Pipeline
> Provider always use compatible policies. One option may be to merge the rack
> aware policies as suggested in HDDS-3079, and also allow Capacity and Random
> to be used in the pipeline provider.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
