December 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10443) Display X-Site information in the console

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-10443?page=com.atlassian.jira.plugi... ] Work on ISPN-10443 started by Katia Aresti. ------------------------------------------- > Display X-Site information in the console > ----------------------------------------- > > Key: ISPN-10443 > URL: https://issues.redhat.com/browse/ISPN-10443 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: console-ng > > Display the x-site information: > - clusters > - nodes > - caches -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11095) Statistics should show the number of expirations similar to eviction

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11095?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez reassigned ISPN-11095: --------------------------------------------- Assignee: Nistor Adrian > Statistics should show the number of expirations similar to eviction > -------------------------------------------------------------------- > > Key: ISPN-11095 > URL: https://issues.redhat.com/browse/ISPN-11095 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Wolf-Dieter Fink > Assignee: Nistor Adrian > Priority: Minor > > Each cache statistic shows the number of evicted entries. > It should also count the number of expired and removed entries. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11079) Cluster Expiration and Optimistic Transactions write skew issues

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11079?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11079: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Cluster Expiration and Optimistic Transactions write skew issues > ---------------------------------------------------------------- > > Key: ISPN-11079 > URL: https://issues.redhat.com/browse/ISPN-11079 > Project: Infinispan > Issue Type: Bug > Components: Expiration > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.1.0.Final, 11.0.0.Final > > > Optimistic write skew and clustered expiration can have some weird issues > One such is: > The issue is the following: > 1. RemoveExpiredCommand reads the expired from the container with version 1 and puts in its context > 2. PutKeyValueCommand sees nothing in container due to expired and adds a new entry with version 1 in its context > 3. Put gets the lock and replaces the value > 4. RemoveExpiredCommand attempts to run and because it saw the old value the lifespans still match (if different) > 5. Then the write skew passes for the remove expired command since the value in container and its context both have version 1 > To workaround this for now we should prevent a get of an expired entry from returning early when using optimistic transactions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11049) Infinispan Server should resolve all the console URLs

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11049?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11049: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.1.0.Final Resolution: Done > Infinispan Server should resolve all the console URLs > ----------------------------------------------------- > > Key: ISPN-11049 > URL: https://issues.redhat.com/browse/ISPN-11049 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.1.0.Beta1 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 10.1.0.Final > > > Infinispan server serves the console from the static resources. This console is an front end app built in react that contains multiple URL paths. > When we do F5 on a URL that is not 'console' or 'console/wlecome' the server responds with 404. > The static resource (or console resource) should be able to serve the console app from any of the '/console/*' Urls so there is no 404 when there ir s refresh -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11102) Purge on JDBC shared stores can cause deadlocks

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-11102: ----------------------------------- Summary: Purge on JDBC shared stores can cause deadlocks Key: ISPN-11102 URL: https://issues.redhat.com/browse/ISPN-11102 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 9.4.17.Final, 10.1.0.CR1 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.1.0.Final, 9.4.18.Final ISPN-10337 ensured that the JdbcStringBasedStore correctly acquired the locks of expired rows during the purging of store entries, however it has exposed an issue with shared stores. When the jdbc store is shared, the coordinator locks the rows of the affected entries and releases them once they have all been removed as part of the purge transaction. However, the call to {{ExpirationManager::handleInStoreExpiration}} also sends a {{RemoveExpiredCommand}} to ensure that entries are removed from memory. This results in a {{java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction}} being thrown by the store's delete method when the purge process is still in progress, because the expired rows are still locked and the purge process cannot complete until the {{RemoveExpiredCommand}} has been executed. In summary: # purge locks all the rows # purge sends a RemoveExpiredCommand and waits for it to complete # RemoveExpiredCommand tries to remove the row but it can't as it is locked Solution, send the {{RemoveExpiredCommand}} with the {{SKIP_CACHE_STORE}} flag when a store is shared,so that it only removes entries from memory. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11101) Purge on JDBC shared stores can cause deadlocks

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-11101: ----------------------------------- Summary: Purge on JDBC shared stores can cause deadlocks Key: ISPN-11101 URL: https://issues.redhat.com/browse/ISPN-11101 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 10.1.0.CR1, 9.4.17.Final Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.1.0.Final, 9.4.18.Final ISPN-10337 ensured that the JdbcStringBasedStore correctly acquired the locks of expired rows during the purging of store entries, however it has exposed an issue with shared stores. When the jdbc store is shared, the coordinator locks the rows of the affected entries and releases them once they have all been removed as part of the purge transaction. However, the call to {{ExpirationManager::handleInStoreExpiration}} also sends a {{RemoveExpiredCommand}} to ensure that entries are removed from memory. This results in a {{java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction}} being thrown by the store's delete method when the purge process is still in progress, because the expired rows are still locked and the purge process cannot complete until the {{RemoveExpiredCommand}} has been executed. In summary: # purge locks all the rows # purge sends a RemoveExpiredCommand and waits for it to complete # RemoveExpiredCommand tries to remove the row but it can't as it is locked Solution, send the {{RemoveExpiredCommand}} with the {{SKIP_CACHE_STORE}} flag when a store is shared,so that it only removes entries from memory. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11100) Rename org.infinispan.server.loader.Loader to InfinispanServerLoader

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-11100?page=com.atlassian.jira.plugi... ] Diego Lovison commented on ISPN-11100: -------------------------------------- I saw latter that we can use: jps -lm > Rename org.infinispan.server.loader.Loader to InfinispanServerLoader > -------------------------------------------------------------------- > > Key: ISPN-11100 > URL: https://issues.redhat.com/browse/ISPN-11100 > Project: Infinispan > Issue Type: Enhancement > Reporter: Diego Lovison > Priority: Minor > > When running a command to get the PID from jps the word Loader will be there and we can conclude what is "Loader" > Before: > {{./profiler.sh -d 10 "$(jps | grep "Loader" | cut -d ' ' -f1)"}} > After: > {{./profiler.sh -d 10 "$(jps | grep "InfinispanServerLoader" | cut -d ' ' -f1)"}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11100) Rename org.infinispan.server.loader.Loader to InfinispanServerLoader

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-11100?page=com.atlassian.jira.plugi... ] Diego Lovison updated ISPN-11100: --------------------------------- Status: Open (was: New) > Rename org.infinispan.server.loader.Loader to InfinispanServerLoader > -------------------------------------------------------------------- > > Key: ISPN-11100 > URL: https://issues.redhat.com/browse/ISPN-11100 > Project: Infinispan > Issue Type: Enhancement > Reporter: Diego Lovison > Priority: Minor > > When running a command to get the PID from jps the word Loader will be there and we can conclude what is "Loader" > Before: > {{./profiler.sh -d 10 "$(jps | grep "Loader" | cut -d ' ' -f1)"}} > After: > {{./profiler.sh -d 10 "$(jps | grep "InfinispanServerLoader" | cut -d ' ' -f1)"}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11100) Rename org.infinispan.server.loader.Loader to InfinispanServerLoader

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-11100?page=com.atlassian.jira.plugi... ] Diego Lovison reassigned ISPN-11100: ------------------------------------ Assignee: Diego Lovison > Rename org.infinispan.server.loader.Loader to InfinispanServerLoader > -------------------------------------------------------------------- > > Key: ISPN-11100 > URL: https://issues.redhat.com/browse/ISPN-11100 > Project: Infinispan > Issue Type: Enhancement > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Minor > > When running a command to get the PID from jps the word Loader will be there and we can conclude what is "Loader" > Before: > {{./profiler.sh -d 10 "$(jps | grep "Loader" | cut -d ' ' -f1)"}} > After: > {{./profiler.sh -d 10 "$(jps | grep "InfinispanServerLoader" | cut -d ' ' -f1)"}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11100) Rename org.infinispan.server.loader.Loader to InfinispanServerLoader

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-11100?page=com.atlassian.jira.plugi... ] Diego Lovison updated ISPN-11100: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7691 > Rename org.infinispan.server.loader.Loader to InfinispanServerLoader > -------------------------------------------------------------------- > > Key: ISPN-11100 > URL: https://issues.redhat.com/browse/ISPN-11100 > Project: Infinispan > Issue Type: Enhancement > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Minor > > When running a command to get the PID from jps the word Loader will be there and we can conclude what is "Loader" > Before: > {{./profiler.sh -d 10 "$(jps | grep "Loader" | cut -d ' ' -f1)"}} > After: > {{./profiler.sh -d 10 "$(jps | grep "InfinispanServerLoader" | cut -d ' ' -f1)"}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2019