|
I'm working with a group who is designing an
application that distributes redundant copies of their data across
multiple server nodes; something akin to RAIS (redundant array of
independent servers). Within the individual server, they have an
application that stores the particular data into a file on a filesystem
based on a hash or some other means by which to distribute the data
across the various filesystems. In their early testing, they found performance gains of ZFS compared to other filesystems. As they begin to think about the production implementation they are considering the following design using external JBOD arrays - each drive is a separate zpool with a single filesystem defined. The goal of this design is to reduce the number of interdependent components and maintain high levels of performance at the individual node level since they feel their redundancy exists by having multiple servers with copies of the data. In recent testing of failure modes, they panic'd the system by removing a drive and ZFS attempting to protect filesystem integrity (found references to bug 6322646 filed for more graceful handling of this condition). I have my concerns regarding this design, but I do not have the in-depth knowledge of ZFS to make the case for or against this design approach. I need help to identify the pros/cons so I can continue the design discussion? Thanks, Todd -- Todd E. Moore Sun Microsystems Incorporated 443.516.4002 AIM: toddmoore72462 |
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
