check for less than zero start and end time#7372
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7372 +/- ##
=============================================
- Coverage 70.40% 32.14% -38.26%
+ Complexity 3307 93 -3214
=============================================
Files 1515 1506 -9
Lines 75008 74660 -348
Branches 10910 10872 -38
=============================================
- Hits 52808 24000 -28808
- Misses 18572 48583 +30011
+ Partials 3628 2077 -1551
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
|
What broke because of this? Was this something that happened due to the recent re-factor of metadata? |
Due to the previous change in #7255 didn't check for negative start/end time. |
|
OK, so the periodic tasks start to throw exception on refresh tables and we see exception logs in the controller because of PR #7255 |
(cherry picked from commit 2302bd2)
|
Is the issue caused by some old segment ZK metadata set negative start/end time and null time unit? |
|
|
Description
Check for the "-1" start time in some use cases
Upgrade Notes
Does this PR prevent a a zero-downtime upgrade?
No
Does this PR fix a zero-downtime upgrade introduced earlier?
No