[
https://issues.apache.org/jira/browse/GEODE-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146712#comment-17146712
]
ASF subversion and git services commented on GEODE-8310:
--------------------------------------------------------
Commit 63a245bf878b68dc466223ad0f02318455f5e7b0 in geode's branch
refs/heads/develop from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=63a245b ]
GEODE-8310: remove numThreads redis sys prop (#5311)
* removed the numThreads redis sys prop
* also simplified initialization of the NettyRedisServer to have
all final instance fields and do all its initialization in the constructor.
> remove the gemfireredis.numthreads system property
> --------------------------------------------------
>
> Key: GEODE-8310
> URL: https://issues.apache.org/jira/browse/GEODE-8310
> Project: Geode
> Issue Type: Improvement
> Components: redis
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Fix For: 1.14.0
>
>
> Currently the geode redis server allows the number of netty threads to be
> changed by a user who sets the "gemfireredis.numthreads" system property. No
> testing of this sys prop has been done and if it is set to 0 it causes geode
> redis to use some deprecated old IO netty apis.
> It also turns out netty has its own system property it uses to determine the
> default number of threads. It is:
> "io.netty.eventLoopThreads"
> So the plan is to remove "gemfireredis.numthreads" and use netty's default
> behavior.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
