[jira] [Updated] (HAWQ-845) Parameter kerberos principal name for HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated HAWQ-845: Description: Currently HAWQ only accept the principle 'postgres' for kerberos settings. This is because there its hardcoded in gpcheckhdfs, we should ensure that it can be parameterized. Also, its better to change the default principal name postgres to gpadmin. It will avoid the need of changing the the hdfs directory during securing the cluster to postgres and will avoid the need of maintaing postgres user. was: Currently HAWQ only accept the principle 'postgres' for kerberos settings. This is because there its hardcoded in gpcheckhdfs, we should ensure that it can be parameterized. > Parameter kerberos principal name for HAWQ > -- > > Key: HAWQ-845 > URL: https://issues.apache.org/jira/browse/HAWQ-845 > Project: Apache HAWQ > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: Lei Chang > > Currently HAWQ only accept the principle 'postgres' for kerberos settings. > This is because there its hardcoded in gpcheckhdfs, we should ensure that it > can be parameterized. > Also, its better to change the default principal name postgres to gpadmin. It > will avoid the need of changing the the hdfs directory during securing the > cluster to postgres and will avoid the need of maintaing postgres user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-845) Parameter kerberos principal name for HAWQ
bhuvnesh chaudhary created HAWQ-845: --- Summary: Parameter kerberos principal name for HAWQ Key: HAWQ-845 URL: https://issues.apache.org/jira/browse/HAWQ-845 Project: Apache HAWQ Issue Type: Bug Reporter: bhuvnesh chaudhary Assignee: Lei Chang Currently HAWQ only accept the principle 'postgres' for kerberos settings. This is because there its hardcoded in gpcheckhdfs, we should ensure that it can be parameterized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-717) HAWQ hawq ssh-exkeys command should consider the string exactly as its given at the command line prompt
[ https://issues.apache.org/jira/browse/HAWQ-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary resolved HAWQ-717. - Resolution: Fixed > HAWQ hawq ssh-exkeys command should consider the string exactly as its given > at the command line prompt > --- > > Key: HAWQ-717 > URL: https://issues.apache.org/jira/browse/HAWQ-717 > Project: Apache HAWQ > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > > HAWQ hawq ssh-exkeys command should consider the string exactly as its given > at the command line prompt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-717) HAWQ hawq ssh-exkeys command should consider the string exactly as its given at the command line prompt
[ https://issues.apache.org/jira/browse/HAWQ-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary reassigned HAWQ-717: --- Assignee: bhuvnesh chaudhary (was: Lei Chang) > HAWQ hawq ssh-exkeys command should consider the string exactly as its given > at the command line prompt > --- > > Key: HAWQ-717 > URL: https://issues.apache.org/jira/browse/HAWQ-717 > Project: Apache HAWQ > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.1.0 > > > HAWQ hawq ssh-exkeys command should consider the string exactly as its given > at the command line prompt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-717) HAWQ hawq ssh-exkeys command should consider the string exactly as its given at the command line prompt
[ https://issues.apache.org/jira/browse/HAWQ-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated HAWQ-717: Affects Version/s: 2.0.0 > HAWQ hawq ssh-exkeys command should consider the string exactly as its given > at the command line prompt > --- > > Key: HAWQ-717 > URL: https://issues.apache.org/jira/browse/HAWQ-717 > Project: Apache HAWQ > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.1.0 > > > HAWQ hawq ssh-exkeys command should consider the string exactly as its given > at the command line prompt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-717) HAWQ hawq ssh-exkeys command should consider the string exactly as its given at the command line prompt
[ https://issues.apache.org/jira/browse/HAWQ-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated HAWQ-717: Description: HAWQ hawq ssh-exkeys command should consider the string exactly as its given at the command line prompt. (was: HAWQ hawq ssh-exkeys command should consider the string exactly as its given at the command line prompt. Currently, if the password is given as "abcd; touch abc.txt", hawq splits the password and considers touch abc.txt as a different command and creates a files. We should avoid such behavior.) > HAWQ hawq ssh-exkeys command should consider the string exactly as its given > at the command line prompt > --- > > Key: HAWQ-717 > URL: https://issues.apache.org/jira/browse/HAWQ-717 > Project: Apache HAWQ > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: Lei Chang > > HAWQ hawq ssh-exkeys command should consider the string exactly as its given > at the command line prompt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (HAWQ-682) hawq init master fails to syncup hawq-site xml if there is a segment host down
[ https://issues.apache.org/jira/browse/HAWQ-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary closed HAWQ-682. --- > hawq init master fails to syncup hawq-site xml if there is a segment host down > -- > > Key: HAWQ-682 > URL: https://issues.apache.org/jira/browse/HAWQ-682 > Project: Apache HAWQ > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.0.0 > > > In hawq init command, default bucket number is calculated and the updated > hawq-site.xml is copied to all the other nodes, if there is a segment host > down it will fail to syncup the fail. > Including the option to skip bad hosts as ambari will override this file > whenever the segment host is brought online and started. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-682) hawq init master fails to syncup hawq-site xml if there is a segment host down
[ https://issues.apache.org/jira/browse/HAWQ-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary resolved HAWQ-682. - Resolution: Fixed Fix Version/s: 2.0.0 > hawq init master fails to syncup hawq-site xml if there is a segment host down > -- > > Key: HAWQ-682 > URL: https://issues.apache.org/jira/browse/HAWQ-682 > Project: Apache HAWQ > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.0.0 > > > In hawq init command, default bucket number is calculated and the updated > hawq-site.xml is copied to all the other nodes, if there is a segment host > down it will fail to syncup the fail. > Including the option to skip bad hosts as ambari will override this file > whenever the segment host is brought online and started. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-682) hawq init master fails to syncup hawq-site xml if there is a segment host down
[ https://issues.apache.org/jira/browse/HAWQ-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated HAWQ-682: Description: In hawq init command, default bucket number is calculated and the updated hawq-site.xml is copied to all the other nodes, if there is a segment host down it will fail to syncup the fail. Including the option to skip bad hosts as ambari will override this file whenever the segment host is brought online and started. was: In hawq init command, default bucket number is calculated and the updated hawq-site.xml is copied to all the other nodes. Including the option to skip bad hosts. > hawq init master fails to syncup hawq-site xml if there is a segment host down > -- > > Key: HAWQ-682 > URL: https://issues.apache.org/jira/browse/HAWQ-682 > Project: Apache HAWQ > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: Lei Chang > > In hawq init command, default bucket number is calculated and the updated > hawq-site.xml is copied to all the other nodes, if there is a segment host > down it will fail to syncup the fail. > Including the option to skip bad hosts as ambari will override this file > whenever the segment host is brought online and started. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-682) hawq init master fails to syncup hawq-site xml if there is a segment host down
[ https://issues.apache.org/jira/browse/HAWQ-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary reassigned HAWQ-682: --- Assignee: bhuvnesh chaudhary (was: Lei Chang) > hawq init master fails to syncup hawq-site xml if there is a segment host down > -- > > Key: HAWQ-682 > URL: https://issues.apache.org/jira/browse/HAWQ-682 > Project: Apache HAWQ > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > > In hawq init command, default bucket number is calculated and the updated > hawq-site.xml is copied to all the other nodes, if there is a segment host > down it will fail to syncup the fail. > Including the option to skip bad hosts as ambari will override this file > whenever the segment host is brought online and started. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-682) hawq init master fails to syncup hawq-site xml if there is a segment host down
bhuvnesh chaudhary created HAWQ-682: --- Summary: hawq init master fails to syncup hawq-site xml if there is a segment host down Key: HAWQ-682 URL: https://issues.apache.org/jira/browse/HAWQ-682 Project: Apache HAWQ Issue Type: Bug Reporter: bhuvnesh chaudhary Assignee: Lei Chang In hawq init command, default bucket number is calculated and the updated hawq-site.xml is copied to all the other nodes. Including the option to skip bad hosts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-679) During remove standby host if a segment host is down remove standby host fails
[ https://issues.apache.org/jira/browse/HAWQ-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary reassigned HAWQ-679: --- Assignee: bhuvnesh chaudhary (was: Lei Chang) > During remove standby host if a segment host is down remove standby host fails > -- > > Key: HAWQ-679 > URL: https://issues.apache.org/jira/browse/HAWQ-679 > Project: Apache HAWQ > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.0.0 > > > During remove standby host command if a segment host is down remove standby > host fails. Added ignore_bad_hosts flag to remove standby command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-677) During activate standby ignore-bad-hosts flag is not passed to the command
[ https://issues.apache.org/jira/browse/HAWQ-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary resolved HAWQ-677. - Resolution: Fixed Fix Version/s: 2.0.0 > During activate standby ignore-bad-hosts flag is not passed to the command > -- > > Key: HAWQ-677 > URL: https://issues.apache.org/jira/browse/HAWQ-677 > Project: Apache HAWQ > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: Lei Chang > Fix For: 2.0.0 > > > During activate standby ignore-bad-hosts flag supplied to activate standby > operation is not passed to the stop allsegments command. So, even though it > was expected to ignore bad hosts, stop all segments tries to stop on the bad > node and fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-677) During activate standby ignore-bad-hosts flag is not passed to the command
[ https://issues.apache.org/jira/browse/HAWQ-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary reassigned HAWQ-677: --- Assignee: bhuvnesh chaudhary (was: Lei Chang) > During activate standby ignore-bad-hosts flag is not passed to the command > -- > > Key: HAWQ-677 > URL: https://issues.apache.org/jira/browse/HAWQ-677 > Project: Apache HAWQ > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.0.0 > > > During activate standby ignore-bad-hosts flag supplied to activate standby > operation is not passed to the stop allsegments command. So, even though it > was expected to ignore bad hosts, stop all segments tries to stop on the bad > node and fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-679) During remove standby host if a segment host is down remove standby host fails
[ https://issues.apache.org/jira/browse/HAWQ-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary resolved HAWQ-679. - Resolution: Fixed Fix Version/s: 2.0.0 > During remove standby host if a segment host is down remove standby host fails > -- > > Key: HAWQ-679 > URL: https://issues.apache.org/jira/browse/HAWQ-679 > Project: Apache HAWQ > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: Lei Chang > Fix For: 2.0.0 > > > During remove standby host command if a segment host is down remove standby > host fails. Added ignore_bad_hosts flag to remove standby command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-679) During remove standby host if a segment host is down remove standby host fails
bhuvnesh chaudhary created HAWQ-679: --- Summary: During remove standby host if a segment host is down remove standby host fails Key: HAWQ-679 URL: https://issues.apache.org/jira/browse/HAWQ-679 Project: Apache HAWQ Issue Type: Bug Reporter: bhuvnesh chaudhary Assignee: Lei Chang During remove standby host command if a segment host is down remove standby host fails. Added ignore_bad_hosts flag to remove standby command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-677) During activate standby ignore-bad-hosts flag is not passed to the command
bhuvnesh chaudhary created HAWQ-677: --- Summary: During activate standby ignore-bad-hosts flag is not passed to the command Key: HAWQ-677 URL: https://issues.apache.org/jira/browse/HAWQ-677 Project: Apache HAWQ Issue Type: Bug Reporter: bhuvnesh chaudhary Assignee: Lei Chang During activate standby ignore-bad-hosts flag supplied to activate standby operation is not passed to the stop allsegments command. So, even though it was expected to ignore bad hosts, stop all segments tries to stop on the bad node and fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-617) Add a flag to hawq config to allow skipping hosts on which ssh fails and continue with syncing configurations files
bhuvnesh chaudhary created HAWQ-617: --- Summary: Add a flag to hawq config to allow skipping hosts on which ssh fails and continue with syncing configurations files Key: HAWQ-617 URL: https://issues.apache.org/jira/browse/HAWQ-617 Project: Apache HAWQ Issue Type: Bug Reporter: bhuvnesh chaudhary Assignee: Lei Chang Add a flag to hawq config to allow skipping hosts on which ssh fails and continue with syncing configurations files. Currently, if there is any one bad host, sync operations fails. Hawq activate standby uses hawq config to update hawq-site.xml configuration, however if the active master host is down, it fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
