On 03/14/2018 08:35 AM, Muhammad Sharfuddin wrote:
> Hi Andrei,
> >Somehow I miss corosync confiuration in this thread. Do you know
> >wait-for-all is set (how?) or you just assume it?
> >
> solution found, I was not using "wait_for_all" option, I was assuming
> that "two_node: 1"
> would be
On Wed, Mar 14, 2018 at 10:35 AM, Muhammad Sharfuddin
wrote:
> Hi Andrei,
>>Somehow I miss corosync confiuration in this thread. Do you know
>>wait-for-all is set (how?) or you just assume it?
>>
> solution found, I was not using "wait_for_all" option, I was assuming
Hi Andrei,
>Somehow I miss corosync confiuration in this thread. Do you know
>wait-for-all is set (how?) or you just assume it?
>
solution found, I was not using "wait_for_all" option, I was assuming
that "two_node: 1"
would be sufficient:
nodelist {
node { ring0_addr: 10.8.9.151
On 03/13/2018 03:43 PM, Muhammad Sharfuddin wrote:
> Thanks a lot for the explanation. But other then the ocfs2 resource
> group, this cluster starts all other resources
>
> on a single node, without any issue just because the use of
> "no-quorum-policy=ignore" option.
Yes I know. And what I
Thanks a lot for the explanation. But other then the ocfs2 resource
group, this cluster starts all other resources
on a single node, without any issue just because the use of
"no-quorum-policy=ignore" option.
--
Regards,
Muhammad Sharfuddin
On 3/13/2018 7:32 PM, Klaus Wenninger wrote:
On
On 03/13/2018 02:30 PM, Muhammad Sharfuddin wrote:
> Yes, by saying pacemaker, I meant to say corosync as well.
>
> Is there any fix ? or a two node cluster can't run ocfs2 resources
> when one node is offline ?
Actually there can't be a "fix" as 2 nodes are just not enough
for a partial-cluster
On 03/13/2018 02:03 PM, Muhammad Sharfuddin wrote:
> Hi,
>
> 1 - if I put a node(node2) offline; ocfs2 resources keep running on
> online node(node1)
>
> 2 - while node2 was offline, via cluster I stop/start the ocfs2
> resource group successfully so many times in a row.
>
> 3 - while node2 was
Hi,
1 - if I put a node(node2) offline; ocfs2 resources keep running on
online node(node1)
2 - while node2 was offline, via cluster I stop/start the ocfs2 resource
group successfully so many times in a row.
3 - while node2 was offline; I restart the pacemaker service on the
node1 and then