[jira] [Updated] (AMBARI-19764) yarn.min.container.size is read incorrectly on first load of the Hive config page
[ https://issues.apache.org/jira/browse/AMBARI-19764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19764: --- Status: Patch Available (was: Open) > yarn.min.container.size is read incorrectly on first load of the Hive config > page > - > > Key: AMBARI-19764 > URL: https://issues.apache.org/jira/browse/AMBARI-19764 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Siddharth Seth >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19764.patch > > > The value is read in as 1024, even though min_container_size is 12GB on the > cluster. Impact: The values for minNodes, maxNodes, minConcurrency, > maxConcurrency on the UI will be incorrect. User selects an incorrect value > and the cluster will not start. > When various llap sliders are moved - the correct value of 12GB is read. > The stack advisor code needs to be modified to take advantage of AMBARI-19701 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19764) yarn.min.container.size is read incorrectly on first load of the Hive config page
[ https://issues.apache.org/jira/browse/AMBARI-19764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19764: --- Attachment: AMBARI-19764.patch > yarn.min.container.size is read incorrectly on first load of the Hive config > page > - > > Key: AMBARI-19764 > URL: https://issues.apache.org/jira/browse/AMBARI-19764 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Siddharth Seth >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19764.patch > > > The value is read in as 1024, even though min_container_size is 12GB on the > cluster. Impact: The values for minNodes, maxNodes, minConcurrency, > maxConcurrency on the UI will be incorrect. User selects an incorrect value > and the cluster will not start. > When various llap sliders are moved - the correct value of 12GB is read. > The stack advisor code needs to be modified to take advantage of AMBARI-19701 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19764) yarn.min.container.size is read incorrectly on first load of the Hive config page
Sumit Mohanty created AMBARI-19764: -- Summary: yarn.min.container.size is read incorrectly on first load of the Hive config page Key: AMBARI-19764 URL: https://issues.apache.org/jira/browse/AMBARI-19764 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.5.0 Reporter: Siddharth Seth Assignee: Sumit Mohanty Priority: Critical Fix For: 2.5.0 Attachments: AMBARI-19764.patch The value is read in as 1024, even though min_container_size is 12GB on the cluster. Impact: The values for minNodes, maxNodes, minConcurrency, maxConcurrency on the UI will be incorrect. User selects an incorrect value and the cluster will not start. When various llap sliders are moved - the correct value of 12GB is read. The stack advisor code needs to be modified to take advantage of AMBARI-19701 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19762) Kerberizing PERF cluster fails since cannot find principal name config in dummy.py
[ https://issues.apache.org/jira/browse/AMBARI-19762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843803#comment-15843803 ] Hudson commented on AMBARI-19762: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6578 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6578/]) AMBARI-19762. Kerberizing PERF cluster fails since cannot find principal (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=50403914c7a092f6e66726b3bf2331be13625f71]) * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHDFS/package/scripts/zkfc_slave.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEYARN/metainfo.xml > Kerberizing PERF cluster fails since cannot find principal name config in > dummy.py > -- > > Key: AMBARI-19762 > URL: https://issues.apache.org/jira/browse/AMBARI-19762 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > > STR: > Install Ambari 2.5.0 on GCE > Install PERF 1.0 stack with all services > Kerberize the cluster > Start services > Fails on History Server and ZKFC. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19762) Kerberizing PERF cluster fails since cannot find principal name config in dummy.py
[ https://issues.apache.org/jira/browse/AMBARI-19762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843799#comment-15843799 ] Hudson commented on AMBARI-19762: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #830 (See [https://builds.apache.org/job/Ambari-branch-2.5/830/]) AMBARI-19762. Kerberizing PERF cluster fails since cannot find principal (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e273668b74cf5f3dd30cb7e4c7ac282e1bc62b39]) * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEYARN/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHDFS/package/scripts/zkfc_slave.py > Kerberizing PERF cluster fails since cannot find principal name config in > dummy.py > -- > > Key: AMBARI-19762 > URL: https://issues.apache.org/jira/browse/AMBARI-19762 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > > STR: > Install Ambari 2.5.0 on GCE > Install PERF 1.0 stack with all services > Kerberize the cluster > Start services > Fails on History Server and ZKFC. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-14023) Phoenix command line tool support
[
https://issues.apache.org/jira/browse/AMBARI-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843794#comment-15843794
]
Nick Dimiduk commented on AMBARI-14023:
---
The above comments are clearly unrelated. If there's no patch attached I have
no patch.
> Phoenix command line tool support
> -
>
> Key: AMBARI-14023
> URL: https://issues.apache.org/jira/browse/AMBARI-14023
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
>Affects Versions: 2.2.0
>Reporter: Nick Dimiduk
> Fix For: 2.5.0
>
>
> Phoenix client scripts appear to be installed where ever HBase client is
> installed. However, those scripts are not available in the path, a la
> {{/usr/bin/hbase}} is available in the path. The user must manually:
> - specify JAVA_HOME
> - place java in the path
> - invoke sqlline.py via pull path specification
> - explicitly provide hbase connection details
> A script in {{/usr/bin}} should:
> - consume in ambari provided JAVA_HOME and java
> - provide sqlline.py in the path
> - use cluster connection details as default when no connection information
> is provided on the command line
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19761) HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'.
[ https://issues.apache.org/jira/browse/AMBARI-19761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843789#comment-15843789 ] Hudson commented on AMBARI-19761: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6577 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6577/]) AMBARI-19761. HSI start fails after Ambari upgrade with Unrecognized (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=771c9c011b3ea00e4ad0171b04bd851c7ee74ee0]) * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py > HSI start fails after Ambari upgrade with Unrecognized option: > '--skiphadoopversion' and '--skiphbasecp'. > - > > Key: AMBARI-19761 > URL: https://issues.apache.org/jira/browse/AMBARI-19761 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19761.patch > > > ' --skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP > 2.6 > *Requirement:* > Add it only if we have HDP 2.6 and onwards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19743) Agent bootstrapping fails for non-root agent user
[
https://issues.apache.org/jira/browse/AMBARI-19743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843788#comment-15843788
]
Hudson commented on AMBARI-19743:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6577 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6577/])
AMBARI-19743. Agent registration fails with non-root agent user (Attila
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0e8c966d20b895442ea461ce488dcb9aae4d8638])
* (edit) ambari-server/src/main/python/bootstrap.py
> Agent bootstrapping fails for non-root agent user
> -
>
> Key: AMBARI-19743
> URL: https://issues.apache.org/jira/browse/AMBARI-19743
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19743.patch
>
>
> STR:
> 1. Create custom agent user, setup {{sudoers}}
> 2. Try to create cluster via wizard
> Result: agent registration fails with
> {noformat}
> ln: creating symbolic link `/usr/bin//ambari-python-wrap': Permission denied
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19743) Agent bootstrapping fails for non-root agent user
[
https://issues.apache.org/jira/browse/AMBARI-19743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843784#comment-15843784
]
Hudson commented on AMBARI-19743:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #829 (See
[https://builds.apache.org/job/Ambari-branch-2.5/829/])
AMBARI-19743. Agent registration fails with non-root agent user (Attila
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4a2c24627205b459ff2ec2b874a2311957df8369])
* (edit) ambari-server/src/main/python/bootstrap.py
> Agent bootstrapping fails for non-root agent user
> -
>
> Key: AMBARI-19743
> URL: https://issues.apache.org/jira/browse/AMBARI-19743
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19743.patch
>
>
> STR:
> 1. Create custom agent user, setup {{sudoers}}
> 2. Try to create cluster via wizard
> Result: agent registration fails with
> {noformat}
> ln: creating symbolic link `/usr/bin//ambari-python-wrap': Permission denied
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19761) HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'.
[ https://issues.apache.org/jira/browse/AMBARI-19761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843785#comment-15843785 ] Hudson commented on AMBARI-19761: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #829 (See [https://builds.apache.org/job/Ambari-branch-2.5/829/]) AMBARI-19761. HSI start fails after Ambari upgrade with Unrecognized (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=80636b9009b5c331e41dc8653ac7098eac897418]) * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py > HSI start fails after Ambari upgrade with Unrecognized option: > '--skiphadoopversion' and '--skiphbasecp'. > - > > Key: AMBARI-19761 > URL: https://issues.apache.org/jira/browse/AMBARI-19761 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19761.patch > > > ' --skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP > 2.6 > *Requirement:* > Add it only if we have HDP 2.6 and onwards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19762) Kerberizing PERF cluster fails since cannot find principal name config in dummy.py
[ https://issues.apache.org/jira/browse/AMBARI-19762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle resolved AMBARI-19762. -- Resolution: Fixed Pushed to 2.5 and trunk. > Kerberizing PERF cluster fails since cannot find principal name config in > dummy.py > -- > > Key: AMBARI-19762 > URL: https://issues.apache.org/jira/browse/AMBARI-19762 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > > STR: > Install Ambari 2.5.0 on GCE > Install PERF 1.0 stack with all services > Kerberize the cluster > Start services > Fails on History Server and ZKFC. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19763) Workflow Manager View : Separate log file into its own directory similar to other views
[
https://issues.apache.org/jira/browse/AMBARI-19763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843779#comment-15843779
]
Hadoop QA commented on AMBARI-19763:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849793/AMBARI-19763.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10308//console
This message is automatically generated.
> Workflow Manager View : Separate log file into its own directory similar to
> other views
> ---
>
> Key: AMBARI-19763
> URL: https://issues.apache.org/jira/browse/AMBARI-19763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-19763.patch
>
>
> Workflow manager view logs entries are currently in the ambari-server.log.
> It should be separated into its own folder under /var/log/ambari-server
> similar to the other views.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19743) Agent bootstrapping fails for non-root agent user
[
https://issues.apache.org/jira/browse/AMBARI-19743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-19743:
---
Resolution: Fixed
Fix Version/s: (was: 3.0.0)
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> Agent bootstrapping fails for non-root agent user
> -
>
> Key: AMBARI-19743
> URL: https://issues.apache.org/jira/browse/AMBARI-19743
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19743.patch
>
>
> STR:
> 1. Create custom agent user, setup {{sudoers}}
> 2. Try to create cluster via wizard
> Result: agent registration fails with
> {noformat}
> ln: creating symbolic link `/usr/bin//ambari-python-wrap': Permission denied
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19761) HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'.
[ https://issues.apache.org/jira/browse/AMBARI-19761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19761: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > HSI start fails after Ambari upgrade with Unrecognized option: > '--skiphadoopversion' and '--skiphbasecp'. > - > > Key: AMBARI-19761 > URL: https://issues.apache.org/jira/browse/AMBARI-19761 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19761.patch > > > ' --skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP > 2.6 > *Requirement:* > Add it only if we have HDP 2.6 and onwards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19763) Workflow Manager View : Separate log file into its own directory similar to other views
[ https://issues.apache.org/jira/browse/AMBARI-19763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19763: Attachment: AMBARI-19763.patch > Workflow Manager View : Separate log file into its own directory similar to > other views > --- > > Key: AMBARI-19763 > URL: https://issues.apache.org/jira/browse/AMBARI-19763 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-19763.patch > > > Workflow manager view logs entries are currently in the ambari-server.log. > It should be separated into its own folder under /var/log/ambari-server > similar to the other views. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19763) Workflow Manager View : Separate log file into its own directory similar to other views
[ https://issues.apache.org/jira/browse/AMBARI-19763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19763: Fix Version/s: 2.5.0 Status: Patch Available (was: In Progress) > Workflow Manager View : Separate log file into its own directory similar to > other views > --- > > Key: AMBARI-19763 > URL: https://issues.apache.org/jira/browse/AMBARI-19763 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-19763.patch > > > Workflow manager view logs entries are currently in the ambari-server.log. > It should be separated into its own folder under /var/log/ambari-server > similar to the other views. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19763) Workflow Manager View : Separate log file into its own directory similar to other views
Sangeeta Ravindran created AMBARI-19763: --- Summary: Workflow Manager View : Separate log file into its own directory similar to other views Key: AMBARI-19763 URL: https://issues.apache.org/jira/browse/AMBARI-19763 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran Workflow manager view logs entries are currently in the ambari-server.log. It should be separated into its own folder under /var/log/ambari-server similar to the other views. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19761) HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'.
[ https://issues.apache.org/jira/browse/AMBARI-19761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843754#comment-15843754 ] Sumit Mohanty commented on AMBARI-19761: LGTM, +1 > HSI start fails after Ambari upgrade with Unrecognized option: > '--skiphadoopversion' and '--skiphbasecp'. > - > > Key: AMBARI-19761 > URL: https://issues.apache.org/jira/browse/AMBARI-19761 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19761.patch > > > ' --skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP > 2.6 > *Requirement:* > Add it only if we have HDP 2.6 and onwards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19762) Kerberizing PERF cluster fails since cannot find principal name config in dummy.py
Madhuvanthi Radhakrishnan created AMBARI-19762: -- Summary: Kerberizing PERF cluster fails since cannot find principal name config in dummy.py Key: AMBARI-19762 URL: https://issues.apache.org/jira/browse/AMBARI-19762 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan STR: Install Ambari 2.5.0 on GCE Install PERF 1.0 stack with all services Kerberize the cluster Start services Fails on History Server and ZKFC. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19758) Post Ambari upgrade AMS config properties changes are marking HDFS/YARN/Hive/HBase with restart required
[
https://issues.apache.org/jira/browse/AMBARI-19758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843735#comment-15843735
]
Hadoop QA commented on AMBARI-19758:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849770/AMBARI-19758.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10306//console
This message is automatically generated.
> Post Ambari upgrade AMS config properties changes are marking
> HDFS/YARN/Hive/HBase with restart required
>
>
> Key: AMBARI-19758
> URL: https://issues.apache.org/jira/browse/AMBARI-19758
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19758.patch
>
>
> Deploy Ambari-2.4 and upgrade to Ambari-2.5. Noticed that all core services
> are marked with restart required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19759) Fix Spark2 service string
[ https://issues.apache.org/jira/browse/AMBARI-19759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843737#comment-15843737 ] Hudson commented on AMBARI-19759: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #828 (See [https://builds.apache.org/job/Ambari-branch-2.5/828/]) AMBARI-19759. Fix Spark2 service description string (Bikas Saha via (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=094e7ae4c3f691f05b516c86a7892411fd00d4ee]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/metainfo.xml > Fix Spark2 service string > - > > Key: AMBARI-19759 > URL: https://issues.apache.org/jira/browse/AMBARI-19759 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.5.0 > > Attachments: AMBARI-19759.1.patch > > > Unnecessarily mentions 2.1 etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19761) HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'.
[
https://issues.apache.org/jira/browse/AMBARI-19761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843727#comment-15843727
]
Swapan Shridhar commented on AMBARI-19761:
--
[~sumitmohanty] | [~afernandez] Patch for review : [^AMBARI-19761.patch]
Tested on HDP 2.5 and HDP 2.6.
*HDP 2.5: command formed:*
{code}
cmd = /usr/hdp/current/hive-server2-hive2/bin/hive --service llap --instances
1 --slider-am-container-mb 2560 --size 5120m --cache 2560m --xmx 2048m
--loglevel INFO --output
/var/lib/ambari-agent/tmp/llap-slider2017-01-28_00-11-40
{code}
*HDP 2.6: command formed:*
{code}
/usr/hdp/current/hive-server2-hive2/bin/hive --service llap --instances 2
--slider-am-container-mb 1024 --size 11264m --cache 8192m --xmx 2457m
--loglevel INFO --output
/var/lib/ambari-agent/tmp/llap-slider2017-01-28_00-40-11 --slider-placement 0
--skiphadoopversion --skiphbasecp
{code}
> HSI start fails after Ambari upgrade with Unrecognized option:
> '--skiphadoopversion' and '--skiphbasecp'.
> -
>
> Key: AMBARI-19761
> URL: https://issues.apache.org/jira/browse/AMBARI-19761
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19761.patch
>
>
> ' --skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP
> 2.6
> *Requirement:*
> Add it only if we have HDP 2.6 and onwards.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-19761) HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'.
[
https://issues.apache.org/jira/browse/AMBARI-19761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843727#comment-15843727
]
Swapan Shridhar edited comment on AMBARI-19761 at 1/28/17 12:48 AM:
[~sumitmohanty] | [~afernandez] Patch for review : [^AMBARI-19761.patch]
Tested on HDP 2.5 and HDP 2.6.
*HDP 2.5: command formed:*
{code}
cmd = /usr/hdp/current/hive-server2-hive2/bin/hive --service llap --instances
1 --slider-am-container-mb 2560 --size 5120m --cache 2560m --xmx 2048m
--loglevel INFO --output
/var/lib/ambari-agent/tmp/llap-slider2017-01-28_00-11-40
{code}
*HDP 2.6: command formed:*
{code}
/usr/hdp/current/hive-server2-hive2/bin/hive --service llap --instances 2
--slider-am-container-mb 1024 --size 11264m --cache 8192m --xmx 2457m
--loglevel INFO --output
/var/lib/ambari-agent/tmp/llap-slider2017-01-28_00-40-11 --slider-placement 0
--skiphadoopversion --skiphbasecp
{code}
was (Author: swapanshridhar):
[~sumitmohanty] | [~afernandez] Patch for review : [^AMBARI-19761.patch]
Tested on HDP 2.5 and HDP 2.6.
*HDP 2.5: command formed:*
{code}
cmd = /usr/hdp/current/hive-server2-hive2/bin/hive --service llap --instances
1 --slider-am-container-mb 2560 --size 5120m --cache 2560m --xmx 2048m
--loglevel INFO --output
/var/lib/ambari-agent/tmp/llap-slider2017-01-28_00-11-40
{code}
*HDP 2.6: command formed:*
{code}
/usr/hdp/current/hive-server2-hive2/bin/hive --service llap --instances 2
--slider-am-container-mb 1024 --size 11264m --cache 8192m --xmx 2457m
--loglevel INFO --output
/var/lib/ambari-agent/tmp/llap-slider2017-01-28_00-40-11 --slider-placement 0
--skiphadoopversion --skiphbasecp
{code}
> HSI start fails after Ambari upgrade with Unrecognized option:
> '--skiphadoopversion' and '--skiphbasecp'.
> -
>
> Key: AMBARI-19761
> URL: https://issues.apache.org/jira/browse/AMBARI-19761
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19761.patch
>
>
> ' --skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP
> 2.6
> *Requirement:*
> Add it only if we have HDP 2.6 and onwards.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19761) HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'.
[ https://issues.apache.org/jira/browse/AMBARI-19761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19761: - Status: Patch Available (was: In Progress) > HSI start fails after Ambari upgrade with Unrecognized option: > '--skiphadoopversion' and '--skiphbasecp'. > - > > Key: AMBARI-19761 > URL: https://issues.apache.org/jira/browse/AMBARI-19761 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19761.patch > > > ' --skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP > 2.6 > *Requirement:* > Add it only if we have HDP 2.6 and onwards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19761) HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'.
[ https://issues.apache.org/jira/browse/AMBARI-19761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19761: - Attachment: AMBARI-19761.patch > HSI start fails after Ambari upgrade with Unrecognized option: > '--skiphadoopversion' and '--skiphbasecp'. > - > > Key: AMBARI-19761 > URL: https://issues.apache.org/jira/browse/AMBARI-19761 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19761.patch > > > ' --skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP > 2.6 > *Requirement:* > Add it only if we have HDP 2.6 and onwards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19761) HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'.
[ https://issues.apache.org/jira/browse/AMBARI-19761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19761: - Description: '--skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP 2.6 *Requirement:* Add it only if we have HDP 2.6 and onwards. was: -- '--skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP 2.6 *Requirement:* Add it only if we have HDP 2.6 and onwards. > HSI start fails after Ambari upgrade with Unrecognized option: > '--skiphadoopversion' and '--skiphbasecp'. > - > > Key: AMBARI-19761 > URL: https://issues.apache.org/jira/browse/AMBARI-19761 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > > '--skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP > 2.6 > *Requirement:* > Add it only if we have HDP 2.6 and onwards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19761) HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'.
[ https://issues.apache.org/jira/browse/AMBARI-19761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19761: - Description: -- '--skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP 2.6 *Requirement:* Add it only if we have HDP 2.6 and onwards. was: - '--skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP 2.6 *Requirement:* Add it only if we have HDP 2.6 and onwards. > HSI start fails after Ambari upgrade with Unrecognized option: > '--skiphadoopversion' and '--skiphbasecp'. > - > > Key: AMBARI-19761 > URL: https://issues.apache.org/jira/browse/AMBARI-19761 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > > -- '--skiphadoopversion' and '--skiphbasecp' are valid only starting from > HDP 2.6 > *Requirement:* > Add it only if we have HDP 2.6 and onwards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19761) HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'.
[ https://issues.apache.org/jira/browse/AMBARI-19761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19761: - Description: ' --skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP 2.6 *Requirement:* Add it only if we have HDP 2.6 and onwards. was: '--skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP 2.6 *Requirement:* Add it only if we have HDP 2.6 and onwards. > HSI start fails after Ambari upgrade with Unrecognized option: > '--skiphadoopversion' and '--skiphbasecp'. > - > > Key: AMBARI-19761 > URL: https://issues.apache.org/jira/browse/AMBARI-19761 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > > ' --skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP > 2.6 > *Requirement:* > Add it only if we have HDP 2.6 and onwards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19761) HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'.
Swapan Shridhar created AMBARI-19761: Summary: HSI start fails after Ambari upgrade with Unrecognized option: '--skiphadoopversion' and '--skiphbasecp'. Key: AMBARI-19761 URL: https://issues.apache.org/jira/browse/AMBARI-19761 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 2.5.0 - '--skiphadoopversion' and '--skiphbasecp' are valid only starting from HDP 2.6 *Requirement:* Add it only if we have HDP 2.6 and onwards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19760) HSI: Fixes for smaller clusters - higher concurrency, min_node_size
[
https://issues.apache.org/jira/browse/AMBARI-19760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843704#comment-15843704
]
Hadoop QA commented on AMBARI-19760:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849783/AMBARI-19760.01.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10305//console
This message is automatically generated.
> HSI: Fixes for smaller clusters - higher concurrency, min_node_size
> ---
>
> Key: AMBARI-19760
> URL: https://issues.apache.org/jira/browse/AMBARI-19760
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19760.01.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19759) Fix Spark2 service string
[ https://issues.apache.org/jira/browse/AMBARI-19759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843703#comment-15843703 ] Hudson commented on AMBARI-19759: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6576 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6576/]) AMBARI-19759. Fix Spark2 service description string (Bikas Saha via (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c60098536dcd7faf85e364fdcafed17cbba340a6]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/metainfo.xml > Fix Spark2 service string > - > > Key: AMBARI-19759 > URL: https://issues.apache.org/jira/browse/AMBARI-19759 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.5.0 > > Attachments: AMBARI-19759.1.patch > > > Unnecessarily mentions 2.1 etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19760) HSI: Fixes for smaller clusters - higher concurrency, min_node_size
[ https://issues.apache.org/jira/browse/AMBARI-19760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-19760: Attachment: AMBARI-19760.01.patch Fixes minNodeCount. Fixes concurrency to go up to 4 for smaller clusters (ignoring the calculations based on queries per executor). Fixes normalizeDown to return 0 if < min_container_size cc [~swapanshridhar], [~sumitmohanty] for review. > HSI: Fixes for smaller clusters - higher concurrency, min_node_size > --- > > Key: AMBARI-19760 > URL: https://issues.apache.org/jira/browse/AMBARI-19760 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19760.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19760) HSI: Fixes for smaller clusters - higher concurrency, min_node_size
[ https://issues.apache.org/jira/browse/AMBARI-19760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-19760: Status: Patch Available (was: Open) > HSI: Fixes for smaller clusters - higher concurrency, min_node_size > --- > > Key: AMBARI-19760 > URL: https://issues.apache.org/jira/browse/AMBARI-19760 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19760.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19760) HSI: Fixes for smaller clusters - higher concurrency, min_node_size
Siddharth Seth created AMBARI-19760: --- Summary: HSI: Fixes for smaller clusters - higher concurrency, min_node_size Key: AMBARI-19760 URL: https://issues.apache.org/jira/browse/AMBARI-19760 Project: Ambari Issue Type: Bug Components: stacks Reporter: Siddharth Seth Assignee: Siddharth Seth Priority: Critical Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19759) Fix Spark2 service string
[ https://issues.apache.org/jira/browse/AMBARI-19759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19759: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Fix Spark2 service string > - > > Key: AMBARI-19759 > URL: https://issues.apache.org/jira/browse/AMBARI-19759 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.5.0 > > Attachments: AMBARI-19759.1.patch > > > Unnecessarily mentions 2.1 etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19759) Fix Spark2 service string
[ https://issues.apache.org/jira/browse/AMBARI-19759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated AMBARI-19759: Attachment: (was: AMBARI-19759.1.patch) > Fix Spark2 service string > - > > Key: AMBARI-19759 > URL: https://issues.apache.org/jira/browse/AMBARI-19759 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.5.0 > > Attachments: AMBARI-19759.1.patch > > > Unnecessarily mentions 2.1 etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19759) Fix Spark2 service string
[ https://issues.apache.org/jira/browse/AMBARI-19759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated AMBARI-19759: Attachment: AMBARI-19759.1.patch > Fix Spark2 service string > - > > Key: AMBARI-19759 > URL: https://issues.apache.org/jira/browse/AMBARI-19759 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.5.0 > > Attachments: AMBARI-19759.1.patch, AMBARI-19759.1.patch > > > Unnecessarily mentions 2.1 etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19759) Fix Spark2 service string
[ https://issues.apache.org/jira/browse/AMBARI-19759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843668#comment-15843668 ] Bikas Saha commented on AMBARI-19759: - https://reviews.apache.org/r/56046/ > Fix Spark2 service string > - > > Key: AMBARI-19759 > URL: https://issues.apache.org/jira/browse/AMBARI-19759 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.5.0 > > Attachments: AMBARI-19759.1.patch > > > Unnecessarily mentions 2.1 etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19759) Fix Spark2 service string
[ https://issues.apache.org/jira/browse/AMBARI-19759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated AMBARI-19759: Status: Patch Available (was: Open) > Fix Spark2 service string > - > > Key: AMBARI-19759 > URL: https://issues.apache.org/jira/browse/AMBARI-19759 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.5.0 > > Attachments: AMBARI-19759.1.patch > > > Unnecessarily mentions 2.1 etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19759) Fix Spark2 service string
[ https://issues.apache.org/jira/browse/AMBARI-19759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated AMBARI-19759: Attachment: AMBARI-19759.1.patch > Fix Spark2 service string > - > > Key: AMBARI-19759 > URL: https://issues.apache.org/jira/browse/AMBARI-19759 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.5.0 > > Attachments: AMBARI-19759.1.patch > > > Unnecessarily mentions 2.1 etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19759) Fix Spark2 service string
Bikas Saha created AMBARI-19759: --- Summary: Fix Spark2 service string Key: AMBARI-19759 URL: https://issues.apache.org/jira/browse/AMBARI-19759 Project: Ambari Issue Type: Bug Reporter: Bikas Saha Assignee: Bikas Saha Fix For: 2.5.0 Unnecessarily mentions 2.1 etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19758) Post Ambari upgrade AMS config properties changes are marking HDFS/YARN/Hive/HBase with restart required
[ https://issues.apache.org/jira/browse/AMBARI-19758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19758: --- Status: Patch Available (was: Open) > Post Ambari upgrade AMS config properties changes are marking > HDFS/YARN/Hive/HBase with restart required > > > Key: AMBARI-19758 > URL: https://issues.apache.org/jira/browse/AMBARI-19758 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19758.patch > > > Deploy Ambari-2.4 and upgrade to Ambari-2.5. Noticed that all core services > are marked with restart required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19758) Post Ambari upgrade AMS config properties changes are marking HDFS/YARN/Hive/HBase with restart required
[ https://issues.apache.org/jira/browse/AMBARI-19758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19758: --- Attachment: AMBARI-19758.patch > Post Ambari upgrade AMS config properties changes are marking > HDFS/YARN/Hive/HBase with restart required > > > Key: AMBARI-19758 > URL: https://issues.apache.org/jira/browse/AMBARI-19758 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19758.patch > > > Deploy Ambari-2.4 and upgrade to Ambari-2.5. Noticed that all core services > are marked with restart required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19758) Post Ambari upgrade AMS config properties changes are marking HDFS/YARN/Hive/HBase with restart required
Aravindan Vijayan created AMBARI-19758: -- Summary: Post Ambari upgrade AMS config properties changes are marking HDFS/YARN/Hive/HBase with restart required Key: AMBARI-19758 URL: https://issues.apache.org/jira/browse/AMBARI-19758 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.5.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Priority: Critical Fix For: 2.5.0 Deploy Ambari-2.4 and upgrade to Ambari-2.5. Noticed that all core services are marked with restart required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19754) Remove white border from the content area in popup wizards
[ https://issues.apache.org/jira/browse/AMBARI-19754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843626#comment-15843626 ] Hudson commented on AMBARI-19754: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6575 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6575/]) AMBARI-19754. Remove white border from the content area in popup (xiwang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b3391f0dd030130add23b9ffb09fb7a776dfe969]) * (edit) ambari-web/app/styles/modal_popups.less * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_history_view.js * (edit) ambari-web/app/views/common/modal_popups/log_tail_popup.js > Remove white border from the content area in popup wizards > -- > > Key: AMBARI-19754 > URL: https://issues.apache.org/jira/browse/AMBARI-19754 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19754.patch, AMBARI-19754.patch > > > The idea is to get rid of the white border around the content so that it > looks more polished. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19754) Remove white border from the content area in popup wizards
[ https://issues.apache.org/jira/browse/AMBARI-19754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843628#comment-15843628 ] Xi Wang commented on AMBARI-19754: -- Committed to trunk > Remove white border from the content area in popup wizards > -- > > Key: AMBARI-19754 > URL: https://issues.apache.org/jira/browse/AMBARI-19754 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19754.patch, AMBARI-19754.patch > > > The idea is to get rid of the white border around the content so that it > looks more polished. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19749) Run ru_set_all script after installing packages on single host not belonging to any cluster
[
https://issues.apache.org/jira/browse/AMBARI-19749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843603#comment-15843603
]
Hadoop QA commented on AMBARI-19749:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849751/AMBARI-19749.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10304//console
This message is automatically generated.
> Run ru_set_all script after installing packages on single host not belonging
> to any cluster
> ---
>
> Key: AMBARI-19749
> URL: https://issues.apache.org/jira/browse/AMBARI-19749
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.5.0
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 2.5.0
>
> Attachments: AMBARI-19749.patch
>
>
> Run ru_set_all script after installing packages on single host not belonging
> to any cluster, to create correct symlinks for new stack version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19755) Perf: start/stop all actions works much slower after few days of testing
[
https://issues.apache.org/jira/browse/AMBARI-19755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843595#comment-15843595
]
Hadoop QA commented on AMBARI-19755:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849759/AMBARI-19755.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10303//console
This message is automatically generated.
> Perf: start/stop all actions works much slower after few days of testing
>
>
> Key: AMBARI-19755
> URL: https://issues.apache.org/jira/browse/AMBARI-19755
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19755.patch
>
>
> Fix performance for long running cluster. Because start/stop all commands
> generation takes too much time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19757) Changes needed in StackAdvisor for supporting {{stack_root}}
Bikas Saha created AMBARI-19757:
---
Summary: Changes needed in StackAdvisor for supporting
{{stack_root}}
Key: AMBARI-19757
URL: https://issues.apache.org/jira/browse/AMBARI-19757
Project: Ambari
Issue Type: Bug
Reporter: Bikas Saha
Priority: Critical
Seems like supporting {{stack_root}} for AMBARI-19733 we need support from
stack advisor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-17328) Spark2 history server quick link still point to spark1 url
[ https://issues.apache.org/jira/browse/AMBARI-17328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-17328. Resolution: Fixed Verified that patch has been committed to branch-2.5 and trunk. > Spark2 history server quick link still point to spark1 url > -- > > Key: AMBARI-17328 > URL: https://issues.apache.org/jira/browse/AMBARI-17328 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Affects Versions: 2.4.0 >Reporter: Saisai Shao >Assignee: Saisai Shao > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17206) Installing Spark2 should not install Slider
[ https://issues.apache.org/jira/browse/AMBARI-17206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-17206. Resolution: Not A Problem Assignee: Robert Nettleton > Installing Spark2 should not install Slider > --- > > Key: AMBARI-17206 > URL: https://issues.apache.org/jira/browse/AMBARI-17206 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Yesha Vora >Assignee: Robert Nettleton > Fix For: 2.4.0 > > > Scenario: > * Install a cluster with Hadoop , Hive and Spark. > * Install Spark2 > At 2nd step, while installing Spark2, ambari mentions slider as dependency. > This behavior is not correct. Spark should have Hive as dependency not > slider. > Currently, if Hive is installed, slider is not being Installed by default. > Since Hive requires slider, Slider should be added as dependency to Hive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17206) Installing Spark2 should not install Slider
[ https://issues.apache.org/jira/browse/AMBARI-17206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17206: --- Fix Version/s: (was: 2.5.0) 2.4.0 > Installing Spark2 should not install Slider > --- > > Key: AMBARI-17206 > URL: https://issues.apache.org/jira/browse/AMBARI-17206 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Yesha Vora > Fix For: 2.4.0 > > > Scenario: > * Install a cluster with Hadoop , Hive and Spark. > * Install Spark2 > At 2nd step, while installing Spark2, ambari mentions slider as dependency. > This behavior is not correct. Spark should have Hive as dependency not > slider. > Currently, if Hive is installed, slider is not being Installed by default. > Since Hive requires slider, Slider should be added as dependency to Hive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14201) Move ResourceProvider methods from AmbariManagementController to appropriate ResourceProviders
[ https://issues.apache.org/jira/browse/AMBARI-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-14201: --- Fix Version/s: (was: 2.5.0) 3.0.0 > Move ResourceProvider methods from AmbariManagementController to appropriate > ResourceProviders > -- > > Key: AMBARI-14201 > URL: https://issues.apache.org/jira/browse/AMBARI-14201 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.3.0 >Reporter: Robert Levas >Assignee: Robert Levas > Fix For: 3.0.0 > > > Move ResourceProvider methods from AmbariManagementController to appropriate > ResourceProviders > List of methods to move: TBD -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19737) Add a validation check in HSI about Capacity Scheduler preemption requirements
[
https://issues.apache.org/jira/browse/AMBARI-19737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843573#comment-15843573
]
Hudson commented on AMBARI-19737:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6574 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6574/])
AMBARI-19737. Add a validation check in HSI about Capacity Scheduler
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dcdf95b28a98e47062727f270adf2b4c69816f93])
* (edit)
ambari-server/src/test/python/stacks/2.5/common/services-normal-his-2-hosts.json
* (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
* (edit)
ambari-server/src/test/python/stacks/2.5/common/services-normal-his-valid.json
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
> Add a validation check in HSI about Capacity Scheduler preemption requirements
> --
>
> Key: AMBARI-19737
> URL: https://issues.apache.org/jira/browse/AMBARI-19737
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19737.patch, pjimage.jpg, Screen Shot 2017-01-26
> at 1.28.16 PM.png
>
>
> Capacity Scheduler preemption is not enabled by default in HDP. Enabling it
> affects the entire cluster and LLAP is of concern in the bug.
> *Requirement:*
> - Add a validation check about CS preemption configuration, while LLAP is not
> enabled.
> *Message:*
> {noformat}
> Enabling YARN config 'yarn.resourcemanager.scheduler.monitor.enable' is
> recommended if enabling LLAP, to ensure it is able to get cluster capacity.
> {noformat}
> If CS preemption is enabled, no validation check required.
> -> Also, uncommenting and fixing the test code in
> test_stack_advisor::test_validateHiveInteractiveSiteConfigurations().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19641) Deleted configuration groups are displayed along with active group with is_current value set to true using Ambari API's
[ https://issues.apache.org/jira/browse/AMBARI-19641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843569#comment-15843569 ] Hudson commented on AMBARI-19641: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6574 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6574/]) AMBARI-19641: Deleted configuration groups are displayed along with (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6d02a7a5b3415a87b0cbcf21d360942719efcb9d]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/orm/dao/ServiceConfigDAOTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceConfigEntity.java > Deleted configuration groups are displayed along with active group with > is_current value set to true using Ambari API's > --- > > Key: AMBARI-19641 > URL: https://issues.apache.org/jira/browse/AMBARI-19641 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-19641.patch, AMBARI-19641_v1.patch, > AMBARI-19641_v2.patch, ConfigHistory.png, > service_config_versions_HDFS_is_current > > > Deleted config groups should not be displayed as active groups. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19663) LLAP metrics collector host gets wrongly updated
[
https://issues.apache.org/jira/browse/AMBARI-19663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843570#comment-15843570
]
Hudson commented on AMBARI-19663:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6574 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6574/])
AMBARI-19663. LLAP metrics collector host gets wrongly updated. (sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=23522a28126bbb1216bb1b556fce1d24a7262d26])
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
> LLAP metrics collector host gets wrongly updated
>
>
> Key: AMBARI-19663
> URL: https://issues.apache.org/jira/browse/AMBARI-19663
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Attachments: AMBARI-19663.1.patch
>
>
> AMS collector hostname gets wrongly updated (as python array to string)
> causing failure to communicate with metrics collector
> {code}
> 2016-12-08T11:26:58,876 INFO [timeline ()]
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink: Collector
> [u'example.com'] is not longer live. Removing it from list of know live
> collector hosts : []
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19741) Ambari Server Unit Test failure on branch-2.5/trunk for testUpdateConfigForceSecurityEnabled
[ https://issues.apache.org/jira/browse/AMBARI-19741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843572#comment-15843572 ] Hudson commented on AMBARI-19741: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6574 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6574/]) Revert "AMBARI-19741. Ambari Server Unit Test failure on (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=65eb886720c2ccff344fe99928fabc23bcc48738]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/kerberos/UpdateKerberosConfigsServerActionTest.java > Ambari Server Unit Test failure on branch-2.5/trunk for > testUpdateConfigForceSecurityEnabled > > > Key: AMBARI-19741 > URL: https://issues.apache.org/jira/browse/AMBARI-19741 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-19741.2.5.patch, AMBARI-19741.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19751) Credential Store params should be in the command json for RESTART
[ https://issues.apache.org/jira/browse/AMBARI-19751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843571#comment-15843571 ] Hudson commented on AMBARI-19751: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6574 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6574/]) AMBARI-19751: Credential Store params should be in the command json for (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9d8a54c23146db595e81d72785c4f9779f3bee00]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java > Credential Store params should be in the command json for RESTART > - > > Key: AMBARI-19751 > URL: https://issues.apache.org/jira/browse/AMBARI-19751 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram >Priority: Critical > Fix For: 2.5.0 > > Attachments: rb56029.patch > > > Command json doesn't contain Credential Store related params > (credentialStoreEnabled, configuration_credentials) for RESTART operation. > Only AmbariManagementControllerimpl:createHostAction enters these parameters, > while for the RESTART operations > AmbariCustomCommandExecutionHelper:addCustomCommandAction creates the command > json, it should also take care of Credential Store related params. As there > are several other locations where the command json is created they may as > well need to be modified. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19732) Allow all sinks a config override to point to a different ZK quorum
[ https://issues.apache.org/jira/browse/AMBARI-19732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843568#comment-15843568 ] Hudson commented on AMBARI-19732: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6574 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6574/]) AMBARI-19732. Allow all sinks a config override to point to a different (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9963ac81963e01eec66467f0536b4ebdf058aa6e]) * (edit) ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java > Allow all sinks a config override to point to a different ZK quorum > --- > > Key: AMBARI-19732 > URL: https://issues.apache.org/jira/browse/AMBARI-19732 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 2.5.0 > > Attachments: AMBARI-19732.patch > > > Right now zk quorum is read from daemon configs. > We should also allow override non-default property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19755) Perf: start/stop all actions works much slower after few days of testing
[
https://issues.apache.org/jira/browse/AMBARI-19755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843566#comment-15843566
]
Hadoop QA commented on AMBARI-19755:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849759/AMBARI-19755.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10302//console
This message is automatically generated.
> Perf: start/stop all actions works much slower after few days of testing
>
>
> Key: AMBARI-19755
> URL: https://issues.apache.org/jira/browse/AMBARI-19755
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19755.patch
>
>
> Fix performance for long running cluster. Because start/stop all commands
> generation takes too much time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19755) Perf: start/stop all actions works much slower after few days of testing
[ https://issues.apache.org/jira/browse/AMBARI-19755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-19755: --- Attachment: AMBARI-19755.patch > Perf: start/stop all actions works much slower after few days of testing > > > Key: AMBARI-19755 > URL: https://issues.apache.org/jira/browse/AMBARI-19755 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19755.patch > > > Fix performance for long running cluster. Because start/stop all commands > generation takes too much time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19755) Perf: start/stop all actions works much slower after few days of testing
[ https://issues.apache.org/jira/browse/AMBARI-19755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-19755: --- Attachment: (was: AMBARI-19755.patch) > Perf: start/stop all actions works much slower after few days of testing > > > Key: AMBARI-19755 > URL: https://issues.apache.org/jira/browse/AMBARI-19755 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19755.patch > > > Fix performance for long running cluster. Because start/stop all commands > generation takes too much time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19746) Ambari HDFS Metric alerts turns to UNKNOWN status with error "argument of type 'NoneType' is not iterable"
[
https://issues.apache.org/jira/browse/AMBARI-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843528#comment-15843528
]
Hudson commented on AMBARI-19746:
-
ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6573 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6573/])
AMBARI-19746 Ambari HDFS Metric alerts turns to UNKNOWN status with (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7c7769b1a00ebeb9a7cf10ae5e7865f13ece7f5e])
* (edit) ambari-common/src/main/python/ambari_commons/ambari_metrics_helper.py
> Ambari HDFS Metric alerts turns to UNKNOWN status with error "argument of
> type 'NoneType' is not iterable"
> --
>
> Key: AMBARI-19746
> URL: https://issues.apache.org/jira/browse/AMBARI-19746
> Project: Ambari
> Issue Type: Bug
> Components: alerts
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19746.patch
>
>
> Build used : ambari-2.5.0.0-724
> Test is updating the alert definition minimumValue to "0.0".
> Payload used to update the minimumValue
> {code:java}
> /{
> "AlertDefinition": {
> "cluster_name": "cl1",
> "id": 81,
> "name": "increase_nn_heap_usage_daily",
> "label": "NameNode Heap Usage (Daily)",
> "component_name": "NAMENODE",
> "description": "This service-level alert is triggered if the
> NameNode heap usage deviation has grown beyond the specified threshold within
> a day period.",
> "enabled": true,
> "ignore_host": false,
> "interval": 1,
> "scope": "ANY",
> "service_name": "HDFS",
> "source": {
> "parameters": [{
> "name": "mergeHaMetrics",
> "display_name": "Whether active and stanby
> NameNodes metrics should be merged",
> "value": "false",
> "description": "Whether active and stanby
> NameNodes metrics should be merged.",
> "type": "STRING",
> "visibility": "HIDDEN"
> }, {
> "name": "interval",
> "display_name": "Time interval in minutes",
> "value": "1440.0",
> "description": "Time interval in minutes.",
> "type": "NUMERIC",
> "visibility": "HIDDEN"
> }, {
> "name": "appId",
> "display_name": "AMS application id",
> "value": "NAMENODE",
> "description": "The application id used to
> retrieve the metric.",
> "type": "STRING",
> "visibility": "HIDDEN"
> }, {
> "name": "metricName",
> "display_name": "Metric Name",
> "value": "jvm.JvmMetrics.MemHeapUsedM",
> "description": "The metric to monitor.",
> "type": "STRING",
> "visibility": "HIDDEN"
> }, {
> "name": "metric.deviation.warning.threshold",
> "display_name": "Growth Rate",
> "value": "20.0",
> "description": "The percentage of NameNode heap
> usage growth.",
> "type": "PERCENT"
> }, {
> "name": "metric.deviation.critical.threshold",
> "display_name": "Growth Rate",
> "value": "50.0",
> "description": "The percentage of NameNode heap
> usage growth.",
> "type": "PERCENT"
> }, {
> "name": "metric.units",
> "display_name": "Metric Units",
> "value": "MB",
> "description": "The units that the metric data
> points are reported in.",
> "type": "STRING",
> "visibility": "HIDDEN"
> }, {
> "name": "minimumValue",
> "display_name": "Minimum
[jira] [Commented] (AMBARI-19751) Credential Store params should be in the command json for RESTART
[ https://issues.apache.org/jira/browse/AMBARI-19751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843505#comment-15843505 ] Hudson commented on AMBARI-19751: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #827 (See [https://builds.apache.org/job/Ambari-branch-2.5/827/]) AMBARI-19751: Credential Store params should be in the command json for (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c2e51758f81bac1f0b1646e8f92846810799ce70]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java > Credential Store params should be in the command json for RESTART > - > > Key: AMBARI-19751 > URL: https://issues.apache.org/jira/browse/AMBARI-19751 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram >Priority: Critical > Fix For: 2.5.0 > > Attachments: rb56029.patch > > > Command json doesn't contain Credential Store related params > (credentialStoreEnabled, configuration_credentials) for RESTART operation. > Only AmbariManagementControllerimpl:createHostAction enters these parameters, > while for the RESTART operations > AmbariCustomCommandExecutionHelper:addCustomCommandAction creates the command > json, it should also take care of Credential Store related params. As there > are several other locations where the command json is created they may as > well need to be modified. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19756) Add common log rotation settings to hive log4j2
Madhuvanthi Radhakrishnan created AMBARI-19756: -- Summary: Add common log rotation settings to hive log4j2 Key: AMBARI-19756 URL: https://issues.apache.org/jira/browse/AMBARI-19756 Project: Ambari Issue Type: Bug Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 2.5.0 1. ./stacks/HDP/2.5/services/HIVE/configuration/beeline-log4j2.xml It has only ConsoleAppender. -No Changes 2. ./stacks/HDP/2.5/services/HIVE/configuration/hive-exec-log4j2.xml It has only ConsoleAppender. -No Changes 3. ./stacks/HDP/2.5/services/HIVE/configuration/hive-log4j2.xml daily rolling file appender 4. ./stacks/HDP/2.5/services/HIVE/configuration/llap-cli-log4j2.xml daily rolling file appender -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19749) Run ru_set_all script after installing packages on single host not belonging to any cluster
[ https://issues.apache.org/jira/browse/AMBARI-19749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19749: Attachment: AMBARI-19749.patch > Run ru_set_all script after installing packages on single host not belonging > to any cluster > --- > > Key: AMBARI-19749 > URL: https://issues.apache.org/jira/browse/AMBARI-19749 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.5.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19749.patch > > > Run ru_set_all script after installing packages on single host not belonging > to any cluster, to create correct symlinks for new stack version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19749) Run ru_set_all script after installing packages on single host not belonging to any cluster
[ https://issues.apache.org/jira/browse/AMBARI-19749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19749: Status: Patch Available (was: Open) > Run ru_set_all script after installing packages on single host not belonging > to any cluster > --- > > Key: AMBARI-19749 > URL: https://issues.apache.org/jira/browse/AMBARI-19749 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.5.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > > Run ru_set_all script after installing packages on single host not belonging > to any cluster, to create correct symlinks for new stack version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19741) Ambari Server Unit Test failure on branch-2.5/trunk for testUpdateConfigForceSecurityEnabled
[ https://issues.apache.org/jira/browse/AMBARI-19741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843480#comment-15843480 ] Hudson commented on AMBARI-19741: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #826 (See [https://builds.apache.org/job/Ambari-branch-2.5/826/]) Revert "AMBARI-19741. Ambari Server Unit Test failure on (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=687d701af60998743dd1d97ab62459e8630b18e7]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/kerberos/UpdateKerberosConfigsServerActionTest.java > Ambari Server Unit Test failure on branch-2.5/trunk for > testUpdateConfigForceSecurityEnabled > > > Key: AMBARI-19741 > URL: https://issues.apache.org/jira/browse/AMBARI-19741 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-19741.2.5.patch, AMBARI-19741.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19751) Credential Store params should be in the command json for RESTART
[ https://issues.apache.org/jira/browse/AMBARI-19751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-19751: --- Committed to branch-2.5 and trunk > Credential Store params should be in the command json for RESTART > - > > Key: AMBARI-19751 > URL: https://issues.apache.org/jira/browse/AMBARI-19751 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram >Priority: Critical > Fix For: 2.5.0 > > Attachments: rb56029.patch > > > Command json doesn't contain Credential Store related params > (credentialStoreEnabled, configuration_credentials) for RESTART operation. > Only AmbariManagementControllerimpl:createHostAction enters these parameters, > while for the RESTART operations > AmbariCustomCommandExecutionHelper:addCustomCommandAction creates the command > json, it should also take care of Credential Store related params. As there > are several other locations where the command json is created they may as > well need to be modified. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19755) Perf: start/stop all actions works much slower after few days of testing
[
https://issues.apache.org/jira/browse/AMBARI-19755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843455#comment-15843455
]
Hadoop QA commented on AMBARI-19755:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849741/AMBARI-19755.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10301//console
This message is automatically generated.
> Perf: start/stop all actions works much slower after few days of testing
>
>
> Key: AMBARI-19755
> URL: https://issues.apache.org/jira/browse/AMBARI-19755
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19755.patch
>
>
> Fix performance for long running cluster. Because start/stop all commands
> generation takes too much time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19751) Credential Store params should be in the command json for RESTART
[
https://issues.apache.org/jira/browse/AMBARI-19751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843446#comment-15843446
]
Hadoop QA commented on AMBARI-19751:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849723/rb56029.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10299//console
This message is automatically generated.
> Credential Store params should be in the command json for RESTART
> -
>
> Key: AMBARI-19751
> URL: https://issues.apache.org/jira/browse/AMBARI-19751
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: rb56029.patch
>
>
> Command json doesn't contain Credential Store related params
> (credentialStoreEnabled, configuration_credentials) for RESTART operation.
> Only AmbariManagementControllerimpl:createHostAction enters these parameters,
> while for the RESTART operations
> AmbariCustomCommandExecutionHelper:addCustomCommandAction creates the command
> json, it should also take care of Credential Store related params. As there
> are several other locations where the command json is created they may as
> well need to be modified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19750) Hive2 view - Clicking on browse databases does not work
[
https://issues.apache.org/jira/browse/AMBARI-19750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843454#comment-15843454
]
Hadoop QA commented on AMBARI-19750:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849720/AMBARI-19750_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10300//console
This message is automatically generated.
> Hive2 view - Clicking on browse databases does not work
> ---
>
> Key: AMBARI-19750
> URL: https://issues.apache.org/jira/browse/AMBARI-19750
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19750_trunk.patch
>
>
> There is "Browse" drop down button in hive2 view. Clicking on it does not do
> anything.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19755) Perf: start/stop all actions works much slower after few days of testing
[ https://issues.apache.org/jira/browse/AMBARI-19755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-19755: --- Status: Patch Available (was: Open) > Perf: start/stop all actions works much slower after few days of testing > > > Key: AMBARI-19755 > URL: https://issues.apache.org/jira/browse/AMBARI-19755 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19755.patch > > > Fix performance for long running cluster. Because start/stop all commands > generation takes too much time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19755) Perf: start/stop all actions works much slower after few days of testing
[ https://issues.apache.org/jira/browse/AMBARI-19755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-19755: --- Attachment: AMBARI-19755.patch > Perf: start/stop all actions works much slower after few days of testing > > > Key: AMBARI-19755 > URL: https://issues.apache.org/jira/browse/AMBARI-19755 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19755.patch > > > Fix performance for long running cluster. Because start/stop all commands > generation takes too much time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19755) Perf: start/stop all actions works much slower after few days of testing
Vitaly Brodetskyi created AMBARI-19755: -- Summary: Perf: start/stop all actions works much slower after few days of testing Key: AMBARI-19755 URL: https://issues.apache.org/jira/browse/AMBARI-19755 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Critical Fix For: 2.5.0 Fix performance for long running cluster. Because start/stop all commands generation takes too much time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19752) Hive View 2.0 execute button needs some feedback
[
https://issues.apache.org/jira/browse/AMBARI-19752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843434#comment-15843434
]
Hadoop QA commented on AMBARI-19752:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849726/AMBARI-19752_trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10298//console
This message is automatically generated.
> Hive View 2.0 execute button needs some feedback
>
>
> Key: AMBARI-19752
> URL: https://issues.apache.org/jira/browse/AMBARI-19752
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19752_trunk.patch
>
>
> When you click execute in the query tab, nothing happens for a while, then
> the result is updated. It needs to indicate query is in progress; otherwise I
> personally just started mashing the button.
> The query was "select 1"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-15121) Ambari integration with Hive LLAP
[ https://issues.apache.org/jira/browse/AMBARI-15121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar resolved AMBARI-15121. -- Resolution: Duplicate > Ambari integration with Hive LLAP > -- > > Key: AMBARI-15121 > URL: https://issues.apache.org/jira/browse/AMBARI-15121 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > > Ambari integration with Hive LLAP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19737) Add a validation check in HSI about Capacity Scheduler preemption requirements
[
https://issues.apache.org/jira/browse/AMBARI-19737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843431#comment-15843431
]
Hudson commented on AMBARI-19737:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #825 (See
[https://builds.apache.org/job/Ambari-branch-2.5/825/])
AMBARI-19737. Add a validation check in HSI about Capacity Scheduler
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=72cff6c680d35bd12903d49fdb9f47b5c1163790])
* (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* (edit)
ambari-server/src/test/python/stacks/2.5/common/services-normal-his-2-hosts.json
* (edit)
ambari-server/src/test/python/stacks/2.5/common/services-normal-his-valid.json
> Add a validation check in HSI about Capacity Scheduler preemption requirements
> --
>
> Key: AMBARI-19737
> URL: https://issues.apache.org/jira/browse/AMBARI-19737
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19737.patch, pjimage.jpg, Screen Shot 2017-01-26
> at 1.28.16 PM.png
>
>
> Capacity Scheduler preemption is not enabled by default in HDP. Enabling it
> affects the entire cluster and LLAP is of concern in the bug.
> *Requirement:*
> - Add a validation check about CS preemption configuration, while LLAP is not
> enabled.
> *Message:*
> {noformat}
> Enabling YARN config 'yarn.resourcemanager.scheduler.monitor.enable' is
> recommended if enabling LLAP, to ensure it is able to get cluster capacity.
> {noformat}
> If CS preemption is enabled, no validation check required.
> -> Also, uncommenting and fixing the test code in
> test_stack_advisor::test_validateHiveInteractiveSiteConfigurations().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19663) LLAP metrics collector host gets wrongly updated
[
https://issues.apache.org/jira/browse/AMBARI-19663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843430#comment-15843430
]
Hudson commented on AMBARI-19663:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #825 (See
[https://builds.apache.org/job/Ambari-branch-2.5/825/])
AMBARI-19663. LLAP metrics collector host gets wrongly updated. (sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3f19ca0c9556f8772cb19ae3dea041bcd1f09341])
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
> LLAP metrics collector host gets wrongly updated
>
>
> Key: AMBARI-19663
> URL: https://issues.apache.org/jira/browse/AMBARI-19663
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
> Attachments: AMBARI-19663.1.patch
>
>
> AMS collector hostname gets wrongly updated (as python array to string)
> causing failure to communicate with metrics collector
> {code}
> 2016-12-08T11:26:58,876 INFO [timeline ()]
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink: Collector
> [u'example.com'] is not longer live. Removing it from list of know live
> collector hosts : []
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18955) AMBARI-18955. Cleanup 'LLAP package' folder(s) before a given Hive Server Interactive (HSI) start/restart.
[ https://issues.apache.org/jira/browse/AMBARI-18955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18955: - Resolution: Fixed Status: Resolved (was: Patch Available) > AMBARI-18955. Cleanup 'LLAP package' folder(s) before a given Hive Server > Interactive (HSI) start/restart. > -- > > Key: AMBARI-18955 > URL: https://issues.apache.org/jira/browse/AMBARI-18955 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18955.patch > > > - With each start/restart of HSI, a new LLAP package folder gets created as > 'llap-slider-MM-DD-HH:MM:SS'. > - As the process continues, the number of package explosion can end up > exhausting the disk space. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18901) LLAP integration enhancements
[ https://issues.apache.org/jira/browse/AMBARI-18901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18901: - Resolution: Fixed Status: Resolved (was: Patch Available) > LLAP integration enhancements > - > > Key: AMBARI-18901 > URL: https://issues.apache.org/jira/browse/AMBARI-18901 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18901-trunk.patch > > > The attached patch is a merged patch for all the changes from branch - > branch-feature-AMBARI-18901 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19143) Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'.
[ https://issues.apache.org/jira/browse/AMBARI-19143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19143: - Resolution: Fixed Status: Resolved (was: Patch Available) > Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'. > - > > Key: AMBARI-19143 > URL: https://issues.apache.org/jira/browse/AMBARI-19143 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19143.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19138) Option for getting heap dump for Hive and Tez services.
[
https://issues.apache.org/jira/browse/AMBARI-19138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19138:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Option for getting heap dump for Hive and Tez services.
> ---
>
> Key: AMBARI-19138
> URL: https://issues.apache.org/jira/browse/AMBARI-19138
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19138.patch
>
>
> We need to add the heap dump option for:
> - All Hive services (Hive1/HiveServer2, Hive2/HiveServer2 and Metastore):
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option appended to "Advance hive-env" -> hive-env-template ->
> HADOOP_CLIENT_OPTS environment variable
> - HSI YARN jobs:
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option added to "Advanced hive-interactive-env" -> Llap app java opts. Logs
> will be generated at: /<'Configurable location
> provided'>/java_.hprof on the nodes that failed with OOM.
> - Tez component:
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option added to tez.am.launch.cmd-opts for AM OOM and
> tez.task.launch.cmd-opts for task OOM.
> ** 'Configurable location provided' should be one config where user can
> change the location and consumable by all others.
> Further, whether to keep the heap dump option ENABLED or DISABLED should be
> configurable via Ambari. [~carter] to confirm for this. By default, option
> should be DISABLED.
> ** ENABLING/DISABLING of option will require the above components
> RESATARt for change to take effect.
> ** permissions for dump file can be 600 for :.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19035) LLAP startup: Ambari should not use slider anti-affinity when it's avoidable
[ https://issues.apache.org/jira/browse/AMBARI-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19035: - Resolution: Fixed Status: Resolved (was: Patch Available) > LLAP startup: Ambari should not use slider anti-affinity when it's avoidable > > > Key: AMBARI-19035 > URL: https://issues.apache.org/jira/browse/AMBARI-19035 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19035.patch > > > - YARN does not support anti-affinity, and therefore Slider implements AA by > the means of exclusion lists - it starts containers one by one and excludes > the nodes it gets; that adds ~2sec./machine of overhead (on openstack). > - When the LLAP container memory size configuration is more than half of YARN > node memory, or the same for number of cores, AA is implicit and should be > avoided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18901) LLAP integration enhancements
[
https://issues.apache.org/jira/browse/AMBARI-18901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843427#comment-15843427
]
Swapan Shridhar commented on AMBARI-18901:
--
commit:
branch-2.5:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
trunk:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
> LLAP integration enhancements
> -
>
> Key: AMBARI-18901
> URL: https://issues.apache.org/jira/browse/AMBARI-18901
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18901-trunk.patch
>
>
> The attached patch is a merged patch for all the changes from branch -
> branch-feature-AMBARI-18901
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18963) Convert config 'hive.llap.io.memory.size' value from MB to Bytes before writing it to hive-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18963: - Resolution: Fixed Status: Resolved (was: Patch Available) > Convert config 'hive.llap.io.memory.size' value from MB to Bytes before > writing it to hive-site.xml > --- > > Key: AMBARI-18963 > URL: https://issues.apache.org/jira/browse/AMBARI-18963 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18963.patch > > > - Currently, we calculate config 'hive.llap.io.memory.size' value in MB. > - We end up writing the config value in MB units to hive-site.xml. > *Expected:* > - Value written in hive-site.xml should be in Bytes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18967) Use max-AM percentage for a queue selected, instead of reading from top level common.
[
https://issues.apache.org/jira/browse/AMBARI-18967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-18967:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Use max-AM percentage for a queue selected, instead of reading from top level
> common.
> -
>
> Key: AMBARI-18967
> URL: https://issues.apache.org/jira/browse/AMBARI-18967
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18967.patch
>
>
> *Current:*
> - We are reading the top level max-AM percent value for non 'llap' named
> queue at root level.
> Eg: yarn.scheduler.capacity.maximum-am-resource-percent=1
> *Required:*
> AM Percent value should be read as:
> - Fetch the 'AM Percent' value for queue in consideration, if exists, else
> - Return default value as 0.1.
> *Eg:*
> Say queue in consideration is named: 'xyz' and is at depth 3. Thus, the
> expected 'key' config to be read is :
> {noformat}
> yarn.scheduler.capacity.root.abc.xyz.maximum-am-resource-percent=
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18967) Use max-AM percentage for a queue selected, instead of reading from top level common.
[
https://issues.apache.org/jira/browse/AMBARI-18967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843424#comment-15843424
]
Swapan Shridhar commented on AMBARI-18967:
--
commit:
branch-2.5:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
trunk:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
> Use max-AM percentage for a queue selected, instead of reading from top level
> common.
> -
>
> Key: AMBARI-18967
> URL: https://issues.apache.org/jira/browse/AMBARI-18967
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18967.patch
>
>
> *Current:*
> - We are reading the top level max-AM percent value for non 'llap' named
> queue at root level.
> Eg: yarn.scheduler.capacity.maximum-am-resource-percent=1
> *Required:*
> AM Percent value should be read as:
> - Fetch the 'AM Percent' value for queue in consideration, if exists, else
> - Return default value as 0.1.
> *Eg:*
> Say queue in consideration is named: 'xyz' and is at depth 3. Thus, the
> expected 'key' config to be read is :
> {noformat}
> yarn.scheduler.capacity.root.abc.xyz.maximum-am-resource-percent=
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18955) AMBARI-18955. Cleanup 'LLAP package' folder(s) before a given Hive Server Interactive (HSI) start/restart.
[
https://issues.apache.org/jira/browse/AMBARI-18955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843425#comment-15843425
]
Swapan Shridhar commented on AMBARI-18955:
--
commit:
branch-2.5:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
trunk:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
> AMBARI-18955. Cleanup 'LLAP package' folder(s) before a given Hive Server
> Interactive (HSI) start/restart.
> --
>
> Key: AMBARI-18955
> URL: https://issues.apache.org/jira/browse/AMBARI-18955
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18955.patch
>
>
> - With each start/restart of HSI, a new LLAP package folder gets created as
> 'llap-slider-MM-DD-HH:MM:SS'.
> - As the process continues, the number of package explosion can end up
> exhausting the disk space.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19741) Ambari Server Unit Test failure on branch-2.5/trunk for testUpdateConfigForceSecurityEnabled
[
https://issues.apache.org/jira/browse/AMBARI-19741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843423#comment-15843423
]
Robert Levas commented on AMBARI-19741:
---
This works for Java 1.8 but not for Java 1.7. Reverting to fix for both
version of Java.
Reverted cc30798a6f1428fbe2a2dd6c64cac2c128cf9a23 from trunk:
{noformat}
commit 65eb886720c2ccff344fe99928fabc23bcc48738
Author: Robert Levas
Date: Fri Jan 27 15:09:57 2017 -0500
{noformat}
Reverted 31527a01564d337986568e58d0d49122a5f952a4 from branch-2.5:
{noformat}
commit 687d701af60998743dd1d97ab62459e8630b18e7
Author: Robert Levas
Date: Fri Jan 27 15:13:01 2017 -0500
{noformat}
> Ambari Server Unit Test failure on branch-2.5/trunk for
> testUpdateConfigForceSecurityEnabled
>
>
> Key: AMBARI-19741
> URL: https://issues.apache.org/jira/browse/AMBARI-19741
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 2.5.0
>
> Attachments: AMBARI-19741.2.5.patch, AMBARI-19741.trunk.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19060) Update the HiveServer config values if Security Authorization chosen is None.
[ https://issues.apache.org/jira/browse/AMBARI-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19060: - Resolution: Fixed Status: Resolved (was: Patch Available) > Update the HiveServer config values if Security Authorization chosen is None. > - > > Key: AMBARI-19060 > URL: https://issues.apache.org/jira/browse/AMBARI-19060 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19060.patch > > > - When hive-env/hive_security_authorization chosen value is None. > - Following configs should be set as: > *"hive.server2.enable.doAs"* = "true" > *"hive.security.authorization.enabled"* = "false", and > - Following configs should be deleted >*"hive.security.authorization.manager"* >*"hive.security.authenticator.manager"* >*"hive.conf.restricted.list"* > Also, if *hive-env/hive_security_authorization* is selected as *'sqlstdauth'* > or *'ranger'*, the following configs should be set as: > - "hive.conf.restricted.list" = > "hive.security.authenticator.manager,hive.security.authorization.manager,hive.security.metastore.authorization.manager, > > hive.security.metastore.authenticator.manager,hive.users.in.admin.role,hive.server2.xsrf.filter.enabled,hive.security.authorization.enabled" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19056) Add two new options from Ambari to LlapServiceDriver. (1). --skiphadoopversion (2). --skiphbasecp
[
https://issues.apache.org/jira/browse/AMBARI-19056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843421#comment-15843421
]
Swapan Shridhar commented on AMBARI-19056:
--
commit:
branch-2.5:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
trunk:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
> Add two new options from Ambari to LlapServiceDriver. (1).
> --skiphadoopversion (2). --skiphbasecp
> --
>
> Key: AMBARI-19056
> URL: https://issues.apache.org/jira/browse/AMBARI-19056
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19056.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19116) Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
[
https://issues.apache.org/jira/browse/AMBARI-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19116:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
> --
>
> Key: AMBARI-19116
> URL: https://issues.apache.org/jira/browse/AMBARI-19116
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19116.patch
>
>
> - Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
> hive/HiveServer2.
> Required:
> - Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
> concurrency.
> {code}
> = min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * RAM>)
> {code}
> *Side fix:* Also, updated "hive.llap.daemon.queue.name" and
> "hive.server2.tez.default.queues" config values to one of the existing leaf
> queues, in case of HSI being turned on and config values have queue names
> which no more exist. The scenario can happen when, say :
> - HSI was ON and the above 2 configs has queue name 'XYZ'.
> - HSI was then turned off.
> - Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
> - The above configs without this fix will otherwise show stale/non-existing
> queue name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19056) Add two new options from Ambari to LlapServiceDriver. (1). --skiphadoopversion (2). --skiphbasecp
[ https://issues.apache.org/jira/browse/AMBARI-19056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19056: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add two new options from Ambari to LlapServiceDriver. (1). > --skiphadoopversion (2). --skiphbasecp > -- > > Key: AMBARI-19056 > URL: https://issues.apache.org/jira/browse/AMBARI-19056 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19056.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19138) Option for getting heap dump for Hive and Tez services.
[
https://issues.apache.org/jira/browse/AMBARI-19138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843417#comment-15843417
]
Swapan Shridhar commented on AMBARI-19138:
--
commit:
branch-2.5:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
trunk:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
> Option for getting heap dump for Hive and Tez services.
> ---
>
> Key: AMBARI-19138
> URL: https://issues.apache.org/jira/browse/AMBARI-19138
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19138.patch
>
>
> We need to add the heap dump option for:
> - All Hive services (Hive1/HiveServer2, Hive2/HiveServer2 and Metastore):
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option appended to "Advance hive-env" -> hive-env-template ->
> HADOOP_CLIENT_OPTS environment variable
> - HSI YARN jobs:
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option added to "Advanced hive-interactive-env" -> Llap app java opts. Logs
> will be generated at: /<'Configurable location
> provided'>/java_.hprof on the nodes that failed with OOM.
> - Tez component:
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option added to tez.am.launch.cmd-opts for AM OOM and
> tez.task.launch.cmd-opts for task OOM.
> ** 'Configurable location provided' should be one config where user can
> change the location and consumable by all others.
> Further, whether to keep the heap dump option ENABLED or DISABLED should be
> configurable via Ambari. [~carter] to confirm for this. By default, option
> should be DISABLED.
> ** ENABLING/DISABLING of option will require the above components
> RESATARt for change to take effect.
> ** permissions for dump file can be 600 for :.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19060) Update the HiveServer config values if Security Authorization chosen is None.
[
https://issues.apache.org/jira/browse/AMBARI-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843420#comment-15843420
]
Swapan Shridhar commented on AMBARI-19060:
--
commit:
branch-2.5:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
trunk:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
> Update the HiveServer config values if Security Authorization chosen is None.
> -
>
> Key: AMBARI-19060
> URL: https://issues.apache.org/jira/browse/AMBARI-19060
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19060.patch
>
>
> - When hive-env/hive_security_authorization chosen value is None.
> - Following configs should be set as:
> *"hive.server2.enable.doAs"* = "true"
> *"hive.security.authorization.enabled"* = "false", and
> - Following configs should be deleted
>*"hive.security.authorization.manager"*
>*"hive.security.authenticator.manager"*
>*"hive.conf.restricted.list"*
> Also, if *hive-env/hive_security_authorization* is selected as *'sqlstdauth'*
> or *'ranger'*, the following configs should be set as:
> - "hive.conf.restricted.list" =
> "hive.security.authenticator.manager,hive.security.authorization.manager,hive.security.metastore.authorization.manager,
>
> hive.security.metastore.authenticator.manager,hive.users.in.admin.role,hive.server2.xsrf.filter.enabled,hive.security.authorization.enabled"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19116) Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
[
https://issues.apache.org/jira/browse/AMBARI-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843419#comment-15843419
]
Swapan Shridhar commented on AMBARI-19116:
--
commit:
branch-2.5:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
trunk:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
> Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
> --
>
> Key: AMBARI-19116
> URL: https://issues.apache.org/jira/browse/AMBARI-19116
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19116.patch
>
>
> - Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
> hive/HiveServer2.
> Required:
> - Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
> concurrency.
> {code}
> = min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * RAM>)
> {code}
> *Side fix:* Also, updated "hive.llap.daemon.queue.name" and
> "hive.server2.tez.default.queues" config values to one of the existing leaf
> queues, in case of HSI being turned on and config values have queue names
> which no more exist. The scenario can happen when, say :
> - HSI was ON and the above 2 configs has queue name 'XYZ'.
> - HSI was then turned off.
> - Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
> - The above configs without this fix will otherwise show stale/non-existing
> queue name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18963) Convert config 'hive.llap.io.memory.size' value from MB to Bytes before writing it to hive-site.xml
[
https://issues.apache.org/jira/browse/AMBARI-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843415#comment-15843415
]
Swapan Shridhar commented on AMBARI-18963:
--
commit:
branch-2.5:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
trunk:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
> Convert config 'hive.llap.io.memory.size' value from MB to Bytes before
> writing it to hive-site.xml
> ---
>
> Key: AMBARI-18963
> URL: https://issues.apache.org/jira/browse/AMBARI-18963
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18963.patch
>
>
> - Currently, we calculate config 'hive.llap.io.memory.size' value in MB.
> - We end up writing the config value in MB units to hive-site.xml.
> *Expected:*
> - Value written in hive-site.xml should be in Bytes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19143) Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'.
[
https://issues.apache.org/jira/browse/AMBARI-19143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843416#comment-15843416
]
Swapan Shridhar commented on AMBARI-19143:
--
commit:
branch-2.5:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
trunk:
{code}
commit 8552345deee7e6d366571a4c926a3093f7a7492a
Author: Sumit Mohanty
Date: Sun Dec 11 11:15:46 2016 -0800
AMBARI-18901. LLAP integration enhancements (Swapan Sridhar via smohanty)
{code}
> Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'.
> -
>
> Key: AMBARI-19143
> URL: https://issues.apache.org/jira/browse/AMBARI-19143
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19143.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18954) Use 'Number of LLAP Nodes' selected as the driver for LLAP config calculations.
[ https://issues.apache.org/jira/browse/AMBARI-18954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18954: - Resolution: Fixed Status: Resolved (was: Patch Available) > Use 'Number of LLAP Nodes' selected as the driver for LLAP config > calculations. > --- > > Key: AMBARI-18954 > URL: https://issues.apache.org/jira/browse/AMBARI-18954 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18901.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
