22f7cc1622
test: replace 'slave' and 'ct_slave' with 'peer'
2023-12-01 08:07:09 +01:00
c4ba558ee3
fix: unset config_loader in emqx's env when stop emqx app
2023-07-10 11:06:08 +08:00
fe0b8cfbaf
test(conf): respect `init_config_load_done` in emqx_conf itself
...
This should make task of configuring various applications (emqx_conf
/ emqx) during testsuites setup much simpler.
2023-07-04 13:20:02 +02:00
acd6e5635b
fix(ct): adapt cluster setup helper to replicant nodes
...
Before this change, trying to start cluster consisting of cores +
replicants resulted in error joining replicant node to the cluster.
2023-06-15 00:50:15 +03:00
4a9f2247ca
test(conf_app): fix bad merge conflict
2023-06-09 11:06:54 -03:00
20a7ce64cd
Merge pull request #10919 from thalesmg/test-flakiness-20230601-a
...
test(pulsar_producer): attempt to fix flaky test
2023-06-09 09:30:30 -03:00
2c97ee1b3f
test(conf_app): fix test after common test helpers changes
2023-06-06 09:32:38 -03:00
332daabcc5
fix(config): Do not sync cluster config from nodes running new version
2023-05-31 20:34:25 +02:00
8facd130f6
chore: update cluster_hocon_file/0 function
2023-04-14 23:19:38 +08:00
c0e6e79bcd
feat: don't remove default value when save config
2023-04-14 21:17:34 +08:00
fa753cf333
fix: failed ct test
2023-04-14 20:51:58 +08:00
7f870257b2
test: fix failed ct
2023-04-14 20:51:58 +08:00
180f571765
feat: configuration priority ENV > emqx.conf > API
2023-04-14 20:51:58 +08:00
b9e92173cf
test: improve cluster helper
...
1) Make each node have its own isolated data dir to avoid false
negatives.
2) Allow parameterizing the peer module.
3) Fix cluster RPC after a node joins the cluster.
2023-03-16 13:42:59 -03:00
b07befbf56
test: conf_app ct failed
2023-01-14 01:03:57 +08:00
dbc10c2eed
chore: update copyright year 2023
2023-01-02 09:22:27 +01:00
c301c8e992
chore: drop few unused macros / includes
2022-12-16 13:45:04 +03:00
64ab4ca025
test: add copy data dir test case
2022-12-05 16:25:28 +08:00
c29eb8a409
feat(testing): Multinode testing helper
2022-06-09 13:33:01 +04:00
6b969c5c84
fix(emqx_conf): avoid crash/deadlock depending on node startup order
...
Depending on the order that a cluster of core nodes might be stopped
and then restarted, there might be a deadlock or crash during the
configuration loading. The nodes try to check with each other which
has the latest cluster overrides and copy that info. However, in some
cases, Mnesia on node A might still think that it needs to consult
another node C that is still down, so that this node proceeds with its
boot sequence but `mnesia:wait_for_tables` in `emqx_cluster_rpc` is
stuck. Meanwhile, a node B can come up, try to copy from the sole
online node A, and fail because it's not ready yet.
2022-04-26 12:03:53 -03:00
Zaiming (Stone) Shi