Re: Innodb as its default storage engine for Mysql 5.0 / 5.1
Yes, InnoDB is the default storage engine for MySQL as of MySQL 5.5.MyISAM and InnoDB has its own features. InnoDB probably the best RDBMS out there. InnoDB is default engine might be due nowadays most of the application required fully ACID-compliant modes, self recovery from a crash, and many more features... 2011/5/25 Halász Sándor h...@tbbs.net 2011/05/25 10:53 +0200, Reindl Harald if there is no good reason i will never enable innodb because MyISAM is enough for most web-apps And also MyISAM supports auto-increment in a lesser part of a primary key and InnoDB not--but although it is of interest, I have not tryed it. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=aim.prab...@gmail.com -- Best Regards, Prabhat Kumar MySQL DBA My Blog: http://adminlinux.blogspot.com My LinkedIn: http://www.linkedin.com/in/profileprabhat
Re: MySQL server has gone away
I had experience with such type of error, It was due lack of resources available to MySql, max connections exceeds on the server. you can write a simple script which will grab and store output of 'show processlist' every min. and later you cna investigate the issue. On Wed, May 25, 2011 at 3:34 AM, Aveek Misra ave...@yahoo-inc.com wrote: Nothing in the error log or the slow query log that suggests that the query size is too large or us taking too much time to execute. Thanks Aveek On May 25, 2011, at 3:53 PM, Rik Wasmus wrote: failed to execute SELECT * FROM cluster_info WHERE cluster = ?: MySQL server has gone away The error MySQL server has gone away is the error from the db handle. Can anyone give me any pointers on why that happens? I looked up the documentation in MySQL docs and the most common reason seems to be that it happens if the query size is very large or if there is a timeout. None of them seems to be a probable cause. The max_allowed_packet on the server is 16 MB and as can be seen in the query above, the query is very small and nowhere near the size limit. We also have a timeout setting (wait_timeout) of 10 minutes and the above query for us cannot possibly take that amount of time. In any case, given the same query, it executes correctly 99% of time (so to speak). It fails intermittently with the above error. What possibly could be the reason? I also looked at the max connections on the server at that time (around ~80) and it is much less than the limit we have (limit is 1000). How can I extract more information when this happens? This error message sucks since it does not tell me what exactly happened. The server version is 5.1.45. Can you access the error log of the server? That can probably shed more light on the issue... -- Rik Wasmus -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=ave...@yahoo-inc.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=aim.prab...@gmail.com -- Best Regards, Prabhat Kumar MySQL DBA My Blog: http://adminlinux.blogspot.com My LinkedIn: http://www.linkedin.com/in/profileprabhat
Re: Changing the default database location
The reason to move database onto the network is that multiple user can access it. Do you think there is a better alternative? shared storage device with MySQL does not work. Perheps it will corrupt datafile. Not sure what do mean by 'multiple user can access' ; Once mysql install you can create N no of users and let them access.. On Fri, May 20, 2011 at 1:06 PM, Johan De Meersman vegiv...@tuxera.bewrote: - Original Message - From: Reindl Harald h.rei...@thelounge.net so put the wgole mysqld and its data on a server in the network for this mysql was built and not for borking the dadadir somewhere else Hmm. The way I interpret what he's saying, is that he wants multiple instances accessing the same datafiles. If that's the case, Firdosh, don't - MySQL is not made for concurrent access to the same datafiles. If multiple people/applications need access to the same data, let them connect to the same server. If that's not an option, you're going to have to look at replication. I repeat, there is no setup possible where it is safe to have multiple instances of mysqld access the same datafiles. If you do, the first thing you'll notice is that one instance doesn't see the other instance's update. The second thing you'll notice, is that your data files will be FUBAR. Fucked Up Beyond Any Recognition. Not kidding, here. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=aim.prab...@gmail.com -- Best Regards, Prabhat Kumar MySQL DBA My Blog: http://adminlinux.blogspot.com My LinkedIn: http://www.linkedin.com/in/profileprabhat
Re: Changing the default database location
PLEASE do not reply to the list and some peopole on the list mailing-list is really enough Am 26.05.2011 23:49, schrieb Prabhat Kumar: The reason to move database onto the network is that multiple user can access it. Do you think there is a better alternative? shared storage device with MySQL does not work. Perheps it will corrupt datafile. Not sure what do mean by 'multiple user can access' ; Once mysql install you can create N no of users and let them access.. On Fri, May 20, 2011 at 1:06 PM, Johan De Meersman vegiv...@tuxera.bewrote: - Original Message - From: Reindl Harald h.rei...@thelounge.net so put the wgole mysqld and its data on a server in the network for this mysql was built and not for borking the dadadir somewhere else Hmm. The way I interpret what he's saying, is that he wants multiple instances accessing the same datafiles. If that's the case, Firdosh, don't - MySQL is not made for concurrent access to the same datafiles. If multiple people/applications need access to the same data, let them connect to the same server. If that's not an option, you're going to have to look at replication. I repeat, there is no setup possible where it is safe to have multiple instances of mysqld access the same datafiles. If you do, the first thing you'll notice is that one instance doesn't see the other instance's update. The second thing you'll notice, is that your data files will be FUBAR. Fucked Up Beyond Any Recognition. Not kidding, here. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=aim.prab...@gmail.com -- Mit besten Grüßen, Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / software-development / cms-solutions p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/ http://www.thelounge.net/signature.asc.what.htm signature.asc Description: OpenPGP digital signature
Re: MySQL server has gone away
'MySQL server has gone away' Can be a network problem, Just to increase complexity :) On May 26, 2011 11:03 PM, Prabhat Kumar aim.prab...@gmail.com wrote: I had experience with such type of error, It was due lack of resources available to MySql, max connections exceeds on the server. you can write a simple script which will grab and store output of 'show processlist' every min. and later you cna investigate the issue. On Wed, May 25, 2011 at 3:34 AM, Aveek Misra ave...@yahoo-inc.com wrote: Nothing in the error log or the slow query log that suggests that the query size is too large or us taking too much time to execute. Thanks Aveek On May 25, 2011, at 3:53 PM, Rik Wasmus wrote: failed to execute SELECT * FROM cluster_info WHERE cluster = ?: MySQL server has gone away The error MySQL server has gone away is the error from the db handle. Can anyone give me any pointers on why that happens? I looked up the documentation in MySQL docs and the most common reason seems to be that it happens if the query size is very large or if there is a timeout. None of them seems to be a probable cause. The max_allowed_packet on the server is 16 MB and as can be seen in the query above, the query is very small and nowhere near the size limit. We also have a timeout setting (wait_timeout) of 10 minutes and the above query for us cannot possibly take that amount of time. In any case, given the same query, it executes correctly 99% of time (so to speak). It fails intermittently with the above error. What possibly could be the reason? I also looked at the max connections on the server at that time (around ~80) and it is much less than the limit we have (limit is 1000). How can I extract more information when this happens? This error message sucks since it does not tell me what exactly happened. The server version is 5.1.45. Can you access the error log of the server? That can probably shed more light on the issue... -- Rik Wasmus -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=ave...@yahoo-inc.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=aim.prab...@gmail.com -- Best Regards, Prabhat Kumar MySQL DBA My Blog: http://adminlinux.blogspot.com My LinkedIn: http://www.linkedin.com/in/profileprabhat
