September 2019 - infinispan-issues

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10689?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10689: ----------------------------------- Fix Version/s: 10.0.0.CR3 > RocksDB 6.2.2 > ------------- > > Key: ISPN-10689 > URL: https://issues.jboss.org/browse/ISPN-10689 > Project: Infinispan > Issue Type: Component Upgrade > Components: Loaders and Stores > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10689) RocksDB 6.2.2

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10689?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10689: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7369 > RocksDB 6.2.2 > ------------- > > Key: ISPN-10689 > URL: https://issues.jboss.org/browse/ISPN-10689 > Project: Infinispan > Issue Type: Component Upgrade > Components: Loaders and Stores > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10689) RocksDB 6.2.2

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10689: -------------------------------------- Summary: RocksDB 6.2.2 Key: ISPN-10689 URL: https://issues.jboss.org/browse/ISPN-10689 Project: Infinispan Issue Type: Component Upgrade Components: Loaders and Stores Reporter: Tristan Tarrant Assignee: Tristan Tarrant -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10688) Error negotiationg MediaType when obtaining cache and cache manager config

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-10688: ---------------------------------------- Summary: Error negotiationg MediaType when obtaining cache and cache manager config Key: ISPN-10688 URL: https://issues.jboss.org/browse/ISPN-10688 Project: Infinispan Issue Type: Bug Components: REST Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes This happens when trying to call those endpoints in the browser: http://localhost:11222/rest/v2/caches/default?action=config -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10687) Invalid JSON produced when obtaining the cache keys via REST v2

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10687?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10687: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.0.0.CR3 Resolution: Done > Invalid JSON produced when obtaining the cache keys via REST v2 > --------------------------------------------------------------- > > Key: ISPN-10687 > URL: https://issues.jboss.org/browse/ISPN-10687 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.CR2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.CR3 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10683) Remove CustomFailurePolicy transaction parameters

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10683?page=com.atlassian.jira.plugin... ] Dan Berindei commented on ISPN-10683: ------------------------------------- Does it really make sense to register/unregister resources in the failure policy? I thought all the policy could do is throw a {{BackupFailureException}}. Initially I meant to remove the transaction completely, but then I thought we might want a way to connect the prepare and commit commands for the same tx. > Remove CustomFailurePolicy transaction parameters > ------------------------------------------------- > > Key: ISPN-10683 > URL: https://issues.jboss.org/browse/ISPN-10683 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 10.0.0.CR2 > Reporter: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > The {{CustomFailurePolicy}} javadoc says it should be thread-safe, but the {{javax.transaction.Transaction}} javadoc doesn't say anything about thread safety. > We should replace the {{javax.transaction.Transaction}} with a {{GlobalTransaction}}, which we know is thread-safe. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10678) Cluster Expiration should only expire primary owned entries

by Wolf-Dieter Fink (Jira)

[ https://issues.jboss.org/browse/ISPN-10678?page=com.atlassian.jira.plugin... ] Wolf-Dieter Fink commented on ISPN-10678: ----------------------------------------- Some tests Environment 2 nodes clustered on a local machine - configuration: ~~~ <cache-container name="clustered" default-cache="ExpirationCache" statistics="true"> <transport lock-timeout="60000"/> <global-state/> <distributed-cache name="ExpirationCache"> <locking isolation="READ_COMMITTED" striping="false"/> <transaction mode="NON_XA" locking="OPTIMISTIC"/> <expiration interval="10000"/> </distributed-cache> </cache-container> ~~~ Two test clients will add as much as possible bc of the key it will be a max of 1 entry per millisecond each. The expiration is set to 1sec In the cluster the expiration thread spikes >50sec (with one node it will be <2sec) Between start and stop message there are 27948 pool-9-thread Submitting expiration removal for key 1200 remote-thread Submitting expiration removal for key > Cluster Expiration should only expire primary owned entries > ----------------------------------------------------------- > > Key: ISPN-10678 > URL: https://issues.jboss.org/browse/ISPN-10678 > Project: Infinispan > Issue Type: Enhancement > Components: Expiration > Affects Versions: 9.4.16.Final, 10.0.0.CR2 > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Final, 9.4.17.Final > > > Today cluster expiration fires for any expired entry it finds. We should instead only expire an entry when it is the primary owner encountering the entry. This will allow expiration to scale much better depending on the number of owners. This also reduces network and locking contention as we may have been sending duplicate expiration commands from backups and primary at the same time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10687) Invalid JSON produced when obtaining the cache keys via REST v2

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10687?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10687: ------------------------------------- Summary: Invalid JSON produced when obtaining the cache keys via REST v2 (was: Invalid JSON producing when obtaining the cache keys via REST v2) > Invalid JSON produced when obtaining the cache keys via REST v2 > --------------------------------------------------------------- > > Key: ISPN-10687 > URL: https://issues.jboss.org/browse/ISPN-10687 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.CR2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10687) Invalid JSON producing when obtaining the cache keys via REST v2

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10687?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10687: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7368 > Invalid JSON producing when obtaining the cache keys via REST v2 > ---------------------------------------------------------------- > > Key: ISPN-10687 > URL: https://issues.jboss.org/browse/ISPN-10687 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.CR2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10687) Invalid JSON producing when obtaining the cache keys via REST v2

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10687?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10687: ------------------------------------- Status: Open (was: New) > Invalid JSON producing when obtaining the cache keys via REST v2 > ---------------------------------------------------------------- > > Key: ISPN-10687 > URL: https://issues.jboss.org/browse/ISPN-10687 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.CR2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2019