October 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4624) Allow custom partition handling strategy

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4624?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4624: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Allow custom partition handling strategy > ---------------------------------------- > > Key: ISPN-4624 > URL: https://issues.jboss.org/browse/ISPN-4624 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 7.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: partition_handling > Fix For: 7.0.0.CR2 > > > Users should be able to configure a custom PartitionHandlingStrategy. It should be able to specify a behaviour on merge as well. > We might want to merge this with the RebalancePolicy, which was also supposed to be configurable. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4643) Make sure EntryIterator doesn't return expired entries

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4643?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4643: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Make sure EntryIterator doesn't return expired entries > ------------------------------------------------------ > > Key: ISPN-4643 > URL: https://issues.jboss.org/browse/ISPN-4643 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Beta1 > Reporter: William Burns > Assignee: Dan Berindei > Fix For: 7.0.0.CR2 > > > We should make sure that the entry iterator doesn't return entries that have expired. Since entries can sit in the data container while expired we need to make sure to ignore those. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4629) Clarify what happens when an available partition and a degraded mode partition merge

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4629?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4629: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Clarify what happens when an available partition and a degraded mode partition merge > ------------------------------------------------------------------------------------ > > Key: ISPN-4629 > URL: https://issues.jboss.org/browse/ISPN-4629 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: partition_handling > Fix For: 7.0.0.CR2 > > > I believe the implementation in https://github.com/infinispan/infinispan/pull/2785 clears the data in the degraded mode partition (since it could be stale) and then rebalances the data from the available partition on all nodes. > We should add a test to confirm and document it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4650) MassIndexer should not use UpdateDocument when adding to Lucene

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4650?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4650: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > MassIndexer should not use UpdateDocument when adding to Lucene > --------------------------------------------------------------- > > Key: ISPN-4650 > URL: https://issues.jboss.org/browse/ISPN-4650 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.0.0.Beta1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 7.0.0.CR2 > > > The MassIndexer currently causes a Delete plus and Add operation to hibernate search backend. > Lucene buffers those deletes queries and during merge it tries to 'apply' those deletes wasting a massive amount of time doing seeks and queries unnecessarily. > Since the mass indexer wipes the index at the beginning, it should simply issue an add operation (or at least rely on Lucene atomic IndexWriter.updateDocument). Performance wise this make a huge difference: > * indexing 50k documents brings down the indexing time from 195s to 33s > * indexing 200k documents brings down the indexing time from 600s to 55s -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4675) Missing server configuration for remote executor thread pool

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4675?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4675: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Missing server configuration for remote executor thread pool > ------------------------------------------------------------ > > Key: ISPN-4675 > URL: https://issues.jboss.org/browse/ISPN-4675 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 6.0.2.Final, 7.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Fix For: 7.0.0.CR2 > > > The remote commands executor configuration is missing in {{EmbeddedCacheManagerConfigurationService}}. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4660) Cache loader interceptor ignores unsafe.unreliableReturnValues setting

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4660?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4660: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Cache loader interceptor ignores unsafe.unreliableReturnValues setting > ---------------------------------------------------------------------- > > Key: ISPN-4660 > URL: https://issues.jboss.org/browse/ISPN-4660 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 7.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: performance > Fix For: 7.0.0.CR2 > > > When {{unsafe.unreliableReturnValues == true}}, we should not try to read the previous value from the loader for non-conditional, non-delta-aware writes. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4677) Map/Reduce job fails with the wrong explanation on underlying TimeoutException

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4677?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4677: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Map/Reduce job fails with the wrong explanation on underlying TimeoutException > ------------------------------------------------------------------------------ > > Key: ISPN-4677 > URL: https://issues.jboss.org/browse/ISPN-4677 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 7.0.0.Beta1 > Reporter: Sanne Grinovero > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.CR2 > > > I'm running a task which is throwing the following exception during the Map phase: > {noformat} > org.infinispan.util.concurrent.TimeoutException: Node main-NodeC-22183 timed out{noformat} > The user facing error however is this very confusing message: > {noformat}org.infinispan.commons.CacheException: java.util.concurrent.ExecutionException: Map phase executing at main-NodeA-39904 did not complete within 0 sec timeout{noformat} > I have no timeout enabled. > The problem is the instanceof operation on the cause of the error in org.infinispan.distexec.mapreduce.MapReduceTask.executeMapPhaseWithLocalReduction(Map<KOut, VOut>): the check on the type only is not good enough. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4681) Preloading from shared cachestore on a new node with non-shared index is skipping indexing

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4681?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4681: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Preloading from shared cachestore on a new node with non-shared index is skipping indexing > ------------------------------------------------------------------------------------------ > > Key: ISPN-4681 > URL: https://issues.jboss.org/browse/ISPN-4681 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 7.0.0.CR2, 7.0.0.Final > > > We have a test already: {{org.infinispan.query.persistence.SharedCacheLoaderQueryIndexTest}} > It was disabled for other reasons, mistakenly identified as a testsuite error. > The case is simple: the test is configured in such a way to trigger a newly joining node using an in-memory dummy CacheStore which is shared by both nodes, with preloading enabled. > Index storage is not shared though: uses {{ram}}. > During the preload phase of the new node, the preload code issues the {{SKIP_INDEXING}} flag.. which in this case it should not. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4684) Segments with potentially stale L1 data are not invalidated correctly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4684?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4684: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Segments with potentially stale L1 data are not invalidated correctly > --------------------------------------------------------------------- > > Key: ISPN-4684 > URL: https://issues.jboss.org/browse/ISPN-4684 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.2.Final, 7.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.0.0.CR2 > > > {{StateConsumerImpl.computeStaleL1Entries()}} uses {{newWriteCh}} instead of {{previousWriteCh}}, so the list of stale L1 segments is always empty. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4708) Make DirectoryImplementor#deleteFile apply changes asynchronously

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4708?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4708: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Make DirectoryImplementor#deleteFile apply changes asynchronously > ----------------------------------------------------------------- > > Key: ISPN-4708 > URL: https://issues.jboss.org/browse/ISPN-4708 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 7.0.0.CR2 > > > Looks like the {{deleteFile}} operation is the main responsible component for the latency generated by writing to the Lucene Directory, but this operation could be processed asynchronously by a background thread. > Configurtion API {{org.infinispan.lucene.directory.BuildContext}} could allow for an optional Executor to be passed for this purpose, and if there isn't we keep current behaviour for running it synchronously. > The tricky part I guess is making sure that the tests, which verify written consistency -including delete operations - are refactored to be able to deal with the fact that delete operations will happen eventually. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 October 2014