[JBoss JIRA] (ISPN-3530) The HotRod client should support a separate CH for each cache
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-3530?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-3530:
-------------------------------
Fix Version/s: 7.0.0.Alpha2
(was: 7.0.0.Alpha1)
> The HotRod client should support a separate CH for each cache
> -------------------------------------------------------------
>
> Key: ISPN-3530
> URL: https://issues.jboss.org/browse/ISPN-3530
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Protocols
> Affects Versions: 6.0.0.Alpha4
> Reporter: Dan Berindei
> Assignee: Galder Zamarreño
> Labels: hotrod, hotrod-java-client
> Fix For: 7.0.0.Alpha2
>
>
> With asymmetric clusters, each cache can have its own consistent hash, so the primary owner of a key in one cache is not necessarily the owner in all the caches. Even with a symmetric cluster, the same client may be used to access both distributed and replicated caches, and those would certainly have a different CH.
> In order to send the operations to the correct owner, the HotRod client should use a different CH for each cache.
--
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
10 years, 2 months
[JBoss JIRA] (ISPN-3529) Add support for the segment-based CH in the HotRod protocol
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-3529?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-3529:
-------------------------------
Fix Version/s: 7.0.0.Alpha2
(was: 7.0.0.Alpha1)
> Add support for the segment-based CH in the HotRod protocol
> -----------------------------------------------------------
>
> Key: ISPN-3529
> URL: https://issues.jboss.org/browse/ISPN-3529
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Protocols
> Affects Versions: 6.0.0.Alpha4
> Reporter: Dan Berindei
> Assignee: Galder Zamarreño
> Labels: hotrod, hotrod-java-client
> Fix For: 7.0.0.Alpha2
>
>
> The server CH changed in version 5.2 from virtual-nodes-based to segment-based, but the client CH stayed the same. The server is able to translate the server CH into a client CH, but the translation is imperfect:
> 1. Sometimes the client CH computes a different primary owner than the server CH.
> 2. The client CH gets slower as the number of segments increases, the server CH performance stays the same.
--
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
10 years, 2 months
[JBoss JIRA] (ISPN-3621) Most CacheStore configuration examples in the documentation are wrong (outdated)
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-3621?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-3621:
-------------------------------
Fix Version/s: 7.0.0.Alpha2
(was: 7.0.0.Alpha1)
> 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
> Fix For: 7.0.0.Alpha2
>
>
> 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 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
10 years, 2 months