[
https://issues.apache.org/jira/browse/GEODE-8295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145781#comment-17145781
]
ASF subversion and git services commented on GEODE-8295:
--------------------------------------------------------
Commit a89dbea6fb631fe6c2d912c8f00426202fd8bdf5 in geode's branch
refs/heads/develop from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a89dbea ]
GEODE-8295: refactor GeodeRedisServer (#5289)
* removed main thread from GeodeRedisServer
* removed NamedThreadFactory in favor of geode's LoggingThreadFactory.
* now uses LoggingExecutors instead of Executors.
* removed logLevel since it is configured by gemfire
* A cache is now passed to the GeodeRedisServer constructor; it no longer
creates its own
* region initialization now done in RegionProvider
* extracted passive expiration code
* extracted netty server code
* changed passive expiration to use scheduleWithFixedDelay
> refactor/cleanup GeodeRedisServer
> ---------------------------------
>
> Key: GEODE-8295
> URL: https://issues.apache.org/jira/browse/GEODE-8295
> Project: Geode
> Issue Type: Improvement
> Components: redis
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Fix For: 1.14.0
>
>
> Here are some things to do to cleanup GeodeRedisServer:
> # remove main thread from GeodeRedisServer
> # remove NamedThreadFactory in favor of geode's LoggingThreadFactory and
> LoggingExecutors
> # remove logLevel since it is configured by gemfire
> # pass an existing cache to the GeodeRedisServer constructor
> # do region creation and initialization in RegionProvider
> # extract passive expiration code
> # extract netty server code
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
