March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5075) org.infinispan.IllegalLifecycleStateException in query tests

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5075?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5075: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > org.infinispan.IllegalLifecycleStateException in query tests > ------------------------------------------------------------ > > Key: ISPN-5075 > URL: https://issues.jboss.org/browse/ISPN-5075 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Query > Affects Versions: 7.1.0.Alpha1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.0.Final > > > Many query tests log an error after running: > {code} > Exception in thread "Hibernate Search: async deletion of index segments-1" org.infinispan.IllegalLifecycleStateException: ISPN000323: Cache 'LuceneIndexesMetadata' is in 'TERMINATED' state and so it does not accept new invocations. Either restart it or recreate the cache container. > at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:89) > at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:71) > at org.infinispan.commands.AbstractVisitor.visitGetKeyValueCommand(AbstractVisitor.java:77) > at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:44) > at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:333) > at org.infinispan.cache.impl.CacheImpl.get(CacheImpl.java:422) > at org.infinispan.cache.impl.DecoratedCache.get(DecoratedCache.java:427) > at org.infinispan.lucene.impl.FileListOperations.getFileList(FileListOperations.java:160) > at org.infinispan.lucene.impl.FileListOperations.deleteFileName(FileListOperations.java:129) > at org.infinispan.lucene.impl.DirectoryImplementor.deleteFile(DirectoryImplementor.java:64) > at org.infinispan.lucene.impl.DirectoryLuceneV4$DeleteTask.run(DirectoryLuceneV4.java:195) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > {code} > That error does not cause the tests to fail, and are due to the async deletes of segments recently implemented. Need to check if the executors are being flushed correctly when the cache manager stops -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5073) Improve "Number of Entries" stats

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5073?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5073: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Improve "Number of Entries" stats > --------------------------------- > > Key: ISPN-5073 > URL: https://issues.jboss.org/browse/ISPN-5073 > Project: Infinispan > Issue Type: Task > Components: Core, JMX, reporting and management > Affects Versions: 7.1.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Vladimir Blagojevic > Fix For: 8.2.0.Final > > > Currently the getNumberOfEntries in CacheMgmtInterceptor returns the size of the datacontainer which doesn't take into account expired entries and cache stores. > To avoid compatibility issues, modify the description to reflect its behaviour and add proper statistics, possibly with different flag combinations (SKIP_REMOTE, SKIP_CACHE_LOAD) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5058) Document example configurations using a CacheStore to persist the Lucene index

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5058?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5058: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Document example configurations using a CacheStore to persist the Lucene index > ------------------------------------------------------------------------------ > > Key: ISPN-5058 > URL: https://issues.jboss.org/browse/ISPN-5058 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Query > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 8.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5210) Support writing multiple modifications to cache stores in batch when using Transactions

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5210?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5210: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Support writing multiple modifications to cache stores in batch when using Transactions > --------------------------------------------------------------------------------------- > > Key: ISPN-5210 > URL: https://issues.jboss.org/browse/ISPN-5210 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Affects Versions: 6.0.2.Final, 7.1.0.Final > Reporter: Richard Lucas > Fix For: 8.2.0.Final > > > Currently writes to a cache store are performed individually for each modification to the cache. > While this makes sense when using a non-tx cache it would be beneficial to support writing multiple modifications to a cache store in a single call when using a Tx cache. > Currently all writes are performed in the commit phase and are done by looping through the modifications in the Tx and writing each one in turn to the the store. > Instead of doing this it would useful to pass all modifications to the store in a single call, this would allow: > a) Taking advantage of support for batch updates in underlying stores (JDBC, MongoDB, DynamoDB) for a more efficient write through. > b) Allow store implementations the chance to clean up if one or more updates in the batch fail (this is especially useful if the store does not support Tx and rollbacks as it means the store implementation can at least try to clean up any partial updates it has performed, something which is not currently possible). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5218) Add batching to the AdvancedCacheWriter interface

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5218?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5218: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Add batching to the AdvancedCacheWriter interface > ------------------------------------------------- > > Key: ISPN-5218 > URL: https://issues.jboss.org/browse/ISPN-5218 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Tristan Tarrant > Fix For: 8.2.0.Final > > > The AdvancedCacheWriter should be extended with a write operation which takes multiple entries so that stores which can do batching can optimize this. This would benefit both passivation and the async writer. > Immediate users would be the JDBC stores. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5238) Maintain session in ispn-mgmt-console (ctrl+R)

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5238?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5238: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Maintain session in ispn-mgmt-console (ctrl+R) > ---------------------------------------------- > > Key: ISPN-5238 > URL: https://issues.jboss.org/browse/ISPN-5238 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Reporter: Tomas Sykora > Assignee: Vladimir Blagojevic > Fix For: 8.2.0.Final > > > When you reload a page in Infinispan Management Console data is lost and you need to re-login. We need to make sure that the session is maintained properly and operations like ctrl+R, F5 etc. does not affect behaviour negatively. > It will also help with development and testing when you need to reload a page to see some changes from time to time. > I did a small research around this topic and made some experiments but I was not able to achieve what I wanted. Maybe we can come up with even different approach. > Anyway I suppose we can stick to the idea that ctrl+R should just reload the page and data successfully. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5163) A write operation with the SKIP_LOCKING flag can roll back the transaction

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5163?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5163: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > A write operation with the SKIP_LOCKING flag can roll back the transaction > -------------------------------------------------------------------------- > > Key: ISPN-5163 > URL: https://issues.jboss.org/browse/ISPN-5163 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.3.Final, 7.1.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.Final > > > When a write operation has the SKIP_LOCKING flag, it does not send a {{LockControlCommand}} to the primary owner, but it can send a {{ClusteredGetCommand}} with {{acquireRemoteLocks=true}} instead. The {{ClusteredGetCommmand}} will then execute a {{LockControlCommand}} with the origin not set properly, and {{TxInterceptor}} will roll back the transaction because the originator ({{null}}) appears to have left the cluster. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5179) Add distributed execution and map/reduce job statistics

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5179?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5179: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Add distributed execution and map/reduce job statistics > -------------------------------------------------------- > > Key: ISPN-5179 > URL: https://issues.jboss.org/browse/ISPN-5179 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 8.2.0.Final > > > We should add DMR/JMX statistics for the running distributed execution jobs as well as map/reduce jobs. The statistics will also include overview/total system statistics of previously executed jobs; we might store statistics of individual executed jobs in some internal cache. However, the primary objective is to calculate and maintain dist.exec and map/reduce job statistics for Infinispan admin console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5211) NPE on NumericVersionGenerator.start() when JGroups configuration resource not found

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5211?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5211: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > NPE on NumericVersionGenerator.start() when JGroups configuration resource not found > ------------------------------------------------------------------------------------ > > Key: ISPN-5211 > URL: https://issues.jboss.org/browse/ISPN-5211 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.1.0.Final > Reporter: Sanne Grinovero > Fix For: 8.2.0.Final > > > This is easy to reproduce: start a {{CacheManager}} which has a {{Transport}} configured with a non-existent resource name for the JGroups configuration. > Would be great to have a better error message. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5241) Cache topology updates should use the NO_FC flag

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5241?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5241: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Cache topology updates should use the NO_FC flag > ------------------------------------------------ > > Key: ISPN-5241 > URL: https://issues.jboss.org/browse/ISPN-5241 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 8.2.0.Final > > > Topology updates are sent while holding the ClusterCacheStatus lock, so they should never block. However, when MFC is present, the topology update can block waiting for enough credits. As most CacheTopologyControlCommands need to acquire the ClusterCacheStatus lock, this can easily lead to a full remote-executor pool (and OOB pool) and the appearance of a deadlock. > What's more, if one node is not responsive, it can block all the other nodes from receiving further topology updates. Topology updates should be as prompt as possible, so we should use the NO_FC flag to ensure that each node receives topology updates as soon as possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2016