Test rpl.rpl_init_slave leaves max_connections = 500 at the end intermittently
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Fix Released
|
Low
|
Laurynas Biveinis | |||
5.6 |
Fix Released
|
Low
|
Laurynas Biveinis | |||
5.7 |
Fix Released
|
Low
|
Laurynas Biveinis |
Bug Description
On 5.5 trunk:
MTR's internal check of the test case 'rpl.rpl_
This means that the test case does not preserve the state that existed
before the test case was executed. Most likely the test case did not
do a proper clean-up. It could also be caused by the previous test run
by this thread, if the server wasn't restarted.
This is the diff of the states of the servers before and after the
test case was executed:
mysqltest: Logging to '/mnt/workspace
mysqltest: Results saved in '/mnt/workspace
mysqltest: Connecting to server localhost:13022 (socket /tmp/V28HcbxC0d
mysqltest: ... Connected.
mysqltest: Start processing test commands from './include/
mysqltest: ... Done processing test commands.
--- /mnt/workspace/
+++ /mnt/workspace/
@@ -268,7 +268,7 @@
MAX_BINLOG_FILES 0
MAX_BINLOG_SIZE 1073741824
MAX_BINLOG_
-MAX_CONNECTIONS 151
+MAX_CONNECTIONS 500
MAX_CONNECT_ERRORS 10
MAX_DELAYED_
MAX_ERROR_COUNT 64
mysqltest: Result content mismatch
This is caused by the slave SQL thread racing to execute init-slave with the testcase, and no synchronisation between the two.
tags: | added: ci upstream |
https:/ /github. com/percona/ percona- server/ pull/967 /github. com/percona/ percona- server/ pull/968 /github. com/percona/ percona- server/ pull/969
https:/
https:/