May 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3105) Design query API for both embedded use and Java Hot Rod client

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3105?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3105: -------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Design query API for both embedded use and Java Hot Rod client > -------------------------------------------------------------- > > Key: ISPN-3105 > URL: https://issues.jboss.org/browse/ISPN-3105 > Project: Infinispan > Issue Type: Task > Components: Querying > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 6.0.0.Alpha3, 6.0.0.Final > > > This would be the API to be replicated/exposed for the remote query as well and a subset of what we currently expose through Lucene queries. Lucene queries would still be available through a different interface. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3105) Design query API for both embedded use and Java Hot Rod client

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-3105?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-3105: -------------------------------- Summary: Design query API for both embedded use and Java Hot Rod client (was: Define an Query API abstraction that doesn't expose lucene ) > Design query API for both embedded use and Java Hot Rod client > -------------------------------------------------------------- > > Key: ISPN-3105 > URL: https://issues.jboss.org/browse/ISPN-3105 > Project: Infinispan > Issue Type: Task > Components: Querying > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > This would be the API to be replicated/exposed for the remote query as well and a subset of what we currently expose through Lucene queries. Lucene queries would still be available through a different interface. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3105) Define an Query API abstraction that doesn't expose lucene

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3105?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3105: -------------------------------- Fix Version/s: 6.0.0.Final > Define an Query API abstraction that doesn't expose lucene > ----------------------------------------------------------- > > Key: ISPN-3105 > URL: https://issues.jboss.org/browse/ISPN-3105 > Project: Infinispan > Issue Type: Task > Components: Querying > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > This would be the API to be replicated/exposed for the remote query as well and a subset of what we currently expose through Lucene queries. Lucene queries would still be available through a different interface. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3105) Define an Query API abstraction that doesn't expose lucene

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3105: ----------------------------------- Summary: Define an Query API abstraction that doesn't expose lucene Key: ISPN-3105 URL: https://issues.jboss.org/browse/ISPN-3105 Project: Infinispan Issue Type: Task Components: Querying Reporter: Mircea Markus Assignee: Adrian Nistor Fix For: 6.0.0.Alpha2 This would be the API to be replicated/exposed for the remote query as well. Lucene queries would still be available through a different interface. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3105) Define an Query API abstraction that doesn't expose lucene

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3105?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3105: -------------------------------- Description: This would be the API to be replicated/exposed for the remote query as well and a subset of what we currently expose through Lucene queries. Lucene queries would still be available through a different interface. (was: This would be the API to be replicated/exposed for the remote query as well. Lucene queries would still be available through a different interface. ) > Define an Query API abstraction that doesn't expose lucene > ----------------------------------------------------------- > > Key: ISPN-3105 > URL: https://issues.jboss.org/browse/ISPN-3105 > Project: Infinispan > Issue Type: Task > Components: Querying > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 6.0.0.Alpha2 > > > This would be the API to be replicated/exposed for the remote query as well and a subset of what we currently expose through Lucene queries. Lucene queries would still be available through a different interface. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3104) org.infinispan.statetransfer.BaseStateTransferManagerImpl#applyState uses local invocation context

by Vitalii Tymchyshyn (JIRA)

Vitalii Tymchyshyn created ISPN-3104: ---------------------------------------- Summary: org.infinispan.statetransfer.BaseStateTransferManagerImpl#applyState uses local invocation context Key: ISPN-3104 URL: https://issues.jboss.org/browse/ISPN-3104 Project: Infinispan Issue Type: Feature Request Affects Versions: 5.1.6.FINAL Reporter: Vitalii Tymchyshyn Assignee: Mircea Markus Currently when remote state is received, it's applied under local invocation context, so every listener receives events with isOriginLocal() == true that is not correct. We are trying to prevent any cache modification while we are not quorum to prevent split brain problems, but currently it's not working because of the problem. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3103) StateRequestCommand requests serialization of type for which no Externalizer exists

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3103?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3103: ---------------------------------- Priority: Critical (was: Major) > StateRequestCommand requests serialization of type for which no Externalizer exists > ----------------------------------------------------------------------------------- > > Key: ISPN-3103 > URL: https://issues.jboss.org/browse/ISPN-3103 > Project: Infinispan > Issue Type: Enhancement > Components: State transfer > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Priority: Critical > > RPC org.infinispan.statetransfer.StateRequestCommand sends a parameter defined as type Set (field segments) which is implemented by a java.util.concurrent.CopyOnWriteArraySet. > This implementation is Serializable but seems to be quite slow as we don't have a custom Externalizer for it. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3103) StateRequestCommand requests serialization of type for which no Externalizer exists

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3103: ------------------------------------- Summary: StateRequestCommand requests serialization of type for which no Externalizer exists Key: ISPN-3103 URL: https://issues.jboss.org/browse/ISPN-3103 Project: Infinispan Issue Type: Enhancement Components: State transfer Reporter: Sanne Grinovero Assignee: Mircea Markus RPC org.infinispan.statetransfer.StateRequestCommand sends a parameter defined as type Set (field segments) which is implemented by a java.util.concurrent.CopyOnWriteArraySet. This implementation is Serializable but seems to be quite slow as we don't have a custom Externalizer for it. -- 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

11 years, 4 months

1
0
0 / 0

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

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3102?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3102: -------------------------------- Priority: Blocker (was: Critical) > 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: Mircea Markus > Priority: Blocker > Fix For: 5.3.0.CR1, 5.3.0.Final > > > 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

11 years, 4 months

1
0
0 / 0

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

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3102?page=com.atlassian.jira.plugin.... ] Mircea Markus edited comment on ISPN-3102 at 5/15/13 7:41 AM: -------------------------------------------------------------- Marking this as blocker as we need to investigate if the performance regression was introduced in Infinispan 5.3 or it was present in 5.2 as well. If later, this shouldn't stop the 5.3 release. was (Author: mircea.markus): Marking this as critical as we need to investigate if the performance regression was introduced in Infinispan 5.3 or it was present in 5.2 as well. If later, this shouldn't stop the 5.3 release. > 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: Mircea Markus > Priority: Blocker > Fix For: 5.3.0.CR1, 5.3.0.Final > > > 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

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2013