[jira] [Updated] (AMBARI-18596) rpm command broken on utility project
[
https://issues.apache.org/jira/browse/AMBARI-18596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-18596:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk, commit 6951da4d531f9f12f0a0e1e8668ab8f7ba0557d2
branch-2.5, commit 05cb5e8cfc24d56a486bad65554956d1bd1f442b
> rpm command broken on utility project
> -
>
> Key: AMBARI-18596
> URL: https://issues.apache.org/jira/browse/AMBARI-18596
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-18596.branch-2.5.patch, AMBARI-18596.trunk.patch
>
>
> The following command to build RPMs is failing because the utility project
> does not have a phase for it.
> {noformat}mvn -B -am clean package rpm:rpm -DskipTests -Dpython.ver="python
> >= 2.6" -pl
> ambari-admin,ambari-agent,utility,ambari-server,ambari-web,ambari-views{noformat}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main ... SUCCESS [1.034s]
> [INFO] Apache Ambari Project POM . SUCCESS [0.064s]
> [INFO] Ambari Web SUCCESS [1:58.669s]
> [INFO] Ambari Views .. SUCCESS [1.403s]
> [INFO] Ambari Admin View . SUCCESS [1:13.669s]
> [INFO] utility ... FAILURE [2.306s]
> [INFO] ambari-metrics SKIPPED
> [INFO] Ambari Metrics Common . SKIPPED
> [INFO] Ambari Server . SKIPPED
> [INFO] Ambari Agent .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3:17.814s
> [INFO] Finished at: Wed Oct 12 12:48:37 UTC 2016
> [INFO] Final Memory: 35M/563M
> [INFO]
>
> [ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1.5:rpm
> (default-cli) on project utility: The parameters 'sourceEncoding', 'group'
> for goal org.codehaus.mojo:rpm-maven-plugin:2.1.5:rpm are missing or invalid
> -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18573) Migration to Bootstrap3 framework
[ https://issues.apache.org/jira/browse/AMBARI-18573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576597#comment-15576597 ] Hudson commented on AMBARI-18573: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5804 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5804/]) AMBARI-18573. Migration to Bootstrap3 framework (akovalenko) (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2a77e39ca78d157c3286a317325ac6cba03670cb]) * (edit) ambari-web/test/views/main/admin/highAvailability/progress_view_test.js * (edit) ambari-web/app/utils/hosts.js * (edit) ambari-web/app/templates/main/admin/highAvailability/hawq/addStandby/wizard.hbs * (edit) ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs * (edit) ambari-web/app/templates/main/service/widgets/create/step2_template.hbs * (edit) ambari-web/app/views/main/admin/highAvailability/resourceManager/step4_view.js * (edit) ambari-web/app/templates/common/time_range.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/resourceManager/step3.hbs * (edit) ambari-web/app/templates/main/service/reassign/step3.hbs * (edit) ambari-web/app/mixins/wizard/wizardProgressPageView.js * (edit) ambari-web/app/routes/rm_high_availability_routes.js * (edit) ambari-web/app/templates/main/admin/kerberos/notify_security_off_popup.hbs * (edit) ambari-web/app/templates/installer.hbs * (edit) ambari-web/app/templates/common/log_tail.hbs * (edit) ambari-web/app/templates/main/admin/kerberos/step1.hbs * (edit) ambari-web/app/templates/common/host_progress_popup_footer.hbs * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs * (edit) ambari-web/app/views/main/admin/highAvailability/hawq/removeStandby/step3_view.js * (edit) ambari-web/app/templates/common/modal_popups/hosts_table_list_popup.hbs * (edit) ambari-web/test/views/common/configs/widgets/config_widget_view_test.js * (edit) ambari-web/vendor/scripts/ember-latest.js * (edit) ambari-web/app/views/wizard/step1_view.js * (edit) ambari-web/app/controllers/main/alerts/alert_definitions_actions_controller.js * (edit) ambari-web/app/utils/load_timer.js * (edit) ambari-web/app/templates/main/alerts/configs/alert_config_threshold.hbs * (edit) ambari-web/app/views/common/configs/widgets/label_config_widget_view.js * (edit) ambari-web/app/templates/common/selectable_popup.hbs * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_column.hbs * (edit) ambari-web/app/templates/main.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/resourceManager/wizard.hbs * (edit) ambari-web/app/templates/common/custom_date_popup.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/nameNode/rollbackHA/rollback_wizard.hbs * (edit) ambari-web/vendor/scripts/bootstrap-datepicker.js * (edit) ambari-web/app/templates/main/admin/highAvailability/hawq/removeStandby/step2.hbs * (edit) ambari-web/app/templates/main/dashboard/widgets/cluster_metrics.hbs * (edit) ambari-web/app/templates/main/service/services/hdfs.hbs * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js * (edit) ambari-web/app/data/host/categories.js * (edit) ambari-web/app/templates/wizard/step3/step3_host_warnings_popup.hbs * (add) ambari-web/app/styles/bootstrap_overrides.less * (edit) ambari-web/app/templates/main/dashboard/config_history.hbs * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/templates/main/service/services/oozie.hbs * (edit) ambari-web/app/routes/add_host_routes.js * (edit) ambari-web/app/templates/common/configs/widgets/controls.hbs * (delete) ambari-web/vendor/scripts/jquery-1.7.2.min.js * (edit) ambari-web/app/templates/common/rolling_restart_view.hbs * (edit) ambari-web/app/templates/main/host/combo_search_box.hbs * (edit) ambari-web/app/templates/common/configs/service_config_wizard.hbs * (edit) ambari-web/app/styles/log_file_search.less * (edit) ambari-web/vendor/scripts/bootstrap.js * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/templates/common/filter_combobox.hbs * (edit) ambari-web/app/templates/main/service/manage_configuration_groups_popup.hbs * (edit) ambari-web/app/styles/config_history_flow.less * (add) ambari-web/vendor/fonts/glyphicons-halflings-regular.eot * (add) ambari-web/app/templates/common/configs/widgets/service_config_password_field.hbs * (edit) ambari-web/app/templates/wizard/step6/step6_issues_popup.hbs * (edit) ambari-web/app/templates/common/widget/number_widget.hbs * (edit) ambari-web/app/templates/wizard/step1/vdf_upload.hbs * (edit) ambari-web/app/views/main/service/reassign/step6_view.js * (edit) ambari-web/app/templates/common/form/check_db_connection.hbs * (edit) ambari-web/app/templates/main/service/widgets/edit.hbs * (edit) ambari-web/app/templates/main/host/rack_id_popup.hbs * (edit) ambari-web/app/styles/widgets.less * (edit)
[jira] [Updated] (AMBARI-18573) Migration to Bootstrap3 framework
[ https://issues.apache.org/jira/browse/AMBARI-18573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18573: - Resolution: Fixed Status: Resolved (was: Patch Available) > Migration to Bootstrap3 framework > - > > Key: AMBARI-18573 > URL: https://issues.apache.org/jira/browse/AMBARI-18573 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: trunk > > Attachments: AMBARI-18573.patch > > > Migrate from Bootstrap2 to Bootstrap3 framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18604) Workflow Designer View: Filtering suggestion for Status on the Workflow Dashboard does not include all status options
[ https://issues.apache.org/jira/browse/AMBARI-18604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18604: Fix Version/s: 2.5.0 Status: Patch Available (was: In Progress) > Workflow Designer View: Filtering suggestion for Status on the Workflow > Dashboard does not include all status options > - > > Key: AMBARI-18604 > URL: https://issues.apache.org/jira/browse/AMBARI-18604 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18604.patch > > > The workflow designer view dashboard allows filtering of workflows based on > Status, Name and User. > When filtering by Status, it does not offer PREP status as a suggestion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18604) Workflow Designer View: Filtering suggestion for Status on the Workflow Dashboard does not include all status options
[ https://issues.apache.org/jira/browse/AMBARI-18604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18604: Attachment: AMBARI-18604.patch > Workflow Designer View: Filtering suggestion for Status on the Workflow > Dashboard does not include all status options > - > > Key: AMBARI-18604 > URL: https://issues.apache.org/jira/browse/AMBARI-18604 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18604.patch > > > The workflow designer view dashboard allows filtering of workflows based on > Status, Name and User. > When filtering by Status, it does not offer PREP status as a suggestion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18573) Migration to Bootstrap3 framework
[ https://issues.apache.org/jira/browse/AMBARI-18573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576481#comment-15576481 ] Aleksandr Kovalenko commented on AMBARI-18573: -- committed to trunk > Migration to Bootstrap3 framework > - > > Key: AMBARI-18573 > URL: https://issues.apache.org/jira/browse/AMBARI-18573 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: trunk > > Attachments: AMBARI-18573.patch > > > Migrate from Bootstrap2 to Bootstrap3 framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18596) rpm command broken on utility project
[
https://issues.apache.org/jira/browse/AMBARI-18596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576462#comment-15576462
]
Hudson commented on AMBARI-18596:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5803 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5803/])
AMBARI-18596. rpm command broken on utility project (alejandro) (afernandez:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6951da4d531f9f12f0a0e1e8668ab8f7ba0557d2])
* (edit) utility/pom.xml
> rpm command broken on utility project
> -
>
> Key: AMBARI-18596
> URL: https://issues.apache.org/jira/browse/AMBARI-18596
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-18596.branch-2.5.patch, AMBARI-18596.trunk.patch
>
>
> The following command to build RPMs is failing because the utility project
> does not have a phase for it.
> {noformat}mvn -B -am clean package rpm:rpm -DskipTests -Dpython.ver="python
> >= 2.6" -pl
> ambari-admin,ambari-agent,utility,ambari-server,ambari-web,ambari-views{noformat}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main ... SUCCESS [1.034s]
> [INFO] Apache Ambari Project POM . SUCCESS [0.064s]
> [INFO] Ambari Web SUCCESS [1:58.669s]
> [INFO] Ambari Views .. SUCCESS [1.403s]
> [INFO] Ambari Admin View . SUCCESS [1:13.669s]
> [INFO] utility ... FAILURE [2.306s]
> [INFO] ambari-metrics SKIPPED
> [INFO] Ambari Metrics Common . SKIPPED
> [INFO] Ambari Server . SKIPPED
> [INFO] Ambari Agent .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3:17.814s
> [INFO] Finished at: Wed Oct 12 12:48:37 UTC 2016
> [INFO] Final Memory: 35M/563M
> [INFO]
>
> [ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1.5:rpm
> (default-cli) on project utility: The parameters 'sourceEncoding', 'group'
> for goal org.codehaus.mojo:rpm-maven-plugin:2.1.5:rpm are missing or invalid
> -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18604) Workflow Designer View: Filtering suggestion for Status on the Workflow Dashboard does not include all status options
[
https://issues.apache.org/jira/browse/AMBARI-18604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576645#comment-15576645
]
Hadoop QA commented on AMBARI-18604:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12833440/AMBARI-18604.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/wfmanager/src/main/resources/ui
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8879//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8879//console
This message is automatically generated.
> Workflow Designer View: Filtering suggestion for Status on the Workflow
> Dashboard does not include all status options
> -
>
> Key: AMBARI-18604
> URL: https://issues.apache.org/jira/browse/AMBARI-18604
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-18604.patch
>
>
> The workflow designer view dashboard allows filtering of workflows based on
> Status, Name and User.
> When filtering by Status, it does not offer PREP status as a suggestion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18597) Rename service to "Microsoft R Server" and component to "Microsoft R Node Client"
[ https://issues.apache.org/jira/browse/AMBARI-18597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18597: --- Attachment: AMBARI-18597-rename-to-node-client.patch patch with fix > Rename service to "Microsoft R Server" and component to "Microsoft R Node > Client" > - > > Key: AMBARI-18597 > URL: https://issues.apache.org/jira/browse/AMBARI-18597 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Critical > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18597-rename-to-node-client.patch > > > Rename service to "Microsoft R Server" and component to "Microsoft R Node > Client" in the Microsoft R management pack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[
https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15574954#comment-15574954
]
Hadoop QA commented on AMBARI-18423:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12833259/AMBARI-18423_1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server ambari-web:
org.apache.ambari.server.state.cluster.ClusterDeadlockTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8874//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8874//console
This message is automatically generated.
> Support creating/editing alert target which notification_type is
> ALERT_SCRIPT in web client
>
>
> Key: AMBARI-18423
> URL: https://issues.apache.org/jira/browse/AMBARI-18423
> Project: Ambari
> Issue Type: Improvement
> Components: alerts, ambari-web
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: 2.5.0
>
> Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch,
> create_alert_notification.png, disabled_alert_scirpt_notification.png,
> edit_alert_notification.png, enabled_alert_scirpt_notification.png
>
>
> Ambari now only support creating/editing alert notifications of type
> EMAIL/SNMP in web client.
> This patch aims to support another notification type:ALERT_SCRIPT
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18567) Cannot start Oozie if WebHDFS is disabled
[
https://issues.apache.org/jira/browse/AMBARI-18567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15574882#comment-15574882
]
Hudson commented on AMBARI-18567:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #146 (See
[https://builds.apache.org/job/Ambari-branch-2.5/146/])
AMBARI-18567. Cannot start Oozie if WebHDFS is disabled. (Attila (stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=827fc5bc2c4e7d0b56ed9b493d0a88cde9f7c7a9])
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py
> Cannot start Oozie if WebHDFS is disabled
> -
>
> Key: AMBARI-18567
> URL: https://issues.apache.org/jira/browse/AMBARI-18567
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18567.patch
>
>
> If WebHDFS is disabled, Oozie cannot be started due to missing import in
> service script.
> {noformat}
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 145, in oozie_service
> hdfs_share_dir_exists = shell.call(format("{kinit_if_needed} hadoop
> --config {hadoop_conf_dir} dfs -ls {hdfs_share_dir} | awk 'BEGIN {{count=0;}}
> /share/ {{count++}} END {{if (count > 0) {{exit 0}} else {{exit 1'"),
> NameError: global name 'shell' is not defined
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-17981: -- Status: Patch Available (was: Open) > Integrate Druid With Ambari > --- > > Key: AMBARI-17981 > URL: https://issues.apache.org/jira/browse/AMBARI-17981 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nishant Bangarwa > Labels: features > Attachments: ambari-17981.patch > > > This task includes adding support for druid cluster provisioning via Ambari. > Details about Druid cluster design and different node types are present here > - > http://druid.io/docs/latest/design/design.html > In general, Druid can be defined as a service in HDP which has following > components - > 1) Coordinator > 2) Overlord > 3) Historical > 4) Broker > 5) Middlemanager > > Druid also has external dependencies on following > 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster > 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS. > 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a > mysql instance provisioned by ambari itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18567) Cannot start Oozie if WebHDFS is disabled
[
https://issues.apache.org/jira/browse/AMBARI-18567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-18567:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed.
trunk: 78f43507f883f527f41c6a3ab71ff40bbd433647
branch-2.5: 827fc5bc2c4e7d0b56ed9b493d0a88cde9f7c7a9
branch-2.4: 559a12030ff41ee3f14b929a7e230994d2c6bcad
> Cannot start Oozie if WebHDFS is disabled
> -
>
> Key: AMBARI-18567
> URL: https://issues.apache.org/jira/browse/AMBARI-18567
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18567.patch
>
>
> If WebHDFS is disabled, Oozie cannot be started due to missing import in
> service script.
> {noformat}
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 145, in oozie_service
> hdfs_share_dir_exists = shell.call(format("{kinit_if_needed} hadoop
> --config {hadoop_conf_dir} dfs -ls {hdfs_share_dir} | awk 'BEGIN {{count=0;}}
> /share/ {{count++}} END {{if (count > 0) {{exit 0}} else {{exit 1'"),
> NameError: global name 'shell' is not defined
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18597) Rename service to "Microsoft R Server" and component to "Microsoft R Node Client"
[ https://issues.apache.org/jira/browse/AMBARI-18597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18597: --- Status: Patch Available (was: Open) > Rename service to "Microsoft R Server" and component to "Microsoft R Node > Client" > - > > Key: AMBARI-18597 > URL: https://issues.apache.org/jira/browse/AMBARI-18597 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Critical > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18597-rename-to-node-client.patch > > > Rename service to "Microsoft R Server" and component to "Microsoft R Node > Client" in the Microsoft R management pack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18597) Rename service to "Microsoft R Server" and component to "Microsoft R Node Client"
[ https://issues.apache.org/jira/browse/AMBARI-18597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18597: --- Fix Version/s: trunk > Rename service to "Microsoft R Server" and component to "Microsoft R Node > Client" > - > > Key: AMBARI-18597 > URL: https://issues.apache.org/jira/browse/AMBARI-18597 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Critical > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18597-rename-to-node-client.patch > > > Rename service to "Microsoft R Server" and component to "Microsoft R Node > Client" in the Microsoft R management pack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-17981: -- Status: Open (was: Patch Available) > Integrate Druid With Ambari > --- > > Key: AMBARI-17981 > URL: https://issues.apache.org/jira/browse/AMBARI-17981 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nishant Bangarwa > Labels: features > Attachments: ambari-17981.patch > > > This task includes adding support for druid cluster provisioning via Ambari. > Details about Druid cluster design and different node types are present here > - > http://druid.io/docs/latest/design/design.html > In general, Druid can be defined as a service in HDP which has following > components - > 1) Coordinator > 2) Overlord > 3) Historical > 4) Broker > 5) Middlemanager > > Druid also has external dependencies on following > 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster > 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS. > 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a > mysql instance provisioned by ambari itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-17981: -- Attachment: (was: ambari-17981.patch) > Integrate Druid With Ambari > --- > > Key: AMBARI-17981 > URL: https://issues.apache.org/jira/browse/AMBARI-17981 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nishant Bangarwa > Labels: features > Attachments: ambari-17981.patch > > > This task includes adding support for druid cluster provisioning via Ambari. > Details about Druid cluster design and different node types are present here > - > http://druid.io/docs/latest/design/design.html > In general, Druid can be defined as a service in HDP which has following > components - > 1) Coordinator > 2) Overlord > 3) Historical > 4) Broker > 5) Middlemanager > > Druid also has external dependencies on following > 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster > 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS. > 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a > mysql instance provisioned by ambari itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17981) Integrate Druid With Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-17981: -- Attachment: ambari-17981.patch > Integrate Druid With Ambari > --- > > Key: AMBARI-17981 > URL: https://issues.apache.org/jira/browse/AMBARI-17981 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nishant Bangarwa > Labels: features > Attachments: ambari-17981.patch > > > This task includes adding support for druid cluster provisioning via Ambari. > Details about Druid cluster design and different node types are present here > - > http://druid.io/docs/latest/design/design.html > In general, Druid can be defined as a service in HDP which has following > components - > 1) Coordinator > 2) Overlord > 3) Historical > 4) Broker > 5) Middlemanager > > Druid also has external dependencies on following > 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster > 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS. > 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a > mysql instance provisioned by ambari itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18581) Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag
[ https://issues.apache.org/jira/browse/AMBARI-18581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-18581: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag > - > > Key: AMBARI-18581 > URL: https://issues.apache.org/jira/browse/AMBARI-18581 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-18581.patch > > > Oozie service script never executes "sysprepped" branch, because it looks for > sysprep_skip_copy_oozie_share_lib_to_hdfs flag in the wrong place. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18567) Cannot start Oozie if WebHDFS is disabled
[
https://issues.apache.org/jira/browse/AMBARI-18567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15574899#comment-15574899
]
Hudson commented on AMBARI-18567:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5799 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5799/])
AMBARI-18567. Cannot start Oozie if WebHDFS is disabled. (Attila (stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=78f43507f883f527f41c6a3ab71ff40bbd433647])
* (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py
> Cannot start Oozie if WebHDFS is disabled
> -
>
> Key: AMBARI-18567
> URL: https://issues.apache.org/jira/browse/AMBARI-18567
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18567.patch
>
>
> If WebHDFS is disabled, Oozie cannot be started due to missing import in
> service script.
> {noformat}
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
> line 145, in oozie_service
> hdfs_share_dir_exists = shell.call(format("{kinit_if_needed} hadoop
> --config {hadoop_conf_dir} dfs -ls {hdfs_share_dir} | awk 'BEGIN {{count=0;}}
> /share/ {{count++}} END {{if (count > 0) {{exit 0}} else {{exit 1'"),
> NameError: global name 'shell' is not defined
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18596) rpm command broken on utility project
[
https://issues.apache.org/jira/browse/AMBARI-18596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576822#comment-15576822
]
Hudson commented on AMBARI-18596:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #151 (See
[https://builds.apache.org/job/Ambari-branch-2.5/151/])
AMBARI-18596. rpm command broken on utility project (alejandro) (afernandez:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=05cb5e8cfc24d56a486bad65554956d1bd1f442b])
* (edit) utility/pom.xml
> rpm command broken on utility project
> -
>
> Key: AMBARI-18596
> URL: https://issues.apache.org/jira/browse/AMBARI-18596
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-18596.branch-2.5.patch, AMBARI-18596.trunk.patch
>
>
> The following command to build RPMs is failing because the utility project
> does not have a phase for it.
> {noformat}mvn -B -am clean package rpm:rpm -DskipTests -Dpython.ver="python
> >= 2.6" -pl
> ambari-admin,ambari-agent,utility,ambari-server,ambari-web,ambari-views{noformat}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main ... SUCCESS [1.034s]
> [INFO] Apache Ambari Project POM . SUCCESS [0.064s]
> [INFO] Ambari Web SUCCESS [1:58.669s]
> [INFO] Ambari Views .. SUCCESS [1.403s]
> [INFO] Ambari Admin View . SUCCESS [1:13.669s]
> [INFO] utility ... FAILURE [2.306s]
> [INFO] ambari-metrics SKIPPED
> [INFO] Ambari Metrics Common . SKIPPED
> [INFO] Ambari Server . SKIPPED
> [INFO] Ambari Agent .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3:17.814s
> [INFO] Finished at: Wed Oct 12 12:48:37 UTC 2016
> [INFO] Final Memory: 35M/563M
> [INFO]
>
> [ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1.5:rpm
> (default-cli) on project utility: The parameters 'sourceEncoding', 'group'
> for goal org.codehaus.mojo:rpm-maven-plugin:2.1.5:rpm are missing or invalid
> -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18605) Hive Settings Page: Mouse-over on "HiveServer2 Interactive host" label repeats same message twice
[ https://issues.apache.org/jira/browse/AMBARI-18605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15577135#comment-15577135 ] Hudson commented on AMBARI-18605: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #153 (See [https://builds.apache.org/job/Ambari-branch-2.5/153/]) AMBARI-18605. Hive Settings Page: Mouse-over on "HiveServer2 Interactive (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ac65566425e2283fa1f937ab4a00af856d449c3b]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml > Hive Settings Page: Mouse-over on "HiveServer2 Interactive host" label > repeats same message twice > - > > Key: AMBARI-18605 > URL: https://issues.apache.org/jira/browse/AMBARI-18605 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-18605.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18605) Hive Settings Page: Mouse-over on "HiveServer2 Interactive host" label repeats same message twice
[ https://issues.apache.org/jira/browse/AMBARI-18605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15577142#comment-15577142 ] Hudson commented on AMBARI-18605: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5806 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5806/]) AMBARI-18605. Hive Settings Page: Mouse-over on "HiveServer2 Interactive (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3417db944c909485ca0af54019b712cd509debc0]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml > Hive Settings Page: Mouse-over on "HiveServer2 Interactive host" label > repeats same message twice > - > > Key: AMBARI-18605 > URL: https://issues.apache.org/jira/browse/AMBARI-18605 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-18605.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18585) Set _HOST for Hbase Master principal in Kerberos enabled Ranger Hbase Plugin
[ https://issues.apache.org/jira/browse/AMBARI-18585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15577376#comment-15577376 ] Gautam Borad commented on AMBARI-18585: --- Committed to trunk : e8544ba49be24774a40b4e95da05ab4d7daeccda Committed to branch-2.4: b07c01fe08abd605f336fbc2509af6fd997d68a0 Committed to branch-2.5: a5f8a903340897a5d0b7369252f3849dec5f4c14 > Set _HOST for Hbase Master principal in Kerberos enabled Ranger Hbase Plugin > > > Key: AMBARI-18585 > URL: https://issues.apache.org/jira/browse/AMBARI-18585 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0, 2.4.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18585.patch > > > Need to update hbase plugin repo config for master principal to have a _HOST > instead of a specific node. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18585) Set _HOST for Hbase Master principal in Kerberos enabled Ranger Hbase Plugin
[ https://issues.apache.org/jira/browse/AMBARI-18585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated AMBARI-18585: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Set _HOST for Hbase Master principal in Kerberos enabled Ranger Hbase Plugin > > > Key: AMBARI-18585 > URL: https://issues.apache.org/jira/browse/AMBARI-18585 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0, 2.4.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18585.patch > > > Need to update hbase plugin repo config for master principal to have a _HOST > instead of a specific node. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18585) Set _HOST for Hbase Master principal in Kerberos enabled Ranger Hbase Plugin
[ https://issues.apache.org/jira/browse/AMBARI-18585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15577432#comment-15577432 ] Hudson commented on AMBARI-18585: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #154 (See [https://builds.apache.org/job/Ambari-branch-2.5/154/]) AMBARI-18585 Set _HOST for Hbase Master principal in Kerberos (gautam: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a5f8a903340897a5d0b7369252f3849dec5f4c14]) * (edit) ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py > Set _HOST for Hbase Master principal in Kerberos enabled Ranger Hbase Plugin > > > Key: AMBARI-18585 > URL: https://issues.apache.org/jira/browse/AMBARI-18585 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0, 2.4.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18585.patch > > > Need to update hbase plugin repo config for master principal to have a _HOST > instead of a specific node. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18595) Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
[
https://issues.apache.org/jira/browse/AMBARI-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575059#comment-15575059
]
Hadoop QA commented on AMBARI-18595:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12833246/AMBARI-18595.v0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8876//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8876//console
This message is automatically generated.
> Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
>
>
> Key: AMBARI-18595
> URL: https://issues.apache.org/jira/browse/AMBARI-18595
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
> Environment: Microsoft Windows 10
> - Microsoft Edge
> - Microsoft Internet Explorer 11
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-18595.v0.patch, Capture.PNG
>
>
> Icons do not display in any page as shown in the screen-shot attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18598) S020 error with Hive view and Mysal
Guillaume created AMBARI-18598:
--
Summary: S020 error with Hive view and Mysal
Key: AMBARI-18598
URL: https://issues.apache.org/jira/browse/AMBARI-18598
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.1
Environment: centos 7, HDP2.5
Reporter: Guillaume
Using hdp2.5 (ambari 2.4.1) with a Hive view, a table has been created by an
external tool (hdfs connector from confluent.io). I can see the table metadata
(column names and type) but trying to get data gives me the error:
{quote}
S020 Data storage error
[blahblah]
Caused by: javax.persistence.RollbackException: Exception [EclipseLink-4002]
(Eclipse Persistence Services - 2.6.2.v20151217-774c696):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
Table 'ambari.DS_JOBIMPL_4' doesn't exist
Error Code: 1146
[a lot more lines]
{quote}
Now I saw another answer giving a cut solution. This does not work for
me, as I then end up with a different error:
{quote}
S020 Data storage error
[blahblah]
Caused by: javax.persistence.RollbackException: Exception [EclipseLink-4002]
(Eclipse Persistence Services - 2.6.2.v20151217-774c696):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
Unknown column 'DS_guid' in 'field list'
Error Code: 1054
[a lot more lines]
{quote}
It looks to me like the answer is out of date.
I suppose the original reason still holds:
bq. ROOT CAUSE: This is a limitation with the Mysql DB itself with varchar
accounting to more than 75000 maximum row size where as the mysql DB can accept
only 65535 as its max value.
But I would love to understand a few things:
* Why does this still happen (I have seen a few commits already in ambari
trying to fix this)
* How can I regenerate the relevant CREATE statement
* Why sometimes is it DS_JOBIMPL_4, sometimes DS_JOBIMPL_8 and how can I be
sure that I am creating the right tables
* In which log file can I find the relevant failded CREATE statement
* Is there a way to fully avoid this
That's a lot of questions but it always happened to me, no matter which HDP
version so I would really love to go to the bottom of it.
Thanks,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18591) Hive Rolling Upgrade Is No Longer Supported In Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-18591: - Resolution: Fixed Status: Resolved (was: Patch Available) > Hive Rolling Upgrade Is No Longer Supported In Ambari > - > > Key: AMBARI-18591 > URL: https://issues.apache.org/jira/browse/AMBARI-18591 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18591.patch > > > HS2 RU expects all users to be using zookeeper based JDBC URLs. However, few > users are using these new Zookeeper discovery urls and they use the old > format, directly specifying the hostname and port number for the HS2 instance > it connects to. During RU, the HS2 port number changes and users using old > url have an outage. Hive needs to be able to support RU without changing the > port. > Due to too many Hive Client user outages as a result of the RU workflow for > HIve, the decision is to just change RU to bounce the HS2 process, knowing > that there will be down time and causing all active queries to fail. So the > runbook for the HS2 process will look like: > * We will no longer change the Hive port at all during either RU or EU. > * During an RU, we will present a message if Hive is present that indicates > that Hive is not rolling and it will be taken down. > * Run the Hive deregister command to remove the ZK entries for the Hive > Servers > * Hive will be shutdown, without draining, during an RU and a new instance > started up on the same port. > In addition, we need to remove the warnings that were added as part of > AMBARI-17319. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18596) rpm command broken on utility project
[
https://issues.apache.org/jira/browse/AMBARI-18596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575013#comment-15575013
]
Hadoop QA commented on AMBARI-18596:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12833249/AMBARI-18596.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in utility.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8875//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8875//console
This message is automatically generated.
> rpm command broken on utility project
> -
>
> Key: AMBARI-18596
> URL: https://issues.apache.org/jira/browse/AMBARI-18596
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-18596.branch-2.5.patch, AMBARI-18596.trunk.patch
>
>
> The following command to build RPMs is failing because the utility project
> does not have a phase for it.
> {noformat}mvn -B -am clean package rpm:rpm -DskipTests -Dpython.ver="python
> >= 2.6" -pl
> ambari-admin,ambari-agent,utility,ambari-server,ambari-web,ambari-views{noformat}
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main ... SUCCESS [1.034s]
> [INFO] Apache Ambari Project POM . SUCCESS [0.064s]
> [INFO] Ambari Web SUCCESS [1:58.669s]
> [INFO] Ambari Views .. SUCCESS [1.403s]
> [INFO] Ambari Admin View . SUCCESS [1:13.669s]
> [INFO] utility ... FAILURE [2.306s]
> [INFO] ambari-metrics SKIPPED
> [INFO] Ambari Metrics Common . SKIPPED
> [INFO] Ambari Server . SKIPPED
> [INFO] Ambari Agent .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3:17.814s
> [INFO] Finished at: Wed Oct 12 12:48:37 UTC 2016
> [INFO] Final Memory: 35M/563M
> [INFO]
>
> [ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1.5:rpm
> (default-cli) on project utility: The parameters 'sourceEncoding', 'group'
> for goal org.codehaus.mojo:rpm-maven-plugin:2.1.5:rpm are missing or invalid
> -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18594) AMBARI-18051 Breaks Stack Upgrade Checks
[
https://issues.apache.org/jira/browse/AMBARI-18594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Thorpe updated AMBARI-18594:
Resolution: Fixed
Fix Version/s: 2.4.2
2.5.0
Status: Resolved (was: Patch Available)
Change has been pushed into 2.4, 2.5 and trunk
> AMBARI-18051 Breaks Stack Upgrade Checks
>
>
> Key: AMBARI-18594
> URL: https://issues.apache.org/jira/browse/AMBARI-18594
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Tim Thorpe
>Priority: Blocker
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18594.patch
>
>
> AMBARI-18051 adds logic which breaks upgrades. The following adds:
> https://github.com/apache/ambari/commit/87423d64f54d896c62d1a9245eb03a97763e35a4#diff-5a960f81153cabb6a060631fd802d076R197
> {code}
> Map services =
> getManagementController().getAmbariMetaInfo().getServices(stackName,
> upgradePack.getTarget());
> {code}
> Which translates into {{getServices("HDP", "2.4.\*.\*")}}
> When attempting an upgrade, we now see this exception thrown and some of the
> upgrade checks do not run:
> {code}
> 2016-10-13 16:44:18,806 ERROR [ambari-client-thread-34]
> (PreUpgradeCheckResourceProvider.java:202) getResources() - Unable to
> register all the custom prechecks from the services
> org.apache.ambari.server.ParentObjectNotFoundException: Parent Stack Version
> resource doesn't exist. Stack data, Stack HDP 2.4.*.* is not found in Ambari
> metainfo. Stack data, Stack HDP 2.4.*.* is not found in Ambari metainfo
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.getServices(AmbariMetaInfo.java:529)
> at
> org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:198)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:398)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.PreUpgradeCheckService.getPreUpgradeChecks(PreUpgradeCheckService.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
>
[jira] [Commented] (AMBARI-18594) AMBARI-18051 Breaks Stack Upgrade Checks
[
https://issues.apache.org/jira/browse/AMBARI-18594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575580#comment-15575580
]
Tim Thorpe commented on AMBARI-18594:
-
[~jonathan.hurley] I have been trying to get all the changes related to custom
service support into one branch. I had planned on putting them in 2.5 but then
one related to this went in 2.4.
https://issues.apache.org/jira/browse/AMBARI-15538
This was the last item that I was aware of to help custom services be fully
integrated in the stack for role command order, stack advisor and upgrade.
> AMBARI-18051 Breaks Stack Upgrade Checks
>
>
> Key: AMBARI-18594
> URL: https://issues.apache.org/jira/browse/AMBARI-18594
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Tim Thorpe
>Priority: Blocker
> Fix For: 2.5.0
>
>
> AMBARI-18051 adds logic which breaks upgrades. The following adds:
> https://github.com/apache/ambari/commit/87423d64f54d896c62d1a9245eb03a97763e35a4#diff-5a960f81153cabb6a060631fd802d076R197
> {code}
> Map services =
> getManagementController().getAmbariMetaInfo().getServices(stackName,
> upgradePack.getTarget());
> {code}
> Which translates into {{getServices("HDP", "2.4.\*.\*")}}
> When attempting an upgrade, we now see this exception thrown and some of the
> upgrade checks do not run:
> {code}
> 2016-10-13 16:44:18,806 ERROR [ambari-client-thread-34]
> (PreUpgradeCheckResourceProvider.java:202) getResources() - Unable to
> register all the custom prechecks from the services
> org.apache.ambari.server.ParentObjectNotFoundException: Parent Stack Version
> resource doesn't exist. Stack data, Stack HDP 2.4.*.* is not found in Ambari
> metainfo. Stack data, Stack HDP 2.4.*.* is not found in Ambari metainfo
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.getServices(AmbariMetaInfo.java:529)
> at
> org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:198)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:398)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.PreUpgradeCheckService.getPreUpgradeChecks(PreUpgradeCheckService.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
[jira] [Commented] (AMBARI-18591) Hive Rolling Upgrade Is No Longer Supported In Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575462#comment-15575462 ] Hudson commented on AMBARI-18591: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #147 (See [https://builds.apache.org/job/Ambari-branch-2.5/147/]) AMBARI-18591 - Hive Rolling Upgrade Is No Longer Supported In Ambari (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4ae5b834d384356ac4dd061c97892ab918cb1abf]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/checks/HiveRollingPortChangeWarningTest.java * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml * (add) ambari-server/src/test/java/org/apache/ambari/server/checks/HiveNotRollingWarningTest.java * (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_upgrade.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml * (add) ambari-server/src/main/java/org/apache/ambari/server/checks/HiveNotRollingWarning.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * (delete) ambari-server/src/main/java/org/apache/ambari/server/checks/HiveRollingPortChangeWarning.java > Hive Rolling Upgrade Is No Longer Supported In Ambari > - > > Key: AMBARI-18591 > URL: https://issues.apache.org/jira/browse/AMBARI-18591 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18591.patch > > > HS2 RU expects all users to be using zookeeper based JDBC URLs. However, few > users are using these new Zookeeper discovery urls and they use the old > format, directly specifying the hostname and port number for the HS2 instance > it connects to. During RU, the HS2 port number changes and users using old > url have an outage. Hive needs to be able to support RU without changing the > port. > Due to too many Hive Client user outages as a result of the RU workflow for > HIve, the decision is to just change RU to bounce the HS2 process, knowing > that there will be down time and causing all active queries to fail. So the > runbook for the HS2 process will look like: > * We will no longer change the Hive port at all during either RU or EU. > * During an RU, we will present a message if Hive is present that indicates > that Hive is not rolling and it will be taken down. > * Run the Hive deregister command to remove the ZK entries for the Hive > Servers > * Hive will be shutdown, without draining, during an RU and a new instance > started up on the same port. > In addition, we need to remove the warnings that were added as part of > AMBARI-17319. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18594) AMBARI-18051 Breaks Stack Upgrade Checks
[
https://issues.apache.org/jira/browse/AMBARI-18594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Thorpe reassigned AMBARI-18594:
---
Assignee: Tim Thorpe
> AMBARI-18051 Breaks Stack Upgrade Checks
>
>
> Key: AMBARI-18594
> URL: https://issues.apache.org/jira/browse/AMBARI-18594
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Tim Thorpe
>Priority: Blocker
> Fix For: 2.5.0
>
>
> AMBARI-18051 adds logic which breaks upgrades. The following adds:
> https://github.com/apache/ambari/commit/87423d64f54d896c62d1a9245eb03a97763e35a4#diff-5a960f81153cabb6a060631fd802d076R197
> {code}
> Map services =
> getManagementController().getAmbariMetaInfo().getServices(stackName,
> upgradePack.getTarget());
> {code}
> Which translates into {{getServices("HDP", "2.4.\*.\*")}}
> When attempting an upgrade, we now see this exception thrown and some of the
> upgrade checks do not run:
> {code}
> 2016-10-13 16:44:18,806 ERROR [ambari-client-thread-34]
> (PreUpgradeCheckResourceProvider.java:202) getResources() - Unable to
> register all the custom prechecks from the services
> org.apache.ambari.server.ParentObjectNotFoundException: Parent Stack Version
> resource doesn't exist. Stack data, Stack HDP 2.4.*.* is not found in Ambari
> metainfo. Stack data, Stack HDP 2.4.*.* is not found in Ambari metainfo
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.getServices(AmbariMetaInfo.java:529)
> at
> org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:198)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:398)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.PreUpgradeCheckService.getPreUpgradeChecks(PreUpgradeCheckService.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
>
[jira] [Commented] (AMBARI-18591) Hive Rolling Upgrade Is No Longer Supported In Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575436#comment-15575436 ] Hudson commented on AMBARI-18591: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5800 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5800/]) AMBARI-18591 - Hive Rolling Upgrade Is No Longer Supported In Ambari (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9b0f631765f1e1c5855b95943c5cfb8c9cfff879]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml * (add) ambari-server/src/main/java/org/apache/ambari/server/checks/HiveNotRollingWarning.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * (delete) ambari-server/src/main/java/org/apache/ambari/server/checks/HiveRollingPortChangeWarning.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml * (delete) ambari-server/src/test/java/org/apache/ambari/server/checks/HiveRollingPortChangeWarningTest.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_upgrade.py * (add) ambari-server/src/test/java/org/apache/ambari/server/checks/HiveNotRollingWarningTest.java > Hive Rolling Upgrade Is No Longer Supported In Ambari > - > > Key: AMBARI-18591 > URL: https://issues.apache.org/jira/browse/AMBARI-18591 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18591.patch > > > HS2 RU expects all users to be using zookeeper based JDBC URLs. However, few > users are using these new Zookeeper discovery urls and they use the old > format, directly specifying the hostname and port number for the HS2 instance > it connects to. During RU, the HS2 port number changes and users using old > url have an outage. Hive needs to be able to support RU without changing the > port. > Due to too many Hive Client user outages as a result of the RU workflow for > HIve, the decision is to just change RU to bounce the HS2 process, knowing > that there will be down time and causing all active queries to fail. So the > runbook for the HS2 process will look like: > * We will no longer change the Hive port at all during either RU or EU. > * During an RU, we will present a message if Hive is present that indicates > that Hive is not rolling and it will be taken down. > * Run the Hive deregister command to remove the ZK entries for the Hive > Servers > * Hive will be shutdown, without draining, during an RU and a new instance > started up on the same port. > In addition, we need to remove the warnings that were added as part of > AMBARI-17319. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18594) AMBARI-18051 Breaks Stack Upgrade Checks
[
https://issues.apache.org/jira/browse/AMBARI-18594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Thorpe updated AMBARI-18594:
Fix Version/s: (was: 2.5.0)
trunk
Affects Version/s: (was: 2.5.0)
trunk
Status: Patch Available (was: Open)
> AMBARI-18051 Breaks Stack Upgrade Checks
>
>
> Key: AMBARI-18594
> URL: https://issues.apache.org/jira/browse/AMBARI-18594
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Tim Thorpe
>Priority: Blocker
> Fix For: trunk
>
> Attachments: AMBARI-18594.patch
>
>
> AMBARI-18051 adds logic which breaks upgrades. The following adds:
> https://github.com/apache/ambari/commit/87423d64f54d896c62d1a9245eb03a97763e35a4#diff-5a960f81153cabb6a060631fd802d076R197
> {code}
> Map services =
> getManagementController().getAmbariMetaInfo().getServices(stackName,
> upgradePack.getTarget());
> {code}
> Which translates into {{getServices("HDP", "2.4.\*.\*")}}
> When attempting an upgrade, we now see this exception thrown and some of the
> upgrade checks do not run:
> {code}
> 2016-10-13 16:44:18,806 ERROR [ambari-client-thread-34]
> (PreUpgradeCheckResourceProvider.java:202) getResources() - Unable to
> register all the custom prechecks from the services
> org.apache.ambari.server.ParentObjectNotFoundException: Parent Stack Version
> resource doesn't exist. Stack data, Stack HDP 2.4.*.* is not found in Ambari
> metainfo. Stack data, Stack HDP 2.4.*.* is not found in Ambari metainfo
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.getServices(AmbariMetaInfo.java:529)
> at
> org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:198)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:398)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.PreUpgradeCheckService.getPreUpgradeChecks(PreUpgradeCheckService.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
>
[jira] [Updated] (AMBARI-18594) AMBARI-18051 Breaks Stack Upgrade Checks
[
https://issues.apache.org/jira/browse/AMBARI-18594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Thorpe updated AMBARI-18594:
Attachment: AMBARI-18594.patch
This is a patch for trunk
> AMBARI-18051 Breaks Stack Upgrade Checks
>
>
> Key: AMBARI-18594
> URL: https://issues.apache.org/jira/browse/AMBARI-18594
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Tim Thorpe
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18594.patch
>
>
> AMBARI-18051 adds logic which breaks upgrades. The following adds:
> https://github.com/apache/ambari/commit/87423d64f54d896c62d1a9245eb03a97763e35a4#diff-5a960f81153cabb6a060631fd802d076R197
> {code}
> Map services =
> getManagementController().getAmbariMetaInfo().getServices(stackName,
> upgradePack.getTarget());
> {code}
> Which translates into {{getServices("HDP", "2.4.\*.\*")}}
> When attempting an upgrade, we now see this exception thrown and some of the
> upgrade checks do not run:
> {code}
> 2016-10-13 16:44:18,806 ERROR [ambari-client-thread-34]
> (PreUpgradeCheckResourceProvider.java:202) getResources() - Unable to
> register all the custom prechecks from the services
> org.apache.ambari.server.ParentObjectNotFoundException: Parent Stack Version
> resource doesn't exist. Stack data, Stack HDP 2.4.*.* is not found in Ambari
> metainfo. Stack data, Stack HDP 2.4.*.* is not found in Ambari metainfo
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.getServices(AmbariMetaInfo.java:529)
> at
> org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:198)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:398)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.PreUpgradeCheckService.getPreUpgradeChecks(PreUpgradeCheckService.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
>
[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message
[ https://issues.apache.org/jira/browse/AMBARI-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18600: Status: Patch Available (was: Open) > Workflow Designer View: When logs are empty, you see the spinner, instead of > a message > -- > > Key: AMBARI-18600 > URL: https://issues.apache.org/jira/browse/AMBARI-18600 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18600.patch > > > In the workflow designer view instance, if there is no log available for the > workflow, then the spinner is seen giving the impression that logs are still > being retrieved. This happens for all the logs, viz. the job log, error log > and audit log. > A message sould be displayed when there are no messages in the log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message
[ https://issues.apache.org/jira/browse/AMBARI-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18600: Status: Open (was: Patch Available) > Workflow Designer View: When logs are empty, you see the spinner, instead of > a message > -- > > Key: AMBARI-18600 > URL: https://issues.apache.org/jira/browse/AMBARI-18600 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18600.patch > > > In the workflow designer view instance, if there is no log available for the > workflow, then the spinner is seen giving the impression that logs are still > being retrieved. This happens for all the logs, viz. the job log, error log > and audit log. > A message sould be displayed when there are no messages in the log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18605) Hive Settings Page: Mouse-over on "HiveServer2 Interactive host" label repeats same message twice
[ https://issues.apache.org/jira/browse/AMBARI-18605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18605: Attachment: AMBARI-18605.patch > Hive Settings Page: Mouse-over on "HiveServer2 Interactive host" label > repeats same message twice > - > > Key: AMBARI-18605 > URL: https://issues.apache.org/jira/browse/AMBARI-18605 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-18605.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18605) Hive Settings Page: Mouse-over on "HiveServer2 Interactive host" label repeats same message twice
[ https://issues.apache.org/jira/browse/AMBARI-18605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18605: Status: Patch Available (was: Open) > Hive Settings Page: Mouse-over on "HiveServer2 Interactive host" label > repeats same message twice > - > > Key: AMBARI-18605 > URL: https://issues.apache.org/jira/browse/AMBARI-18605 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-18605.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18605) Hive Settings Page: Mouse-over on "HiveServer2 Interactive host" label repeats same message twice
Jaimin D Jetly created AMBARI-18605: --- Summary: Hive Settings Page: Mouse-over on "HiveServer2 Interactive host" label repeats same message twice Key: AMBARI-18605 URL: https://issues.apache.org/jira/browse/AMBARI-18605 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.4.0 Reporter: Jaimin D Jetly Assignee: Jaimin D Jetly Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18535) Ambari is not picking up the latest repo for HDP-2.4
[ https://issues.apache.org/jira/browse/AMBARI-18535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18535: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk and branch-2.5 96d66e0d41d49e67d11d5ea558c24d858f4b9577 > Ambari is not picking up the latest repo for HDP-2.4 > > > Key: AMBARI-18535 > URL: https://issues.apache.org/jira/browse/AMBARI-18535 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18535.v0.patch > > > During fresh deployment, if HDP-2.4 is chosen then Ambari does not default to > the latest 2.4 release, HDP-2.4.2. This is likely because VDF files do not > exist for HDP-2.4 release and the older mechanism of picking the latest repo > URL form the hdp_urlinfo.json does not work. HDP-2.4.0 is chosen where as the > latest is HDP-2.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18605) Hive Settings Page: Mouse-over on "HiveServer2 Interactive host" label repeats same message twice
[ https://issues.apache.org/jira/browse/AMBARI-18605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18605: Resolution: Fixed Status: Resolved (was: Patch Available) Received +1 on review board. Patch committed to trunk and branch-2.5 > Hive Settings Page: Mouse-over on "HiveServer2 Interactive host" label > repeats same message twice > - > > Key: AMBARI-18605 > URL: https://issues.apache.org/jira/browse/AMBARI-18605 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-18605.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18535) Ambari is not picking up the latest repo for HDP-2.4
[ https://issues.apache.org/jira/browse/AMBARI-18535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15577098#comment-15577098 ] Hudson commented on AMBARI-18535: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #152 (See [https://builds.apache.org/job/Ambari-branch-2.5/152/]) AMBARI-18535 Ambari is not picking up the latest repo for HDP-2.4 (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dc3e200cba9f8a99430b220efa0bea99f3b5b060]) * (edit) ambari-web/app/controllers/installer.js > Ambari is not picking up the latest repo for HDP-2.4 > > > Key: AMBARI-18535 > URL: https://issues.apache.org/jira/browse/AMBARI-18535 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18535.v0.patch > > > During fresh deployment, if HDP-2.4 is chosen then Ambari does not default to > the latest 2.4 release, HDP-2.4.2. This is likely because VDF files do not > exist for HDP-2.4 release and the older mechanism of picking the latest repo > URL form the hdp_urlinfo.json does not work. HDP-2.4.0 is chosen where as the > latest is HDP-2.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18603) Remove Unnecessary Locks Inside Of ServiceComponent Business Object Implementations
[
https://issues.apache.org/jira/browse/AMBARI-18603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576716#comment-15576716
]
Hadoop QA commented on AMBARI-18603:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12833435/AMBARI-18603.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/8881//console
This message is automatically generated.
> Remove Unnecessary Locks Inside Of ServiceComponent Business Object
> Implementations
> ---
>
> Key: AMBARI-18603
> URL: https://issues.apache.org/jira/browse/AMBARI-18603
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18603.patch
>
>
> Many of the business object implementations include needless locks which
> simply add the overhead and contention in larger clusters. Some examples of
> these are :
> - HostImpl
> -- get/set DisksInfo()
> -- get/set TotalMemBytes()
> - ServiceComponentHostImpl
> -- get/set MaintenanceState()
> -- get/set LastOpLastUpdateTime()
> These types of methods are found on other business classes as well, like
> {{ClusterImpl}} and {{ServiceImpl}}. Additionally, methods like
> {{convertToResponse()}} and {{debugDump()}} need not acquire locks since they
> are used mostly for serialization of data to the web client where the data
> will then immediately become stale anyway.
> The {{ServiceComponent}} business object should have the following work
> performed:
> - Remove locking around areas where its no longer required
> - Replace collections with thread-safe concurrent versions
> - Remove some reliance on state-full business objects (caches)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message
[
https://issues.apache.org/jira/browse/AMBARI-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576712#comment-15576712
]
Hadoop QA commented on AMBARI-18600:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12833439/AMBARI-18600.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/wfmanager/src/main/resources/ui
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8880//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8880//console
This message is automatically generated.
> Workflow Designer View: When logs are empty, you see the spinner, instead of
> a message
> --
>
> Key: AMBARI-18600
> URL: https://issues.apache.org/jira/browse/AMBARI-18600
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-18600.patch
>
>
> In the workflow designer view instance, if there is no log available for the
> workflow, then the spinner is seen giving the impression that logs are still
> being retrieved. This happens for all the logs, viz. the job log, error log
> and audit log.
> A message sould be displayed when there are no messages in the log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4
[ https://issues.apache.org/jira/browse/AMBARI-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576738#comment-15576738 ] Hudson commented on AMBARI-18601: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #150 (See [https://builds.apache.org/job/Ambari-branch-2.5/150/]) Revert "AMBARI-18601 : Analyze and Optimize Ambari Server Unit Tests - (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=86c2cda7e13e7db18beb464264a02f164cb14f21]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/ServiceComponentTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog220Test.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java AMBARI-18601 : Analyze and Optimize Ambari Server Unit Tests - Group 4 (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=724da086472793b580a3a228bab31979143a1aff]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog220Test.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java > Analyze and Optimize Ambari Server Unit Tests - - Group 4 > - > > Key: AMBARI-18601 > URL: https://issues.apache.org/jira/browse/AMBARI-18601 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18601-1.patch > > > ||Test||Count||Time (s)|| > |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAControllerTest > | |197.933| > |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.discovery.TestMetadataManager| > |143.545| > |org.apache.ambari.server.upgrade.UpgradeCatalog220Test |27|60.285| > |org.apache.ambari.server.state.ConfigHelperTest|18|45.862| > |org.apache.ambari.server.orm.dao.ServiceConfigDAOTest|15|40.703| > |org.apache.ambari.server.state.ServiceComponentTest|9|31.207| > |org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest|5|38.724| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18535) Ambari is not picking up the latest repo for HDP-2.4
[ https://issues.apache.org/jira/browse/AMBARI-18535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15577103#comment-15577103 ] Hudson commented on AMBARI-18535: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5805 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5805/]) AMBARI-18535 Ambari is not picking up the latest repo for HDP-2.4 (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=96d66e0d41d49e67d11d5ea558c24d858f4b9577]) * (edit) ambari-web/app/controllers/installer.js > Ambari is not picking up the latest repo for HDP-2.4 > > > Key: AMBARI-18535 > URL: https://issues.apache.org/jira/browse/AMBARI-18535 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18535.v0.patch > > > During fresh deployment, if HDP-2.4 is chosen then Ambari does not default to > the latest 2.4 release, HDP-2.4.2. This is likely because VDF files do not > exist for HDP-2.4 release and the older mechanism of picking the latest repo > URL form the hdp_urlinfo.json does not work. HDP-2.4.0 is chosen where as the > latest is HDP-2.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4
[ https://issues.apache.org/jira/browse/AMBARI-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18601: --- Fix Version/s: 2.5.0 > Analyze and Optimize Ambari Server Unit Tests - - Group 4 > - > > Key: AMBARI-18601 > URL: https://issues.apache.org/jira/browse/AMBARI-18601 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4
[ https://issues.apache.org/jira/browse/AMBARI-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18601: --- Component/s: ambari-server > Analyze and Optimize Ambari Server Unit Tests - - Group 4 > - > > Key: AMBARI-18601 > URL: https://issues.apache.org/jira/browse/AMBARI-18601 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4
Aravindan Vijayan created AMBARI-18601: -- Summary: Analyze and Optimize Ambari Server Unit Tests - - Group 4 Key: AMBARI-18601 URL: https://issues.apache.org/jira/browse/AMBARI-18601 Project: Ambari Issue Type: Bug Reporter: Aravindan Vijayan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4
[ https://issues.apache.org/jira/browse/AMBARI-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18601: --- Description: ||Test||Count||Time (s)|| |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAControllerTest | |197.933| |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.discovery.TestMetadataManager| |143.545| |org.apache.ambari.server.upgrade.UpgradeCatalog220Test |27|60.285| |org.apache.ambari.server.state.ConfigHelperTest|18|45.862| |org.apache.ambari.server.orm.dao.ServiceConfigDAOTest|15|40.703| |org.apache.ambari.server.state.ServiceComponentTest|9|31.207| |org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest|5|38.724| > Analyze and Optimize Ambari Server Unit Tests - - Group 4 > - > > Key: AMBARI-18601 > URL: https://issues.apache.org/jira/browse/AMBARI-18601 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan > Fix For: 2.5.0 > > > ||Test||Count||Time (s)|| > |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAControllerTest > | |197.933| > |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.discovery.TestMetadataManager| > |143.545| > |org.apache.ambari.server.upgrade.UpgradeCatalog220Test |27|60.285| > |org.apache.ambari.server.state.ConfigHelperTest|18|45.862| > |org.apache.ambari.server.orm.dao.ServiceConfigDAOTest|15|40.703| > |org.apache.ambari.server.state.ServiceComponentTest|9|31.207| > |org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest|5|38.724| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4
[ https://issues.apache.org/jira/browse/AMBARI-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18601: --- Component/s: (was: ambari-server) > Analyze and Optimize Ambari Server Unit Tests - - Group 4 > - > > Key: AMBARI-18601 > URL: https://issues.apache.org/jira/browse/AMBARI-18601 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17981) Integrate Druid With Ambari
[
https://issues.apache.org/jira/browse/AMBARI-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575984#comment-15575984
]
Hadoop QA commented on AMBARI-17981:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12833341/ambari-17981.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8877//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8877//console
This message is automatically generated.
> Integrate Druid With Ambari
> ---
>
> Key: AMBARI-17981
> URL: https://issues.apache.org/jira/browse/AMBARI-17981
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nishant Bangarwa
> Labels: features
> Attachments: ambari-17981.patch
>
>
> This task includes adding support for druid cluster provisioning via Ambari.
> Details about Druid cluster design and different node types are present here
> -
> http://druid.io/docs/latest/design/design.html
> In general, Druid can be defined as a service in HDP which has following
> components -
> 1) Coordinator
> 2) Overlord
> 3) Historical
> 4) Broker
> 5) Middlemanager
>
> Druid also has external dependencies on following
> 1) Zookeeper - Ambari should be able to pass in zk configs to druid cluster
> 2) Deep storage - A distributed FS, can be one of HDFS/S3 or any other NFS.
> 3) Metadata Store - Mysql/Postgres. can be either provided by the user or a
> mysql instance provisioned by ambari itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message
Sangeeta Ravindran created AMBARI-18600: --- Summary: Workflow Designer View: When logs are empty, you see the spinner, instead of a message Key: AMBARI-18600 URL: https://issues.apache.org/jira/browse/AMBARI-18600 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran Priority: Minor In the workflow designer view instance, if there is no log available for the workflow, then the spinner is seen giving the impression that logs are still being retrieved. This happens for all the logs, viz. the job log, error log and audit log. A message sould be displayed when there are no messages in the log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4
[ https://issues.apache.org/jira/browse/AMBARI-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18601: --- Affects Version/s: 2.5.0 > Analyze and Optimize Ambari Server Unit Tests - - Group 4 > - > > Key: AMBARI-18601 > URL: https://issues.apache.org/jira/browse/AMBARI-18601 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4
[ https://issues.apache.org/jira/browse/AMBARI-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18601: --- Attachment: AMBARI-18601-1.patch > Analyze and Optimize Ambari Server Unit Tests - - Group 4 > - > > Key: AMBARI-18601 > URL: https://issues.apache.org/jira/browse/AMBARI-18601 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18601-1.patch > > > ||Test||Count||Time (s)|| > |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAControllerTest > | |197.933| > |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.discovery.TestMetadataManager| > |143.545| > |org.apache.ambari.server.upgrade.UpgradeCatalog220Test |27|60.285| > |org.apache.ambari.server.state.ConfigHelperTest|18|45.862| > |org.apache.ambari.server.orm.dao.ServiceConfigDAOTest|15|40.703| > |org.apache.ambari.server.state.ServiceComponentTest|9|31.207| > |org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest|5|38.724| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18051) Services should be able to provide their own pre-req checks by supplying a jar file
[ https://issues.apache.org/jira/browse/AMBARI-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575750#comment-15575750 ] Hudson commented on AMBARI-18051: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #148 (See [https://builds.apache.org/job/Ambari-branch-2.5/148/]) AMBARI-18594 - AMBARI-18051 Breaks Stack Upgrade Checks (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cb9db0aef3d2ee6c11d9d7f15c4a4709c14dd1a8]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProviderTest.java > Services should be able to provide their own pre-req checks by supplying a > jar file > --- > > Key: AMBARI-18051 > URL: https://issues.apache.org/jira/browse/AMBARI-18051 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18051.patch > > > Services should be able to provide their own pre-req checks by supplying a > jar file. > This would allow custom services to supply their own jar files to handle > pre-req checks rather than forcing third party developers to make changes to > ambari-server code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18594) AMBARI-18051 Breaks Stack Upgrade Checks
[
https://issues.apache.org/jira/browse/AMBARI-18594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575767#comment-15575767
]
Hudson commented on AMBARI-18594:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5801 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5801/])
AMBARI-18594 - AMBARI-18051 Breaks Stack Upgrade Checks (tthorpe:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=10c7595a4ac858ac5a095f2caf8770f1ea685c1c])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
> AMBARI-18051 Breaks Stack Upgrade Checks
>
>
> Key: AMBARI-18594
> URL: https://issues.apache.org/jira/browse/AMBARI-18594
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Tim Thorpe
>Priority: Blocker
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18594.patch
>
>
> AMBARI-18051 adds logic which breaks upgrades. The following adds:
> https://github.com/apache/ambari/commit/87423d64f54d896c62d1a9245eb03a97763e35a4#diff-5a960f81153cabb6a060631fd802d076R197
> {code}
> Map services =
> getManagementController().getAmbariMetaInfo().getServices(stackName,
> upgradePack.getTarget());
> {code}
> Which translates into {{getServices("HDP", "2.4.\*.\*")}}
> When attempting an upgrade, we now see this exception thrown and some of the
> upgrade checks do not run:
> {code}
> 2016-10-13 16:44:18,806 ERROR [ambari-client-thread-34]
> (PreUpgradeCheckResourceProvider.java:202) getResources() - Unable to
> register all the custom prechecks from the services
> org.apache.ambari.server.ParentObjectNotFoundException: Parent Stack Version
> resource doesn't exist. Stack data, Stack HDP 2.4.*.* is not found in Ambari
> metainfo. Stack data, Stack HDP 2.4.*.* is not found in Ambari metainfo
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.getServices(AmbariMetaInfo.java:529)
> at
> org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:198)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:398)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.PreUpgradeCheckService.getPreUpgradeChecks(PreUpgradeCheckService.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
>
[jira] [Commented] (AMBARI-18594) AMBARI-18051 Breaks Stack Upgrade Checks
[
https://issues.apache.org/jira/browse/AMBARI-18594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575751#comment-15575751
]
Hudson commented on AMBARI-18594:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #148 (See
[https://builds.apache.org/job/Ambari-branch-2.5/148/])
AMBARI-18594 - AMBARI-18051 Breaks Stack Upgrade Checks (tthorpe:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cb9db0aef3d2ee6c11d9d7f15c4a4709c14dd1a8])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProviderTest.java
> AMBARI-18051 Breaks Stack Upgrade Checks
>
>
> Key: AMBARI-18594
> URL: https://issues.apache.org/jira/browse/AMBARI-18594
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Tim Thorpe
>Priority: Blocker
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18594.patch
>
>
> AMBARI-18051 adds logic which breaks upgrades. The following adds:
> https://github.com/apache/ambari/commit/87423d64f54d896c62d1a9245eb03a97763e35a4#diff-5a960f81153cabb6a060631fd802d076R197
> {code}
> Map services =
> getManagementController().getAmbariMetaInfo().getServices(stackName,
> upgradePack.getTarget());
> {code}
> Which translates into {{getServices("HDP", "2.4.\*.\*")}}
> When attempting an upgrade, we now see this exception thrown and some of the
> upgrade checks do not run:
> {code}
> 2016-10-13 16:44:18,806 ERROR [ambari-client-thread-34]
> (PreUpgradeCheckResourceProvider.java:202) getResources() - Unable to
> register all the custom prechecks from the services
> org.apache.ambari.server.ParentObjectNotFoundException: Parent Stack Version
> resource doesn't exist. Stack data, Stack HDP 2.4.*.* is not found in Ambari
> metainfo. Stack data, Stack HDP 2.4.*.* is not found in Ambari metainfo
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.getServices(AmbariMetaInfo.java:529)
> at
> org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:198)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:398)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.PreUpgradeCheckService.getPreUpgradeChecks(PreUpgradeCheckService.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
>
[jira] [Commented] (AMBARI-18051) Services should be able to provide their own pre-req checks by supplying a jar file
[ https://issues.apache.org/jira/browse/AMBARI-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575766#comment-15575766 ] Hudson commented on AMBARI-18051: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5801 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5801/]) AMBARI-18594 - AMBARI-18051 Breaks Stack Upgrade Checks (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=10c7595a4ac858ac5a095f2caf8770f1ea685c1c]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java > Services should be able to provide their own pre-req checks by supplying a > jar file > --- > > Key: AMBARI-18051 > URL: https://issues.apache.org/jira/browse/AMBARI-18051 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18051.patch > > > Services should be able to provide their own pre-req checks by supplying a > jar file. > This would allow custom services to supply their own jar files to handle > pre-req checks rather than forcing third party developers to make changes to > ambari-server code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18603) Remove Unnecessary Locks Inside Of ServiceComponent Business Object Implementations
Jonathan Hurley created AMBARI-18603:
Summary: Remove Unnecessary Locks Inside Of ServiceComponent
Business Object Implementations
Key: AMBARI-18603
URL: https://issues.apache.org/jira/browse/AMBARI-18603
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.5.0
Many of the business object implementations include needless locks which simply
add the overhead and contention in larger clusters. Some examples of these are :
- HostImpl
-- get/set DisksInfo()
-- get/set TotalMemBytes()
- ServiceComponentHostImpl
-- get/set MaintenanceState()
-- get/set LastOpLastUpdateTime()
These types of methods are found on other business classes as well, like
{{ClusterImpl}} and {{ServiceImpl}}. Additionally, methods like
{{convertToResponse()}} and {{debugDump()}} need not acquire locks since they
are used mostly for serialization of data to the web client where the data will
then immediately become stale anyway.
The {{ServiceComponent}} business object should have the following work
performed:
- Remove locking around areas where its no longer required
- Replace collections with thread-safe concurrent versions
- Remove some reliance on state-full business objects (caches)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18456) Refactor Unnecessary In-Memory Locks Around Business Objects
[
https://issues.apache.org/jira/browse/AMBARI-18456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18456:
-
Fix Version/s: 2.5.0
> Refactor Unnecessary In-Memory Locks Around Business Objects
>
>
> Key: AMBARI-18456
> URL: https://issues.apache.org/jira/browse/AMBARI-18456
> Project: Ambari
> Issue Type: Epic
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Labels: branch-feature-AMBARI-18456
> Fix For: 2.5.0
>
>
> The top 4 business objects in Ambari:
> - ClusterImpl
> - ServiceImpl
> - ServiceComponentImpl
> - ServiceComponentHostImpl
> All use {{ReadWriteLock}} implementations to prevent dirty reads and
> concurrent writes. However, {{ClusterImpl}} exposes a "global"
> {{ReadWriteLock}} which the other business objects share. This causes
> tremendous problems with deadlocks, especially on slow databases.
> Consider the case where you have 3 threads:
> # thread-1 acquires {{ClusterReadLock}}
> # thread-2 acquires {{ServiceComponenWriteLock}}
> # thread-3 tries to get {{ClusterWriteLock}} and is blocked by {{thread-1}}
> # thread-2 tries to get {{ClusterReadLock}} and is blocked by {{thread-3}}
> # thread-1 tries to get {{ServiceComponentReadLock}} and is blocked by
> {{thread-2}}
> Essentially, the exposure of the "cluster global lock" causes problems since
> multiple threads can acquire other internal locks and be blocked waiting on
> the global lock.
> In general, I don't believe that the read locks help at all. Ambari usually
> encounters these locks while try to display web page information. Once
> displayed, the locks are removed and the information is already stale if
> there were write threads waiting.
> These locks should be investigated and, for the most part, except in some
> cases involving concurrent writes, removed.
> Part of the problem revolves around our assumption about how the
> ReadWriteLock works. The issue in the above scenario is that the
> clusterWriteLock request is pending. This actually blocks all subsequent
> readers even though the lock is not fair.
> FYI, this code shows that a reader, in unfair mode, will wait when there is a
> waiting writer:
> {noformat:title=Output}
> Waiting for a read lock...
> Read lock acquired!
> Waiting for a write lock...
> Trying to acquire a second read lock...
> {noformat}
> {code}
> import java.util.concurrent.locks.ReentrantReadWriteLock;
> public class Test {
> private static ReentrantReadWriteLock lock = new
> ReentrantReadWriteLock(false);
> public static void main(String[] args) throws InterruptedException {
> // A reader which takes too long to finish
> new Thread() {
> @Override
> public void run() {
> System.out.println("Waiting for a read lock...");
> lock.readLock().lock();
> System.out.println("Read lock acquired!");
> try {
> try {
> Thread.sleep(1000 * 60 * 60);
> } catch (InterruptedException e) {
> }
> } finally {
> lock.readLock().unlock();
> }
> }
> }.start();
> Thread.sleep(3000);
> // A writer which will be waiting
> new Thread() {
> @Override
> public void run() {
> System.out.println("Waiting for a write lock...");
> lock.writeLock().lock();
> System.out.println("Write lock acquired!");
> lock.writeLock().unlock();
> }
> }.start();
> Thread.sleep(3000);
> // Another reader
> new Thread() {
> @Override
> public void run() {
> System.out.println("Trying to acquire a second read lock...");
> lock.readLock().lock();
> try {
> System.out.println("Second read lock acquired successfully!!");
> } finally {
> lock.readLock().unlock();
> }
> }
> }.start();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4
[ https://issues.apache.org/jira/browse/AMBARI-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576194#comment-15576194 ] Hudson commented on AMBARI-18601: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5802 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5802/]) AMBARI-18601 : Analyze and Optimize Ambari Server Unit Tests - Group 4 (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9b9a2c07c7fa06f6575997b46583fc1dcafbfb08]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog220Test.java > Analyze and Optimize Ambari Server Unit Tests - - Group 4 > - > > Key: AMBARI-18601 > URL: https://issues.apache.org/jira/browse/AMBARI-18601 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18601-1.patch > > > ||Test||Count||Time (s)|| > |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAControllerTest > | |197.933| > |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.discovery.TestMetadataManager| > |143.545| > |org.apache.ambari.server.upgrade.UpgradeCatalog220Test |27|60.285| > |org.apache.ambari.server.state.ConfigHelperTest|18|45.862| > |org.apache.ambari.server.orm.dao.ServiceConfigDAOTest|15|40.703| > |org.apache.ambari.server.state.ServiceComponentTest|9|31.207| > |org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest|5|38.724| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18599) Workflow Designer View: When logs are empty, you see the spinner, instead of a message
[ https://issues.apache.org/jira/browse/AMBARI-18599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran resolved AMBARI-18599. - Resolution: Invalid > Workflow Designer View: When logs are empty, you see the spinner, instead of > a message > -- > > Key: AMBARI-18599 > URL: https://issues.apache.org/jira/browse/AMBARI-18599 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > > In the workflow designer view instance, if there is no log available for the > workflow, then the spinner is seen giving the impression that logs are still > being retrieved. This happens for all the logs, viz. the job log, error log > and audit log. > A message sould be displayed when there are no messages in the log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18597) Rename service to "Microsoft R Server" and component to "Microsoft R Node Client"
[
https://issues.apache.org/jira/browse/AMBARI-18597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576046#comment-15576046
]
Hadoop QA commented on AMBARI-18597:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/1288/AMBARI-18597-rename-to-node-client.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server contrib/management-packs/microsoft-r_mpack.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8878//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8878//console
This message is automatically generated.
> Rename service to "Microsoft R Server" and component to "Microsoft R Node
> Client"
> -
>
> Key: AMBARI-18597
> URL: https://issues.apache.org/jira/browse/AMBARI-18597
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18597-rename-to-node-client.patch
>
>
> Rename service to "Microsoft R Server" and component to "Microsoft R Node
> Client" in the Microsoft R management pack.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18602) Not able to install HBase through Ambari 2.2
venkata veluguri created AMBARI-18602:
-
Summary: Not able to install HBase through Ambari 2.2
Key: AMBARI-18602
URL: https://issues.apache.org/jira/browse/AMBARI-18602
Project: Ambari
Issue Type: Bug
Components: ambari-client
Affects Versions: 2.2.0
Environment: Red Hat 7.2 on Azure Cloud D14 VM
Reporter: venkata veluguri
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_client.py",
line 80, in
HbaseClient().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 219, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_client.py",
line 35, in install
self.configure(env)
File
"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_client.py",
line 40, in configure
hbase(name='client')
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
line 89, in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase.py",
line 56, in hbase
recursive = True
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 154, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 144, in action_create
raise Fail("Applying %s failed, looped symbolic links found while resolving
%s" % (self.resource, path))
resource_management.core.exceptions.Fail: Applying
Directory['/usr/hdp/current/hbase-client/conf'] failed, looped symbolic links
found while resolving /usr/hdp/current/hbase-client/conf
stdout: /var/lib/ambari-agent/data/output-1669.txt
2016-10-14 17:03:52,597 - Using hadoop conf dir:
/usr/hdp/current/hadoop-client/conf
2016-10-14 17:03:52,598 - Group['hadoop'] {}
2016-10-14 17:03:52,599 - Group['users'] {}
2016-10-14 17:03:52,599 - User['hive'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
2016-10-14 17:03:52,600 - User['zookeeper'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
2016-10-14 17:03:52,601 - User['ams'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
2016-10-14 17:03:52,601 - User['oozie'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'users']}
2016-10-14 17:03:52,602 - User['ambari-qa'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'users']}
2016-10-14 17:03:52,602 - User['tez'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'users']}
2016-10-14 17:03:52,603 - User['hdfs'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
2016-10-14 17:03:52,604 - User['sqoop'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
2016-10-14 17:03:52,604 - User['yarn'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
2016-10-14 17:03:52,605 - User['hcat'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
2016-10-14 17:03:52,606 - User['mapred'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
2016-10-14 17:03:52,606 - User['hbase'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': [u'hadoop']}
2016-10-14 17:03:52,607 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
2016-10-14 17:03:52,608 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
ambari-qa
/tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
{'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
2016-10-14 17:03:52,613 - Skipping
Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
/tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
due to not_if
2016-10-14 17:03:52,613 - Directory['/tmp/hbase-hbase'] {'owner': 'hbase',
'recursive': True, 'mode': 0775, 'cd_access': 'a'}
2016-10-14 17:03:52,614 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
2016-10-14 17:03:52,615 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh hbase
/home/hbase,/tmp/hbase,/usr/bin/hbase,/var/log/hbase,/tmp/hbase-hbase']
{'not_if': '(test $(id -u hbase) -gt 1000) || (false)'}
2016-10-14 17:03:52,619 - Skipping
Execute['/var/lib/ambari-agent/tmp/changeUid.sh hbase
/home/hbase,/tmp/hbase,/usr/bin/hbase,/var/log/hbase,/tmp/hbase-hbase'] due to
not_if
2016-10-14
[jira] [Commented] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4
[ https://issues.apache.org/jira/browse/AMBARI-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576067#comment-15576067 ] Hudson commented on AMBARI-18601: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #149 (See [https://builds.apache.org/job/Ambari-branch-2.5/149/]) AMBARI-18601 : Analyze and Optimize Ambari Server Unit Tests - Group 4 (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=71cf8c252db91400f54cda45de8edf5bfaa00b55]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog220Test.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/ServiceComponentTest.java > Analyze and Optimize Ambari Server Unit Tests - - Group 4 > - > > Key: AMBARI-18601 > URL: https://issues.apache.org/jira/browse/AMBARI-18601 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-18601-1.patch > > > ||Test||Count||Time (s)|| > |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAControllerTest > | |197.933| > |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.discovery.TestMetadataManager| > |143.545| > |org.apache.ambari.server.upgrade.UpgradeCatalog220Test |27|60.285| > |org.apache.ambari.server.state.ConfigHelperTest|18|45.862| > |org.apache.ambari.server.orm.dao.ServiceConfigDAOTest|15|40.703| > |org.apache.ambari.server.state.ServiceComponentTest|9|31.207| > |org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest|5|38.724| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18603) Remove Unnecessary Locks Inside Of ServiceComponent Business Object Implementations
[
https://issues.apache.org/jira/browse/AMBARI-18603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18603:
-
Status: Patch Available (was: Open)
> Remove Unnecessary Locks Inside Of ServiceComponent Business Object
> Implementations
> ---
>
> Key: AMBARI-18603
> URL: https://issues.apache.org/jira/browse/AMBARI-18603
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> Many of the business object implementations include needless locks which
> simply add the overhead and contention in larger clusters. Some examples of
> these are :
> - HostImpl
> -- get/set DisksInfo()
> -- get/set TotalMemBytes()
> - ServiceComponentHostImpl
> -- get/set MaintenanceState()
> -- get/set LastOpLastUpdateTime()
> These types of methods are found on other business classes as well, like
> {{ClusterImpl}} and {{ServiceImpl}}. Additionally, methods like
> {{convertToResponse()}} and {{debugDump()}} need not acquire locks since they
> are used mostly for serialization of data to the web client where the data
> will then immediately become stale anyway.
> The {{ServiceComponent}} business object should have the following work
> performed:
> - Remove locking around areas where its no longer required
> - Replace collections with thread-safe concurrent versions
> - Remove some reliance on state-full business objects (caches)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18603) Remove Unnecessary Locks Inside Of ServiceComponent Business Object Implementations
[
https://issues.apache.org/jira/browse/AMBARI-18603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18603:
-
Attachment: AMBARI-18603.patch
> Remove Unnecessary Locks Inside Of ServiceComponent Business Object
> Implementations
> ---
>
> Key: AMBARI-18603
> URL: https://issues.apache.org/jira/browse/AMBARI-18603
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18603.patch
>
>
> Many of the business object implementations include needless locks which
> simply add the overhead and contention in larger clusters. Some examples of
> these are :
> - HostImpl
> -- get/set DisksInfo()
> -- get/set TotalMemBytes()
> - ServiceComponentHostImpl
> -- get/set MaintenanceState()
> -- get/set LastOpLastUpdateTime()
> These types of methods are found on other business classes as well, like
> {{ClusterImpl}} and {{ServiceImpl}}. Additionally, methods like
> {{convertToResponse()}} and {{debugDump()}} need not acquire locks since they
> are used mostly for serialization of data to the web client where the data
> will then immediately become stale anyway.
> The {{ServiceComponent}} business object should have the following work
> performed:
> - Remove locking around areas where its no longer required
> - Replace collections with thread-safe concurrent versions
> - Remove some reliance on state-full business objects (caches)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message
[ https://issues.apache.org/jira/browse/AMBARI-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18600: Attachment: AMBARI-18600.patch > Workflow Designer View: When logs are empty, you see the spinner, instead of > a message > -- > > Key: AMBARI-18600 > URL: https://issues.apache.org/jira/browse/AMBARI-18600 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Attachments: AMBARI-18600.patch > > > In the workflow designer view instance, if there is no log available for the > workflow, then the spinner is seen giving the impression that logs are still > being retrieved. This happens for all the logs, viz. the job log, error log > and audit log. > A message sould be displayed when there are no messages in the log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message
[ https://issues.apache.org/jira/browse/AMBARI-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18600: Status: Patch Available (was: In Progress) > Workflow Designer View: When logs are empty, you see the spinner, instead of > a message > -- > > Key: AMBARI-18600 > URL: https://issues.apache.org/jira/browse/AMBARI-18600 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Attachments: AMBARI-18600.patch > > > In the workflow designer view instance, if there is no log available for the > workflow, then the spinner is seen giving the impression that logs are still > being retrieved. This happens for all the logs, viz. the job log, error log > and audit log. > A message sould be displayed when there are no messages in the log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message
[ https://issues.apache.org/jira/browse/AMBARI-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18600: Status: Open (was: Patch Available) > Workflow Designer View: When logs are empty, you see the spinner, instead of > a message > -- > > Key: AMBARI-18600 > URL: https://issues.apache.org/jira/browse/AMBARI-18600 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > > In the workflow designer view instance, if there is no log available for the > workflow, then the spinner is seen giving the impression that logs are still > being retrieved. This happens for all the logs, viz. the job log, error log > and audit log. > A message sould be displayed when there are no messages in the log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message
[ https://issues.apache.org/jira/browse/AMBARI-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18600: Attachment: (was: AMBARI-18600.patch) > Workflow Designer View: When logs are empty, you see the spinner, instead of > a message > -- > > Key: AMBARI-18600 > URL: https://issues.apache.org/jira/browse/AMBARI-18600 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > > In the workflow designer view instance, if there is no log available for the > workflow, then the spinner is seen giving the impression that logs are still > being retrieved. This happens for all the logs, viz. the job log, error log > and audit log. > A message sould be displayed when there are no messages in the log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message
[ https://issues.apache.org/jira/browse/AMBARI-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18600: Fix Version/s: 2.5.0 Status: Patch Available (was: In Progress) > Workflow Designer View: When logs are empty, you see the spinner, instead of > a message > -- > > Key: AMBARI-18600 > URL: https://issues.apache.org/jira/browse/AMBARI-18600 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18600.patch > > > In the workflow designer view instance, if there is no log available for the > workflow, then the spinner is seen giving the impression that logs are still > being retrieved. This happens for all the logs, viz. the job log, error log > and audit log. > A message sould be displayed when there are no messages in the log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message
[ https://issues.apache.org/jira/browse/AMBARI-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18600: Attachment: AMBARI-18600.patch > Workflow Designer View: When logs are empty, you see the spinner, instead of > a message > -- > > Key: AMBARI-18600 > URL: https://issues.apache.org/jira/browse/AMBARI-18600 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18600.patch > > > In the workflow designer view instance, if there is no log available for the > workflow, then the spinner is seen giving the impression that logs are still > being retrieved. This happens for all the logs, viz. the job log, error log > and audit log. > A message sould be displayed when there are no messages in the log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18604) Workflow Designer View: Filtering suggestion for Status on the Workflow Dashboard does not include all status options
Sangeeta Ravindran created AMBARI-18604: --- Summary: Workflow Designer View: Filtering suggestion for Status on the Workflow Dashboard does not include all status options Key: AMBARI-18604 URL: https://issues.apache.org/jira/browse/AMBARI-18604 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran Priority: Minor The workflow designer view dashboard allows filtering of workflows based on Status, Name and User. When filtering by Status, it does not offer PREP status as a suggestion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
