[jboss-jira] [JBoss JIRA] (AS7-6460) Attribute check-for-live-server must set on live server to faillback
Miroslav Novak (JIRA)
jira-events at lists.jboss.org
Fri Feb 8 08:19:51 EST 2013
[ https://issues.jboss.org/browse/AS7-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753006#comment-12753006 ]
Miroslav Novak commented on AS7-6460:
-------------------------------------
There is one more thing we could mention. I'm not sure if it's really problem now. Imagine this scenario:
1. There is live/backup pair in dedicated topology with replicated journal
2. Live is killed and backup takes its role (so everything failover to backup)
3. Now for whatever reason backup is shutdowned/killed too
4. Administrator comes and start live server first. Then he starts backup server.
Live is not up-to-date and also backup will corrupt its journal when it synchronizes with "old" live.
I guess we could add warning to doc not to do this if this is really an issue.
> Attribute check-for-live-server must set on live server to faillback
> --------------------------------------------------------------------
>
> Key: AS7-6460
> URL: https://issues.jboss.org/browse/AS7-6460
> Project: Application Server 7
> Issue Type: Task
> Components: JMS
> Affects Versions: 7.2.0.Alpha1
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Fix For: 7.2.0.CR1
>
> Attachments: standalone-full-ha-backup.xml, standalone-full-ha-live.xml
>
>
> When there is live/backup pair with replicated journal then it should be sufficient to set attribute "check-for-live-server" in messaging subsystem only on backup to force backup server to shutdown when live server comes alive again. Problem is this won't happen.
> Only when attribute "check-for-live-server" is set on live server then failback is successful (backup shutdown itself)
> It's not well documented where "check-for-live-server" should be set in HornetQ project documentation:
> http://docs.jboss.org/hornetq/2.3.0.CR1/docs/user-manual/html_single/index.html#ha.allow-fail-back
> This issue was hit with EAP 6.1.0.DR2 (HQ 2.3.0.CR1).
--
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
More information about the jboss-jira
mailing list