On Fri, May 11, 2018 at 5:21 PM, Han Zhou wrote:
> Thanks for the output. It appears to be more complex than I thought
> before. It is good that the new slave doesn't listen on 6641, although I am
> not sure how is it achieved. I guess a stop&start has been triggered
> instead of simply demote, b
Thanks for the output. It appears to be more complex than I thought before.
It is good that the new slave doesn't listen on 6641, although I am not
sure how is it achieved. I guess a stop&start has been triggered instead of
simply demote, but I need to spend some time on the pacemaker state
machine
Sure:
*VIP_ip* = 10.149.4.252
*LB IP* = 10.149.0.40
*slave netstat where it syncs from master LB VIP IP *
#netstat -an | grep 6641
tcp0 0 10.169.129.34:47426 10.149.4.252:6641
ESTABLISHED
tcp0 0 10.169.129.34:47444 10.149.4.252:6641
ESTABLISHED
*Slave OVS:, *
#
Ali, could you share output of "ps | grep ovsdb" and "netstat -lpn | grep
6641" on the new slave node after you do "crm resource move"?
On Fri, May 11, 2018 at 2:25 PM, aginwala wrote:
> Thanks Han for more suggestions:
>
>
> I did test failover by gracefully stopping pacemaker+corosync on maste
Thanks Han for more suggestions:
I did test failover by gracefully stopping pacemaker+corosync on master
node along with crm move and it works as expected too as crm move is
triggering promote of new master and hence the new master gets elected
along with slave getting demoted as expected to list
Good progress!
I think at least one more change is needed to ensure when demote happens,
the TCP port is shut down. Otherwise, the LB will be confused again and
can't figure out which one is active. This is the graceful failover
scenario which can be tested by crm resource move instead of reboot/k
On Thu, May 10, 2018 at 1:54 PM, aginwala wrote:
> Hi :
>
> Just to further update, I am able to re-open tcp port for failover
> scenario when new master is getting promoted with additional code changes
> as below which do require stop of ovs service on the new selected master to
> reset the tcp
Hi :
Just to further update, I am able to re-open tcp port for failover scenario
when new master is getting promoted with additional code changes as below
which do require stop of ovs service on the new selected master to reset
the tcp settings:
diff --git a/ovn/utilities/ovndb-servers.ocf
b/ovn
Thanks folks for suggestions:
For LB vip configurations, I did the testing further and yes it does tries
to hit the slave db as per the logs below and fails as slave do not have
write permission of which LB is not aware of:
for i in `seq 1 500`; do ovn-nbctl --db=tcp:10.149.4.252:6641 ls-add
$i59
On Thu, May 10, 2018 at 12:44 AM, Han Zhou wrote:
>
>
> On Wed, May 9, 2018 at 11:51 AM, Numan Siddique
> wrote:
>
>>
>>
>> On Thu, May 10, 2018 at 12:15 AM, Han Zhou wrote:
>>
>>> Thanks Ali for the quick patch. Please see my comments inline.
>>>
>>> On Wed, May 9, 2018 at 9:30 AM, aginwala w
On Wed, May 9, 2018 at 11:51 AM, Numan Siddique wrote:
>
>
> On Thu, May 10, 2018 at 12:15 AM, Han Zhou wrote:
>
>> Thanks Ali for the quick patch. Please see my comments inline.
>>
>> On Wed, May 9, 2018 at 9:30 AM, aginwala wrote:
>> >
>> > Thanks Han and Numan for the clarity to help sort it
On Thu, May 10, 2018 at 12:15 AM, Han Zhou wrote:
> Thanks Ali for the quick patch. Please see my comments inline.
>
> On Wed, May 9, 2018 at 9:30 AM, aginwala wrote:
> >
> > Thanks Han and Numan for the clarity to help sort it out.
> >
> > For making vip work with using LB in my two node setup,
Thanks Ali for the quick patch. Please see my comments inline.
On Wed, May 9, 2018 at 9:30 AM, aginwala wrote:
>
> Thanks Han and Numan for the clarity to help sort it out.
>
> For making vip work with using LB in my two node setup, I had changed
below code to skip setting master IP when creatin
Thanks Han and Numan for the clarity to help sort it out.
For making vip work with using LB in my two node setup, I had changed below
code to skip setting master IP when creating pcs resource for ovndbs and
listen on 0.0.0.0 instead. Hence, the discussion seems inline with the code
change which i
On Wed, May 9, 2018 at 9:02 AM, Numan Siddique wrote:
>
>
> On Wed, May 9, 2018 at 9:02 PM, Han Zhou wrote:
>
>> Hi Numan,
>>
>> Thanks you so much for the detailed answer! Please see my comments inline.
>>
>> On Wed, May 9, 2018 at 7:41 AM, Numan Siddique
>> wrote:
>>
>>> Hi Han,
>>>
>>> Pleas
On Wed, May 9, 2018 at 9:02 PM, Han Zhou wrote:
> Hi Numan,
>
> Thanks you so much for the detailed answer! Please see my comments inline.
>
> On Wed, May 9, 2018 at 7:41 AM, Numan Siddique
> wrote:
>
>> Hi Han,
>>
>> Please see below for inline comments
>>
>> On Wed, May 9, 2018 at 5:17 AM, Han
Hi Numan,
Thanks you so much for the detailed answer! Please see my comments inline.
On Wed, May 9, 2018 at 7:41 AM, Numan Siddique wrote:
> Hi Han,
>
> Please see below for inline comments
>
> On Wed, May 9, 2018 at 5:17 AM, Han Zhou wrote:
>
>> Hi Babu/Numan,
>>
>> I have a question regardin
Hi Han,
Please see below for inline comments
On Wed, May 9, 2018 at 5:17 AM, Han Zhou wrote:
> Hi Babu/Numan,
>
> I have a question regarding OVN pacemaker OCF script.
> I see in the script MASTER_IP is used to start the active DB and standby
> DBs will use that IP to sync from.
>
> In the Docu
Hi Babu/Numan,
I have a question regarding OVN pacemaker OCF script.
I see in the script MASTER_IP is used to start the active DB and standby
DBs will use that IP to sync from.
In the Documentation/topics/integration.rst it is also mentioned:
`master_ip` is the IP address on which the active dat
19 matches
Mail list logo
