-
Notifications
You must be signed in to change notification settings - Fork 1k
Fix artificially high ping latency in MySQL backend monitoring #5199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
rahim-kanji
wants to merge
4
commits into
v3.0
Choose a base branch
from
v3.0_refactor_monitoring_ping
base: v3.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
1c3c429
Improve ping accuracy
rahim-kanji 50fae0b
Current check on file descriptors (fd) is not reliable or necessary
rahim-kanji 6a80c3f
Implemented explicit task memory ownership management in Monitor_Poll.
rahim-kanji 24e02e9
Changing monitor ping poll() timeout to 10ms
rahim-kanji File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
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.
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.
Using
= defaultfor the destructor is a good modern C++ practice. However, the current design requires the user ofWorkItem(likeConsumerThread) to manually delete the pointers stored in thedatavector. This separates resource acquisition (new WorkItem(...)) from resource release (delete ptr; ... delete item;), which can be error-prone.To improve encapsulation and adhere more closely to RAII principles, consider making
WorkItemresponsible for the memory it conceptually owns. You could implement a custom destructor to delete the pointers.