cancel
Showing results for 
Search instead for 
Did you mean: 

EDB-EFM-REPLICATIONS

Highlighted
Silver Adventurer

EDB-EFM-REPLICATIONS

Ho folks,

             I have a 4 servers,each node running in efm services,pem client and three is running database. also .

1.master

2.slave 1

3.slave 2

4.witness

Os team plan to apply patch.which one can i bring down first..

please share the details of which one i going to down first and which i going to start first after patch.please included the service and database also.

 

yours

Diny

Tags (1)
15 REPLIES 15
Highlighted
EDB Team Member

Re: EDB-EFM-REPLICATIONS

Hi  Din2pg,

 

EFM Service should have the sequence as 

1.Stop EFM Service on Witness

2.Stop EFM Service on Slave 2

3.Stop EFM Serivce on Slave 1

4.Stop EFM Serivce on Master.

 

1.Start EFM Service on Witness

2.Start EFM Service on Master

3.Start EFM Serivce on Slave 2

4.Start EFM Serivce on Slave1

 

Database cluster stop, start can be followed  with the above sequence.

 

 

Highlighted
EDB Team Member

Re: EDB-EFM-REPLICATIONS

Are you patching the database or efm?

 

If the database, I'd recommend:

1. Stop efm agent on one standby, patch/restart database, then start the efm agent.

2. Repeat for the other standby.

3. Perform a switchover.

4. Perform step #1 on the original master.

5. Run the 'efm set-priority' command to make the original master the highest priority and perform another switchover to go back to the original master.

 

If you're upgrading efm, just stop all the agents, e.g. 'efm stop-cluster.' Then upgrade them and start them again.

 

Cheers,

Bobby

 

Highlighted
EDB Team Member

Re: EDB-EFM-REPLICATIONS

 


@Rahul wrote:

Hi  Din2pg,

 

EFM Service should have the sequence as 

1.Stop EFM Service on Witness

2.Stop EFM Service on Slave 2

3.Stop EFM Serivce on Slave 1

4.Stop EFM Serivce on Master.

If you're going to stop all of them, you might as well use the 'efm stop-cluster' command. This is especially useful with older versions of efm so that the <clustername>.nodes file doesn't change on each node.

 

It also doesn't matter what order you start the agents. Though if you shut them down like above then the <clustername>.nodes file on the master won't have any addresses in it, so you might as well start that one first because it's easiest.

 

Bobby

 

Highlighted
Silver Adventurer

Re: EDB-EFM-REPLICATIONS

Hi @bbissett 

            Thanks for you promt action..but i want to clarify some thing.

see..

1.Now iam going to patch standby 1---------->can i change any parameter in master(like archive command,pg_hba.conf file edit)

       --Ios patching completed now standby1 bring back all serverice and database-----> rsync is working or not?

2.Clinet give full downtime of the four servers.which one i need to down first

      ---mster or standby 1 or standby 2(please dont confuse/include witness server)

      -

Highlighted
EDB Team Member

Re: EDB-EFM-REPLICATIONS


@Din2pg wrote:

Hi @bbissett 

            Thanks for you promt action..but i want to clarify some thing.

see..

1.Now iam going to patch standby 1---------->can i change any parameter in master(like archive command,pg_hba.conf file edit)

       --Ios patching completed now standby1 bring back all serverice and database-----> rsync is working or not?

2.Clinet give full downtime of the four servers.which one i need to down first

      ---mster or standby 1 or standby 2(please dont confuse/include witness server)

      -


Sorry, I can't help you with #1. For #2, it's safer I believe to patch the standby databases before the master.

 

Hopefully someone else can help out here.

 

Bobby

 

Highlighted
EDB Team Member

Re: EDB-EFM-REPLICATIONS

Just to be really clear about my initial question: you're talking about patching the databases, not upgrading efm, right?

 

Bobby

 

Highlighted
Silver Adventurer

Re: EDB-EFM-REPLICATIONS

Hi @bbissett 

              yes only patching time how to start and stop the serial's..not upgrade efm...

 

Thanks

Diny

Highlighted
EDB Team Member

Re: EDB-EFM-REPLICATIONS

Hi Din, 

 

As per my understanding. Your question would be stopping/starting agents when Maintenance.

The answer would be. For stopping EFM services , Please follow below sequence 

 

1.Stop EFM Service on Witness

2.Stop EFM Service on Slave 2

3.Stop EFM Serivce on Slave 1

4.Stop EFM Serivce on Master.

 

For Starting EFM services: You can go with any order. 

 

Please let me know if you need anymore details. 

 

Regards

Siva.

 

Highlighted
EDB Team Member

Re: EDB-EFM-REPLICATIONS

 


@sivamekala wrote:

Hi Din, 

 

As per my understanding. Your question would be stopping/starting agents when Maintenance.

The answer would be. For stopping EFM services , Please follow below sequence 

 

1.Stop EFM Service on Witness

2.Stop EFM Service on Slave 2

3.Stop EFM Serivce on Slave 1

4.Stop EFM Serivce on Master.

 

For Starting EFM services: You can go with any order. 

 


 

I think this was already covered above. It does not matter what order you stop the efm agents or what order you start them. Personally, I would use the 'efm stop-cluster' command and stop them all at once.

 

Cheers,

Bobby

 

 

Highlighted
Silver Adventurer

Re: EDB-EFM-REPLICATIONS

Hi 

     i have an issue in th efm-3.4

we installed db 2 server and install efm in 3 servers'.but cannot accept database information(not sync.)

Please help to how to sync woth cluster.

 

FYI:-

---

[root@SG********** efm-3.4]# /usr/edb/efm-3.4/bin/efm cluster-status efm
Cluster Status: efm

Agent Type Address Agent DB VIP
-----------------------------------------------------------------------
Idle 10.138.50.23 UP UNKNOWN 10.138.50.101*

Allowed node host list:
10.138.50.23

Membership coordinator: 10.138.50.23

Standby priority host list:
(List is empty.)

Promote Status:

Did not find XLog location for any non-idle nodes.

Idle Node Status (idle nodes ignored in XLog location comparisons):

Address XLog Loc Info
--------------------------------------------------------------
10.138.50.23 UNKNOWN The server does not support SSL.
[root@SG******** efm-3.4]#

Highlighted
EDB Team Member

Re: EDB-EFM-REPLICATIONS

Hi Din, 

 

I kindly request you to please provide some more information or please go through below. 

 

1. Did you setup streaming replication and both master and slave are in sync...?

2. Please read parameter descriptions available in efm.properties file. And read efm documentation for more information. Please assign valid values to efm parameters.

3. If your database doesn't accept SSL, Please turn off this on efm. (jdbc.sslmode=disable)

4. Please make sure all files(efm.properties, efm.nodes) having proper permissions before setting up efm cluster. 

 

Among below is one of the way you can setup efm cluster after pre-requisites done:

 

a. Start efm service on master

2. Send allow node to slave from master. 

3. Add master and slave node ip address(ip:bindaddress- ex: 192.168.1.100:7800) in efm.nodes file on slave

4. Then start slave server efm service. Check cluster status.

5. Send allow node to witness from master. 

6. Add master and slave node and witness node ip address(ip:bindaddress) in efm.nodes file on witness

7. Then start witness efm service. Check cluster status.

 

Please let us know if you need anymore information. 

 

Regards

Siva.

 

 

 

 

 

 

Silver Adventurer

Re: EDB-EFM-REPLICATIONS

Hi Siva,

        AS per your below command.i added the bind ip in efm.node file and have valid permission.

 

1.Did you setup streaming replication and both master and slave are in sync...?

Yes.Master and slave in Sync.

2. Please read parameter descriptions available in efm.properties file. And read efm documentation for more information. Please assign valid values to efm parameters.?

    Yes,i configure the valid parameters as per my old projects..

3. If your database doesn't accept SSL, Please turn off this on efm. (jdbc.sslmode=disable)?

    Okie,but if i will set disable any proble in this connection ,becuase in my old project efm2.0 it in verify-ca is there(little confused).

4. Please make sure all files(efm.properties, efm.nodes) having proper permissions before setting up efm cluster. 

      yes all are in proper permissions.  eg.chmod 644 efm.properties,chmod 666 efm.nodes

                  --

Ok after done as per your command.

 

[root@SGATRUATDB03 efm-3.4]# /usr/edb/efm-3.4/bin/efm cluster-status efm
Cluster Status: efm

Agent Type Address Agent DB VIP
-----------------------------------------------------------------------
Idle 10.138.50.23 UP UNKNOWN 10.138.50.101*
Idle 10.138.50.24 UP UNKNOWN 10.138.50.101
Witness 10.138.50.25 UP N/A 10.138.50.101

Allowed node host list:
10.138.50.23 10.138.50.24 10.138.50.25

Membership coordinator: 10.138.50.23

Standby priority host list:
(List is empty.)

Promote Status:

Did not find XLog location for any non-idle nodes.

Idle Node Status (idle nodes ignored in XLog location comparisons):

Address XLog Loc Info
--------------------------------------------------------------
10.138.50.24 UNKNOWN The server does not support SSL.
10.138.50.23 UNKNOWN The server does not support SSL.
[root@SGATRUATDB03 efm-3.4]#

 

 

 

FYI:-

Try to start after seeting ssl disable in efm.properties file..cannot start in efm.service in Master node.

The errror is:-

4/22/19 10:50:47 AM Starting agent.
4/22/19 10:50:47 AM Database user validation failed. Cannot start agent. Check logs for more details.
4/22/19 10:50:47 AM 2019-04-22 10:50:47,353 Notification-ShutdownHook WARN Unable to register Log4j shutdown hook because JVM is shutting down. Using SimpleLogger
4/22/19 10:52:58 AM Starting agent.
4/22/19 10:52:58 AM Database user validation failed. Cannot start agent. Check logs for more details.
4/22/19 10:52:58 AM 2019-04-22 10:52:58,867 Notification-ShutdownHook WARN Unable to register Log4j shutdown hook because JVM is shutting down. Using SimpleLogger

 

 

 

Highlighted
Silver Adventurer

Re: EDB-EFM-REPLICATIONS

Hi @sivamekala  @bbissett 

             This post show "its yesterday updated" please advice me on this..

 

Thanks

Highlighted
EDB Team Member

Re: EDB-EFM-REPLICATIONS

I would advise you send the current logs/steps to your support contact. I *think* you posted something from the efm startup log but not the agent log that has the full details.

 

Bobby

 

Highlighted
EDB Team Member

Re: EDB-EFM-REPLICATIONS

 


@Din2pg wrote:

Hi @sivamekala  @bbissett 

             This post show "its yesterday updated" please advice me on this..

 

Thanks


 

Please, you don't need to include me directly. If you need help right away, contact your support person. I help here when I'm available.

 

Bobby