optimize: abnormal global transactions, output logs according to frequency #2523
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## develop #2523 +/- ##
=============================================
- Coverage 51.45% 51.42% -0.04%
+ Complexity 2808 2805 -3
=============================================
Files 553 553
Lines 17691 17699 +8
Branches 2088 2089 +1
=============================================
- Hits 9103 9101 -2
- Misses 7735 7743 +8
- Partials 853 855 +2
|
slievrly
reviewed
Apr 12, 2020
|
|
||
| StackTraceLogger.warn(LOGGER, | ||
| new RuntimeException("rm client is not connected. dbkey:" + resourceId + ",clientId:" + clientId), | ||
| "rm client is not connected. dbkey: {},clientId: {}", new String[] {resourceId, clientId}); |
funky-eyes
force-pushed
the
optimize_rm_not_connected
branch
from
df6b8ce
to
4ae665f
Compare
funky-eyes
changed the title
funky-eyes
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 did
optimize log output when rm client disconnects abnormally
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews