hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Tidy the lining up of a message; add documentation.

Browse Source
This commit is contained in:
counterpoint
2015-06-24 14:39:13 +01:00
parent bf6eea38aa
commit 7f35bbed55
3 changed files with 82 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
Reference/MaxAdmin.md
View File

@ -314,10 +314,25 @@ It is possible to see more details regarding a given server using the show serve
Port: 3307
Server Version: 5.5.25-MariaDB-log
Node Id: 124
Number of connections: 0
Current no. of conns: 0
Number of connections: 0
Current no. of conns: 0
Current no. of operations: 0
MaxScale>
If the server has a non-zero value set for the server configuration item "persistpoolmax",
then additional information will be shown:
Persistent pool size: 1
Persistent measured pool size: 1
Persistent pool max size: 10
Persistent max time (secs): 3660
The distinction between pool size and measured pool size is that the first is a
counter that is updated when operations affect the persistent connections pool,
whereas the measured size is the result of checking how many persistent connections
are currently in the pool. It can be slightly different, since any expired
connections are removed during the check.
## Setting The State Of A Server
MaxScale maintains a number of status bits for each server that is configured, these status bits are normally maintained by the monitors, there are two commands in the user interface that are used to manually maintain these bits also; the set server and clear server commands.
@ -358,6 +373,13 @@ All status bits, with the exception of the maintenance bit, will be set by the m
MaxScale> clear server server3 maintenance
MaxScale>
## Viewing the persistent pool of DCB
The DCBs that are in the pool for a particular server can be displayed (in the
format described below in the DCB section) with a command like:
MaxScale> show persistent server1
# Working With Sessions
The MaxScale session represents the state within MaxScale. Sessions are dynamic entities and not named in the configuration file, this means that sessions can not be easily named within the user interface. The sessions are referenced using ID values, these are actually memory address, however the important thing is that no two session have the same ID.
@ -448,6 +470,10 @@ The details of an individual DCB can be obtained by use of the show dcb command
MaxScale> show dcb 0x727900
DCB: 0x727900
DCB state: DCB in the polling loop
Username: somename
Protocol: MySQLBackend
Server Status: Master, running
Role: Request Handler
Connected to: 127.0.0.1
Owning Session: 0x727da0
Statistics:
@ -457,8 +483,14 @@ The details of an individual DCB can be obtained by use of the show dcb command
No. of Accepts: 0
No. of High Water Events: 0
No. of Low Water Events: 0
Added to persistent pool: Jun 24 09:09:56
MaxScale>
The information Username, Protocol, Server Status are not
always relevant, and will not be shown when they are null.
The time the DCB was added to the persistent pool is only shown
for a DCB that is in a persistent pool.
# Working with Filters
Filters allow the request contents and result sets from a database to be modified for a client connection, pipelines of filters can be created between the client connection and MaxScale router modules.