You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Owen Nichols (Jira)" <ji...@apache.org> on 2022/06/22 20:46:01 UTC

[jira] [Closed] (GEODE-9613) Investigate the effect of putting re-auth in ClientCacheUpdater in a different thread

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

Owen Nichols closed GEODE-9613.
-------------------------------

> Investigate the effect of putting re-auth in ClientCacheUpdater in a different thread
> -------------------------------------------------------------------------------------
>
>                 Key: GEODE-9613
>                 URL: https://issues.apache.org/jira/browse/GEODE-9613
>             Project: Geode
>          Issue Type: Sub-task
>          Components: core
>            Reporter: Jinmei Liao
>            Assignee: Jinmei Liao
>            Priority: Major
>              Labels: GeodeOperationAPI
>             Fix For: 1.15.0
>
>
> Currently, when client receives a "re-authenticate" message, it's doing re-authentication in the updater thread, the updater is blocked until the re-auth returned. It seems ok since theoretically the updater won't receive any further message from the server until the re-auth succeeds anyway. But investigate what's the benefit of putting re-auth in another thread.



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