August 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2973) HotRod client doesn't retry on suspect

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2973?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2973: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > HotRod client doesn't retry on suspect > -------------------------------------- > > Key: ISPN-2973 > URL: https://issues.jboss.org/browse/ISPN-2973 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.2.2.Final > Reporter: Takayoshi Kimura > Assignee: Tristan Tarrant > Fix For: 5.2.6.Final, 6.0.0.Alpha3 > > > HotRod client does retry on RemoteNodeSuspectException and Codec10#checkForErrorsInResponseStatus() checks message from server if it contains "Suspect" message. > ISPN-2737 fix changed the message and HotRod is unable to perform retry as there is no "Suspect" string in the message from server. > ISPN-2737 PullReq: https://github.com/infinispan/infinispan/pull/1629 and commit https://github.com/galderz/infinispan/commit/3ee1b96ace284ba108eb3abfd855... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3173) Define a new query operation over hotrod

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3173?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3173: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Define a new query operation over hotrod > ---------------------------------------- > > Key: ISPN-3173 > URL: https://issues.jboss.org/browse/ISPN-3173 > Project: Infinispan > Issue Type: Sub-task > Reporter: Mircea Markus > Assignee: Galder Zamarreño > Priority: Blocker > Fix For: 6.0.0.Alpha3, 6.0.0.Final > > > Add a new query predicated to the [Hot Rod Protocol | https://docs.jboss.org/author/display/ISPN/Hot+Rod+Protocol+-+Version+1.2] and implement server side support for it. > For now this operation should send an byte[] (the query encoded) over the network and receive an byte[] as response. The query and the result might get further specified in the future. > This will be used by ISPN-3175 to implement the initial remote querying functionality the java hotrod client. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3147) Fix test ReplCommandForwardingTest.testForwardToJoinerNonTransactional

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3147?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3147: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Fix test ReplCommandForwardingTest.testForwardToJoinerNonTransactional > ---------------------------------------------------------------------- > > Key: ISPN-3147 > URL: https://issues.jboss.org/browse/ISPN-3147 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 5.3.0.CR1 > Reporter: Adrian Nistor > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 6.0.0.Alpha3, 6.0.0.Final > > > This test is broken by ISPN-2772. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3159) Implementing SERIALIZABLE isolation level based on GMU

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3159?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3159: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Implementing SERIALIZABLE isolation level based on GMU > ------------------------------------------------------ > > Key: ISPN-3159 > URL: https://issues.jboss.org/browse/ISPN-3159 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 6.0.0.Alpha3, 6.0.0.Final > > > Implementation based in GMU, a Cloud-TM project research (www.cloudtm.eu). > GMU is a muti-version scheme that provides Update Serializability. It allows the read-only transaction to proceed without blocking, but they can observe an old value (but always a consistent value). > This scheme relies in Vector Clock to manage the snapshots to read and the transaction dependencies in each node in the cluster. > Also, it is a genuine scheme, i.e., only the nodes involved in the transaction (that contains data read or write) are involved in the transaction commit. > A paper describing GMU can be found here: http://ieeexplore.ieee.org/xpl/articleDetails.jsp?reload=true&arnumber=62... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3051) Allow configuring the number of segments per node

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3051?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3051: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Allow configuring the number of segments per node > ------------------------------------------------- > > Key: ISPN-3051 > URL: https://issues.jboss.org/browse/ISPN-3051 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Guillermo GARCIA OCHOA > Assignee: Dan Berindei > Priority: Critical > Fix For: 6.0.0.Alpha3, 6.0.0.Final > > > This should allow for the following use cases: > - a node to take more load > - a node to take no load > A simple way for specifying this would be to configure a load factor per node, e.g. more powerful machine would be 2*x and that would mean that it would take twice the load of an "ordinary" machine in the cluster. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3301) Tests create files where they shouldn't

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3301?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3301: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Tests create files where they shouldn't > --------------------------------------- > > Key: ISPN-3301 > URL: https://issues.jboss.org/browse/ISPN-3301 > Project: Infinispan > Issue Type: Bug > Components: Build process > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha3 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3290) Redesign CacheStore API

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3290?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3290: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Redesign CacheStore API > ----------------------- > > Key: ISPN-3290 > URL: https://issues.jboss.org/browse/ISPN-3290 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Critical > Fix For: 6.0.0.Alpha3, 6.0.0.Final > > > the cache store API should be redesigned in the scope of 6.0. See all the related JIRAs for requirements. > Also a discussion has been started here: https://community.jboss.org/wiki/CacheLoaderAndCacheStoreSPIRedesign -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3200) Allow KeyFilters to be applied to listeners

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3200?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3200: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Allow KeyFilters to be applied to listeners > ------------------------------------------- > > Key: ISPN-3200 > URL: https://issues.jboss.org/browse/ISPN-3200 > Project: Infinispan > Issue Type: Feature Request > Components: Listeners > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Assignee: Mircea Markus > Labels: leads > Fix For: 6.0.0.Alpha3, 6.0.0.Final > > > When registering a listener, users should be able to provide a {{KeyFilter}}, a simple interface that determines whether a listener is invoked or not based on whether the affected key(s) matches the filter. > The proposed API may overload the {{addListener(Object listener)}} method on {{Cache}}, adding: > {code} > void addListener(Object listener, KeyFilter filter); > {code} > where {{KeyFilter}} may be an interface that looks like: > {code} > public interface KeyFilter { > boolean match(Object key); > } > {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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3261) Extract clustering functionality from core to infinispan-clustering

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3261?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3261: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Extract clustering functionality from core to infinispan-clustering > ------------------------------------------------------------------- > > Key: ISPN-3261 > URL: https://issues.jboss.org/browse/ISPN-3261 > Project: Infinispan > Issue Type: Sub-task > Components: Build process, Core API > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha3 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3263) LevelDB cachestore doesn't have a 5.3 parser + XSD

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3263?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3263: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > LevelDB cachestore doesn't have a 5.3 parser + XSD > -------------------------------------------------- > > Key: ISPN-3263 > URL: https://issues.jboss.org/browse/ISPN-3263 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha3, 6.0.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

12 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2013