cancel
Showing results for 
Search instead for 
Did you mean: 

Auto-Failover Not Happening (EFM-3.4)

Adventurer

Re: Auto-Failover Not Happening (EFM-3.4)

My hunch is that the problem was in the JGroups. I made sure to kill all EFM processes when they weren't cleanly killed. I didn't do anything with JGroups, however.

How can I check if JGroups are still OK?

Adventurer

Re: Auto-Failover Not Happening (EFM-3.4)


@slonkar wrote:

Hi @wcruz,

 

Agreed and glad to hear that the issue solved. From the logs, it looks like the communication was not happening between the nodes that could have been resolved after the reboot.

 

Regards,

Sudhir


Hi, Sudhir,

If communication was not happening, how come "efm cluster-status efm" always gave out the correct values?

Do you mean communication JGroups-wise?

 

Adventurer

Re: Auto-Failover Not Happening (EFM-3.4)

By the way, the OS on the DB nodes is RHEL 7 and on the Witness node is Centos 7.

EDB Team Member

Re: Auto-Failover Not Happening (EFM-3.4)

Hi @wcruz,

 

We recommend having all the servers on the same distribution of Linux.

 

To get a clearer picture of the possible root cause of the issue, could you please share the efm.properties files from all nodes and DB logs of the Master and Standby at the time you were performing the test.

 

Regards,

Sudhir

 

Adventurer

Re: Auto-Failover Not Happening (EFM-3.4)

EDB Team Member

Re: Auto-Failover Not Happening (EFM-3.4)

Hi wcruz,

 

To avoid delay in responses and to get a proper RCA for your issue, you can raise a case to "support@enterprisedb.com" with the subscribed user.