Varsha Ravi created HDDS-8224:
---------------------------------
Summary: Ozone network topology does not create pipelines based on
rack aware policy
Key: HDDS-8224
URL: https://issues.apache.org/jira/browse/HDDS-8224
Project: Apache Ozone
Issue Type: Bug
Components: SCM
Reporter: Varsha Ravi
When rack aware placement policy is set, the pipelines created at the start of
Ozone is not rack aware.
*Flags set:*
||Name||Value||
|net.topology.node.switch.mapping.impl|org.apache.hadoop.net.ScriptBasedMapping|
|net.topology.script.file.name|/etc/hadoop/topology/rack.py|
|ozone.scm.datanode.disallow.same.peers|true|
|ozone.scm.container.placement.impl|org.apache.hadoop.hdds.scm.container.placement.algorithms.SCMContainerPlacementRackAware|
To test whether the pipelines were re-created after setting the above flags,
Ozone was started with a clean slate with new meta,DB and data directories of
OM, SCM,DN.
*Racks:*
DN1 /rack1
DN2 /rack1
DN3 /rack4
DN4 /rack8
DN5 /rack4
DN7 /rack4
DN8 /rack1
DN9 /rack7
*Pipelines after clean start:*
{noformat}
{'1d44f491-7666-44fd-91e5-d79d2d30a7a0': [DN4, DN1, DN7],
'af93cf32-86c6-4982-baba-e4aac67a0a45': [DN4, DN3, DN8],
'e19e7bb6-1188-4e57-8ca1-88cfae5b9b32': [DN1, DN3, DN2],
'eb301397-8681-4e80-9618-67d1d2be3140': [DN2, DN7, DN8]}{noformat}
In the above case, only 2 pipelines follow rack aware topology. But for the
same combination of datanodes and racks, 5 rack aware pipelines can be created.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
