On Oct 4, 2012, at 2:58 PM, Mircea Markus <mircea.markus(a)jboss.com> wrote:
Hi,
Re:
https://issues.jboss.org/browse/ISPN-2320
Here is a list of admin operations I'd like to implement for ISPN-2320:
- status: shows a map with all defined sites and their status: available xor offline
- takeOffline: takes a site offline, i.e. backup to that site is ignored
- takeOnline: the reverse to takeOffline
- amendTakeOffline (int:afterFailures, long:minTimeToWait): changes the takeOffline
functionality[1]
- statistics: numberOfBackupCalls, successfullBackupCalls, failedBackupCalls
Each of the operations that modify configs would be available on a per node or on a per
cluster basis (a flag to the operation would differentiated between the two).
^ I guess not, but just wondering if those modifications would be persisted in the XML
config if there's any? That needs to be clearly defined.
I understand afterFailure, but I don't understand minTimeToWait. What is minTimeToWait
really used for? " the minimal number of millis to wait…" - wait for what?
And is it its use mutually exclusive from afterFailure? IOW, does it make sense to
configure both at the same time? Or if you configure one, the other is not used, and
viceversa? Judging from the comments it sounds they're mutually exclusive, in which
case adding both as XML properties of the same XML element doesn't sound like a good
idea.
Cheers,
Cheers,
--
Mircea Markus
Infinispan lead (
www.infinispan.org)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
galder(a)redhat.com
twitter.com/galderz
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org