yuanbiao
/
emqx
1
0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(eval): use running node for rpc eval, not a fresh one 

With the previous arguments, a fresh hidden node with the same name as
the expected running one was being started and commands were being run
there.  This caused commands like `ekka_cluster:info()` to report
seemingly weird results.
This commit is contained in:
Thales Macedo Garitezi 2022-01-06 17:24:47 -03:00
parent f24b3f416e
commit 03e0c5ef2a
No known key found for this signature in database
GPG Key ID: DD279F8152A9B6DD
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
bin/emqx
View File

@ -864,10 +864,12 @@ case "${COMMAND}" in
then then
"$REL_DIR/elixir" \ "$REL_DIR/elixir" \
--hidden \ --hidden \
--name "rand-$(relx_gen_id)-$NAME" \
--cookie "$COOKIE" \ --cookie "$COOKIE" \
--boot "$REL_DIR/start_clean" \ --boot "$REL_DIR/start_clean" \
--boot-var RELEASE_LIB "$ERTS_LIB_DIR" \ --boot-var RELEASE_LIB "$ERTS_LIB_DIR" \
--vm-args "$(latest_vm_args 'EMQX_NODE__NAME')"\ --vm-args "$REL_DIR/remote.vm.args" \
--erl "-start_epmd false -epmd_module ekka_epmd" \
--rpc-eval "$NAME" "$@" --rpc-eval "$NAME" "$@"
else else
relx_nodetool "eval" "$@" relx_nodetool "eval" "$@"