[Pacemaker] iscsi migration to slow (disk errors) tune pacemaker or open-iscsi?

[Florian Haas]

On 2011-02-24 13:05, Jelle de Jong wrote:
> Hello everybody,
> 
> I started a nice new tread for this,
> 
> I seem to got a working drbd/iscsi pacemaker setup that behaves as
> expected when nodes go done/up or resources are moved. (only got some
> issues with the high verbosity in syslog, but that is unrelated to this
> thread)
> 
> When resources are migrated on the crm nods, the open-iscsi client side
> will get disk errors and the running kvm quest will get in trouble, this
> only seems to happen when there is a lot of disk activity on the kvm
> quest, (higher loads on all systems)
> 
> # summary syslog of problem and pacemaker and iscsi configurations.
> http://debian.pastebin.com/FM3P0Qe8
> 
> Would somebody give some advice on either optimising my pacemaker
> configuration or tune my open-iscsi (timeouts?) some examples or good
> documentation URL's would be appreciated.

http://www.linbit.com/en/education/tech-guides/highly-available-iscsi-with-drbd-and-pacemaker/

Mentions DefaultTime2Retain, which is likely what you need to tune.

Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110224/c89afa33/attachment-0003.sig>