[Building Sakai] evals tool and MySQL

[Hedrick Charles]

To answer the original question, we are. Mysql 5.1, everything Innodb. Hosted on Solaris 10 with a ZFS file system on Sun J4000 disks.

I'm pretty happy. We are seeing 3700 queries / sec averaged over the life of the Mysql, with much higher peaks. Load peaks around 25% of CPU, and  low disk activity (2/3 or more writes).


On Oct 28, 2010, at 7:06:40 PM, Steve Swinsburg wrote:

> Luckily this was just a dev db so I've fixed that up locally, but we have a very old production DB that was created as MyISAM (been running for for years though).
> We've got the DBAs looking into how to change it to InnoDB.
> 
> thanks,
> Steve
> 
> 
> On 29/10/2010, at 10:03 AM, Sam Ottenhoff wrote:
> 
>> I believe it's from attempting to create a table using MyISAM engine and 
>> character set UTF8.
>> 
>> You can try changing your global storage engine to InnoDB first:
>> 
>>   mysql> set GLOBAL storage_engine='InnoDb';
>> 
>> --Sam
>> 
>>> Looks like it might be an InnoDB issue. Old database.
>>> 
>>> Steve
>>> 
>>> 
>>> On 29/10/2010, at 9:51 AM, Steve Swinsburg wrote:
>>> 
>>>> Hi all,
>>>> 
>>>> Is anyone running the Evaluations tool [1] under MySQL (5.1.40)? I'm having hard time starting up because of the keys being too long for MySQL:
>>>> 
>>>> Unsuccessful schema statement: create table EVAL_ASSIGN_USER (ID bigint not null auto_increment, EID varchar(255), LAST_MODIFIED datetime not null, OWNER varchar(255) not null, USER_ID varchar(255) not null, GROUP_ID varchar(255) not null, ASSIGN_TYPE varchar(255) not null, ASSIGN_STATUS varchar(255) not null, LIST_ORDER integer not null, ASSIGN_GROUP_ID bigint, EVALUATION_FK bigint not null, primary key (ID), unique (USER_ID, GROUP_ID, ASSIGN_TYPE, EVALUATION_FK))
>>>> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes
>>>> 
>>>> Unsuccessful schema statement: create table EVAL_RESPONSE (ID bigint not null auto_increment, LAST_MODIFIED datetime not null, OWNER varchar(255) not null, GROUP_ID varchar(255) not null, START_TIME datetime not null, COMMENT_RESPONSE text, SELECTIONS_CODE text, END_TIME datetime, EVALUATION_FK bigint not null, primary key (ID), unique (OWNER, GROUP_ID, EVALUATION_FK))
>>>> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes
>>>> 
>>>> Anyone addressed this?
>>>> 
>>>> Thanks,
>>>> Steve
>>>> 
>>>> [1] http://confluence.sakaiproject.org/display/EVALSYS/Home
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>> 
>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3817 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101105/3dd84050/attachment.bin