[ https://issues.apache.org/jira/browse/HDDS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844527#comment-16844527 ]
Siddharth Wagle edited comment on HDDS-700 at 5/21/19 5:57 AM: --------------------------------------------------------------- Thanks [~Sammi], that does make sense. But can a simple change in the current patch to take in a configuration for the ancestor gen jump, would actually enable multiple topologies without new implementations? Maybe {replicaNumber -> ancestorGen} as a config? was (Author: swagle): Thanks [~Sammi], that does make sense. But can a simple change in the current patch to take in a configuration for the ancestor gen jump, would actually enable multiple topologies without new implementations? > Support rack awared node placement policy based on network topology > ------------------------------------------------------------------- > > Key: HDDS-700 > URL: https://issues.apache.org/jira/browse/HDDS-700 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Reporter: Xiaoyu Yao > Assignee: Sammi Chen > Priority: Major > Attachments: HDDS-700.01.patch > > > Implement a new container placement policy implementation based datanode's > network topology. It follows the same rule as HDFS. > By default with 3 replica, two replica will be on the same rack, the third > replica and all the remaining replicas will be on different racks. > > {color:#808080} {color} -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org