I do not know how debian works,
but in any case it is not even 'thinkable' a MySQL instance without
being able to read the error log,
you should at least be able to read MySQL server output (error log)
before going any further.
Dealing with the status you could reset the status and start monit
i m not lucky, the server has not an exclusive error log. It is not
configure. It says: Error logging goes to syslog. This is a Debian
improvement :)
but I can not see anything clear in syslog.
On Mon, 2009-03-09 at 23:20 +0100, Claudio Nanni wrote:
> uld be
> just a Django problem (does no
Hi Mattia,
On Mar 9, 2009, at 6:21 PM, Mattia Merzi wrote:
Hi everyone,
I've got some problems with deadlocks on InnoDB tables.
On paragraph 13.6.8.10. "How to Cope with Deadlocks"
of the mysql 5.1 version, the last sentence states:
--
Another way to serialize transactions is to cr
Still everything is relative, Aborted clients seems high but it could be
just a Django problem (does not close correctly connections),
can you tail some 100 lines from the mysql error log?
Miguel wrote:
On Mon, 2009-03-09 at 22:37 +0100, Miguel wrote:
as you say, it is not a fact. I m trying to
On Mon, 2009-03-09 at 22:37 +0100, Miguel wrote:
> as you say, it is not a fact. I m trying to find the problem but I
> have no experiences with ddbb performance.
>
> I have also found file descriptors really big like this one (lsof
> info):
>
>
>
> > mysqld17638 mysql 71u REG
David Karr wrote:
it's supposedly good advice in a multi-step stored procedure to have an
explicit "start transaction" and "commit" wrapping the work. What is the
impact of doing this if the stored procedure is called from code managed by
a transaction manager. For instance, in a JEE appserver
it's supposedly good advice in a multi-step stored procedure to have an
explicit "start transaction" and "commit" wrapping the work. What is the
impact of doing this if the stored procedure is called from code managed by
a transaction manager. For instance, in a JEE appserver and a transaction
ma
HI Miguel,
first everything in your status is related to 7079381seconds uptime, that is
81 days.
After that it depends on the activity, but It seems that yours is just a
feeling, not a fact.
You have a that a table si (re)opened 350 times per day that is nothing,
mysql caches table files descripto
On Mon, March 9, 2009 12:51, Mihail Manolov wrote:
> I would strongly suggest logging all your 4.0 queries for at least 24
> hours and then running them on your new 5.x server to avoid any
> surprises such as incompatible queries for example.
>
> Good luck!
>
> Mihail
Good idea. I would pay partic
I would strongly suggest logging all your 4.0 queries for at least 24
hours and then running them on your new 5.x server to avoid any
surprises such as incompatible queries for example.
Good luck!
Mihail
On Mar 9, 2009, at 1:42 PM, Matthew Stuart wrote:
Hi all, I am on... wait for it... ve
Hi Mat,
How many databases have you got running on 4.0? You can certainly go
through the motions of downloading each interim release, however my best
advice would be (if time/disk space permits) to dump your databases to
plain SQL files (using mysqldump) obliterate your 4.0 install, install a
my worry is that the framework is running really slowly and I am trying
to justify why...
here, I can see a high number of Opens and questions when the sytem is
not now being used by anybody... Is it normal to keep the tables opened?
and have so many queries per second? and what about the slow que
Hi all, I am on... wait for it... version 4.0.25 and I want to upgrade
to MySQL 5.x
Is there anything special I should do in order to upgrade? Do I need
to uninstall v4 or can I just download the most current version and
double click to upgrade? I am not particularly hardcore mysql minded,
It is really not enough for me to give an opinion but I do not see
anything strange, what is your worry?
Miguel wrote:
thank you Claudio, something that is messing me up is what folllows:
Uptime: 7079381 Threads: 3 Questions: 776439788 Slow queries: 189
Opens: 27771 Flush tables: 1 Ope
Hi everyone,
I've got some problems with deadlocks on InnoDB tables.
On paragraph 13.6.8.10. "How to Cope with Deadlocks"
of the mysql 5.1 version, the last sentence states:
--
Another way to serialize transactions is to create an auxiliary
“semaphore” table that contains just a single
you may like to try "mytop"
or
watch -n10 mysql -BNA -e "show full processlist"
add user,host,databasename as needed
Sven schrieb:
> Hi folks
>
> I am searching for a generic command to monitor that MySQL instance is
> up and running. I don't have any know-how about the schema of the DB.
>
>
MySQL and ZFS
http://forge.mysql.com/wiki/MySQL_and_ZFS
This Thursday (March 12th, 14:00 UTC), Martin MC Brown will give a MySQL
University session on MySQL and ZFS. MC works on the MySQL Documentation
Team and has been involved with quite a few Solaris things, for example
porting MySQL to openSol
Hi folks
I am searching for a generic command to monitor that MySQL instance is
up and running. I don't have any know-how about the schema of the DB.
kind regards
Sven Aluoor
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/
thank you Claudio, something that is messing me up is what folllows:
Uptime: 7079381 Threads: 3 Questions: 776439788 Slow queries: 189
Opens: 27771 Flush tables: 1 Open tables: 64 Queries per second avg:
109.676
I am trying to optimize a django project. I am not familiar with this
framework
Here is a very interesting reading for you!
http://dev.mysql.com/doc/refman/5.0/en/table-cache.html
Claudio
2009/3/8 Miguel
> Hello,
>
> I wanted to know how mysql behaves when accessing to its tables.
> I have check the file descriptors and I could see different MYI and MYD
> opened.
>
> mys
20 matches
Mail list logo
