Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAE44UQcWX33ik89hv1jWRKB_kpZrv3Qtpy9n6c-fs417uZTD4Q@mail.gmail.com>
References: <CAHVwNMi25XCF7YzXqeg6G1oqRfAHy5csyAxx4ZUJkLzrUfJtzA@mail.gmail.com>
 <CAE44UQcWX33ik89hv1jWRKB_kpZrv3Qtpy9n6c-fs417uZTD4Q@mail.gmail.com>
From: Shubham Sharma <ssharma@pivotal.io>
Date: Mon, 13 Nov 2017 16:46:46 -0800
Message-ID: <CAHVwNMi8Rg5NG9ybD6cWypd00WxJaFhUECd5y3QzCmgBaVzQDw@mail.gmail.com>
Subject: Re: Hawq standby sync fails if there are existing connections to master
To: dev@hawq.incubator.apache.org
Content-Type: multipart/alternative; boundary="94eb2c07dcaac4f6eb055de6b8a3"
archived-at: Tue, 14 Nov 2017 00:47:11 -0000

--94eb2c07dcaac4f6eb055de6b8a3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks for the response Lei.

I understand this completely and agree with the behavior that we should not
brutally terminate connections.

However, the case here is, am deliberately trying to use stop mode using
command `hawq init standby -n -v -M fast`. At this point as a user I
understand that connections will be terminated without warning. When
passing option `-M fast` hawq should not interrupt me.

Basically, hawq command line is not respecting `-M fast`. Whereas hawq init
standby --help documents this option. Let me know if this makes sense.


hawq init standby --help

Usage: HAWQ management scripts options


Options:

  -h, --help            show this help message and exit

  -a, --prompt          Execute automatically

  -M STOP_MODE, --mode=3DSTOP_MODE

                        HAWQ stop mode: smart/fast/immediate


On Mon, Nov 13, 2017 at 4:32 PM, Lei Chang <chang.lei.cn@gmail.com> wrote:

> Hi Shubham,
>
> The behavior is intentional. If there are connections when HAWQ init
> standby, it is better to warn the client instead of cutting the connectio=
ns
> brutally.
>
> Cheers
> Lei
>
>
>
> On Mon, Nov 13, 2017 at 11:58 AM, Shubham Sharma <ssharma@pivotal.io>
> wrote:
>
> > Hello folks,
> >
> > Recently observed a behaviour while re-syncing standby from hawq comman=
d
> > line.
> >
> > Here are the reproduction steps -
> >
> > 1 - Open a client connection to hawq using psql
> > 2 - From a different terminal run command - hawq init standby -n -v -M
> fast
> > 3 - Standby resync fails with error
> >
> >
> > 20171113:03:49:21:158354 hawq_stop:hdp3:gpadmin-[WARNING]:-There are
> > other connections to this instance, shutdown mode smart aborted
> >
> > 20171113:03:49:21:158354 hawq_stop:hdp3:gpadmin-[WARNING]:-Either
> > remove connections, or use 'hawq stop master -M fast' or 'hawq stop
> > master -M immediate'
> >
> > 20171113:03:49:21:158354 hawq_stop:hdp3:gpadmin-[WARNING]:-See hawq
> > stop --help for all options
> >
> > 20171113:03:49:21:158354 hawq_stop:hdp3:gpadmin-[ERROR]:-Active
> > connections. Aborting shutdown...
> >
> > 20171113:03:49:21:158143 hawq_init:hdp3:gpadmin-[ERROR]:-Stop hawq
> > cluster failed, exit
> >
> > 4 - My understanding is when -M (stop mode) is passed it should termina=
te
> > existing client connections. Also, it seems like a good practice to
> > terminate client connections before standby master resync.
> >
> > Is this an expected behavior in hawq ? If not, I can open a JIRA and wo=
rk
> > on a pull request to fix this.
> >
> > Looking forward to your thoughts on this.
> > =E2=80=8B
> > --
> > Regards,
> > Shubham Sharma
> >
>


--=20
Regards,
Shubham Sharma
Staff Customer Engineer
Pivotal Global Support Services
ssharma@pivotal.io
Direct Tel: +1(510)-304-8201
Office Hours: Mon-Fri 9:00 am to 5:00 pm PDT
Out of Office Hours Contact +1 877-477-2269

--94eb2c07dcaac4f6eb055de6b8a3--