Active
Project:
DB Tuner
Version:
6.x-1.0-alpha2
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
13 Aug 2010 at 21:33 UTC
Updated:
14 Aug 2010 at 00:55 UTC
I set indexes "Experimental Indexes for Core modules", but i get mysql server to crash, i unselect, don't know if the indexes get removed or set to drupal default ? How i can get to drupal default....?
Thanks
Comments
Comment #1
mikeytown2 commentedIf you unselect and save it will remove the indexes.
What mysql sever are you using? Adding indexes to tables should not make mysql crash. Are you 100% sure this is what caused the crash? any way to reproduce this? What do you mean by crash?
Comment #2
toma commentedI am setting my website offline now because it slow down mysql until the server get down, i am not sure if its what make my server down, but it was the last change i make to gain performance to my website...
I have MySQL 5.0.91 with php 5.2.14
Information from my drupal sql status report
Command counters
SELECT-statements.INSERT-statements.UPDATE-statements.DELETE-statements.Query performance
Query cache information
The MySQL query cache can improve performance of your site by storing the result of queries. Then, if an identical query is received later, the MySQL server retrieves the result from the query cache rather than parsing and executing the statement again.
Comment #3
mikeytown2 commentedYou enabled the experimental indexes and after some time mysql could not keep up with the requests coming in. Is this correct? I run with all the experimental indexes so I wonder which one could be giving you grief. Could you try it without the menu_links turned on?
Are you using innodb or myisam?
Comment #4
toma commentedYes!For the first time i was run with innodb engine, and switch back to myisam, i unselect all Experimental Indexes for Core modules
Thanks
Comment #5
mikeytown2 commentedI should make a note saying that unless your using innodb, the Experimental Indexes might be a bad idea. Thanks for the bug report; & let me know how menu_links turn out, if you wish to test (please do). I came up with the experimental indexes after running "mysql_explain_slow_log" from http://www.willamowius.de/mysql-tools.html
Comment #6
toma commentedWhen i am trying to unselect "Table: node Column: type"
I get
But i receive change after the message
user warning: Can't DROP 'type'; check that column/key exists query: ALTER TABLE node DROP INDEX type in /home/biladim/public_html/includes/database.mysql-common.inc on line 448.The "Table: node Column: type" still get indexed and selected
Comment #7
toma commentedI undo every step i make, i trun the engine to myisam, unselect all index table, still get "Table: node Column: type " selected even i get the success message
Thanks for your support
Comment #8
mikeytown2 commentedThat's an index that is apart of core; It will show it, but if you try to remove it it will won't work.
Are you sure you wish to undo all the indexes? The ones that gave you issues are "experimental" for a reason (not a 100% sure thing). The rest will help the performance of your views; I'm fairly certain of this.
Comment #9
toma commentedI am just trying to undo everything so i can see if i get the server to work when i get the website online, so the indexes will work better with MyISAM engine ?
Comment #10
mikeytown2 commentedis the server still down? if so then this is something else...
do you have something like phpmyadmin? if so click on the "Processes" tab. If not run this mysql command
SHOW PROCESSLISTCount how many rows appear.
Comment #11
toma commentedI have the server up, just one website that i set offline, now i unselect all "Experimental Indexes for Core modules" and i keep the indexe core as you advise me, i set the website online, for now i have no problem, hope it still up
I can't access the server now, i am out of office