# Getting a lot of wsrep: initiating TOI for write set (-1)

**URL:** <https://forums.percona.com/t/getting-a-lot-of-wsrep-initiating-toi-for-write-set-1/14511>\
**Category:** Percona XtraDB Cluster\
**Created:** [February 21, 2022, 8:43pm UTC](https://forums.percona.com/t/getting-a-lot-of-wsrep-initiating-toi-for-write-set-1/14511 "2022-02-21T20:43:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![danarashad](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@danarashad](https://forums.percona.com/u/danarashad)\
**Post date:** [February 21, 2022, 8:43pm UTC](https://forums.percona.com/t/getting-a-lot-of-wsrep-initiating-toi-for-write-set-1/14511/1 "2022-02-21T20:43:06Z")

</div>

I have a two node cluster up and running using `show processlist` I have got alot of

```auto
wsrep: initiating TOI for write set (-1) | drop table if exists data_search

```

Drop table if exists if a temp table, but this seems to be jamming up the server. What exactly is `write set(-1)`  
The error log has `Page cleaner took 4784ms to flush 2232 pages`. Is it ok to kill `write set(-1)`

---

<div class="post-metadata">

**Author:** ![Oleksandr\_Bezpiatov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/oleksandr_bezpiatov/32/4451_2.png) [@Oleksandr\_Bezpiatov](https://forums.percona.com/u/Oleksandr_Bezpiatov)\
**Post date:** [February 22, 2022, 1:11pm UTC](https://forums.percona.com/t/getting-a-lot-of-wsrep-initiating-toi-for-write-set-1/14511/2 "2022-02-22T13:11:07Z")

</div>

Hi,  
Error like  
`Page cleaner took 4784ms to flush 2232 pages`  
could be a result of improper my.cnf configuration. Can you please clarify what DB/Cluster version you are running and what configs did you changed from defaults?

---

<div class="post-metadata">

**Author:** ![danarashad](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@danarashad](https://forums.percona.com/u/danarashad)\
**Post date:** [February 22, 2022, 2:38pm UTC](https://forums.percona.com/t/getting-a-lot-of-wsrep-initiating-toi-for-write-set-1/14511/3 "2022-02-22T14:38:26Z")

</div>

My version is:  
Ubuntu 20.04.3 LTS  
8.0.26-16.1 Percona XtraDB Cluster (GPL), Release rel16, Revision b141904, WSREP version 26.4.3

My config is below:

```auto
[client]
socket=/var/run/mysqld/mysqld.sock
ssl-ca=/etc/mysql/percona-cert/ca.pem
ssl-cert=/etc/mysql/percona-cert/server-cert.pem
ssl-key=/etc/mysql/percona-cert/server-key.pem

[mysqld]
server-id=404
user=mysql
tmpdir=/db2/tmp
datadir=/db1
pid-file=/var/run/mysqld/mysqld.pid
socket=/var/run/mysqld/mysqld.sock
local_infile=ON
log-error-verbosity=3
log-error=/var/log/mysql/error.log

default_storage_engine=InnoDB
sql_mode = STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION

innodb_buffer_pool_size = 20G
innodb_buffer_pool_instances = 8
innodb_lock_wait_timeout = 100 #default is 50 seconds
wait_timeout = 300 #was 86400 defaut is 28800 seconds
interactive_timeout = 600 #was 86400 default is 28800 seconds
max_heap_table_size = 96M
sort_buffer_size = 16M
join_buffer_size = 16M
tmp_table_size = 96M
max_sort_length = 8K
max_allowed_packet = 16M
group_concat_max_len = 16M
max_connections = 200
max_connect_errors = 10

max_binlog_size = 128M

log-bin=binlog
log_replica_updates
binlog_expire_logs_seconds=604800
wsrep_provider=/usr/lib/galera4/libgalera_smm.so
wsrep_cluster_address=gcomm://192.168.2.61
binlog_format=ROW
wsrep_applier_threads=8
wsrep_log_conflicts
innodb_autoinc_lock_mode=2
wsrep_node_address=192.168.2.64
wsrep_cluster_name=WebDB-cluster
wsrep_node_name=DB404
pxc_strict_mode=PERMISSIVE
ssl-ca=/etc/mysql/percona-cert/ca.pem
ssl-cert=/etc/mysql/percona-cert/server-cert.pem
ssl-key=/etc/mysql/percona-cert/server-key.pem
tls_version=TLSv1.2,TLSv1.3
[sst]
tmpdir=/db2/tmp
xbstream_opts="--verbose" #turned this on because I was getting errors.

sst-idle-timeout=0
encrypt=4
ssl-ca=/etc/mysql/percona-cert/ca.pem
ssl-cert=/etc/mysql/percona-cert/server-cert.pem
ssl-key=/etc/mysql/percona-cert/server-key.pem

[mysqld_safe]
service_startup_timeout=73200

```

---

<div class="post-metadata">

**Author:** ![svetasmirnova](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/svetasmirnova/32/21_2.png) [@svetasmirnova](https://forums.percona.com/u/svetasmirnova)\
**Post date:** [February 23, 2022, 12:48am UTC](https://forums.percona.com/t/getting-a-lot-of-wsrep-initiating-toi-for-write-set-1/14511/4 "2022-02-23T00:48:49Z")

</div>

It does not matter if you drop a permanent or a temporary table. DROP TABLE is a DDL operation. In TOI mode it will block all nodes in the cluster. Please read how to perform schema upgrades in PXC at [Redirecting](https://www.percona.com/doc/percona-xtradb-cluster/LATEST/wsrep-system-index.html#wsrep_OSU_method)
