wsrep_slave_threads change is not effective after node rejoins cluster #319

Closed
sjaakola opened this Issue Jan 6, 2018 · 0 comments

Comments

Projects
None yet
2 participants
@sjaakola
Contributor

sjaakola commented Jan 6, 2018

If wsrep_slave_threads count has been changed in a node, and node then drops from cluster and joins back, then changing the wsrep_slave_threads count will not be effective any more.

This is because the first invocation to change wsrep_slave_threads leaves a sticky counter in variables handling context, and this counter is not zeroed during node rejoining cluster.

@sjaakola sjaakola self-assigned this Jan 6, 2018

temeo pushed a commit that referenced this issue Feb 7, 2018

temeo pushed a commit that referenced this issue Feb 7, 2018

codership/mysql-wsrep/#319 wsrep_slave_threads issue after node rejoin
Recorded new result set for galera_var_slave_threads

temeo pushed a commit that referenced this issue Feb 7, 2018

Merge remote-tracking branch 'mysql-wsrep-bugs/5.7-v25-mysql-wsrep-gh…
…319' into mysql-wsrep-bugs_5.7-v25

* mysql-wsrep-bugs/5.7-v25-mysql-wsrep-gh319:
  codership/mysql-wsrep/#319 wsrep_slave_threads issue after node rejoin
  codership/mysql-wsrep/#319 wsrep_slave_threads issue after node rejoin
  codership/mysql-wsrep/#319 wsrep_slave_threads issue after node rejoin

@temeo temeo closed this Feb 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment