Project

General

Profile

Support #9703

Support #9068: Move the GUMS databases to the DB groups HA facility

Stop the databases on fg5x4/6x4

Added by Anthony Tiradani over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Start date:
08/20/2015
Due date:
08/20/2015
% Done:

100%

Estimated time:
1.00 h
Spent time:
Duration: 1

Description

Stop the databases on fg5x2/6x2. Leave intact for a short time to provide a fall back in case of migration failures.


Related issues

Precedes GUMS - Support #9702: Migrate data from fg5x4/6x4 to new mariadb production GUMS clusterClosed08/21/201508/21/2015

History

#1 Updated by Gerard Bernabeu Altayo over 4 years ago

  • Subject changed from Stop the databases on fg5x2/6x2 to Stop the databases on fg5x4/6x4

#2 Updated by Gerard Bernabeu Altayo over 4 years ago

  • Precedes Support #9702: Migrate data from fg5x4/6x4 to new mariadb production GUMS cluster added

#3 Updated by Gerard Bernabeu Altayo over 4 years ago

  • Due date set to 08/05/2015
  • Start date changed from 07/22/2015 to 08/05/2015
  • Estimated time set to 1.00 h

#4 Updated by Merina Albert over 4 years ago

  • Due date changed from 08/05/2015 to 08/20/2015
  • Start date changed from 08/05/2015 to 08/20/2015
  • % Done changed from 0 to 100

#5 Updated by Merina Albert over 4 years ago

  • Status changed from New to Closed

#6 Updated by Gerard Bernabeu Altayo over 4 years ago

This was NOT properly done, DBs are still running on both fg5x4/6x4...

Please add notes on what was done when updating tickets (eg: maybe it was done but something brought them up again).

Disabling the network for those systems and powering them off:

[root@fg5x4 ~]# ifdown lo:124
[root@fg5x4 ~]# vim /etc/sysconfig/network-scripts/ifcfg-lo:124
[root@fg5x4 ~]# poweroff

Broadcast message from root (pts/0) (Thu Sep 3 13:21:12 2015):

The system is going down for system halt NOW!
[root@fg5x4 ~]# Connection to fg5x4 closed by remote host.
Connection to fg5x4 closed.

[root@fg6x4 ~]# vim /etc/sysconfig/network-scripts/ifcfg-lo:124
[root@fg6x4 ~]# vim /etc/sysconfig/network-scripts/ifcfg-eth0
[root@fg6x4 ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:3E:05:06:04
inet addr:131.225.152.109 Bcast:131.225.153.255 Mask:255.255.254.0
inet6 addr: fe80::216:3eff:fe05:604/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17176277365 errors:0 dropped:0 overruns:0 frame:0
TX packets:16654427596 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3892763465340 (3.5 TiB) TX bytes:3587492635866 (3.2 TiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:24135500 errors:0 dropped:0 overruns:0 frame:0
TX packets:24135500 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2429372961 (2.2 GiB) TX bytes:2429372961 (2.2 GiB)

[root@fg6x4 ~]# poweroff

Broadcast message from root (pts/0) (Thu Sep 3 13:22:05 2015):

The system is going down for system halt NOW!
[root@fg6x4 ~]# Connection to fg6x4 closed by remote host.
Connection to fg6x4 closed.

On the ifcfg* files I have set:

ONBOOT=no

Gerard

#7 Updated by Gerard Bernabeu Altayo over 4 years ago

Updating the hypervisors so that they don't autostart the node:

[root@fermigrid15 ~]# virsh autostart --disable fg5x4
Domain fg5x4 unmarked as autostarted

[root@fermigrid16 ~]# virsh autostart --disable fg6x4
Domain fg6x4 unmarked as autostarted

#8 Updated by Merina Albert over 4 years ago

mysql stop on these nodes were not enough as they started next day.

"chkconfig mysqld off" should be performed.



Also available in: Atom PDF