[
https://issues.jboss.org/browse/ISPN-1239?page=com.atlassian.jira.plugin....
]
Dan Berindei updated ISPN-1239:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request:
https://github.com/infinispan/infinispan/pull/456
Apply workaround in the test suite: stop all the caches before stopping the cache
managers.
Related fixes:
* Allow unregistering the cache instance from JMX when the cache is stopped.
* Don't log a huge stacktrace in RehashTask and in CommandAwareRpcDispatcher when the
cache is shutting down.
* Don't log "Ignoring call to stop" during normal shutdown.
* Don't clear the data container before stopping a cache - that cache might be
participating in an ongoing rehash.
Fixed the ConcurrentOverlappingLeaveTest issues in the previous comment.
Graceful shutdown should be supported
-------------------------------------
Key: ISPN-1239
URL:
https://issues.jboss.org/browse/ISPN-1239
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache
Affects Versions: 5.0.0.FINAL
Reporter: Manik Surtani
Assignee: Dan Berindei
Priority: Critical
Labels: clean_shutdown, rehashing
Fix For: 5.1.0.BETA1, 5.1.0.FINAL
Currently, killing any node will result in a rehash. A mechanism for clean shutdown
should also be supported, so that a rehash is *not* triggered. Useful when the entire
cluster is being intentionally brought down.
Need to think about how we do this; perhaps a LEAVE message that will prevent nodes
triggering a rehash when a subsequent view change is detected. This could be done
programmatically via a {{clean}} parameter to {{stop()}}, but we should explore
alternatives here.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira