hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jiali Yao <j...@pivotal.io>
Subject Re: question on pg_hba.conf updates
Date Tue, 12 Jul 2016 03:32:49 GMT
Hi Radar,

I think we should add the scenario Ming described in document in case when
master is crashed after user add some entries in pg_hba.conf.
Thought?

Jiali


On Tue, Jul 12, 2016 at 11:12 AM, Radar Da lei <rlei@pivotal.io> wrote:

> Hi Ming,
>
> If user manually added some entires into pg_hba.conf and they want it be
> available after activated standby, then user need to add them to standby's
> pg_hba.conf as well.
>
> We do not do sync things for such case. Thanks.
>
> Regards,
> Radar
>
> On Tue, Jul 12, 2016 at 11:05 AM, Ming Li <mli@pivotal.io> wrote:
>
> > Hi Radar,
> >
> > If user manually added some entries into master pg_hba.conf, after we
> > active standby as new master, those entries should be exists on the new
> > master(previous standby).
> >
> > So my question is: when those entries copied? At init standby or active
> > standby?
> >
> > Thanks.
> >
> > On Tue, Jul 12, 2016 at 10:49 AM, Radar Da lei <rlei@pivotal.io> wrote:
> >
> > > Hi Vineet,
> > >
> > > While doing HAWQ cluster init, we will collect master/standby/segment
> ip
> > > addresses and update pg_hba.conf. After hawq init, content of
> > 'pg_hba.conf'
> > > on each node should be different.
> > >
> > > When a cluster adding a new standby, this will get pg_hba.conf updated
> on
> > > all the nodes. Activate standby will not update pg_hba.conf since all
> > > entires already in standby and segments's pg_hba.conf.
> > >
> > > Adding a new segment will only generate a new pg_hba.conf for itself.
> > >
> > > These are what I can think out for this moment. Thanks.
> > >
> > > Regards,
> > > Radar
> > >
> > > On Tue, Jul 12, 2016 at 10:08 AM, Vineet Goel <vvineet@apache.org>
> > wrote:
> > >
> > > > Hi all,
> > > >
> > > > Question related to integration with Apache Ambari.
> > > >
> > > > It would be nice to make pg_hba.conf visible and editable in Ambari,
> so
> > > > that Ambari allows one single interface for admins to update HAWQ and
> > > > System configs such as hawq-site.xml, hawq-check.conf, sysctl.conf,
> > > > limits.conf, hdfs-client.xml, yarn-client.xml etc. Rollback and
> > > > version-history of config files is always a bonus in Ambari.
> > > >
> > > > Are there any backend HAWQ utilities (such as activate-standby or
> > others)
> > > > that update pg_hba.conf file in any way, ever? It would be nice to
> know
> > > so
> > > > that config file change conflicts are managed appropriately.
> > > >
> > > > Thanks
> > > > Vineet
> > > >
> > >
> >
>

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