I have an installation of MySQL where the data directory is located on an NFS share.
Client and server are connected by Full Duplex Gigabit Ethernet (both hosts run Linux
2.4.21). The NFS is exported with sync option.
Read performance is really fine, but when it comes to writing e.g. an
On Fri, Jun 27, 2003 at 09:20:45AM +0200, [EMAIL PROTECTED] wrote:
I have an installation of MySQL where the data directory is located
on an NFS share. Client and server are connected by Full Duplex
Gigabit Ethernet (both hosts run Linux 2.4.21). The NFS is exported
with sync option.
Read
Hi... I've got the folowing question, our servers are running pretty
busy these days and our main DB server is taking high load peaks (memory
is OK but the cpu has almost no idle time). We have another spare server
and I'm thinking about mounting the database over NFS (100mb LAN) to the
spare
On Tuesday 20 August 2002 06:39 am, Luis Calero wrote:
NFS locking is ALWAYS problematical. You might have no problems, you might
also be instantly in hell.
Its really hard actually to answer your question. NFS implementations vary
greatly in their quality. In addition it depends on the NICs
, this is a bit
different.
Let us know if you try it and how it turns out.
- Original Message -
From: Luis Calero [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 20, 2002 5:39 AM
Subject: MySQL over NFS
|
| Hi... I've got the folowing question, our servers are running pretty
| busy
]
To: Luis Calero [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, August 20, 2002 8:07 AM
Subject: Re: MySQL over NFS
| This is an interesting idea. I would be a happy man if it would actually
| work. My experiences with NFS would lead me to believe that this would
not
| help and could hurt
: Tuesday, August 20, 2002 5:39 AM
Subject: MySQL over NFS
|
| Hi... I've got the folowing question, our servers are running pretty
| busy these days and our main DB server is taking high load peaks (memory
| is OK but the cpu has almost no idle time). We have another spare server
| and I'm
Also, what we have done is used a replicating box as a select only server.
This requires you to write your code in such a way that only selects get
sent to the slave. A simple function wrapper in PHP is all we needed.
I've been thinking of this idea too but it's a bit of a problem because
PROTECTED]
Sent: Tuesday, August 20, 2002 8:57 AM
Subject: Re: MySQL over NFS
|
| Also, what we have done is used a replicating box as a select only
server.
| This requires you to write your code in such a way that only selects get
| sent to the slave. A simple function wrapper in PHP is all
Hi there,
i anybody out there running mysql on a netapp filer as data storage?
regards
Sven Huster
Senior Unix System Administrator
*BSD, Linux, Solaris
-
Before posting, please check:
http://www.mysql.com/manual.php
Sven Huster wrote:
Hi there,
i anybody out there running mysql on a netapp filer as data storage?
Yes, I've done this for a client from a linux server. Worked
fine as long as there was only one mysql server accessing
the data. The network as 100 Mbs, and the SQL volume was
pretty
Am 00:20 30.03.2001 schrieb Joshua Chamas:
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Sven Huster wrote:
Hi there,
i anybody out there running mysql on a netapp filer as data storage?
Yes, I've done this for a client from a linux server. Worked
fine as
Yep, what do you need ?
Sven Huster wrote:
Hi there,
i anybody out there running mysql on a netapp filer as data storage?
regards
Sven Huster
Senior Unix System Administrator
*BSD, Linux, Solaris
-
Before
Hi,
my problem is that now the second time the performance of my f740
goes down every day.
i solved the prob with increasing maxfiles (no to the max for the
volume).
after that the cpu of the filer, which went up from
25% peak to 90% peak in 5 days, goes down again.
any ideas why
I am trying to setup some sort of loadbalancing and more importantly
fail-over-services for my mysql servers. I would like to have all the data
stored on a RAID interface that will mirror the data and provide the data to
two separate mysql daemons on two separate boxes. That way if one daemon
Nope...
It's stated explicitly in the docs that this is a *Bad Idea* (with caps,
even! *grin*). You'll need to look at other options - replication,
possibly, either on to the same machine with your db on a different
drive, or (probably preferable) onto a seperate box.
regards,
P
On Tue, 6
16 matches
Mail list logo