You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/06/27 01:03:00 UTC
[jira] [Commented] (GEODE-8310) remove the gemfireredis.numthreads
system property
[ https://issues.apache.org/jira/browse/GEODE-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146711#comment-17146711 ]
ASF GitHub Bot commented on GEODE-8310:
---------------------------------------
dschneider-pivotal merged pull request #5311:
URL: https://github.com/apache/geode/pull/5311
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> 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
>
> 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)