7d49d1ee5c
feat: add dns.record_type config for cluster discovery
2022-06-16 08:59:09 +02:00
67b8e6c3bd
test: add a script to test dns cluster node discovery
2022-06-16 01:34:16 +02:00
d35b95d00f
refactor: remove dns.app config
2022-06-16 00:11:41 +02:00
05782c4e4e
refactor: delete k8s.app_name config
2022-06-16 00:11:41 +02:00
be7724b4e7
chore: add emqx-example-en.conf in release
2022-06-15 22:45:43 +08:00
219f159fe7
Merge pull request #8219 from qzhuyan/dev/william/emqx-conf-vm-args
...
chore(conf): mv some default val of vmargs to emqx_conf
2022-06-15 14:14:57 +02:00
c371dd2464
Merge pull request #8202 from zmstone/0613-fix-no-alarm-when-init-rpc-call-failed
...
fix(cluster_rpc): no alarm when failed to initiate RPC call
2022-06-15 11:36:58 +01:00
efed970aab
chore(conf): mv some default val of vmargs to emqx_conf
2022-06-15 09:06:06 +02:00
7961f9206b
Merge pull request #8205 from qzhuyan/dev/william/emqx-conf-vm-args
...
fix(emqx_conf): add missing vm.args
2022-06-14 23:23:07 +02:00
2ec1a5bdb8
fix(emqx_conf): add missing vm.args
...
- process_limit
- max_ports
- dist_buffer_size
- max_ets_tables
2022-06-14 10:31:29 +02:00
c72a0c386f
fix: set retry interval to 1s in test cases
2022-06-14 10:34:33 +08:00
f4f263f91e
fix: change the default retry_interval of cluster_rpc call to 1min
2022-06-13 22:52:51 +08:00
e2ba1f1538
refactor: refuse initiating cluster call from stale node
2022-06-13 16:50:19 +02:00
7e98bd7d2f
fix(cluster_rpc): no alarm when failed to initiate a new cluster call
2022-06-13 15:56:00 +02:00
8518e71db1
Merge pull request #8182 from zmstone/0611-fix-config-update-race-condition
...
fix(cluster_rpc): config update race condition
2022-06-13 11:46:08 +01:00
2065be569e
fix(emqx_cluster_rpc): fail fast on stale state
...
Due to:
* Cluster RPC MFA is not idempotent!
* There is a lack of rollback for callback's side-effects
For instance, when two nodes try to add a cluster-singleton
concurrently, one of them will have to wait for the table lock
then try to catch-up, then try to apply MFA.
The catch-up will have the singleton created, but the initiated
initiated multicall apply will fail causing the commit to rollback,
but not to 'undo' the singleton creation.
Later, the retries will fail indefinitely.
2022-06-12 20:18:48 +02:00
0e06e4acaa
fix(emqx_conf): throw exception on clusetr_call falure
...
Not all callers handle error, some even ignore errors!
2022-06-12 20:18:48 +02:00
4fdd793071
refactor: move config template file to rel dir
2022-06-12 19:57:08 +02:00
86c1610d26
Merge pull request #8039 from gsychev/multinode_helper
...
Multinode helper
2022-06-10 13:10:38 +00:00
146b8f34aa
fix(spell): please the spell check
2022-06-10 14:22:40 +08:00
b0cd83254d
fix: schema and desc for time_offset of the log handlers
2022-06-09 17:59:35 +08:00
c29eb8a409
feat(testing): Multinode testing helper
2022-06-09 13:33:01 +04:00
eb2a4df4af
feat: change node.applications default to []
2022-06-07 10:19:26 +08:00
c7cc2e85b2
fix: add default&example for schema
2022-06-06 09:52:10 +08:00
6c9b959651
fix: ct failed
2022-05-31 19:20:27 +08:00
26a57a00bb
fix: cluster crash
2022-05-31 19:20:27 +08:00
1345b7e993
chore: bump hocon to 0.28.0
2022-05-31 19:20:27 +08:00
86113f3494
chore: don't gen example.conf in v5.0.0
2022-05-31 19:20:27 +08:00
9ec804ae03
feat: generate example.conf from schemas
2022-05-31 19:20:27 +08:00
8519b161dc
chore: replace = by : in conf
2022-05-31 19:20:27 +08:00
8aa60cc0a5
feat: generate a minimized emqx.conf
2022-05-31 19:20:27 +08:00
b456ef711c
fix: always commit to TargetTnxId when init
2022-05-30 16:35:14 +08:00
d0c5de1da6
chore(config): move db configs under cluster/node keys
2022-05-26 14:02:22 -03:00
09e5f35f5c
fix: include ref's desc
2022-05-12 16:17:03 +08:00
426a829ee0
docs: more clear about stop plugins error.
2022-05-11 22:13:44 +08:00
e0054f6a4e
Merge pull request #7906 from thalesmg/doc-hide-per-shard
...
docs: hide shard transport config from docs
2022-05-11 11:02:48 -03:00
135cf4fac2
docs: hide shard transport config from docs
...
Those configurations are too "magical" for the average user, and
keeping them in the docs might confuse users.
2022-05-10 11:40:49 -03:00
7c34c8a8b1
fix: retry if init_disaptch failed
2022-05-10 09:38:48 +08:00
bef00b461e
chore: update .gitignore emqx_conf generated files
2022-04-29 16:43:51 +08:00
4f36a5152a
chore: rename log_file_handlers's label
2022-04-29 11:45:22 +08:00
1be9d4f48f
Merge pull request #7731 from thalesmg/fix-copy-conf-override-startup
...
fix(emqx_conf): avoid crash/deadlock depending on node startup order
2022-04-27 10:01:06 -03:00
55be66a5eb
feat: add self node to /cluster
2022-04-27 13:55:42 +08:00
a99c49e75f
fix: limit file ^[/\_a-zA-Z0-9\.\-]*$
2022-04-27 13:55:42 +08:00
8cfcb10c7e
fix: make logger config options more specific
2022-04-27 13:55:42 +08:00
67ed7ba7b8
refactor: do not differentiate node roles
2022-04-26 12:14:38 -03:00
8519948742
refactor: use macro to denote initial transaction id
2022-04-26 12:03:53 -03: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
4b763a3a12
Merge pull request #7742 from zhongwencool/schema-namespace
...
fix: add namespace to schema
2022-04-26 09:26:04 +08:00
a4feb3e6e9
style: reformat emqx_auto_subscribe and emqx_conf
2022-04-25 18:05:10 +02:00
184554246c
Merge pull request #7746 from EMQ-YangM/fix_docs
...
fix: modify the error statement
2022-04-25 09:31:31 +08:00
Zaiming (Stone) Shi