August 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5578) Allow default index storage location scoped by cache name

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5578?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5578: -------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha4) > Allow default index storage location scoped by cache name > --------------------------------------------------------- > > Key: ISPN-5578 > URL: https://issues.jboss.org/browse/ISPN-5578 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Beta1 > > > Thus avoiding clashing of multiple indexed caches without necessarily needing to configure {{indexBase}} for each one -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5575) Shared write-behind store can read stale entries on joiner

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5575?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5575: -------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha4) > Shared write-behind store can read stale entries on joiner > ---------------------------------------------------------- > > Key: ISPN-5575 > URL: https://issues.jboss.org/browse/ISPN-5575 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 8.0.0.Alpha2, 7.2.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta1 > > > The AsyncCacheWriter modification queue is not sent with state transfer when the store is shared. A joiner can then read from the shared store a stale version of entries that have updates in the modification queue but are no longer in memory (because they were either removed explicitly, or evicted). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5574) Define high-level cache capabilities

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5574?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5574: -------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha4) > Define high-level cache capabilities > ------------------------------------ > > Key: ISPN-5574 > URL: https://issues.jboss.org/browse/ISPN-5574 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Core > Affects Versions: 7.2.3.Final > Reporter: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Beta1 > > > Infinispan's configuration is very flexible, and it's sometimes hard to figure out how different settings affect things like cache consistency. > For example, the lucene-directory module uses the fairly complicated {{Configurations.noDataLossOnJoiner()}} method to validate that a cache is safe for storing lucene indexes. > Another example is users who would like to use a store for backup, but they don't want read from the store for M/R tasks or when get(k) doesn't find the key in memory. > One idea would be to define a set of "capabilities" like "state-transfer-complete" or "all-data-in-memory". The user could then add those capabilities in the cache definition, and the cache won't start if the configuration violates those capabilities. The capabilities would also be used internally, to improve the error message when a feature requires a particular combination of settings. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5617) Clearly define which cachestores are shared and which are non-shared

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5617?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5617: -------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha4) > Clearly define which cachestores are shared and which are non-shared > -------------------------------------------------------------------- > > Key: ISPN-5617 > URL: https://issues.jboss.org/browse/ISPN-5617 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Fix For: 9.0.0.Beta1 > > > Cache stores should explicitly declare if they work in shared or non-shared mode, so that unsupported configurations cannot be started. > See http://lists.jboss.org/pipermail/infinispan-dev/2015-July/016076.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5615) Transfer sections from the Hibernate Search reference documentation about the Lucene Directory Provider

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5615?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5615: -------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha4) > Transfer sections from the Hibernate Search reference documentation about the Lucene Directory Provider > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-5615 > URL: https://issues.jboss.org/browse/ISPN-5615 > Project: Infinispan > Issue Type: Task > Components: Documentation-Query > Reporter: Sanne Grinovero > Fix For: 9.0.0.Beta1 > > > The general introduction to Infinispan should stay in the Hibernate Search documentation > - http://docs.jboss.org/hibernate/search/5.3/reference/en-US/html_single/#i... > But configuration options and tuning recommendations whould be transferred to the Infinispan reference documentation as the exact properties and their effect would depend on the Infinispan version being used (most of section 3.3.1.3. Infinispan Configuration) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5614) Write performance regression after ISPN-5484

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5614?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5614: -------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha4) > Write performance regression after ISPN-5484 > -------------------------------------------- > > Key: ISPN-5614 > URL: https://issues.jboss.org/browse/ISPN-5614 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta1 > > > Regression test shows a significant drop in throughput in the replicated and distributed write tests. > This was after adjusting the internal thread pool settings in the JGroups configuration: with the default (min=5, max=20, queue=0), the distributed read test would fail to finish. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5601) Merge ExtendedModuleCommandFactory into ModuleCommandFactory

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5601?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5601: -------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha4) > Merge ExtendedModuleCommandFactory into ModuleCommandFactory > ------------------------------------------------------------ > > Key: ISPN-5601 > URL: https://issues.jboss.org/browse/ISPN-5601 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.0.0.Alpha2 > Reporter: Radim Vansa > Fix For: 9.0.0.Beta1 > > > These are the docs for ExtendedModuleCommandFactory: > {quote} > Temporary workaround to avoid modifying ModuleCommandFactory interface. This interface should be merged with ModuleCommandFactory in 6.0. > {quote} > Seems that was forgotten in 6.0, 8.0 can fix that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5657) Add missing embedded configuration elements to server schema

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5657?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5657: -------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha4) > Add missing embedded configuration elements to server schema > ------------------------------------------------------------ > > Key: ISPN-5657 > URL: https://issues.jboss.org/browse/ISPN-5657 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta1 > > > The embedded and server schema, while mostly compatible with each other, still differ in a number of aspects, e.g. store-as-binary, unsafe, etc. > The server should be able to parse these additional elements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5654) Make DeadlockDetectingLockManager aware of single-node locking

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5654?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5654: -------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha4) > Make DeadlockDetectingLockManager aware of single-node locking > -------------------------------------------------------------- > > Key: ISPN-5654 > URL: https://issues.jboss.org/browse/ISPN-5654 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Fix For: 9.0.0.Beta1 > > > {{DeadlockDetectingLockManager}} seems to assume that the node that started a transaction acquires a local lock before replicating, which is wrong since we switched to locking only on the primary owner. > In particular, {{isSameKeyDeadlock}} can probably be removed altogether. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5642) Reduce contention in the RPC timeout handling

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5642?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5642: -------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha4) > Reduce contention in the RPC timeout handling > --------------------------------------------- > > Key: ISPN-5642 > URL: https://issues.jboss.org/browse/ISPN-5642 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Labels: help_wanted > Fix For: 9.0.0.Beta1 > > > Most of the RPC timeout tasks are cancelled way before their timeout expires. This means the scheduler spends a lot of time reordering the elements of its DelayQueue. > It should be possible to store the tasks with a long timeout (e.g. 1s) in a queue and only move them to the scheduler's priority queue when they have less than 1s to expiration (e.g. by a worker thread that runs every 0.5s) > Storing all the tasks in a single queue may be impractical because the worker thread would have more and work to do as load increases and the RPCs take longer to finish, so a [hashed timing wheel|http://www.cse.wustl.edu/~cdgill/courses/cs6874/TimingWheels.ppt] may be needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 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 August 2016