faaf7f483e
2.4.13 Update Change Date
2020-10-14 09:15:46 +03:00
9304230212
MXS-3149 Properly remove master-status from server during demotion
...
Removing it from the pending status field has not effect as the
pending changes have all ready been written to real status.
2020-09-02 15:13:23 +03:00
babcda3eca
2.4.12 Update Change Date
2020-08-24 09:42:48 +03:00
fc9c9fcd77
2.4.11 Update change date
2020-07-07 10:01:38 +03:00
5ebae9be90
Merge branch '2.3' into 2.4
2020-06-05 09:36:24 +03:00
aa11c960b1
2.3.20 Update change date
2020-06-05 09:31:45 +03:00
d3d7054639
Merge branch '2.3' into 2.4
2020-04-24 16:09:20 +03:00
f527a8f2e6
2.3.19 Update Change Date
2020-04-23 14:23:57 +03:00
d0ab797938
Merge branch '2.3' into 2.4
2020-03-12 10:33:57 +02:00
e0cd6adb26
Update change date for 2.3.18
2020-03-10 10:45:47 +02:00
4a5293ebba
Merge branch '2.3' into 2.4
2020-03-02 18:05:11 +02:00
67fee60f80
Fix Auth Error server status
...
The mon_ping_or_connect_to_db resets the MYSQL handle which caused the
loss of the error message. Returning a new enumeration value for
authentication errors solves this problem.
2020-03-02 16:32:35 +02:00
8b763fb88b
Merge branch '2.3' into 2.4
2020-02-12 08:27:48 +02:00
cfb3f79b54
Update 2.3.17 Change Date
2020-02-10 15:28:38 +02:00
a7e0142224
Merge branch '2.3' into 2.4
2020-01-15 11:29:37 +02:00
790d90f229
Update 2.3.16 Change Date
2020-01-15 11:08:51 +02:00
4ae22f9991
Merge branch '2.3' into 2.4.5
2019-12-19 10:03:35 +02:00
a73b183555
MXS-2813: Mask password values in output
...
The password values are now masked with asterisks. This tells whether a
password is set or not but it does not expose any information about the
password itself.
2019-12-19 09:56:00 +02:00
a9a2b753c0
Update 2.4.5 change date
2019-12-18 13:25:03 +02:00
f6731a898d
Update change date
2019-11-13 08:37:17 +02:00
fdfbf3e133
Update 2.4.3 change date
2019-11-05 12:21:00 +02:00
861e27eb00
Merge branch '2.3' into 2.4
2019-10-29 14:04:31 +02:00
df6c56e7ca
Update 2.3.13 Change Date
2019-10-29 12:51:31 +02:00
00feb61b23
MXS-2652 Do not clear maintenance flag when a server goes down
...
The set of flags to clear should be well-defined.
2019-09-06 09:43:32 +03:00
e6bf020b9e
Continue name resolution fixing, add unit test
...
name_lookup() now returns all results given by getnameinfo(). When searching
for a server, finding one matching address in the lookup-results is enough for
a match.
Also, added a test for name_lookup(). The test is minimal on its own, as hardcoded
test cases are not generally valid.
2019-08-16 12:52:52 +03:00
d4b712ae84
MXS-2546 Add DNS-resolving to topology detection
...
When matching hostnames between MaxScale server configuration and the
SHOW SLAVE STATUS-output, use DNS-resolution if a simple string comparison
doesn't find an answer. Results of the resolution are saved to avoid
repeating the operation for the same address.
2019-07-22 11:10:23 +03:00
5df1f2561c
MXS-2546 Save master server to slave connection object
...
Simplifies later checks and removes duplicate code. The "assume_unique_hostnames"-
setting is no longer required within the MariaDBServer-class.
2019-07-19 17:10:10 +03:00
0257e6e690
MXS-2546 Remove external master tracking
...
It was only used for logging.
2019-07-19 16:39:03 +03:00
0ba779d5a2
Update 2.4.0 Change Date
2019-06-25 10:11:55 +03:00
648eda9262
Remove deprecated parameters from MariaDBMon
...
Also deprecates an unused parameter.
2019-06-13 14:35:50 +03:00
4efa9dbeea
Remove maxscale/alloc.h
...
The remaining contents were moved to maxbase/alloc.h.
2019-06-10 14:11:25 +03:00
fc9ef715bd
Move last MariaDB-Monitor settings inside class
2019-06-07 11:42:21 +03:00
cf46004bd8
Make the servers-array in Monitor private
...
This prevents derived classes from modifying the array directly,
which would be unsafe.
2019-05-21 10:58:24 +03:00
4ee30f5c52
MXS-2169 Allow a downed server to be selected as topology master
...
This is required for the case when MaxScale is started when the master is
already down.
2019-05-17 13:46:33 +03:00
d2f3e56d0a
MXS-2169 Add 'enforce_simple_topology'-setting
...
Does not add any functionality yet.
2019-05-17 13:46:33 +03:00
c801789ff3
Cleanup monitor running state
2019-05-17 13:34:48 +03:00
476dc80bc9
Move settings shared between MariaDBMonitor and MariaDBServer to container
...
Removes the need to communicate these settings via call parameters.
2019-05-10 14:48:41 +03:00
d10c7a4140
Rearrange MariaDB-Monitor settings variables
...
Moves some of the settings to a dedicated container to separate them
from other fields.
2019-05-10 14:48:41 +03:00
a9b1e3a442
Move some Monitor fields to private and protected
...
None of the fields should be publicly writable and some should not even
be writable from derived classes.
2019-05-10 14:48:41 +03:00
418ccf861d
Format routers and monitors
2019-05-10 10:31:12 +03:00
3d420dee6f
MXS-2329 Use durations in MariaDB monitor
2019-04-30 13:02:53 +03:00
75c0ac5323
Move items from MonitorWorker to MonitorWorkerSimple
...
MonitorWorker only enforces the use of a worker thread but otherwise
does not define how the monitor is implemented.
2019-04-24 11:27:11 +03:00
067660e3e7
Merge branch '2.3' into develop
2019-04-16 16:55:12 +03:00
2ca9337da1
Merge branch '2.2' into 2.3
2019-04-16 16:34:57 +03:00
5ba305c2c1
MXS-2426 Do not permanently disable automatic cluster operations when they fail
...
Only disabled for "failcount" monitor ticks. Also turns some related log
messages to notices.
2019-04-16 11:26:34 +03:00
3c188bf421
Merge branch '2.3' into develop
2019-04-16 11:23:49 +03:00
f8a22d0ac0
MXS-2344 Add setting for enabling SSL for replication
...
If the monitor setting "replication_master_ssl" is set to on, any CHANGE MASTER TO-command
will have MASTER_SSL=1. If set to off or unset, MASTER_SSL is left unchanged to match existing
behaviour.
2019-04-15 19:15:45 +03:00
4c6306e363
Merge commit '5cdba97ec7ee7f1ef74249b952774adf1b111464' into develop
2019-03-22 13:25:58 +02:00
5cdba97ec7
Merge commit '216eb904c557509ea5a3216e68e274df957ab807' into 2.3
2019-03-22 10:48:31 +02:00
216eb904c5
MXS-1991 Allow replication_user and replication_password be set runtime
...
Because runtime changes are performed one at a time, adding replication credentials
to a mariadbmon which didn't have any would cause an error to be printed, and
the monitor would not start.
This is now fixed by allowing replication_user without replication_password. This
is not an ideal solution as a configuration file with only replication_user would be
accepted. Also, when adding the credentials to a monitor, replication_user must be
given first to avoid the error.
2019-03-21 17:06:24 +02:00
