October 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-825) Consider staggering remote get requests when using DIST

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-825?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-825: ------------------------------- Assignee: William Burns (was: Mircea Markus) > Consider staggering remote get requests when using DIST > ------------------------------------------------------- > > Key: ISPN-825 > URL: https://issues.jboss.org/browse/ISPN-825 > Project: Infinispan > Issue Type: Feature Request > Components: RPC > Affects Versions: 4.1.0.Final > Reporter: Manik Surtani > Assignee: William Burns > Priority: Critical > Labels: optimization, performance > > In DIST mode, when a request is made on a key that is not mapped locally, a remote get is sent to all data owners of that key and the first response is used. This can add unnecessary load on the network as all nodes still eventually respond, and if values are large this can cause a lot of unnecessary network traffic. > The purpose of broadcasting to all data owners is so that (1) if one is down, another could still respond (2) if one is overloaded, others may respond faster. > A solution around this could be based on either (or both) of: > * Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1. Wait for timeout t. If no response, RPC to Owner2. etc. > * Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners is 5. > Needs careful thought and design. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3635) Out of data read after write on node losing ownership

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3635?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3635: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2173 > Out of data read after write on node losing ownership > ----------------------------------------------------- > > Key: ISPN-3635 > URL: https://issues.jboss.org/browse/ISPN-3635 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache, State transfer > Affects Versions: 5.3.0.Final > Reporter: Radim Vansa > Assignee: Pedro Ruivo > Priority: Critical > Labels: jdg62blocker > Fix For: 6.0.0.Final > > > In a situation where a node is losing ownership of an entry (during a state transfer), when the node does a write (and commits that), the change is propagated only to the new owners, the entry is not written locally. However, when it executes read for this key afterwards, it gets the old value as this is directly retrieved from the data container. > This bug was observed in transactional mode, but might not be limited to 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3617) Inconsistent L1 in non-tx distributed cache

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3617?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-3617: ------------------------------------- Radim, I think it is just an artifact of code since refactored. The wrapping itself doesn't cause the entry to be removed, that is done through a command. I have changed the code to also send down an invalidation command after it is wrapped which fixes the issue in my test. > Inconsistent L1 in non-tx distributed cache > ------------------------------------------- > > Key: ISPN-3617 > URL: https://issues.jboss.org/browse/ISPN-3617 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.7.Final > Reporter: Radim Vansa > Assignee: William Burns > Priority: Critical > Labels: jdg62blocker > Fix For: 6.0.0.CR2, 6.0.0.Final > > > When the change is replicated to backup owner, it sends the InvalidateL1Command to backup owners before committing the entry in EntryWrappingInterceptor (it performs the WriteCommand in parallel with sending the invalidation commmand, but then it waits until the invalidation request gets acked. If a GET is executed between the invalidation and committing the entry, the response contains outdated result and the L1 will not be invalidated until next write operation. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3653) Add possibility to run Infinispan-server testsuite also with 1.6xx JDKs

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-3653?page=com.atlassian.jira.plugin.... ] Jiří Holuša updated ISPN-3653: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan-server/pull/178 > Add possibility to run Infinispan-server testsuite also with 1.6xx JDKs > ----------------------------------------------------------------------- > > Key: ISPN-3653 > URL: https://issues.jboss.org/browse/ISPN-3653 > Project: Infinispan > Issue Type: Bug > Reporter: Tomas Sykora > Assignee: Jiří Holuša > Fix For: 6.0.0.CR2 > > > Currently, there is a restriction in Infinispan-server set by maven-enforcer-plugin as > <requireJavaVersion> > <version>[1.7,)</version> > </requireJavaVersion> > This prevents us from comfortable running Infinispan-server testsuite with JDKs version 1.6 etc. > As this restriction is required, it's needed to implement new profile for running tests with JDKs 1.6. > See *jdk6testsuite* profile here, in Infinispan parent/pom.xml, which solves this already for Infinispan: https://github.com/infinispan/infinispan/blob/master/parent/pom.xml -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2359) Query should not reindex cache entries on preload or activation

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2359?page=com.atlassian.jira.plugin.... ] Work on ISPN-2359 started by Adrian Nistor. > Query should not reindex cache entries on preload or activation > --------------------------------------------------------------- > > Key: ISPN-2359 > URL: https://issues.jboss.org/browse/ISPN-2359 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Labels: stable_embedded_query > > If a cache entry is returning to the Infinispan datacontainer after activation or preloading it should not be re-indexed. > Check also that passivation doesn't remove the entry from the index. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3653) Add possibility to run Infinispan-server testsuite also with 1.6xx JDKs

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-3653?page=com.atlassian.jira.plugin.... ] Martin Gencur reassigned ISPN-3653: ----------------------------------- Assignee: Jiří Holuša (was: Mircea Markus) Assigning this to Jiri. > Add possibility to run Infinispan-server testsuite also with 1.6xx JDKs > ----------------------------------------------------------------------- > > Key: ISPN-3653 > URL: https://issues.jboss.org/browse/ISPN-3653 > Project: Infinispan > Issue Type: Bug > Reporter: Tomas Sykora > Assignee: Jiří Holuša > Fix For: 6.0.0.CR2 > > > Currently, there is a restriction in Infinispan-server set by maven-enforcer-plugin as > <requireJavaVersion> > <version>[1.7,)</version> > </requireJavaVersion> > This prevents us from comfortable running Infinispan-server testsuite with JDKs version 1.6 etc. > As this restriction is required, it's needed to implement new profile for running tests with JDKs 1.6. > See *jdk6testsuite* profile here, in Infinispan parent/pom.xml, which solves this already for Infinispan: https://github.com/infinispan/infinispan/blob/master/parent/pom.xml -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3654) Consolidate Infinispan and JDG Quickstarts and Demos

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3654: ------------------------------------- Summary: Consolidate Infinispan and JDG Quickstarts and Demos Key: ISPN-3654 URL: https://issues.jboss.org/browse/ISPN-3654 Project: Infinispan Issue Type: Task Reporter: Tristan Tarrant Assignee: Tristan Tarrant -- 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, 2 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3592?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3592: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> changed the Status of [bug 1018097|https://bugzilla.redhat.com/show_bug.cgi?id=1018097] from ON_QA to VERIFIED > 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

11 years, 2 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3592?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3592: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> made a comment on [bug 1018097|https://bugzilla.redhat.com/show_bug.cgi?id=1018097] I've run the test org.infinispan.lucene.profiling.PerformanceCompareStressTest.profileInfinispanLocalDirectory() using JDG_6.2.0.ER3 and JDG_6.2.0.ER3.1. For the first one the test fails, for the newest tag, it passes. The issue is verified. > 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3653) Add possibility to run Infinispan-server testsuite also with 1.6xx JDKs

by Tomas Sykora (JIRA)

Tomas Sykora created ISPN-3653: ---------------------------------- Summary: Add possibility to run Infinispan-server testsuite also with 1.6xx JDKs Key: ISPN-3653 URL: https://issues.jboss.org/browse/ISPN-3653 Project: Infinispan Issue Type: Bug Reporter: Tomas Sykora Assignee: Mircea Markus Fix For: 6.0.0.CR2 Currently, there is a restriction in Infinispan-server set by maven-enforcer-plugin as <requireJavaVersion> <version>[1.7,)</version> </requireJavaVersion> This prevents us from comfortable running Infinispan-server testsuite with JDKs version 1.6 etc. As this restriction is required, it's needed to implement new profile for running tests with JDKs 1.6. See *jdk6testsuite* profile here, in Infinispan parent/pom.xml, which solves this already for Infinispan: https://github.com/infinispan/infinispan/blob/master/parent/pom.xml -- 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, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2013