-
15. Re: strange failover behaviour in clustered config
"timfox" wrote:
"clebert.suconic@jboss.com" wrote:
Just an idea: It would be possible to expose a method to mergeQueus from a dead node like they're describing, so a Human knowing the server will never come back could start the merge procedure. But I feel like this is way too dangerous and error prone!
You woulldn't need to do that if you just started a new server with the same id on a different node - why is this such an issue?
I said it would be possible.. but that's a bad idea... so I would stick with with start another node with the same ID (as I also said early on this thread). -
16. Re: strange failover behaviour in clustered config
I fully agree workaround you provide will work but with 1 constraint: you should have direct access to the machine to do that. With all security in production it not always possible. So it would be very nice if there is possibility to do merge manually. If it a call of function via jmx-console it's perfect.
Thanks anyway for such fast response and explanation. -
17. Re: strange failover behaviour in clustered config
After power failure I would suspect a sysadmin would access the machines anyway to start everything up?
If you want, you can add a JIRA feature request for the manual merge queue feature via JMX. -
18. Re: strange failover behaviour in clustered config
I would create jira task. Sysadmin are not always smart enougth to deal with difficult situation such as queue recovery :) They know how to stop/start backup/upgrade. It's looks something more for DBA but even so.
Thanks again. Jira task will follow