Rajan,
In a SAN configuration, the lun/volume should appear just like a
locally attached physical disk on your server. MySQL will not need any
special configurations to access it, just poiint the datadir to the SAN
disk.
Regards,
Scott Tanner
On Mon, 2007-10-08 at 11:06 +0530, Ace wrote
, Scott Tanner [EMAIL PROTECTED] wrote:
Rajan,
In a SAN configuration, the lun/volume should appear just like a
locally attached physical disk on your server. MySQL will not need any
special configurations to access it, just poiint the datadir to the SAN
disk.
Regards,
Scott Tanner
Maybe I missed this in the text below, but are you trying to daisy
chain the slaves (master - slave 1 - slave 2) or have multiple slaves
connecting to one master?
Is slave 1 configured with log-slave-updates?
Regards,
Scott
On Wed, 2007-09-19 at 12:31 -0500, [EMAIL
There's a 'report-host' option that can be set in the conf file to
mask the host name. Sounds like this may be set.
If you want to get the server's actual host name from within mysql,
how about running a system command:
mysql \! hostname;
or
mysql \! cat /etc/hostnames;
our servers, and we haven't had an issue yet (restoring daily
to a testing environment).
Regards,
Scott Tanner
On Mon, 2007-06-04 at 14:57 -0700, Wm Mussatto wrote:
On Mon, June 4, 2007 14:21, murthy gandikota said:
Hi
When restoring a DB from a tar file, I had to repair some of the tables
I think you'll need to do a lot of testing to yourself to find the
right answer to that. The number of disks, type of disks, and raid
configuration will have the most effect on performance.
Personally, we had roughly 15% increase in performance from ditching
our EMC clarion and going with
Gouedard
Envoyé: mercredi 30 mai 2007 09:02
À: Scott Tanner
Cc: mysql@lists.mysql.com
Objet: Re: mysql creating lots of processes (not
threads, linux processes)
Nope
Sounds like your not using threaded libraries. Was mysql built
differently, or are you using a different RPM on this server?
Scott
On Tue, 2007-05-29 at 22:49 +0200, Quentin Gouedard wrote:
No, I have just collectd+mrtg, but i don't even use them to monitor mysql.
I launch mysql via
On Fri, 2007-04-27 at 09:19 -0500, [EMAIL PROTECTED] wrote:
So if one is doing a full mysqldump every night, all bin-logs can be
deleted after this?
On the slave - Yes. In fact I would highly recommend it before
starting the slave processes again. This will reset the bin log's
'position'
the --delete-master-logs
option.
If you want to turn the logs off, remove log-bin and log-bin-index
from the conf file.
Regards,
Scott Tanner
On Thu, 2007-04-26 at 09:47 -0700, Scott Haneda wrote:
In the short term, see the manual page for PURGE MASTER LOGS. In the
long term, write
this helps,
Scott Tanner
On Mon, Apr 02, 2007 at 08:43:35AM +0100, Ben Clewett wrote:
I forgot to mention that I am running Linux.
If anybody has some idea of software which can do this, I'd be very
interested.
Regards,
Ben
Ben Clewett wrote:
Dear MySql,
I'm looking
-performance-whitepaper.pdf
I know there were some presentations at this years MySQL Conference that
went over this (MySQL Performance Landscape comes to mind). You might be
able to find a presentations on the mysql site.
Regards,
Scott Tanner
On Fri, 2006-08-11 at 14:44 -0400, Ed Pauley II wrote
to have a larger effect then the type of disk. SAS also has more fiber
like features then SCSI, making it better suited for HA environments.
Just something else to consider.
Regards,
Scott Tanner
Sys Admin
www.amientertainment.net
--
MySQL General Mailing List
For list archives: http
On Tue, 2006-06-13 at 19:04, Dan Trainor wrote:
Jake Peavy wrote:
On 5/24/06, *Dan Trainor* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Hi -
I would like to be able to replicate all queries from a live MySQL
server, to a testing server at the office.
Can you post the failed SQL statement from your altered bin log, and
maybe the preceding commands related to that table?
Scott Tanner
AMi Entertainment.net
On Thu, 2006-03-09 at 08:28, Goldblatt, Eric wrote:
Scott,
The table already existed before the binlog. The strange thing
Does anyone know what the various lock modes mean in the show innodb
status reports?
We are investigating a dead-lock issue, and see lock_mode x and
lock_mode s. We have transaction that locks a record in mode x, and is
appears to be waiting for a lock on the same record in mode s - by the
I've been having this issue as well, happening more frequently to our
production web /ejb servers. I've increased the logging to warning level,
but my logs don't contain much (if any) information. Is there a way to
increase logging to debug level, or get more information as to what is
causing
17 matches
Mail list logo
