免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
楼主: hoking
打印 上一主题 下一主题

[集群与高可用] Isilon集群存储 有问必答 [复制链接]

论坛徽章:
0
11 [报告]
发表于 2008-04-30 11:55 |只看该作者
一份简单的测试报告,适合媒体、广播电视领域参考。

node #                       3        5        10          18            24
极限读 (MB/s)        101        336        795        1400        1720
极限写 (MB/s)        71.9        343        724        1200        1580
稳定读 (MB/s)        91.75        455    733                  
稳定写 (MB/s)        43.7        91        131                  
混合读写 (MB/s)122.692 345          876          1313           1402

论坛徽章:
0
12 [报告]
发表于 2008-04-30 16:26 |只看该作者
叫网格存储应该更合适

论坛徽章:
0
13 [报告]
发表于 2008-05-02 20:22 |只看该作者

回复 #10 deadwind 的帖子

理论上来说谁都不能达到线性一倍,因为节点之间互相交换信息,还是要耗费一些资源的。
但是市场推广上都会采用这些语言。

除了Isilon,EL,还有其他家的集群存储都可以声称自己有这种功能。比如NetApp,IBM,EMC 等等。

论坛徽章:
0
14 [报告]
发表于 2008-05-04 12:17 |只看该作者
数据通明移植和负载均衡?
我还想请教,能否比较与NetApp的GX进行一下比较。

论坛徽章:
0
15 [报告]
发表于 2008-05-04 21:57 |只看该作者

回复 #15 3150391 的帖子

透明数据移植和负载均衡:
两方面理解:
其一,举例说明,假如现有4台存储节点构成的存储集群,数据量达到90%(因为Isilon的OneFS是分布式文件系统,所以每个节点上的数据量都是90%);现加入一个新节点,原来的数据将会自动透明的重新分不到这五个节点上,以为是后台执行的,所以不会影响系统的性能。
其二,负责均衡
Isilon有个模块,叫SmartConnect,这个模块,可以提供客户端具体访问哪个存储节点,从而实现负载均衡。有四个可选的策略:roundrobin、CPU、connection、aggregation。

和GX的比较:
1) 从架构角度来看:
OneFS:64-bit journaled and fully distributed filesystem (data and metadata)
GX 10.0.X:WAFL non-distributed file system, ONTAP GX 10.0

2)从方案架构角度来看:
Isilon:File system is fully distributed across entire storage cluster.  Hardware is fully symmetric cluster (Global coherency & data striped across all storage nodes).  OneFS (One File System) combines the traditional storage layers of the file system, volume manager and RAID into a single software layer making for industry leading simplicity and management.  Fully Distributed Cluster N-way.  Each "node" contains CPU, NVRAM, memory, Gbe ports and disk.  Isilon solution is built from day one as a simple all in one modular network storage cluster

NetAppGX:ONTAP GX allows for traditional NetApp controllers/storage silos (FAS 3000's, 6000's) to operate under a single global namespace.  "Clustered" together via GigE network must add controllers in multiples of 2 controllers at a time.  Supporting from 2-24 controllers.  Solution is effectively managing FlexVol volumes and Aggregates.  ONTAP GX joins these flexible volumes into a single tree to create the global namespace.  File system is still the traditional non-distributed WAFL file system. Solution requires management of each traditional storage silo including each FAS head, HA and FC interconnects, ESH, RAID DP, spares, etc...

3)后端连接方式:
Isilon:千兆网或者10GB Infiniband网;NetAppGX:千兆网

4)全局命名空间:
Isilon:True single global namespace (F: Drive) regardless of size of cluster
NetAppGX:Single namespace (single mount point) achieved by pulling together traditional storage silos and file systems

5)数据透明迁移(autobalance)
Isilon:AutoBalance: Automatic content migration with addition of new capacity.  Isilon automatically rebalances (restripes) all data in the background across all the nodes (including new nodes) balancing content across entire cluster
NetAppGX:Manual administrative process to manage and keep data balanced across the "cluster".  Requires expertise in FlexVol and Aggregate management, understanding the application workflows and hot spots, and the intricacies of understanding the virtualized cluster that ONTAP GX has created.

6)RAID管理
Isilon:RAID protection change on the fly (during r/w or capacity scaling).  RAID mgmt is extremely easy and simple
NetAppGX:Cannot change RAID on the fly during production.  RAID protection change requires backup/restore.  Traditional RAID configuration challenges

7)性能安全性
Isilon:Because each node in an Isilon cluster is a coherent peer performance is only nominally impacted should a node(s) go out of service or come down.  With NFS failover clients are automatically distributed across the remaining nodes minimizing end user impact
NetAppGX:Uncertain perfomance degredation when you lose controllers depending on workflow and configuration.

Global Memory and NVRAM
Isilon:Each node adds 4GB of Globally Coherent cache.  Linearly scales.  Max cache 384GB (Globally coherent with 96 nodes tested); 49.2GB NVRAM(96 Node Cluster 512MB/Node); all via TrueScale technology.
NetAppGXedicated memory per filer head.  Not globally coherent.  6 - 8 GB per single head; Dedicated NVRAM per filer head.  1GB, 512MB single controller

先说这些吧,有什么问题再继续讨论。

论坛徽章:
0
16 [报告]
发表于 2008-05-09 12:54 |只看该作者
目前集群存储领域,个厂商都摩拳擦掌,准备开始下一轮竞争,具体参与的厂商包括:
IBM :XIV
HP   : PolyServ
EMC:Maui/Hulk
NetApp:GX
Isilon : IQ cluster
PANASAS
3PAR
BLUEARC
Omneon MediaGrid

论坛徽章:
0
17 [报告]
发表于 2008-11-30 15:34 |只看该作者
不会这么就沉底了吧,自己顶一把。

论坛徽章:
0
18 [报告]
发表于 2008-11-30 22:11 |只看该作者
原帖由 hoking 于 2008-11-30 15:34 发表
不会这么就沉底了吧,自己顶一把。


禁止挖坟!~~~

论坛徽章:
0
19 [报告]
发表于 2008-12-01 10:37 |只看该作者
lz应该发点儿培训手册让大家研究再发问
否则好多人都不了解,无从问起啊

论坛徽章:
0
20 [报告]
发表于 2008-12-02 11:53 |只看该作者
培训手册参见:

ftp://222.128.91.6/pub/outcoming

[ 本帖最后由 hoking 于 2008-12-2 13:50 编辑 ]
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP