May 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9137) Add checksums to the distributions on downloads.jboss.org

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-9137: ------------------------------------- Summary: Add checksums to the distributions on downloads.jboss.org Key: ISPN-9137 URL: https://issues.jboss.org/browse/ISPN-9137 Project: Infinispan Issue Type: Enhancement Components: Build Affects Versions: 9.3.0.Alpha1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.3.0.Beta1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9110) Create generic store migrator

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9110?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9110: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.3.0.Final Resolution: Done > Create generic store migrator > ----------------------------- > > Key: ISPN-9110 > URL: https://issues.jboss.org/browse/ISPN-9110 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 9.3.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Beta1, 9.3.0.Final > > > Currently we have the JDBCMigrator to help users migrate from infinispan 8.2.x -> 9.x as 8.x stores are not compatible with 9.x stores due to the marshaller changes. We should make this tool a generic store migrator that allows any of our supported stores to migrate to the latest Infinispan version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9136) RegionFactory.stop does not undefine pending-puts cache

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-9136?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-9136: ------------------------------ Summary: RegionFactory.stop does not undefine pending-puts cache (was: Pending-puts cache configuration is not cleaned up) > RegionFactory.stop does not undefine pending-puts cache > ------------------------------------------------------- > > Key: ISPN-9136 > URL: https://issues.jboss.org/browse/ISPN-9136 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.2.2.Final, 9.3.0.Alpha1 > Reporter: Radim Vansa > Assignee: Radim Vansa > > When shutting down the RegionFactory the caches belonging to regions are cleaned up; pending-puts caches are not, though. > Actually this is not really a problem since SessionFactoryImp.close > EnabledCaching.close iterates through all regions and calls 'destroy'. However we should centralize the shutdown a bit and make the impl more resilient against starting with existing configuration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9003) Clustered maxIdle expiration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9003?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9003: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Clustered maxIdle expiration > ---------------------------- > > Key: ISPN-9003 > URL: https://issues.jboss.org/browse/ISPN-9003 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: William Burns > Fix For: 9.3.0.Beta1, 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9119) Update Caffeine Dependency

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9119?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9119: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update Caffeine Dependency > -------------------------- > > Key: ISPN-9119 > URL: https://issues.jboss.org/browse/ISPN-9119 > Project: Infinispan > Issue Type: Task > Components: Dependency > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.Beta1 > > > We should update caffeine to latest version. There have been quite a few minor updates since we last updated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9123) Off heap shouldn't trace every address when doing an iteration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9123?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9123: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Off heap shouldn't trace every address when doing an iteration > -------------------------------------------------------------- > > Key: ISPN-9123 > URL: https://issues.jboss.org/browse/ISPN-9123 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.3.0.Alpha1 > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.Beta1 > > > Off heap currently prints out every possible address when doing iteration operations (such as invoking clear). We should only print out the address if something exists during these. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9136) Pending-puts cache configuration is not cleaned up

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-9136?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-9136: ------------------------------ Description: When shutting down the RegionFactory the caches belonging to regions are cleaned up; pending-puts caches are not, though. Actually this is not really a problem since SessionFactoryImp.close > EnabledCaching.close iterates through all regions and calls 'destroy'. However we should centralize the shutdown a bit and make the impl more resilient against starting with existing configuration. was: When shutting down the RegionFactory the caches belonging to regions are cleaned up; pending-puts caches are not, though. Actually this is not really a problem since SessionFactoryImp.close > EnabledCaching.close iterates through all regions and calls 'destroy'. However we should make the impl more resilient against starting with existing configuration. > Pending-puts cache configuration is not cleaned up > -------------------------------------------------- > > Key: ISPN-9136 > URL: https://issues.jboss.org/browse/ISPN-9136 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.2.2.Final, 9.3.0.Alpha1 > Reporter: Radim Vansa > Assignee: Radim Vansa > > When shutting down the RegionFactory the caches belonging to regions are cleaned up; pending-puts caches are not, though. > Actually this is not really a problem since SessionFactoryImp.close > EnabledCaching.close iterates through all regions and calls 'destroy'. However we should centralize the shutdown a bit and make the impl more resilient against starting with existing configuration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9136) Pending-puts cache configuration is not cleaned up

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-9136?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-9136: ------------------------------ Description: When shutting down the RegionFactory the caches belonging to regions are cleaned up; pending-puts caches are not, though. Actually this is not really a problem since SessionFactoryImp.close > EnabledCaching.close iterates through all regions and calls 'destroy'. However we should make the impl more resilient against starting with existing configuration. was:When shutting down the RegionFactory the caches belonging to regions are cleaned up; pending-puts caches are not, though. > Pending-puts cache configuration is not cleaned up > -------------------------------------------------- > > Key: ISPN-9136 > URL: https://issues.jboss.org/browse/ISPN-9136 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.2.2.Final, 9.3.0.Alpha1 > Reporter: Radim Vansa > Assignee: Radim Vansa > > When shutting down the RegionFactory the caches belonging to regions are cleaned up; pending-puts caches are not, though. > Actually this is not really a problem since SessionFactoryImp.close > EnabledCaching.close iterates through all regions and calls 'destroy'. However we should make the impl more resilient against starting with existing configuration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-54) Protobuf schema should not accept L, D, F suffixes for numeric constants in default value

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-54?page=com.atlassian.jira.plugin.... ] Work on IPROTO-54 started by Adrian Nistor. ------------------------------------------- > Protobuf schema should not accept L,D,F suffixes for numeric constants in default value > --------------------------------------------------------------------------------------- > > Key: IPROTO-54 > URL: https://issues.jboss.org/browse/IPROTO-54 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 3.0.5.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > The suffixes are specific to java and protobuf is language neutral. In order to be compatible with google's implementations we should not require nor accept them. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2442) Ability to take site offline needs to be extended to async replication

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2442?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-2442: ------------------------------------ {{SITE_UNREACHABLE}} messages are still ignored for async backup sites, as the backup take-offline policy can only act on individual RPC failures and there is no way to connect a {{SITE_UNREACHABLE}} message to a previous async backup command. As a compromise, we could make {{SITE_UNREACHABLE}} trigger a failure on all the async backups to that site. To keep the take-offline policy settings independent of the number of caches, we could assign the failure randomly to one of the async backups to that site (or to none of them if one of the sync backups has outstanding requests). It would be even better to define the site and the take-offline policy at the cache manager level. That way all the {{SITE_UNREACHABLE}} messages will be counted as failures against the same target, and the backup site will be taken offline at the same time for all the caches. > Ability to take site offline needs to be extended to async replication > ---------------------------------------------------------------------- > > Key: ISPN-2442 > URL: https://issues.jboss.org/browse/ISPN-2442 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Affects Versions: 5.2.0.Beta2 > Reporter: Erik Salter > > Currently the site offline implementation only accounts for synchronous caches. This needs to be extended to asynchronous replication as well. > Best case, this avoids wasted cycles and thread resources sending to a dead site. Worst case this could tie up all OOB threads, which could halt communication in the local site. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2018