April 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4162) Can DIST use multicast when num_owners >= cluster size?

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4162?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-4162. -------------------------------- Fix Version/s: 6.0.0.Final Resolution: Partially Completed There might be some slight overhead left in DIST, e.g. it will probably do some extra list copying and merging than REPL. But at least at the network level, they're equivalent. > Can DIST use multicast when num_owners >= cluster size? > ------------------------------------------------------- > > Key: ISPN-4162 > URL: https://issues.jboss.org/browse/ISPN-4162 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 7.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Dan Berindei > Fix For: 6.0.0.Final > > > It would be nice if DIST could conditionally use multicast instead of multiple unicasts when the number of owners to which to send a given command >= the size of the cluster. In fact, we could probably come up with some configurable ratio of the size of the cluster (perhaps as high as 50%?), above which it is more optimal to use multicast vs multiple unicasts. This would optimize the use of DIST in smaller, dynamic clusters. > With such an optimization in place, REPL would be completely obsolete. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4200) ExampleConfigsTest.testRestRollingUpgrades fails

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4200?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4200: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1086180 > ExampleConfigsTest.testRestRollingUpgrades fails > ------------------------------------------------ > > Key: ISPN-4200 > URL: https://issues.jboss.org/browse/ISPN-4200 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Jakub Markos > Assignee: Mircea Markus > > Fails in the latest snapshot on line 240 with > {code} > Can't access etries stored in source node (target's RestCacheStore). expected:<value1> but was:<[B@19676adb> > {code} > you can run the test from /server/integration/testsuite with this command: > mvn clean test -Psuite.examples -Dtest=ExampleConfigsTest#testRestRollingUpgrades > The configs used are /server/integration/testsuite/target/server/node1/standalone/configuration/examples/{standalone-rest-rolling-upgrade.xml, standalone-compatibility-mode.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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4200) ExampleConfigsTest.testRestRollingUpgrades fails

by Jakub Markos (JIRA)

Jakub Markos created ISPN-4200: ---------------------------------- Summary: ExampleConfigsTest.testRestRollingUpgrades fails Key: ISPN-4200 URL: https://issues.jboss.org/browse/ISPN-4200 Project: Infinispan Issue Type: Bug Components: Test Suite - Server Reporter: Jakub Markos Assignee: Mircea Markus Fails in the latest snapshot on line 240 with {code} Can't access etries stored in source node (target's RestCacheStore). expected:<value1> but was:<[B@19676adb> {code} you can run the test from /server/integration/testsuite with this command: mvn clean test -Psuite.examples -Dtest=ExampleConfigsTest#testRestRollingUpgrades The configs used are /server/integration/testsuite/target/server/node1/standalone/configuration/examples/{standalone-rest-rolling-upgrade.xml, standalone-compatibility-mode.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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3761) Tests from org.infinispan.query.dsl.embedded package fail on all environmets

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3761?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3761: -------------------------------- Fix Version/s: 7.0.0.Alpha3 7.0.0.Final > Tests from org.infinispan.query.dsl.embedded package fail on all environmets > ---------------------------------------------------------------------------- > > Key: ISPN-3761 > URL: https://issues.jboss.org/browse/ISPN-3761 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Environment: OS: Windows 2012 64bit > Reporter: Jiří Holuša > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha3, 7.0.0.Final > > Attachments: log.txt > > > * Method throws assertion ERROR on Windows > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.createBeforeMethod > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > * These tests are failing periodically on Windows: > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testIteration3 > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testIteration4 > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testIteration5 > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testOrderByAsc > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testOrderByDesc > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testProjection1 > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testStartOffset > * This test failed only once out of three times: > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testMaxResults > * Test fails very often on RHEL > ** org.infinispan.query.dsl.embedded.ClusteredQueryDslConditionsTest.testSampleDomainQuery16 > here is trace log https://www.dropbox.com/s/yvrbs2i2tvh0wzz/ClusteredQueryDslConditionsTest... -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3761) Tests from org.infinispan.query.dsl.embedded package fail on all environmets

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3761?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3761: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Tests from org.infinispan.query.dsl.embedded package fail on all environmets > ---------------------------------------------------------------------------- > > Key: ISPN-3761 > URL: https://issues.jboss.org/browse/ISPN-3761 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Environment: OS: Windows 2012 64bit > Reporter: Jiří Holuša > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha3, 7.0.0.Final > > Attachments: log.txt > > > * Method throws assertion ERROR on Windows > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.createBeforeMethod > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > * These tests are failing periodically on Windows: > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testIteration3 > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testIteration4 > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testIteration5 > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testOrderByAsc > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testOrderByDesc > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testProjection1 > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testStartOffset > * This test failed only once out of three times: > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testMaxResults > * Test fails very often on RHEL > ** org.infinispan.query.dsl.embedded.ClusteredQueryDslConditionsTest.testSampleDomainQuery16 > here is trace log https://www.dropbox.com/s/yvrbs2i2tvh0wzz/ClusteredQueryDslConditionsTest... -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3761) Tests from org.infinispan.query.dsl.embedded package fail on all environmets

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3761?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned ISPN-3761: ----------------------------------- Assignee: Martin Gencur (was: Mircea Markus) Integrated in master. Thanks! > Tests from org.infinispan.query.dsl.embedded package fail on all environmets > ---------------------------------------------------------------------------- > > Key: ISPN-3761 > URL: https://issues.jboss.org/browse/ISPN-3761 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Environment: OS: Windows 2012 64bit > Reporter: Jiří Holuša > Assignee: Martin Gencur > Attachments: log.txt > > > * Method throws assertion ERROR on Windows > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.createBeforeMethod > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > * These tests are failing periodically on Windows: > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testIteration3 > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testIteration4 > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testIteration5 > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testOrderByAsc > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testOrderByDesc > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testProjection1 > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testStartOffset > * This test failed only once out of three times: > ** org.infinispan.query.dsl.embedded.FilesystemQueryDslIterationTest.testMaxResults > * Test fails very often on RHEL > ** org.infinispan.query.dsl.embedded.ClusteredQueryDslConditionsTest.testSampleDomainQuery16 > here is trace log https://www.dropbox.com/s/yvrbs2i2tvh0wzz/ClusteredQueryDslConditionsTest... -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4199) Server logs that databaseType is ignored, when it's really not

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4199?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4199: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1086158 > Server logs that databaseType is ignored, when it's really not > -------------------------------------------------------------- > > Key: ISPN-4199 > URL: https://issues.jboss.org/browse/ISPN-4199 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Server > Reporter: Jakub Markos > Assignee: Dan Berindei > > In current snapshot, when you configure the databaseType property for the jdbc cache store, server logs: > {code} > 11:10:21,088 WARN [org.infinispan.configuration.parsing.XmlConfigHelper] (ServerService Thread Pool -- 18) ISPN000282: Unrecognized attribute databaseType. Please check your configuration. Ignoring!! > {code} -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4199) Server logs that databaseType is ignored, when it's really not

by Jakub Markos (JIRA)

Jakub Markos created ISPN-4199: ---------------------------------- Summary: Server logs that databaseType is ignored, when it's really not Key: ISPN-4199 URL: https://issues.jboss.org/browse/ISPN-4199 Project: Infinispan Issue Type: Bug Components: Loaders and Stores, Server Reporter: Jakub Markos Assignee: Dan Berindei In current snapshot, when you configure the databaseType property for the jdbc cache store, server logs: {code} 11:10:21,088 WARN [org.infinispan.configuration.parsing.XmlConfigHelper] (ServerService Thread Pool -- 18) ISPN000282: Unrecognized attribute databaseType. Please check your configuration. Ignoring!! {code} -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2916) Group-based expiration

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-2916?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on ISPN-2916: ------------------------------------ OK - thanks for the clarification [~dan.berindei] As for point #2, when using pessimistic locking (our default), we already perform our read of the primary entry of a group using Flag.FORCE_WRITE_LOCK, so I think we should be ok. > Group-based expiration > ---------------------- > > Key: ISPN-2916 > URL: https://issues.jboss.org/browse/ISPN-2916 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 5.2.5.Final > Reporter: Paul Ferraro > Assignee: Mircea Markus > > Now that WildFly represents a web session as a group of cache entries (instead of a single entry containing an atomic map), there are a few hurdles preventing us from leveraging infinispan-managed expiration. > One of which is the fact that expiration of cache entries within a group *must* be atomic. It would be very bad if a request arrives for a session whose entries are in the process of being expired. The expiration thread should obtain a lock on *all* the keys for a group (or at least some pre-determined "primary" key), so that late session access doesn't result in session attributes mysteriously disappearing (because they were independently expired). This can also cause integrity constraint violations if cache entries reference other entries in the group. e.g. currently the "primary" cache entry for a session (keyed by session id), contains a set of attribute names. These names correspond to other cache entries that contain the value of a given attribute for that session. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-4162) Can DIST use multicast when num_owners >= cluster size?

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-4162?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on ISPN-4162: ------------------------------------ After our last F2F meeting, I was under the impression that this optimization was not in place. I guess I was mistaken. I guess we can close this then? > Can DIST use multicast when num_owners >= cluster size? > ------------------------------------------------------- > > Key: ISPN-4162 > URL: https://issues.jboss.org/browse/ISPN-4162 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 7.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Dan Berindei > > It would be nice if DIST could conditionally use multicast instead of multiple unicasts when the number of owners to which to send a given command >= the size of the cluster. In fact, we could probably come up with some configurable ratio of the size of the cluster (perhaps as high as 50%?), above which it is more optimal to use multicast vs multiple unicasts. This would optimize the use of DIST in smaller, dynamic clusters. > With such an optimization in place, REPL would be completely obsolete. -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2014