Configuration-Guide.md
This commit is contained in:
@ -13,7 +13,7 @@ Last Updated: 29th November 2014
|
||||
# Document History
|
||||
|
||||
Date | Change | Who
|
||||
----------------|------------------|-----------------
|
||||
-------------------|------------------|-----------------
|
||||
21st July 2013 | Initial version|Mark Riddoch
|
||||
23rd July 2013 | Addition of default user and password for a monitor and discussion of monitor user requirements<br/> New monitor documented for Galera clusters<br/>Addition of example Galera cluster configuration|Mark Riddoch
|
||||
13th November 2013 | state for Galera Monitor is "synced"|Massimiliano Pinto
|
||||
@ -45,7 +45,7 @@ The purpose of this document is to describe how to configure MaxScale and to dis
|
||||
## Terms
|
||||
|
||||
Term | Description
|
||||
----|-----------
|
||||
-------------------|------------------
|
||||
service | A service represents a set of databases with a specific access mechanism that is offered to clients of MaxScale. The access mechanism defines the algorithm that MaxScale will use to direct particular requests to the individual databases.
|
||||
server | A server represents an individual database server to which a client can be connected via MaxScale.
|
||||
router | A router is a module within MaxScale that will route client requests to the various database servers which MaxScale provides a service interface to.
|
||||
|
Reference in New Issue
Block a user