enterprise-support team mailing list archive

[Nilnandan Joshi <nilnandan.joshi@xxxxxxxxxxx>]

Unable to reproduce the same with 5.5.36 and 5.6.16
I tried to test by running sysbench with --num-threads=100  and got Innodb_row_lock_current_waits >0 but when test completes, it's set back to 0. So I don't see the behavior "Constantly increasing Innodb_row_lock_current_waits value "

nilnandan@nilnandan-Dell-XPS:~/sandboxes/msb_5_6_16$ sysbench --test=oltp --oltp-table-size=1000000 --oltp-test-mode=complex --oltp-read-only=off --num-threads=100 --max-time=90 --max-requests=0 --mysql-db=dbtest --mysql-user=root --mysql-socket=/tmp/mysql_sandbox5616.sock run
sysbench 0.4.12:  multi-threaded system evaluation benchmark

No DB drivers specified, using mysql
Running the test with following options:
Number of threads: 100

Doing OLTP test.
Running mixed OLTP test
Using Special distribution (12 iterations,  1 pct of values are returned in 75 pct cases)
Using "BEGIN" for starting transactions
Using auto_inc on the id column
Threads started!
Time limit exceeded, exiting...
(last message repeated 99 times)
Done.

OLTP test statistics:
    queries performed:
        read:                            2669604
        write:                           953430
        other:                           381372
        total:                           4004406
    transactions:                        190686 (2118.37 per sec.)
    deadlocks:                           0      (0.00 per sec.)
    read/write requests:                 3623034 (40248.94 per sec.)
    other operations:                    381372 (4236.73 per sec.)

Test execution summary:
    total time:                          90.0156s
    total number of events:              190686
    total time taken by event execution: 8998.5023
    per-request statistics:
         min:                                  4.23ms
         avg:                                 47.19ms
         max:                                240.82ms
         approx.  95 percentile:              93.18ms

Threads fairness:
    events (avg/stddev):           1906.8600/21.21
    execution time (avg/stddev):   89.9850/0.01

nilnandan@nilnandan-Dell-XPS:~/sandboxes/msb_5_6_16$


mysql> show global status like 'innodb_row_lock_current_waits';
+-------------------------------+-------+
| Variable_name                 | Value |
+-------------------------------+-------+
| Innodb_row_lock_current_waits | 2    |
+-------------------------------+-------+
1 row in set (0.00 sec)

mysql>


mysql> show global status like 'innodb_row_lock_current_waits';
+-------------------------------+-------+
| Variable_name                 | Value |
+-------------------------------+-------+
| Innodb_row_lock_current_waits | 1     |
+-------------------------------+-------+
1 row in set (0.00 sec)

mysql>

mysql> show global status like 'innodb_row_lock_current_waits';
+-------------------------------+-------+
| Variable_name                 | Value |
+-------------------------------+-------+
| Innodb_row_lock_current_waits | 0     |
+-------------------------------+-------+
1 row in set (0.00 sec)

mysql>


** Changed in: percona-server/5.5
       Status: New => Invalid

** Changed in: percona-server/5.6
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1303336

Title:
  Constantly increasing Innodb_row_lock_current_waits value

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1303336/+subscriptions