-
Notifications
You must be signed in to change notification settings - Fork 188
Conversation
Codecov Report
@@ Coverage Diff @@
## release-1.0 #704 +/- ##
==============================================
Coverage 57.9412% 57.9412%
==============================================
Files 166 166
Lines 16981 16981
==============================================
Hits 9839 9839
Misses 6187 6187
Partials 955 955 |
/run-all-tests |
@GMHDBJD PTAL |
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
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
@@ -101,8 +101,8 @@ function run() { | |||
# use sync_diff_inspector to check data now! | |||
check_sync_diff $WORK_DIR $cur/conf/diff_config.toml | |||
|
|||
check_metric $WORKER1_PORT 'dm_syncer_replication_lag{task="test"}' 3 0 1 | |||
check_metric $WORKER2_PORT 'dm_syncer_replication_lag{task="test"}' 3 0 1 | |||
check_metric $WORKER1_PORT 'dm_syncer_replication_lag{task="test"}' 3 0 2 |
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.
why need to increase the upper
to 2
? It seems that use UTC_TIMESTAMP(6)
to replace UTC_TIMESTAMP
when update ts will decrease the replication lag.
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.
I saw lag with 1.x (but < 1.5) in some cases. in the old UTC_TIMESTAMP
it ==1
, but now it > 1
.
LGTM |
What problem does this PR solve?
What is changed and how it works?
UTC_TIMESTAMP(6)
to replaceUTC_TIMESTAMP()
Check List
Tests
Related changes