You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dave Barnes (Jira)" <ji...@apache.org> on 2021/09/07 18:02:00 UTC

[jira] [Assigned] (GEODE-9558) State in the documentation that function executions do not honor the conserve-sockets setting

     [ https://issues.apache.org/jira/browse/GEODE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Barnes reassigned GEODE-9558:
----------------------------------

    Assignee: Dave Barnes

> State in the documentation that function executions do not honor the conserve-sockets setting
> ---------------------------------------------------------------------------------------------
>
>                 Key: GEODE-9558
>                 URL: https://issues.apache.org/jira/browse/GEODE-9558
>             Project: Geode
>          Issue Type: Bug
>          Components: docs
>            Reporter: Alberto Gomez
>            Assignee: Dave Barnes
>            Priority: Major
>
> According to [https://community.pivotal.io/s/article/GemFire-Function-Executions-and-conserve-sockets-behavior?language=en_US:]
> "even with conserve-sockets set to false, function executions do not use this setting and defaults to conserve-sockets=true behavior, regardless of the conserve-sockets setting.
>  
> And according to: [https://medium.com/swlh/threads-used-in-apache-geode-function-execution-9dd707cf227c#bd8c]
> "a Function Execution Processor does not honor the conserve-sockets setting so a shared P2P message reader is used in the remote server"
>  
> This information is not present in the current Geode documentation when describing the conserve-sockets property.
> This information must be added together with the information on how to set conserve-sockets in function executions (see the first link above).
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)