Vladislav Bogdanov bub...@hoster-ok.com schrieb am 12.07.2013 um 11:06 in
Nachricht 51dfc715.2030...@hoster-ok.com:
Hi Dejan,
It seems like resource restart does not work any longer.
BTW: The way resource restart is implemented (i.e.: stop wait, then start)
has a major problem: If stop
On 2013-07-12T12:19:40, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote:
BTW: The way resource restart is implemented (i.e.: stop wait, then
start) has a major problem: If stop causes to fence the node where the crm
command is running, the resource will remain stopped even after the
Lars Marowsky-Bree l...@suse.com schrieb am 12.07.2013 um 12:23 in
Nachricht
20130712102340.go19...@suse.de:
On 2013-07-12T12:19:40, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de
wrote:
BTW: The way resource restart is implemented (i.e.: stop wait, then
start) has a major problem: If
On 2013-07-12T12:26:18, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote:
(Another way to trigger a restart is to modify the instance parameters.
Set __manual_restart=1 and it'll restart.)
once? ;-)
Keep increasing it. ;-)
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff
On 12/07/2013, at 8:23 PM, Lars Marowsky-Bree l...@suse.com wrote:
On 2013-07-12T12:19:40, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de
wrote:
BTW: The way resource restart is implemented (i.e.: stop wait, then
start) has a major problem: If stop causes to fence the node where the crm
