[jira] [Updated] (AMBARI-19330) LogSearch upgrade support 2.4 -> 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19330: Attachment: AMBARI-19330-addendum.patch > LogSearch upgrade support 2.4 -> 2.5 > > > Key: AMBARI-19330 > URL: https://issues.apache.org/jira/browse/AMBARI-19330 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19330-addendum.patch, AMBARI-19330.patch > > > Check configuration differences between logsearch in ambari version 2.4 and > 2.5. > Manually do a yum upgrade with new packages, then during ambari upgrade: > - check the new configurations are added properly > - implement renames/deletions in UpgradeCatalogXX.java > additional taks here (not really related with upgrade): > - config cleanup (check configuration dependencies, display names, typos etc.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-19330) LogSearch upgrade support 2.4 -> 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely reopened AMBARI-19330: - > LogSearch upgrade support 2.4 -> 2.5 > > > Key: AMBARI-19330 > URL: https://issues.apache.org/jira/browse/AMBARI-19330 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19330.patch > > > Check configuration differences between logsearch in ambari version 2.4 and > 2.5. > Manually do a yum upgrade with new packages, then during ambari upgrade: > - check the new configurations are added properly > - implement renames/deletions in UpgradeCatalogXX.java > additional taks here (not really related with upgrade): > - config cleanup (check configuration dependencies, display names, typos etc.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19411) Metrics Sink for Atlas
[
https://issues.apache.org/jira/browse/AMBARI-19411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813332#comment-15813332
]
Hadoop QA commented on AMBARI-19411:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846425/AMBARI-19411.v1.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:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9971//console
This message is automatically generated.
> Metrics Sink for Atlas
> --
>
> Key: AMBARI-19411
> URL: https://issues.apache.org/jira/browse/AMBARI-19411
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Apoorv Naik
> Fix For: 2.5.0
>
> Attachments: 0001-AMBARI-19411-Atlas-AMS-support.patch,
> AMBARI-19411.v1.patch
>
>
> Currently atlas has no way of publishing metrics/insights to AMS. This change
> adds a Atlas sink that will periodically collect and emit metrics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19434) Changing Capacity-scheduler configs while llap is enabled should warn the user if llap is affected
Vivek Ratnavel Subramanian created AMBARI-19434: --- Summary: Changing Capacity-scheduler configs while llap is enabled should warn the user if llap is affected Key: AMBARI-19434 URL: https://issues.apache.org/jira/browse/AMBARI-19434 Project: Ambari Issue Type: Improvement Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19433) Increase default timeout and threadpool size for the external script to work on slower machines
[ https://issues.apache.org/jira/browse/AMBARI-19433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19433: -- Attachment: AMBARI-19433.patch > Increase default timeout and threadpool size for the external script to work > on slower machines > --- > > Key: AMBARI-19433 > URL: https://issues.apache.org/jira/browse/AMBARI-19433 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19433.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19433) Increase default timeout and threadpool size for the external script to work on slower machines
[ https://issues.apache.org/jira/browse/AMBARI-19433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19433: -- Status: Patch Available (was: Open) > Increase default timeout and threadpool size for the external script to work > on slower machines > --- > > Key: AMBARI-19433 > URL: https://issues.apache.org/jira/browse/AMBARI-19433 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19433.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19406) Provide default value for hbase java io tmp dir
[ https://issues.apache.org/jira/browse/AMBARI-19406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812694#comment-15812694 ] Di Li commented on AMBARI-19406: pushed to trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=6e9b4be25ece4d9023c98283f9a88051bf8e81ea > Provide default value for hbase java io tmp dir > --- > > Key: AMBARI-19406 > URL: https://issues.apache.org/jira/browse/AMBARI-19406 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-19406.patch > > > provide default value for hbase_java_io_tmpdir defined in hbase-env -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19406) Provide default value for hbase java io tmp dir
[ https://issues.apache.org/jira/browse/AMBARI-19406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19406: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Provide default value for hbase java io tmp dir > --- > > Key: AMBARI-19406 > URL: https://issues.apache.org/jira/browse/AMBARI-19406 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-19406.patch > > > provide default value for hbase_java_io_tmpdir defined in hbase-env -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19293) Component install and after-install should not run in parallel
[
https://issues.apache.org/jira/browse/AMBARI-19293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19293:
---
Attachment: (was: AMBARI-19293.patch)
> Component install and after-install should not run in parallel
> --
>
> Key: AMBARI-19293
> URL: https://issues.apache.org/jira/browse/AMBARI-19293
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 3.0.0
>
>
> If Ambari executes component installation in parallel, execution of
> {{link_configs}} in the after-install hook for one component may interfere
> with the {{configure}} step of another component's installation. This may
> cause loss of configuration files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19431) Limit number of active sessions in ambari
Sangeeta Ravindran created AMBARI-19431: --- Summary: Limit number of active sessions in ambari Key: AMBARI-19431 URL: https://issues.apache.org/jira/browse/AMBARI-19431 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: trunk Environment: Provide the ability to limit the number of active sessions in ambari. Reporter: Sangeeta Ravindran Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19397) Infra Solr Upgrade support 2.4 -> 2.5
[
https://issues.apache.org/jira/browse/AMBARI-19397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813193#comment-15813193
]
Miklos Gergely commented on AMBARI-19397:
-
committed to trunk:
{code:java}
commit 3f886882b970854fce2b9e79234f4b3357b27719
Author: Miklos Gergely
Date: Tue Jan 10 00:24:53 2017 +0100
AMBARI-19397 Infra Solr Upgrade support 2.4 -> 2.5 (mgergely)
Change-Id: I9f697adb605c3b732627417343a78fb1c76e1dc0
{code}
committed to branch-2.5:
{code:java}
commit 777d97afb6c8f0846c0ea8386db5a6f6aa1c5f86
Author: Miklos Gergely
Date: Tue Jan 10 00:08:28 2017 +0100
AMBARI-19397 Infra Solr Upgrade support 2.4 -> 2.5 (mgergely)
Change-Id: I4c753856516fc416433f677664df2515c0d9f493
{code}
> Infra Solr Upgrade support 2.4 -> 2.5
> -
>
> Key: AMBARI-19397
> URL: https://issues.apache.org/jira/browse/AMBARI-19397
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-19397.patch
>
>
> Upgrade Infra solr related properties for ambari 2.5.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813285#comment-15813285 ] Hudson commented on AMBARI-17596: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6391 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6391/]) AMBARI-17596 : Collect & Publish AmbariServer database metrics. (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7ca559ccf12dacb1ee053e537868b915ba880647]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AmbariMetricSinkImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/MetricsConfiguration.java * (edit) ambari-server/conf/windows/metrics.properties * (edit) ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/TestMetricsSource.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/MetricsSource.java * (add) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AmbariPerformanceMonitor.java * (add) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/DatabaseMetricsSource.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AbstractMetricsSource.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/MetricsServiceTest.java * (edit) ambari-server/conf/unix/metrics.properties * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/MetricsServiceImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/MetricsService.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/JvmMetricsSource.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/JvmMetricsSourceTest.java * (edit) ambari-server/src/test/resources/metrics.properties * (edit) ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/TestAmbariMetricsSinkImpl.java * (add) ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/MetricsSourceTest.java > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-17596-4.patch > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19432) Improve "Install Wizard step 1" after new guidelines
Xi Wang created AMBARI-19432: Summary: Improve "Install Wizard step 1" after new guidelines Key: AMBARI-19432 URL: https://issues.apache.org/jira/browse/AMBARI-19432 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Xi Wang Assignee: Xi Wang Fix For: 3.0.0 Should do the following adjustments to integrate with the new style guidelines: As for the contents inside of the white panel: 1. Make tabs in a horizontal view. 2. Select stack button changed from blue to white. 3. Repositories should be the title of the following section, so move the radio buttons under that. 4. Make two radio buttons in horizontal view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19397) Infra Solr Upgrade support 2.4 -> 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19397: Resolution: Fixed Status: Resolved (was: Patch Available) > Infra Solr Upgrade support 2.4 -> 2.5 > - > > Key: AMBARI-19397 > URL: https://issues.apache.org/jira/browse/AMBARI-19397 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19397.patch > > > Upgrade Infra solr related properties for ambari 2.5.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19433) Increase default timeout and threadpool size for the external script to work on slower machines
Jaimin Jetly created AMBARI-19433: - Summary: Increase default timeout and threadpool size for the external script to work on slower machines Key: AMBARI-19433 URL: https://issues.apache.org/jira/browse/AMBARI-19433 Project: Ambari Issue Type: Task Affects Versions: 2.5.0 Reporter: Jaimin Jetly Assignee: Jaimin Jetly Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19433) Increase default timeout and threadpool size for the external script to work on slower machines
[ https://issues.apache.org/jira/browse/AMBARI-19433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19433: -- Attachment: AMBARI-19433.patch > Increase default timeout and threadpool size for the external script to work > on slower machines > --- > > Key: AMBARI-19433 > URL: https://issues.apache.org/jira/browse/AMBARI-19433 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19433.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-17596. Resolution: Fixed Pushed to branch-2.5 and trunk. > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-17596-4.patch > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19397) Infra Solr Upgrade support 2.4 -> 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813377#comment-15813377 ] Hudson commented on AMBARI-19397: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6392 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6392/]) AMBARI-19397 Infra Solr Upgrade support 2.4 -> 2.5 (mgergely) (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3f886882b970854fce2b9e79234f4b3357b27719]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/configuration/infra-solr-client-log4j.xml * (edit) ambari-web/app/data/configs/services/ambari_infra_properties.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/configuration/infra-solr-log4j.xml * (add) ambari-server/src/main/java/org/apache/ambari/server/upgrade/SchemaUpgradeUtil.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/properties/solr-log4j.properties.j2 > Infra Solr Upgrade support 2.4 -> 2.5 > - > > Key: AMBARI-19397 > URL: https://issues.apache.org/jira/browse/AMBARI-19397 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19397.patch > > > Upgrade Infra solr related properties for ambari 2.5.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19433) Increase default timeout and threadpool size for the external script to work on slower machines
[ https://issues.apache.org/jira/browse/AMBARI-19433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19433: -- Attachment: (was: AMBARI-19433.patch) > Increase default timeout and threadpool size for the external script to work > on slower machines > --- > > Key: AMBARI-19433 > URL: https://issues.apache.org/jira/browse/AMBARI-19433 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17596: --- Status: Open (was: Patch Available) > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17596: --- Attachment: (was: AMBARI-17596.patch) > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17596: --- Attachment: (was: AMBARI-17589.patch) > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17596: --- Attachment: AMBARI-17596-4.patch > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-17596-4.patch > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19411) Metrics Sink for Atlas
[ https://issues.apache.org/jira/browse/AMBARI-19411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated AMBARI-19411: - Attachment: 0001-AMBARI-19411-Atlas-AMS-support.patch > Metrics Sink for Atlas > -- > > Key: AMBARI-19411 > URL: https://issues.apache.org/jira/browse/AMBARI-19411 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Apoorv Naik > Fix For: 2.5.0 > > Attachments: 0001-AMBARI-19411-Atlas-AMS-support.patch > > > Currently atlas has no way of publishing metrics/insights to AMS. This change > adds a Atlas sink that will periodically collect and emit metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19407) Provide default values for oozie nproc_limit and nofile_limit configuration
[ https://issues.apache.org/jira/browse/AMBARI-19407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812843#comment-15812843 ] Hudson commented on AMBARI-19407: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6390 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6390/]) AMBARI-19407: Provide default values for oozie nproc_limit and (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c1acfac7e8b041cb9ddcb45c9a1115286b8a6b45]) * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py > Provide default values for oozie nproc_limit and nofile_limit configuration > --- > > Key: AMBARI-19407 > URL: https://issues.apache.org/jira/browse/AMBARI-19407 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-19407.patch > > > Provide default values for Oozie nproc_limit and nonfile_limit configurations > defined in oozie-env. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19406) Provide default value for hbase java io tmp dir
[ https://issues.apache.org/jira/browse/AMBARI-19406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812750#comment-15812750 ] Hudson commented on AMBARI-19406: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6389 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6389/]) AMBARI-19406: Provide default value for hbase java io tmp dir (dili) (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6e9b4be25ece4d9023c98283f9a88051bf8e81ea]) * (edit) ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py > Provide default value for hbase java io tmp dir > --- > > Key: AMBARI-19406 > URL: https://issues.apache.org/jira/browse/AMBARI-19406 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-19406.patch > > > provide default value for hbase_java_io_tmpdir defined in hbase-env -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19096) HDP 3.0 TP - create Service Advisor for ZK
[ https://issues.apache.org/jira/browse/AMBARI-19096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812751#comment-15812751 ] Hudson commented on AMBARI-19096: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6389 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6389/]) AMBARI-19096. HDP 3.0 TP - create Service Advisor for ZK (alejandro) (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8258cf893175342142523ec0001b9f4d3f09ce3f]) * (edit) ambari-server/src/main/resources/scripts/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py * (add) ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.9/service_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/service_advisor.py * (edit) ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor_perf.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py > HDP 3.0 TP - create Service Advisor for ZK > -- > > Key: AMBARI-19096 > URL: https://issues.apache.org/jira/browse/AMBARI-19096 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19096.preview.patch > > > Create a Service Advisor script for ZK in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19338) AM sizing for LLAP - min container size changes
[ https://issues.apache.org/jira/browse/AMBARI-19338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812639#comment-15812639 ] Hudson commented on AMBARI-19338: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #668 (See [https://builds.apache.org/job/Ambari-branch-2.5/668/]) Revert "AMBARI-19338 AM sizing for LLAP - min container size changes (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=61ba63f21236026b3857c0c01c960d73eee70649]) * (edit) ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py > AM sizing for LLAP - min container size changes > --- > > Key: AMBARI-19338 > URL: https://issues.apache.org/jira/browse/AMBARI-19338 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19338_2.patch > > > Currently, AMs are sized too big for LLAP (especially with small setups). > Better defaults are needed, but min container size has to change for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19429) Create an ODPi stack definition
Roman Shaposhnik created AMBARI-19429: - Summary: Create an ODPi stack definition Key: AMBARI-19429 URL: https://issues.apache.org/jira/browse/AMBARI-19429 Project: Ambari Issue Type: Improvement Components: stacks Affects Versions: 2.4.2 Reporter: Roman Shaposhnik Assignee: Roman Shaposhnik ODPi is a nonprofit organization committed to simplification & standardization of the big data ecosystem with common reference specifications and test suites. As part of its mission, ODPi has been developing a series of specifications for how to integrate upstream Apache projects into the coherent platform. Part of this standardization effort is maintenance of the ODPi core stack definition which today includes: * Apache Zookeeper * Apache Hadoop * Apache Hive and has been maintained as a custom stack on ODPi side: https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0 In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to propose that instead of migrating the stack definition to Bigtop, we should actually migrate it to Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19096) HDP 3.0 TP - create Service Advisor for ZK
[ https://issues.apache.org/jira/browse/AMBARI-19096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19096: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit 8258cf893175342142523ec0001b9f4d3f09ce3f > HDP 3.0 TP - create Service Advisor for ZK > -- > > Key: AMBARI-19096 > URL: https://issues.apache.org/jira/browse/AMBARI-19096 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19096.preview.patch > > > Create a Service Advisor script for ZK in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19293) Component install and after-install should not run in parallel
[
https://issues.apache.org/jira/browse/AMBARI-19293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19293:
---
Description:
If Ambari executes component installation in parallel, execution of
{{link_configs}} in the after-install hook for one component may interfere with
the {{configure}} step of another component's installation. This may cause
loss of configuration files.
What's more, {{configure}} from different components may also interfere with
each other.
was:If Ambari executes component installation in parallel, execution of
{{link_configs}} in the after-install hook for one component may interfere with
the {{configure}} step of another component's installation. This may cause
loss of configuration files.
> Component install and after-install should not run in parallel
> --
>
> Key: AMBARI-19293
> URL: https://issues.apache.org/jira/browse/AMBARI-19293
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 3.0.0
>
>
> If Ambari executes component installation in parallel, execution of
> {{link_configs}} in the after-install hook for one component may interfere
> with the {{configure}} step of another component's installation. This may
> cause loss of configuration files.
> What's more, {{configure}} from different components may also interfere with
> each other.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19428) druid user does not have cd_access on historical nodes segment cache directory
[
https://issues.apache.org/jira/browse/AMBARI-19428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812704#comment-15812704
]
Hadoop QA commented on AMBARI-19428:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846385/AMBARI-19428.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9969//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9969//console
This message is automatically generated.
> druid user does not have cd_access on historical nodes segment cache directory
> --
>
> Key: AMBARI-19428
> URL: https://issues.apache.org/jira/browse/AMBARI-19428
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19428.patch
>
>
> this is a regression after the changes in AMBARI-19328.
> If the parent directories are created by ambari and does not already have
> cd_access for druid user, ambari fails to set proper permissions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19429) Create an ODPi stack definition
[ https://issues.apache.org/jira/browse/AMBARI-19429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shaposhnik updated AMBARI-19429: -- Description: ODPi is a nonprofit organization committed to simplification & standardization of the big data ecosystem with common reference specifications and test suites. As part of its mission, ODPi has been developing a series of specifications for how to integrate upstream Apache projects into the coherent platform. Part of this standardization effort is maintenance of the ODPi core stack definition which today includes: * Apache Zookeeper * Apache Hadoop * Apache Hive and has been maintained as a custom stack on ODPi side: https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0 In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to propose that instead of migrating the stack definition to Bigtop, we should actually migrate it to Ambari. was: ODPi is a nonprofit organization committed to simplification & standardization of the big data ecosystem with common reference specifications and test suites. As part of its mission, ODPi has been developing a series of specifications for how to integrate upstream Apache projects into the coherent platform. Part of this standardization effort is maintenance of the ODPi core stack definition which today includes: * Apache Zookeeper * Apache Hadoop * Apache Hive and has been maintained as a custom stack on ODPi side: https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0 In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to propose that instead of migrating the stack definition to Bigtop, we should actually migrate it to Ambari. > Create an ODPi stack definition > --- > > Key: AMBARI-19429 > URL: https://issues.apache.org/jira/browse/AMBARI-19429 > Project: Ambari > Issue Type: Improvement > Components: stacks >Affects Versions: 2.4.2 >Reporter: Roman Shaposhnik >Assignee: Roman Shaposhnik > > ODPi is a nonprofit organization committed to simplification & > standardization of the big data ecosystem with common reference > specifications and test suites. As part of its mission, ODPi has been > developing a series of specifications for how to integrate upstream Apache > projects into the coherent platform. Part of this standardization effort is > maintenance of the ODPi core stack definition which today includes: >* Apache Zookeeper >* Apache Hadoop >* Apache Hive > and has been maintained as a custom stack on ODPi side: > > https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0 > In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to > propose that instead of migrating the stack definition to Bigtop, we should > actually migrate it to Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19429) Create an ODPi stack definition
[ https://issues.apache.org/jira/browse/AMBARI-19429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812665#comment-15812665 ] Roman Shaposhnik commented on AMBARI-19429: --- See BIGTOP-2666 for details on the Bigtop side. > Create an ODPi stack definition > --- > > Key: AMBARI-19429 > URL: https://issues.apache.org/jira/browse/AMBARI-19429 > Project: Ambari > Issue Type: Improvement > Components: stacks >Affects Versions: 2.4.2 >Reporter: Roman Shaposhnik >Assignee: Roman Shaposhnik > > ODPi is a nonprofit organization committed to simplification & > standardization of the big data ecosystem with common reference > specifications and test suites. As part of its mission, ODPi has been > developing a series of specifications for how to integrate upstream Apache > projects into the coherent platform. Part of this standardization effort is > maintenance of the ODPi core stack definition which today includes: >* Apache Zookeeper >* Apache Hadoop >* Apache Hive > and has been maintained as a custom stack on ODPi side: > > https://github.com/odpi/bigtop/tree/odpi-master/bigtop-packages/src/common/ambari/ODPi/1.0 > In conjunction with merge effort for Apache Bigtop BIGTOP-2666 I'd like to > propose that instead of migrating the stack definition to Bigtop, we should > actually migrate it to Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19411) Metrics Sink for Atlas
[ https://issues.apache.org/jira/browse/AMBARI-19411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated AMBARI-19411: - Attachment: (was: AMBARI-19411.patch) > Metrics Sink for Atlas > -- > > Key: AMBARI-19411 > URL: https://issues.apache.org/jira/browse/AMBARI-19411 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Apoorv Naik > Fix For: 2.5.0 > > Attachments: 0001-AMBARI-19411-Atlas-AMS-support.patch > > > Currently atlas has no way of publishing metrics/insights to AMS. This change > adds a Atlas sink that will periodically collect and emit metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-19430) Use common property for principal name prefix to help with customization of unique principal names
[
https://issues.apache.org/jira/browse/AMBARI-19430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas reassigned AMBARI-19430:
-
Assignee: Robert Levas
> Use common property for principal name prefix to help with customization of
> unique principal names
> --
>
> Key: AMBARI-19430
> URL: https://issues.apache.org/jira/browse/AMBARI-19430
> Project: Ambari
> Issue Type: Bug
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos, kerberos_descriptor
>
> Use common property for principal name prefix to help with customization of
> unique principal names.
> All _headless_ Kerberos identities have a non-unique principal name (across
> clusters). To help this issue, the cluster name is appended to these
> principal names by adding "-$\{cluster-name|toLower()\}" after the principal
> name component. If the user wants to change this convention, they will need
> to find all _headless_ principals and make the change. On top of that, when
> adding new components, they will need to remember to make the change to new
> _headless_ principal names.
> A better solution is to provide a _global_ property named "principal_suffix"
> and use that in each _headless_ principal name. By default the value for this
> property will be
> {code}
> principal_suffix="-${cluster_name|toLower()}"
> {code}
> If the user would like not use a prefix (in the event there is only a single
> cluster connecting to the KDC), the value can be changed to
> {code}
> principal_suffix=""
> {code}
> Finally if the user would like to use some other randomizer, they can set the
> value to something else. For example
> {code}
> principal_suffix="_12345"
> {code}
> The property is set in the Kerberos descriptor's "properties" block. For
> example:
> {code}
> {
> "properties": {
> "realm": "${kerberos-env/realm}",
> ...,
> "principal_suffix": "${cluster_name|toLower()}"
> },
> "identities": [
> ...,
> {
> "name": "smokeuser",
> "principal": {
> "value": "${cluster-env/smokeuser}-${principal_suffix}@${realm}",
> "type": "user",
> "configuration": "cluster-env/smokeuser_principal_name",
> "local_username": "${cluster-env/smokeuser}"
> },
> ...
> }
> ],
> "services": [
> {
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19430) Use common property for principal name prefix to help with customization of unique principal names
Robert Levas created AMBARI-19430:
-
Summary: Use common property for principal name prefix to help
with customization of unique principal names
Key: AMBARI-19430
URL: https://issues.apache.org/jira/browse/AMBARI-19430
Project: Ambari
Issue Type: Bug
Reporter: Robert Levas
Use common property for principal name prefix to help with customization of
unique principal names.
All _headless_ Kerberos identities have a non-unique principal name (across
clusters). To help this issue, the cluster name is appended to these principal
names by adding "-$\{cluster-name|toLower()\}" after the principal name
component. If the user wants to change this convention, they will need to find
all _headless_ principals and make the change. On top of that, when adding new
components, they will need to remember to make the change to new _headless_
principal names.
A better solution is to provide a _global_ property named "principal_suffix"
and use that in each _headless_ principal name. By default the value for this
property will be
{code}
principal_suffix="-${cluster_name|toLower()}"
{code}
If the user would like not use a prefix (in the event there is only a single
cluster connecting to the KDC), the value can be changed to
{code}
principal_suffix=""
{code}
Finally if the user would like to use some other randomizer, they can set the
value to something else. For example
{code}
principal_suffix="_12345"
{code}
The property is set in the Kerberos descriptor's "properties" block. For
example:
{code}
{
"properties": {
"realm": "${kerberos-env/realm}",
...,
"principal_suffix": "${cluster_name|toLower()}"
},
"identities": [
...,
{
"name": "smokeuser",
"principal": {
"value": "${cluster-env/smokeuser}-${principal_suffix}@${realm}",
"type": "user",
"configuration": "cluster-env/smokeuser_principal_name",
"local_username": "${cluster-env/smokeuser}"
},
...
}
],
"services": [
{
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19411) Metrics Sink for Atlas
[ https://issues.apache.org/jira/browse/AMBARI-19411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated AMBARI-19411: - Attachment: AMBARI-19411.v1.patch > Metrics Sink for Atlas > -- > > Key: AMBARI-19411 > URL: https://issues.apache.org/jira/browse/AMBARI-19411 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Apoorv Naik > Fix For: 2.5.0 > > Attachments: 0001-AMBARI-19411-Atlas-AMS-support.patch, > AMBARI-19411.v1.patch > > > Currently atlas has no way of publishing metrics/insights to AMS. This change > adds a Atlas sink that will periodically collect and emit metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19397) Infra Solr Upgrade support 2.4 -> 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813720#comment-15813720 ] Hudson commented on AMBARI-19397: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #670 (See [https://builds.apache.org/job/Ambari-branch-2.5/670/]) AMBARI-19397 Infra Solr Upgrade support 2.4 -> 2.5 (mgergely) (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=777d97afb6c8f0846c0ea8386db5a6f6aa1c5f86]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/configuration/infra-solr-log4j.xml * (add) ambari-server/src/main/java/org/apache/ambari/server/upgrade/SchemaUpgradeUtil.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/properties/solr-log4j.properties.j2 * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/configuration/infra-solr-client-log4j.xml > Infra Solr Upgrade support 2.4 -> 2.5 > - > > Key: AMBARI-19397 > URL: https://issues.apache.org/jira/browse/AMBARI-19397 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19397.patch > > > Upgrade Infra solr related properties for ambari 2.5.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813719#comment-15813719 ] Hudson commented on AMBARI-17596: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #670 (See [https://builds.apache.org/job/Ambari-branch-2.5/670/]) AMBARI-17596 : Collect & Publish AmbariServer database metrics. (Fix (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a6d858add4d6aea657f1494a9b6118c3f2fcb4c2]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/DatabaseMetricsSource.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/MetricsSourceTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AmbariPerformanceMonitor.java > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-17596-4.patch > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19435) NodeManager restart fails during HOU if it is on same host as RM
[
https://issues.apache.org/jira/browse/AMBARI-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813517#comment-15813517
]
Jonathan Hurley commented on AMBARI-19435:
--
It seems like there are two possible solutions to this:
- Instead of creating a single START stage for every host, we can create two
stages; one for masters and one for non-masters. This, however, leads to the
problem with components like ZKFC which is not a master but is required to be
started before NameNode.
- Use the {{RoleCommandOrder}} to create the correct number of stages per host,
grouping as many together as the dependencies will allow.
> NodeManager restart fails during HOU if it is on same host as RM
>
>
> Key: AMBARI-19435
> URL: https://issues.apache.org/jira/browse/AMBARI-19435
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 - 4 node cluster with
> NodeManager installed on all hosts, NN HA is enabled, RM HA is not enabled
> # Register 2.5.3.0 version and install the bits
> # Start HOU using API and accept manual prompts to sys-prep the hosts.
> Observe the wizard at restart task of host that runs RM and NM together
> *Result:*
> At the task to Restart Node Manager on the RM host, observed below failure:
> {code}
> 2016-12-20 18:32:39,446 -
> File['/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'action':
> ['delete'], 'not_if': 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'}
> 2016-12-20 18:32:39,459 - Execute['ulimit -c unlimited; export
> HADOOP_LIBEXEC_DIR=/usr/hdp/2.5.3.0-37/hadoop/libexec &&
> /usr/hdp/current/hadoop-yarn-nodemanager/sbin/yarn-daemon.sh --config
> /usr/hdp/2.5.3.0-37/hadoop/conf start nodemanager'] {'not_if':
> 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'user': 'yarn'}
> 2016-12-20 18:32:40,558 - Execute['ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'not_if':
> 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'tries': 5,
> 'try_sleep': 1}
> 2016-12-20 18:32:40,576 - Skipping Execute['ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] due to not_if
> 2016-12-20 18:32:40,576 - Executing NodeManager Stack Upgrade post-restart
> 2016-12-20 18:32:40,578 - NodeManager executing "yarn node -list
> -states=RUNNING" to verify the node has rejoined the cluster...
> 2016-12-20 18:32:40,578 - checked_call['yarn node -list -states=RUNNING']
> {'user': 'yarn'}
> Command failed after 1 tries
> {code}
> A retry of the failed task is successful.
> The issue looks due to the fact that RM is still down while we try to start
> NM on the host. While starting NM, we run below command to verify if NM has
> come up
> {code}
> yarn node -list -states=RUNNING
> {code}
> The command fails since it tries to connect to RM, resulting in timeout
> As a possible fix, we may need to adjust the order in HOU upgrade pack so as
> to start RM before NM in such cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19432) Improve "Install Wizard step 1" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19432: - Attachment: AMBARI-19432.patch > Improve "Install Wizard step 1" after new guidelines > > > Key: AMBARI-19432 > URL: https://issues.apache.org/jira/browse/AMBARI-19432 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19432.patch > > > Should do the following adjustments to integrate with the new style > guidelines: > As for the contents inside of the white panel: > 1. Make tabs in a horizontal view. > 2. Select stack button changed from blue to white. > 3. Repositories should be the title of the following section, so move the > radio buttons under that. > 4. Make two radio buttons in horizontal view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19432) Improve "Install Wizard step 1" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813593#comment-15813593 ] Xi Wang commented on AMBARI-19432: -- 20205 passing (19s) 153 pending > Improve "Install Wizard step 1" after new guidelines > > > Key: AMBARI-19432 > URL: https://issues.apache.org/jira/browse/AMBARI-19432 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19432.patch > > > Should do the following adjustments to integrate with the new style > guidelines: > As for the contents inside of the white panel: > 1. Make tabs in a horizontal view. > 2. Select stack button changed from blue to white. > 3. Repositories should be the title of the following section, so move the > radio buttons under that. > 4. Make two radio buttons in horizontal view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19432) Improve "Install Wizard step 1" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19432: - Status: Patch Available (was: Open) > Improve "Install Wizard step 1" after new guidelines > > > Key: AMBARI-19432 > URL: https://issues.apache.org/jira/browse/AMBARI-19432 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19432.patch > > > Should do the following adjustments to integrate with the new style > guidelines: > As for the contents inside of the white panel: > 1. Make tabs in a horizontal view. > 2. Select stack button changed from blue to white. > 3. Repositories should be the title of the following section, so move the > radio buttons under that. > 4. Make two radio buttons in horizontal view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17596) Collect & Publish AmbariServer database metrics
[ https://issues.apache.org/jira/browse/AMBARI-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813634#comment-15813634 ] Hudson commented on AMBARI-17596: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #669 (See [https://builds.apache.org/job/Ambari-branch-2.5/669/]) AMBARI-17596 : Collect & Publish AmbariServer database metrics. (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ec8809cea9f175ac8604eb7e3be817150e5fd47a]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AbstractMetricsSource.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/JvmMetricsSource.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/JvmMetricsSourceTest.java * (edit) ambari-server/conf/unix/metrics.properties * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/MetricsConfiguration.java * (add) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AmbariPerformanceMonitor.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/MetricsServiceTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/DatabaseMetricsSource.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/MetricsServiceImpl.java * (add) ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/MetricsSourceTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/TestAmbariMetricsSinkImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/MetricsService.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/MetricsSource.java * (edit) ambari-server/src/test/resources/metrics.properties * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AmbariMetricSinkImpl.java * (edit) ambari-server/conf/windows/metrics.properties * (edit) ambari-server/src/test/java/org/apache/ambari/server/metric/system/impl/TestMetricsSource.java > Collect & Publish AmbariServer database metrics > --- > > Key: AMBARI-17596 > URL: https://issues.apache.org/jira/browse/AMBARI-17596 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-17596-4.patch > > > Implement the collection APIs to get the defined metrics from Ambari Server > and use the Ambari-Server metrics Sink to publish metrics to AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19435) NodeManager restart fails during HOU if it is on same host as RM
Jonathan Hurley created AMBARI-19435:
Summary: NodeManager restart fails during HOU if it is on same
host as RM
Key: AMBARI-19435
URL: https://issues.apache.org/jira/browse/AMBARI-19435
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.5.0
*Steps*
# Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 - 4 node cluster with
NodeManager installed on all hosts, NN HA is enabled, RM HA is not enabled
# Register 2.5.3.0 version and install the bits
# Start HOU using API and accept manual prompts to sys-prep the hosts. Observe
the wizard at restart task of host that runs RM and NM together
*Result:*
At the task to Restart Node Manager on the RM host, observed below failure:
{code}
2016-12-20 18:32:39,446 -
File['/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'action':
['delete'], 'not_if': 'ambari-sudo.sh -H -E test -f
/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'}
2016-12-20 18:32:39,459 - Execute['ulimit -c unlimited; export
HADOOP_LIBEXEC_DIR=/usr/hdp/2.5.3.0-37/hadoop/libexec &&
/usr/hdp/current/hadoop-yarn-nodemanager/sbin/yarn-daemon.sh --config
/usr/hdp/2.5.3.0-37/hadoop/conf start nodemanager'] {'not_if': 'ambari-sudo.sh
-H -E test -f /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid &&
ambari-sudo.sh -H -E pgrep -F
/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'user': 'yarn'}
2016-12-20 18:32:40,558 - Execute['ambari-sudo.sh -H -E test -f
/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'not_if':
'ambari-sudo.sh -H -E test -f
/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'tries': 5,
'try_sleep': 1}
2016-12-20 18:32:40,576 - Skipping Execute['ambari-sudo.sh -H -E test -f
/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] due to not_if
2016-12-20 18:32:40,576 - Executing NodeManager Stack Upgrade post-restart
2016-12-20 18:32:40,578 - NodeManager executing "yarn node -list
-states=RUNNING" to verify the node has rejoined the cluster...
2016-12-20 18:32:40,578 - checked_call['yarn node -list -states=RUNNING']
{'user': 'yarn'}
Command failed after 1 tries
{code}
A retry of the failed task is successful.
The issue looks due to the fact that RM is still down while we try to start NM
on the host. While starting NM, we run below command to verify if NM has come up
{code}
yarn node -list -states=RUNNING
{code}
The command fails since it tries to connect to RM, resulting in timeout
As a possible fix, we may need to adjust the order in HOU upgrade pack so as to
start RM before NM in such cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19422) Supported kylin4 OS for ambari-2.2.1
[ https://issues.apache.org/jira/browse/AMBARI-19422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813569#comment-15813569 ] Xing commented on AMBARI-19422: --- These patches should be applied to ambari-2.2.1. Please checkout branch to ambari-2.2.1. > Supported kylin4 OS for ambari-2.2.1 > > > Key: AMBARI-19422 > URL: https://issues.apache.org/jira/browse/AMBARI-19422 > Project: Ambari > Issue Type: Improvement > Components: 2.2.1, ambari-server >Affects Versions: 2.2.1 > Environment: kylin4 OS, x86_64 >Reporter: Xing >Priority: Minor > Labels: patch > Fix For: 2.2.1 > > Attachments: 0001-Supported-Kylin4-OS.patch, > 0002-Added-kylin4-osFamily-to-metainfo.xml-and-repoinfo.x.patch > > > My team wanted to install ambari-2.2.1 on kylin4, but we got a bad result. > So my team made some changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19289) HDFS Service check fails if previous active NN is down
[
https://issues.apache.org/jira/browse/AMBARI-19289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang updated AMBARI-19289:
-
Attachment: AMBARI-19289_trunk.02.patch
> HDFS Service check fails if previous active NN is down
> --
>
> Key: AMBARI-19289
> URL: https://issues.apache.org/jira/browse/AMBARI-19289
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
> Attachments: AMBARI-19289_trunk.01.patch, AMBARI-19289_trunk.02.patch
>
>
> *Reproduce steps*
> # Enable namenode HA
> # Shutdown the active namenode, standby takes over
> # Run HDFS service check
> hdfs service check script uses
> {{hdfs dfsadmin -fs hdfs://mycluster -safemode get | grep OFF}}
> to check if namenode is out of safemode. However this command will fail if
> 1st NN is down without checking the state of 2nd NN. This is likely a HDFS
> bug similar to HDFS-8277.
> *Proposal*
> There are several approaches to fix this
> # Loop each namenode address and get safemode with {{hdfs dfsadmin -fs
> hdfs://nn_host:8020 -safemode get | grep OFF}}, as long as there is one NN
> returns OFF, consider DFS is not in safemode and continue the rest of check.
> However is it really necessary to add such complexity for service check?
> # Remove the safemode check code, if HDFS is in safemode, read/write
> operations will fail anyway so service check won't pass
> I am preferring to #2 because it makes script simpler and work in all cases.
> Note this is service check, it should pass as long as HDFS is in working
> state. It is not namenode check.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19289) HDFS Service check fails if previous active NN is down
[
https://issues.apache.org/jira/browse/AMBARI-19289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang updated AMBARI-19289:
-
Attachment: AMBARI-19289_branch-2.5.01.patch
> HDFS Service check fails if previous active NN is down
> --
>
> Key: AMBARI-19289
> URL: https://issues.apache.org/jira/browse/AMBARI-19289
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
> Attachments: AMBARI-19289_branch-2.5.01.patch,
> AMBARI-19289_trunk.01.patch, AMBARI-19289_trunk.02.patch
>
>
> *Reproduce steps*
> # Enable namenode HA
> # Shutdown the active namenode, standby takes over
> # Run HDFS service check
> hdfs service check script uses
> {{hdfs dfsadmin -fs hdfs://mycluster -safemode get | grep OFF}}
> to check if namenode is out of safemode. However this command will fail if
> 1st NN is down without checking the state of 2nd NN. This is likely a HDFS
> bug similar to HDFS-8277.
> *Proposal*
> There are several approaches to fix this
> # Loop each namenode address and get safemode with {{hdfs dfsadmin -fs
> hdfs://nn_host:8020 -safemode get | grep OFF}}, as long as there is one NN
> returns OFF, consider DFS is not in safemode and continue the rest of check.
> However is it really necessary to add such complexity for service check?
> # Remove the safemode check code, if HDFS is in safemode, read/write
> operations will fail anyway so service check won't pass
> I am preferring to #2 because it makes script simpler and work in all cases.
> Note this is service check, it should pass as long as HDFS is in working
> state. It is not namenode check.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19432) Improve "Install Wizard step 1" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19432: - Attachment: AMBARI-19432.patch > Improve "Install Wizard step 1" after new guidelines > > > Key: AMBARI-19432 > URL: https://issues.apache.org/jira/browse/AMBARI-19432 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19432.patch, AMBARI-19432.patch > > > Should do the following adjustments to integrate with the new style > guidelines: > As for the contents inside of the white panel: > 1. Make tabs in a horizontal view. > 2. Select stack button changed from blue to white. > 3. Repositories should be the title of the following section, so move the > radio buttons under that. > 4. Make two radio buttons in horizontal view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19420) Import from local file system doesn't work if the same file is selected again.
[ https://issues.apache.org/jira/browse/AMBARI-19420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19420: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Import from local file system doesn't work if the same file is selected again. > -- > > Key: AMBARI-19420 > URL: https://issues.apache.org/jira/browse/AMBARI-19420 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19420_trunk.patch > > > Import a workflow by using local file system. Do a reset layout. Import again > the same file. No effect is seen. > Expected: > The file should be able to import again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19420) Import from local file system doesn't work if the same file is selected again.
[ https://issues.apache.org/jira/browse/AMBARI-19420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814061#comment-15814061 ] Hudson commented on AMBARI-19420: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6393 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6393/]) AMBARI-19420. Import from local file system doesn't work if the same (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=96aaf1dbb1a1d8a1d416736e5ae7f5b4cf81bc1a]) * (add) contrib/views/wfmanager/src/main/resources/ui/app/components/file-picker.js > Import from local file system doesn't work if the same file is selected again. > -- > > Key: AMBARI-19420 > URL: https://issues.apache.org/jira/browse/AMBARI-19420 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19420_trunk.patch > > > Import a workflow by using local file system. Do a reset layout. Import again > the same file. No effect is seen. > Expected: > The file should be able to import again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18259) ExtesnsionModule.java description is not correct
[ https://issues.apache.org/jira/browse/AMBARI-18259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu resolved AMBARI-18259. -- Resolution: Not A Bug > ExtesnsionModule.java description is not correct > > > Key: AMBARI-18259 > URL: https://issues.apache.org/jira/browse/AMBARI-18259 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: zhangxiaolu > Attachments: > AMBARI-18259-ExtensionModule-description-is-not-correct.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17910) JsonSerializerTest.java cannot pass
[ https://issues.apache.org/jira/browse/AMBARI-17910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-17910: - Resolution: Not A Problem Status: Resolved (was: Patch Available) > JsonSerializerTest.java cannot pass > --- > > Key: AMBARI-17910 > URL: https://issues.apache.org/jira/browse/AMBARI-17910 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: zhangxiaolu > Fix For: 2.1.1 > > Attachments: AMBARI-17910-JsonSerializerTest-cannot-pass.patch > > > testSerializeResourcesAsArray.java cannot pass because the input was not > correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19436) Need ability to upload a file in HDFS browser.
Padma Priya Nagaraj created AMBARI-19436: Summary: Need ability to upload a file in HDFS browser. Key: AMBARI-19436 URL: https://issues.apache.org/jira/browse/AMBARI-19436 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Fix For: 2.5.0 Need ability to upload a file in HDFS browser. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19436) Need ability to upload a file in HDFS browser.
[ https://issues.apache.org/jira/browse/AMBARI-19436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19436: - Attachment: AMBARI-19436_trunk.patch > Need ability to upload a file in HDFS browser. > -- > > Key: AMBARI-19436 > URL: https://issues.apache.org/jira/browse/AMBARI-19436 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19436_trunk.patch > > > Need ability to upload a file in HDFS browser. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19289) HDFS Service check fails if previous active NN is down
[
https://issues.apache.org/jira/browse/AMBARI-19289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814244#comment-15814244
]
Hadoop QA commented on AMBARI-19289:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846481/AMBARI-19289_branch-2.5.01.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9973//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9973//console
This message is automatically generated.
> HDFS Service check fails if previous active NN is down
> --
>
> Key: AMBARI-19289
> URL: https://issues.apache.org/jira/browse/AMBARI-19289
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
> Attachments: AMBARI-19289_branch-2.5.01.patch,
> AMBARI-19289_trunk.01.patch, AMBARI-19289_trunk.02.patch
>
>
> *Reproduce steps*
> # Enable namenode HA
> # Shutdown the active namenode, standby takes over
> # Run HDFS service check
> hdfs service check script uses
> {{hdfs dfsadmin -fs hdfs://mycluster -safemode get | grep OFF}}
> to check if namenode is out of safemode. However this command will fail if
> 1st NN is down without checking the state of 2nd NN. This is likely a HDFS
> bug similar to HDFS-8277.
> *Proposal*
> There are several approaches to fix this
> # Loop each namenode address and get safemode with {{hdfs dfsadmin -fs
> hdfs://nn_host:8020 -safemode get | grep OFF}}, as long as there is one NN
> returns OFF, consider DFS is not in safemode and continue the rest of check.
> However is it really necessary to add such complexity for service check?
> # Remove the safemode check code, if HDFS is in safemode, read/write
> operations will fail anyway so service check won't pass
> I am preferring to #2 because it makes script simpler and work in all cases.
> Note this is service check, it should pass as long as HDFS is in working
> state. It is not namenode check.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19420) Import from local file system doesn't work if the same file is selected again.
[ https://issues.apache.org/jira/browse/AMBARI-19420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814041#comment-15814041 ] Hudson commented on AMBARI-19420: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #671 (See [https://builds.apache.org/job/Ambari-branch-2.5/671/]) AMBARI-19420. Import from local file system doesn't work if the same (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f6b288f0deb10f0f3477e1fc0055e80aacb75b23]) * (add) contrib/views/wfmanager/src/main/resources/ui/app/components/file-picker.js > Import from local file system doesn't work if the same file is selected again. > -- > > Key: AMBARI-19420 > URL: https://issues.apache.org/jira/browse/AMBARI-19420 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19420_trunk.patch > > > Import a workflow by using local file system. Do a reset layout. Import again > the same file. No effect is seen. > Expected: > The file should be able to import again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17806) when set metrics distribute,then start namenode ha,metrics collector cannot start because the property of 'hbase.rootdir' hasnot changed
[ https://issues.apache.org/jira/browse/AMBARI-17806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu resolved AMBARI-17806. -- Resolution: Invalid > when set metrics distribute,then start namenode ha,metrics collector cannot > start because the property of 'hbase.rootdir' hasnot changed > > > Key: AMBARI-17806 > URL: https://issues.apache.org/jira/browse/AMBARI-17806 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0 >Reporter: zhangxiaolu > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19438) Add enable delta sync property for Ranger
[
https://issues.apache.org/jira/browse/AMBARI-19438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-19438:
-
Attachment: AMBARI-19438.patch
> Add enable delta sync property for Ranger
> -
>
> Key: AMBARI-19438
> URL: https://issues.apache.org/jira/browse/AMBARI-19438
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19438.patch
>
>
> Add new property {{ranger.usersync.ldap.deltasync}} under ranger-ugsync-site
> config type to enable delta-sync. Need to show it under existing Smart Config
> Tab Ranger Usersync for LDAP/AD Sub Tab.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19438) Add enable delta sync property for Ranger
[
https://issues.apache.org/jira/browse/AMBARI-19438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-19438:
-
Status: Patch Available (was: In Progress)
> Add enable delta sync property for Ranger
> -
>
> Key: AMBARI-19438
> URL: https://issues.apache.org/jira/browse/AMBARI-19438
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19438.patch
>
>
> Add new property {{ranger.usersync.ldap.deltasync}} under ranger-ugsync-site
> config type to enable delta-sync. Need to show it under existing Smart Config
> Tab Ranger Usersync for LDAP/AD Sub Tab.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19432) Improve "Install Wizard step 1" after new guidelines
[
https://issues.apache.org/jira/browse/AMBARI-19432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814081#comment-15814081
]
Hadoop QA commented on AMBARI-19432:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846482/AMBARI-19432.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/9972//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9972//console
This message is automatically generated.
> Improve "Install Wizard step 1" after new guidelines
>
>
> Key: AMBARI-19432
> URL: https://issues.apache.org/jira/browse/AMBARI-19432
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19432.patch, AMBARI-19432.patch
>
>
> Should do the following adjustments to integrate with the new style
> guidelines:
> As for the contents inside of the white panel:
> 1. Make tabs in a horizontal view.
> 2. Select stack button changed from blue to white.
> 3. Repositories should be the title of the following section, so move the
> radio buttons under that.
> 4. Make two radio buttons in horizontal view.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19437) Remove anonymous bind option for Ranger User sync for LDAP/AD
Mugdha Varadkar created AMBARI-19437:
Summary: Remove anonymous bind option for Ranger User sync for
LDAP/AD
Key: AMBARI-19437
URL: https://issues.apache.org/jira/browse/AMBARI-19437
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Fix For: 2.5.0
Remove config {{bind_anonymous/ranger-env.xml}} from Ranger configs as it is
not supported.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19438) Add enable delta sync property for Ranger
Mugdha Varadkar created AMBARI-19438:
Summary: Add enable delta sync property for Ranger
Key: AMBARI-19438
URL: https://issues.apache.org/jira/browse/AMBARI-19438
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Fix For: 2.5.0
Add new property {{ranger.usersync.ldap.deltasync}} under ranger-ugsync-site
config type to enable delta-sync. Need to show it under existing Smart Config
Tab Ranger Usersync for LDAP/AD Sub Tab.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18869) the property 'dfs.cluster.administrators' of hdfs-site in ambari issue
[ https://issues.apache.org/jira/browse/AMBARI-18869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-18869: - Resolution: Not A Bug Status: Resolved (was: Patch Available) > the property 'dfs.cluster.administrators' of hdfs-site in ambari issue > -- > > Key: AMBARI-18869 > URL: https://issues.apache.org/jira/browse/AMBARI-18869 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: zhangxiaolu > Fix For: 2.4.0 > > Attachments: AMBARI-18869.patch > > > the property 'dfs.cluster.administrators' of hdfs-site should be 'hdfs' not ' > hdfs' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19437) Remove anonymous bind option for Ranger User sync for LDAP/AD
[
https://issues.apache.org/jira/browse/AMBARI-19437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-19437:
-
Status: Patch Available (was: In Progress)
> Remove anonymous bind option for Ranger User sync for LDAP/AD
> -
>
> Key: AMBARI-19437
> URL: https://issues.apache.org/jira/browse/AMBARI-19437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19437.patch
>
>
> Remove config {{bind_anonymous/ranger-env.xml}} from Ranger configs as it is
> not supported.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19437) Remove anonymous bind option for Ranger User sync for LDAP/AD
[
https://issues.apache.org/jira/browse/AMBARI-19437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-19437:
-
Attachment: AMBARI-19437.patch
> Remove anonymous bind option for Ranger User sync for LDAP/AD
> -
>
> Key: AMBARI-19437
> URL: https://issues.apache.org/jira/browse/AMBARI-19437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19437.patch
>
>
> Remove config {{bind_anonymous/ranger-env.xml}} from Ranger configs as it is
> not supported.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19424) Hive View 2.0: Introduction of worksheets for query editor
[
https://issues.apache.org/jira/browse/AMBARI-19424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812072#comment-15812072
]
Hadoop QA commented on AMBARI-19424:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846318/AMBARI-19424_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:red}-1 core tests{color}. The test build failed in
contrib/views/hive20
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9962//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9962//console
This message is automatically generated.
> Hive View 2.0: Introduction of worksheets for query editor
> --
>
> Key: AMBARI-19424
> URL: https://issues.apache.org/jira/browse/AMBARI-19424
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19424_trunk.patch
>
>
> Introduction of worksheets for query editor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19415) Network interface check returns no value if there is no `ifconfig` command
[
https://issues.apache.org/jira/browse/AMBARI-19415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812118#comment-15812118
]
Hadoop QA commented on AMBARI-19415:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846316/AMBARI-19415.0.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-agent.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9963//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9963//console
This message is automatically generated.
> Network interface check returns no value if there is no `ifconfig` command
> --
>
> Key: AMBARI-19415
> URL: https://issues.apache.org/jira/browse/AMBARI-19415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk, 2.5.0
> Environment: CentOS7.3 Minimal Install
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-19415.0.patch
>
>
> Ambari Agent Hardware check assumes there is {{ifconfig}} command in Linux,
> but some environments (e.g. CentOS 7.3 with minimal install) doens't have
> {{ifconfig}} command, but {{ip}} command.
> A warning like below (which is in ambari-agent.log) is because of the
> assumption.
> {code}
> WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network
> interfaces list from
> {code}
> It would be better to check the NIC with {{ifconfig}} and {{ip}} both for
> better coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19424) Hive View 2.0: Introduction of worksheets for query editor
[ https://issues.apache.org/jira/browse/AMBARI-19424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19424: - Attachment: AMBARI-19424_trunk.patch > Hive View 2.0: Introduction of worksheets for query editor > -- > > Key: AMBARI-19424 > URL: https://issues.apache.org/jira/browse/AMBARI-19424 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-19424_trunk.patch > > > Introduction of worksheets for query editor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19425) Add secure znode command for ambari infra solr client
[ https://issues.apache.org/jira/browse/AMBARI-19425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19425: -- Description: Adding secure znode command for solr client (used by logsearch, ranger, atlas) in order to set ACLs on znodes (was: Adding secure znode options for solr client (used by logsearch, ranger, atlas) in order to set ACLs on znodes) > Add secure znode command for ambari infra solr client > - > > Key: AMBARI-19425 > URL: https://issues.apache.org/jira/browse/AMBARI-19425 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > > Adding secure znode command for solr client (used by logsearch, ranger, > atlas) in order to set ACLs on znodes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19425) Add secure znode command for ambari infra solr client
[ https://issues.apache.org/jira/browse/AMBARI-19425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19425: -- Attachment: AMBARI-19425.patch > Add secure znode command for ambari infra solr client > - > > Key: AMBARI-19425 > URL: https://issues.apache.org/jira/browse/AMBARI-19425 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19425.patch > > > Adding secure znode command for solr client (used by logsearch, ranger, > atlas) in order to set ACLs on znodes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19426) Modify quick link resource provider to consider filters and return visibility
Balázs Bence Sári created AMBARI-19426: -- Summary: Modify quick link resource provider to consider filters and return visibility Key: AMBARI-19426 URL: https://issues.apache.org/jira/browse/AMBARI-19426 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Balázs Bence Sári Assignee: Balázs Bence Sári Fix For: 2.5.0 Existing quicklinks API (e.g: http://c6401:8080/api/v1/stacks/HDP/versions/2.5/services/ACCUMULO/quicklinks/quicklinks.json) should return visible = true/false based on the quick links profile. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19426) Modify quick link resource provider to consider filters and return visibility
[ https://issues.apache.org/jira/browse/AMBARI-19426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-19426: --- Status: Patch Available (was: In Progress) > Modify quick link resource provider to consider filters and return visibility > - > > Key: AMBARI-19426 > URL: https://issues.apache.org/jira/browse/AMBARI-19426 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0 > > Attachments: AMBARI-19426-Use-profile-trunk-v1.patch > > > Existing quicklinks API (e.g: > http://c6401:8080/api/v1/stacks/HDP/versions/2.5/services/ACCUMULO/quicklinks/quicklinks.json) > should return visible = true/false based on the quick links profile. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19360) Ranger policies not syncing for storm, kafka and knox
[ https://issues.apache.org/jira/browse/AMBARI-19360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19360: Attachment: AMBARI-19360.1.patch > Ranger policies not syncing for storm, kafka and knox > - > > Key: AMBARI-19360 > URL: https://issues.apache.org/jira/browse/AMBARI-19360 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 > Environment: On enabling Namenode-HA and one-way SSL for Ranger, > plugins for storm kafka and knox are not able to communicate to Ranger. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19360.1.patch, AMBARI-19360.patch > > > On Enabling Namenode-HA, and One-way SSL for Ranger, plugins are not able to > fetch latest policies as authorization does not work for Storm, knox and > Kafka plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19044) Install & configure Ranger plugin components independently of Ranger admin components
[
https://issues.apache.org/jira/browse/AMBARI-19044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812010#comment-15812010
]
Hadoop QA commented on AMBARI-19044:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846326/AMBARI-19044.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/9961//console
This message is automatically generated.
> Install & configure Ranger plugin components independently of Ranger admin
> components
> -
>
> Key: AMBARI-19044
> URL: https://issues.apache.org/jira/browse/AMBARI-19044
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19044.patch
>
>
> Currently, Ambari provides a single toggle button to enable Ranger plugins
> for a component. Plugin enabled results in a bunch of configuration which are
> created on backend which are tighly coupled with Ranger admin installed on
> the same cluster.
> Need to make sure plugins communicate to Ranger admin which is installed on
> separate cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19381) Heartbeat version transitions must update Component alongside Cluster
[ https://issues.apache.org/jira/browse/AMBARI-19381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-19381: --- Status: Patch Available (was: Open) > Heartbeat version transitions must update Component alongside Cluster > - > > Key: AMBARI-19381 > URL: https://issues.apache.org/jira/browse/AMBARI-19381 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-19381.patch > > > Cluster can no longer be considered CURRENT on any singular version. Several > repositories can be current. In that regard, heartbeats should be updating > the component record with the appropriate repository status, and make sure > there is a version record for the repository. > * On heartbeat, create servicecomponent_version records > * On cluster install (via install_packages), create servicecomponent_version > records, if required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19381) Heartbeat version transitions must update Component alongside Cluster
[ https://issues.apache.org/jira/browse/AMBARI-19381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-19381: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Heartbeat version transitions must update Component alongside Cluster > - > > Key: AMBARI-19381 > URL: https://issues.apache.org/jira/browse/AMBARI-19381 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-19381.patch > > > Cluster can no longer be considered CURRENT on any singular version. Several > repositories can be current. In that regard, heartbeats should be updating > the component record with the appropriate repository status, and make sure > there is a version record for the repository. > * On heartbeat, create servicecomponent_version records > * On cluster install (via install_packages), create servicecomponent_version > records, if required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19251) Ambari capacity queue manager only accepts values in integers i.e not decimal values like 0.5
[
https://issues.apache.org/jira/browse/AMBARI-19251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812216#comment-15812216
]
Hadoop QA commented on AMBARI-19251:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846308/AMBARI-19251_trunk.03.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/capacity-scheduler
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9965//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9965//console
This message is automatically generated.
> Ambari capacity queue manager only accepts values in integers i.e not decimal
> values like 0.5
> -
>
> Key: AMBARI-19251
> URL: https://issues.apache.org/jira/browse/AMBARI-19251
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Akhil PB
>Assignee: Akhil PB
> Fix For: 2.5.0
>
> Attachments: AMBARI-19251_trunk.01.patch,
> AMBARI-19251_trunk.02.patch, AMBARI-19251_trunk.03.patch
>
>
> Ambari yarn queue manager accepts only integer capacity values.
> This JIRA is to enable decimal capacity support.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19422) Supported kylin4 OS for ambari-2.2.1
[
https://issues.apache.org/jira/browse/AMBARI-19422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812218#comment-15812218
]
Hadoop QA commented on AMBARI-19422:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846299/0002-Added-kylin4-osFamily-to-metainfo.xml-and-repoinfo.x.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/9966//console
This message is automatically generated.
> Supported kylin4 OS for ambari-2.2.1
>
>
> Key: AMBARI-19422
> URL: https://issues.apache.org/jira/browse/AMBARI-19422
> Project: Ambari
> Issue Type: Improvement
> Components: 2.2.1, ambari-server
>Affects Versions: 2.2.1
> Environment: kylin4 OS, x86_64
>Reporter: Xing
>Priority: Minor
> Labels: patch
> Fix For: 2.2.1
>
> Attachments: 0001-Supported-Kylin4-OS.patch,
> 0002-Added-kylin4-osFamily-to-metainfo.xml-and-repoinfo.x.patch
>
>
> My team wanted to install ambari-2.2.1 on kylin4, but we got a bad result.
> So my team made some changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19421) OpenSuse Leap Support
Nicola Marangoni created AMBARI-19421: - Summary: OpenSuse Leap Support Key: AMBARI-19421 URL: https://issues.apache.org/jira/browse/AMBARI-19421 Project: Ambari Issue Type: Wish Components: ambari-agent, ambari-server, stacks Affects Versions: 2.5.0 Environment: Suse Reporter: Nicola Marangoni Fix For: 2.5.0 Since OpenSuse Leap is compatible with SLES starting from SLES 12.1 (like CentOS with RHEL), It would be helpful to add OpenSuse Leap to the allowed operating systems. In particular, there are many enterprises that use SLES as default operating system. In particular, it is possible that current repositories for SLES 12 are already compatible with Leap 42.x. In this case it could be sufficient to add the OS to the allowed list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19399) Workflow imported into Local FS cannot be imported into WFD
[ https://issues.apache.org/jira/browse/AMBARI-19399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-19399: Resolution: Fixed Status: Resolved (was: Patch Available) committed to branch-2.5 and trunk > Workflow imported into Local FS cannot be imported into WFD > --- > > Key: AMBARI-19399 > URL: https://issues.apache.org/jira/browse/AMBARI-19399 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19399_branch-2.5.patch > > > Step1:Create a workflow with an action. > Step2:Fill all the action properties. > Step3:Export the workflow into local FS. > Step4:Import the same workflow into WFD -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19419) Save workflows via save mechanism instead of submission button
venkat created AMBARI-19419: --- Summary: Save workflows via save mechanism instead of submission button Key: AMBARI-19419 URL: https://issues.apache.org/jira/browse/AMBARI-19419 Project: Ambari Issue Type: New Feature Components: ambari-views Affects Versions: 2.5.0 Reporter: venkat Assignee: venkat Fix For: 2.5.0 Significant disadvantage of not having it, user will have to basically use the submit featue. Store the valid workflow in a file location (HDFS). The user can later import this file in designer and submit -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19419) Save workflows via save mechanism instead of submission button
[ https://issues.apache.org/jira/browse/AMBARI-19419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19419: Status: Patch Available (was: In Progress) > Save workflows via save mechanism instead of submission button > -- > > Key: AMBARI-19419 > URL: https://issues.apache.org/jira/browse/AMBARI-19419 > Project: Ambari > Issue Type: New Feature > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > > Significant disadvantage of not having it, user will have to basically use > the submit featue. > Store the valid workflow in a file location (HDFS). The user can later import > this file in designer and submit -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19420) Import from local file system doesn't work if the same file is selected again.
[ https://issues.apache.org/jira/browse/AMBARI-19420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19420: - Attachment: AMBARI-19420_trunk.patch > Import from local file system doesn't work if the same file is selected again. > -- > > Key: AMBARI-19420 > URL: https://issues.apache.org/jira/browse/AMBARI-19420 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19420_trunk.patch > > > Import a workflow by using local file system. Do a reset layout. Import again > the same file. No effect is seen. > Expected: > The file should be able to import again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19399) Workflow imported into Local FS cannot be imported into WFD
[ https://issues.apache.org/jira/browse/AMBARI-19399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811512#comment-15811512 ] Hudson commented on AMBARI-19399: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6385 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6385/]) AMBARI-19399 Workflow imported into Local FS cannot be imported into WFD (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8fa58061480e9f325e74d0637d6d9ac858955911]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js > Workflow imported into Local FS cannot be imported into WFD > --- > > Key: AMBARI-19399 > URL: https://issues.apache.org/jira/browse/AMBARI-19399 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19399_branch-2.5.patch > > > Step1:Create a workflow with an action. > Step2:Fill all the action properties. > Step3:Export the workflow into local FS. > Step4:Import the same workflow into WFD -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19420) Import from local file system doesn't work if the same file is selected again.
Padma Priya Nagaraj created AMBARI-19420: Summary: Import from local file system doesn't work if the same file is selected again. Key: AMBARI-19420 URL: https://issues.apache.org/jira/browse/AMBARI-19420 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Fix For: 2.5.0 Import a workflow by using local file system. Do a reset layout. Import again the same file. No effect is seen. Expected: The file should be able to import again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19416) Ambari agents remain in heartbeat lost state after ambari server restart
[
https://issues.apache.org/jira/browse/AMBARI-19416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-19416:
--
Attachment: (was: AMBARI-19416.v2.patch)
> Ambari agents remain in heartbeat lost state after ambari server restart
>
>
> Key: AMBARI-19416
> URL: https://issues.apache.org/jira/browse/AMBARI-19416
> Project: Ambari
> Issue Type: Bug
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19416.v3.patch
>
>
> With the implementation https://issues.apache.org/jira/browse/AMBARI-18505
> the execution of status commands is done in a separate child process. Status
> commands received from the server by ambari agent are passed to the status
> command executor child process via Queue ({{multiprocessing.Queue()}}. In
> case the child process is killed, either manually or by the parent process
> the queue may end up in bad state (see: http://bugs.python.org/issue20527)
> thus the re-spawned status command executor child process may not receive new
> status commands any more.
> When ambari server is restarted the agent re-registers with ambari server and
> upon re-registration it re-spawns the status command child process in order
> to receive up to date agent configs
> (https://issues.apache.org/jira/browse/AMBARI-19392). In this case the status
> commands won't be received by the status command executor child process due
> the queue may get stuck leading the ambari agent to stay in heatbeat lost
> state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19422) Supported kylin4 OS for ambari-2.2.1
Xing created AMBARI-19422: - Summary: Supported kylin4 OS for ambari-2.2.1 Key: AMBARI-19422 URL: https://issues.apache.org/jira/browse/AMBARI-19422 Project: Ambari Issue Type: Improvement Components: 2.2.1, ambari-server Affects Versions: 2.2.1 Environment: kylin4 OS, x86_64 Reporter: Xing Priority: Minor Fix For: 2.2.1 My team wanted to install ambari-2.2.1 on kylin4, but we got a bad result. So my team made some changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19422) Supported kylin4 OS for ambari-2.2.1
[ https://issues.apache.org/jira/browse/AMBARI-19422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing updated AMBARI-19422: -- Attachment: 0002-Added-kylin4-osFamily-to-metainfo.xml-and-repoinfo.x.patch 0001-Supported-Kylin4-OS.patch > Supported kylin4 OS for ambari-2.2.1 > > > Key: AMBARI-19422 > URL: https://issues.apache.org/jira/browse/AMBARI-19422 > Project: Ambari > Issue Type: Improvement > Components: 2.2.1, ambari-server >Affects Versions: 2.2.1 > Environment: kylin4 OS, x86_64 >Reporter: Xing >Priority: Minor > Labels: patch > Fix For: 2.2.1 > > Attachments: 0001-Supported-Kylin4-OS.patch, > 0002-Added-kylin4-osFamily-to-metainfo.xml-and-repoinfo.x.patch > > > My team wanted to install ambari-2.2.1 on kylin4, but we got a bad result. > So my team made some changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19422) Supported kylin4 OS for ambari-2.2.1
[ https://issues.apache.org/jira/browse/AMBARI-19422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing updated AMBARI-19422: -- Status: Patch Available (was: Open) > Supported kylin4 OS for ambari-2.2.1 > > > Key: AMBARI-19422 > URL: https://issues.apache.org/jira/browse/AMBARI-19422 > Project: Ambari > Issue Type: Improvement > Components: 2.2.1, ambari-server >Affects Versions: 2.2.1 > Environment: kylin4 OS, x86_64 >Reporter: Xing >Priority: Minor > Labels: patch > Fix For: 2.2.1 > > Attachments: 0001-Supported-Kylin4-OS.patch, > 0002-Added-kylin4-osFamily-to-metainfo.xml-and-repoinfo.x.patch > > > My team wanted to install ambari-2.2.1 on kylin4, but we got a bad result. > So my team made some changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19422) Supported kylin4 OS for ambari-2.2.1
[ https://issues.apache.org/jira/browse/AMBARI-19422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing updated AMBARI-19422: -- Status: Patch Available (was: Open) > Supported kylin4 OS for ambari-2.2.1 > > > Key: AMBARI-19422 > URL: https://issues.apache.org/jira/browse/AMBARI-19422 > Project: Ambari > Issue Type: Improvement > Components: 2.2.1, ambari-server >Affects Versions: 2.2.1 > Environment: kylin4 OS, x86_64 >Reporter: Xing >Priority: Minor > Labels: patch > Fix For: 2.2.1 > > Attachments: 0001-Supported-Kylin4-OS.patch, > 0002-Added-kylin4-osFamily-to-metainfo.xml-and-repoinfo.x.patch > > > My team wanted to install ambari-2.2.1 on kylin4, but we got a bad result. > So my team made some changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19422) Supported kylin4 OS for ambari-2.2.1
[ https://issues.apache.org/jira/browse/AMBARI-19422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing updated AMBARI-19422: -- Status: Open (was: Patch Available) > Supported kylin4 OS for ambari-2.2.1 > > > Key: AMBARI-19422 > URL: https://issues.apache.org/jira/browse/AMBARI-19422 > Project: Ambari > Issue Type: Improvement > Components: 2.2.1, ambari-server >Affects Versions: 2.2.1 > Environment: kylin4 OS, x86_64 >Reporter: Xing >Priority: Minor > Labels: patch > Fix For: 2.2.1 > > Attachments: 0001-Supported-Kylin4-OS.patch, > 0002-Added-kylin4-osFamily-to-metainfo.xml-and-repoinfo.x.patch > > > My team wanted to install ambari-2.2.1 on kylin4, but we got a bad result. > So my team made some changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19399) Workflow imported into Local FS cannot be imported into WFD
[ https://issues.apache.org/jira/browse/AMBARI-19399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811495#comment-15811495 ] Hudson commented on AMBARI-19399: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #667 (See [https://builds.apache.org/job/Ambari-branch-2.5/667/]) AMBARI-19399 Workflow imported into Local FS cannot be imported into WFD (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8a9d5fd5294d1482af1fbe021bc2c565f2d12769]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js > Workflow imported into Local FS cannot be imported into WFD > --- > > Key: AMBARI-19399 > URL: https://issues.apache.org/jira/browse/AMBARI-19399 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19399_branch-2.5.patch > > > Step1:Create a workflow with an action. > Step2:Fill all the action properties. > Step3:Export the workflow into local FS. > Step4:Import the same workflow into WFD -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19420) Import from local file system doesn't work if the same file is selected again.
[ https://issues.apache.org/jira/browse/AMBARI-19420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19420: - Status: Patch Available (was: Open) > Import from local file system doesn't work if the same file is selected again. > -- > > Key: AMBARI-19420 > URL: https://issues.apache.org/jira/browse/AMBARI-19420 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19420_trunk.patch > > > Import a workflow by using local file system. Do a reset layout. Import again > the same file. No effect is seen. > Expected: > The file should be able to import again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19419) Save workflows via save mechanism instead of submission button
[ https://issues.apache.org/jira/browse/AMBARI-19419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-19419: Attachment: AMBARI-19419_branch-2.5.patch > Save workflows via save mechanism instead of submission button > -- > > Key: AMBARI-19419 > URL: https://issues.apache.org/jira/browse/AMBARI-19419 > Project: Ambari > Issue Type: New Feature > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-19419_branch-2.5.patch > > > Significant disadvantage of not having it, user will have to basically use > the submit featue. > Store the valid workflow in a file location (HDFS). The user can later import > this file in designer and submit -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19416) Ambari agents remain in heartbeat lost state after ambari server restart
[
https://issues.apache.org/jira/browse/AMBARI-19416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-19416:
--
Attachment: AMBARI-19416.v3.patch
> Ambari agents remain in heartbeat lost state after ambari server restart
>
>
> Key: AMBARI-19416
> URL: https://issues.apache.org/jira/browse/AMBARI-19416
> Project: Ambari
> Issue Type: Bug
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19416.v3.patch
>
>
> With the implementation https://issues.apache.org/jira/browse/AMBARI-18505
> the execution of status commands is done in a separate child process. Status
> commands received from the server by ambari agent are passed to the status
> command executor child process via Queue ({{multiprocessing.Queue()}}. In
> case the child process is killed, either manually or by the parent process
> the queue may end up in bad state (see: http://bugs.python.org/issue20527)
> thus the re-spawned status command executor child process may not receive new
> status commands any more.
> When ambari server is restarted the agent re-registers with ambari server and
> upon re-registration it re-spawns the status command child process in order
> to receive up to date agent configs
> (https://issues.apache.org/jira/browse/AMBARI-19392). In this case the status
> commands won't be received by the status command executor child process due
> the queue may get stuck leading the ambari agent to stay in heatbeat lost
> state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19251) Ambari capacity queue manager only accepts values in integers i.e not decimal values like 0.5
[ https://issues.apache.org/jira/browse/AMBARI-19251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated AMBARI-19251: -- Attachment: AMBARI-19251_trunk.03.patch > Ambari capacity queue manager only accepts values in integers i.e not decimal > values like 0.5 > - > > Key: AMBARI-19251 > URL: https://issues.apache.org/jira/browse/AMBARI-19251 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.0 >Reporter: Akhil PB >Assignee: Akhil PB > Fix For: 2.5.0 > > Attachments: AMBARI-19251_trunk.01.patch, > AMBARI-19251_trunk.02.patch, AMBARI-19251_trunk.03.patch > > > Ambari yarn queue manager accepts only integer capacity values. > This JIRA is to enable decimal capacity support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19419) Manage Workflows-Feature to list and edit the users workflows.
[ https://issues.apache.org/jira/browse/AMBARI-19419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Belliraj HB updated AMBARI-19419: - Description: 1) There should be a project manager listing screen that lists all my saved workflows. 2) User should be able to navigate to edit workflow from the listing screen. 3) when the user saves a workflow or a draft or submits, it should be saving in project listing. 4) project listing would contain Workflow Type, Workflow Name,Workflow Path,Updated Time. 5) Project listing should support pagination. was: Significant disadvantage of not having it, user will have to basically use the submit featue. Store the valid workflow in a file location (HDFS). The user can later import this file in designer and submit > Manage Workflows-Feature to list and edit the users workflows. > -- > > Key: AMBARI-19419 > URL: https://issues.apache.org/jira/browse/AMBARI-19419 > Project: Ambari > Issue Type: New Feature > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-19419_branch-2.5.patch > > > 1) There should be a project manager listing screen that lists all my saved > workflows. > 2) User should be able to navigate to edit workflow from the listing screen. > 3) when the user saves a workflow or a draft or submits, it should be saving > in project listing. > 4) project listing would contain Workflow Type, Workflow Name,Workflow > Path,Updated Time. > 5) Project listing should support pagination. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19419) Manage Workflows-Feature to list and edit the users workflows.
[ https://issues.apache.org/jira/browse/AMBARI-19419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811578#comment-15811578 ] Belliraj HB commented on AMBARI-19419: -- Updated requirements. > Manage Workflows-Feature to list and edit the users workflows. > -- > > Key: AMBARI-19419 > URL: https://issues.apache.org/jira/browse/AMBARI-19419 > Project: Ambari > Issue Type: New Feature > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-19419_branch-2.5.patch > > > 1) There should be a project manager listing screen that lists all my saved > workflows. > 2) User should be able to navigate to edit workflow from the listing screen. > 3) when the user saves a workflow or a draft or submits, it should be saving > in project listing. > 4) project listing would contain Workflow Type, Workflow Name,Workflow > Path,Updated Time. > 5) Project listing should support pagination. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
