October 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3593) Disallow storing a Lucene index when storeAsBinary is enabled

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3593: ------------------------------------- Summary: Disallow storing a Lucene index when storeAsBinary is enabled Key: ISPN-3593 URL: https://issues.jboss.org/browse/ISPN-3593 Project: Infinispan Issue Type: Enhancement Components: Lucene Directory Affects Versions: 6.0.0.CR1 Reporter: Sanne Grinovero Assignee: Pedro Ruivo Fix For: 6.0.0.Final As discussed on the mailing list, this configuration doesn't make sense for the Lucene Directory and can cause trouble. Let's add some validation to throw a runtime exception to disallow this configuration when a Directory is created on a cache. Could probably be done in a very similar way as: https://github.com/infinispan/infinispan/commit/2f6447e197abe2e9e62c796ab... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3592) Regression in Lucene Directory: NPE during SegmentInfos.getLastCommitGeneration

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3592?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3592: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2142 > Regression in Lucene Directory: NPE during SegmentInfos.getLastCommitGeneration > ------------------------------------------------------------------------------- > > Key: ISPN-3592 > URL: https://issues.jboss.org/browse/ISPN-3592 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 6.0.0.CR1 > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Blocker > Fix For: 6.0.0.Final > > > The problem is a very recent regression, so relative to 6.0.0.CR1 only. > {noformat} > java.lang.NullPointerException > at org.apache.lucene.index.SegmentInfos.getLastCommitGeneration(SegmentInfos.java:160) > at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:605) > at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:554) > at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:359) > at org.apache.lucene.index.SegmentInfos.readCurrentVersion(SegmentInfos.java:483) > at org.apache.lucene.index.DirectoryReader.isCurrent(DirectoryReader.java:891) > at org.apache.lucene.index.DirectoryReader.doOpenNoWriter(DirectoryReader.java:455) > at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:434) > at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:375) > at org.apache.lucene.index.IndexReader.openIfChanged(IndexReader.java:508) > at org.apache.lucene.index.IndexReader.reopen(IndexReader.java:695) > at org.infinispan.lucene.profiling.LuceneReaderThread.refreshIndexReader(LuceneReaderThread.java:58) > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3592) Regression in Lucene Directory: NPE during SegmentInfos.getLastCommitGeneration

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3592: ------------------------------------- Summary: Regression in Lucene Directory: NPE during SegmentInfos.getLastCommitGeneration Key: ISPN-3592 URL: https://issues.jboss.org/browse/ISPN-3592 Project: Infinispan Issue Type: Bug Components: Lucene Directory Affects Versions: 6.0.0.CR1 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Blocker Fix For: 6.0.0.Final The problem is a very recent regression, so relative to 6.0.0.CR1 only. {noformat} java.lang.NullPointerException at org.apache.lucene.index.SegmentInfos.getLastCommitGeneration(SegmentInfos.java:160) at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:605) at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:554) at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:359) at org.apache.lucene.index.SegmentInfos.readCurrentVersion(SegmentInfos.java:483) at org.apache.lucene.index.DirectoryReader.isCurrent(DirectoryReader.java:891) at org.apache.lucene.index.DirectoryReader.doOpenNoWriter(DirectoryReader.java:455) at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:434) at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:375) at org.apache.lucene.index.IndexReader.openIfChanged(IndexReader.java:508) at org.apache.lucene.index.IndexReader.reopen(IndexReader.java:695) at org.infinispan.lucene.profiling.LuceneReaderThread.refreshIndexReader(LuceneReaderThread.java:58) {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3102) Analyse the performance of MassIndexingTest

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3102?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-3102: --------------------------------------- +1 [~anistor], thanks for the inspection! > Analyse the performance of MassIndexingTest > ------------------------------------------- > > Key: ISPN-3102 > URL: https://issues.jboss.org/browse/ISPN-3102 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 6.0.0.CR1 > > > MassIndexingTest runs on CI in 10 mins with TRACE on and 3 mins with TRACE off. According to Sanne this shouldn't take that long: > {quote} > sannegrinovero > 11:50 mmarkus: the org.infinispan.query.distributed.MassIndexingTest test is adding 2000 entries to the cache. True that might be a bit excessive, still if it takes 10 minutes you have a problem in Infinispan core. > mmarkus > 11:52 sannegrinovero: each such write is indexed I take it? > sannegrinovero > 11:53 mmarkus: no: withFlags(Flag.SKIP_INDEXING) > 11:54 mmarkus: but it's a 4 node DIST test using Map/Reduce. > sannegrinovero > 11:54 then the Map/Reduce job does some indexing but the indexing engine didn't change overnight > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3591) Upgrade Lucene Directory to support Apache Lucene version 4.5

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3591?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3591: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2141 > Upgrade Lucene Directory to support Apache Lucene version 4.5 > ------------------------------------------------------------- > > Key: ISPN-3591 > URL: https://issues.jboss.org/browse/ISPN-3591 > Project: Infinispan > Issue Type: Component Upgrade > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 6.0.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3591) Upgrade Lucene Directory to support Apache Lucene version 4.5

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3591: ------------------------------------- Summary: Upgrade Lucene Directory to support Apache Lucene version 4.5 Key: ISPN-3591 URL: https://issues.jboss.org/browse/ISPN-3591 Project: Infinispan Issue Type: Component Upgrade Components: Lucene Directory Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 6.0.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2879) Have ResultIterator implement AutoCloseable

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2879?page=com.atlassian.jira.plugin.... ] Sanne Grinovero resolved ISPN-2879. ----------------------------------- Resolution: Duplicate Issue > Have ResultIterator implement AutoCloseable > -------------------------------------------- > > Key: ISPN-2879 > URL: https://issues.jboss.org/browse/ISPN-2879 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > > Assuming we'll baseline on Java7, it would be very nice to have the following code valid and changing the default Fetch to LAZY: > {code} > Query query = queryBuilder.all().createQuery(); > CacheQuery cacheQuery = searchManager.getQuery(query, Bean.class); > for (Object object : cacheQuery) { > ... > }{code} > the problem is the implicit iterable opened needs to be closed. > see also ISPN-2874. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3583) When indexing is enabled but Query module isn't available configuration validation should fail

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3583?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3583: ---------------------------------- Assignee: Dan Berindei (was: Sanne Grinovero) > When indexing is enabled but Query module isn't available configuration validation should fail > ---------------------------------------------------------------------------------------------- > > Key: ISPN-3583 > URL: https://issues.jboss.org/browse/ISPN-3583 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Querying > Reporter: Sanne Grinovero > Assignee: Dan Berindei > Priority: Minor > Fix For: 6.0.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3398) Unmarshall problem in compatibility mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3398?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3398: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 993738|https://bugzilla.redhat.com/show_bug.cgi?id=993738] from MODIFIED to ON_QA > Unmarshall problem in compatibility mode > ---------------------------------------- > > Key: ISPN-3398 > URL: https://issues.jboss.org/browse/ISPN-3398 > Project: Infinispan > Issue Type: Bug > Components: Marshalling, Remote protocols, Server > Affects Versions: 5.3.0.Final, 6.0.0.Alpha2 > Reporter: Michal Linhard > Assignee: Pedro Ruivo > Priority: Critical > Labels: jdg62blocker > Fix For: 6.0.0.Beta2, 6.0.0.Final > > > JDG 6.2.0.DR2 client/server tests using hotrod and cache in compatibility mode: > throw this: > {code} > 04:48:28,445 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (remote-thread-0) ISPN000136: Execution error: java.io.IOException: Unsupported protocol version 9 > at org.jboss.marshalling.river.RiverUnmarshaller.start(RiverUnmarshaller.java:1243) > at org.infinispan.commons.marshall.jboss.AbstractJBossMarshaller.startObjectInput(AbstractJBossMarshaller.java:138) [infinispan-commons-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commons.marshall.jboss.AbstractJBossMarshaller.objectFromByteBuffer(AbstractJBossMarshaller.java:119) [infinispan-commons-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commons.marshall.AbstractMarshaller.objectFromByteBuffer(AbstractMarshaller.java:83) [infinispan-commons-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.server.hotrod.HotRodTypeConverter.unmarshall(HotRodTypeConverter.scala:36) [infinispan-server-hotrod-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.server.hotrod.HotRodTypeConverter.boxValue(HotRodTypeConverter.scala:22) [infinispan-server-hotrod-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.interceptors.compat.TypeConverterInterceptor.visitPutKeyValueCommand(TypeConverterInterceptor.java:72) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:106) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:70) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:32) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:321) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commands.remote.BaseRpcInvokingCommand.processVisitableCommand(BaseRpcInvokingCommand.java:39) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.commands.remote.SingleRpcCommand.perform(SingleRpcCommand.java:48) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.remoting.InboundInvocationHandlerImpl.handleInternal(InboundInvocationHandlerImpl.java:97) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.remoting.InboundInvocationHandlerImpl.access$000(InboundInvocationHandlerImpl.java:46) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at org.infinispan.remoting.InboundInvocationHandlerImpl$2.run(InboundInvocationHandlerImpl.java:169) [infinispan-core-6.0.0.Alpha2-redhat-1.jar:6.0.0.Alpha2-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} > the exception appears for each request, the form is always > "Unsupported protocol version X" where X differs > see > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/PERF-CS/jo... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/PERF-CS/jo... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3443) WriteCommand may be ignored during state transfer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3443?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3443: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1001634|https://bugzilla.redhat.com/show_bug.cgi?id=1001634] from MODIFIED to ON_QA > WriteCommand may be ignored during state transfer > ------------------------------------------------- > > Key: ISPN-3443 > URL: https://issues.jboss.org/browse/ISPN-3443 > Project: Infinispan > Issue Type: Bug > Components: Locking and Concurrency, State transfer > Affects Versions: 6.0.0.Alpha3 > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Blocker > Labels: jdg62blocker > Fix For: 6.0.0.CR1 > > > Distributed sync non-tx cache. > Situation: > 1) A node is joining the cluster, requesting some segment > 2) RemoveCommand is sent to backup owner with ignorePreviousValue=true > 3) It looks up the entry and finds null > 4) State transfer invokes the PutKeyValueCommand and sets the value for removed entry (updateKeys has not the key yet) > 5) RemoveCommand adds its key to updateKeys set, but it does not remove the value as it is already null (in its context) > Result: the value is removed on primary but on backup this is still present -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 2013