Thank you for the quick response. I have 2 follow up questions below: 1. I don't see the differences between wait-for-activation=true or false. Who activated it? Can I set the wait time to be activated in XML config? Is it intended for the primary server to delay the takeover of backup when the primary recovers from crash? 2. If I set " allow-failback" = false in backup server, the primary was announced as backup when it recovered from crash but I couldn't login to the primary UI console. Is it normal?
Thanks in advance. Regards, Rahman -----Original Message----- From: Justin Bertram <jbert...@apache.org> Sent: Thursday, February 17, 2022 4:34 PM To: users@activemq.apache.org Subject: [EXTERNAL] Re: Question on failback-delay for Artemis 2.19.1 shared store config Although you're using ActiveMQ Artemis 2.19.1 you're reading documentation from version 1.0.0. Notice the "1.0.0" in the URL. The "failback-delay" parameter was deprecated in version 1.2.0 released way back in January 2016, over 6 years ago now. It was deprecated via ARTEMIS-256 [2] which you can refer to for more details about why this change was made. Please refer to the documentation for the 2.19.x branch here [1]. Justin [1] https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcomponents%2Fartemis%2Fdocumentation%2F2.19.0%2F&data=04%7C01%7Crahman.gunawan%40nasa.gov%7C3196976e061d41e24fd008d9f25d5a3e%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637807306387628543%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=5BO%2FC1YT5Bx%2FAuZpxgu2EnFVY53RhX8NtbQZT4tnuR0%3D&reserved=0 [2] https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FARTEMIS-256&data=04%7C01%7Crahman.gunawan%40nasa.gov%7C3196976e061d41e24fd008d9f25d5a3e%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637807306387628543%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=S78sRSHg89vlEXdUIcRCgt4f97necrhVesfph9tnK%2Fo%3D&reserved=0 On Thu, Feb 17, 2022 at 2:36 PM Gunawan, Rahman (GSFC-703.H)[BUSINESS INTEGRA, INC.] <rahman.guna...@nasa.gov.invalid> wrote: > I'm trying share store configuration based on this doc > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcomponents%2Fartemis%2Fdocumentation%2F1.0.0%2Fha.html&data=04%7C01%7Crahman.gunawan%40nasa.gov%7C3196976e061d41e24fd008d9f25d5a3e%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637807306387628543%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ygKMj0stEYe1omIrzAGoqBOyqs30Rlt4TUfNt%2B9QPX8%3D&reserved=0. > Failback-delay is configured to be 300000 (300 seconds) hoping that > when primary goes down, the backup takes over and when the primary is > back alive, it waits for 300 seconds before the primary takes over. > However; the primary took over immediately when I started it. Was the config > wrong? > Is there a way to let the backup server as live server when primary > goes down and stay that way although the primary recovers from crash > (primary will be announced as backup)? > > Below is the configuration for primary and secondary: > The primary is configured below: > <ha-policy> > <shared-store> > <master> > <failover-on-shutdown>true</failover-on-shutdown> > <failback-delay>300000</failback-delay> > </master> > </shared-store> > </ha-policy> > > The backup is configured: > <ha-policy> > <shared-store> > <slave> > <failover-on-shutdown>true</failover-on-shutdown> > <allow-failback>true</allow-failback> > <failback-delay>300000</failback-delay> > </slave> > </shared-store> > </ha-policy> > > Thanks > > Regards, > Rahman > >
