October 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-352) Add per-cache coordinator.

by Alexander Gavrilov (JIRA)

Add per-cache coordinator. -------------------------- Key: ISPN-352 URL: https://jira.jboss.org/jira/browse/ISPN-352 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: Alexander Gavrilov Assignee: Manik Surtani We trying to use Infinispan for our cluster. We have two types of nodes in cluster. "Type 1" nodes use all set of caches defined in system, but "Type 2" nodes uses only small subset of nodes. For each cache on each node we have job, that fetch data from external store and put that data in the cache. We need this job to be executed only in one node from whole cluster and is natural to test if node is cache coordinator and execute job only if it is. In current implementation it's possible to determinate only cluster coordinator. But when node of "Type 2" becomes coordinator it is impossible to update some caches, because they are not defined in this node. It would be fine to declare not only oldest node in cluster as cluster coordinator but oldest node containing cache as this concrete cache coordinator. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-723) slow puts on async JdbmCacheStore

by Michael Brackx (JIRA)

slow puts on async JdbmCacheStore --------------------------------- Key: ISPN-723 URL: https://jira.jboss.org/browse/ISPN-723 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.1.0.Final Reporter: Michael Brackx Assignee: Manik Surtani Puts on a cache with an async JdbmCacheStore are much slower than on a cache with an async FileCacheStore. If the cache store does not yet exists, it is as fast as a FileCacheStore. If it already exists, it is about 10 times slower. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-651) Document Infinispan tree module

by Galder Zamarreño (JIRA)

Document Infinispan tree module ------------------------------- Key: ISPN-651 URL: https://jira.jboss.org/browse/ISPN-651 Project: Infinispan Issue Type: Task Components: Tree API Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.Final See dev list thread. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (ISPN-751) Infinispan release reporting itself as a SNAPSHOT in logs

by Paul Ferraro (JIRA)

Infinispan release reporting itself as a SNAPSHOT in logs --------------------------------------------------------- Key: ISPN-751 URL: https://jira.jboss.org/browse/ISPN-751 Project: Infinispan Issue Type: Bug Affects Versions: 4.2.0.ALPHA5 Reporter: Paul Ferraro Assignee: Manik Surtani Priority: Minor Using infinispan-core-4.2.0.ALPHA5, I see the following in the logs: 2010-10-29 12:20:39,557 INFO [org.infinispan.factories.GlobalComponentRegistry] (RMI TCP Connection(6)-127.0.0.1) Infinispan version: Infinispan 'Ursus' 4.2.0.SNAPSHOT It seems the release was built prior to tagging/labelling? While this is trivial - it is definitely something you'll want to fix before the final release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
9
0 / 0

[JBoss JIRA] Created: (ISPN-744) A cloned configuration object should not inherit component status from parent object

by Paul Ferraro (JIRA)

A cloned configuration object should not inherit component status from parent object ------------------------------------------------------------------------------------ Key: ISPN-744 URL: https://jira.jboss.org/browse/ISPN-744 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 4.2.0.ALPHA4 Reporter: Paul Ferraro Priority: Minor If I clone the GlobalConfiguration from a running cache manager and attempt setTransportProperties(...) on the cloned object, I get a ConfigurationException indicating that I cannot modify a non-dynamic configuration element of a started component. I would expect that a cloned config would be disconnected and would not inherit the component status of its parent object. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-739) Change default Hot Rod port to 11222

by Galder Zamarreño (JIRA)

Change default Hot Rod port to 11222 ------------------------------------ Key: ISPN-739 URL: https://jira.jboss.org/browse/ISPN-739 Project: Infinispan Issue Type: Task Components: Cache Server Affects Versions: 4.2.0.ALPHA4, 4.1.0.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.BETA1, 4.2.0.Final This is essentially to avoid issues with different port configurations in AS, where the offset between diff ports is 100. Make sure wikis and documentation are updated accordingly. galderz: hi manik [1:31pm] manik: galderz: yo [1:31pm] manik: whassup? [1:31pm] galderz: hey, i've just spotted one thing [1:31pm] galderz: we've defined memcached and hot rod default ports as: 11211 and 11311 [1:31pm] manik: yes [1:32pm] galderz: now, AS uses an offset to define ports for different port settings: ports-default, port-01...etc [1:32pm] galderz: and the offset is 100 [1:32pm] galderz: so, it means that when you use ports-01, your ports are: 11311 and 11411 [1:32pm] galderz: that could confuse things up cos you old default hot rod protocol would now be a memcached port [1:33pm] manik: Yep. [1:33pm] galderz: i was wondering whether we should do something to avoid this [1:33pm] manik: What do you reckon? Configure Hot Rod to listen on 11221 ? [1:33pm] galderz: it could lead to issues [1:34pm] manik: 11222 ? [1:34pm] galderz: yeah, one of those [1:34pm] galderz: we don't wanna change the default memcached port -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (ISPN-675) Make Infinispan JOPR plugin friendly with AS environments

by Galder Zamarreño (JIRA)

Make Infinispan JOPR plugin friendly with AS environments --------------------------------------------------------- Key: ISPN-675 URL: https://jira.jboss.org/browse/ISPN-675 Project: Infinispan Issue Type: Feature Request Components: JMX, reporting and management Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.CR1 Within the descriptor: - Change top level from server to service - Within the service add: <parent-resource-type name="JMX Server" plugin="JMX"/> <parent-resource-type name="JBossAS Server" plugin="JBossAS"/> <parent-resource-type name="JBossAS Server" plugin="JBossAS5"/> Within source: - From "implements ResourceComponent" should convert into "extend MBeanResourceComponent" (like StatisticsComponent) - You might be able to reduce the code with the above change Base your work on what has been done in: https://svn.jboss.org/repos/jopr/trunk/modules/plugins/hibernate Test: - Test with AS6 admin console (drop the plugin jar into the plugins subdirectory in the admin console) - Test with RHQ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
13
0 / 0

[JBoss JIRA] Created: (ISPN-746) In Memcached, implement 250 character key check

by Galder Zamarreño (JIRA)

In Memcached, implement 250 character key check ----------------------------------------------- Key: ISPN-746 URL: https://jira.jboss.org/browse/ISPN-746 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.2.0.ALPHA4, 4.1.0.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.BETA1, 4.2.0.Final Memcached protocol has a limit of 250 characters in the size of keys. We should implement this check as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (ISPN-728) Make NamespaceFilter.ISPN_NS not rely on hardcoded version

by Galder Zamarreño (JIRA)

Make NamespaceFilter.ISPN_NS not rely on hardcoded version ---------------------------------------------------------- Key: ISPN-728 URL: https://jira.jboss.org/browse/ISPN-728 Project: Infinispan Issue Type: Task Affects Versions: 4.2.0.ALPHA4 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.BETA1 >From Vladimir: "I coded this part and I thought it was an accident waiting to happen. However, I could not use expression "urn:infinispan:config:" + Version.getMajorVersion() because compiler forces us to use constant expressions [1] here. If you agree we can add another public static field in Version.java: public static final String MAJOR_VERSION = "4.2"; Maybe we have similar use cases somewhere else as well! [1] http://java.sun.com/docs/books/jls/third_edition/html/expressions.html#15.28" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-682) return value of Remove command is unreliable in DIST without L1

by Sanne Grinovero (JIRA)

return value of Remove command is unreliable in DIST without L1 --------------------------------------------------------------- Key: ISPN-682 URL: https://jira.jboss.org/browse/ISPN-682 Project: Infinispan Issue Type: Bug Components: Core API, Distributed Cache Affects Versions: 4.2.0.ALPHA2 Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 4.2.0.BETA1 cache.remove(key) returns null in DIST mode when L1 is disabled (unreliableReturnValues was not enabled) providing a unit test highlighting the difference between L1 on/off -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2010