[
https://issues.jboss.org/browse/ISPN-4144?page=com.atlassian.jira.plugin....
]
Radim Vansa commented on ISPN-4144:
-----------------------------------
1) I wouldn't call clear, this operation has to lock all entries and this would most
certainly cause slow down
2) Clear wouldn't get rid of the logs: if one node is not shut down yet and the others
already are (and the rebalance is triggered), this node becomes owner of some new
*segments*. Then it finds that there is no live owner of these segments and logs the
warning. See, it's all about segment ownership, not entries.
I am not sure whether the ability to disable rebalance is currently implemented cache-wise
or globally - if the latter is the case, we should probably consider more fine-grained
operation.
Cleanly shutdown intermediate M/R cache
---------------------------------------
Key: ISPN-4144
URL:
https://issues.jboss.org/browse/ISPN-4144
Project: Infinispan
Issue Type: Feature Request
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
For intermediate per task caches we simply remove that cache from cache manager. This
operation is cluster wide but it still triggers rebalancing which in turn possibly creates
logs that might raise false alarms for admins. Investigate if calling clear before
removing cache from cache manager and/or disabling rebalancing for intermediate cache
leads to a "cleaner" cache shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira