Merged tickets are sloooow after upgrade to 3.6.6 - Locking problem?

RT Users
1

Hello everyone,

after upgrading to V3.6.6 merged tickets are really slow.

After doing a bit research, I saw a lot of MySQL entrys stating that
get_lock queries took a long time:

Query_time: 69 Lock_time: 0 Rows_sent: 1 Rows_examined: 0

use rtdb;
SELECT GET_LOCK(‘Apache-Session-1b11b6323211dc42ec9d40473784e254’,
3600);

I first converted the table to innodb and then changed the session
backend to Apache::Session::File. Now the mysql log entries are gone
but the ticket system is not faster than before…

However, this does only affect merged tickets.

It seems that rt locks and tries to access the locked data in some way
because it used to be two tickets?

Has anyone else experienced this behaviour and dound a solution?

Best regards,

2

Hello everyone,

I solved this problem by setting the mySQL setting low_priority_updates
to 1 .

You kmight want to try this option if your installation is slow in
displaying merged tickets.

Best regards,On Di, Jul 01, 2008 at 03:30:00 +0200, Franz Georg Köhler lists@openunix.de wrote:

Hello everyone,

after upgrading to V3.6.6 merged tickets are really slow.

After doing a bit research, I saw a lot of MySQL entrys stating that
get_lock queries took a long time:

Query_time: 69 Lock_time: 0 Rows_sent: 1 Rows_examined: 0

use rtdb;
SELECT GET_LOCK(‘Apache-Session-1b11b6323211dc42ec9d40473784e254’,
3600);

I first converted the table to innodb and then changed the session
backend to Apache::Session::File. Now the mysql log entries are gone
but the ticket system is not faster than before…

However, this does only affect merged tickets.

It seems that rt locks and tries to access the locked data in some way
because it used to be two tickets?

Has anyone else experienced this behaviour and dound a solution?

Best regards,

The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Warning: You are not root

     -- nmap V. 2.54BETA31