[jira] [Commented] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs
[ https://issues.apache.org/jira/browse/AMBARI-17285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365339#comment-15365339 ] bhuvnesh chaudhary commented on AMBARI-17285: - [~jluniya][~ncole] [~jwang] Jayush, during the meetup we spoke about it for a moment, and you suggested that you will followup with your team internally. Any updates on this ? > Custom service repos in repoinfo.xml got overwritten by public VDFs > --- > > Key: AMBARI-17285 > URL: https://issues.apache.org/jira/browse/AMBARI-17285 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov > Fix For: 2.4.0 > > > Ambari 2.4 introduced Version Definition Files that break the functionality > of adding a custom service repo, since custom services do not have an entry > in the public VDF. > In the case of HAWQ, the plugin is installed on Ambari host and it adds the > new repo information to the repoinfo.xml of all available stacks on the file > system. Once Ambari cluster creation wizard queries the latest repo info from > the public URLs, it will get the info for all stack repos, but not the custom > ones. > So, the logic should be: > 1. Use default repoinfo (from file system) as the base > 2. Query public VDF, if available > 3. For each entry in public VDF overwrite values in the default repoinfo > 4. Entries in default repoinfo that do not have corresponding entries in VDF > should stay intact > This way custom services can be added via file edit and the latest > information can still be retrieved and applied for the standard stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17571) Show gpadmin as hawq service account user on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17571: Resolution: Fixed Status: Resolved (was: Patch Available) > Show gpadmin as hawq service account user on Ambari > --- > > Key: AMBARI-17571 > URL: https://issues.apache.org/jira/browse/AMBARI-17571 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-17571.patch > > > Show gpadmin as hawq service account user on Ambari -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17569) Update config update message for Activate HAWQ Standby wizard
[ https://issues.apache.org/jira/browse/AMBARI-17569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17569: Resolution: Fixed Status: Resolved (was: Patch Available) > Update config update message for Activate HAWQ Standby wizard > - > > Key: AMBARI-17569 > URL: https://issues.apache.org/jira/browse/AMBARI-17569 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-17569.patch > > > Update config update message for Activate HAWQ Standby wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17571) Show gpadmin as hawq service account user on Ambari
bhuvnesh chaudhary created AMBARI-17571: --- Summary: Show gpadmin as hawq service account user on Ambari Key: AMBARI-17571 URL: https://issues.apache.org/jira/browse/AMBARI-17571 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.2.0 Reporter: bhuvnesh chaudhary Assignee: bhuvnesh chaudhary Attachments: AMBARI-17571.patch Show gpadmin as hawq service account user on Ambari -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17571) Show gpadmin as hawq service account user on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17571: Attachment: AMBARI-17571.patch > Show gpadmin as hawq service account user on Ambari > --- > > Key: AMBARI-17571 > URL: https://issues.apache.org/jira/browse/AMBARI-17571 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-17571.patch > > > Show gpadmin as hawq service account user on Ambari -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17571) Show gpadmin as hawq service account user on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17571: Fix Version/s: 2.4.0 Status: Patch Available (was: Open) > Show gpadmin as hawq service account user on Ambari > --- > > Key: AMBARI-17571 > URL: https://issues.apache.org/jira/browse/AMBARI-17571 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-17571.patch > > > Show gpadmin as hawq service account user on Ambari -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17569) Update config update message for Activate HAWQ Standby wizard
[ https://issues.apache.org/jira/browse/AMBARI-17569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17569: Fix Version/s: 2.4.0 > Update config update message for Activate HAWQ Standby wizard > - > > Key: AMBARI-17569 > URL: https://issues.apache.org/jira/browse/AMBARI-17569 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-17569.patch > > > Update config update message for Activate HAWQ Standby wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17569) Update config update message for Activate HAWQ Standby wizard
[ https://issues.apache.org/jira/browse/AMBARI-17569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17569: Attachment: AMBARI-17569.patch > Update config update message for Activate HAWQ Standby wizard > - > > Key: AMBARI-17569 > URL: https://issues.apache.org/jira/browse/AMBARI-17569 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-17569.patch > > > Update config update message for Activate HAWQ Standby wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17569) Update config update message for Activate HAWQ Standby wizard
[ https://issues.apache.org/jira/browse/AMBARI-17569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17569: Status: Patch Available (was: Open) > Update config update message for Activate HAWQ Standby wizard > - > > Key: AMBARI-17569 > URL: https://issues.apache.org/jira/browse/AMBARI-17569 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Priority: Minor > Attachments: AMBARI-17569.patch > > > Update config update message for Activate HAWQ Standby wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17569) Update config update message for Activate HAWQ Standby wizard
[ https://issues.apache.org/jira/browse/AMBARI-17569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17569: Affects Version/s: (was: 2.4.0) 2.2.0 > Update config update message for Activate HAWQ Standby wizard > - > > Key: AMBARI-17569 > URL: https://issues.apache.org/jira/browse/AMBARI-17569 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-17569.patch > > > Update config update message for Activate HAWQ Standby wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-17569) Update config update message for Activate HAWQ Standby wizard
[ https://issues.apache.org/jira/browse/AMBARI-17569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary reassigned AMBARI-17569: --- Assignee: bhuvnesh chaudhary > Update config update message for Activate HAWQ Standby wizard > - > > Key: AMBARI-17569 > URL: https://issues.apache.org/jira/browse/AMBARI-17569 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-17569.patch > > > Update config update message for Activate HAWQ Standby wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17569) Update config update message for Activate HAWQ Standby wizard
bhuvnesh chaudhary created AMBARI-17569: --- Summary: Update config update message for Activate HAWQ Standby wizard Key: AMBARI-17569 URL: https://issues.apache.org/jira/browse/AMBARI-17569 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: bhuvnesh chaudhary Priority: Minor Update config update message for Activate HAWQ Standby wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17208) Add logging for the command executed during PXF service check
[ https://issues.apache.org/jira/browse/AMBARI-17208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17208: Resolution: Fixed Status: Resolved (was: Patch Available) > Add logging for the command executed during PXF service check > - > > Key: AMBARI-17208 > URL: https://issues.apache.org/jira/browse/AMBARI-17208 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-17208.patch > > > Add logging for the command executed during PXF service check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17023) Show only relevant properties based on the status of HAWQ Resource Manager
[ https://issues.apache.org/jira/browse/AMBARI-17023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17023: Resolution: Fixed Status: Resolved (was: Patch Available) > Show only relevant properties based on the status of HAWQ Resource Manager > -- > > Key: AMBARI-17023 > URL: https://issues.apache.org/jira/browse/AMBARI-17023 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-17023-1.patch, AMBARI-17023-2.patch, > AMBARI-17023.patch > > > Show only relevant properties based on the status of HAWQ Resource Manager. > When Yarn mode is enable, only two parameters should be invisible. > hawq_rm_memory_limit_perseg > hawq_rm_nvcore_limit_perseg > When standalone mode is enabled, four parameters should be invisible. what > you list are correct. > hawq_rm_yarn_app_name > hawq_rm_yarn_queue_name > hawq_rm_yarn_scheduler_address > hawq_rm_yarn_address -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17208) Add logging for the command executed during PXF service check
[ https://issues.apache.org/jira/browse/AMBARI-17208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17208: Attachment: AMBARI-17208.patch > Add logging for the command executed during PXF service check > - > > Key: AMBARI-17208 > URL: https://issues.apache.org/jira/browse/AMBARI-17208 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-17208.patch > > > Add logging for the command executed during PXF service check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17208) Add logging for the command executed during PXF service check
[ https://issues.apache.org/jira/browse/AMBARI-17208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17208: Assignee: bhuvnesh chaudhary Fix Version/s: 2.4.0 Status: Patch Available (was: Open) > Add logging for the command executed during PXF service check > - > > Key: AMBARI-17208 > URL: https://issues.apache.org/jira/browse/AMBARI-17208 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > > Add logging for the command executed during PXF service check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17208) Add logging for the command executed during PXF service check
bhuvnesh chaudhary created AMBARI-17208: --- Summary: Add logging for the command executed during PXF service check Key: AMBARI-17208 URL: https://issues.apache.org/jira/browse/AMBARI-17208 Project: Ambari Issue Type: Improvement Affects Versions: 2.4.0 Reporter: bhuvnesh chaudhary Add logging for the command executed during PXF service check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17023) Show only relevant properties based on the status of HAWQ Resource Manager
[ https://issues.apache.org/jira/browse/AMBARI-17023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17023: Attachment: AMBARI-17023-2.patch > Show only relevant properties based on the status of HAWQ Resource Manager > -- > > Key: AMBARI-17023 > URL: https://issues.apache.org/jira/browse/AMBARI-17023 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-17023-1.patch, AMBARI-17023-2.patch, > AMBARI-17023.patch > > > Show only relevant properties based on the status of HAWQ Resource Manager. > When Yarn mode is enable, only two parameters should be invisible. > hawq_rm_memory_limit_perseg > hawq_rm_nvcore_limit_perseg > When standalone mode is enabled, four parameters should be invisible. what > you list are correct. > hawq_rm_yarn_app_name > hawq_rm_yarn_queue_name > hawq_rm_yarn_scheduler_address > hawq_rm_yarn_address -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17023) Show only relevant properties based on the status of HAWQ Resource Manager
[ https://issues.apache.org/jira/browse/AMBARI-17023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17023: Attachment: AMBARI-17023-1.patch > Show only relevant properties based on the status of HAWQ Resource Manager > -- > > Key: AMBARI-17023 > URL: https://issues.apache.org/jira/browse/AMBARI-17023 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-17023-1.patch, AMBARI-17023.patch > > > Show only relevant properties based on the status of HAWQ Resource Manager. > When Yarn mode is enable, only two parameters should be invisible. > hawq_rm_memory_limit_perseg > hawq_rm_nvcore_limit_perseg > When standalone mode is enabled, four parameters should be invisible. what > you list are correct. > hawq_rm_yarn_app_name > hawq_rm_yarn_queue_name > hawq_rm_yarn_scheduler_address > hawq_rm_yarn_address -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17023) Show only relevant properties based on the status of HAWQ Resource Manager
[ https://issues.apache.org/jira/browse/AMBARI-17023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17023: Attachment: AMBARI-17023.patch > Show only relevant properties based on the status of HAWQ Resource Manager > -- > > Key: AMBARI-17023 > URL: https://issues.apache.org/jira/browse/AMBARI-17023 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-17023.patch > > > Show only relevant properties based on the status of HAWQ Resource Manager. > When Yarn mode is enable, only two parameters should be invisible. > hawq_rm_memory_limit_perseg > hawq_rm_nvcore_limit_perseg > When standalone mode is enabled, four parameters should be invisible. what > you list are correct. > hawq_rm_yarn_app_name > hawq_rm_yarn_queue_name > hawq_rm_yarn_scheduler_address > hawq_rm_yarn_address -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17023) Show only relevant properties based on the status of HAWQ Resource Manager
[ https://issues.apache.org/jira/browse/AMBARI-17023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17023: Fix Version/s: 2.4.0 Status: Patch Available (was: Open) > Show only relevant properties based on the status of HAWQ Resource Manager > -- > > Key: AMBARI-17023 > URL: https://issues.apache.org/jira/browse/AMBARI-17023 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > > Show only relevant properties based on the status of HAWQ Resource Manager. > When Yarn mode is enable, only two parameters should be invisible. > hawq_rm_memory_limit_perseg > hawq_rm_nvcore_limit_perseg > When standalone mode is enabled, four parameters should be invisible. what > you list are correct. > hawq_rm_yarn_app_name > hawq_rm_yarn_queue_name > hawq_rm_yarn_scheduler_address > hawq_rm_yarn_address -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17024) Update name of PXF component to PXF Agent
[ https://issues.apache.org/jira/browse/AMBARI-17024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17024: Resolution: Fixed Status: Resolved (was: Patch Available) > Update name of PXF component to PXF Agent > - > > Key: AMBARI-17024 > URL: https://issues.apache.org/jira/browse/AMBARI-17024 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-17024.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17024) Update name of PXF component to PXF Agent
[ https://issues.apache.org/jira/browse/AMBARI-17024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17024: Attachment: AMBARI-17024.patch > Update name of PXF component to PXF Agent > - > > Key: AMBARI-17024 > URL: https://issues.apache.org/jira/browse/AMBARI-17024 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-17024.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17024) Update name of PXF component to PXF Agent
[ https://issues.apache.org/jira/browse/AMBARI-17024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-17024: Fix Version/s: 2.4.0 Status: Patch Available (was: Open) > Update name of PXF component to PXF Agent > - > > Key: AMBARI-17024 > URL: https://issues.apache.org/jira/browse/AMBARI-17024 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-17024) Update name of PXF component to PXF Agent
[ https://issues.apache.org/jira/browse/AMBARI-17024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary reassigned AMBARI-17024: --- Assignee: bhuvnesh chaudhary > Update name of PXF component to PXF Agent > - > > Key: AMBARI-17024 > URL: https://issues.apache.org/jira/browse/AMBARI-17024 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17024) Update name of PXF component to PXF Agent
bhuvnesh chaudhary created AMBARI-17024: --- Summary: Update name of PXF component to PXF Agent Key: AMBARI-17024 URL: https://issues.apache.org/jira/browse/AMBARI-17024 Project: Ambari Issue Type: New Feature Components: stacks Affects Versions: 2.4.0 Reporter: bhuvnesh chaudhary -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17023) Show only relevant properties based on the status of HAWQ Resource Manager
bhuvnesh chaudhary created AMBARI-17023: --- Summary: Show only relevant properties based on the status of HAWQ Resource Manager Key: AMBARI-17023 URL: https://issues.apache.org/jira/browse/AMBARI-17023 Project: Ambari Issue Type: New Feature Components: stacks Affects Versions: 2.4.0 Reporter: bhuvnesh chaudhary Assignee: bhuvnesh chaudhary Show only relevant properties based on the status of HAWQ Resource Manager. When Yarn mode is enable, only two parameters should be invisible. hawq_rm_memory_limit_perseg hawq_rm_nvcore_limit_perseg When standalone mode is enabled, four parameters should be invisible. what you list are correct. hawq_rm_yarn_app_name hawq_rm_yarn_queue_name hawq_rm_yarn_scheduler_address hawq_rm_yarn_address -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
[ https://issues.apache.org/jira/browse/AMBARI-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary resolved AMBARI-16992. - Resolution: Fixed > Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor > - > > Key: AMBARI-16992 > URL: https://issues.apache.org/jira/browse/AMBARI-16992 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-16992-trunk-orig.patch > > > Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
[ https://issues.apache.org/jira/browse/AMBARI-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary reopened AMBARI-16992: - > Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor > - > > Key: AMBARI-16992 > URL: https://issues.apache.org/jira/browse/AMBARI-16992 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-16992-trunk-orig.patch > > > Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16970) Update derivation of hawq_rm_memory_limit_perseg
[ https://issues.apache.org/jira/browse/AMBARI-16970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16970: Resolution: Fixed Assignee: bhuvnesh chaudhary Fix Version/s: 2.4.0 Status: Resolved (was: Patch Available) > Update derivation of hawq_rm_memory_limit_perseg > > > Key: AMBARI-16970 > URL: https://issues.apache.org/jira/browse/AMBARI-16970 > Project: Ambari > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16970-1.patch, AMBARI-16970.patch > > > Update derivation of hawq_rm_memory_limit_perseg. It should be calculated > based on vm.overcommit_ratio, vm.overcommit_memory and the available system > memory. It should also have a default value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16970) Update derivation of hawq_rm_memory_limit_perseg
[ https://issues.apache.org/jira/browse/AMBARI-16970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16970: Attachment: AMBARI-16970.patch > Update derivation of hawq_rm_memory_limit_perseg > > > Key: AMBARI-16970 > URL: https://issues.apache.org/jira/browse/AMBARI-16970 > Project: Ambari > Issue Type: Bug >Reporter: bhuvnesh chaudhary > Attachments: AMBARI-16970.patch > > > Update derivation of hawq_rm_memory_limit_perseg. It should be calculated > based on vm.overcommit_ratio, vm.overcommit_memory and the available system > memory. It should also have a default value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16970) Update derivation of hawq_rm_memory_limit_perseg
bhuvnesh chaudhary created AMBARI-16970: --- Summary: Update derivation of hawq_rm_memory_limit_perseg Key: AMBARI-16970 URL: https://issues.apache.org/jira/browse/AMBARI-16970 Project: Ambari Issue Type: Bug Reporter: bhuvnesh chaudhary Update derivation of hawq_rm_memory_limit_perseg. It should be calculated based on vm.overcommit_ratio, vm.overcommit_memory and the available system memory. It should also have a default value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16936) BP deploy to put default password for hawq_password
[ https://issues.apache.org/jira/browse/AMBARI-16936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16936: Resolution: Fixed Status: Resolved (was: Patch Available) > BP deploy to put default password for hawq_password > --- > > Key: AMBARI-16936 > URL: https://issues.apache.org/jira/browse/AMBARI-16936 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-16936.patch > > > BP deploy to put default password for hawq_password -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16827) expose vm.overcommit_ratio on hawq-sysctl-env
[ https://issues.apache.org/jira/browse/AMBARI-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16827: Resolution: Fixed Status: Resolved (was: Patch Available) > expose vm.overcommit_ratio on hawq-sysctl-env > - > > Key: AMBARI-16827 > URL: https://issues.apache.org/jira/browse/AMBARI-16827 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Attachments: AMBARI-16827-2.patch, AMBARI-16827.patch > > > vm.overcommit_ratio is used for calculation of hawq_rm_memory_limit_perseg. > So, expose it on the UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16917) Use postgres database instead of template1 during service check in HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-16917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16917: Resolution: Fixed Assignee: bhuvnesh chaudhary Status: Resolved (was: Patch Available) > Use postgres database instead of template1 during service check in HAWQ > --- > > Key: AMBARI-16917 > URL: https://issues.apache.org/jira/browse/AMBARI-16917 > Project: Ambari > Issue Type: Improvement > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-16917.patch > > > Use postgres database instead of template1 during service check in HAWQ. > template1 database is used as a default template while creating new > databases, so anything in template1 gets carried over to the new database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-16827) expose vm.overcommit_ratio on hawq-sysctl-env
[ https://issues.apache.org/jira/browse/AMBARI-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary reassigned AMBARI-16827: --- Assignee: bhuvnesh chaudhary > expose vm.overcommit_ratio on hawq-sysctl-env > - > > Key: AMBARI-16827 > URL: https://issues.apache.org/jira/browse/AMBARI-16827 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Attachments: AMBARI-16827-2.patch, AMBARI-16827.patch > > > vm.overcommit_ratio is used for calculation of hawq_rm_memory_limit_perseg. > So, expose it on the UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16936) BP deploy to put default password for hawq_password
[ https://issues.apache.org/jira/browse/AMBARI-16936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16936: Attachment: AMBARI-16936.patch > BP deploy to put default password for hawq_password > --- > > Key: AMBARI-16936 > URL: https://issues.apache.org/jira/browse/AMBARI-16936 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-16936.patch > > > BP deploy to put default password for hawq_password -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16936) BP deploy to put default password for hawq_password
[ https://issues.apache.org/jira/browse/AMBARI-16936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16936: Fix Version/s: 2.4.0 Status: Patch Available (was: Open) > BP deploy to put default password for hawq_password > --- > > Key: AMBARI-16936 > URL: https://issues.apache.org/jira/browse/AMBARI-16936 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-16936.patch > > > BP deploy to put default password for hawq_password -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16936) BP deploy to put default password for hawq_password
bhuvnesh chaudhary created AMBARI-16936: --- Summary: BP deploy to put default password for hawq_password Key: AMBARI-16936 URL: https://issues.apache.org/jira/browse/AMBARI-16936 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.4.0 Reporter: bhuvnesh chaudhary Assignee: bhuvnesh chaudhary Priority: Minor BP deploy to put default password for hawq_password -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16917) Use postgres database instead of template1 during service check in HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-16917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16917: Fix Version/s: 2.4.0 Status: Patch Available (was: Open) > Use postgres database instead of template1 during service check in HAWQ > --- > > Key: AMBARI-16917 > URL: https://issues.apache.org/jira/browse/AMBARI-16917 > Project: Ambari > Issue Type: Improvement > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-16917.patch > > > Use postgres database instead of template1 during service check in HAWQ. > template1 database is used as a default template while creating new > databases, so anything in template1 gets carried over to the new database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16917) Use postgres database instead of template1 during service check in HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-16917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16917: Attachment: AMBARI-16917.patch > Use postgres database instead of template1 during service check in HAWQ > --- > > Key: AMBARI-16917 > URL: https://issues.apache.org/jira/browse/AMBARI-16917 > Project: Ambari > Issue Type: Improvement > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-16917.patch > > > Use postgres database instead of template1 during service check in HAWQ. > template1 database is used as a default template while creating new > databases, so anything in template1 gets carried over to the new database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16917) Use postgres database instead of template1 during service check in HAWQ
bhuvnesh chaudhary created AMBARI-16917: --- Summary: Use postgres database instead of template1 during service check in HAWQ Key: AMBARI-16917 URL: https://issues.apache.org/jira/browse/AMBARI-16917 Project: Ambari Issue Type: Improvement Components: stacks Affects Versions: 2.4.0 Reporter: bhuvnesh chaudhary Priority: Minor Use postgres database instead of template1 during service check in HAWQ. template1 database is used as a default template while creating new databases, so anything in template1 gets carried over to the new database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16827) expose vm.overcommit_ratio on hawq-sysctl-env
[ https://issues.apache.org/jira/browse/AMBARI-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16827: Attachment: AMBARI-16827-2.patch > expose vm.overcommit_ratio on hawq-sysctl-env > - > > Key: AMBARI-16827 > URL: https://issues.apache.org/jira/browse/AMBARI-16827 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary > Attachments: AMBARI-16827-2.patch, AMBARI-16827.patch > > > vm.overcommit_ratio is used for calculation of hawq_rm_memory_limit_perseg. > So, expose it on the UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16827) expose vm.overcommit_ratio on hawq-sysctl-env
[ https://issues.apache.org/jira/browse/AMBARI-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16827: Attachment: AMBARI-16827.patch > expose vm.overcommit_ratio on hawq-sysctl-env > - > > Key: AMBARI-16827 > URL: https://issues.apache.org/jira/browse/AMBARI-16827 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary > Attachments: AMBARI-16827.patch > > > vm.overcommit_ratio is used for calculation of hawq_rm_memory_limit_perseg. > So, expose it on the UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16827) expose vm.overcommit_ratio on hawq-sysctl-env
bhuvnesh chaudhary created AMBARI-16827: --- Summary: expose vm.overcommit_ratio on hawq-sysctl-env Key: AMBARI-16827 URL: https://issues.apache.org/jira/browse/AMBARI-16827 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.4.0 Reporter: bhuvnesh chaudhary vm.overcommit_ratio is used for calculation of hawq_rm_memory_limit_perseg. So, expose it on the UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16800) Hawq password to use !h flag to ensure that its only hidden and no special processing is done for it.
[ https://issues.apache.org/jira/browse/AMBARI-16800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16800: Resolution: Fixed Status: Resolved (was: Patch Available) > Hawq password to use !h flag to ensure that its only hidden and no special > processing is done for it. > - > > Key: AMBARI-16800 > URL: https://issues.apache.org/jira/browse/AMBARI-16800 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16800.patch > > > Hawq password to use !h flag to ensure that its only hidden and no special > processing is done for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16800) Hawq password to use !h flag to ensure that its only hidden and no special processing is done for it.
[ https://issues.apache.org/jira/browse/AMBARI-16800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16800: Fix Version/s: 2.4.0 Status: Patch Available (was: Open) > Hawq password to use !h flag to ensure that its only hidden and no special > processing is done for it. > - > > Key: AMBARI-16800 > URL: https://issues.apache.org/jira/browse/AMBARI-16800 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16800.patch > > > Hawq password to use !h flag to ensure that its only hidden and no special > processing is done for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16786) hawq_standby_address_host property should be removed from configuration if HAWQSTANDBY component does not exist in BP
[ https://issues.apache.org/jira/browse/AMBARI-16786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16786: Resolution: Fixed Status: Resolved (was: Patch Available) > hawq_standby_address_host property should be removed from configuration if > HAWQSTANDBY component does not exist in BP > - > > Key: AMBARI-16786 > URL: https://issues.apache.org/jira/browse/AMBARI-16786 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16786-1.patch, AMBARI-16786-2.patch, > AMBARI-16786.patch > > > hawq_standby_address_host property should be removed from configuration if > HAWQSTANDBY component does not exist in BP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16786) hawq_standby_address_host property should be removed from configuration if HAWQSTANDBY component does not exist in BP
[ https://issues.apache.org/jira/browse/AMBARI-16786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294596#comment-15294596 ] bhuvnesh chaudhary commented on AMBARI-16786: - BlueprintConfigurationProcessTest were successful. The failure is due to a different test Running org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessorTest Tests run: 152, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.962 sec - in org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessorTest Running org.apache.ambari.server.controller.internal.GroupResourceProviderTest > hawq_standby_address_host property should be removed from configuration if > HAWQSTANDBY component does not exist in BP > - > > Key: AMBARI-16786 > URL: https://issues.apache.org/jira/browse/AMBARI-16786 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16786-1.patch, AMBARI-16786-2.patch, > AMBARI-16786.patch > > > hawq_standby_address_host property should be removed from configuration if > HAWQSTANDBY component does not exist in BP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16786) hawq_standby_address_host property should be removed from configuration if HAWQSTANDBY component does not exist in BP
[ https://issues.apache.org/jira/browse/AMBARI-16786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16786: Attachment: AMBARI-16786-2.patch > hawq_standby_address_host property should be removed from configuration if > HAWQSTANDBY component does not exist in BP > - > > Key: AMBARI-16786 > URL: https://issues.apache.org/jira/browse/AMBARI-16786 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16786-1.patch, AMBARI-16786-2.patch, > AMBARI-16786.patch > > > hawq_standby_address_host property should be removed from configuration if > HAWQSTANDBY component does not exist in BP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16786) hawq_standby_address_host property should be removed from configuration if HAWQSTANDBY component does not exist in BP
[ https://issues.apache.org/jira/browse/AMBARI-16786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16786: Attachment: AMBARI-16786-1.patch > hawq_standby_address_host property should be removed from configuration if > HAWQSTANDBY component does not exist in BP > - > > Key: AMBARI-16786 > URL: https://issues.apache.org/jira/browse/AMBARI-16786 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16786-1.patch, AMBARI-16786.patch > > > hawq_standby_address_host property should be removed from configuration if > HAWQSTANDBY component does not exist in BP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16800) Hawq password to use !h flag to ensure that its only hidden and no special processing is done for it.
[ https://issues.apache.org/jira/browse/AMBARI-16800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16800: Attachment: AMBARI-16800.patch > Hawq password to use !h flag to ensure that its only hidden and no special > processing is done for it. > - > > Key: AMBARI-16800 > URL: https://issues.apache.org/jira/browse/AMBARI-16800 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Attachments: AMBARI-16800.patch > > > Hawq password to use !h flag to ensure that its only hidden and no special > processing is done for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16800) Hawq password to use !h flag to ensure that its only hidden and no special processing is done for it.
bhuvnesh chaudhary created AMBARI-16800: --- Summary: Hawq password to use !h flag to ensure that its only hidden and no special processing is done for it. Key: AMBARI-16800 URL: https://issues.apache.org/jira/browse/AMBARI-16800 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.4.0 Reporter: bhuvnesh chaudhary Assignee: bhuvnesh chaudhary Hawq password to use !h flag to ensure that its only hidden and no special processing is done for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16786) hawq_standby_address_host property should be removed from configuration if HAWQSTANDBY component does not exist in BP
[ https://issues.apache.org/jira/browse/AMBARI-16786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16786: Fix Version/s: 2.4.0 Status: Patch Available (was: Open) > hawq_standby_address_host property should be removed from configuration if > HAWQSTANDBY component does not exist in BP > - > > Key: AMBARI-16786 > URL: https://issues.apache.org/jira/browse/AMBARI-16786 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16786.patch > > > hawq_standby_address_host property should be removed from configuration if > HAWQSTANDBY component does not exist in BP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16786) hawq_standby_address_host property should be removed from configuration if HAWQSTANDBY component does not exist in BP
[ https://issues.apache.org/jira/browse/AMBARI-16786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16786: Attachment: AMBARI-16786.patch > hawq_standby_address_host property should be removed from configuration if > HAWQSTANDBY component does not exist in BP > - > > Key: AMBARI-16786 > URL: https://issues.apache.org/jira/browse/AMBARI-16786 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16786.patch > > > hawq_standby_address_host property should be removed from configuration if > HAWQSTANDBY component does not exist in BP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16786) hawq_standby_address_host property should be removed from configuration if HAWQSTANDBY component does not exist in BP
bhuvnesh chaudhary created AMBARI-16786: --- Summary: hawq_standby_address_host property should be removed from configuration if HAWQSTANDBY component does not exist in BP Key: AMBARI-16786 URL: https://issues.apache.org/jira/browse/AMBARI-16786 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.4.0 Reporter: bhuvnesh chaudhary Assignee: bhuvnesh chaudhary hawq_standby_address_host property should be removed from configuration if HAWQSTANDBY component does not exist in BP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16745) Recommend value for hawq_rm_memory_limit_perseg for HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-16745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16745: Resolution: Fixed Status: Resolved (was: Patch Available) > Recommend value for hawq_rm_memory_limit_perseg for HAWQ > > > Key: AMBARI-16745 > URL: https://issues.apache.org/jira/browse/AMBARI-16745 > Project: Ambari > Issue Type: New Feature >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16745.patch > > > Recommend value for hawq_rm_memory_limit_perseg for HAWQ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16754) Next button is disabled on assign master page in Add Hawq Standby wizard
[ https://issues.apache.org/jira/browse/AMBARI-16754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16754: Resolution: Fixed Status: Resolved (was: Patch Available) > Next button is disabled on assign master page in Add Hawq Standby wizard > > > Key: AMBARI-16754 > URL: https://issues.apache.org/jira/browse/AMBARI-16754 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16754.patch > > > Next button is disabled on assign master page in Add Hawq Standby wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16754) Next button is disabled on assign master page in Add Hawq Standby wizard
[ https://issues.apache.org/jira/browse/AMBARI-16754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16754: Attachment: AMBARI-16754.patch > Next button is disabled on assign master page in Add Hawq Standby wizard > > > Key: AMBARI-16754 > URL: https://issues.apache.org/jira/browse/AMBARI-16754 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16754.patch > > > Next button is disabled on assign master page in Add Hawq Standby wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16754) Next button is disabled on assign master page in Add Hawq Standby wizard
[ https://issues.apache.org/jira/browse/AMBARI-16754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16754: Fix Version/s: 2.4.0 Status: Patch Available (was: Open) > Next button is disabled on assign master page in Add Hawq Standby wizard > > > Key: AMBARI-16754 > URL: https://issues.apache.org/jira/browse/AMBARI-16754 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > > Next button is disabled on assign master page in Add Hawq Standby wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16754) Next button is disabled on assign master page in Add Hawq Standby wizard
bhuvnesh chaudhary created AMBARI-16754: --- Summary: Next button is disabled on assign master page in Add Hawq Standby wizard Key: AMBARI-16754 URL: https://issues.apache.org/jira/browse/AMBARI-16754 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.4.0 Reporter: bhuvnesh chaudhary Assignee: bhuvnesh chaudhary Next button is disabled on assign master page in Add Hawq Standby wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16745) Recommend value for hawq_rm_memory_limit_perseg for HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-16745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16745: Fix Version/s: 2.4.0 Status: Patch Available (was: Open) > Recommend value for hawq_rm_memory_limit_perseg for HAWQ > > > Key: AMBARI-16745 > URL: https://issues.apache.org/jira/browse/AMBARI-16745 > Project: Ambari > Issue Type: New Feature >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16745.patch > > > Recommend value for hawq_rm_memory_limit_perseg for HAWQ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16745) Recommend value for hawq_rm_memory_limit_perseg for HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-16745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16745: Attachment: AMBARI-16745.patch > Recommend value for hawq_rm_memory_limit_perseg for HAWQ > > > Key: AMBARI-16745 > URL: https://issues.apache.org/jira/browse/AMBARI-16745 > Project: Ambari > Issue Type: New Feature >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Attachments: AMBARI-16745.patch > > > Recommend value for hawq_rm_memory_limit_perseg for HAWQ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16745) Recommend value for hawq_rm_memory_limit_perseg for HAWQ
bhuvnesh chaudhary created AMBARI-16745: --- Summary: Recommend value for hawq_rm_memory_limit_perseg for HAWQ Key: AMBARI-16745 URL: https://issues.apache.org/jira/browse/AMBARI-16745 Project: Ambari Issue Type: New Feature Affects Versions: 2.4.0 Reporter: bhuvnesh chaudhary Assignee: bhuvnesh chaudhary Recommend value for hawq_rm_memory_limit_perseg for HAWQ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16665) Cache service advisors when stack advisor is loaded
[ https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16665: Assignee: Lav Jain > Cache service advisors when stack advisor is loaded > --- > > Key: AMBARI-16665 > URL: https://issues.apache.org/jira/browse/AMBARI-16665 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Matt >Assignee: Lav Jain >Priority: Minor > > With the current implementation, service advisors for the same service are > loaded multiple times in the stack advisor. > The service advisors should be cached when the stack advisor is loaded and > used where necessary. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16694) Remove unused parameters from hawq-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-16694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16694: Resolution: Fixed Status: Resolved (was: Patch Available) > Remove unused parameters from hawq-site.xml > --- > > Key: AMBARI-16694 > URL: https://issues.apache.org/jira/browse/AMBARI-16694 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.2.0, 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0, 2.4.1 > > Attachments: AMBARI-16694.patch > > > Remove the below unused parameters from hawq-site.xml > - hawq_re_cgroup_hierarchy_name > - hawq_re_cgroup_mount_point > - hawq_re_cpu_enable -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16694) Remove unused parameters from hawq-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-16694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16694: Assignee: bhuvnesh chaudhary Fix Version/s: 2.4.1 2.4.0 Status: Patch Available (was: Open) > Remove unused parameters from hawq-site.xml > --- > > Key: AMBARI-16694 > URL: https://issues.apache.org/jira/browse/AMBARI-16694 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.2.0, 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0, 2.4.1 > > Attachments: AMBARI-16694.patch > > > Remove the below unused parameters from hawq-site.xml > - hawq_re_cgroup_hierarchy_name > - hawq_re_cgroup_mount_point > - hawq_re_cpu_enable -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16694) Remove unused parameters from hawq-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-16694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16694: Attachment: AMBARI-16694.patch > Remove unused parameters from hawq-site.xml > --- > > Key: AMBARI-16694 > URL: https://issues.apache.org/jira/browse/AMBARI-16694 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.2.0, 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0, 2.4.1 > > Attachments: AMBARI-16694.patch > > > Remove the below unused parameters from hawq-site.xml > - hawq_re_cgroup_hierarchy_name > - hawq_re_cgroup_mount_point > - hawq_re_cpu_enable -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16694) Remove unused parameters from hawq-site.xml
bhuvnesh chaudhary created AMBARI-16694: --- Summary: Remove unused parameters from hawq-site.xml Key: AMBARI-16694 URL: https://issues.apache.org/jira/browse/AMBARI-16694 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.2.0, 2.4.0 Reporter: bhuvnesh chaudhary Remove the below unused parameters from hawq-site.xml - hawq_re_cgroup_hierarchy_name - hawq_re_cgroup_mount_point - hawq_re_cpu_enable -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16624) hawq_ssh_exkeys should be a checkbox
[ https://issues.apache.org/jira/browse/AMBARI-16624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16624: Resolution: Fixed Fix Version/s: 2.4.0 Status: Resolved (was: Patch Available) > hawq_ssh_exkeys should be a checkbox > > > Key: AMBARI-16624 > URL: https://issues.apache.org/jira/browse/AMBARI-16624 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.3.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-16624.patch > > > hawq_ssh_exkeys should be a checkbox. Currently it accepts a string. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16386) HAWQ Password handling updated
[ https://issues.apache.org/jira/browse/AMBARI-16386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16386: Resolution: Fixed Fix Version/s: 2.4.0 Status: Resolved (was: Patch Available) > HAWQ Password handling updated > -- > > Key: AMBARI-16386 > URL: https://issues.apache.org/jira/browse/AMBARI-16386 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.3.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16386-2.patch, AMBARI-16386-4.patch, > AMBARI-16386.patch > > > Updated salt used while creating HAWQ user, and also ensured that the > password is treated exactly as entered on the HAWQ config ui. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16386) HAWQ Password handling updated
[
https://issues.apache.org/jira/browse/AMBARI-16386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283147#comment-15283147
]
bhuvnesh chaudhary commented on AMBARI-16386:
-
From: https://builds.apache.org/job/Ambari-trunk-test-patch/6850/console
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12803695/AMBARI-16386-4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6850//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6850//console
This message is automatically generated.
> HAWQ Password handling updated
> --
>
> Key: AMBARI-16386
> URL: https://issues.apache.org/jira/browse/AMBARI-16386
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.3.0
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Attachments: AMBARI-16386-2.patch, AMBARI-16386-4.patch,
> AMBARI-16386.patch
>
>
> Updated salt used while creating HAWQ user, and also ensured that the
> password is treated exactly as entered on the HAWQ config ui.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16386) HAWQ Password handling updated
[ https://issues.apache.org/jira/browse/AMBARI-16386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16386: Attachment: AMBARI-16386-4.patch > HAWQ Password handling updated > -- > > Key: AMBARI-16386 > URL: https://issues.apache.org/jira/browse/AMBARI-16386 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.3.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Attachments: AMBARI-16386-2.patch, AMBARI-16386-4.patch, > AMBARI-16386.patch > > > Updated salt used while creating HAWQ user, and also ensured that the > password is treated exactly as entered on the HAWQ config ui. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16624) hawq_ssh_exkeys should be a checkbox
[ https://issues.apache.org/jira/browse/AMBARI-16624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16624: Attachment: AMBARI-16624.patch > hawq_ssh_exkeys should be a checkbox > > > Key: AMBARI-16624 > URL: https://issues.apache.org/jira/browse/AMBARI-16624 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.3.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Attachments: AMBARI-16624.patch > > > hawq_ssh_exkeys should be a checkbox. Currently it accepts a string. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-16624) hawq_ssh_exkeys should be a checkbox
[ https://issues.apache.org/jira/browse/AMBARI-16624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary reassigned AMBARI-16624: --- Assignee: bhuvnesh chaudhary > hawq_ssh_exkeys should be a checkbox > > > Key: AMBARI-16624 > URL: https://issues.apache.org/jira/browse/AMBARI-16624 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.3.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > > hawq_ssh_exkeys should be a checkbox. Currently it accepts a string. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16624) hawq_ssh_exkeys should be a checkbox
bhuvnesh chaudhary created AMBARI-16624: --- Summary: hawq_ssh_exkeys should be a checkbox Key: AMBARI-16624 URL: https://issues.apache.org/jira/browse/AMBARI-16624 Project: Ambari Issue Type: Improvement Affects Versions: 2.3.0 Reporter: bhuvnesh chaudhary Priority: Minor hawq_ssh_exkeys should be a checkbox. Currently it accepts a string. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16386) HAWQ Password handling updated
[ https://issues.apache.org/jira/browse/AMBARI-16386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16386: Attachment: AMBARI-16386-3.patch > HAWQ Password handling updated > -- > > Key: AMBARI-16386 > URL: https://issues.apache.org/jira/browse/AMBARI-16386 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.3.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Attachments: AMBARI-16386-2.patch, AMBARI-16386-3.patch, > AMBARI-16386.patch > > > Updated salt used while creating HAWQ user, and also ensured that the > password is treated exactly as entered on the HAWQ config ui. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16386) HAWQ Password handling updated
[ https://issues.apache.org/jira/browse/AMBARI-16386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16386: Attachment: AMBARI-16386-2.patch > HAWQ Password handling updated > -- > > Key: AMBARI-16386 > URL: https://issues.apache.org/jira/browse/AMBARI-16386 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.3.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Attachments: AMBARI-16386-2.patch, AMBARI-16386.patch > > > Updated salt used while creating HAWQ user, and also ensured that the > password is treated exactly as entered on the HAWQ config ui. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16386) HAWQ Password handling updated
[ https://issues.apache.org/jira/browse/AMBARI-16386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16386: Assignee: bhuvnesh chaudhary Status: Patch Available (was: Open) > HAWQ Password handling updated > -- > > Key: AMBARI-16386 > URL: https://issues.apache.org/jira/browse/AMBARI-16386 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.3.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Attachments: AMBARI-16386.patch > > > Updated salt used while creating HAWQ user, and also ensured that the > password is treated exactly as entered on the HAWQ config ui. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16386) HAWQ Password handling updated
bhuvnesh chaudhary created AMBARI-16386: --- Summary: HAWQ Password handling updated Key: AMBARI-16386 URL: https://issues.apache.org/jira/browse/AMBARI-16386 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.3.0 Reporter: bhuvnesh chaudhary Attachments: AMBARI-16386.patch Updated salt used while creating HAWQ user, and also ensured that the password is treated exactly as entered on the HAWQ config ui. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16386) HAWQ Password handling updated
[ https://issues.apache.org/jira/browse/AMBARI-16386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16386: Attachment: AMBARI-16386.patch > HAWQ Password handling updated > -- > > Key: AMBARI-16386 > URL: https://issues.apache.org/jira/browse/AMBARI-16386 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.3.0 >Reporter: bhuvnesh chaudhary > Attachments: AMBARI-16386.patch > > > Updated salt used while creating HAWQ user, and also ensured that the > password is treated exactly as entered on the HAWQ config ui. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16024: Resolution: Fixed Status: Resolved (was: Patch Available) > Remove performing service check during "Remove Standby Wizard" > -- > > Key: AMBARI-16024 > URL: https://issues.apache.org/jira/browse/AMBARI-16024 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.3.0 > > Attachments: AMBARI-16024-1.patch, AMBARI-16024.patch > > > Users will need to remove the HAWQ Standby Master using "Remove Standby > Wizard" after enabling HDFS HA. > So the service check may fail during the wizard as the HAWQ catalog might be > still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16191) HAWQ Configuration should be updated whenever Namenode is being moved
[ https://issues.apache.org/jira/browse/AMBARI-16191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16191: Resolution: Fixed Status: Resolved (was: Patch Available) > HAWQ Configuration should be updated whenever Namenode is being moved > - > > Key: AMBARI-16191 > URL: https://issues.apache.org/jira/browse/AMBARI-16191 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16191.patch > > > HAWQ Configuration should be updated whenever Namenode is being moved using > the move namenode wizard. > Parameters which should be updated > Case 1: HDFS HA > hdfs-client parameters under HAWQ service > dfs.namenode.rpc-address.. > dfs.namenode.http-address.. > Case 2: Non HA HDFS > hawq-site parmeters under HAWQ service > hawq_dfs_url -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16191) HAWQ Configuration should be updated whenever Namenode is being moved
[ https://issues.apache.org/jira/browse/AMBARI-16191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16191: Fix Version/s: 2.4.0 Affects Version/s: (was: 2.3.0) 2.4.0 Status: Patch Available (was: Open) > HAWQ Configuration should be updated whenever Namenode is being moved > - > > Key: AMBARI-16191 > URL: https://issues.apache.org/jira/browse/AMBARI-16191 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.4.0 > > Attachments: AMBARI-16191.patch > > > HAWQ Configuration should be updated whenever Namenode is being moved using > the move namenode wizard. > Parameters which should be updated > Case 1: HDFS HA > hdfs-client parameters under HAWQ service > dfs.namenode.rpc-address.. > dfs.namenode.http-address.. > Case 2: Non HA HDFS > hawq-site parmeters under HAWQ service > hawq_dfs_url -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16191) HAWQ Configuration should be updated whenever Namenode is being moved
bhuvnesh chaudhary created AMBARI-16191: --- Summary: HAWQ Configuration should be updated whenever Namenode is being moved Key: AMBARI-16191 URL: https://issues.apache.org/jira/browse/AMBARI-16191 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.3.0 Reporter: bhuvnesh chaudhary Assignee: bhuvnesh chaudhary HAWQ Configuration should be updated whenever Namenode is being moved using the move namenode wizard. Parameters which should be updated Case 1: HDFS HA hdfs-client parameters under HAWQ service dfs.namenode.rpc-address.. dfs.namenode.http-address.. Case 2: Non HA HDFS hawq-site parmeters under HAWQ service hawq_dfs_url -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16172) HAWQ Configuration should be updated whenever Namenode is being moved.
[ https://issues.apache.org/jira/browse/AMBARI-16172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16172: Attachment: AMBARI-16172-branch-2.2.patch > HAWQ Configuration should be updated whenever Namenode is being moved. > -- > > Key: AMBARI-16172 > URL: https://issues.apache.org/jira/browse/AMBARI-16172 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.2.0 > > Attachments: AMBARI-16172-branch-2.2.patch > > > HAWQ Configuration should be updated whenever Namenode is being moved using > the move namenode wizard. > Parameters which should be updated > Case 1: HDFS HA > hdfs-client parameters under HAWQ service > dfs.namenode.rpc-address.. > dfs.namenode.http-address.. > Case 2: Non HA HDFS > hawq-site parmeters under HAWQ service > hawq_dfs_url -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16172) HAWQ Configuration should be updated whenever Namenode is being moved.
[ https://issues.apache.org/jira/browse/AMBARI-16172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16172: Attachment: (was: AMBARI-16172-branch-2.2.patch) > HAWQ Configuration should be updated whenever Namenode is being moved. > -- > > Key: AMBARI-16172 > URL: https://issues.apache.org/jira/browse/AMBARI-16172 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.2.0 > > > HAWQ Configuration should be updated whenever Namenode is being moved using > the move namenode wizard. > Parameters which should be updated > Case 1: HDFS HA > hdfs-client parameters under HAWQ service > dfs.namenode.rpc-address.. > dfs.namenode.http-address.. > Case 2: Non HA HDFS > hawq-site parmeters under HAWQ service > hawq_dfs_url -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16172) HAWQ Configuration should be updated whenever Namenode is being moved.
[ https://issues.apache.org/jira/browse/AMBARI-16172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16172: Attachment: AMBARI-16172-branch-2.2.patch > HAWQ Configuration should be updated whenever Namenode is being moved. > -- > > Key: AMBARI-16172 > URL: https://issues.apache.org/jira/browse/AMBARI-16172 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.2.0 > > Attachments: AMBARI-16172-branch-2.2.patch > > > HAWQ Configuration should be updated whenever Namenode is being moved using > the move namenode wizard. > Parameters which should be updated > Case 1: HDFS HA > hdfs-client parameters under HAWQ service > dfs.namenode.rpc-address.. > dfs.namenode.http-address.. > Case 2: Non HA HDFS > hawq-site parmeters under HAWQ service > hawq_dfs_url -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16172) HAWQ Configuration should be updated whenever Namenode is being moved.
bhuvnesh chaudhary created AMBARI-16172: --- Summary: HAWQ Configuration should be updated whenever Namenode is being moved. Key: AMBARI-16172 URL: https://issues.apache.org/jira/browse/AMBARI-16172 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.2.0 Reporter: bhuvnesh chaudhary Assignee: bhuvnesh chaudhary HAWQ Configuration should be updated whenever Namenode is being moved using the move namenode wizard. Parameters which should be updated Case 1: HDFS HA hdfs-client parameters under HAWQ service dfs.namenode.rpc-address.. dfs.namenode.http-address.. Case 2: Non HA HDFS hawq-site parmeters under HAWQ service hawq_dfs_url -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16172) HAWQ Configuration should be updated whenever Namenode is being moved.
[ https://issues.apache.org/jira/browse/AMBARI-16172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16172: Fix Version/s: 2.2.0 Status: Patch Available (was: Open) > HAWQ Configuration should be updated whenever Namenode is being moved. > -- > > Key: AMBARI-16172 > URL: https://issues.apache.org/jira/browse/AMBARI-16172 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.2.0 > > > HAWQ Configuration should be updated whenever Namenode is being moved using > the move namenode wizard. > Parameters which should be updated > Case 1: HDFS HA > hdfs-client parameters under HAWQ service > dfs.namenode.rpc-address.. > dfs.namenode.http-address.. > Case 2: Non HA HDFS > hawq-site parmeters under HAWQ service > hawq_dfs_url -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252680#comment-15252680 ] bhuvnesh chaudhary commented on AMBARI-16024: - In case of Non-HA we might not see the problem listed in the jira but my above comment describes the other problem which we see because of segments not being registered early enough. What you mentioned, in general service check is a good thing, i agree with that. > Remove performing service check during "Remove Standby Wizard" > -- > > Key: AMBARI-16024 > URL: https://issues.apache.org/jira/browse/AMBARI-16024 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.3.0 > > Attachments: AMBARI-16024.patch > > > Users will need to remove the HAWQ Standby Master using "Remove Standby > Wizard" after enabling HDFS HA. > So the service check may fail during the wizard as the HAWQ catalog might be > still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252647#comment-15252647 ] bhuvnesh chaudhary commented on AMBARI-16024: - Also, we do execute the service check as part of the api calling start, so often it happens that the segments have not registered and due to which service check fails, so we should not do it here in my opinion. We can definitely add the service check but we should find out a way to identify the right time to run the service check. > Remove performing service check during "Remove Standby Wizard" > -- > > Key: AMBARI-16024 > URL: https://issues.apache.org/jira/browse/AMBARI-16024 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.3.0 > > Attachments: AMBARI-16024.patch > > > Users will need to remove the HAWQ Standby Master using "Remove Standby > Wizard" after enabling HDFS HA. > So the service check may fail during the wizard as the HAWQ catalog might be > still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16024: Fix Version/s: 2.3.0 > Remove performing service check during "Remove Standby Wizard" > -- > > Key: AMBARI-16024 > URL: https://issues.apache.org/jira/browse/AMBARI-16024 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.3.0 > > Attachments: AMBARI-16024.patch > > > Users will need to remove the HAWQ Standby Master using "Remove Standby > Wizard" after enabling HDFS HA. > So the service check may fail during the wizard as the HAWQ catalog might be > still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16024: Affects Version/s: 2.2.0 > Remove performing service check during "Remove Standby Wizard" > -- > > Key: AMBARI-16024 > URL: https://issues.apache.org/jira/browse/AMBARI-16024 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.3.0 > > Attachments: AMBARI-16024.patch > > > Users will need to remove the HAWQ Standby Master using "Remove Standby > Wizard" after enabling HDFS HA. > So the service check may fail during the wizard as the HAWQ catalog might be > still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary reassigned AMBARI-16024: --- Assignee: bhuvnesh chaudhary > Remove performing service check during "Remove Standby Wizard" > -- > > Key: AMBARI-16024 > URL: https://issues.apache.org/jira/browse/AMBARI-16024 > Project: Ambari > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Attachments: AMBARI-16024.patch > > > Users will need to remove the HAWQ Standby Master using "Remove Standby > Wizard" after enabling HDFS HA. > So the service check may fail during the wizard as the HAWQ catalog might be > still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
bhuvnesh chaudhary created AMBARI-16024: --- Summary: Remove performing service check during "Remove Standby Wizard" Key: AMBARI-16024 URL: https://issues.apache.org/jira/browse/AMBARI-16024 Project: Ambari Issue Type: Bug Reporter: bhuvnesh chaudhary Attachments: AMBARI-16024.patch Users will need to remove the HAWQ Standby Master using "Remove Standby Wizard" after enabling HDFS HA. So the service check may fail during the wizard as the HAWQ catalog might be still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16024: Attachment: AMBARI-16024.patch > Remove performing service check during "Remove Standby Wizard" > -- > > Key: AMBARI-16024 > URL: https://issues.apache.org/jira/browse/AMBARI-16024 > Project: Ambari > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Attachments: AMBARI-16024.patch > > > Users will need to remove the HAWQ Standby Master using "Remove Standby > Wizard" after enabling HDFS HA. > So the service check may fail during the wizard as the HAWQ catalog might be > still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16024: Status: Patch Available (was: Open) > Remove performing service check during "Remove Standby Wizard" > -- > > Key: AMBARI-16024 > URL: https://issues.apache.org/jira/browse/AMBARI-16024 > Project: Ambari > Issue Type: Bug >Reporter: bhuvnesh chaudhary > Attachments: AMBARI-16024.patch > > > Users will need to remove the HAWQ Standby Master using "Remove Standby > Wizard" after enabling HDFS HA. > So the service check may fail during the wizard as the HAWQ catalog might be > still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15930) hawq init master fails to syncup hawq-site xml if there is a segment host down
[ https://issues.apache.org/jira/browse/AMBARI-15930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15244057#comment-15244057 ] bhuvnesh chaudhary commented on AMBARI-15930: - Committed to trunk, 2.2.2 and 2.2. > hawq init master fails to syncup hawq-site xml if there is a segment host down > -- > > Key: AMBARI-15930 > URL: https://issues.apache.org/jira/browse/AMBARI-15930 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.2 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.2.2 > > Attachments: AMBARI-15930-branch-2.2.patch, AMBARI-15930.patch > > > 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] (AMBARI-15930) hawq init master fails to syncup hawq-site xml if there is a segment host down
[ https://issues.apache.org/jira/browse/AMBARI-15930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-15930: Resolution: Fixed Status: Resolved (was: Patch Available) > hawq init master fails to syncup hawq-site xml if there is a segment host down > -- > > Key: AMBARI-15930 > URL: https://issues.apache.org/jira/browse/AMBARI-15930 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.2 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.2.2 > > Attachments: AMBARI-15930-branch-2.2.patch, AMBARI-15930.patch > > > 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)
