Re: Antw: Re: file system resource becomes inaccesible when any of the node goes down

On 07/07/2015 12:14 PM, Ulrich Windl wrote:
>>>> Muhammad Sharfuddin <[email protected]> schrieb am 06.07.2015 um 12:14 in
> Nachricht <[email protected]>:
> [...]
>> Ok, so reducing the sbd timeout(or msgwait) would provide the
>> uninterrupted access to the ocfs2 file system on the surviving/online node ?
>> or would it just minimize the downtime ?
> It will reduce the time between "writing the reset message for a node" and "the cluster believes the node is down". So you can guess what happens if you set it to some very short time like 1 second...
>
> Regards,
> Ulrich
>
now msgwait timeout is set to 10s and a delay/inaccessibility of 15 
seconds was observed. If a service(App, DB, file server) is installed 
and running from the ocfs2 file system via the surviving/online node, then
wouldn't that service get crashed or become offline due to the 
inaccessibility of the file system(event though its ocfs2) while a 
member node goes down ?


If cluster is configured to run the two independent services, and starts 
one on node1 and ther on node2, while both the service shared the same 
file system, /sharedata(ocfs2),  then in case of a failure of one node, 
the other/online wont be able to
keep running the particular service because the file system holding the 
binaries/configuration/service is not available for around at least 15 
seconds.

I don't understand the advantage of Ocfs2 file system in such a setup.


-- 
Regards,

Muhammad Sharfuddin
<http://www.nds.com.pk>
_______________________________________________
Linux-HA mailing list is closing down.
Please subscribe to [email protected] instead.
http://clusterlabs.org/mailman/listinfo/users
_______________________________________________
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha