-
Notifications
You must be signed in to change notification settings - Fork 188
Conversation
…rtise # Conflicts: # tests/_utils/run_dm_worker
/run-all-tests tidb=release-3.0 |
@WangXiangUSTC @lichunzhu PTAL |
advertise-addr
for DM-workeradvertise-addr
for DM-worker
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rest LGTM
@@ -25,7 +25,7 @@ PWD=$(pwd) | |||
echo "[$(date)] <<<<<< START DM-WORKER on port $port, config: $conf >>>>>>" | |||
cd $workdir | |||
$binary -test.coverprofile="$TEST_DIR/cov.$TEST_NAME.worker.$port.$(date +"%s").out" DEVEL \ | |||
--worker-addr=:$port \ | |||
--worker-addr=0.0.0.0:$port \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to check the host? 0.0.0.0:$port
will become the advertise-addr
, but it can not be used by dm-master
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 addressed in 2024c7c.
- add the check for
0.0.0.0
as theadvertise-addr
- add
advertise-addr
when running dm-worker in tests.
/run-all-tests tidb=release-3.0 |
LGTM |
There same to be some problem with |
/run-all-tests tidb=release-3.0 |
Yes, the problem was introduced when merging changes from for other PR, and I've updated in d6f8084. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What problem does this PR solve?
DM-worker may listen on some special address (like
0.0.0.0:8262
) in a k8s pod, when registering it into the DM-master cluster, the DM-master may not access it with this special address.What is changed and how it works?
advertise-addr
config item for DM-worker to handle client traffic.Check List
Tests
Code changes
Related changes
dm/dm-ansible