hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shubham Sharma <ssha...@pivotal.io>
Subject Hawq standby sync fails if there are existing connections to master
Date Mon, 13 Nov 2017 03:58:20 GMT
Hello folks,

Recently observed a behaviour while re-syncing standby from hawq command

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 terminate
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 work
on a pull request to fix this.

Looking forward to your thoughts on this.
Shubham Sharma

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message