-
Notifications
You must be signed in to change notification settings - Fork 639
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
[ISSUE #4674] Add a run log for the ThreadPoolExecutor #4673
base: master
Are you sure you want to change the base?
[ISSUE #4674] Add a run log for the ThreadPoolExecutor #4673
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #4673 +/- ##
============================================
+ Coverage 17.28% 17.37% +0.09%
- Complexity 1742 1759 +17
============================================
Files 792 798 +6
Lines 29703 29821 +118
Branches 2567 2581 +14
============================================
+ Hits 5134 5182 +48
- Misses 24095 24158 +63
- Partials 474 481 +7 ☔ View full report in Codecov by Sentry. |
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.
@karsonto Thanks for your contribution. Please create a issue to describe you idea and link this pr to it.
@mxsm thanks for your reminder,I created issue and link this PR. |
|
||
public static ThreadPoolExecutor createThreadPoolExecutor(int core, int max, BlockingQueue<Runnable> blockingQueue, | ||
final String threadName, final boolean isDaemon) { | ||
return new ThreadPoolExecutor(core, max, 10 * 1000, TimeUnit.MILLISECONDS, blockingQueue, | ||
return new LogThreadPoolExecutor(core, max, 10 * 1000, TimeUnit.MILLISECONDS, blockingQueue, |
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.
These two createThreadPoolExecutor
methods are used by EventMeshGrpcServer
and HTTPThreadPoolGroup
. Why their return type should be changed to LogThreadPoolExecutor
?
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.
Returning the LogThreadPoolExecutor can lay the groundwork for subsequent monitoring.
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.
May you please describe the subsequent monitoring features to be implemented?
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.
@karsonto Can you elaborate on the subsequent use of this design? For example, how and where it will be used in detail?
I have reviewed the source code and found that this class is used in many places. Using this class allows you to print exception information in the log of the thread and also to print information about closing the thread pool. |
It has been 60 days since the last activity on this pull request. I am reaching out here to gently remind you that the Apache EventMesh community values every pull request, and please feel free to get in touch with the reviewers at any time. They are available to assist you in advancing the progress of your pull request and offering the latest feedback. If you encounter any challenges during development, seeking support within the community is encouraged. We sincerely appreciate your contributions to Apache EventMesh. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4673 +/- ##
============================================
+ Coverage 17.28% 17.37% +0.09%
- Complexity 1742 1759 +17
============================================
Files 792 798 +6
Lines 29703 29821 +118
Branches 2567 2581 +14
============================================
+ Hits 5134 5182 +48
- Misses 24095 24158 +63
- Partials 474 481 +7 ☔ View full report in Codecov by Sentry. |
It has been 60 days since the last activity on this pull request. I am reaching out here to gently remind you that the Apache EventMesh community values every pull request, and please feel free to get in touch with the reviewers at any time. They are available to assist you in advancing the progress of your pull request and offering the latest feedback. If you encounter any challenges during development, seeking support within the community is encouraged. We sincerely appreciate your contributions to Apache EventMesh. |
It has been 60 days since the last activity on this pull request. I am reaching out here to gently remind you that the Apache EventMesh community values every pull request, and please feel free to get in touch with the reviewers at any time. They are available to assist you in advancing the progress of your pull request and offering the latest feedback. If you encounter any challenges during development, seeking support within the community is encouraged. We sincerely appreciate your contributions to Apache EventMesh. |
Fixes #4674
Motivation
Explain the content here.
Explain why you want to make the changes and what problem you're trying to solve.
Modifications
Describe the modifications you've done.
Documentation