infinispan-issues November 2010

infinispan-issues@lists.jboss.org

1 participants
214 discussions

[JBoss JIRA] Created: (ISPN-754) Build object names that follow best practices that are clearer and avoid confusion

by Galder Zamarreño (JIRA)

Build object names that follow best practices that are clearer and avoid confusion ---------------------------------------------------------------------------------- Key: ISPN-754 URL: https://jira.jboss.org/browse/ISPN-754 Project: Infinispan Issue Type: Task Components: JMX, reporting and management Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.BETA1, 5.0.0.Final CacheManager JMX object names need revisiting to better follow best practices (http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/bes...) and enable easier identification in multi CacheManager environments. At the moment, cache managers follow this pattern: *:cache-name="[global]",jmx-resource=CacheManager and in app server environments, we can find these names deployed: [infinispan4:cache-name="[global]",jmx-resource=CacheManager, infinispan3:cache-name="[global]",jmx-resource=CacheManager, infinispan:cache-name="[global]",jmx-resource=CacheManager, infinispan2:cache-name="[global]",jmx-resource=CacheManager] Suggestions: 1. As per best practices, the ON should start with the java package name, so preferably the default domain name should be: org.infinispan. 2. Every ON should contain a type=key for each object type. In Infinispan, we differentiate between CacheManager and Cache, so accordingly, we should have: type=CacheManager and type=Cache 3. A name property should be available to differentiate each ON of a particular type. cache-name is not good for this cos it's only meaningful at the cache level and can confuse people searching for CacheManager instances. I think it's good that we keep a jmxDomain optionally configurable, but we should add name to globalJmxStatistics configuration to define the cache manager name and to avoid confusion with domain redefinition. The end result for a CacheManager object name would be: org.infinispan:type=CacheManager,name="Hibernate2LC" org.infinispan:type=CacheManager,name="HttpSession" org.infinispan:type=CacheManager,name="Ejb3SfsbState" ...etc At the cache level, currently JMX names would look like: infinispan:cache-name="MyCache(local)",jmx-resource=Cache This should be transformed into something along the lines of: org.infinispan:type=Cache,mode=local,name="MyCache" -- 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

1
9
0 / 0

[JBoss JIRA] Resolved: (ISPN-180) Colocated nodes should be handled in DIST

by Mircea Markus (JIRA)

[ https://jira.jboss.org/browse/ISPN-180?page=com.atlassian.jira.plugin.sys... ] Mircea Markus resolved ISPN-180. -------------------------------- Resolution: Done > Colocated nodes should be handled in DIST > ----------------------------------------- > > Key: ISPN-180 > URL: https://jira.jboss.org/browse/ISPN-180 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Manik Surtani > Assignee: Mircea Markus > Priority: Blocker > Fix For: 4.2.0.BETA1, 4.2.0.Final > > > DefaultConsistentHash should place addresses on the hash wheel such that colocated nodes are never less than repl_count nodes apart to prevent data loss when a server fails. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-757) Cassandra cachestore should qualify keys with cache name

by Tristan Tarrant (JIRA)

Cassandra cachestore should qualify keys with cache name -------------------------------------------------------- Key: ISPN-757 URL: https://jira.jboss.org/browse/ISPN-757 Project: Infinispan Issue Type: Task Components: Loaders and Stores Affects Versions: 4.2.0.ALPHA5 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Minor Implement the ability to share a single keyspace for multiple caches by encoding the name of the cache within the key. Should be optional and set via a boolean flag (sharedKeyspace) in the config. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-758) Cassandra cachestore should allow choosing consistency for reads and writes

by Tristan Tarrant (JIRA)

Cassandra cachestore should allow choosing consistency for reads and writes --------------------------------------------------------------------------- Key: ISPN-758 URL: https://jira.jboss.org/browse/ISPN-758 Project: Infinispan Issue Type: Task Components: Loaders and Stores Affects Versions: 4.2.0.ALPHA5 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Currently the Cassandra cachestore uses Consistency ONE for reads / writes. The consistency level should be set via configuration and separated between the two types. -- 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

1
1
0 / 0

← Newer
1
...
19
20
21
22
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2010