Hi,

On Thu, Dec 30, 2010 at 08:56:09PM +0000, James Smith wrote:
> Hi,
> 
> I've been hitting some problems with my drbd / iscsi-target clusters, 
> resources
> dropping in to FAILED (unmanaged) states etc.  I'm after a bit of a sanity 
> check
> on the config below.
> 
> Firstly, I know the timesouts and intervals are lacking / too short on some
> resources.  I'm also looking for advice on this.

If you run your configuration through crm configure verify, it
will let you know what are the recommended minimum timeouts.
Your timeouts are really too short. As for intervals, that
depends on your requirements/resources/expectations. Just note
that the shorter the interval, the more computing resources your
nodes will devote to monitoring.

>   It's not clear to me what an interval
> would do on a start / stop operation?

Nothing. Due to XML schema limitations they have to be present,
but they should always be set to 0.

Can't comment further on the configuration.

Thanks,

Dejan

> node iscsi1cl5 \
>         attributes standby="off"
> node iscsi2cl5 \
>         attributes standby="off"
> primitive ClusterIP ocf:heartbeat:IPaddr2 \
>         params ip="10.100.0.104" cidr_netmask="255.255.255.0" nic="vlan158" \
>         op monitor interval="1s" \
>         meta migration-threshold="3"
> primitive iscsidrbd ocf:linbit:drbd \
>         params drbd_resource="iscsidisk" \
>         op monitor interval="1s" \
>         meta migration-threshold="3"
> primitive iscsilun ocf:heartbeat:iSCSILogicalUnit \
>         params implementation="iet" lun="5" 
> target_iqn="iqn.2010-05.iscsicl5:LUN05.sanvol" path="/dev/drbd0" 
> scsi_id="cl5iscsi" vendor_id="INTERNAL" \
>         op monitor interval="1s" timeout="5s" \
>         meta target-role="Started" migration-threshold="3"
> primitive iscsitarget ocf:heartbeat:iSCSITarget \
>         params implementation="iet" iqn="iqn.2010-05.iscsicl5:LUN05.sanvol" \
>         meta target-role="Started" migration-threshold="3" \
>         op monitor interval="1s" timeout="5s"
> primitive ping_gw ocf:pacemaker:ping \
>         params name="pingd" host_list="1.1.1.254 1.1.1.243 1.1.1.244" 
> multiplier="3000" attempts="2" \
>         op start interval="0" timeout="60s" \
>         op monitor interval="3s" timeout="10s" \
>         meta migration-threshold="3"
> group coregroup ClusterIP iscsitarget iscsilun
> ms iscsidrbdclone iscsidrbd \
>         meta master-max="1" master-node-max="1" clone-max="2" 
> clone-node-max="1" notify="true" target-role="Started" migration-threshold="3"
> clone ping_clone ping_gw
> location iscsidrbdclone-with-ping iscsidrbdclone \
>         rule $id="iscsidrbdclone-with-ping-rule" pingd: defined pingd
> colocation core_group-with-iscsidrbdclone inf: coregroup iscsidrbdclone:Master
> order iscsidrbdclone-before-core_group inf: iscsidrbdclone:promote 
> iscsitarget:start
> property $id="cib-bootstrap-options" \
>         dc-version="1.0.10-da7075976b5ff0bee71074385f8fd02f296ec8a3" \
>         cluster-infrastructure="openais" \
>         expected-quorum-votes="2" \
>         stonith-enabled="false" \
>         no-quorum-policy="ignore" \
>         last-lrm-refresh="1293447778"
> rsc_defaults $id="rsc-options" \
>         resource-stickiness="100"
> 
> Regards,
> James
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to