June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5451) Data Container Segment Striping

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5451?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5451: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Data Container Segment Striping > ------------------------------- > > Key: ISPN-5451 > URL: https://issues.jboss.org/browse/ISPN-5451 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.CR1 > > > Today each node owns a given number of segments at a time. There are many operations that are only concerned with entries of a given segment. Unfortunately this means that we must iterate over the entire contents of the cache to find only the entries that match given segments. Note this JIRA is only for the in memory data container. The cache store requires additional work and should be done separately as it may involve reworking many more areas of the code base. > # State Transfer entry removal (this removes all entries of given segments) > # Entry retrieval (if we could iterate by segment instead of over all values we could complete segments sooner which would reduce how much memory a client must hold) > # Indexing may want to index by segment at some point as well -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9223) 1PC isn't properly implemented in Hot Rod Client

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9223?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9223: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.3.0.CR1 Resolution: Done > 1PC isn't properly implemented in Hot Rod Client > ------------------------------------------------ > > Key: ISPN-9223 > URL: https://issues.jboss.org/browse/ISPN-9223 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod, Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.3.0.CR1 > > > One-Phase-Commit should be sent in the last cache involved and not in all, otherwise, the transaction won't be atomic in Infinispan with some caches committing and another rolling-back. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9223) 1PC isn't properly implemented in Hot Rod Client

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9223?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9223: -------------------------------- Sprint: Sprint 9.3.0.CR1 > 1PC isn't properly implemented in Hot Rod Client > ------------------------------------------------ > > Key: ISPN-9223 > URL: https://issues.jboss.org/browse/ISPN-9223 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod, Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > One-Phase-Commit should be sent in the last cache involved and not in all, otherwise, the transaction won't be atomic in Infinispan with some caches committing and another rolling-back. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8008) Add Fault-tolerance to write-behind stores

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8008?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-8008. -------------------------------- Resolution: Done > Add Fault-tolerance to write-behind stores > ------------------------------------------ > > Key: ISPN-8008 > URL: https://issues.jboss.org/browse/ISPN-8008 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.CR1 > > > Currently when a store is configured to be write-behind, three attempts are made to write the queued modifications to the store. If all three attempts fail, then this error is simply logged and the modifications are never written to the store. > We should allow users to configure a write-behind store so that: In the event that a write-behind fails, further operations on the cache are not allowed and the modifications which failed to write to the store are queued indefinitely. Once the underlying store becomes available, the queued modifications should be written and then the cache should become available. > To determine whether a store has become available again, the AsyncCacheWriter will have to poll the store's availability. Currently the CacheWriter interface does not allow such behaviour, therefore there are two options: > * Attempt a write and catch an exception if the store is not currently available > * Add a method to return the current status of a store to the CacheWriter interface -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6677) Deal with unavailable dependencies during startup

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6677?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-6677. -------------------------------- Fix Version/s: 9.3.0.CR1 Resolution: Done > Deal with unavailable dependencies during startup > ------------------------------------------------- > > Key: ISPN-6677 > URL: https://issues.jboss.org/browse/ISPN-6677 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud > Reporter: Sebastian Łaskawiec > Assignee: Ryan Emerson > Priority: Blocker > Fix For: 9.3.0.CR1 > > > In Kubernetes not all Pods start at the same time. It is perfectly possible to start first Infinispan and a bit later the database (in this configuration we are assuming that Infinispan has a dependency to DB). Note that this setup would fails. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9021) Remote query: add option to disable default/legacy indexing per schema file

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9021?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9021: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Remote query: add option to disable default/legacy indexing per schema file > --------------------------------------------------------------------------- > > Key: ISPN-9021 > URL: https://issues.jboss.org/browse/ISPN-9021 > Project: Infinispan > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.3.0.CR1, 9.3.0.Final > > > All types that are not annotated are currently fully indexed for backward compat with first version of remote query (which did not have protobuf annotations to control indexing). > This behaviour is very inefficient and confusing for users that do not intend to use indexing (non-indexed query works anyway). > Given the history of this behaviour we cannot remove it until next major version. Until then we can offer the choice of disabling it per each schema file via a boolean protobuf file-level option named{color:#cccccc} -'enable_legacy_indexing'-{color} 'indexed_by_default', which when absent is considered to default to true. Setting it to false will disable indexing of types that do not have indexing annotations. > Whenever an entry is indexed using default indexing a warning will be logged in order to motivate people to switch to using proper annotations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9254) Document Single Port

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-9254: -------------------------------------- Summary: Document Single Port Key: ISPN-9254 URL: https://issues.jboss.org/browse/ISPN-9254 Project: Infinispan Issue Type: Task Components: Remote Protocols Reporter: Galder Zamarreño Assignee: Sebastian Łaskawiec Fix For: 9.3.0.CR1, 9.3.0.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9253) Integrate Forbidden API maven plugin

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-9253: -------------------------------------- Summary: Integrate Forbidden API maven plugin Key: ISPN-9253 URL: https://issues.jboss.org/browse/ISPN-9253 Project: Infinispan Issue Type: Task Components: Build Reporter: Galder Zamarreño Integrate Forbidden APIs maven plugin: {code} Sanne Grinovero: regarding System.out, and org.junit vs junit.framework, or importing the wrong @Immutable annotation.. introduce Forbidden APIs plugin? https://github.com/hibernate/hibernate-search/blob/master/pom.xml#L1593-L... ... Sanne Grinovero: Also, this one is amazingly fast (just takes ~1s to scan our whole codebase) and includes very updarules to e.g. Sanne Grinovero: And includes rules like "don't use methods removed in JDK11" Sanne Grinovero: @Tristan it's easy to customize too: https://github.com/hibernate/hibernate-search/blob/master/build-config/sr... {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9252) Easier statistics collection in NettyTransportConnectionStats

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-9252: -------------------------------------- Summary: Easier statistics collection in NettyTransportConnectionStats Key: ISPN-9252 URL: https://issues.jboss.org/browse/ISPN-9252 Project: Infinispan Issue Type: Task Components: Remote Protocols Reporter: Galder Zamarreño Fix For: 9.3.0.CR1 NettyTransportConnectionStats should have an easier way to get statistics rather than going over JMX itself. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9251) Cleanup System.out calls

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-9251: -------------------------------------- Summary: Cleanup System.out calls Key: ISPN-9251 URL: https://issues.jboss.org/browse/ISPN-9251 Project: Infinispan Issue Type: Bug Components: Remote Protocols Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 9.3.0.CR1 Cleanup System.out calls introduced by ISPN-8756 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2018