July 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11286) compute(...) is not working without any error message if expiration parameter is used

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11286?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11286: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/8556, https://github.com/infinispan/infinispan/pull/8557 (was: https://github.com/infinispan/infinispan/pull/8556, https://github.com/infinispan/infinispan/pull/8558) > compute(...) is not working without any error message if expiration parameter is used > ------------------------------------------------------------------------------------- > > Key: ISPN-11286 > URL: https://issues.redhat.com/browse/ISPN-11286 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final, 11.0.2.Final > > Attachments: Book.java, LibraryManager.java > > > If the compute operation is used with expiration parameters the value is not applied without any error message! > compute() without expiration or a put() with expiration will work correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11286) compute(...) is not working without any error message if expiration parameter is used

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11286?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11286: ------------------------------ Status: Open (was: New) > compute(...) is not working without any error message if expiration parameter is used > ------------------------------------------------------------------------------------- > > Key: ISPN-11286 > URL: https://issues.redhat.com/browse/ISPN-11286 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Major > Attachments: Book.java, LibraryManager.java > > > If the compute operation is used with expiration parameters the value is not applied without any error message! > compute() without expiration or a put() with expiration will work correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11286) compute(...) is not working without any error message if expiration parameter is used

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11286?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11286: ------------------------------ Fix Version/s: 12.0.0.Final 11.0.2.Final > compute(...) is not working without any error message if expiration parameter is used > ------------------------------------------------------------------------------------- > > Key: ISPN-11286 > URL: https://issues.redhat.com/browse/ISPN-11286 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final, 11.0.2.Final > > Attachments: Book.java, LibraryManager.java > > > If the compute operation is used with expiration parameters the value is not applied without any error message! > compute() without expiration or a put() with expiration will work correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11286) compute(...) is not working without any error message if expiration parameter is used

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11286?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11286: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8556 > compute(...) is not working without any error message if expiration parameter is used > ------------------------------------------------------------------------------------- > > Key: ISPN-11286 > URL: https://issues.redhat.com/browse/ISPN-11286 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final, 11.0.2.Final > > Attachments: Book.java, LibraryManager.java > > > If the compute operation is used with expiration parameters the value is not applied without any error message! > compute() without expiration or a put() with expiration will work correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12128) Remote read during state transfer should store entry in data container

by Dan Berindei (Jira)

Dan Berindei created ISPN-12128: ----------------------------------- Summary: Remote read during state transfer should store entry in data container Key: ISPN-12128 URL: https://issues.redhat.com/browse/ISPN-12128 Project: Infinispan Issue Type: Bug Components: Core, State Transfer Affects Versions: 11.0.1.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 12.0.0.Final A cache with {{await-initial-transfer="false"}} will execute cache operations while it is receiving state, during rebalance phase {{READ_OLD_WRITE_ALL}}. State transfer can take a long time, and during that time, it is not a read owner for any segments, it is only a write owner for the segments it is receiving. That means {{cache.get(k)}} will perform a remote lookup every time, even AFTER the node received entry {{k=v}} via transfer, as long as not all the nodes have confirmed the end of state transfer and the coordinator hasn't changed the rebalance phase to {{READ_ALL_WRITE_ALL}}. The extra remote lookups can have a negative impact on application performance. Especially in a replicated cache, the application would expect reads to be very fast, and the repeated remote lookups would break that assumption. In order to encourage {{await-initial-transfer="false"}} and eventually make it the default (ISPN-9112), we should limit the number of remote lookups performed by a node while is is a write-only owner of a key: * Remote reads should write the entry in the data container, the same way state transfer would (i.e. skipping the write if a write operation already changed the entry). * Reads should first look up the key in the local data container before going remotely. If the key exists locally, the value can be returned directly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12127) Caches created via REST doesn't appear with CLI unless you disconnect/connect again

by Gustavo Lira Silva (Jira)

[ https://issues.redhat.com/browse/ISPN-12127?page=com.atlassian.jira.plugi... ] Gustavo Lira Silva updated ISPN-12127: -------------------------------------- Description: # Start the server # Connect to CLI # Create the cache with REST [http://localhost:11222/rest/v2/caches/mycache] # Execute ls caches into CLI # The cache doesn't appear unless you disconnect/connect again was: # Start the server # Connect to CLI # Create the cache with REST [http://localhost:11222/rest/v2/caches/mycache] # Execute ls caches into CLI # The cache doesn't appear unless you disconnect/connect again > Caches created via REST doesn't appear with CLI unless you disconnect/connect again > ----------------------------------------------------------------------------------- > > Key: ISPN-12127 > URL: https://issues.redhat.com/browse/ISPN-12127 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Lira Silva > Priority: Major > > # Start the server > # Connect to CLI > # Create the cache with REST [http://localhost:11222/rest/v2/caches/mycache] > # Execute ls caches into CLI > # The cache doesn't appear unless you disconnect/connect again -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12127) Caches created via REST doesn't appear with CLI unless you disconnect/connect again

by Gustavo Lira Silva (Jira)

[ https://issues.redhat.com/browse/ISPN-12127?page=com.atlassian.jira.plugi... ] Gustavo Lira Silva updated ISPN-12127: -------------------------------------- Component/s: CLI > Caches created via REST doesn't appear with CLI unless you disconnect/connect again > ----------------------------------------------------------------------------------- > > Key: ISPN-12127 > URL: https://issues.redhat.com/browse/ISPN-12127 > Project: Infinispan > Issue Type: Bug > Components: CLI > Reporter: Gustavo Lira Silva > Priority: Major > > # Start the server > # Connect to CLI > # Create the cache with REST [http://localhost:11222/rest/v2/caches/mycache] > # Execute ls caches into CLI > # The cache doesn't appear unless you disconnect/connect again -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12127) Caches created via REST doesn't appear with CLI unless you disconnect/connect again

by Gustavo Lira Silva (Jira)

Gustavo Lira Silva created ISPN-12127: ----------------------------------------- Summary: Caches created via REST doesn't appear with CLI unless you disconnect/connect again Key: ISPN-12127 URL: https://issues.redhat.com/browse/ISPN-12127 Project: Infinispan Issue Type: Bug Reporter: Gustavo Lira Silva # Start the server # Connect to CLI # Create the cache with REST [http://localhost:11222/rest/v2/caches/mycache] # Execute ls caches into CLI # The cache doesn't appear unless you disconnect/connect again -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12124) OracleTableManager is overly conservative with object name max length

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/ISPN-12124?page=com.atlassian.jira.plugi... ] Paul Ferraro updated ISPN-12124: -------------------------------- Priority: Critical (was: Major) > OracleTableManager is overly conservative with object name max length > --------------------------------------------------------------------- > > Key: ISPN-12124 > URL: https://issues.redhat.com/browse/ISPN-12124 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 11.0.1.Final > Reporter: Paul Ferraro > Priority: Critical > > The OracleTableManager limits the size of generated object names to 30 characters. While 30 characters was the max object name length in 12.1 and earlier, since 12.2, this limit was increased to 128 characters. > 30 characters is prohibitively restrictive when it come to objects like the index name, the names for which are auto-generated based on the cache name, table name, and, in the case of the segment column, a long hard coded prefix (e.g. "segment_index") uses up nearly half of the available characters. > Rather than fixed lengths per database type, Infinispan should leverage the DatabaseMetaData to determine the max size for a given database object, e.g. getMaxTableNameLength(), getMaxColumnNameLength(), etc. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12126) Performance drop when using auth in REST

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12126?page=com.atlassian.jira.plugi... ] Work on ISPN-12126 started by Gustavo Fernandes. ------------------------------------------------ > Performance drop when using auth in REST > ---------------------------------------- > > Key: ISPN-12126 > URL: https://issues.redhat.com/browse/ISPN-12126 > Project: Infinispan > Issue Type: Bug > Components: REST, Security > Affects Versions: 11.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 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 July 2020