GEODE-7361: sever ties to PoolStatHelper & CoreLoggingExecutors #4238
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
Bill
force-pushed
the
feature/GEODE-7361
branch
from
6fe89d7
to
5d4216e
Compare
Bill
force-pushed
the
feature/GEODE-7361
branch
from
5d4216e
to
12a68c1
Compare
dschneider-pivotal
approved these changes
Oct 29, 2019
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.
GEODE-7361
As part of the effort to sever dependencies on
geode-coreingeode-membershipwe are severing ties ongeode-coreinTcpServer. This PR eliminates two such dependencies ongeode-coreinTcpServer:PoolStatsHelperCoreLoggingExecutorsFormerly, the
TcpServerconstructor took aPoolStatHelper poolHelperparameter.TcpServerretained that parameter. It then constructed a newExecutorServiceviaCoreLoggingExecutors.newThreadPoolWithSynchronousFeed(). In theTcpServer.restarting()method it also had to create anExecutorServicethe same way.This PR changes the
TcpServerconstructor to take aSupplier<ExecutorService>. That supplier hides both thePoolStatHelperclass and theCoreLoggingExecutorsclass (fromTcpServer).For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
Has your PR been rebased against the latest commit within the target branch (typically
develop)?Is your initial contribution a single, squashed commit?
Does
gradlew buildrun cleanly?Have you written or updated unit tests to verify your changes?
If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.