MariaDB Galera 5.5.34 - Error 1317 (70100): Query execution was interrupted

1,077 views
Skip to first unread message

Thomas Plant

unread,
Feb 6, 2014, 10:41:55 AM2/6/14
to codersh...@googlegroups.com
Hello.

When doing a select * from a big table (approx. 2.4 Million rows) and interrupting the query with CTRL-C any command I type afterwards gives the error "1317 (70100): Query execution was interrupted".
The next command I type works normally.

No log entries on the MariaDB Galera Node to which I'm connected.

Every tip on how to resolve this would be very appreciated.

Thanks,
Thomas

here my server.cnf file:

[mysqld]
max_allowed_packet=32M
log-error=/var/log/mariadb/mariadb.log

# 1. Mandatory settings: these settings are REQUIRED for proper cluster operation
query_cache_size=0
binlog_format=ROW
default_storage_engine=innodb
innodb_autoinc_lock_mode=2
# innodb_doublewrite=1 - this is the default and it should stay this way

# 2. Optional mysqld settings: your regular InnoDB tuning and such
datadir=/var/lib/mysql
innodb_buffer_pool_size=2G
innodb_log_file_size=10M
innodb_file_per_table
innodb_flush_log_at_trx_commit=2
innodb_file_per_table=1

# 3. wsrep provider configuration: basic wsrep options
wsrep_provider=/usr/lib64/galera/libgalera_smm.so
wsrep_provider_options="gcache.size=1G"
wsrep_cluster_address=gcomm://vs18.int.zcom.it,vs19.int.zcom.it,vs20.int.zcom.it
wsrep_cluster_name='LimitisCluster'
wsrep_node_address='10.10.100.6'
wsrep_node_name='vs20'
wsrep_sst_method=xtrabackup
wsrep_sst_auth=userxy:XXXXXXXXX
wsrep_notify_cmd='/usr/local/bin/galeranotify.py'

Alex Yurchenko

unread,
Feb 7, 2014, 9:01:57 AM2/7/14
to codersh...@googlegroups.com
On 2014-02-06 17:41, Thomas Plant wrote:
> Hello.
>
> When doing a select * from a big table (approx. 2.4 Million rows) and
> interrupting the query with CTRL-C any command I type afterwards gives
> the
> error "1317 (70100): Query execution was interrupted".
> The next command I type works normally.
>
> No log entries on the MariaDB Galera Node to which I'm connected.
>
> Every tip on how to resolve this would be very appreciated.

This seems to be a normal MySQL behavior. At least I can reproduce it on
a stock MySQL 5.5.34 in Ubuntu.
--
Alexey Yurchenko,
Codership Oy, www.codership.com
Skype: alexey.yurchenko, Phone: +358-400-516-011
Reply all
Reply to author
Forward
0 new messages