It's now possible to use both a Unix domain socket and host/port when connecting with MaxAdmin to MaxScale. By default MaxAdmin will attempt to use the default Unix domain socket, but if host and/or port has been specified, then an inet socket will be used. maxscaled will authenticate the connection attempt differently depending on whether a Unix domain socket is used or not. If a Unix domain socket is used, then the Linux user id will be used for the authorization, otherwise the 1.4.3 username/password handshake will be performed. adminusers has now been extended so that there is one set of functions for local users (connecting locally over a Unix socket) and one set of functions for remote users (connecting locally or remotely over an Inet socket). The local users are stored in the new .../maxscale-users and the remote users in .../passwd. That is, the old users of a 1.4 installation will work as such in 2.0. One difference is that there will be *no* default remote user. That is, remote users will always have to be added manually using a local user. The implementation is shared; the local and remote alternatives use common functions to which the hashtable and filename to be used are forwarded. The commands "[add|remove] user" behave now exactly like they did in 1.4.3, and also all existing users work out of the box. In addition there is now the commands "[enable|disable] account" using which Linux accounts can be enabled for MaxAdmin usage.
		
			
				
	
	
		
			34 lines
		
	
	
		
			1.2 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			34 lines
		
	
	
		
			1.2 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
# Upgrading MariaDB MaxScale from 1.4 to 2.0
 | 
						|
 | 
						|
This document describes particular issues to take into account when upgrading
 | 
						|
MariaDB MaxScale from version 1.4 to 2.0.
 | 
						|
 | 
						|
For more information about MariaDB MaxScale 2.0, please refer to [ChangeLog](../Changelog.md).
 | 
						|
 | 
						|
## Installation
 | 
						|
 | 
						|
Before starting the upgrade, we **strongly** recommend you back up your current
 | 
						|
configuration file.
 | 
						|
 | 
						|
## MaxAdmin
 | 
						|
 | 
						|
The default way the communication between MaxAdmin and MariaDB MaxScale is
 | 
						|
handled has been changed from an internet socket to a Unix domain socket.
 | 
						|
The former alternative is still available but has been _deprecated_.
 | 
						|
 | 
						|
If no arguments are given to MaxAdmin, it will attempt to connect to
 | 
						|
MariaDB MaxScale using a Unix domain socket. After the upgrade you will
 | 
						|
need to provide at least one internet socket related flag - `-h`, `-P`,
 | 
						|
`-u` or `-p` - to force MaxAdmin to use the internet socket approach.
 | 
						|
 | 
						|
E.g.
 | 
						|
 | 
						|
    user@host $ maxadmin -u admin
 | 
						|
 | 
						|
## MySQL Monitor
 | 
						|
 | 
						|
The MySQL Monitor now assigns the stale state to the master server by default.
 | 
						|
In addition to this, the slave servers receive the stale slave state when they
 | 
						|
lose the connection to the master. This should not cause changes in behavior
 | 
						|
but the output of MaxAdmin will show new states when replication is broken.
 |