MaxScale

Files

MassimilianoPinto 75b17151f3 Removed FULL option from SHOW BINARY LOGS

If option ‘binlog_structure’ is set to ‘tree’ then SHOW BINARY LOGS
displays the tree details of the binlog files.

MySQL [(none)]> SHOW BINARY LOGS;
+--------------------------+-----------+
| Log_name                 | File_size |
+--------------------------+-----------+
| 0/10122/mysql-bin.000117 |      1167 |
| 0/10122/mysql-bin.000118 |       652 |
| 0/10124/foo-bin.000016   |      5082 |
| 0/10124/foo-bin.000017   |       491 |
+--------------------------+-----------+

With option set to ‘flat’ (which is the default) the output contains
only
names:

MySQL [(none)]> SHOW BINARY LOGS;
+------------------+-----------+
| Log_name         | File_size |
+------------------+-----------+
| mysql-bin.000110 |       425 |
| mysql-bin.000111 |     10409 |
| mysql-bin.000112 |      9659 |
+------------------+-----------+

2017-08-04 10:08:11 +02:00

test

Update change date of 2.2

2017-06-01 10:24:20 +03:00

binlog_common.c

Update change date of 2.2

2017-06-01 10:24:20 +03:00

blr_cache.c

Update change date of 2.2

2017-06-01 10:24:20 +03:00

blr_file.c

Update GTID repository while receiving ROTATE events and check the current file exists.

2017-08-02 17:32:07 +02:00

blr_master.c

Update GTID repository while receiving ROTATE events and check the current file exists.

2017-08-02 17:32:07 +02:00

blr_slave.c

Removed FULL option from SHOW BINARY LOGS

2017-08-04 10:08:11 +02:00

blr.c

Binlog Server doesn't start without last found GTID in the repo only if “mariadb10_master_gtid” option is On

2017-08-02 11:56:32 +02:00

blr.h

Merge branch '2.1' into develop

2017-07-24 12:37:25 +03:00

CMakeLists.txt

MXS-1075: Sqlite db for GTID - file, pos mapping

2017-03-28 10:23:09 +02:00

maxbinlogcheck.c

Add support for non-glibc systems

2017-08-02 11:51:55 +03:00

README

Make directory name equal to the library name

2016-12-01 15:23:42 +02:00

STATUS

Make directory name equal to the library name

2016-12-01 15:23:42 +02:00

README

The binlog router is not a "normal" MaxScale router, it is not
designed to be used to route client requests to a database in the
usual proxy fashion. Rather it is designed to allow MaxScale to be
used as a relay server in a MySQL replication environment.

In this environment MaxScale sits between a master MySQL server and
a set of slave servers. The slaves servers execute a change master
to the MaxScale server, otehrwise they are configured in exactly
the same way as a normal MySQL slave server.

The master server configuration is unaltered, it simply sees a
single slave server.

MaxScale is configured as usual, with a service definition that
references the binlog router. The major configuration option to
consider is the router_options paramter, in the binlog router this
provides the binlog specific configuration parameters.

uuid=
This is the UUID that MaxScale uses when it connects
to the real master. It will report the master's
UUID to slaves that connect to it.

server-id=
The server-id that MaxScale uses when it connects
to the real master server. Again it will reports
the master's server-id to the slaves that connect
to it.
user=
The user that MaxScale uses to login to the real
master
password=
The password that MaxScale uses to login to the
real master
master-id=
The server-id of the real master. MaxScale should
get this by sending a query, but at the moment it
is in the configuration file for ease of implementation

An example binlog service configuration is shown below:

[Binlog Service]
type=service
router=binlogrouter
servers=master
router_options=uuid=f12fcb7f-b97b-11e3-bc5e-0401152c4c22,server-id=3,user=repl,password=slavepass,master-id=1
user=maxscale
passwd=Mhu87p2D

The servers list for a binlog router service should contain just
the master server. In future a list will be given and the monitor
used to determine which server is the current master server.