027c05af99
test(emqx_channel): fix two flaky tests
2022-11-27 13:15:06 +01:00
f3fd906043
chore: bump emqx app vsn
2022-11-27 09:18:56 +01:00
51c532546c
feat: options for trigger disconnected events by different reasons
2022-11-03 16:43:34 +08:00
e0db524a10
refactor: change the format of auth_order and acl_order configs
2022-11-02 11:49:55 +01:00
52652f6c96
feat(hooks): add config options to set explicit callback order
2022-11-01 19:39:52 +01:00
4614167488
Merge pull request #9234 from savonarola/update-emqx-cm
...
chore(cm): sync emqx_cm with ee
2022-10-28 14:09:06 +02:00
e66e563648
fix(logger): add new macro `?LOG_SENSITIVE` and use it to replace some `?LOG` for security reason
...
some arguments passed to external API may contain sensitive data, when the API execution fails, sensitive data may be returned as a part of the failure reason, if this reason printed to the log, it will lead to sensitive data leakage, so we should check carefully and scan these failed returns
2022-10-26 17:14:46 +08:00
cc468dca4e
chore(cm): sync emqx_cm with ee
2022-10-26 11:49:22 +03:00
e0e8a5a707
chore: re-generate appup for v4.3.22
2022-10-20 10:37:32 +08:00
8adddb018f
Merge remote-tracking branch 'emqx/release-v43' into 1020-sync-release-v43-back-to-main
2022-10-20 10:23:08 +08:00
73a5462cba
fix(shared): do not redispatch shared messages for certain shutdown
...
For takeover, there should be no message re-dispatch because
the messages will be retried by the new session.
For kick, messages should not be re-dispatched for security reason.
i.e. if admin has identified that there are malicious messages
stored in persisted sessions, killing the session should not
cause messages to be re-dispatched
2022-10-19 17:21:56 +02:00
11026b7644
chore: re-generate appup for v4.3.22
2022-10-16 08:43:45 +02:00
20e0d14026
chore: bump app versions
2022-10-15 15:01:57 +02:00
1ba2c01f25
Merge remote-tracking branch 'origin/release-v43' into main-v4.3
2022-10-15 14:58:22 +02:00
198a1ed6cb
Merge remote-tracking branch 'origin/main-v4.3' into main-v4.3
2022-10-13 08:54:26 +02:00
e57ab9a8c1
fix: remsh prefix may not include an underscore
2022-10-12 12:42:37 +02:00
73d72eacce
fix: demote rate limit log level to notice
2022-10-11 13:05:21 +02:00
124f9795cd
Merge pull request #9091 from zmstone/1003-no-shutdown-logging-to-remote-node-when-rpc
...
fix(emqx): emqx:shutdown should not log to remote node
2022-10-11 08:12:28 +02:00
a1affa94b5
Merge pull request #9045 from HJianBo/enhance-flapping-detect
...
refactor: enhance the flapping detect accuracy
2022-10-11 10:10:47 +08:00
edf69cee88
feat: mute emqx shutdown log in rpc calls
2022-10-10 17:57:33 +02:00
48d8f7e7a9
fix(channel): add warning log if the acl check of a subscribed topic failed
2022-10-10 16:03:31 +08:00
2f178fa8f1
Merge branch 'release-v43' into enhance-flapping-detect
2022-10-10 09:40:49 +08:00
4f8a7349bf
fix(shared): ensure sticky strategy sticks to the first pick
...
Prior to this fix, the alive pids are never inserted due to a
missing insert when handing remote pids from mnesia event.
2022-10-09 20:18:33 +02:00
b2b05c0077
Merge remote-tracking branch 'origin/release-v43' into 1009-fix-sticky-dispatch-should-check-subscription-table
2022-10-09 11:43:14 +02:00
8e8ff08973
fix(shared): check sticky if sticky pid is still a member
...
Prior to this fix, in case of a subscriber unsubscribes without
disconnect, the sticky dispatch strategy will continue to pick the
old member.
This commit fixes it by checking if the member is still in the
group
2022-10-09 11:31:54 +02:00
e2b0048e88
refactor(flapping): count flapping event if connecting failed
2022-10-08 10:06:20 +08:00
13f3dafe22
refactor: enhance the flapping detect accuracy
...
Count the `flapping` event as long as a client try to connect to server
whatever it suceed or failed. It is more helpful to improve
stablebility.
2022-10-08 09:56:23 +08:00
d23dfcca39
fix(shared): only re-dispatch QoS1 inflights
2022-10-05 16:03:43 +02:00
09b08d092d
chore: revert double exported pmap after merge
2022-10-05 15:10:10 +02:00
8d42589bf5
chore: update appup
2022-10-05 13:32:48 +02:00
d46393c45c
Merge remote-tracking branch 'origin/release-v43' into 1004-fix-wildcard-redispatch-for-shared-subs
2022-10-05 12:42:03 +02:00
3339df8b24
test: Add test case to cover shared sub QoS2 pubrel in inflights
2022-10-05 12:38:12 +02:00
6769bd4edc
fix(shared): drop pubrel from inflight collection before redispatch
2022-10-05 10:30:59 +02:00
ba1c276c75
fix(typespec): fix type spec for emqx_shared_sub:redispatch_to
2022-10-05 10:04:09 +02:00
9989f4df7e
chore: fix shared subscription redispatch
2022-10-04 18:15:45 +02:00
366999ccbb
Merge remote-tracking branch 'origin/release-v43' into main-v4.3
2022-10-02 11:25:16 +02:00
ebf131266a
test: fix flaky shared sub test case
...
the route replication is async, added a function to wait for it
2022-09-30 17:22:58 +02:00
07f0f0a5f8
Merge remote-tracking branch 'origin/release-v43' into 0921-build-merge-release-br-back-to-main-asap
2022-09-29 10:56:45 +02:00
527ce097aa
feat: add emqx_secret module
2022-09-27 21:18:07 +02:00
2e0eae54f8
fix(acl): check ACL before publishing last will testament (lwt) message (4.3)
2022-09-26 15:22:29 -03:00
1379f39f26
chore: sync from release-e4.3
2022-09-22 18:02:39 +08:00
9642f25ea0
chore: update changelog
2022-09-22 15:12:31 +08:00
27983e7df4
chore: update emqx.appup.src
2022-09-22 14:24:59 +08:00
61d745a230
feat: add emqx_misc:ipv6_probe/2 function
2022-09-22 11:00:16 +08:00
c2f1f1aab8
chore: rename on_xxx_hooks to on_xxx
2022-09-22 10:04:52 +08:00
362c176d24
chore: update appup.src
2022-09-22 10:02:48 +08:00
4635d52273
chore: add reboot_hook/shutdown_hook for enterprise
2022-09-22 10:02:00 +08:00
90995069c6
chore(auth_mongo): bump appup
2022-09-21 14:46:17 -03:00
83fb479311
chore: port `pmap/nolink_apply` features from master
2022-09-21 14:03:44 -03:00
cdadc8ad44
chore: update appup src
2022-09-19 14:53:41 +02:00
Zaiming (Stone) Shi