January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3351) Controlled cluster shutdown with data restore from persistent storage

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3351?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3351: ---------------------------------- Fix Version/s: (was: 7.1.0.CR1) > Controlled cluster shutdown with data restore from persistent storage > --------------------------------------------------------------------- > > Key: ISPN-3351 > URL: https://issues.jboss.org/browse/ISPN-3351 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Loaders and Stores > Reporter: Mircea Markus > Labels: roadmap > > https://community.jboss.org/wiki/ControlledClusterShutdownWithDataRestore... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5134) Cluster Cache Loader returns null as a valid value

by Ilya Kikoin (JIRA)

[ https://issues.jboss.org/browse/ISPN-5134?page=com.atlassian.jira.plugin.... ] Ilya Kikoin commented on ISPN-5134: ----------------------------------- Are there any possible workarounds for this issue? > Cluster Cache Loader returns null as a valid value > -------------------------------------------------- > > Key: ISPN-5134 > URL: https://issues.jboss.org/browse/ISPN-5134 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 7.0.3.Final > Reporter: William Burns > > Found this at http://stackoverflow.com/questions/27840070/infinispan-cluster-in-invalid... > I tweaked the ClusterCacheLoaderTest to have a 3rd cache manager and I can see intermittent failures in either test due to using a null value from a different node. > Unfortunately this isn't as simple as tweaking ClusteredGetResponseValidityFilter to only say a valid response on a non null, since JGroups will throw an exception when there are no responses. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3602) Cache statistics update differently in library and Client-Server mode

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3602?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-3602: --------------------------------------- Looking at the code, this now seems fixed as a side-effect of ISPN-3234 > Cache statistics update differently in library and Client-Server mode > --------------------------------------------------------------------- > > Key: ISPN-3602 > URL: https://issues.jboss.org/browse/ISPN-3602 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.CR1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Priority: Minor > Labels: dm > Fix For: 7.0.0.Final > > > When running jdg quickstart carmart ( https://github.com/infinispan/jdg-quickstart/tree/master/carmart ) I noticed interesting thing. > When calling replace() in library mode, the number of stores in cache statistics doesn't change whereas when calling in Client-Server mode, the number of stores increase by 1. > I went deeper into the code and I found out that in CacheMgmtInterceptor, where there are implemented methods for such statistics updates (like for put() ), there isn't implemented method for updating stats for replace() method, so the control flow is just passed. > I think it should be consistent, but I don't know which approach is intended, if either increase by 1 or leave it the same. > If increase is the answer than the solution is simple, implement CacheMgmtInterceptor.visitReplaceCommand(...) the same way as e.g. visitPutKeyValueCommand. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3602) Cache statistics update differently in library and Client-Server mode

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3602?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-3602. ----------------------------------- Fix Version/s: 7.0.0.Final (was: 7.1.0.CR1) Resolution: Done > Cache statistics update differently in library and Client-Server mode > --------------------------------------------------------------------- > > Key: ISPN-3602 > URL: https://issues.jboss.org/browse/ISPN-3602 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.CR1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Priority: Minor > Labels: dm > Fix For: 7.0.0.Final > > > When running jdg quickstart carmart ( https://github.com/infinispan/jdg-quickstart/tree/master/carmart ) I noticed interesting thing. > When calling replace() in library mode, the number of stores in cache statistics doesn't change whereas when calling in Client-Server mode, the number of stores increase by 1. > I went deeper into the code and I found out that in CacheMgmtInterceptor, where there are implemented methods for such statistics updates (like for put() ), there isn't implemented method for updating stats for replace() method, so the control flow is just passed. > I think it should be consistent, but I don't know which approach is intended, if either increase by 1 or leave it the same. > If increase is the answer than the solution is simple, implement CacheMgmtInterceptor.visitReplaceCommand(...) the same way as e.g. visitPutKeyValueCommand. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5141) SingleFileStore.process() should use sequential access

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5141: ---------------------------------- Summary: SingleFileStore.process() should use sequential access Key: ISPN-5141 URL: https://issues.jboss.org/browse/ISPN-5141 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 7.0.3.Final, 7.1.0.Beta1 Reporter: Dan Berindei {{SingleFileStore.process()}} iterates over its keys in pseudo-random order. (It puts all the entries in a {{HashSet}} and iterates it to minimize the amount of time it keeps the global lock.) It should instead either iterate the entries directly from the disk, or at least sort the entries by their offset when iterating. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3614) Add remote query quick start/demo

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3614?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3614: ---------------------------------- Fix Version/s: 7.0.0.Final (was: 7.1.0.CR1) > Add remote query quick start/demo > --------------------------------- > > Key: ISPN-3614 > URL: https://issues.jboss.org/browse/ISPN-3614 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 7.0.0.Final > > > Should describe how the users: > - download the servers > - configure it (indexing ...) > - with sample domain model, how to write the marshallers, define the indexes using the RHQ plugin > - some code that connects to the server, adds and queries the data (mvn module?) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3614) Add remote query quick start/demo

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3614?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-3614. ----------------------------------- Resolution: Done This was resolved by the introduction of the remote query quickstart > Add remote query quick start/demo > --------------------------------- > > Key: ISPN-3614 > URL: https://issues.jboss.org/browse/ISPN-3614 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 7.0.0.Final > > > Should describe how the users: > - download the servers > - configure it (indexing ...) > - with sample domain model, how to write the marshallers, define the indexes using the RHQ plugin > - some code that connects to the server, adds and queries the data (mvn module?) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3621) Most CacheStore configuration examples in the documentation are wrong (outdated)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3621?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-3621. ----------------------------------- Fix Version/s: 7.0.0.Final Resolution: Done > Most CacheStore configuration examples in the documentation are wrong (outdated) > -------------------------------------------------------------------------------- > > Key: ISPN-3621 > URL: https://issues.jboss.org/browse/ISPN-3621 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 6.0.0.CR1 > Reporter: Sanne Grinovero > Fix For: 7.0.0.Final > > > I've been trying half a dozen configuration snippets from the documentation, I couldn't get any CacheStore to work. All I get from the configuration parser is an unhelpfull stack trace: > {quote} > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[50,63] > Message: Unexpected element '{urn:infinispan:config:6.0}loaders' encountered > at org.infinispan.configuration.parsing.ParseUtils.unexpectedElement(ParseUtils.java:35) > at org.infinispan.configuration.parsing.Parser60.parseCache(Parser60.java:178) > at org.infinispan.configuration.parsing.Parser60.parseNamedCache(Parser60.java:109) > at org.infinispan.configuration.parsing.Parser60.readElement(Parser60.java:76) > at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:130) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:112) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:99) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:86) > ... 47 more > {quote} > One might think that something (what?) is wrong at [row,col]:[50,63] but I'm copy pasting the documentation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3621) Most CacheStore configuration examples in the documentation are wrong (outdated)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3621?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3621: ---------------------------------- Fix Version/s: (was: 7.1.0.CR1) > Most CacheStore configuration examples in the documentation are wrong (outdated) > -------------------------------------------------------------------------------- > > Key: ISPN-3621 > URL: https://issues.jboss.org/browse/ISPN-3621 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 6.0.0.CR1 > Reporter: Sanne Grinovero > Assignee: Mircea Markus > > I've been trying half a dozen configuration snippets from the documentation, I couldn't get any CacheStore to work. All I get from the configuration parser is an unhelpfull stack trace: > {quote} > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[50,63] > Message: Unexpected element '{urn:infinispan:config:6.0}loaders' encountered > at org.infinispan.configuration.parsing.ParseUtils.unexpectedElement(ParseUtils.java:35) > at org.infinispan.configuration.parsing.Parser60.parseCache(Parser60.java:178) > at org.infinispan.configuration.parsing.Parser60.parseNamedCache(Parser60.java:109) > at org.infinispan.configuration.parsing.Parser60.readElement(Parser60.java:76) > at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:130) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:112) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:99) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:86) > ... 47 more > {quote} > One might think that something (what?) is wrong at [row,col]:[50,63] but I'm copy pasting the documentation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3621) Most CacheStore configuration examples in the documentation are wrong (outdated)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3621?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3621: ------------------------------------- Assignee: (was: Mircea Markus) > Most CacheStore configuration examples in the documentation are wrong (outdated) > -------------------------------------------------------------------------------- > > Key: ISPN-3621 > URL: https://issues.jboss.org/browse/ISPN-3621 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 6.0.0.CR1 > Reporter: Sanne Grinovero > > I've been trying half a dozen configuration snippets from the documentation, I couldn't get any CacheStore to work. All I get from the configuration parser is an unhelpfull stack trace: > {quote} > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[50,63] > Message: Unexpected element '{urn:infinispan:config:6.0}loaders' encountered > at org.infinispan.configuration.parsing.ParseUtils.unexpectedElement(ParseUtils.java:35) > at org.infinispan.configuration.parsing.Parser60.parseCache(Parser60.java:178) > at org.infinispan.configuration.parsing.Parser60.parseNamedCache(Parser60.java:109) > at org.infinispan.configuration.parsing.Parser60.readElement(Parser60.java:76) > at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:130) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:112) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:99) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:86) > ... 47 more > {quote} > One might think that something (what?) is wrong at [row,col]:[50,63] but I'm copy pasting the documentation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2015