d632c195ff
2.4.19 Update change date
2022-01-04 15:47:38 +02:00
2a54224927
2.4.18 Update change date
2021-10-29 08:29:51 +03:00
a8bfbbe254
2.4.17 Update change date
2021-03-08 09:03:02 +02:00
0224f24077
2.4.16 Update Change Date
2021-02-16 14:59:00 +02:00
c5bcf7a8b1
2.4.15 Update change date
2021-01-18 15:30:30 +02:00
072661e26b
MXS-3326 Fix hostname validation
...
A hyphen '-' is a valid character in a domain name, as long as it
is not the first character and does not appear two in a row.
2020-12-08 15:30:47 +02:00
d20ea5265f
MXS-3326 Add test that reveals problem
...
A hyphen '-' is a valid character in a domain name, as long as it
is not the first character and does not appear two in a row.
2020-12-08 15:26:41 +02:00
df36ef86d0
2.4.14 Update Change Date
2020-11-16 14:23:26 +02:00
faaf7f483e
2.4.13 Update Change Date
2020-10-14 09:15:46 +03:00
babcda3eca
2.4.12 Update Change Date
2020-08-24 09:42:48 +03:00
f3d4c27e58
Merge branch '2.3' into 2.4
2020-08-19 12:20:49 +03:00
b5fa26e8a6
MXS-3113: Log a message when log rotation is complete
...
This helps detect that writes to the new log file are working.
2020-08-19 12:15:25 +03:00
ce05b68030
Merge branch '2.3' into 2.4
2020-07-27 14:55:58 +03:00
ffb237628c
fix GCC 10 warnings
2020-07-27 10:42:38 +03:00
82b4315fa6
Merge branch '2.3' into 2.4
2020-07-24 14:25:29 +03:00
429d44e2d6
Add <stdexcept> to http.hh
...
Fixes a compile error with GCC 10.1.
2020-07-24 14:24:13 +03:00
39aa129fc5
Fix narrowing conversion warnings on GCC 10.1
...
Using an unsigned value in a switch with signed case values produced the
error.
2020-07-24 14:23:14 +03:00
fc9c9fcd77
2.4.11 Update change date
2020-07-07 10:01:38 +03:00
31591dbf00
MXS-3057: Fix session_trace
...
The log priority check must not check session trace as it is used inside
the logging code.
2020-07-01 11:12:32 +03:00
c8700a94ab
MXS-2900 Cleanup maxtest compilation
...
The cdc-connector source does not need to be included, linking is enough.
2020-06-12 20:08:40 +03:00
7781f7042a
2.4.10 Update change date
2020-06-05 10:21:37 +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
06bd6f1812
Merge branch '2.3' into 2.4
2020-05-04 21:10:51 +03:00
c34b835c51
Build maxbase tests only if BUILD_TESTS in on
2020-04-30 17:55:23 +03:00
321126660f
2.4.9 Update Change Date
2020-04-29 10:17:14 +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
5217836e83
Update 2.4.8 Change Date
...
Same as that of 2.3.17. Consequently, only the 2.4 specific files
are updated.
2020-03-16 11:25:59 +02: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
f576680ed9
Update 2.4.7 change date
...
Only the files that were not already updated as part of the
2.3.17 release.
2020-02-12 15:21:44 +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
41a07a4bd9
MXS-2801: Log INFO messages when session_trace is on
...
Since the session trace should contain all messages, the log priority
check should always return true when session_trace is on.
2020-01-27 15:39:39 +02:00
714dece7dd
Update 2.4.6 Change Date
...
We use same as for 2.3.16.
2020-01-21 13:22:25 +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
2c2363c639
MXS-2801: Log INFO messages when session_trace is on
...
Since the session trace should contain all messages, the log priority
check should always return true when session_trace is on.
2019-12-31 07:39:44 +02:00
4bde824021
MXS-2815: Downgrade O_DIRECT from warning to notice
...
There's no real action the user can take which is why it shouldn't be a
warning.
2019-12-20 10:59:08 +02:00
a9a2b753c0
Update 2.4.5 change date
2019-12-18 13:25:03 +02:00
41c1ce441a
fix bug in average
2019-12-16 09:36:20 +02:00
899e6db120
fix bug in average
2019-12-16 09:25:22 +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
4d513941a7
Merge commit '8ac11a97c29ac9ce3e4099e77a9aa9475c1002b4' into 2.4
2019-09-23 14:07:32 +03:00
8ac11a97c2
Extend pipe buffer size error message
...
The message now logs the instructions on how to increase the per-process
page limit for pipe buffers. This can happen if fs.pipe-max-size
multiplied by the number of workers exceeds the value of
fs.pipe-user-pages-soft multiplied by 4096.
2019-09-21 10:30:00 +03:00
6830f517b4
Improve message queue logging
...
Logging the pipe buffer size on startup will tell how large it was at the
time when MaxScale read it. If there are some abnormalities in it, this
will make it visible.
Logging the worker ID when the posting of a message fails will tell which
particular worker it was. For example, if the worker in question is the
main worker (i.e. ID 0), we know there's something that's blocking the
processing.
2019-09-21 09:43:12 +03:00
