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 <[email protected]> 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 >
