[ https://issues.apache.org/jira/browse/HDFS-11493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anu Engineer updated HDFS-11493: -------------------------------- Attachment: exploring-scalability-scm.pdf During the review of this JIRA, both [~cheersyang] and [~yuanbo] expressed concerns about the scalability limits of SCM. This is something that I have spend time thinking about myself. So this attached document captures a set of constraints for SCM and what size limits we will have in the first release of Ozone/SCM. This is a list of items that I have kept track of in terms of SCM's scalability. I look forward to your comments, questions and other feedback. > Ozone: SCM: Add the ability to handle container reports > --------------------------------------------------------- > > Key: HDFS-11493 > URL: https://issues.apache.org/jira/browse/HDFS-11493 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ozone > Affects Versions: HDFS-7240 > Reporter: Anu Engineer > Assignee: Anu Engineer > Attachments: container-replication-storage.pdf, > exploring-scalability-scm.pdf, HDFS-11493-HDFS-7240.001.patch, > HDFS-11493-HDFS-7240.002.patch, HDFS-11493-HDFS-7240.003.patch > > > Once a datanode sends the container report it is SCM's responsibility to > determine if the replication levels are acceptable. If it is not, SCM should > initiate a replication request to another datanode. This JIRA tracks how SCM > handles a container report. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org