[Pacemaker] i stop mysql service but the crm status is still runing
ch huang
justlooks at gmail.com
Mon Jun 7 01:23:52 UTC 2010
i notice my drbd status is abnormal,it seems they can not find each
other,and i try to restart drbd ,but still can not find each other
before restart drbd
[root at PRIM init.d]# cat /proc/drbd
version: 8.3.2 (api:88/proto:86-90)
GIT-hash: dd7985327f146f33b86d4bff5ca8c94234ce840e build by
mockbuild at v20z-x86-64.home.local, 2009-08-29 14:02:24
1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----
ns:0 nr:0 dw:100 dr:2863 al:3 bm:3 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
oos:16384
[root at SEC ~]# cat /proc/drbd
version: 8.3.2 (api:88/proto:86-90)
GIT-hash: dd7985327f146f33b86d4bff5ca8c94234ce840e build by
mockbuild at v20z-x86-64.home.local, 2009-08-29 14:02:24
1: cs:StandAlone ro:Secondary/Unknown ds:Outdated/DUnknown r----
ns:0 nr:0 dw:0 dr:0 al:0 bm:18 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:270284
after restart drbd
[root at PRIM init.d]# cat /proc/drbd
version: 8.3.2 (api:88/proto:86-90)
GIT-hash: dd7985327f146f33b86d4bff5ca8c94234ce840e build by
mockbuild at v20z-x86-64.home.local, 2009-08-29 14:02:24
1: cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown r----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:16384
[root at SEC ~]# cat /proc/drbd
version: 8.3.2 (api:88/proto:86-90)
GIT-hash: dd7985327f146f33b86d4bff5ca8c94234ce840e build by
mockbuild at v20z-x86-64.home.local, 2009-08-29 14:02:24
1: cs:StandAlone ro:Secondary/Unknown ds:Outdated/DUnknown r----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:270284
On Mon, Jun 7, 2010 at 9:15 AM, ch huang <justlooks at gmail.com> wrote:
> mysql is running ,and crm status output is
>
> ============
> Last updated: Sat Jun 5 09:48:58 2010
> Stack: openais
> Current DC: PRIM - partition with quorum
> Version: 1.0.8-9881a7350d6182bae9e8e557cf20a3cc5dac3ee7
> 2 Nodes configured, 2 expected votes
> 2 Resources configured.
> ============
>
> Online: [ PRIM SEC ]
>
> Resource Group: mysql
> fs_mysql (ocf::heartbeat:Filesystem): Started PRIM
> ip_mysql (ocf::heartbeat:IPaddr2): Started PRIM
> mysqld (lsb:mysqld): Started PRIM
> Master/Slave Set: ms_drbd_mysql
> Masters: [ PRIM ]
> Slaves: [ SEC ]
>
> and i finished the mysql by
>
> #service mysqld stop
> Stopping MySQL: [ OK ]
> # service mysqld status
> mysqld is stopped
>
> but in the crm status output , mysql still in running ,i do not understand
> why?
>
> ============
> Last updated: Sat Jun 5 09:48:58 2010
> Stack: openais
> Current DC: PRIM - partition with quorum
> Version: 1.0.8-9881a7350d6182bae9e8e557cf20a3cc5dac3ee7
> 2 Nodes configured, 2 expected votes
> 2 Resources configured.
> ============
>
> Online: [ PRIM SEC ]
>
> Resource Group: mysql
> fs_mysql (ocf::heartbeat:Filesystem): Started PRIM
> ip_mysql (ocf::heartbeat:IPaddr2): Started PRIM
> mysqld (lsb:mysqld): Started PRIM
> Master/Slave Set: ms_drbd_mysql
> Masters: [ PRIM ]
> Slaves: [ SEC ]
>
> and here is my configure
>
> # crm
> crm(live)# configure
> crm(live)configure# show
> node PRIM
> node SEC
> primitive drbd_mysql ocf:linbit:drbd \
> params drbd_resource="r1" \
> op monitor interval="15s"
> primitive fs_mysql ocf:heartbeat:Filesystem \
> params device="/dev/drbd/by-res/r1" directory="/drbddata/"
> fstype="ext3"
> primitive ip_mysql ocf:heartbeat:IPaddr2 \
> params ip="192.168.76.227" nic="eth0"
> primitive mysqld lsb:mysqld
> group mysql fs_mysql ip_mysql mysqld
> ms ms_drbd_mysql drbd_mysql \
> meta master-max="1" master-node-max="1" clone-max="2"
> clone-node-max="1" notify="true"
> colocation mysql_on_drbd inf: mysql ms_drbd_mysql:Master
> order mysql_after_drbd inf: ms_drbd_mysql:promote mysql:start
> property $id="cib-bootstrap-options" \
> no-quorum-policy="ignore" \
> stonith-enabled="false" \
> expected-quorum-votes="2" \
> dc-version="1.0.8-9881a7350d6182bae9e8e557cf20a3cc5dac3ee7" \
> cluster-infrastructure="openais" \
> default-action-timeout="240s"
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100607/f579c120/attachment-0002.htm>
More information about the Pacemaker
mailing list