英语翻译MCKUSICK And historically you’ve had one cell per data center,right?QUINLAN That was initially the goal,but it didn’t work out like that to a large extent—partly because of the limitations of the single-master design and partly beca
来源:学生作业帮助网 编辑:作业帮 时间:2024/11/18 04:30:21
英语翻译MCKUSICK And historically you’ve had one cell per data center,right?QUINLAN That was initially the goal,but it didn’t work out like that to a large extent—partly because of the limitations of the single-master design and partly beca
英语翻译
MCKUSICK And historically you’ve had one cell per data center,right?
QUINLAN That was initially the goal,but it didn’t work out like that to a large extent—partly because of the limitations of the single-master design and partly because isolation proved to be difficult.As a consequence,people generally ended up with more than one cell per data center.We also ended up doing what we call a “multi-cell” approach,which basically made it possible to put multiple GFS masters on top of a pool of chunkservers.That way,the chunkservers could be configured to have,say,eight GFS masters assigned to them,and that would give you at least one pool of underlying storage—with multiple master heads on it,if you will.Then the application was responsible for partitioning data across those different cells.
MCKUSICK Presumably each application would then essentially have its own master that would be responsible for managing its own little file system.Was that basically the idea?
QUINLAN Well,yes and no.Applications would tend to use either one master or a small set of the masters.We also have something we called Name Spaces,which are just a very static way of partitioning a namespace that people can use to hide all of this from the actual application.The Logs Processing System offers an example of this approach:once logs exhaust their ability to use just one cell,they move to multiple GFS cells; a namespace file describes how the log data is partitioned across those different cells and basically serves to hide the exact partitioning from the application.But this is all fairly static.
英语翻译MCKUSICK And historically you’ve had one cell per data center,right?QUINLAN That was initially the goal,but it didn’t work out like that to a large extent—partly because of the limitations of the single-master design and partly beca
MCKUSICK And historically you’ve had one cell per data center,right?
你已经MCKUSICK和历史的一个细胞/数据中心,对吗?
QUINLAN That was initially the goal,but it didn’t work out like that to a large extent—partly because of the limitations of the single-master design and partly because isolation proved to be difficult.As a consequence,people generally ended up with more than one cell per data center.We also ended up doing what we call a “multi-cell” approach,which basically made it possible to put multiple GFS masters on top of a pool of chunkservers.That way,the chunkservers could be configured to have,say,eight GFS masters assigned to them,and that would give you at least one pool of underlying storage—with multiple master heads on it,if you will.Then the application was responsible for partitioning data across those different cells.
昆兰,最初的目标,但是没能做到像一大extent-partly因为single-master设计的局限性,部分原因是隔离被证明是困难的.因此,人们通常结束了不止一个细胞/数据中心.我们也做了我们所说的“多”的方法,就是使它可能提出多个服务队大师的顶端chunkservers水池.这样的话,chunkservers可以配置,说,按照分配给他们8主人,会给你至少有一个潜在的storage-with多个主人池头,假如你愿意.然后应用负责分区数据在这些不同的细胞.
MCKUSICK Presumably each application would then essentially have its own master that would be responsible for managing its own little file system.Was that basically the idea?
MCKUSICK大概每个应用程序将有自己的主人,本质上是将负责管理其自己的小的文件系统.基本上是,这个主意怎么样?
QUINLAN Well,yes and no.Applications would tend to use either one master or a small set of the masters.We also have something we called Name Spaces,which are just a very static way of partitioning a namespace that people can use to hide all of this from the actual application.The Logs Processing System offers an example of this approach:once logs exhaust their ability to use just one cell,they move to multiple GFS cells; a namespace file describes how the log data is partitioned across those different cells and basically serves to hide the exact partitioning from the application.But this is all fairly static
昆兰是也不是.应用任何一个倾向于使用主人或一个小套的主人.我们也有一些我们称为名字空间,这是一个非常静态方法命名空间的分割,人们可以用来掩饰这一切从实际应用的需要.原木加工系统提供了这种方法的一个例子:一旦记录排气了他们的能力,只使用一个细胞,他们搬到多个服务队细胞;一个命名空间的文件描述了测井资料划分不同的细胞,在那些隐藏的确切的基本服务.从应用分割但这都是相当静止
我不会