May 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3075) Infinispan CLI does not work on windows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3075?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3075: ----------------------------------------------- dereed(a)redhat.com made a comment on [bug 959539|https://bugzilla.redhat.com/show_bug.cgi?id=959539] Same issue as https://issues.jboss.org/browse/AS7-6169 for EAP > Infinispan CLI does not work on windows > --------------------------------------- > > Key: ISPN-3075 > URL: https://issues.jboss.org/browse/ISPN-3075 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 5.2.4.Final > Reporter: Dennis Reed > Assignee: Tristan Tarrant > > Same as https://issues.jboss.org/browse/AS7-6169 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3075) Infinispan CLI does not work on windows

by Dennis Reed (JIRA)

Dennis Reed created ISPN-3075: --------------------------------- Summary: Infinispan CLI does not work on windows Key: ISPN-3075 URL: https://issues.jboss.org/browse/ISPN-3075 Project: Infinispan Issue Type: Bug Components: CLI Affects Versions: 5.2.4.Final Reporter: Dennis Reed Assignee: Tristan Tarrant Same as https://issues.jboss.org/browse/AS7-6169 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-999) Support eventual consistency

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-999?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-999: ------------------------------- Fix Version/s: 7.0.0.Final (was: 6.0.0.Final) > Support eventual consistency > ---------------------------- > > Key: ISPN-999 > URL: https://issues.jboss.org/browse/ISPN-999 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache, Locking and Concurrency > Reporter: Manik Surtani > Assignee: Manik Surtani > Priority: Critical > Labels: eventual_consistency > Fix For: 7.0.0.Final > > Original Estimate: 1 minute > Remaining Estimate: 1 minute > > Essentially, it is about supporting eventual consistency in Infinispan. Currently Infinispan is strongly consistent when using synchronous distribution mode. Each data owner receives updates synchronously so anyone anywhere on the cluster doing a GET will see the correct value. The only exception is during a rehash (when a new node joins or leaves), that consistency is eventual since the GET may reach a new joiner who may not have applied state it receives from its neighbours yet. However this is hidden from users since the GET is sent to> 1 data owner and if an UnsureResponse is received (determined by the fact that a new joiner responds and the new joiner wouldn't have finished applying state), the caller thread waits for more definite responses. > However, there is a use case for being eventually consistent as well: the main benefits being speed and partition tolerance. E.g., if we use distribution in asynchronous mode, the writes become *much* faster. However, anyone anywhere doing a GET will have to perform the GET on all data owners, and compare the versions of the data received to determine which is the latest. And if there is a conflict, to pass back all values to the user. > So in terms of design, what I have in mind is: > * All cache entries are versioned using vector clocks. One vector clock per node. > * When a node performs a GET, the GET is sent to all data owners (concurrently), and the value + version is retrieved from each. > * If the versions are all the same (or they can be "fast forwarded"), the value is returned > * Otherwise, all potential values and their versions are returned > * A resolve() API should be provided where application code may provide a "hint" as to which version should be "correct" - which will cause an update. > * In terms of implementation, this will touch the DistributionInterceptor, InternalCacheEntry and relevant factories, some config code (since this should be consistency model should be configurable), and a new public 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3027) Update Lucene Directory to support Lucene 4.3

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3027?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3027: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1803 > Update Lucene Directory to support Lucene 4.3 > --------------------------------------------- > > Key: ISPN-3027 > URL: https://issues.jboss.org/browse/ISPN-3027 > Project: Infinispan > Issue Type: Component Upgrade > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 5.3.0.Beta2, 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3008) HotRod Servers sharing a container should check for a compatible topology cache

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3008?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3008: ---------------------------------- Summary: HotRod Servers sharing a container should check for a compatible topology cache (was: HotRod Server should check if topology cache already exists) > HotRod Servers sharing a container should check for a compatible topology cache > ------------------------------------------------------------------------------- > > Key: ISPN-3008 > URL: https://issues.jboss.org/browse/ISPN-3008 > Project: Infinispan > Issue Type: Task > Components: Remote protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.3.0.Beta2 > > > The HotRod Server always creates a topology cache. If the same cache container is shared by multiple endpoints this causes problems. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3008) HotRod Servers sharing a container should check for a compatible topology cache

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3008?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3008: ---------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/1802 > HotRod Servers sharing a container should check for a compatible topology cache > ------------------------------------------------------------------------------- > > Key: ISPN-3008 > URL: https://issues.jboss.org/browse/ISPN-3008 > Project: Infinispan > Issue Type: Task > Components: Remote protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.3.0.Beta2 > > > The HotRod Server always creates a topology cache. If the same cache container is shared by multiple endpoints this causes problems. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2162) ParallelCacheStartTest.testParallelStartup fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2162?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2162: -------------------------------- Fix Version/s: 5.3.0.Beta2 (was: 5.3.0.Beta1) > ParallelCacheStartTest.testParallelStartup fails randomly > --------------------------------------------------------- > > Key: ISPN-2162 > URL: https://issues.jboss.org/browse/ISPN-2162 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Galder Zamarreño > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 5.3.0.Beta2 > > > Failed tests: testParallelStartup(org.infinispan.api.ParallelCacheStartTest): Timed out before caches had complete views. Expected 1 members in each view. Views are as follows: [[ParallelCacheStartTest-NodeA-41416, ParallelCacheStartTest-NodeB-21482]] -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2264) DistL1WriteSkewTest.testSharedCounter failing randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2264?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2264: -------------------------------- Fix Version/s: 5.3.0.Beta2 (was: 5.3.0.Beta1) > DistL1WriteSkewTest.testSharedCounter failing randomly > ------------------------------------------------------ > > Key: ISPN-2264 > URL: https://issues.jboss.org/browse/ISPN-2264 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Adrian Nistor > Labels: testsuite_stability > Fix For: 5.3.0.Beta2 > > > {code}Failed tests: > testSharedCounter(org.infinispan.container.versioning.DistL1WriteSkewTest): > Timed out waiting for updater threads{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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2160) ReplWriteSkewTest.testSharedCounter failing randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2160?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2160: -------------------------------- Fix Version/s: 5.3.0.Beta2 (was: 5.3.0.Beta1) > ReplWriteSkewTest.testSharedCounter failing randomly > ---------------------------------------------------- > > Key: ISPN-2160 > URL: https://issues.jboss.org/browse/ISPN-2160 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Galder Zamarreño > Assignee: Adrian Nistor > Labels: testsuite_stability > Fix For: 5.3.0.Beta2 > > > Failing randomly with: > {code}Failed tests: > testSharedCounter(org.infinispan.container.versioning.ReplWriteSkewTest): > Node-2 has put a duplicate value{code} > TRACE logs coming right up -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2161) InitiatorCrashPessimisticReplTest.testInitiatorNodeCrashesBeforeCommit fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2161?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2161: -------------------------------- Fix Version/s: 5.3.0.Beta2 (was: 5.3.0.Beta1) > InitiatorCrashPessimisticReplTest.testInitiatorNodeCrashesBeforeCommit fails randomly > ------------------------------------------------------------------------------------- > > Key: ISPN-2161 > URL: https://issues.jboss.org/browse/ISPN-2161 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Galder Zamarreño > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 5.3.0.Beta2 > > Attachments: testInitiatorNodeCrashesBeforeCommit-0.log > > > Failed tests: testInitiatorNodeCrashesBeforeCommit(org.infinispan.lock.singlelock.replicated.pessimistic.InitiatorCrashPessimisticReplTest): expected key 'k' to be locked on cache Cache '___defaultcache'@InitiatorCrashPessimisticReplTest-NodeD-44283, but it is not -- 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, 8 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