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

Configuration-Guide.md

Browse Source
This commit is contained in:
Kolbe Kegel
2015-02-04 15:49:48 -08:00
parent 5907c18c44
commit 6f22f8cd94
1 changed files with 38 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/Getting-Started/Configuration-Guide.md
View File

@ -13,7 +13,7 @@ Last Updated: 29th November 2014
# Document History # Document History
Date | Change | Who Date | Change | Who
----------------|------------------|----------------- -------------------|------------------|-----------------
21st July 2013 | Initial version|Mark Riddoch 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 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 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 ## Terms
Term | Description 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. 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. 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. 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.