Bug #21517 Several variables need to be added to show variabels and slave status
Submitted: 8 Aug 2006 18:10 Modified: 8 Aug 2006 18:11
Reporter: Jonathan Miller Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:5.1.12 OS:Linux (Linux)
Assigned to: Assigned Account CPU Architecture:Any

[8 Aug 2006 18:10] Jonathan Miller
Jonathan Miller wrote:
> Hi,
> Looking at different stuff and noticed that when I do show variables 
> "master-connect-retry" does not show in the list nor does it show when 
> I do a show slave status. I think that it should show in one of the 2 places.
> Probably both (master-connect-retry & slave-net-timeout) should show 
> in slave status although slave status is pretty long as it is.

For SHOW SLAVE STATUS, there is a Connect_Retry column. Isn't that the master-connect-retry?

In general, I would have preferred just showing the slave status variables (i.e., variables that actually change while the slave is
running) and showing slave configuration variables just under SHOW VARIABLES (with a suitable prefix for slave variables). However, since the SHOW SLAVE STATUS contain all kinds of information about the slave execution and configuration, we might just as well add the variables you mention above to both lists. This is probably what the customers expect right now.

> Also, --master-retry-count=count is not found in show variables or 
> show slave status. Default value is not given in the docs and not sure 
> where you would go to change this.

IMHO, we should ensure that this is added to both lists (with the same reasoning as above). If it is not changeable, I would suggest that we ensure that it is indeed a changeable server variables, since there is no rational reason to not allow it.




Mats Kindahl

How to repeat:
see above