[
https://issues.jboss.org/browse/ISPN-1147?page=com.atlassian.jira.plugin....
]
Prashanth ga commented on ISPN-1147:
------------------------------------
Yes,agree with that. It would be appropriate if Infinispan takes care of reflecting the
config changes also throughout the cluster along with data. We would be eagerly waiting
for that fix, please keep us updated.
Till then, we are planning to update the configurations simultaneaoulsy on all the nodes.
The reads/writes to these regions won't happen till then.
Also, I assume that runtime config changes are not just creating a new named cache but
also changing the attributes of the named cache (those which are allowed).
Programmatically creating cache should be automatically reflected
throughout the cluster
----------------------------------------------------------------------------------------
Key: ISPN-1147
URL:
https://issues.jboss.org/browse/ISPN-1147
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache, State transfer
Affects Versions: 4.2.1.FINAL
Reporter: Randall Hauch
Assignee: Manik Surtani
Fix For: 6.0.0.Final
Consider a symmetric cluster of two nodes (N1 and N2) each with a single cache (C1).
Currently, a new cache (C2) must be programmatically created _on all all nodes in the
cluster_ (if REPL, or all appropriate nodes if DIST) _before_ that new cache can even be
_used_.
Ideally, when a new cache (C2) is created on one node (N1), Infinispan should
automatically propagate that creation to the appropriate nodes in the cluster so that the
new cache can be used immediately.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira