Question regarding Solaris LVM state replica databases

From: Paul Boven (p.boven_at_chello.nl)
Date: 04/29/03

  • Next message: rachid boukhari: "SUMMARY: Install over the network"
    Date: Tue, 29 Apr 2003 13:39:40 +0200
    To: sunmanagers@sunmanagers.org
    
    

    L.S.,

    I'm installing an E450 which will have 20 disks, 12 filesystems. We will
    use DiskSuite aka Solaris LVM for mirroring: each disk will be mirrored
    onto another disk on another controller.
    I'm trying to come up with the correct number of metadata-replicas I
    would need for this. The documentation has this to say about it:

    > Too few state database replicas relative to the number of mirrors
    > might cause replica I/O to impact RAID 1 volume performance. That is,
    > if you have a large number of mirrors, make sure that you have a total
    > of at least two state database replicas per RAID 1 volume, up to the
    > maximum of 50 replicas per disk set.

    This system will have 12 Raid-1 volumes (some will be a simple mirrored
    partition, others will mirror a 4-disk stripe), so I'd need 24 metadb's?
    However, this seems a bit excessive to me, to have the state database
    replicated over so many different disks.

    The documentation also states that:

    > If you have a RAID 1 volume that will be used for small-sized random
    > I/O (as in for a database), be sure that you have at least two extra
    > replicas per RAID 1 volume on slices (and preferably disks and
    > controllers)that are unconnected to the RAID 1 volume for best
    > performance.

    Of course, the machine in question will be a database server, and 4 of
    these RAID-1's will be doing heavy IO. So this would add another 8
    replica's? That would get me up to 32.

    I could for instance set this up so every disk has 2 replica's which
    gets me 40 of them. Another setup might be to use 1 replica per drive,
    and put 3 additional replica's on each of the drives that will have less
    IO. That, however, makes those 4 drives a lot more 'important' in the
    majority consensus algorithm in case I have diskfailure(s) in the
    machine. And I'm not too sure that having 4 metadb replicas in slice 7
    would be a good idea.

    What would your reccommendation be? And why?

    Regards, Paul Boven.
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers


  • Next message: rachid boukhari: "SUMMARY: Install over the network"

    Relevant Pages

    • Re: Software Raid 1 Query
      ... > was to arrange software raid 1 mirroring between two 160Gb SATA drives. ... > Disk 0: ... and the system will boot from disk 0 when I ...
      (microsoft.public.windows.server.sbs)
    • Re: Disk space issue on dynamic disc
      ... used RAID 1 software mirroring, I would expect the RAID 5 software mirroring ... With a normal mirror you can split the drives and put them back ... party software and you can do it all from the Disk Management GUI. ...
      (microsoft.public.windows.server.sbs)
    • Re: New Webserver with multiple drives
      ... > raid controller, so I'll assume that isn't a possibility either. ... > disk size, in which case you'ld end up appending one disk to the ... > IO evenly of the two drives and should maximize performance. ... > iii) RAID 1 or mirroring. ...
      (freebsd-questions)
    • Re: Mirror and/or copy
      ... > O/S files and the other contains database files. ... > Enough room to put all files on one disk. ... > documentation that is only possible to do O/S mirroring ... if you have a test machine around with two drives that you ...
      (RedHat)
    • Re: Solaris 10 + SVM = What a Piece of Sh#t !!!
      ... > the root file system when mirroring the root file system on a 2 ... Solaris SVM is the easiest ever volume manager ...
      (comp.unix.solaris)