[jira] [Commented] (AMBARI-15381) PXF should start after HDFS
[
https://issues.apache.org/jira/browse/AMBARI-15381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194816#comment-15194816
]
Hadoop QA commented on AMBARI-15381:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12793372/AMBARI-15381-1.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5863//console
This message is automatically generated.
> PXF should start after HDFS
> ---
>
> Key: AMBARI-15381
> URL: https://issues.apache.org/jira/browse/AMBARI-15381
> Project: Ambari
> Issue Type: Bug
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-15381-1.patch, AMBARI-15381.patch
>
>
> Update RCO to ensure that PXF is started after HDFS.
> PXF connects to namenode during startup and retries couple of times until
> namenode has come up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15420) Refactor resource_management library
[ https://issues.apache.org/jira/browse/AMBARI-15420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-15420: --- Status: Patch Available (was: In Progress) > Refactor resource_management library > > > Key: AMBARI-15420 > URL: https://issues.apache.org/jira/browse/AMBARI-15420 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 2.2.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.0 > > Attachments: AMBARI-15420.patch > > > Refactor resource_management library, to generalize the library and remove > HDP-specific hardcodings > Specifically, > # Make stack-selector, conf-selector tools stack-driven instead of hardcoding > hdp-select and conf-select > # Make stack-root stack-driven instead of hardcoding /usr/hdp > # Make copy_tarball mappings stack-driven > # Make PACKAGE_DIRS mapping in conf_select use stack-root instead of > hardcoding the "/usr/hdp" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15420) Refactor resource_management library
[ https://issues.apache.org/jira/browse/AMBARI-15420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-15420: --- Attachment: AMBARI-15420.patch > Refactor resource_management library > > > Key: AMBARI-15420 > URL: https://issues.apache.org/jira/browse/AMBARI-15420 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 2.2.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.0 > > Attachments: AMBARI-15420.patch > > > Refactor resource_management library, to generalize the library and remove > HDP-specific hardcodings > Specifically, > # Make stack-selector, conf-selector tools stack-driven instead of hardcoding > hdp-select and conf-select > # Make stack-root stack-driven instead of hardcoding /usr/hdp > # Make copy_tarball mappings stack-driven > # Make PACKAGE_DIRS mapping in conf_select use stack-root instead of > hardcoding the "/usr/hdp" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15368) there are some mistake in vendor.js when insatll hbase
[ https://issues.apache.org/jira/browse/AMBARI-15368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194772#comment-15194772 ] wuhui commented on AMBARI-15368: If you want to see the patch you can sign in the url. https://reviews.apache.org/r/44698/ > there are some mistake in vendor.js when insatll hbase > -- > > Key: AMBARI-15368 > URL: https://issues.apache.org/jira/browse/AMBARI-15368 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.1 >Reporter: wuhui > Fix For: 2.1.1 > > Attachments: hbase_error.png > > > if you install hbase there will be a error at the step7 in vendor.js which > showed uncaught Error: could not respond to event > didChangeData in state rootState -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15297) In the step 2 of install resourcemanager ha ,the hosts showd in mistake
[ https://issues.apache.org/jira/browse/AMBARI-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194771#comment-15194771 ] wuhui commented on AMBARI-15297: If you want to see the patch you can sign in the url. https://reviews.apache.org/r/44613/ > In the step 2 of install resourcemanager ha ,the hosts showd in mistake > --- > > Key: AMBARI-15297 > URL: https://issues.apache.org/jira/browse/AMBARI-15297 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.1 >Reporter: wuhui > Fix For: 2.1.1 > > Attachments: rm_error.jpg > > > In the step 2 of install RM HA,if you select the extra host for the HA > host,it will show a error host which not match with the selected host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-13366) Add conf-select python script into Ambari for conf version selection
[ https://issues.apache.org/jira/browse/AMBARI-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-13366. Resolution: Duplicate Assignee: Jayush Luniya Will track work in AMBARI-15420. > Add conf-select python script into Ambari for conf version selection > > > Key: AMBARI-13366 > URL: https://issues.apache.org/jira/browse/AMBARI-13366 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0 >Reporter: Tuong Truong >Assignee: Jayush Luniya > > Currently, there is an conf-select script is that is used in HDP > distribution. However, this is not in Ambari. We propose to add the > conf-select script into Ambari but with parameterized stack info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15297) In the step 2 of install resourcemanager ha ,the hosts showd in mistake
[ https://issues.apache.org/jira/browse/AMBARI-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194762#comment-15194762 ] wuhui commented on AMBARI-15297: if I login in the console platform and type ambari-server --hash,it shows ambari-server --hash dd69b547b5458ae34ec0d4738f388611fe651460. I think there are some bug in the ember.js progress.I really want to make a contribution to the apache community. thanks! > In the step 2 of install resourcemanager ha ,the hosts showd in mistake > --- > > Key: AMBARI-15297 > URL: https://issues.apache.org/jira/browse/AMBARI-15297 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.1 >Reporter: wuhui > Fix For: 2.1.1 > > Attachments: rm_error.jpg > > > In the step 2 of install RM HA,if you select the extra host for the HA > host,it will show a error host which not match with the selected host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15368) there are some mistake in vendor.js when insatll hbase
[ https://issues.apache.org/jira/browse/AMBARI-15368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194763#comment-15194763 ] wuhui commented on AMBARI-15368: if I login in the console platform and type ambari-server --hash,it shows ambari-server --hash dd69b547b5458ae34ec0d4738f388611fe651460. I think there are some bug in the ember.js progress.I really want to make a contribution to the apache community. thanks! > there are some mistake in vendor.js when insatll hbase > -- > > Key: AMBARI-15368 > URL: https://issues.apache.org/jira/browse/AMBARI-15368 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.1 >Reporter: wuhui > Fix For: 2.1.1 > > Attachments: hbase_error.png > > > if you install hbase there will be a error at the step7 in vendor.js which > showed uncaught Error: could not respond to event > didChangeData in state rootState -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-13365) Add stack-select python script into Ambari for stack-select package
[ https://issues.apache.org/jira/browse/AMBARI-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reassigned AMBARI-13365: -- Assignee: Jayush Luniya > Add stack-select python script into Ambari for stack-select package > --- > > Key: AMBARI-13365 > URL: https://issues.apache.org/jira/browse/AMBARI-13365 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0 >Reporter: Tuong Truong >Assignee: Jayush Luniya > > Currently, there is an hdp-select script is that is used in HDP distribution. > However, this is not in Ambari. We propose to add a stack-select script into > Ambari that will perform similar function to hdp-select, but with > parameterized stack info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-13365) Add stack-select python script into Ambari for stack-select package
[ https://issues.apache.org/jira/browse/AMBARI-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-13365. Resolution: Duplicate Will track work in AMBARI-15420 > Add stack-select python script into Ambari for stack-select package > --- > > Key: AMBARI-13365 > URL: https://issues.apache.org/jira/browse/AMBARI-13365 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0 >Reporter: Tuong Truong > > Currently, there is an hdp-select script is that is used in HDP distribution. > However, this is not in Ambari. We propose to add a stack-select script into > Ambari that will perform similar function to hdp-select, but with > parameterized stack info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15420) Refactor resource_management library
Jayush Luniya created AMBARI-15420: -- Summary: Refactor resource_management library Key: AMBARI-15420 URL: https://issues.apache.org/jira/browse/AMBARI-15420 Project: Ambari Issue Type: Bug Components: ambari-agent, ambari-server Affects Versions: 2.2.0 Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: 2.4.0 Refactor resource_management library, to generalize the library and remove HDP-specific hardcodings Specifically, # Make stack-selector, conf-selector tools stack-driven instead of hardcoding hdp-select and conf-select # Make stack-root stack-driven instead of hardcoding /usr/hdp # Make copy_tarball mappings stack-driven # Make PACKAGE_DIRS mapping in conf_select use stack-root instead of hardcoding the "/usr/hdp" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-13367) rename stack related methods to be more generic for better reuse
[ https://issues.apache.org/jira/browse/AMBARI-13367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reassigned AMBARI-13367: -- Assignee: Jayush Luniya > rename stack related methods to be more generic for better reuse > > > Key: AMBARI-13367 > URL: https://issues.apache.org/jira/browse/AMBARI-13367 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Tuong Truong >Assignee: Jayush Luniya >Priority: Minor > > Currently, many of the methods in Ambari has HDP prefix, infix, or postfix. > This can cause confusion when the methods are used in context of other stack > such as OPD, PHD or IOP. With the parameterized stack info, remove these > *fixes should have with reduce much confusion for developers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-13367) rename stack related methods to be more generic for better reuse
[ https://issues.apache.org/jira/browse/AMBARI-13367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-13367. Resolution: Duplicate Duplicate of AMBARI-15329 > rename stack related methods to be more generic for better reuse > > > Key: AMBARI-13367 > URL: https://issues.apache.org/jira/browse/AMBARI-13367 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Tuong Truong >Priority: Minor > > Currently, many of the methods in Ambari has HDP prefix, infix, or postfix. > This can cause confusion when the methods are used in context of other stack > such as OPD, PHD or IOP. With the parameterized stack info, remove these > *fixes should have with reduce much confusion for developers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-15329) Code Cleanup: Remove hdp hardcodings in functions, variables etc.
[ https://issues.apache.org/jira/browse/AMBARI-15329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-15329. Resolution: Fixed > Code Cleanup: Remove hdp hardcodings in functions, variables etc. > -- > > Key: AMBARI-15329 > URL: https://issues.apache.org/jira/browse/AMBARI-15329 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server, stacks >Affects Versions: 2.2.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.0 > > Attachments: hdp_cleanup.2.patch, hdp_cleanup.addendum.patch > > > Cleanup code to remove HDP hardcodings in variable names, function names. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15075) Edit Widget Wizard still open even though it was closed/saved in the previous step
[ https://issues.apache.org/jira/browse/AMBARI-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194739#comment-15194739 ] Hudson commented on AMBARI-15075: - ABORTED: Integrated in Ambari-branch-2.2 #510 (See [https://builds.apache.org/job/Ambari-branch-2.2/510/]) AMBARI-15075. Edit Widget Wizard still open even though it was (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cae751a39e31891e8a6a18c80e4e758f3e397d44]) * ambari-web/app/controllers/main/service/widgets/edit_controller.js > Edit Widget Wizard still open even though it was closed/saved in the previous > step > -- > > Key: AMBARI-15075 > URL: https://issues.apache.org/jira/browse/AMBARI-15075 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15075.2.patch, AMBARI-15075.3.patch, > AMBARI-15075.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15413) Metrics Grafana Failed to start
[ https://issues.apache.org/jira/browse/AMBARI-15413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194738#comment-15194738 ] Hudson commented on AMBARI-15413: - ABORTED: Integrated in Ambari-branch-2.2 #510 (See [https://builds.apache.org/job/Ambari-branch-2.2/510/]) AMBARI-15413 : Metrics Grafana Failed to start (avijayan) (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0e78f7019ebd10c25db07fbb675bda521fa55208]) * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py * ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py > Metrics Grafana Failed to start > --- > > Key: AMBARI-15413 > URL: https://issues.apache.org/jira/browse/AMBARI-15413 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15413.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15417) Blueprint should have a flag to allow configuring use of RCO vs Retry method
[
https://issues.apache.org/jira/browse/AMBARI-15417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194733#comment-15194733
]
bhuvnesh chaudhary commented on AMBARI-15417:
-
Pasting email discussion for reference
{code}
-- Forwarded message --
From: Robert Nettleton
Date: Mon, Mar 14, 2016 at 6:38 AM
Subject: Re: Blueprints - RCO - Related question.
To: "d...@ambari.apache.org"
Cc: Sumit Mohanty , Alejandro Fernandez
Hi Bhuvnesh,
You are correct. The Blueprints deployment mechanism in Ambari no longer
relies on Role-command ordering to install or start components across the
cluster.
This change to Blueprints was actually implemented in Ambari 2.1.0, so it has
been around for several releases now. The new approach was implemented to
improve the performance times of cluster deployments, and provide better
support for dynamic scaling of clusters.
That being said, the new deployment mechanism does indeed remove the guarantee
of ordering, which can potentially cause some problems for certain types of
clusters. There were also changes implemented on the Ambari Agent side to
mitigate this problem or ordering. The ambari-agent will now retry INSTALL and
START operations if those operations happen to fail. The START operation is
probably the most relevant in your case, and is also the operation that does
show the ordering issues you’ve mentioned in some deployments.
The idea is that the ambari-agent retries should help to resolve any issues
with services starting in an unexpected order.
This ambari-agent feature is on by default, but can be configured in a more
fine-grained fashion by setting some properties in “cluster-env” in your
Blueprint or Cluster Creation Template.
Unfortunately, this is not documented very well, but the three properties in
question are set by default in the BlueprintConfigurationProcessor in the
following method:
org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor#setRetryConfiguration
The properties set in this method allow control over the types of operations
that are retried, the max number of retries attempted, and the maximum amount
of time that the agent should attempt a retry.
We’ve seen many clusters using this new approach, and have not run into that
many problems with respect to ordering.
One possible problem we’ve seen is in a small number of components that launch
services as a background command. In that case, the ambari-agent cannot detect
that a retry is required, and so cannot attempt a restart of a failed service.
This problem can usually be resolved with component-specific retries.
I don’t know much about the HAWQ component, but I would expect that customizing
the retry settings may help this problem. Do the HAWQ components implement
retry attempts when booting up?
Hope this helps.
Thanks,
Bob
On Mar 11, 2016, at 7:18 PM, Alejandro Fernandez
wrote:
> +others who have more insight into BluePrints
>
> On 3/11/16, 3:24 PM, "Bhuvnesh Chaudhary" wrote:
>
>> Hello Sebastian, Alejandro, Andrew,
>>
>> Referring to the discussion on RB: https://reviews.apache.org/r/43948
>> , it appears that while
>> deploying clusters using Blueprints, RCO is not honored. Please confirm if
>> this understanding is correct.
>>
>> While running internal test suites for HAWQ, we deploy the clusters using
>> BP, and we need a specific order in which the HAWQ components must be
>> initialized / started.
>>
>> "HAWQ Standby" component should be initialized after "HAWQ Master"
>> component as it has to copy the contents from HAWQ Master. However, since
>> RCO is not honored, we often come across issues as HAWQ Standby start /
>> initialization before HAWQ Master.
>>
>> Could you please let us know if there any work already going on for
>> bringing in RCO dependency for Blueprints, if not is there any other
>> alternative which can be used to enforce the dependency locally, or
>> something else which you suggest.
{code}
> Blueprint should have a flag to allow configuring use of RCO vs Retry method
>
>
> Key: AMBARI-15417
> URL: https://issues.apache.org/jira/browse/AMBARI-15417
> Project: Ambari
> Issue Type: Bug
> Components: blueprints
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>
> With Blueprint deploy's, role command oder (RCO) is not honored.
> Currently, in order to mitigate failure for a service start due to
> dependencies on other services, blueprint deploy uses retry mechanism to
> ensure that the services are started and their prerequisite are met.
> However, retry mechanism in some cases can cause the install / start time to
> take long and might need additional logic on component spec
[jira] [Assigned] (AMBARI-15396) Config recommendations for installed services are getting cleared out
[ https://issues.apache.org/jira/browse/AMBARI-15396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lav Jain reassigned AMBARI-15396: - Assignee: Lav Jain > Config recommendations for installed services are getting cleared out > - > > Key: AMBARI-15396 > URL: https://issues.apache.org/jira/browse/AMBARI-15396 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.2.0 >Reporter: Lav Jain >Assignee: Lav Jain > Fix For: 2.3.0, 2.2.2 > > Attachments: AMBARI-15396.branch22.patch > > > As part of AMBARI-15189, dfs.allow.truncate was set to true if HAWQ service > is being installed. However, the recommendation is getting cleared in > ambari-web because HDFS is already installed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15419) After EU Some Services Fail To Start Because of Missing JKS Files
[
https://issues.apache.org/jira/browse/AMBARI-15419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-15419:
-
Status: Patch Available (was: Open)
> After EU Some Services Fail To Start Because of Missing JKS Files
> -
>
> Key: AMBARI-15419
> URL: https://issues.apache.org/jira/browse/AMBARI-15419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15419.patch
>
>
> During an upgrade, configuration files from the old stack are not copied to
> the new configuration folders created using {{conf-select}}. This means that
> files which Ambari does not track, are never included in the new
> configuration directories.
> This is what happens on a clean install:
> {noformat}
> /etc/foo/conf (physical conf files placed here)
> /usr/hdp//foo/conf -> /etc/foo/conf
> {noformat}
> Ambari then uses {{conf-select}} to change this:
> {noformat}
> /etc/foo/conf.backup (contents of original /etc/foo/conf folder)
> /etc/foo/conf -> /usr/hdp//foo/conf
> /usr/hdp//foo/conf -> /etc/foo//0
> /etc/foo//0 (physical conf files placed here)
> {noformat}
> But in this scenario, we make sure to seed {{/etc/foo//0}} with the
> files which were in {{/etc/foo/conf}} originally, including files which we
> don't track. This is to prevent files, like JKS keystores, from being lost.
> *Now the upgrade scenario:*
>
> If you already have {{/usr/hdp/2.3.0.0}} installed, that means that you have
> {{/etc/foo/conf}} and all associated files already on the disk. When you
> distribute HDP 2.4, {{/usr/hdp/2.4.0.0}} is created. However, it cannot
> overwrite any existing configurations since you haven't upgraded yet. So, it
> basically does nothing with the configurations. We invoke {{conf-select}} to
> create {{/etc/foo/2.4.0.0/0}}, but it is never seeded with any values from
> {{/etc/foo/2.3.0.0/0}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15419) After EU Some Services Fail To Start Because of Missing JKS Files
[
https://issues.apache.org/jira/browse/AMBARI-15419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-15419:
-
Attachment: AMBARI-15419.patch
> After EU Some Services Fail To Start Because of Missing JKS Files
> -
>
> Key: AMBARI-15419
> URL: https://issues.apache.org/jira/browse/AMBARI-15419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15419.patch
>
>
> During an upgrade, configuration files from the old stack are not copied to
> the new configuration folders created using {{conf-select}}. This means that
> files which Ambari does not track, are never included in the new
> configuration directories.
> This is what happens on a clean install:
> {noformat}
> /etc/foo/conf (physical conf files placed here)
> /usr/hdp//foo/conf -> /etc/foo/conf
> {noformat}
> Ambari then uses {{conf-select}} to change this:
> {noformat}
> /etc/foo/conf.backup (contents of original /etc/foo/conf folder)
> /etc/foo/conf -> /usr/hdp//foo/conf
> /usr/hdp//foo/conf -> /etc/foo//0
> /etc/foo//0 (physical conf files placed here)
> {noformat}
> But in this scenario, we make sure to seed {{/etc/foo//0}} with the
> files which were in {{/etc/foo/conf}} originally, including files which we
> don't track. This is to prevent files, like JKS keystores, from being lost.
> *Now the upgrade scenario:*
>
> If you already have {{/usr/hdp/2.3.0.0}} installed, that means that you have
> {{/etc/foo/conf}} and all associated files already on the disk. When you
> distribute HDP 2.4, {{/usr/hdp/2.4.0.0}} is created. However, it cannot
> overwrite any existing configurations since you haven't upgraded yet. So, it
> basically does nothing with the configurations. We invoke {{conf-select}} to
> create {{/etc/foo/2.4.0.0/0}}, but it is never seeded with any values from
> {{/etc/foo/2.3.0.0/0}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15419) After EU Some Services Fail To Start Because of Missing JKS Files
[
https://issues.apache.org/jira/browse/AMBARI-15419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-15419:
-
Description:
During an upgrade, configuration files from the old stack are not copied to the
new configuration folders created using {{conf-select}}. This means that files
which Ambari does not track, are never included in the new configuration
directories.
This is what happens on a clean install:
{noformat}
/etc/foo/conf (physical conf files placed here)
/usr/hdp//foo/conf -> /etc/foo/conf
{noformat}
Ambari then uses {{conf-select}} to change this:
{noformat}
/etc/foo/conf.backup (contents of original /etc/foo/conf folder)
/etc/foo/conf -> /usr/hdp//foo/conf
/usr/hdp//foo/conf -> /etc/foo//0
/etc/foo//0 (physical conf files placed here)
{noformat}
But in this scenario, we make sure to seed {{/etc/foo//0}} with the
files which were in {{/etc/foo/conf}} originally, including files which we
don't track. This is to prevent files, like JKS keystores, from being lost.
*Now the upgrade scenario:*
If you already have {{/usr/hdp/2.3.0.0}} installed, that means that you have
{{/etc/foo/conf}} and all associated files already on the disk. When you
distribute HDP 2.4, {{/usr/hdp/2.4.0.0}} is created. However, it cannot
overwrite any existing configurations since you haven't upgraded yet. So, it
basically does nothing with the configurations. We invoke {{conf-select}} to
create {{/etc/foo/2.4.0.0/0}}, but it is never seeded with any values from
{{/etc/foo/2.3.0.0/0}}.
was:
During an upgrade, configuration files from the old stack are not copied to the
new configuration folders created using {{conf-select}}. This means that files
which Ambari does not track, are never included in the new configuration
directories.
This is what happens on a clean install:
{noformat}
/etc/foo/conf (physical conf files placed here)
/usr/hdp//foo/conf -> /etc/foo/conf
{noformat}
Ambari then uses {{conf-select}} to change this:
{noformat}
/etc/foo/conf.backup (contents of original /etc/foo/conf folder)
/etc/foo/conf -> /usr/hdp//foo/conf
/usr/hdp//foo/conf -> /etc/foo//0
/etc/foo//0 (physical conf files placed here)
{noformat}
But in this scenario, we make sure to seed {{/etc/foo//0}} with the
files which were in {{/etc/foo/conf}} originally, including files which we
don't track. This is to prevent files, like JKS keystores, from being lost.
Now the upgrade scenario:
If you already have {{/usr/hdp/2.3.0.0}} install, that means that you have
{{/etc/foo/conf}} and all associated files already on the disk. When you
distribute HDP 2.4, {{/usr/hdp/2.4.0.0}} is created. However, it cannot
overwrite any existing configurations since you haven't upgraded yet. So, it
basically does nothing with the configurations.
> After EU Some Services Fail To Start Because of Missing JKS Files
> -
>
> Key: AMBARI-15419
> URL: https://issues.apache.org/jira/browse/AMBARI-15419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.2.2
>
>
> During an upgrade, configuration files from the old stack are not copied to
> the new configuration folders created using {{conf-select}}. This means that
> files which Ambari does not track, are never included in the new
> configuration directories.
> This is what happens on a clean install:
> {noformat}
> /etc/foo/conf (physical conf files placed here)
> /usr/hdp//foo/conf -> /etc/foo/conf
> {noformat}
> Ambari then uses {{conf-select}} to change this:
> {noformat}
> /etc/foo/conf.backup (contents of original /etc/foo/conf folder)
> /etc/foo/conf -> /usr/hdp//foo/conf
> /usr/hdp//foo/conf -> /etc/foo//0
> /etc/foo//0 (physical conf files placed here)
> {noformat}
> But in this scenario, we make sure to seed {{/etc/foo//0}} with the
> files which were in {{/etc/foo/conf}} originally, including files which we
> don't track. This is to prevent files, like JKS keystores, from being lost.
> *Now the upgrade scenario:*
>
> If you already have {{/usr/hdp/2.3.0.0}} installed, that means that you have
> {{/etc/foo/conf}} and all associated files already on the disk. When you
> distribute HDP 2.4, {{/usr/hdp/2.4.0.0}} is created. However, it cannot
> overwrite any existing configurations since you haven't upgraded yet. So, it
> basically does nothing with the configurations. We invoke {{conf-select}} to
> create {{/etc/foo/2.4.0.0/0}}, but it is never seeded with any values from
> {{/etc/foo/2.3.0.0/0}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15419) After EU Some Services Fail To Start Because of Missing JKS Files
[
https://issues.apache.org/jira/browse/AMBARI-15419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-15419:
-
Description:
During an upgrade, configuration files from the old stack are not copied to the
new configuration folders created using {{conf-select}}. This means that files
which Ambari does not track, are never included in the new configuration
directories.
This is what happens on a clean install:
{noformat}
/etc/foo/conf (physical conf files placed here)
/usr/hdp//foo/conf -> /etc/foo/conf
{noformat}
Ambari then uses {{conf-select}} to change this:
{noformat}
/etc/foo/conf.backup (contents of original /etc/foo/conf folder)
/etc/foo/conf -> /usr/hdp//foo/conf
/usr/hdp//foo/conf -> /etc/foo//0
/etc/foo//0 (physical conf files placed here)
{noformat}
But in this scenario, we make sure to seed {{/etc/foo//0}} with the
files which were in {{/etc/foo/conf}} originally, including files which we
don't track. This is to prevent files, like JKS keystores, from being lost.
Now the upgrade scenario:
If you already have {{/usr/hdp/2.3.0.0}} install, that means that you have
{{/etc/foo/conf}} and all associated files already on the disk. When you
distribute HDP 2.4, {{/usr/hdp/2.4.0.0}} is created. However, it cannot
overwrite any existing configurations since you haven't upgraded yet. So, it
basically does nothing with the configurations.
was:
During an upgrade, configuration files from the old stack are not copied to the
new configuration folders created using {{conf-select}}. This means that files
which Ambari does not track, are never included in the new configuration
directories.
This is what happens on a clean install:
{noformat}
/etc/foo/conf (physical conf files placed here)
/usr/hdp//foo/conf -> /etc/foo/conf
{noformat}
Ambari then uses {{conf-select}} to change this:
{noformat}
/etc/foo/conf.backup (contents of original /etc/foo/conf folder)
/etc/foo/conf -> /usr/hdp//foo/conf
/usr/hdp//foo/conf -> /etc/foo//0
/etc/foo//0 (physical conf files placed here)
{noformat}
But in this scenario, we make sure to seed {{/etc/foo//0}} with the
files which were in {{/etc/foo/conf}} originally, include files which we don't
track.
Now the upgrade scnenario. If you already have {{/usr/hdp/2.3.0.0}} install,
that means that you have {{/etc/foo/conf}} and all associated files already on
the disk. When you distribute HDP 2.4, {{/usr/hdp/2.4.0.0}} is created.
However, it cannot overwrite any existing configurations since you haven't
upgraded yet. So, it basically does nothing with the configurations.
> After EU Some Services Fail To Start Because of Missing JKS Files
> -
>
> Key: AMBARI-15419
> URL: https://issues.apache.org/jira/browse/AMBARI-15419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.2.2
>
>
> During an upgrade, configuration files from the old stack are not copied to
> the new configuration folders created using {{conf-select}}. This means that
> files which Ambari does not track, are never included in the new
> configuration directories.
> This is what happens on a clean install:
> {noformat}
> /etc/foo/conf (physical conf files placed here)
> /usr/hdp//foo/conf -> /etc/foo/conf
> {noformat}
> Ambari then uses {{conf-select}} to change this:
> {noformat}
> /etc/foo/conf.backup (contents of original /etc/foo/conf folder)
> /etc/foo/conf -> /usr/hdp//foo/conf
> /usr/hdp//foo/conf -> /etc/foo//0
> /etc/foo//0 (physical conf files placed here)
> {noformat}
> But in this scenario, we make sure to seed {{/etc/foo//0}} with the
> files which were in {{/etc/foo/conf}} originally, including files which we
> don't track. This is to prevent files, like JKS keystores, from being lost.
> Now the upgrade scenario:
>
> If you already have {{/usr/hdp/2.3.0.0}} install, that means that you have
> {{/etc/foo/conf}} and all associated files already on the disk. When you
> distribute HDP 2.4, {{/usr/hdp/2.4.0.0}} is created. However, it cannot
> overwrite any existing configurations since you haven't upgraded yet. So, it
> basically does nothing with the configurations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15419) After EU Some Services Fail To Start Because of Missing JKS Files
Jonathan Hurley created AMBARI-15419:
Summary: After EU Some Services Fail To Start Because of Missing
JKS Files
Key: AMBARI-15419
URL: https://issues.apache.org/jira/browse/AMBARI-15419
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.2.2
During an upgrade, configuration files from the old stack are not copied to the
new configuration folders created using {{conf-select}}. This means that files
which Ambari does not track, are never included in the new configuration
directories.
This is what happens on a clean install:
{noformat}
/etc/foo/conf (physical conf files placed here)
/usr/hdp//foo/conf -> /etc/foo/conf
{noformat}
Ambari then uses {{conf-select}} to change this:
{noformat}
/etc/foo/conf.backup (contents of original /etc/foo/conf folder)
/etc/foo/conf -> /usr/hdp//foo/conf
/usr/hdp//foo/conf -> /etc/foo//0
/etc/foo//0 (physical conf files placed here)
{noformat}
But in this scenario, we make sure to seed {{/etc/foo//0}} with the
files which were in {{/etc/foo/conf}} originally, include files which we don't
track.
Now the upgrade scnenario. If you already have {{/usr/hdp/2.3.0.0}} install,
that means that you have {{/etc/foo/conf}} and all associated files already on
the disk. When you distribute HDP 2.4, {{/usr/hdp/2.4.0.0}} is created.
However, it cannot overwrite any existing configurations since you haven't
upgraded yet. So, it basically does nothing with the configurations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15402) AMS fails to start with TTL for column family 0 must be positive after upgrade
[
https://issues.apache.org/jira/browse/AMBARI-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194675#comment-15194675
]
Hadoop QA commented on AMBARI-15402:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12793342/AMBARI-15402-trunk_4.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5861//console
This message is automatically generated.
> AMS fails to start with TTL for column family 0 must be positive after upgrade
> --
>
> Key: AMBARI-15402
> URL: https://issues.apache.org/jira/browse/AMBARI-15402
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-15402-trunk_4.patch
>
>
> STR:
> Deploy ambari (version < 2.2.2) with AMS
> Upgrade ambari to 2.2.2 version
> Result: AMS failed to start.
> {code}
> 14:13:41,116 FATAL [main] ApplicationHistoryServer:140 - Error starting
> ApplicationHistoryServer
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.MetricsSystemInitializationException:
> Error creating Metrics Schema in HBase
> using Phoenix.
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.PhoenixHBaseAccessor.initMetricSchema(PhoenixHBaseAccessor.java:31
> 8)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.initializeSubsystem(HBaseTimelineMetricSt
> ore.java:84)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.HBaseTimelineMetricStore.serviceInit(HBaseTimelineMetricStore.java
> :76)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:84)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:137)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: org.apache.phoenix.exception.PhoenixIOException:
> org.apache.hadoop.hbase.DoNotRetryIOException: TTL for column family 0 must
> be positive. S
> et hbase.table.sanity.checks to false at conf or table descriptor if you want
> to bypass sanity checks
> at
> org.apache.hadoop.hbase.master.HMaster.warnOrThrowExceptionForFailure(HMaster.java:1734)
> at
> org.apache.hadoop.hbase.master.HMaster.sanityCheckTableDescriptor(HMaster.java:1633)
> at
> org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1521)
> at
> org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:453)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:53170)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2114)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:101)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:130)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:107)
> at java.lang.Thread.run(Thread.java:745)
> at
> org.apache.phoenix.util.ServerUtil.parseServerException(ServerUtil.java:108)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl.ensureTableCreated(ConnectionQueryServicesImpl.java:877)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl.createTable(ConnectionQueryServicesImpl.java:1174)
> at
> org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:1974)
> at
> org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:770)
> at
> org.apache.phoenix.compile.CreateTableCompiler$2.execute(CreateTableCompiler.java:186)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:305)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:297)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation
[jira] [Commented] (AMBARI-15417) Blueprint should have a flag to allow configuring use of RCO vs Retry method
[ https://issues.apache.org/jira/browse/AMBARI-15417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194671#comment-15194671 ] jun aoki commented on AMBARI-15417: --- I don't have a background knowledge of why RCO is only honored through Wizard, but would like to chip in my idea. The service dependencies (RCO) should be always honored regardless of user input type (Through Wizard, or Blueprint, or even some other means in future) because it should be simply a part of stack definition. So I'd like to downvote to introduce a flag to control whether or not RCO is used. > Blueprint should have a flag to allow configuring use of RCO vs Retry method > > > Key: AMBARI-15417 > URL: https://issues.apache.org/jira/browse/AMBARI-15417 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: trunk >Reporter: bhuvnesh chaudhary > > With Blueprint deploy's, role command oder (RCO) is not honored. > Currently, in order to mitigate failure for a service start due to > dependencies on other services, blueprint deploy uses retry mechanism to > ensure that the services are started and their prerequisite are met. > However, retry mechanism in some cases can cause the install / start time to > take long and might need additional logic on component specific installation > to handle retries. > In order to provide with flexibility, we should put up a flag in blueprints > which drive the required behavior. (Use RCO vs Use Retry) > Say: The flag name is use_rco (Change what seems better)) > By default, the value of use_rco can be false and if someone wan't to > override it they can specify it as true in the blueprint. > Note: Keeping it as false by default as it has been already there since > Ambari 2.1.0. Hopefully, even if we set this to true by default, it should > not impact customers except a few. But we can make this decision based on > communities opinion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15382) Alert for updating HAWQ namespace after enabling HDFS HA
[ https://issues.apache.org/jira/browse/AMBARI-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194667#comment-15194667 ] Lav Jain commented on AMBARI-15382: --- There seems to be a problem with Hadoop QA as the build was aborted when testing ambari-web due to unrelated issues. Other ambari-web builds also ran into the same issue with Hadoop QA. Ran the tests locally on trunk as well as branch 2.2 > Alert for updating HAWQ namespace after enabling HDFS HA > - > > Key: AMBARI-15382 > URL: https://issues.apache.org/jira/browse/AMBARI-15382 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk, 2.2.0 >Reporter: Lav Jain >Assignee: Lav Jain >Priority: Minor > Fix For: 2.3.0, 2.2.2 > > Attachments: AMBARI-15382.branch22.patch, > AMBARI-15382.branch22.v2.patch, AMBARI-15382.patch, AMBARI-15382.v2.patch, > Screen Shot 2016-03-10 at 5.06.47 PM.png, Screen Shot 2016-03-10 at 5.13.41 > PM.png > > > Alert user on step1 of the wizard (conditional if HAWQ is installed). Repeat > the message when the namenode HA wizard is done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15382) Alert for updating HAWQ namespace after enabling HDFS HA
[ https://issues.apache.org/jira/browse/AMBARI-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194668#comment-15194668 ] bhuvnesh chaudhary commented on AMBARI-15382: - On behalf of [~lavjain] mvn test was successful, Manual testing on 2.2 and trunk was successful. The QA job did not run successfully due to issue which was not related to this patch. > Alert for updating HAWQ namespace after enabling HDFS HA > - > > Key: AMBARI-15382 > URL: https://issues.apache.org/jira/browse/AMBARI-15382 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk, 2.2.0 >Reporter: Lav Jain >Assignee: Lav Jain >Priority: Minor > Fix For: 2.3.0, 2.2.2 > > Attachments: AMBARI-15382.branch22.patch, > AMBARI-15382.branch22.v2.patch, AMBARI-15382.patch, AMBARI-15382.v2.patch, > Screen Shot 2016-03-10 at 5.06.47 PM.png, Screen Shot 2016-03-10 at 5.13.41 > PM.png > > > Alert user on step1 of the wizard (conditional if HAWQ is installed). Repeat > the message when the namenode HA wizard is done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15382) Alert for updating HAWQ namespace after enabling HDFS HA
[ https://issues.apache.org/jira/browse/AMBARI-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lav Jain updated AMBARI-15382: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Alert for updating HAWQ namespace after enabling HDFS HA > - > > Key: AMBARI-15382 > URL: https://issues.apache.org/jira/browse/AMBARI-15382 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk, 2.2.0 >Reporter: Lav Jain >Assignee: Lav Jain >Priority: Minor > Fix For: 2.3.0, 2.2.2 > > Attachments: AMBARI-15382.branch22.patch, > AMBARI-15382.branch22.v2.patch, AMBARI-15382.patch, AMBARI-15382.v2.patch, > Screen Shot 2016-03-10 at 5.06.47 PM.png, Screen Shot 2016-03-10 at 5.13.41 > PM.png > > > Alert user on step1 of the wizard (conditional if HAWQ is installed). Repeat > the message when the namenode HA wizard is done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15382) Alert for updating HAWQ namespace after enabling HDFS HA
[ https://issues.apache.org/jira/browse/AMBARI-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lav Jain updated AMBARI-15382: -- Fix Version/s: 2.3.0 > Alert for updating HAWQ namespace after enabling HDFS HA > - > > Key: AMBARI-15382 > URL: https://issues.apache.org/jira/browse/AMBARI-15382 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk, 2.2.0 >Reporter: Lav Jain >Assignee: Lav Jain >Priority: Minor > Fix For: 2.3.0, 2.2.2 > > Attachments: AMBARI-15382.branch22.patch, > AMBARI-15382.branch22.v2.patch, AMBARI-15382.patch, AMBARI-15382.v2.patch, > Screen Shot 2016-03-10 at 5.06.47 PM.png, Screen Shot 2016-03-10 at 5.13.41 > PM.png > > > Alert user on step1 of the wizard (conditional if HAWQ is installed). Repeat > the message when the namenode HA wizard is done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15382) Alert for updating HAWQ namespace after enabling HDFS HA
[ https://issues.apache.org/jira/browse/AMBARI-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194666#comment-15194666 ] bhuvnesh chaudhary commented on AMBARI-15382: - Committed branch: 2613351185e787c1ad218d972c15a1de8d749390 trunk: ac774546d1bdb4a38ffb391b75062c12b776d53a > Alert for updating HAWQ namespace after enabling HDFS HA > - > > Key: AMBARI-15382 > URL: https://issues.apache.org/jira/browse/AMBARI-15382 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk, 2.2.0 >Reporter: Lav Jain >Assignee: Lav Jain >Priority: Minor > Fix For: 2.2.2 > > Attachments: AMBARI-15382.branch22.patch, > AMBARI-15382.branch22.v2.patch, AMBARI-15382.patch, AMBARI-15382.v2.patch, > Screen Shot 2016-03-10 at 5.06.47 PM.png, Screen Shot 2016-03-10 at 5.13.41 > PM.png > > > Alert user on step1 of the wizard (conditional if HAWQ is installed). Repeat > the message when the namenode HA wizard is done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15418) hive.server2.authentication.pam.services and hive.server2.custom.authentication.class are required at NOSASL
Wataru Yukawa created AMBARI-15418: -- Summary: hive.server2.authentication.pam.services and hive.server2.custom.authentication.class are required at NOSASL Key: AMBARI-15418 URL: https://issues.apache.org/jira/browse/AMBARI-15418 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.2.1 Environment: HDP2.4 CentOS6 JDK1.8 Reporter: Wataru Yukawa I use HDP2.3.4 and I use Hive with hive.server2.authentication=NOSASL After I upgrade HDP2.4, I notice that hive.server2.authentication.pam.services and hive.server2.custom.authentication.class are required. https://gyazo.com/b3bf1cc1c6b8720292a4632efdea9bd4 In my understanding, because I use Hive with hive.server2.authentication=NOSASL, hive.server2.authentication.pam.services and hive.server2.custom.authentication.class are not required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15411) RBAC: Name filter does not work for user with no role
[ https://issues.apache.org/jira/browse/AMBARI-15411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194607#comment-15194607 ] Hudson commented on AMBARI-15411: - FAILURE: Integrated in Ambari-trunk-Commit #4493 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4493/]) AMBARI-15411. RBAC: Name filter does not work for user with no role (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b88aaa3ea00be20ec65590d5dd4f9a67d2d8fecc]) * ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Cluster.js > RBAC: Name filter does not work for user with no role > - > > Key: AMBARI-15411 > URL: https://issues.apache.org/jira/browse/AMBARI-15411 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-15411.patch > > > After type in characters in "Name" filter, matching matching users with > role=None is not showing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15075) Edit Widget Wizard still open even though it was closed/saved in the previous step
[ https://issues.apache.org/jira/browse/AMBARI-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194606#comment-15194606 ] Hudson commented on AMBARI-15075: - FAILURE: Integrated in Ambari-trunk-Commit #4493 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4493/]) AMBARI-15075. Edit Widget Wizard still open even though it was (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3eb766410f35cd8769f9e77969ef0c4b0c5bcb90]) * ambari-web/app/controllers/main/service/widgets/edit_controller.js > Edit Widget Wizard still open even though it was closed/saved in the previous > step > -- > > Key: AMBARI-15075 > URL: https://issues.apache.org/jira/browse/AMBARI-15075 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15075.2.patch, AMBARI-15075.3.patch, > AMBARI-15075.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15414) Version Register/manage: UX edits #1
[ https://issues.apache.org/jira/browse/AMBARI-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194608#comment-15194608 ] Hudson commented on AMBARI-15414: - FAILURE: Integrated in Ambari-trunk-Commit #4493 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4493/]) AMBARI-15414. Version Register/manage: UX edits #1.(xiwang) (xiwang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c612a462cbb1cef67a245b78234e66ab541577b8]) * ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_column.hbs * ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js * ambari-web/app/styles/stack_versions.less * ambari-admin/src/main/resources/ui/admin-web/app/styles/main.css * ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js * ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js * ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html > Version Register/manage: UX edits #1 > > > Key: AMBARI-15414 > URL: https://issues.apache.org/jira/browse/AMBARI-15414 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15414.patch, Ambari-15414-1.png, > Ambari-15414-2.png, Ambari-15414-3.png, Ambari-15414-4.png, Ambari-15414-5.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15401) AMS service failed to start
[ https://issues.apache.org/jira/browse/AMBARI-15401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194605#comment-15194605 ] Hudson commented on AMBARI-15401: - FAILURE: Integrated in Ambari-trunk-Commit #4493 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4493/]) AMBARI-15401 AMS service failed to start (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=be57b745dbd8cb695fed883130a6028825fe0241]) * ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-env.xml > AMS service failed to start > --- > > Key: AMBARI-15401 > URL: https://issues.apache.org/jira/browse/AMBARI-15401 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics, stacks >Affects Versions: 2.2.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15401-trunk_1.patch > > > STR: > 1) Setup and configure LDAPS > 2) Install Ambari and deploy cluster > Results ams service check fails, all the following start commands aborted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15416) Grafana password is required field after upgrade from 2.2.0 to 2.2.2
[ https://issues.apache.org/jira/browse/AMBARI-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-15416: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to 2.2 and trunk. > Grafana password is required field after upgrade from 2.2.0 to 2.2.2 > > > Key: AMBARI-15416 > URL: https://issues.apache.org/jira/browse/AMBARI-15416 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 2.2.2 > > Attachments: AMBARI-15416.patch > > > The _metrics_grafana_password_ shows up as the required field even though > Grafana component is not added. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15415) Fix new HDFS AMS alerts to account for NN rpc ports
[ https://issues.apache.org/jira/browse/AMBARI-15415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-15415: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to 2.2 and trunk. > Fix new HDFS AMS alerts to account for NN rpc ports > --- > > Key: AMBARI-15415 > URL: https://issues.apache.org/jira/browse/AMBARI-15415 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 2.2.2 > > Attachments: AMBARI-15415.patch > > > AMBARI-15293, changed the metric names for rpc and rpcdetailed metrics for NN > based on the port configuration for client / datanode / healthcheck rpc > We need a fix this by cloning the alert definition that we have into 2 > different alerts for Client / DN ports. > *Note*: By default client and DN RPC ports are the same 8020 and for this > case DN rpc alert should be a NOOP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-15413) Metrics Grafana Failed to start
[ https://issues.apache.org/jira/browse/AMBARI-15413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-15413. Resolution: Fixed Pushed to trunk and branch-2.2 > Metrics Grafana Failed to start > --- > > Key: AMBARI-15413 > URL: https://issues.apache.org/jira/browse/AMBARI-15413 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15413.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15417) Blueprint should have a flag to allow configuring use of RCO vs Retry method
bhuvnesh chaudhary created AMBARI-15417: --- Summary: Blueprint should have a flag to allow configuring use of RCO vs Retry method Key: AMBARI-15417 URL: https://issues.apache.org/jira/browse/AMBARI-15417 Project: Ambari Issue Type: Bug Components: blueprints Affects Versions: trunk Reporter: bhuvnesh chaudhary With Blueprint deploy's, role command oder (RCO) is not honored. Currently, in order to mitigate failure for a service start due to dependencies on other services, blueprint deploy uses retry mechanism to ensure that the services are started and their prerequisite are met. However, retry mechanism in some cases can cause the install / start time to take long and might need additional logic on component specific installation to handle retries. In order to provide with flexibility, we should put up a flag in blueprints which drive the required behavior. (Use RCO vs Use Retry) Say: The flag name is use_rco (Change what seems better)) By default, the value of use_rco can be false and if someone wan't to override it they can specify it as true in the blueprint. Note: Keeping it as false by default as it has been already there since Ambari 2.1.0. Hopefully, even if we set this to true by default, it should not impact customers except a few. But we can make this decision based on communities opinion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15360) (1). Support install of 'Hive Server Interactive' and related 'Tez' binaries. (2). Parameter declarations in 'params_linux' and 'status_params' related to 'Hive Server
[ https://issues.apache.org/jira/browse/AMBARI-15360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-15360: - Status: Patch Available (was: Open) > (1). Support install of 'Hive Server Interactive' and related 'Tez' binaries. > (2). Parameter declarations in 'params_linux' and 'status_params' related to > 'Hive Server Interactive'. > - > > Key: AMBARI-15360 > URL: https://issues.apache.org/jira/browse/AMBARI-15360 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-15360-1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15360) (1). Support install of 'Hive Server Interactive' and related 'Tez' binaries. (2). Parameter declarations in 'params_linux' and 'status_params' related to 'Hive Server
[ https://issues.apache.org/jira/browse/AMBARI-15360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-15360: - Attachment: AMBARI-15360-1.patch > (1). Support install of 'Hive Server Interactive' and related 'Tez' binaries. > (2). Parameter declarations in 'params_linux' and 'status_params' related to > 'Hive Server Interactive'. > - > > Key: AMBARI-15360 > URL: https://issues.apache.org/jira/browse/AMBARI-15360 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-15360-1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15403) Definition state is empty while some wizard is running
[
https://issues.apache.org/jira/browse/AMBARI-15403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194467#comment-15194467
]
Hadoop QA commented on AMBARI-15403:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12793323/AMBARI-15403.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/5859//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5859//console
This message is automatically generated.
> Definition state is empty while some wizard is running
> --
>
> Key: AMBARI-15403
> URL: https://issues.apache.org/jira/browse/AMBARI-15403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15403.patch, IBcZW.jpg
>
>
> User A (with admin rules) starts ASW
> User B (with admin rules) is on the Alert Definition details page
> {{State}} is shown empty (see screenshot attached)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15416) Grafana password is required field after upgrade from 2.2.0 to 2.2.2
[ https://issues.apache.org/jira/browse/AMBARI-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-15416: - Status: Patch Available (was: Open) > Grafana password is required field after upgrade from 2.2.0 to 2.2.2 > > > Key: AMBARI-15416 > URL: https://issues.apache.org/jira/browse/AMBARI-15416 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 2.2.2 > > Attachments: AMBARI-15416.patch > > > The _metrics_grafana_password_ shows up as the required field even though > Grafana component is not added. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15416) Grafana password is required field after upgrade from 2.2.0 to 2.2.2
[ https://issues.apache.org/jira/browse/AMBARI-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-15416: - Attachment: AMBARI-15416.patch > Grafana password is required field after upgrade from 2.2.0 to 2.2.2 > > > Key: AMBARI-15416 > URL: https://issues.apache.org/jira/browse/AMBARI-15416 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 2.2.2 > > Attachments: AMBARI-15416.patch > > > The _metrics_grafana_password_ shows up as the required field even though > Grafana component is not added. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15416) Grafana password is required field after upgrade from 2.2.0 to 2.2.2
Siddharth Wagle created AMBARI-15416: Summary: Grafana password is required field after upgrade from 2.2.0 to 2.2.2 Key: AMBARI-15416 URL: https://issues.apache.org/jira/browse/AMBARI-15416 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.2.2 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Fix For: 2.2.2 The _metrics_grafana_password_ shows up as the required field even though Grafana component is not added. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15415) Fix new HDFS AMS alerts to account for NN rpc ports
[ https://issues.apache.org/jira/browse/AMBARI-15415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-15415: - Status: Patch Available (was: Open) > Fix new HDFS AMS alerts to account for NN rpc ports > --- > > Key: AMBARI-15415 > URL: https://issues.apache.org/jira/browse/AMBARI-15415 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 2.2.2 > > Attachments: AMBARI-15415.patch > > > AMBARI-15293, changed the metric names for rpc and rpcdetailed metrics for NN > based on the port configuration for client / datanode / healthcheck rpc > We need a fix this by cloning the alert definition that we have into 2 > different alerts for Client / DN ports. > *Note*: By default client and DN RPC ports are the same 8020 and for this > case DN rpc alert should be a NOOP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15415) Fix new HDFS AMS alerts to account for NN rpc ports
[ https://issues.apache.org/jira/browse/AMBARI-15415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-15415: - Attachment: AMBARI-15415.patch > Fix new HDFS AMS alerts to account for NN rpc ports > --- > > Key: AMBARI-15415 > URL: https://issues.apache.org/jira/browse/AMBARI-15415 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 2.2.2 > > Attachments: AMBARI-15415.patch > > > AMBARI-15293, changed the metric names for rpc and rpcdetailed metrics for NN > based on the port configuration for client / datanode / healthcheck rpc > We need a fix this by cloning the alert definition that we have into 2 > different alerts for Client / DN ports. > *Note*: By default client and DN RPC ports are the same 8020 and for this > case DN rpc alert should be a NOOP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15415) Fix new HDFS AMS alerts to account for NN rpc ports
Siddharth Wagle created AMBARI-15415: Summary: Fix new HDFS AMS alerts to account for NN rpc ports Key: AMBARI-15415 URL: https://issues.apache.org/jira/browse/AMBARI-15415 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.2.2 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Fix For: 2.2.2 AMBARI-15293, changed the metric names for rpc and rpcdetailed metrics for NN based on the port configuration for client / datanode / healthcheck rpc We need a fix this by cloning the alert definition that we have into 2 different alerts for Client / DN ports. *Note*: By default client and DN RPC ports are the same 8020 and for this case DN rpc alert should be a NOOP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-15075) Edit Widget Wizard still open even though it was closed/saved in the previous step
[ https://issues.apache.org/jira/browse/AMBARI-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly resolved AMBARI-15075. - Resolution: Fixed Patch committed to trunk and branch-2.2 > Edit Widget Wizard still open even though it was closed/saved in the previous > step > -- > > Key: AMBARI-15075 > URL: https://issues.apache.org/jira/browse/AMBARI-15075 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15075.2.patch, AMBARI-15075.3.patch, > AMBARI-15075.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15414) Version Register/manage: UX edits #1
[ https://issues.apache.org/jira/browse/AMBARI-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-15414: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Version Register/manage: UX edits #1 > > > Key: AMBARI-15414 > URL: https://issues.apache.org/jira/browse/AMBARI-15414 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15414.patch, Ambari-15414-1.png, > Ambari-15414-2.png, Ambari-15414-3.png, Ambari-15414-4.png, Ambari-15414-5.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15414) Version Register/manage: UX edits #1
[ https://issues.apache.org/jira/browse/AMBARI-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194432#comment-15194432 ] Xi Wang commented on AMBARI-15414: -- Got +1 on review board > Version Register/manage: UX edits #1 > > > Key: AMBARI-15414 > URL: https://issues.apache.org/jira/browse/AMBARI-15414 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15414.patch, Ambari-15414-1.png, > Ambari-15414-2.png, Ambari-15414-3.png, Ambari-15414-4.png, Ambari-15414-5.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15075) Edit Widget Wizard still open even though it was closed/saved in the previous step
[ https://issues.apache.org/jira/browse/AMBARI-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194430#comment-15194430 ] Yusaku Sako commented on AMBARI-15075: -- +1 for the patch. > Edit Widget Wizard still open even though it was closed/saved in the previous > step > -- > > Key: AMBARI-15075 > URL: https://issues.apache.org/jira/browse/AMBARI-15075 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15075.2.patch, AMBARI-15075.3.patch, > AMBARI-15075.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15401) AMS service failed to start
[ https://issues.apache.org/jira/browse/AMBARI-15401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194426#comment-15194426 ] Hudson commented on AMBARI-15401: - SUCCESS: Integrated in Ambari-branch-2.2 #509 (See [https://builds.apache.org/job/Ambari-branch-2.2/509/]) AMBARI-15401 AMS service failed to start (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dfc0e753ba358e614e0ad4b921be69b0cd563780]) * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-env.xml * ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py > AMS service failed to start > --- > > Key: AMBARI-15401 > URL: https://issues.apache.org/jira/browse/AMBARI-15401 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics, stacks >Affects Versions: 2.2.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15401-trunk_1.patch > > > STR: > 1) Setup and configure LDAPS > 2) Install Ambari and deploy cluster > Results ams service check fails, all the following start commands aborted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15348) Ambari upgrade/start commands should detect any ambari-server hotfix and fail upgrade/start from proceeding
[
https://issues.apache.org/jira/browse/AMBARI-15348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194427#comment-15194427
]
Hudson commented on AMBARI-15348:
-
SUCCESS: Integrated in Ambari-branch-2.2 #509 (See
[https://builds.apache.org/job/Ambari-branch-2.2/509/])
Revert "AMBARI-15348 Ambari upgrade/start commands should detect any (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0d3debf368ab606bb0520fb817f2de6f9665a78c])
* ambari-server/src/main/python/ambari_server/serverClassPath.py
* ambari-server/src/main/package/deb/control/preinst
* ambari-server/src/main/package/rpm/preinstall.sh
* ambari-server/src/test/python/TestServerClassPath.py
* ambari-server/pom.xml
> Ambari upgrade/start commands should detect any ambari-server hotfix and fail
> upgrade/start from proceeding
> ---
>
> Key: AMBARI-15348
> URL: https://issues.apache.org/jira/browse/AMBARI-15348
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15348-trunk.patch
>
>
> If user copied hotfixed ambari-server.jar to /usr/lib/ambari-server and
> didn't remove the hotfix, the upgrade will fails with error:
> {code}
> Internal Exception: Exception [EclipseLink-7250] (Eclipse Persistence
> Services - 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.ValidationException
> Exception Description: [class
> org.apache.ambari.server.orm.entities.HostEntity] uses a non-entity [class
> org.apache.ambari.server.orm.entities.HostVersionEntity] as target entity in
> the relationship attribute [field hostVersionEntities].
> at
> org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.createPredeployFailedPersistenceException(EntityManagerSetupImpl.java:1954)
> at
> org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:1945)
> at
> org.eclipse.persistence.internal.jpa.deployment.JPAInitializer.callPredeploy(JPAInitializer.java:98)
> at
> org.eclipse.persistence.jpa.PersistenceProvider.createEntityManagerFactoryImpl(PersistenceProvider.java:96)
> ... 15 more
> Caused by: Exception [EclipseLink-28018] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.EntityManagerSetupException
> Exception Description: Predeployment of PersistenceUnit [ambari-server]
> failed.
> {code}
> As a workaround, user needs to restore all the database and configuration,
> remove all the hotfix and run "ambari-server upgrade" again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15075) Edit Widget Wizard still open even though it was closed/saved in the previous step
[ https://issues.apache.org/jira/browse/AMBARI-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194419#comment-15194419 ] Jaimin D Jetly commented on AMBARI-15075: - Attached an additive patch [^AMBARI-15075.3.patch] on top of original fix. Although this issues happens rarely with same STR and is hard to verify manually, I tested it multiple times and wasn't able to reproduce. Verified that all ambari-web unit tests passes with the patch: 24569 tests complete (25 seconds) 145 tests pending > Edit Widget Wizard still open even though it was closed/saved in the previous > step > -- > > Key: AMBARI-15075 > URL: https://issues.apache.org/jira/browse/AMBARI-15075 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15075.2.patch, AMBARI-15075.3.patch, > AMBARI-15075.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15075) Edit Widget Wizard still open even though it was closed/saved in the previous step
[ https://issues.apache.org/jira/browse/AMBARI-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-15075: Attachment: AMBARI-15075.3.patch > Edit Widget Wizard still open even though it was closed/saved in the previous > step > -- > > Key: AMBARI-15075 > URL: https://issues.apache.org/jira/browse/AMBARI-15075 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15075.2.patch, AMBARI-15075.3.patch, > AMBARI-15075.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-15075) Edit Widget Wizard still open even though it was closed/saved in the previous step
[ https://issues.apache.org/jira/browse/AMBARI-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly reopened AMBARI-15075: - Reopening the issue as this issue was noted once. > Edit Widget Wizard still open even though it was closed/saved in the previous > step > -- > > Key: AMBARI-15075 > URL: https://issues.apache.org/jira/browse/AMBARI-15075 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15075.2.patch, AMBARI-15075.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-584) yum process becomes after long time install
[ https://issues.apache.org/jira/browse/AMBARI-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang resolved AMBARI-584. - Resolution: Invalid > yum process becomes after long time install > - > > Key: AMBARI-584 > URL: https://issues.apache.org/jira/browse/AMBARI-584 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 0.1.0 > Environment: CentOS 5.7 >Reporter: Zhiyuan Yang > Original Estimate: 3h > Remaining Estimate: 3h > > When deploying Hadoop without local repo, ambari installs all software using > only one yum command with a slow network. After long time waiting, this yum > process become defunct and then deployment fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15348) Ambari upgrade/start commands should detect any ambari-server hotfix and fail upgrade/start from proceeding
[
https://issues.apache.org/jira/browse/AMBARI-15348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194353#comment-15194353
]
Hudson commented on AMBARI-15348:
-
FAILURE: Integrated in Ambari-trunk-Commit #4492 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4492/])
Revert "AMBARI-15348 Ambari upgrade/start commands should detect any (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b99085b7c1beb78896e98f0d39f94eafb9c26afb])
* ambari-server/pom.xml
* ambari-server/src/main/package/rpm/preinstall.sh
* ambari-server/src/test/python/TestServerClassPath.py
* ambari-server/src/main/python/ambari_server/serverClassPath.py
* ambari-server/src/main/package/deb/control/preinst
> Ambari upgrade/start commands should detect any ambari-server hotfix and fail
> upgrade/start from proceeding
> ---
>
> Key: AMBARI-15348
> URL: https://issues.apache.org/jira/browse/AMBARI-15348
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15348-trunk.patch
>
>
> If user copied hotfixed ambari-server.jar to /usr/lib/ambari-server and
> didn't remove the hotfix, the upgrade will fails with error:
> {code}
> Internal Exception: Exception [EclipseLink-7250] (Eclipse Persistence
> Services - 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.ValidationException
> Exception Description: [class
> org.apache.ambari.server.orm.entities.HostEntity] uses a non-entity [class
> org.apache.ambari.server.orm.entities.HostVersionEntity] as target entity in
> the relationship attribute [field hostVersionEntities].
> at
> org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.createPredeployFailedPersistenceException(EntityManagerSetupImpl.java:1954)
> at
> org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:1945)
> at
> org.eclipse.persistence.internal.jpa.deployment.JPAInitializer.callPredeploy(JPAInitializer.java:98)
> at
> org.eclipse.persistence.jpa.PersistenceProvider.createEntityManagerFactoryImpl(PersistenceProvider.java:96)
> ... 15 more
> Caused by: Exception [EclipseLink-28018] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.EntityManagerSetupException
> Exception Description: Predeployment of PersistenceUnit [ambari-server]
> failed.
> {code}
> As a workaround, user needs to restore all the database and configuration,
> remove all the hotfix and run "ambari-server upgrade" again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15414) Version Register/manage: UX edits #1
[ https://issues.apache.org/jira/browse/AMBARI-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194347#comment-15194347 ] Xi Wang commented on AMBARI-15414: -- 24569 tests complete (28 seconds) 145 tests pending > Version Register/manage: UX edits #1 > > > Key: AMBARI-15414 > URL: https://issues.apache.org/jira/browse/AMBARI-15414 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15414.patch, Ambari-15414-1.png, > Ambari-15414-2.png, Ambari-15414-3.png, Ambari-15414-4.png, Ambari-15414-5.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15414) Version Register/manage: UX edits #1
[ https://issues.apache.org/jira/browse/AMBARI-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-15414: - Status: Patch Available (was: Open) > Version Register/manage: UX edits #1 > > > Key: AMBARI-15414 > URL: https://issues.apache.org/jira/browse/AMBARI-15414 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15414.patch, Ambari-15414-1.png, > Ambari-15414-2.png, Ambari-15414-3.png, Ambari-15414-4.png, Ambari-15414-5.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15414) Version Register/manage: UX edits #1
[ https://issues.apache.org/jira/browse/AMBARI-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-15414: - Attachment: AMBARI-15414.patch > Version Register/manage: UX edits #1 > > > Key: AMBARI-15414 > URL: https://issues.apache.org/jira/browse/AMBARI-15414 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15414.patch, Ambari-15414-1.png, > Ambari-15414-2.png, Ambari-15414-3.png, Ambari-15414-4.png, Ambari-15414-5.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15414) Version Register/manage: UX edits #1
[ https://issues.apache.org/jira/browse/AMBARI-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-15414: - Attachment: Ambari-15414-5.png Ambari-15414-4.png Ambari-15414-3.png Ambari-15414-2.png Ambari-15414-1.png > Version Register/manage: UX edits #1 > > > Key: AMBARI-15414 > URL: https://issues.apache.org/jira/browse/AMBARI-15414 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: Ambari-15414-1.png, Ambari-15414-2.png, > Ambari-15414-3.png, Ambari-15414-4.png, Ambari-15414-5.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15414) Version Register/manage: UX edits #1
Xi Wang created AMBARI-15414: Summary: Version Register/manage: UX edits #1 Key: AMBARI-15414 URL: https://issues.apache.org/jira/browse/AMBARI-15414 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Xi Wang Assignee: Xi Wang Priority: Critical Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-13364) Parameterize stack information used by common services
[
https://issues.apache.org/jira/browse/AMBARI-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194312#comment-15194312
]
Juanjo Marron commented on AMBARI-13364:
Attached patch (AMBARI-14435.patch) implementing the new parametrization
approach for Zookeeper:
https://issues.apache.org/jira/browse/AMBARI-14435
[~jluniya] [~afernandez] Per our last conversation, this patch removes the
hardcoded stack versions in ZK common-services code (centralized version and
parameterized stack configurations will be faced in other JIRAS)
stack_features is now a property in .json format in
configuration/cluster-env.xml for each stack version.
With the structure:
{
"stack_features": [
{ "name": "feature1", "description" : "Feature1 support", "min_version" :
"Y.Y.Y.Y" , "max_version" : "X.X.X.X"}
,
...
]
}
where min_version/max_version are optional constraints.
New resource_management/libraries/functions/stack_fetaures.py has been
introduced to parse the json file and called from service code to check if the
stack supports the required feature.
Zookeeper fresh installation has been tested using HDP stack 2.3 and
AMBARI-13364 branch code.
Please, can you review when you have the chance and validate if it is the
expected behavior?
Would it fit in the other set of changes you are planning to do?
Thanks
> Parameterize stack information used by common services
> ---
>
> Key: AMBARI-13364
> URL: https://issues.apache.org/jira/browse/AMBARI-13364
> Project: Ambari
> Issue Type: Story
> Components: ambari-server
>Reporter: Tuong Truong
>Assignee: Juanjo Marron
> Attachments: AMBARI-13364 Parameterize stack information used by
> common services.pdf, AMBARI-13364.patch, stack_featurizer.patch
>
>
> This feature will add a basic framework to remove hardcoded stack information
> out of the common services and use parameter to get access to stack
> information. Currently, common services hardcodes much information specific
> to Hortonworks' HDP stack including name (HDP), specific versions (2.0, 2.1,
> 2.2), and install location. This feature will propose a way of
> configuration these information and parameterize them into the services for
> reference as require.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-14435) Parameterize distro-specific stack information for ZOOKEEPER
[ https://issues.apache.org/jira/browse/AMBARI-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-14435: --- Attachment: AMBARI-14435.patch > Parameterize distro-specific stack information for ZOOKEEPER > > > Key: AMBARI-14435 > URL: https://issues.apache.org/jira/browse/AMBARI-14435 > Project: Ambari > Issue Type: Technical task > Components: ambari-server >Affects Versions: 2.2.0, 2.2.1 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 2.4.0 > > Attachments: > 0001-AMBARI-14435-Parameterize-distro-specific-stack-info.patch, > AMBARI-14435.patch > > > Apply the prototype detailed on AMBARI-13364 to ZOOKEEPER service. > Tokens such as: current version, upgrade version, stack name, install > path..., will be parameterized and distro-agnostic at service definition > level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15230) Auto-start services: Move default values in ambari.properties to cluster-env.xml
[ https://issues.apache.org/jira/browse/AMBARI-15230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15230: --- Status: Patch Available (was: In Progress) > Auto-start services: Move default values in ambari.properties to > cluster-env.xml > > > Key: AMBARI-15230 > URL: https://issues.apache.org/jira/browse/AMBARI-15230 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: rb44352.patch > > > Verify recovery.* default values in ambari.properties. > Move the recover.* values to cluster-env.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15230) Auto-start services: Move default values in ambari.properties to cluster-env.xml
[ https://issues.apache.org/jira/browse/AMBARI-15230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15230: --- Status: In Progress (was: Patch Available) > Auto-start services: Move default values in ambari.properties to > cluster-env.xml > > > Key: AMBARI-15230 > URL: https://issues.apache.org/jira/browse/AMBARI-15230 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: rb44352.patch > > > Verify recovery.* default values in ambari.properties. > Move the recover.* values to cluster-env.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14435) Parameterize distro-specific stack information for ZOOKEEPER
[ https://issues.apache.org/jira/browse/AMBARI-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-14435: --- Attachment: (was: AMBARI-14435.patch) > Parameterize distro-specific stack information for ZOOKEEPER > > > Key: AMBARI-14435 > URL: https://issues.apache.org/jira/browse/AMBARI-14435 > Project: Ambari > Issue Type: Technical task > Components: ambari-server >Affects Versions: 2.2.0, 2.2.1 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 2.4.0 > > Attachments: > 0001-AMBARI-14435-Parameterize-distro-specific-stack-info.patch > > > Apply the prototype detailed on AMBARI-13364 to ZOOKEEPER service. > Tokens such as: current version, upgrade version, stack name, install > path..., will be parameterized and distro-agnostic at service definition > level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15230) Auto-start services: Move default values in ambari.properties to cluster-env.xml
[ https://issues.apache.org/jira/browse/AMBARI-15230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15230: --- Status: Patch Available (was: Open) > Auto-start services: Move default values in ambari.properties to > cluster-env.xml > > > Key: AMBARI-15230 > URL: https://issues.apache.org/jira/browse/AMBARI-15230 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: rb44352.patch > > > Verify recovery.* default values in ambari.properties. > Move the recover.* values to cluster-env.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15230) Auto-start services: Move default values in ambari.properties to cluster-env.xml
[ https://issues.apache.org/jira/browse/AMBARI-15230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15230: --- Attachment: rb44352.patch Patch > Auto-start services: Move default values in ambari.properties to > cluster-env.xml > > > Key: AMBARI-15230 > URL: https://issues.apache.org/jira/browse/AMBARI-15230 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: rb44352.patch > > > Verify recovery.* default values in ambari.properties. > Move the recover.* values to cluster-env.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15230) Auto-start services: Move default values in ambari.properties to cluster-env.xml
[ https://issues.apache.org/jira/browse/AMBARI-15230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15230: --- Attachment: (was: rb44352.patch) > Auto-start services: Move default values in ambari.properties to > cluster-env.xml > > > Key: AMBARI-15230 > URL: https://issues.apache.org/jira/browse/AMBARI-15230 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > > Verify recovery.* default values in ambari.properties. > Move the recover.* values to cluster-env.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15230) Auto-start services: Move default values in ambari.properties to cluster-env.xml
[ https://issues.apache.org/jira/browse/AMBARI-15230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15230: --- Status: Open (was: Patch Available) > Auto-start services: Move default values in ambari.properties to > cluster-env.xml > > > Key: AMBARI-15230 > URL: https://issues.apache.org/jira/browse/AMBARI-15230 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: rb44352.patch > > > Verify recovery.* default values in ambari.properties. > Move the recover.* values to cluster-env.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15413) Metrics Grafana Failed to start
[ https://issues.apache.org/jira/browse/AMBARI-15413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15413: --- Attachment: AMBARI-15413.patch > Metrics Grafana Failed to start > --- > > Key: AMBARI-15413 > URL: https://issues.apache.org/jira/browse/AMBARI-15413 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15413.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15413) Metrics Grafana Failed to start
Aravindan Vijayan created AMBARI-15413: -- Summary: Metrics Grafana Failed to start Key: AMBARI-15413 URL: https://issues.apache.org/jira/browse/AMBARI-15413 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.2.2 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Priority: Critical Fix For: 2.2.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15412) Improve error logging for install errors during blueprint deployments
[ https://issues.apache.org/jira/browse/AMBARI-15412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-15412: --- Status: Patch Available (was: In Progress) > Improve error logging for install errors during blueprint deployments > - > > Key: AMBARI-15412 > URL: https://issues.apache.org/jira/browse/AMBARI-15412 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Attachments: AMBARI-15412.patch, AMBARI-15412_output.png > > > Improve error logging for install errors during blueprint deployment. > Currently a severe error during install of a service component gets logged as > a WARNing. > E.g.: > 09 Mar 2016 12:11:45,881 WARN [qtp-ambari-agent-146] HeartBeatHandler:603 - > Operation failed - may be retried. Service component host: KAFKA_BROKER, > host: hdtest159.svl.ibm.com Action id12-0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15412) Improve error logging for install errors during blueprint deployments
[ https://issues.apache.org/jira/browse/AMBARI-15412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-15412: --- Attachment: AMBARI-15412.patch Modified logging level from warning to error. > Improve error logging for install errors during blueprint deployments > - > > Key: AMBARI-15412 > URL: https://issues.apache.org/jira/browse/AMBARI-15412 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Attachments: AMBARI-15412.patch, AMBARI-15412_output.png > > > Improve error logging for install errors during blueprint deployment. > Currently a severe error during install of a service component gets logged as > a WARNing. > E.g.: > 09 Mar 2016 12:11:45,881 WARN [qtp-ambari-agent-146] HeartBeatHandler:603 - > Operation failed - may be retried. Service component host: KAFKA_BROKER, > host: hdtest159.svl.ibm.com Action id12-0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15404) File resource timed out
[
https://issues.apache.org/jira/browse/AMBARI-15404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194194#comment-15194194
]
Andrew Onischuk commented on AMBARI-15404:
--
The failure doesn't look like connected with patch. It's in java tests, while
patch only changes python part.
> File resource timed out
> ---
>
> Key: AMBARI-15404
> URL: https://issues.apache.org/jira/browse/AMBARI-15404
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15404.patch
>
>
> Python script has been killed due to timeout after waiting 1200 secs
> Happens when filename contains //
>
>
> File['//usr/jdk64/jdk1.7.0_67/bin/java'] {'mode': 0755, 'cd_access': 'a'}
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15411) RBAC: Name filter does not work for user with no role
[ https://issues.apache.org/jira/browse/AMBARI-15411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-15411: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > RBAC: Name filter does not work for user with no role > - > > Key: AMBARI-15411 > URL: https://issues.apache.org/jira/browse/AMBARI-15411 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-15411.patch > > > After type in characters in "Name" filter, matching matching users with > role=None is not showing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15401) AMS service failed to start
[ https://issues.apache.org/jira/browse/AMBARI-15401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-15401: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.2 > AMS service failed to start > --- > > Key: AMBARI-15401 > URL: https://issues.apache.org/jira/browse/AMBARI-15401 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics, stacks >Affects Versions: 2.2.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15401-trunk_1.patch > > > STR: > 1) Setup and configure LDAPS > 2) Install Ambari and deploy cluster > Results ams service check fails, all the following start commands aborted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15412) Improve error logging for install errors during blueprint deployments
[ https://issues.apache.org/jira/browse/AMBARI-15412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-15412: --- Attachment: AMBARI-15412_output.png > Improve error logging for install errors during blueprint deployments > - > > Key: AMBARI-15412 > URL: https://issues.apache.org/jira/browse/AMBARI-15412 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Attachments: AMBARI-15412_output.png > > > Improve error logging for install errors during blueprint deployment. > Currently a severe error during install of a service component gets logged as > a WARNing. > E.g.: > 09 Mar 2016 12:11:45,881 WARN [qtp-ambari-agent-146] HeartBeatHandler:603 - > Operation failed - may be retried. Service component host: KAFKA_BROKER, > host: hdtest159.svl.ibm.com Action id12-0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15412) Improve error logging for install errors during blueprint deployments
[ https://issues.apache.org/jira/browse/AMBARI-15412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-15412: --- Description: Improve error logging for install errors during blueprint deployment. Currently a severe error during install of a service component gets logged as a WARNing. E.g.: 09 Mar 2016 12:11:45,881 WARN [qtp-ambari-agent-146] HeartBeatHandler:603 - Operation failed - may be retried. Service component host: KAFKA_BROKER, host: hdtest159.svl.ibm.com Action id12-0 > Improve error logging for install errors during blueprint deployments > - > > Key: AMBARI-15412 > URL: https://issues.apache.org/jira/browse/AMBARI-15412 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Amruta Borkar >Assignee: Amruta Borkar > > Improve error logging for install errors during blueprint deployment. > Currently a severe error during install of a service component gets logged as > a WARNing. > E.g.: > 09 Mar 2016 12:11:45,881 WARN [qtp-ambari-agent-146] HeartBeatHandler:603 - > Operation failed - may be retried. Service component host: KAFKA_BROKER, > host: hdtest159.svl.ibm.com Action id12-0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15401) AMS service failed to start
[
https://issues.apache.org/jira/browse/AMBARI-15401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194166#comment-15194166
]
Hadoop QA commented on AMBARI-15401:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12793316/AMBARI-15401-trunk_1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5857//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5857//console
This message is automatically generated.
> AMS service failed to start
> ---
>
> Key: AMBARI-15401
> URL: https://issues.apache.org/jira/browse/AMBARI-15401
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, stacks
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15401-trunk_1.patch
>
>
> STR:
> 1) Setup and configure LDAPS
> 2) Install Ambari and deploy cluster
> Results ams service check fails, all the following start commands aborted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15412) Improve error logging for install errors during blueprint deployments
Amruta Borkar created AMBARI-15412: -- Summary: Improve error logging for install errors during blueprint deployments Key: AMBARI-15412 URL: https://issues.apache.org/jira/browse/AMBARI-15412 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.2.0 Reporter: Amruta Borkar Assignee: Amruta Borkar -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15411) RBAC: Name filter does not work for user with no role
[ https://issues.apache.org/jira/browse/AMBARI-15411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-15411: -- Status: Patch Available (was: Open) > RBAC: Name filter does not work for user with no role > - > > Key: AMBARI-15411 > URL: https://issues.apache.org/jira/browse/AMBARI-15411 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-15411.patch > > > After type in characters in "Name" filter, matching matching users with > role=None is not showing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15411) RBAC: Name filter does not work for user with no role
[ https://issues.apache.org/jira/browse/AMBARI-15411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-15411: -- Attachment: AMBARI-15411.patch > RBAC: Name filter does not work for user with no role > - > > Key: AMBARI-15411 > URL: https://issues.apache.org/jira/browse/AMBARI-15411 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-15411.patch > > > After type in characters in "Name" filter, matching matching users with > role=None is not showing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15397) Rolling Upgrade: incorrect display_status of upgrade groups
[
https://issues.apache.org/jira/browse/AMBARI-15397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194127#comment-15194127
]
Hudson commented on AMBARI-15397:
-
SUCCESS: Integrated in Ambari-branch-2.2 #508 (See
[https://builds.apache.org/job/Ambari-branch-2.2/508/])
AMBARI-15397 Rolling Upgrade: incorrect display_status of upgrade groups (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7757499c05768c533601e8199114c276912ebe3f])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/CalculatedStatus.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/CalculatedStatusTest.java
> Rolling Upgrade: incorrect display_status of upgrade groups
> ---
>
> Key: AMBARI-15397
> URL: https://issues.apache.org/jira/browse/AMBARI-15397
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15397.patch
>
>
> Upgrade display_status does not correspond to status of its upgrade items.
> Upgrade group must have display_status IN_PROGRESS instead of COMPLETE:
> {code:java}
> {
> "UpgradeGroup" : {
> "completed_task_count" : 1,
> "display_status" : "COMPLETED",
> "group_id" : 53,
> "in_progress_task_count" : 2,
> "name" : "ZOOKEEPER",
> "progress_percent" : 45.0,
> "request_id" : 24,
> "status" : "IN_PROGRESS",
> "title" : "ZooKeeper",
> "total_task_count" : 3
> },
> "upgrade_items" : [
> {
> "UpgradeItem" : {
> "context" : "Restarting ZooKeeper Server on
> c6401.ambari.apache.org (Batch 1 of 3)",
> "display_status" : "COMPLETED",
> "group_id" : 53,
> "progress_percent" : 100.0,
> "request_id" : 24,
> "skippable" : true,
> "stage_id" : 20,
> "status" : "COMPLETED",
> "text" : "Restarting ZooKeeper Server on c6401.ambari.apache.org
> (Batch 1 of 3)"
> }
> },
> {
> "UpgradeItem" : {
> "context" : "Restarting ZooKeeper Server on
> c6402.ambari.apache.org (Batch 2 of 3)",
> "display_status" : "IN_PROGRESS",
> "group_id" : 53,
> "progress_percent" : 35.0,
> "request_id" : 24,
> "skippable" : true,
> "stage_id" : 21,
> "status" : "IN_PROGRESS",
> "text" : "Restarting ZooKeeper Server on c6402.ambari.apache.org
> (Batch 2 of 3)"
> }
> },
> {
> "UpgradeItem" : {
> "context" : "Restarting ZooKeeper Server on
> c6403.ambari.apache.org (Batch 3 of 3)",
> "display_status" : "PENDING",
> "group_id" : 53,
> "progress_percent" : 0.0,
> "request_id" : 24,
> "skippable" : true,
> "stage_id" : 22,
> "status" : "PENDING",
> "text" : "Restarting ZooKeeper Server on c6403.ambari.apache.org
> (Batch 3 of 3)"
> }
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15404) File resource timed out
[
https://issues.apache.org/jira/browse/AMBARI-15404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194129#comment-15194129
]
Hudson commented on AMBARI-15404:
-
SUCCESS: Integrated in Ambari-branch-2.2 #508 (See
[https://builds.apache.org/job/Ambari-branch-2.2/508/])
AMBARI-15404. File resource timed out (aonishuk) (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b6d0f773f3a44825543a86a31d9299c6fe29fa89])
* ambari-common/src/main/python/resource_management/core/providers/system.py
> File resource timed out
> ---
>
> Key: AMBARI-15404
> URL: https://issues.apache.org/jira/browse/AMBARI-15404
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15404.patch
>
>
> Python script has been killed due to timeout after waiting 1200 secs
> Happens when filename contains //
>
>
> File['//usr/jdk64/jdk1.7.0_67/bin/java'] {'mode': 0755, 'cd_access': 'a'}
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15357) Rename Service Action 'HAWQ Check' to 'HAWQ Config Check'
[ https://issues.apache.org/jira/browse/AMBARI-15357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194125#comment-15194125 ] Hudson commented on AMBARI-15357: - SUCCESS: Integrated in Ambari-branch-2.2 #508 (See [https://builds.apache.org/job/Ambari-branch-2.2/508/]) AMBARI-15357: Rename Service Action 'HAWQ Check' to 'HAWQ Config Check' (bchaudhary: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f7594bdc097c8d6d55736a73f177f9f37770b83b]) * ambari-web/app/views/main/host/hosts_table_menu_view.js * ambari-web/app/messages.js > Rename Service Action 'HAWQ Check' to 'HAWQ Config Check' > - > > Key: AMBARI-15357 > URL: https://issues.apache.org/jira/browse/AMBARI-15357 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Goutam Tadi >Assignee: Goutam Tadi >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15357-branch-2_2.patch, AMBARI-15357-trunk.patch, > AMBARI-15357-v1.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15400) Loading monitoring page is stuck after cluster deploy (java.lang.StackOverflowError)
[
https://issues.apache.org/jira/browse/AMBARI-15400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194124#comment-15194124
]
Hudson commented on AMBARI-15400:
-
SUCCESS: Integrated in Ambari-branch-2.2 #508 (See
[https://builds.apache.org/job/Ambari-branch-2.2/508/])
AMBARI-15400. Loading monitoring page is stuck after cluster deploy
(mpapyrkovskyy:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dd1011cba7f7dc2684c920c003b70c9179c07cd8])
*
ambari-server/src/main/java/org/apache/ambari/server/state/stack/MetricDefinition.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackArtifactResourceProvider.java
> Loading monitoring page is stuck after cluster deploy
> (java.lang.StackOverflowError)
>
>
> Key: AMBARI-15400
> URL: https://issues.apache.org/jira/browse/AMBARI-15400
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-15400.patch
>
>
> Sometimes UI loading stuck because backend response with HTTP code 500.
> StackOverflowError is present is server logs:
> {code:title=ambari-server.log}
> 13 Mar 2016 04:47:18,462 WARN [qtp-ambari-client-22] ServletHandler:563 -
> /api/v1/stacks/HDP/versions/2.4/services/HDFS
> java.lang.StackOverflowError
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15398) Disable HDP 2.5 stack in Ambari 2.2.2
[ https://issues.apache.org/jira/browse/AMBARI-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194126#comment-15194126 ] Hudson commented on AMBARI-15398: - SUCCESS: Integrated in Ambari-branch-2.2 #508 (See [https://builds.apache.org/job/Ambari-branch-2.2/508/]) AMBARI-15398 Disable HDP 2.5 stack in Ambari 2.2.2 (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=254e6348567ea05ae6534401ed1431bfa1595675]) * ambari-server/src/main/resources/stacks/HDP/2.5/metainfo.xml > Disable HDP 2.5 stack in Ambari 2.2.2 > - > > Key: AMBARI-15398 > URL: https://issues.apache.org/jira/browse/AMBARI-15398 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen > Fix For: 2.2.2 > > Attachments: AMBARI-15398.patch > > > Disable the HDP 2.5 stack option from Ambari in Ambari 2.2.2 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15311) Update descriptions for HAWQ and PXF configurations
[ https://issues.apache.org/jira/browse/AMBARI-15311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194128#comment-15194128 ] Hudson commented on AMBARI-15311: - SUCCESS: Integrated in Ambari-branch-2.2 #508 (See [https://builds.apache.org/job/Ambari-branch-2.2/508/]) AMBARI-15311: Update descriptions for HAWQ and PXF configurations (bchaudhary: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b6e5bc0da6331942ff7af931ccc876fca1d66a2e]) * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hdfs-client.xml * ambari-server/src/main/resources/common-services/PXF/3.0.0/configuration/pxf-site.xml * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-check-env.xml * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-env.xml * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-limits-env.xml * ambari-server/src/main/resources/common-services/PXF/3.0.0/configuration/pxf-profiles.xml * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-sysctl-env.xml * ambari-server/src/main/resources/common-services/PXF/3.0.0/configuration/pxf-public-classpath.xml * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-site.xml * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/yarn-client.xml > Update descriptions for HAWQ and PXF configurations > --- > > Key: AMBARI-15311 > URL: https://issues.apache.org/jira/browse/AMBARI-15311 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Reporter: Matt >Assignee: Goutam Tadi >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15311-branch-2_2.patch, AMBARI-15311-trunk.patch, > AMBARI-15311.v1-trunk.patch > > > Update the descriptions for HAWQ and PXF configurations so that they are more > readable and convey the right message to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-6432) FreeIPA Support in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194122#comment-15194122 ] Bolke de Bruin commented on AMBARI-6432: [~rlevas] Fixed typo in the VariableReplacementHelperTest (and tested locally, had some trouble doing this before). Other failures seem unrelated to me. > FreeIPA Support in Ambari > - > > Key: AMBARI-6432 > URL: https://issues.apache.org/jira/browse/AMBARI-6432 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: jay vyas >Assignee: Bolke de Bruin > Fix For: 2.4.0 > > Attachments: AMBARI-6432-FreeIPA.patch, AMBARI-6432.patch, > AMBARI-6432.patch, AMBARI-6432.trunk.v1.patch, AMBARI-6432.trunk.v2.patch, > AMBARI-6432.trunk.v3.patch, AMBARI-6432.trunk.v4.patch, > AMBARI-6432.trunk.v5.patch, AMBARI-6432.trunk.v5.patch, > AMBARI-6432.trunk.v6.patch, AMBARI-6432.trunk.v7.patch, > AMBARI-6432.trunk.v8.patch, ipa-patch-v0.5.patch > > > FreeIPA Is a powerful tool for unifying identity, kerberos credentials, > across a cluster. > A great value add for ambari would be to provide support for using FreeIPA to > kerberize services. This would allow for > 1) better HCFS interoperability, because first class GID/UID is critical for > certain file systems (GlusterFS, Lustre, and any other file system which uses > kernel / FUSE apis for determining identity) > 2) better enterprise interoperability. Because of the fact that FreeIPA > makes it easy to interop with different identity solutions (like active > directory), it would make ambari easier to adopt for various enterprises. > 3) broadens ambaris scope. Now ambari could also allow people to setup the > users of their clusters, and at least some of the security features of their > clusters, all from one interface (no more manual handling of TGTs and such - > it could all be done quite easily via the ambari UI which could make calls to > underlying FreeIPA clients). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-6432) FreeIPA Support in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated AMBARI-6432: --- Attachment: AMBARI-6432.trunk.v8.patch * Fixes test (VariableReplacementHelperTest) * Add some javadoc > FreeIPA Support in Ambari > - > > Key: AMBARI-6432 > URL: https://issues.apache.org/jira/browse/AMBARI-6432 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: jay vyas >Assignee: Bolke de Bruin > Fix For: 2.4.0 > > Attachments: AMBARI-6432-FreeIPA.patch, AMBARI-6432.patch, > AMBARI-6432.patch, AMBARI-6432.trunk.v1.patch, AMBARI-6432.trunk.v2.patch, > AMBARI-6432.trunk.v3.patch, AMBARI-6432.trunk.v4.patch, > AMBARI-6432.trunk.v5.patch, AMBARI-6432.trunk.v5.patch, > AMBARI-6432.trunk.v6.patch, AMBARI-6432.trunk.v7.patch, > AMBARI-6432.trunk.v8.patch, ipa-patch-v0.5.patch > > > FreeIPA Is a powerful tool for unifying identity, kerberos credentials, > across a cluster. > A great value add for ambari would be to provide support for using FreeIPA to > kerberize services. This would allow for > 1) better HCFS interoperability, because first class GID/UID is critical for > certain file systems (GlusterFS, Lustre, and any other file system which uses > kernel / FUSE apis for determining identity) > 2) better enterprise interoperability. Because of the fact that FreeIPA > makes it easy to interop with different identity solutions (like active > directory), it would make ambari easier to adopt for various enterprises. > 3) broadens ambaris scope. Now ambari could also allow people to setup the > users of their clusters, and at least some of the security features of their > clusters, all from one interface (no more manual handling of TGTs and such - > it could all be done quite easily via the ambari UI which could make calls to > underlying FreeIPA clients). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15411) RBAC: Name filter does not work for user with no role
Richard Zang created AMBARI-15411: - Summary: RBAC: Name filter does not work for user with no role Key: AMBARI-15411 URL: https://issues.apache.org/jira/browse/AMBARI-15411 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 2.4.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.4.0 After type in characters in "Name" filter, matching matching users with role=None is not showing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15397) Rolling Upgrade: incorrect display_status of upgrade groups
[
https://issues.apache.org/jira/browse/AMBARI-15397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194111#comment-15194111
]
Hudson commented on AMBARI-15397:
-
FAILURE: Integrated in Ambari-trunk-Commit #4491 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4491/])
AMBARI-15397 Rolling Upgrade: incorrect display_status of upgrade groups (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b9d06931abf989eb8c6715ff9a4cc4c3f4f25ece])
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/CalculatedStatusTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/CalculatedStatus.java
> Rolling Upgrade: incorrect display_status of upgrade groups
> ---
>
> Key: AMBARI-15397
> URL: https://issues.apache.org/jira/browse/AMBARI-15397
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15397.patch
>
>
> Upgrade display_status does not correspond to status of its upgrade items.
> Upgrade group must have display_status IN_PROGRESS instead of COMPLETE:
> {code:java}
> {
> "UpgradeGroup" : {
> "completed_task_count" : 1,
> "display_status" : "COMPLETED",
> "group_id" : 53,
> "in_progress_task_count" : 2,
> "name" : "ZOOKEEPER",
> "progress_percent" : 45.0,
> "request_id" : 24,
> "status" : "IN_PROGRESS",
> "title" : "ZooKeeper",
> "total_task_count" : 3
> },
> "upgrade_items" : [
> {
> "UpgradeItem" : {
> "context" : "Restarting ZooKeeper Server on
> c6401.ambari.apache.org (Batch 1 of 3)",
> "display_status" : "COMPLETED",
> "group_id" : 53,
> "progress_percent" : 100.0,
> "request_id" : 24,
> "skippable" : true,
> "stage_id" : 20,
> "status" : "COMPLETED",
> "text" : "Restarting ZooKeeper Server on c6401.ambari.apache.org
> (Batch 1 of 3)"
> }
> },
> {
> "UpgradeItem" : {
> "context" : "Restarting ZooKeeper Server on
> c6402.ambari.apache.org (Batch 2 of 3)",
> "display_status" : "IN_PROGRESS",
> "group_id" : 53,
> "progress_percent" : 35.0,
> "request_id" : 24,
> "skippable" : true,
> "stage_id" : 21,
> "status" : "IN_PROGRESS",
> "text" : "Restarting ZooKeeper Server on c6402.ambari.apache.org
> (Batch 2 of 3)"
> }
> },
> {
> "UpgradeItem" : {
> "context" : "Restarting ZooKeeper Server on
> c6403.ambari.apache.org (Batch 3 of 3)",
> "display_status" : "PENDING",
> "group_id" : 53,
> "progress_percent" : 0.0,
> "request_id" : 24,
> "skippable" : true,
> "stage_id" : 22,
> "status" : "PENDING",
> "text" : "Restarting ZooKeeper Server on c6403.ambari.apache.org
> (Batch 3 of 3)"
> }
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15360) (1). Support install of 'Hive Server Interactive' and related 'Tez' binaries. (2). Parameter declarations in 'params_linux' and 'status_params' related to 'Hive Serve
[ https://issues.apache.org/jira/browse/AMBARI-15360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194113#comment-15194113 ] Hudson commented on AMBARI-15360: - FAILURE: Integrated in Ambari-trunk-Commit #4491 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4491/]) Revert "AMBARI-15360. HiveInteractive. (1). Code for 'Hive Server (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2f9945fadf8f67d1ee5a7478a5284ba2e237166b]) * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * ambari-server/src/test/python/stacks/2.0.6/configs/default_no_install.json * ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py * ambari-server/src/test/python/stacks/2.1/configs/hive-metastore-upgrade.json * ambari-server/src/test/python/stacks/2.0.6/configs/default_client.json * ambari-agent/src/main/python/ambari_agent/AmbariConfig.py * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py * ambari-server/src/test/python/stacks/2.0.6/hooks/after-INSTALL/test_after_install.py * ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/metainfo.xml * ambari-server/src/test/python/stacks/2.0.6/configs/default_hive_nn_ha_2.json * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/status_params.py * ambari-server/src/test/python/stacks/2.0.6/configs/default_hive_nn_ha.json * ambari-server/src/test/python/stacks/2.0.6/configs/secured_client.json * ambari-common/src/main/python/resource_management/libraries/functions/stack_select.py * ambari-server/src/test/python/stacks/2.1/configs/default.json * ambari-server/src/test/python/stacks/2.0.6/configs/default.json * ambari-server/src/test/python/stacks/2.2/configs/hive-upgrade.json * ambari-server/src/test/python/stacks/2.0.6/configs/default_hive_non_hdfs.json * ambari-server/src/test/python/stacks/2.1/configs/secured.json * ambari-server/src/test/python/stacks/2.0.6/configs/secured.json > (1). Support install of 'Hive Server Interactive' and related 'Tez' binaries. > (2). Parameter declarations in 'params_linux' and 'status_params' related to > 'Hive Server Interactive'. > - > > Key: AMBARI-15360 > URL: https://issues.apache.org/jira/browse/AMBARI-15360 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15373) Provide composite Kerberos Descriptor via the REST API
[
https://issues.apache.org/jira/browse/AMBARI-15373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194112#comment-15194112
]
Hudson commented on AMBARI-15373:
-
FAILURE: Integrated in Ambari-trunk-Commit #4491 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4491/])
AMBARI-15373. Provide composite Kerberos Descriptor via the REST API (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cbd88027a4cfd287e6b8669c30db06231a63c2b6])
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AbstractControllerResourceProviderTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImplTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractControllerResourceProvider.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterKerberosDescriptorResourceProviderTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/ClusterService.java
*
ambari-server/src/test/java/org/apache/ambari/server/api/resources/ClusterResourceDefinitionTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
*
ambari-server/src/test/java/org/apache/ambari/server/api/services/ClusterKerberosDescriptorServiceTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterKerberosDescriptorResourceProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/ClusterKerberosDescriptorService.java
*
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ClusterResourceDefinition.java
> Provide composite Kerberos Descriptor via the REST API
> --
>
> Key: AMBARI-15373
> URL: https://issues.apache.org/jira/browse/AMBARI-15373
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos_descriptor, rest_api
> Fix For: 2.4.0
>
> Attachments: AMBARI-15373_trunk_01.patch
>
>
> Provide an entry point in the REST API to retrieve the _composite_ Kerberos
> descriptor. This includes the default Kerberos descriptor built from the
> stack definitions overlaid with the (potentially sparse) Kerberos descriptor
> stored as an artifact of the cluster.
> The entry point should be a read-only sub-resource of "clusters", and should
> only be made available if asked for explicitly due to the size of the data
> that will be returned.
> {noformat:title=Example API call}
> GET /api/v1/clusters/:cluster_name/kerberos_descriptors/COMPOSITE
> {noformat}
> Note: Kerberos Descriptors available via this interface are:
> * STACK - the default Kerberos Descriptor from the relevant stack definition
> * USER - the user-suppled updates to the stack default Kerberos Descriptor
> * COMPOSITE - the stack default Kerberos Descriptor with the user-suppled
> updates applied (this is the Kerberos Descriptor used when performing
> Kerberos-related operations)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15404) File resource timed out
[
https://issues.apache.org/jira/browse/AMBARI-15404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194114#comment-15194114
]
Hudson commented on AMBARI-15404:
-
FAILURE: Integrated in Ambari-trunk-Commit #4491 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4491/])
AMBARI-15404. File resource timed out (aonishuk) (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5bd7c2bc7db2808a1fe9d6048e72ff483a6208ef])
* ambari-common/src/main/python/resource_management/core/providers/system.py
> File resource timed out
> ---
>
> Key: AMBARI-15404
> URL: https://issues.apache.org/jira/browse/AMBARI-15404
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15404.patch
>
>
> Python script has been killed due to timeout after waiting 1200 secs
> Happens when filename contains //
>
>
> File['//usr/jdk64/jdk1.7.0_67/bin/java'] {'mode': 0755, 'cd_access': 'a'}
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15400) Loading monitoring page is stuck after cluster deploy (java.lang.StackOverflowError)
[
https://issues.apache.org/jira/browse/AMBARI-15400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194110#comment-15194110
]
Hudson commented on AMBARI-15400:
-
FAILURE: Integrated in Ambari-trunk-Commit #4491 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4491/])
AMBARI-15400. Loading monitoring page is stuck after cluster deploy
(mpapyrkovskyy:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7210c9dfb804cbe0622b4f568f29f57e311df024])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackArtifactResourceProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/stack/MetricDefinition.java
> Loading monitoring page is stuck after cluster deploy
> (java.lang.StackOverflowError)
>
>
> Key: AMBARI-15400
> URL: https://issues.apache.org/jira/browse/AMBARI-15400
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-15400.patch
>
>
> Sometimes UI loading stuck because backend response with HTTP code 500.
> StackOverflowError is present is server logs:
> {code:title=ambari-server.log}
> 13 Mar 2016 04:47:18,462 WARN [qtp-ambari-client-22] ServletHandler:563 -
> /api/v1/stacks/HDP/versions/2.4/services/HDFS
> java.lang.StackOverflowError
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
> at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
