[JBoss JIRA] (WFLY-13637) Invalidation caches need to consider keys in the cache store when reassigning ownership
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-13637:
-----------------------------------
Summary: Invalidation caches need to consider keys in the cache store when reassigning ownership
Key: WFLY-13637
URL: https://issues.redhat.com/browse/WFLY-13637
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 20.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
On cache topology changes, the distributed web/SFSB manager iterates over keys in memory to determine primary ownership changes. This is not sufficient for invalidation caches - which will not necessary contain those keys in memory that require rescheduling.
This has the consequence of leaking memory for abandoned sessions.
This also impacts replication caches that contain passivated entries.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (WFLY-13636) Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-13636:
-----------------------------------
Summary: Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally
Key: WFLY-13636
URL: https://issues.redhat.com/browse/WFLY-13636
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 20.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the session. For non-transactional invalidation caches expiration should always be scheduled locally. This used to be the case, however, the logic for determining this has changed such that expirations happen on the owner of segment 0.
This has the consequence of an RPC cost per request (and one after).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (WFLY-13628) Invalidation caches need to consider keys in the cache store when reassigning ownership
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13628?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13628:
--------------------------------
Description:
On cache topology changes, the distributed web/SFSB manager iterates over keys in memory to determine primary ownership changes. This is not sufficient for invalidation caches - which will not necessary contain those keys in memory that require rescheduling.
This has the consequence of leaking memory for abandoned sessions.
This also impacts replication caches that contain passivated entries.
was:
On cache topology changes, the distributed web/SFSB manager iterates over keys in memory to determine primary ownership changes. This is not sufficient for invalidation caches - which will not necessary contain those keys in memory that require rescheduling.
This has the consequence of leaking memory for abandoned sessions.
> Invalidation caches need to consider keys in the cache store when reassigning ownership
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-13628
> URL: https://issues.redhat.com/browse/WFLY-13628
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 20.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
>
> On cache topology changes, the distributed web/SFSB manager iterates over keys in memory to determine primary ownership changes. This is not sufficient for invalidation caches - which will not necessary contain those keys in memory that require rescheduling.
> This has the consequence of leaking memory for abandoned sessions.
> This also impacts replication caches that contain passivated entries.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (WFLY-13628) Invalidation caches need to consider keys in the cache store when reassigning ownership
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13628?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13628:
--------------------------------
Description:
On cache topology changes, the distributed web/SFSB manager iterates over keys in memory to determine primary ownership changes. This is not sufficient for invalidation caches - which will not necessary contain those keys in memory that require rescheduling.
This has the consequence of leaking memory for abandoned sessions.
was:On cache topology changes, the distributed web/SFSB manager iterates over keys in memory to determine primary ownership changes. This is not sufficient for invalidation caches - which will not necessary contain those keys in memory that require rescheduling.
> Invalidation caches need to consider keys in the cache store when reassigning ownership
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-13628
> URL: https://issues.redhat.com/browse/WFLY-13628
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 20.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
>
> On cache topology changes, the distributed web/SFSB manager iterates over keys in memory to determine primary ownership changes. This is not sufficient for invalidation caches - which will not necessary contain those keys in memory that require rescheduling.
> This has the consequence of leaking memory for abandoned sessions.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (WFLY-13627) Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13627?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13627:
--------------------------------
Description:
Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the session. For non-transactional invalidation caches expiration should always be scheduled locally. This used to be the case, however, the logic for determining this has changed such that expirations happen on the owner of segment 0.
This has the consequence of an RPC cost per request (and one after).
was:Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the session. For non-transactional invalidation caches expiration should always be scheduled locally. This used to be the case, however, the logic for determining this has changed such that expirations happen on the owner of segment 0.
> Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally
> -------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13627
> URL: https://issues.redhat.com/browse/WFLY-13627
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 20.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
>
> Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the session. For non-transactional invalidation caches expiration should always be scheduled locally. This used to be the case, however, the logic for determining this has changed such that expirations happen on the owner of segment 0.
> This has the consequence of an RPC cost per request (and one after).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months