[jboss-jira] [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3488 at 3/5/12 8:56 PM:
------------------------------------------------------------------
Note to myself:
Changing the default cache value should require some degree of restart: if we are in a
cluster with several cache-using app instances using the default cache, we change the
default cache and then a new member joins with no intervening restart, the caches used
will become out of sync.
Given the options for restarts (no-services, all-services, jvm, resource-services), rather
than restart all services in the system, we need only restart the services associated with
that cache container (i.e. restart-required => resource-services):
EmbeddedCacheManagerConfigurationService, DefaultEmbeddedCacheManagerService. This entails
shutting them down and then starting with the revised configuration.
The DEFAULT_CACHE attribute access flags are currently set to RESTART_ALL_SERVICES,
meaning that we need to perform a /:reload operation, but not a full JVM restart.
was (Author: rachmato):
Note to myself:
Changing the default cache value should require some degree of restart: if we are in a
cluster with several cache-using app instances using the default cache, we change the
default cache and then a new member joins with no intervening restart, the caches used
will become out of sync.
Given the options for restarts (no-services, all-services, jvm, resource-services), rather
than restart all services in the system, we need only restart the services associated with
that cache container (i.e. restart-required => resource-services):
EmbeddedCacheManagerConfigurationService, DefaultEmbeddedCacheManagerService. This entails
shutting them down and then starting with the revised configuration.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira