Hello Dan Nelson <[EMAIL PROTECTED]>, So, what will happen if I use iSCSI/Fiberchannel/NFS to share the storage? Well, I am just worried about the chance of data loss in MySQL 3.23 two-way replication. I hope there is a share storage and 2 or more write-only mysql servers could mount the device. In this case, I don't worry about the raw data consistency and can balance the write-only connections to mutiple mysql servers. Ideas?
I am looking a solution to implement load balance amount write-only mysql servers yet keeping the data consistency. On Thu, 23 May 2002 01:16:35 -0500 Dan Nelson <[EMAIL PROTECTED]> wrote: > In the last episode (May 22), Jeremy Zawodny said: > > On Wed, May 22, 2002 at 03:52:33PM +0800, Patrick Hsieh wrote: > > > Hello Dan Nelson <[EMAIL PROTECTED]>, > > > > > > Is there any lock problem on iSCSI or SAN environment? Say, > > > mutliple mysql server mount the backend iSCSI or SAN storage > > > device. Is it safe? > > > > It is safe if you use MySQL's external (file) locking. > > You will also need a filesystem that supports shared storage. > Sistina's Global File System (GFS) is the only such filesystem > available for Linux, afaik (at only $995 per node; shared storage is > NOT easy to implement). If you do not have such a filesystem, you will > most likely completely trash your filesystem when you mount it from the > 2nd machine. > > iSCSI/FibreChannel is not NFS. It is block-level access to raw storage > just like SCSI or IDE. > > -- > Dan Nelson > [EMAIL PROTECTED] -- Patrick Hsieh <[EMAIL PROTECTED]> GPG public key http://pahud.net/pubkeys/pahudatpahud.gpg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
