January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2750) Uneven request balancing via hotrod

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-2750?page=com.atlassian.jira.plugin.... ] Michal Linhard commented on ISPN-2750: -------------------------------------- I've traced resilience test runs 8-7-8 and 16-15-16 with 10 clients, but the chart doesn't give me the same look as in 32-31-32 test, at least I can't be sure for such small absolute values (under 20 ops/sec) http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0039-resi-0... http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0040-resi-1... the original chart that showed the problem: http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0036-resi-3... had the higher throughput values (around 250 ops/sec per node) In all cases I can see topology info updated in each client: http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0039-resi-0... http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0040-resi-1... http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0036-resi-3... the category "INFO New topology received Full Before" and "INFO New topology received Full After" has an entry for each client thread. In the 32-31-32 run where the problem manifests, all threads received the same topology id=62 before crash and id=67 after rejoin. Hmm, just checked the entry distribution in the failing test: http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0036-resi-3... vs the traced runs: http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0039-resi-0... http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0040-resi-1... so it seems like the hotrod servers really are following the cache topology distribution and its the cache topology itself that's weird. the trace logs for 8-7-8 and 16-15-16 runs can be found here: http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0039-resi-0... http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0039-resi-0... http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0040-resi-1... http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0040-resi-1... > Uneven request balancing via hotrod > ----------------------------------- > > Key: ISPN-2750 > URL: https://issues.jboss.org/browse/ISPN-2750 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.2.0.CR2 > Reporter: Michal Linhard > Assignee: Dan Berindei > Fix For: 5.2.0.Final > > > The load sent to servers in the cluster isn't balanced > tried in 32 node resilience tests: > http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0035-resi-3... > http://dev39.mw.lab.eng.bos.redhat.com/~mlinhard/hyperion3/run0036-resi-3... > this differs from ISPN-2632 in that the load is unbalanced from the beginning of the test. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2739) Incorrect help for "encoding" command

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2739?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2739: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1603 > Incorrect help for "encoding" command > -------------------------------------- > > Key: ISPN-2739 > URL: https://issues.jboss.org/browse/ISPN-2739 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 5.2.0.CR2 > Reporter: Martin Gencur > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 5.2.0.Final > > > The help for "encoding" command shows the following: > SYNOPSIS > encoding [cachename] > DESCRIPTION > Shows the currently selected cache or selects a cache to be used as default for CLI operations > ARGUMENTS > cachename > (optional) the name of the cache to set as default for the following operations -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2435) Cache#replace(key, old, new) method doesn't check old value on non-local invocations

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2435?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2435: ---------------------------------------- Sanne, I'll check with Mircea when he's back. > Cache#replace(key, old, new) method doesn't check old value on non-local invocations > ------------------------------------------------------------------------------------ > > Key: ISPN-2435 > URL: https://issues.jboss.org/browse/ISPN-2435 > Project: Infinispan > Issue Type: Bug > Components: Core API, Distributed Cache > Affects Versions: 5.1.8.Final, 5.2.0.Beta2 > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Priority: Critical > Fix For: 5.3.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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2015) Upgrade to Netty 3.4.5

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2015: ----------------------------------------------- jbertram(a)redhat.com made a comment on [bug 899966|https://bugzilla.redhat.com/show_bug.cgi?id=899966] Swift, I'm not exactly sure what you're asking about, but whatever it is this bug report is almost certainly the wrong place. Open a new thread on the HornetQ or AS7 community forum or leverage your Red Hat support subscription if you have one. > Upgrade to Netty 3.4.5 > ---------------------- > > Key: ISPN-2015 > URL: https://issues.jboss.org/browse/ISPN-2015 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote protocols > Affects Versions: 5.1.3.FINAL > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 5.1.5.FINAL, 5.2.0.Final > > > According to Norman, there's some important memory optimisations coming in this version, that should in theory allow us to get rid of the custom replaying decoder. > I'll do the upgrade in a separate branch and I'll pass on to QE to run: > * Data stress tests and compare with current version > * Client stress tests and compare with native Memcached and previous versions > Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2015) Upgrade to Netty 3.4.5

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2015: ----------------------------------------------- MP Swift <mp-swift(a)outlook.com> made a comment on [bug 899966|https://bugzilla.redhat.com/show_bug.cgi?id=899966] Hi, Anyone, can help me? Can I ask the org.jboss.netty.channel.Channel support getRemoteAddress support IPv6? Hope there is someone can assist me with that =) >From Swift > Upgrade to Netty 3.4.5 > ---------------------- > > Key: ISPN-2015 > URL: https://issues.jboss.org/browse/ISPN-2015 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote protocols > Affects Versions: 5.1.3.FINAL > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 5.1.5.FINAL, 5.2.0.Final > > > According to Norman, there's some important memory optimisations coming in this version, that should in theory allow us to get rid of the custom replaying decoder. > I'll do the upgrade in a separate branch and I'll pass on to QE to run: > * Data stress tests and compare with current version > * Client stress tests and compare with native Memcached and previous versions > Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2747) Drop Woodstox from the dependencies

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2747?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2747: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated. Thanks! > Drop Woodstox from the dependencies > ----------------------------------- > > Key: ISPN-2747 > URL: https://issues.jboss.org/browse/ISPN-2747 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 5.2.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.2.0.Final > > > The Woodstox jars are listed as dependencies, but Java6 (which is our minimum requirement) already provides an embedded StaX parser. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2742) Hot Rod client to log Infinispan version

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2742?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2742: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated. Thanks! > Hot Rod client to log Infinispan version > ---------------------------------------- > > Key: ISPN-2742 > URL: https://issues.jboss.org/browse/ISPN-2742 > Project: Infinispan > Issue Type: Enhancement > Components: Remote protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 5.2.0.Final > > > To help figure out client version being run. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2723) NPE using cache loader preload with Lucene directory

by Christopher Wong (JIRA)

[ https://issues.jboss.org/browse/ISPN-2723?page=com.atlassian.jira.plugin.... ] Christopher Wong commented on ISPN-2723: ---------------------------------------- Thanks, Galder. I have tried building and installing the infinispan-core.jar lib from your branch. With your latest fix, the NPE and other exceptions related to cache preloading in distributed mode that I reported in this bug report no longer occurs on my system. > NPE using cache loader preload with Lucene directory > ---------------------------------------------------- > > Key: ISPN-2723 > URL: https://issues.jboss.org/browse/ISPN-2723 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache, Loaders and Stores > Affects Versions: 5.2.0.CR1 > Reporter: Christopher Wong > Assignee: Galder Zamarreño > Fix For: 5.2.0.Final > > Attachments: infinispan.cfg.xml, infinispan.log > > > I am seeing an NPE that looks a lot like ISPN-1470, except this is happening in version 5.2.0.CR1 of Infinispan. I have configured Infinispan's Lucene directory provider for use in Hibernate Search. The Hibernate SessionFactory is configured with a JTA transaction manager. Starting with no index works fine, but if I shut down Tomcat (with shutdown.sh) and restart, a huge pile of exceptions occur, starting with an NPE. The cache configuration in infinispan.cfg.xml looks like the following. I will attach a log file excerpt with a sampling of the exceptions being logged. This only happens with distributed mode. Replicated mode is fine. I have seen this happen with both the Jdbm and file cache store. > <namedCache > name="LuceneIndexesData"> > <clustering > mode="dist"> > <stateTransfer fetchInMemoryState="true"/> > <sync > replTimeout="50000" /> > <l1 enabled="false" /> > </clustering> > <loaders shared="true" preload="true"> > <loader class="org.infinispan.loaders.file.FileCacheStore" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false"> > <properties> > <property name="location" value="/some/path/.index/data" /> > </properties> > </loader> > </loaders> > </namedCache> -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2740) NPE at AbstractEnlistmentAdapter

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2740?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2740: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > NPE at AbstractEnlistmentAdapter > -------------------------------- > > Key: ISPN-2740 > URL: https://issues.jboss.org/browse/ISPN-2740 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 5.2.0.CR2 > Reporter: Thomas Fromm > Assignee: Adrian Nistor > Fix For: 5.2.0.Final > > > Happens on local cache with pessimistic tx. > ERROR 22.01.13 17:21:31,510 [IS-dev-blade-Node-1-MThread-1] DummyTransaction ISPN000111: afterCompletion() failed for SynchronizationAdapter{localTransaction=LocalTransaction{remoteLockedNodes=null, isMarkedForRollback=false, lockedKeys=null, backupKeyLocks=null, topologyId=-1, isFromStateTransfer=false} org.infinispan.transaction.synchronization.SyncLocalTransaction@fb} org.infinispan.transaction.synchronization.SynchronizationAdapter@11a > java.lang.NullPointerException > at org.infinispan.transaction.AbstractEnlistmentAdapter.mayHaveRemoteLocks(AbstractEnlistmentAdapter.java:96) > at org.infinispan.transaction.AbstractEnlistmentAdapter.removeTransactionInfoRemotely(AbstractEnlistmentAdapter.java:86) > at org.infinispan.transaction.AbstractEnlistmentAdapter.releaseLocksForCompletedTransaction(AbstractEnlistmentAdapter.java:82) > at org.infinispan.transaction.synchronization.SynchronizationAdapter.afterCompletion(SynchronizationAdapter.java:85) > at org.infinispan.transaction.tm.DummyTransaction.notifyAfterCompletion(DummyTransaction.java:285) > at org.infinispan.transaction.tm.DummyTransaction.runCommitTx(DummyTransaction.java:334) > at org.infinispan.transaction.tm.DummyTransaction.commit(DummyTransaction.java:91) > at org.infinispan.transaction.tm.DummyBaseTransactionManager.commit(DummyBaseTransactionManager.java:102) > ... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2435) Cache#replace(key, old, new) method doesn't check old value on non-local invocations

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2435?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-2435: --------------------------------------- With six people watching this, I think a lot of people would be very happy Galder :) thanks, just keep in mind Mircea had an "almost ready" solution according to his comments above. > Cache#replace(key, old, new) method doesn't check old value on non-local invocations > ------------------------------------------------------------------------------------ > > Key: ISPN-2435 > URL: https://issues.jboss.org/browse/ISPN-2435 > Project: Infinispan > Issue Type: Bug > Components: Core API, Distributed Cache > Affects Versions: 5.1.8.Final, 5.2.0.Beta2 > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Priority: Critical > Fix For: 5.3.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

11 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2013