You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Alberto Gomez (Jira)" <ji...@apache.org> on 2022/05/25 06:59:00 UTC

[jira] [Updated] (GEODE-10155) ServerConnection thread hangs when client function execution times-out

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

Alberto Gomez updated GEODE-10155:
----------------------------------
    Description: 
If a Geode client executes a non-HA server function (isHA=false) with a timeout

and

the function is handled in the Geode server by a "Function Execution Processor" thread (for example by calling the function with onRegion() on a partitioned region without a filter)

and

the function times-out before the server has answered back with all the results

then

the ServerConnection thread that originally started to handle the function execution will be stuck forever.

 

If this happens several times and the max-threads parameters is set to a value greater than 0, the server will eventually run out of ServerConnection threads and will not be able to process more client requests.

 

  was:
If a Geode client executes a server function with a timeout

and

the function is handled in the Geode server by a "Function Execution Processor" thread (for example by calling the function with onRegion() on a partitioned region without a filter)

and

the function times-out before the server has answered back with all the results

then

the ServerConnection thread that originally started to handle the function execution will be stuck forever.

 

If this happens several times and the max-threads parameters is set to a value greater than 0, the server will eventually run out of ServerConnection threads and will not be able to process more client requests.

 


> ServerConnection thread hangs when client function execution times-out
> ----------------------------------------------------------------------
>
>                 Key: GEODE-10155
>                 URL: https://issues.apache.org/jira/browse/GEODE-10155
>             Project: Geode
>          Issue Type: Bug
>          Components: core, functions
>            Reporter: Alberto Gomez
>            Assignee: Alberto Gomez
>            Priority: Major
>              Labels: pull-request-available
>
> If a Geode client executes a non-HA server function (isHA=false) with a timeout
> and
> the function is handled in the Geode server by a "Function Execution Processor" thread (for example by calling the function with onRegion() on a partitioned region without a filter)
> and
> the function times-out before the server has answered back with all the results
> then
> the ServerConnection thread that originally started to handle the function execution will be stuck forever.
>  
> If this happens several times and the max-threads parameters is set to a value greater than 0, the server will eventually run out of ServerConnection threads and will not be able to process more client requests.
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)