Refactor: Get the max allowed RT directly from SentinelConfig.statisticMaxRt() #1173
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe what this PR does / why we need it
Get the max allowed RT directly from
SentinelConfig.statisticMaxRt()
, to avoid the class dependency chain:Constants -> SentinelConfig
. TheConstants
class should not depend on any classes that could trigger static initialization.Does this pull request fix one issue?
NONE
Describe how you did it
TIME_DROP_VALUE
inConstants
class (which was resolved withSentinelConfig.statisticMaxRt()
)SentinelConfig.statisticMaxRt()
Describe how to verify it
Run the test cases.
Special notes for reviews
NONE