[jira] [Updated] (AMBARI-18901) LLAP integration enhancements
[ https://issues.apache.org/jira/browse/AMBARI-18901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18901: --- Summary: LLAP integration enhancements (was: Umbrella JIRA for tracking the work done in feature branch : 'branch-feature-AMBARI-18901') > LLAP integration enhancements > - > > Key: AMBARI-18901 > URL: https://issues.apache.org/jira/browse/AMBARI-18901 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18901.patch > > > The attached patch is a merged patch for all the changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19123) Update zeppelin configuration for ambari 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-19123: - Attachment: AMBARI-19123_branch-2.5-v4.patch > Update zeppelin configuration for ambari 2.5 > > > Key: AMBARI-19123 > URL: https://issues.apache.org/jira/browse/AMBARI-19123 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-19123_branch-2.5-v1.patch, > AMBARI-19123_branch-2.5-v2.patch, AMBARI-19123_branch-2.5-v3.patch, > AMBARI-19123_branch-2.5-v4.patch > > > Update zeppelin configuration for ambari 2.5, and add more configuration > template for shiro.ini -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19157) hive_heapsize property should not auto add m
[
https://issues.apache.org/jira/browse/AMBARI-19157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737087#comment-15737087
]
Sumit Mohanty commented on AMBARI-19157:
UTs passed.
{code}
App.store.commit error: Error: Error
25565 tests complete (20 seconds)
57 tests pending
[INFO]
[INFO] --- apache-rat-plugin:0.11:check (default) @ ambari-web ---
[INFO] 51 implicit excludes (use -debug for more details).
[INFO] Exclude: .idea/**
[INFO] Exclude: package.json
[INFO] Exclude: public/**
[INFO] Exclude: public-static/**
[INFO] Exclude: app/assets/**
[INFO] Exclude: vendor/**
[INFO] Exclude: node_modules/**
[INFO] Exclude: node/**
[INFO] Exclude: npm-debug.log
[INFO] 1495 resources included (use -debug for more details)
Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
recognized.
Compiler warnings:
WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
Warning: org.apache.xerces.parsers.SAXParser: Feature
'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
Warning: org.apache.xerces.parsers.SAXParser: Property
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
Warning: org.apache.xerces.parsers.SAXParser: Property
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
recognized.
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 1495 licence.
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1:24.934s
[INFO] Finished at: Fri Dec 09 19:05:49 PST 2016
[INFO] Final Memory: 13M/335M
[INFO]
{code}
> hive_heapsize property should not auto add m
>
>
> Key: AMBARI-19157
> URL: https://issues.apache.org/jira/browse/AMBARI-19157
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web, stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.0
>
> Attachments: AMBARI-19157.patch
>
>
> ambari web auto adds 'm' to hive_heapsize property and that leads to an extra
> m in the hive-env.sh file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18901) Umbrella JIRA for tracking the work done in feature branch : 'branch-feature-AMBARI-18901'
[ https://issues.apache.org/jira/browse/AMBARI-18901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18901: --- Status: Open (was: Patch Available) > Umbrella JIRA for tracking the work done in feature branch : > 'branch-feature-AMBARI-18901' > -- > > Key: AMBARI-18901 > URL: https://issues.apache.org/jira/browse/AMBARI-18901 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18901.patch > > > The attached patch is a merged patch for all the changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18901) Umbrella JIRA for tracking the work done in feature branch : 'branch-feature-AMBARI-18901'
[ https://issues.apache.org/jira/browse/AMBARI-18901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18901: --- Status: Patch Available (was: Open) > Umbrella JIRA for tracking the work done in feature branch : > 'branch-feature-AMBARI-18901' > -- > > Key: AMBARI-18901 > URL: https://issues.apache.org/jira/browse/AMBARI-18901 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18901.patch > > > The attached patch is a merged patch for all the changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18901) Umbrella JIRA for tracking the work done in feature branch : 'branch-feature-AMBARI-18901'
[ https://issues.apache.org/jira/browse/AMBARI-18901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18901: --- Attachment: AMBARI-18901.patch > Umbrella JIRA for tracking the work done in feature branch : > 'branch-feature-AMBARI-18901' > -- > > Key: AMBARI-18901 > URL: https://issues.apache.org/jira/browse/AMBARI-18901 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18901.patch > > > The attached patch is a merged patch for all the changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18901) Umbrella JIRA for tracking the work done in feature branch : 'branch-feature-AMBARI-18901'
[ https://issues.apache.org/jira/browse/AMBARI-18901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18901: --- Description: The attached patch is a merged patch for all the changes. > Umbrella JIRA for tracking the work done in feature branch : > 'branch-feature-AMBARI-18901' > -- > > Key: AMBARI-18901 > URL: https://issues.apache.org/jira/browse/AMBARI-18901 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.5.0 > > > The attached patch is a merged patch for all the changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-14958) Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB
[ https://issues.apache.org/jira/browse/AMBARI-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reassigned AMBARI-14958: --- Assignee: Vivek Ratnavel Subramanian (was: Zhe (Joe) Wang) > Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB > - > > Key: AMBARI-14958 > URL: https://issues.apache.org/jira/browse/AMBARI-14958 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-14958.patch, AMBARI-14958.v0.patch > > > 1) Rename current notification type "SNMP" to "Custom SNMP" > 2) Create a new notification type "SNMP" that prompts for version, community, > hosts, ports > 3) When this is chosen, Ambari under-the-hood generates the SNMP traps based > on the MIB. > 4) The MIB file should be shipped with Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19117) Implement Create Alerts: PORT alert configs page (step 2)
[ https://issues.apache.org/jira/browse/AMBARI-19117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736855#comment-15736855 ] Xi Wang commented on AMBARI-19117: -- 8032 passing (3s) 2 pending > Implement Create Alerts: PORT alert configs page (step 2) > - > > Key: AMBARI-19117 > URL: https://issues.apache.org/jira/browse/AMBARI-19117 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19117.patch, AMBARI-19117.patch, > AMBARI-19117.patch, Step2-PORT-40% done.png > > > This is a FE task to implement the "Create Alerts Wizard " based on the > design attached. > This task is to create Step 2 of PORT alert. see the design for details. > Pay attention to the dependencies on selecting different options. The further > fields will determined by the current selection. > eg. Selecting HDP service (such as HDFS, YARN) or Custom service will display > totally different UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19117) Implement Create Alerts: PORT alert configs page (step 2)
[ https://issues.apache.org/jira/browse/AMBARI-19117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19117: - Attachment: AMBARI-19117.patch > Implement Create Alerts: PORT alert configs page (step 2) > - > > Key: AMBARI-19117 > URL: https://issues.apache.org/jira/browse/AMBARI-19117 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19117.patch, AMBARI-19117.patch, > AMBARI-19117.patch, Step2-PORT-40% done.png > > > This is a FE task to implement the "Create Alerts Wizard " based on the > design attached. > This task is to create Step 2 of PORT alert. see the design for details. > Pay attention to the dependencies on selecting different options. The further > fields will determined by the current selection. > eg. Selecting HDP service (such as HDFS, YARN) or Custom service will display > totally different UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19160) Add ReviewBoard config file
[
https://issues.apache.org/jira/browse/AMBARI-19160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19160:
---
Attachment: AMBARI-19160_branch-2.5.patch
> Add ReviewBoard config file
> ---
>
> Key: AMBARI-19160
> URL: https://issues.apache.org/jira/browse/AMBARI-19160
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Trivial
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19160_branch-2.5.patch, AMBARI-19160_trunk.patch
>
>
> ReviewBoard has [command-line
> tools|https://www.reviewboard.org/docs/rbtools/] for working with review
> requests. The goal of this task is to add a small [config
> file|https://www.reviewboard.org/docs/rbtools/0.7/rbt/configuration/repositories/#reviewboardrc]
> to the Ambari project, so that {{rbt}} can talk to the right RB server
> out-of-the box.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19160) Add ReviewBoard config file
[
https://issues.apache.org/jira/browse/AMBARI-19160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19160:
---
Status: Patch Available (was: Open)
> Add ReviewBoard config file
> ---
>
> Key: AMBARI-19160
> URL: https://issues.apache.org/jira/browse/AMBARI-19160
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Trivial
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19160_branch-2.5.patch, AMBARI-19160_trunk.patch
>
>
> ReviewBoard has [command-line
> tools|https://www.reviewboard.org/docs/rbtools/] for working with review
> requests. The goal of this task is to add a small [config
> file|https://www.reviewboard.org/docs/rbtools/0.7/rbt/configuration/repositories/#reviewboardrc]
> to the Ambari project, so that {{rbt}} can talk to the right RB server
> out-of-the box.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19160) Add ReviewBoard config file
[
https://issues.apache.org/jira/browse/AMBARI-19160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19160:
---
Attachment: AMBARI-19160_trunk.patch
> Add ReviewBoard config file
> ---
>
> Key: AMBARI-19160
> URL: https://issues.apache.org/jira/browse/AMBARI-19160
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Trivial
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19160_trunk.patch
>
>
> ReviewBoard has [command-line
> tools|https://www.reviewboard.org/docs/rbtools/] for working with review
> requests. The goal of this task is to add a small [config
> file|https://www.reviewboard.org/docs/rbtools/0.7/rbt/configuration/repositories/#reviewboardrc]
> to the Ambari project, so that {{rbt}} can talk to the right RB server
> out-of-the box.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19160) Add ReviewBoard config file
Doroszlai, Attila created AMBARI-19160:
--
Summary: Add ReviewBoard config file
Key: AMBARI-19160
URL: https://issues.apache.org/jira/browse/AMBARI-19160
Project: Ambari
Issue Type: Improvement
Components: ambari-server
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Priority: Trivial
Fix For: 3.0.0, 2.5.0
ReviewBoard has [command-line tools|https://www.reviewboard.org/docs/rbtools/]
for working with review requests. The goal of this task is to add a small
[config
file|https://www.reviewboard.org/docs/rbtools/0.7/rbt/configuration/repositories/#reviewboardrc]
to the Ambari project, so that {{rbt}} can talk to the right RB server
out-of-the box.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736524#comment-15736524
]
Doroszlai, Attila edited comment on AMBARI-19149 at 12/9/16 10:36 PM:
--
[~jonathan.hurley], [~ncole]:
* {{utility}} was introduced for AMBARI-14439 in non-{{org.apache.ambari}}
group. It was also surprising to me, but didn't want to change that now.
* The two separate {{dependency}} sections for {{com.puppycrawl.tools}} have
different {{type}} and {{scope}}. We need the {{test-jar}} to be able to use
{{BaseCheckTestSupport}} from the Checkstyle project. This is not distributed
with their regular {{jar}}, since it's needed only for compiling and running
custom checks (eg. {{AvoidTransactionalOnPrivateMethodsCheckTest}} in our case).
* {{$checkstyle.version}} for the {{checkstyle/test-jar}} dependency, and
{{}} for the regular {{checkstyle}} dependency are inherited from the
parent pom, ie. {{ambari-project/pom.xml}}.
* There is no need to always compile the whole root project. However, when
working with a single module (eg. {{ambari-server}}), one needs to get the
dependencies in one of two ways:
** Always make dependencies, too, with the {{-am}} Maven flag. Note that
Ambari Web, Logsearch, etc. are skipped, since those are not required for the
building the server.
** Get the dependencies from some repository. In our case this means having to
install {{utility}}, its parents, and some other Ambari projects in a local
repository once. One needs to re-install them if the dependencies themselves
are updated.
* Now I've noticed that running {{mvn checkstyle:check}} performs the default
checks instead of our custom list, because the configuration was done only for
the execution tied to the test phase, not for the plugin itself. This is being
fixed in AMBARI-19158.
{noformat:title=Always making dependencies}
$ mvn -am -pl ambari-server clean compile
...
[INFO] Reactor Build Order:
[INFO]
[INFO] Ambari Main
[INFO] Apache Ambari Project POM
[INFO] Ambari Views
[INFO] utility
[INFO] ambari-metrics
[INFO] Ambari Metrics Common
[INFO] Ambari Server
{noformat}
{noformat:title=Installing once}
$ mvn -am -pl ambari-server -DskipTests clean install
$ cd ambari-server
$ mvn -DskipTest clean test
$ mvn checkstyle:check
{noformat}
was (Author: adoroszlai):
[~jonathan.hurley], [~ncole]:
* {{utility}} was introduced for AMBARI-14439 in non-{{org.apache.ambari}}
group. It was also surprising to me, but didn't want to change that now.
* The two separate {{dependency}} sections for {{com.puppycrawl.tools}} have
different {{type}} and {{scope}}. We need the {{test-jar}} to be able to use
{{BaseCheckTestSupport}} from the Checkstyle project. This is not distributed
with their regular {{jar}}, since it's needed only for compiling and running
custom checks (eg. {{AvoidTransactionalOnPrivateMethodsCheckTest}} in our case).
* {{$checkstyle.version}} for the {{checkstyle/test-jar}} dependency, and
{{}} for the regular {{checkstyle}} dependency are inherited from the
parent pom, ie. {{ambari-project/pom.xml}}.
* There is no need to always compile the whole root project. However, when
working with a single module (eg. {{ambari-server}}), one needs to get the
dependencies in one of two ways:
* Always make dependencies, too, with the {{-am}} Maven flag. Note that
Ambari Web, Logsearch, etc. are skipped, since those are not required for the
building the server.
* Get the dependencies from some repository. In our case this means having
to install {{utility}}, its parents, and some other Ambari projects in a local
repository once. One needs to re-install them if the dependencies themselves
are updated.
* Now I've noticed that running {{mvn checkstyle:check}} performs the default
checks instead of our custom list, because the configuration was done only for
the execution tied to the test phase, not for the plugin itself. This is being
fixed in AMBARI-19158.
{noformat:title=Always making dependencies}
$ mvn -am -pl ambari-server clean compile
...
[INFO] Reactor Build Order:
[INFO]
[INFO] Ambari Main
[INFO] Apache Ambari Project POM
[INFO] Ambari Views
[INFO] utility
[INFO] ambari-metrics
[INFO] Ambari Metrics Common
[INFO] Ambari Server
{noformat}
{noformat:title=Installing once}
$ mvn -am -pl ambari-server -DskipTests clean install
$ cd ambari-server
$ mvn -DskipTest clean test
$ mvn checkstyle:check
{noformat}
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments:
[jira] [Created] (AMBARI-19159) Namenode went down after enabling NNHA
Vivek Rathod created AMBARI-19159: - Summary: Namenode went down after enabling NNHA Key: AMBARI-19159 URL: https://issues.apache.org/jira/browse/AMBARI-19159 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 After enabling NNHA, One of the Namenodes went down STR: 1) Enable NNHA with 4 Journalnodes 2) Stop All/Start all services After that one of the namenodes went down one host -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736524#comment-15736524
]
Doroszlai, Attila commented on AMBARI-19149:
[~jonathan.hurley], [~ncole]:
* {{utility}} was introduced for AMBARI-14439 in non-{{org.apache.ambari}}
group. It was also surprising to me, but didn't want to change that now.
* The two separate {{dependency}} sections for {{com.puppycrawl.tools}} have
different {{type}} and {{scope}}. We need the {{test-jar}} to be able to use
{{BaseCheckTestSupport}} from the Checkstyle project. This is not distributed
with their regular {{jar}}, since it's needed only for compiling and running
custom checks (eg. {{AvoidTransactionalOnPrivateMethodsCheckTest}} in our case).
* {{$checkstyle.version}} for the {{checkstyle/test-jar}} dependency, and
{{}} for the regular {{checkstyle}} dependency are inherited from the
parent pom, ie. {{ambari-project/pom.xml}}.
* There is no need to always compile the whole root project. However, when
working with a single module (eg. {{ambari-server}}), one needs to get the
dependencies in one of two ways:
* Always make dependencies, too, with the {{-am}} Maven flag. Note that
Ambari Web, Logsearch, etc. are skipped, since those are not required for the
building the server.
* Get the dependencies from some repository. In our case this means having
to install {{utility}}, its parents, and some other Ambari projects in a local
repository once. One needs to re-install them if the dependencies themselves
are updated.
* Now I've noticed that running {{mvn checkstyle:check}} performs the default
checks instead of our custom list, because the configuration was done only for
the execution tied to the test phase, not for the plugin itself. This is being
fixed in AMBARI-19158.
{noformat:title=Always making dependencies}
$ mvn -am -pl ambari-server clean compile
...
[INFO] Reactor Build Order:
[INFO]
[INFO] Ambari Main
[INFO] Apache Ambari Project POM
[INFO] Ambari Views
[INFO] utility
[INFO] ambari-metrics
[INFO] Ambari Metrics Common
[INFO] Ambari Server
{noformat}
{noformat:title=Installing once}
$ mvn -am -pl ambari-server -DskipTests clean install
$ cd ambari-server
$ mvn -DskipTest clean test
$ mvn checkstyle:check
{noformat}
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19158) Plugin configuration ignored when directly running checkstyle goals
[
https://issues.apache.org/jira/browse/AMBARI-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19158:
---
Attachment: AMBARI-19158.patch
> Plugin configuration ignored when directly running checkstyle goals
> ---
>
> Key: AMBARI-19158
> URL: https://issues.apache.org/jira/browse/AMBARI-19158
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19158.patch
>
>
> Checkstyle uses the default checks when running {{mvn checkstyle:check}} on
> {{ambari-server}} instead of the custom list defined in
> {{ambari-server/checkstyle.xml}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19158) Plugin configuration ignored when directly running checkstyle goals
[
https://issues.apache.org/jira/browse/AMBARI-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19158:
---
Status: Patch Available (was: Open)
> Plugin configuration ignored when directly running checkstyle goals
> ---
>
> Key: AMBARI-19158
> URL: https://issues.apache.org/jira/browse/AMBARI-19158
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19158.patch
>
>
> Checkstyle uses the default checks when running {{mvn checkstyle:check}} on
> {{ambari-server}} instead of the custom list defined in
> {{ambari-server/checkstyle.xml}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19158) Plugin configuration ignored when directly running checkstyle goals
Doroszlai, Attila created AMBARI-19158:
--
Summary: Plugin configuration ignored when directly running
checkstyle goals
Key: AMBARI-19158
URL: https://issues.apache.org/jira/browse/AMBARI-19158
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Priority: Minor
Fix For: 3.0.0, 2.5.0
Checkstyle uses the default checks when running {{mvn checkstyle:check}} on
{{ambari-server}} instead of the custom list defined in
{{ambari-server/checkstyle.xml}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19157) hive_heapsize property should not auto add m
[ https://issues.apache.org/jira/browse/AMBARI-19157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19157: --- Status: Patch Available (was: Open) > hive_heapsize property should not auto add m > > > Key: AMBARI-19157 > URL: https://issues.apache.org/jira/browse/AMBARI-19157 > Project: Ambari > Issue Type: Bug > Components: ambari-web, stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: AMBARI-19157.patch > > > ambari web auto adds 'm' to hive_heapsize property and that leads to an extra > m in the hive-env.sh file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19157) hive_heapsize property should not auto add m
Sumit Mohanty created AMBARI-19157: -- Summary: hive_heapsize property should not auto add m Key: AMBARI-19157 URL: https://issues.apache.org/jira/browse/AMBARI-19157 Project: Ambari Issue Type: Bug Components: ambari-web, stacks Affects Versions: 2.5.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 2.5.0 ambari web auto adds 'm' to hive_heapsize property and that leads to an extra m in the hive-env.sh file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[ https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19156: --- Status: Patch Available (was: Open) > Install Packages fails with the old stack has services removed in the new > stack > --- > > Key: AMBARI-19156 > URL: https://issues.apache.org/jira/browse/AMBARI-19156 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19156.patch > > > Install packages step (before RU/EU) fails with err "Cannot enumerate > services" if the current stack has services that have been removed in the new > stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, > where Spark's metainfo.xml in mystack-2.0 has the true > section. > Workaround is to remove Spark before attempting the install packages. > The error is below: > 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] > BaseManagementHandler:61 - Caught a system exception while attempting to > create a resource: Cannot enumerate services > org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate > services > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) > at > org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[ https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19156: --- Attachment: AMBARI-19156.patch > Install Packages fails with the old stack has services removed in the new > stack > --- > > Key: AMBARI-19156 > URL: https://issues.apache.org/jira/browse/AMBARI-19156 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19156.patch > > > Install packages step (before RU/EU) fails with err "Cannot enumerate > services" if the current stack has services that have been removed in the new > stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, > where Spark's metainfo.xml in mystack-2.0 has the true > section. > Workaround is to remove Spark before attempting the install packages. > The error is below: > 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] > BaseManagementHandler:61 - Caught a system exception while attempting to > create a resource: Cannot enumerate services > org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate > services > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) > at > org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
Di Li created AMBARI-19156: -- Summary: Install Packages fails with the old stack has services removed in the new stack Key: AMBARI-19156 URL: https://issues.apache.org/jira/browse/AMBARI-19156 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk, 2.5.0 Reporter: Di Li Assignee: Di Li Install packages step (before RU/EU) fails with err "Cannot enumerate services" if the current stack has services that have been removed in the new stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, where Spark's metainfo.xml in mystack-2.0 has the true section. Workaround is to remove Spark before attempting the install packages. The error is below: 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] BaseManagementHandler:61 - Caught a system exception while attempting to create a resource: Cannot enumerate services org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate services at org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) at org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) at org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) at org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) at org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) at org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) at org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) at org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) at org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) at org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) at org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19154) RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator
[ https://issues.apache.org/jira/browse/AMBARI-19154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736255#comment-15736255 ] Hudson commented on AMBARI-19154: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6202 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6202/]) AMBARI-19154. RAT check failure in (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=09fba63242eeb3c2cd6a06d9b23e11fcea5dee30]) * (edit) ambari-server/pom.xml > RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator > - > > Key: AMBARI-19154 > URL: https://issues.apache.org/jira/browse/AMBARI-19154 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19154.patch > > > Unapproved licenses: > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer-err.log > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19154) RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator
[ https://issues.apache.org/jira/browse/AMBARI-19154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736249#comment-15736249 ] Hudson commented on AMBARI-19154: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #502 (See [https://builds.apache.org/job/Ambari-branch-2.5/502/]) AMBARI-19154. RAT check failure in (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=93bc5d8192de9860940ba938986e33d07d3d01aa]) * (edit) ambari-server/pom.xml > RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator > - > > Key: AMBARI-19154 > URL: https://issues.apache.org/jira/browse/AMBARI-19154 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19154.patch > > > Unapproved licenses: > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer-err.log > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19141) Refinements for AMS whitelisting.
[ https://issues.apache.org/jira/browse/AMBARI-19141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19141: --- Description: Must Haves Ability to specify metric expressions for whitelisting. Ability to whitelist/blacklist metrics from entire sources (APP_IDs) was: Must Haves Ability to specify metric expressions for whitelisting. Ability to whitelist/blacklist metrics from entire sources (APP_IDs) Nice to Haves Ability to update metric whitelist through AMS API. > Refinements for AMS whitelisting. > - > > Key: AMBARI-19141 > URL: https://issues.apache.org/jira/browse/AMBARI-19141 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > > Must Haves > Ability to specify metric expressions for whitelisting. > Ability to whitelist/blacklist metrics from entire sources (APP_IDs) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19141) Refinements for AMS whitelisting.
[ https://issues.apache.org/jira/browse/AMBARI-19141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19141: --- Description: Ability to specify metric expressions for whitelisting. Ability to whitelist/blacklist metrics from entire sources (APP_IDs) was: Must Haves Ability to specify metric expressions for whitelisting. Ability to whitelist/blacklist metrics from entire sources (APP_IDs) > Refinements for AMS whitelisting. > - > > Key: AMBARI-19141 > URL: https://issues.apache.org/jira/browse/AMBARI-19141 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > > Ability to specify metric expressions for whitelisting. > Ability to whitelist/blacklist metrics from entire sources (APP_IDs) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19155) Ambari Blueprint doesn't configure the SmartSense ActiveAnalysis Admin password
[ https://issues.apache.org/jira/browse/AMBARI-19155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19155: - Attachment: 9374-screen-shot-2016-11-11-at-202221.png > Ambari Blueprint doesn't configure the SmartSense ActiveAnalysis Admin > password > --- > > Key: AMBARI-19155 > URL: https://issues.apache.org/jira/browse/AMBARI-19155 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez > Attachments: 9374-screen-shot-2016-11-11-at-202221.png > > > When using a blueprint to install HDP 2.5.0 including SmartSense, the > ActivityAnalysis admin password is not configured by the "default_password" > in blueprint. The component fails to start, and the user has to set the > password manually. > See attached screenshot. > This issue was created based on > https://community.hortonworks.com/questions/66107/ambari-blueprint-doesnt-configure-the-smartsense-a.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19155) Ambari Blueprint doesn't configure the SmartSense ActiveAnalysis Admin password
Alejandro Fernandez created AMBARI-19155: Summary: Ambari Blueprint doesn't configure the SmartSense ActiveAnalysis Admin password Key: AMBARI-19155 URL: https://issues.apache.org/jira/browse/AMBARI-19155 Project: Ambari Issue Type: Bug Components: blueprints Affects Versions: 2.4.0 Reporter: Alejandro Fernandez When using a blueprint to install HDP 2.5.0 including SmartSense, the ActivityAnalysis admin password is not configured by the "default_password" in blueprint. The component fails to start, and the user has to set the password manually. See attached screenshot. This issue was created based on https://community.hortonworks.com/questions/66107/ambari-blueprint-doesnt-configure-the-smartsense-a.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18435) Provide script to delete an old HDP stack version
[
https://issues.apache.org/jira/browse/AMBARI-18435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736154#comment-15736154
]
Alejandro Fernandez commented on AMBARI-18435:
--
Here's the API call to remove older versions. E.g.,
{code}
curl 'http://c6401.ambari.apache.org:8080/api/v1/clusters/cl1/requests' -u
admin:admin -H "X-Requested-By: ambari" -X POST
-d'{"RequestInfo":{"context":"remove_previous_stacks", "action" :
"remove_previous_stacks", "parameters" : {"version":"2.5.0.0-1245"}},
"Requests/resource_filters": [{"hosts":"c6403.ambari.apache.org,
c6402.ambari.apache.org"}]}'
{code}
That removes all versions older than "2.5.0.0-1245". Version mentioned in
request remains intact. We also have checks that prevent removing the current
version and the operation is idempotent.
> Provide script to delete an old HDP stack version
> -
>
> Key: AMBARI-18435
> URL: https://issues.apache.org/jira/browse/AMBARI-18435
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18435.patch
>
>
> We need a script or hacky solution internally for base-cluster to be able to
> delete old HDP stacks.
> This does not need to be a full-blown feature with tons of bells and whistles
> and UI support.
> Instead, it needs to be a simple script that can be ran on all hosts.
> Ideally, it would accept the version of the stack to remove, and perhaps can
> go into contrib.
> If we want to make it slightly better, than we can figure out how to actually
> make it a custom command to remove older versions (value is less than the
> CURRENT version).
> If done this way, we can add checks to make it more robust, bubble up errors
> to the UI task output, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736113#comment-15736113
]
Jonathan Hurley commented on AMBARI-19149:
--
I too am having issues with {{utility}}. A few observations:
- Why isn't {{utility}} scoped under {{org.apache.ambari}}? Why is it just
{{utility}}?
- It looks like {{utility/pom.xml}} is invalid. It includes two dependency
sections for {{com.puppycrawl.tools}}
-- https://github.com/apache/ambari/blob/trunk/utility/pom.xml#L40-L50
- When I install {{utility-1.0.0.0-SNAPSHOT}}, the generated {{pom.xml}} is
wrong:
-- [WARNING] The POM for org.apache.ambari:utility:jar:1.0.0.0-SNAPSHOT is
invalid, transitive dependencies (if any) will not be available: 1 problem was
encountered while building the effective model for
org.apache.ambari:utility:1.0.0.0-SNAPSHOT
[ERROR] 'dependencies.dependency.version' for
com.puppycrawl.tools:checkstyle:jar is missing.
- I have to manually edit this generated {{utility/pom.xml}}:
-- Replace ${checkstyle.version}} with 6.19
-- Remove partial {{dependency}} on {{com.puppycrawl.tools}}
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19154) RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator
[ https://issues.apache.org/jira/browse/AMBARI-19154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19154: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit 09fba63242eeb3c2cd6a06d9b23e11fcea5dee30 branch-2.5, commit 93bc5d8192de9860940ba938986e33d07d3d01aa > RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator > - > > Key: AMBARI-19154 > URL: https://issues.apache.org/jira/browse/AMBARI-19154 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19154.patch > > > Unapproved licenses: > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer-err.log > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19154) RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator
[ https://issues.apache.org/jira/browse/AMBARI-19154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736101#comment-15736101 ] Nate Cole commented on AMBARI-19154: +1 > RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator > - > > Key: AMBARI-19154 > URL: https://issues.apache.org/jira/browse/AMBARI-19154 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19154.patch > > > Unapproved licenses: > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer-err.log > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19154) RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator
[ https://issues.apache.org/jira/browse/AMBARI-19154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736103#comment-15736103 ] Robert Levas commented on AMBARI-19154: --- +1 for [^AMBARI-19154.patch] > RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator > - > > Key: AMBARI-19154 > URL: https://issues.apache.org/jira/browse/AMBARI-19154 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19154.patch > > > Unapproved licenses: > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer-err.log > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19154) RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator
[ https://issues.apache.org/jira/browse/AMBARI-19154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19154: - Status: Patch Available (was: Open) > RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator > - > > Key: AMBARI-19154 > URL: https://issues.apache.org/jira/browse/AMBARI-19154 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19154.patch > > > Unapproved licenses: > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer-err.log > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19154) RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator
[ https://issues.apache.org/jira/browse/AMBARI-19154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19154: - Attachment: AMBARI-19154.patch > RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator > - > > Key: AMBARI-19154 > URL: https://issues.apache.org/jira/browse/AMBARI-19154 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19154.patch > > > Unapproved licenses: > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer-err.log > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19154) RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator
[ https://issues.apache.org/jira/browse/AMBARI-19154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19154: - Reporter: Nahappan Somasundaram (was: Alejandro Fernandez) > RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator > - > > Key: AMBARI-19154 > URL: https://issues.apache.org/jira/browse/AMBARI-19154 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > > Unapproved licenses: > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer-err.log > src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736082#comment-15736082
]
Nate Cole commented on AMBARI-19149:
[~adoroszlai]
I was not able to get this running standalone in ambari-server (something I
definitely want to do, since I don't always compile out of the root source
tree). I want to run only out of a-s:
{noformat}
mvn checkstyle:checkstyle
{noformat}
One change was to {{ambari-server/pom.xml}} to include
{{checkstyle.xml}} in checkstyle plugin. Then
it couldn't load {{utility}} because of some error related to
{{checkstyle.version}}. I didn't research this thoroughly to understand all
the changes needed.
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19154) RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator
Alejandro Fernandez created AMBARI-19154: Summary: RAT check failure in HDFS/3.0.0/package/scripts/balancer-emulator Key: AMBARI-19154 URL: https://issues.apache.org/jira/browse/AMBARI-19154 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.5.0 Unapproved licenses: src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer-err.log src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19139) UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but before was 'Falcon Web UI'
[ https://issues.apache.org/jira/browse/AMBARI-19139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736006#comment-15736006 ] Hudson commented on AMBARI-19139: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6201 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6201/]) AMBARI-19139. UI: Quick Link from Falcon has not correct name (Now: (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d6c0587a317127b44f258b3f160284695e412f3e]) * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/quicklinks/quicklinks.json > UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but > before was 'Falcon Web UI' > --- > > Key: AMBARI-19139 > URL: https://issues.apache.org/jira/browse/AMBARI-19139 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19139.patch > > > STR: > 1)Deploy cluster > 2)Check Quick Links from Falcon > *Actual result:* UI: Quick Link from Falcon has not correct name (Now: Falcon > Dashboard), but before was Falcon Web UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19152) Perf: UI hangs after click on button, on step
[
https://issues.apache.org/jira/browse/AMBARI-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735978#comment-15735978
]
Hadoop QA commented on AMBARI-19152:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842578/AMBARI-19152.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/9609//console
This message is automatically generated.
> Perf: UI hangs after click on button, on step
> -
>
> Key: AMBARI-19152
> URL: https://issues.apache.org/jira/browse/AMBARI-19152
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.5.0
>
> Attachments: AMBARI-19152.patch
>
>
> STR:
> 1) prepare perf cluster on GCE.
> 2) Go through deploy steps to "Assign Masters" step.
> 3) Assign each master to separate host.
> 4) Click "Next" button.
> Not always, but in most of cases UI hangs. One more thing, if you will not
> assign masters to different hosts this issue will not reproduce.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19139) UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but before was 'Falcon Web UI'
[ https://issues.apache.org/jira/browse/AMBARI-19139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-19139: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and 2.5 > UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but > before was 'Falcon Web UI' > --- > > Key: AMBARI-19139 > URL: https://issues.apache.org/jira/browse/AMBARI-19139 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19139.patch > > > STR: > 1)Deploy cluster > 2)Check Quick Links from Falcon > *Actual result:* UI: Quick Link from Falcon has not correct name (Now: Falcon > Dashboard), but before was Falcon Web UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735936#comment-15735936
]
Doroszlai, Attila commented on AMBARI-19149:
[~jonathan.hurley] Do you think the patch for the imports can be committed?
I'd like to avoid too much conflict if possible.
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19153) "Create Principals" fails intermittently
[
https://issues.apache.org/jira/browse/AMBARI-19153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-19153:
Affects Version/s: 2.5.0
> "Create Principals" fails intermittently
>
>
> Key: AMBARI-19153
> URL: https://issues.apache.org/jira/browse/AMBARI-19153
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.5.0
>
>
> {panel:title=stderr}
> 2016-12-05 21:08:15,369 - Failed to create principal,
> activity_explorer/host-3.dom...@example.com - Failed to execute the command:
> Broken pipe
> {panel}
> {panel:title=stdout}
> 2016-12-05 21:07:40,114 - Processing identities...\n2016-12-05 21:07:40,120 -
> Processing principal, activity_explorer/host-3.dom...@example.com
> {panel}
> {panel:title=from ambari-server.log}
> 05 Dec 2016 21:08:55,686 INFO [Server Action Executor Worker 166]
> KerberosServerAction:353 - Processing identities...
> 05 Dec 2016 21:08:55,689 INFO [Server Action Executor Worker 166]
> CreatePrincipalsServerAction:203 - Processing principal,
> HTTP/host-2.dom...@example.com
> 05 Dec 2016 21:09:05,698 WARN [Server Action Executor Worker 166]
> MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of
> 10 seconds :
> Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com,
> -r, EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
> 05 Dec 2016 21:09:05,709 ERROR [Server Action Executor Worker 166]
> KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
> java.io.IOException: Broken pipe
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:345)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.BufferedWriter.flush(BufferedWriter.java:254)
> at
> org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosOperationHandler.executeCommand(KerberosOperationHandler.java:736)
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.invokeKAdmin(MITKerberosOperationHandler.java:464)
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:195)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:256)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:159)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processRecord(KerberosServerAction.java:532)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:414)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:91)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:555)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:492)
> at java.lang.Thread.run(Thread.java:745)
> 05 Dec 2016 21:09:15,710 WARN [Server Action Executor Worker 166]
> MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of
> 10 seconds :
> Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com,
> -r, EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
> 05 Dec 2016 21:09:15,722 ERROR [Server Action Executor Worker 166]
> KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
> java.io.IOException: Broken pipe
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:345)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.BufferedWriter.flush(BufferedWriter.java:254)
> at
> org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
> at
>
[jira] [Updated] (AMBARI-19153) "Create Principals" fails intermittently
[
https://issues.apache.org/jira/browse/AMBARI-19153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-19153:
Fix Version/s: 2.5.0
> "Create Principals" fails intermittently
>
>
> Key: AMBARI-19153
> URL: https://issues.apache.org/jira/browse/AMBARI-19153
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.5.0
>
>
> {panel:title=stderr}
> 2016-12-05 21:08:15,369 - Failed to create principal,
> activity_explorer/host-3.dom...@example.com - Failed to execute the command:
> Broken pipe
> {panel}
> {panel:title=stdout}
> 2016-12-05 21:07:40,114 - Processing identities...\n2016-12-05 21:07:40,120 -
> Processing principal, activity_explorer/host-3.dom...@example.com
> {panel}
> {panel:title=from ambari-server.log}
> 05 Dec 2016 21:08:55,686 INFO [Server Action Executor Worker 166]
> KerberosServerAction:353 - Processing identities...
> 05 Dec 2016 21:08:55,689 INFO [Server Action Executor Worker 166]
> CreatePrincipalsServerAction:203 - Processing principal,
> HTTP/host-2.dom...@example.com
> 05 Dec 2016 21:09:05,698 WARN [Server Action Executor Worker 166]
> MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of
> 10 seconds :
> Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com,
> -r, EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
> 05 Dec 2016 21:09:05,709 ERROR [Server Action Executor Worker 166]
> KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
> java.io.IOException: Broken pipe
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:345)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.BufferedWriter.flush(BufferedWriter.java:254)
> at
> org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosOperationHandler.executeCommand(KerberosOperationHandler.java:736)
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.invokeKAdmin(MITKerberosOperationHandler.java:464)
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:195)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:256)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:159)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processRecord(KerberosServerAction.java:532)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:414)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:91)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:555)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:492)
> at java.lang.Thread.run(Thread.java:745)
> 05 Dec 2016 21:09:15,710 WARN [Server Action Executor Worker 166]
> MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of
> 10 seconds :
> Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com,
> -r, EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
> 05 Dec 2016 21:09:15,722 ERROR [Server Action Executor Worker 166]
> KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
> java.io.IOException: Broken pipe
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:345)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.BufferedWriter.flush(BufferedWriter.java:254)
> at
> org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
> at
>
[jira] [Updated] (AMBARI-19153) "Create Principals" fails intermittently
[
https://issues.apache.org/jira/browse/AMBARI-19153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-19153:
Description:
{panel:title=stderr}
2016-12-05 21:08:15,369 - Failed to create principal,
activity_explorer/host-3.dom...@example.com - Failed to execute the command:
Broken pipe
{panel}
{panel:title=stdout}
2016-12-05 21:07:40,114 - Processing identities...\n2016-12-05 21:07:40,120 -
Processing principal, activity_explorer/host-3.dom...@example.com
{panel}
{panel:title=from ambari-server.log}
05 Dec 2016 21:08:55,686 INFO [Server Action Executor Worker 166]
KerberosServerAction:353 - Processing identities...
05 Dec 2016 21:08:55,689 INFO [Server Action Executor Worker 166]
CreatePrincipalsServerAction:203 - Processing principal,
HTTP/host-2.dom...@example.com
05 Dec 2016 21:09:05,698 WARN [Server Action Executor Worker 166]
MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of 10
seconds :
Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com, -r,
EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
05 Dec 2016 21:09:05,709 ERROR [Server Action Executor Worker 166]
KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
java.io.IOException: Broken pipe
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:345)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
at java.io.BufferedWriter.flush(BufferedWriter.java:254)
at
org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
at
org.apache.ambari.server.serveraction.kerberos.KerberosOperationHandler.executeCommand(KerberosOperationHandler.java:736)
at
org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.invokeKAdmin(MITKerberosOperationHandler.java:464)
at
org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:195)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:256)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:159)
at
org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processRecord(KerberosServerAction.java:532)
at
org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:414)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:91)
at
org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:555)
at
org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:492)
at java.lang.Thread.run(Thread.java:745)
05 Dec 2016 21:09:15,710 WARN [Server Action Executor Worker 166]
MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of 10
seconds :
Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com, -r,
EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
05 Dec 2016 21:09:15,722 ERROR [Server Action Executor Worker 166]
KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
java.io.IOException: Broken pipe
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:345)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
at java.io.BufferedWriter.flush(BufferedWriter.java:254)
at
org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
at
org.apache.ambari.server.serveraction.kerberos.KerberosOperationHandler.executeCommand(KerberosOperationHandler.java:736)
at
org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.invokeKAdmin(MITKerberosOperationHandler.java:464)
at
org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:195)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:256)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:159)
at
[jira] [Updated] (AMBARI-19153) "Create Principals" fails intermittently
[
https://issues.apache.org/jira/browse/AMBARI-19153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-19153:
Description:
{panel:title=stderr}
2016-12-05 21:08:15,369 - Failed to create principal,
activity_explorer/host-3.dom...@example.com - Failed to execute the command:
Broken pipe
{panel}
{panel:title=stdout}
2016-12-05 21:07:40,114 - Processing identities...\n2016-12-05 21:07:40,120 -
Processing principal, activity_explorer/host-3.dom...@example.com
{panel}
{panel:title=from ambari-server.log}
05 Dec 2016 21:08:55,686 INFO [Server Action Executor Worker 166]
KerberosServerAction:353 - Processing identities...
05 Dec 2016 21:08:55,689 INFO [Server Action Executor Worker 166]
CreatePrincipalsServerAction:203 - Processing principal,
HTTP/host-2.dom...@example.com
05 Dec 2016 21:09:05,698 WARN [Server Action Executor Worker 166]
MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of 10
seconds :
Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com, -r,
EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
05 Dec 2016 21:09:05,709 ERROR [Server Action Executor Worker 166]
KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
java.io.IOException: Broken pipe
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:345)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
at java.io.BufferedWriter.flush(BufferedWriter.java:254)
at
org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
at
org.apache.ambari.server.serveraction.kerberos.KerberosOperationHandler.executeCommand(KerberosOperationHandler.java:736)
at
org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.invokeKAdmin(MITKerberosOperationHandler.java:464)
at
org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:195)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:256)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:159)
at
org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processRecord(KerberosServerAction.java:532)
at
org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:414)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:91)
at
org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:555)
at
org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:492)
at java.lang.Thread.run(Thread.java:745)
05 Dec 2016 21:09:15,710 WARN [Server Action Executor Worker 166]
MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of 10
seconds :
Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com, -r,
EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
05 Dec 2016 21:09:15,722 ERROR [Server Action Executor Worker 166]
KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
java.io.IOException: Broken pipe
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:345)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
at java.io.BufferedWriter.flush(BufferedWriter.java:254)
at
org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
at
org.apache.ambari.server.serveraction.kerberos.KerberosOperationHandler.executeCommand(KerberosOperationHandler.java:736)
at
org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.invokeKAdmin(MITKerberosOperationHandler.java:464)
at
org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:195)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:256)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:159)
at
[jira] [Updated] (AMBARI-19153) "Create Principals" fails intermittently
[
https://issues.apache.org/jira/browse/AMBARI-19153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-19153:
Component/s: ambari-server
> "Create Principals" fails intermittently
>
>
> Key: AMBARI-19153
> URL: https://issues.apache.org/jira/browse/AMBARI-19153
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
>
> # Jira description
> {panel:title=stderr}
> 2016-12-05 21:08:15,369 - Failed to create principal,
> activity_explorer/host-3.dom...@example.com - Failed to execute the command:
> Broken pipe
> {panel}
> {panel:title=stdout}
> 2016-12-05 21:07:40,114 - Processing identities...\n2016-12-05 21:07:40,120 -
> Processing principal, activity_explorer/host-3.dom...@example.com
> {panel}
> {panel:title=from ambari-server.log}
> 05 Dec 2016 21:08:55,686 INFO [Server Action Executor Worker 166]
> KerberosServerAction:353 - Processing identities...
> 05 Dec 2016 21:08:55,689 INFO [Server Action Executor Worker 166]
> CreatePrincipalsServerAction:203 - Processing principal,
> HTTP/host-2.dom...@example.com
> 05 Dec 2016 21:09:05,698 WARN [Server Action Executor Worker 166]
> MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of
> 10 seconds :
> Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com,
> -r, EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
> 05 Dec 2016 21:09:05,709 ERROR [Server Action Executor Worker 166]
> KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
> java.io.IOException: Broken pipe
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:345)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.BufferedWriter.flush(BufferedWriter.java:254)
> at
> org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosOperationHandler.executeCommand(KerberosOperationHandler.java:736)
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.invokeKAdmin(MITKerberosOperationHandler.java:464)
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:195)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:256)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:159)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processRecord(KerberosServerAction.java:532)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:414)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:91)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:555)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:492)
> at java.lang.Thread.run(Thread.java:745)
> 05 Dec 2016 21:09:15,710 WARN [Server Action Executor Worker 166]
> MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of
> 10 seconds :
> Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com,
> -r, EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
> 05 Dec 2016 21:09:15,722 ERROR [Server Action Executor Worker 166]
> KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
> java.io.IOException: Broken pipe
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:345)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.BufferedWriter.flush(BufferedWriter.java:254)
> at
> org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
> at
>
[jira] [Created] (AMBARI-19153) "Create Principals" fails intermittently
Dmitry Lysnichenko created AMBARI-19153:
---
Summary: "Create Principals" fails intermittently
Key: AMBARI-19153
URL: https://issues.apache.org/jira/browse/AMBARI-19153
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Priority: Critical
# Jira description
{panel:title=stderr}
2016-12-05 21:08:15,369 - Failed to create principal,
activity_explorer/host-3.dom...@example.com - Failed to execute the command:
Broken pipe
{panel}
{panel:title=stdout}
2016-12-05 21:07:40,114 - Processing identities...\n2016-12-05 21:07:40,120 -
Processing principal, activity_explorer/host-3.dom...@example.com
{panel}
{panel:title=from ambari-server.log}
05 Dec 2016 21:08:55,686 INFO [Server Action Executor Worker 166]
KerberosServerAction:353 - Processing identities...
05 Dec 2016 21:08:55,689 INFO [Server Action Executor Worker 166]
CreatePrincipalsServerAction:203 - Processing principal,
HTTP/host-2.dom...@example.com
05 Dec 2016 21:09:05,698 WARN [Server Action Executor Worker 166]
MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of 10
seconds :
Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com, -r,
EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
05 Dec 2016 21:09:05,709 ERROR [Server Action Executor Worker 166]
KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
java.io.IOException: Broken pipe
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:345)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
at java.io.BufferedWriter.flush(BufferedWriter.java:254)
at
org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
at
org.apache.ambari.server.serveraction.kerberos.KerberosOperationHandler.executeCommand(KerberosOperationHandler.java:736)
at
org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.invokeKAdmin(MITKerberosOperationHandler.java:464)
at
org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:195)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:256)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:159)
at
org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processRecord(KerberosServerAction.java:532)
at
org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:414)
at
org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:91)
at
org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:555)
at
org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:492)
at java.lang.Thread.run(Thread.java:745)
05 Dec 2016 21:09:15,710 WARN [Server Action Executor Worker 166]
MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of 10
seconds :
Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com, -r,
EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
05 Dec 2016 21:09:15,722 ERROR [Server Action Executor Worker 166]
KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
java.io.IOException: Broken pipe
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:345)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
at java.io.BufferedWriter.flush(BufferedWriter.java:254)
at
org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
at
org.apache.ambari.server.serveraction.kerberos.KerberosOperationHandler.executeCommand(KerberosOperationHandler.java:736)
at
org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.invokeKAdmin(MITKerberosOperationHandler.java:464)
at
org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:195)
at
[jira] [Commented] (AMBARI-19152) Perf: UI hangs after click on button, on step
[
https://issues.apache.org/jira/browse/AMBARI-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735759#comment-15735759
]
Hadoop QA commented on AMBARI-19152:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842578/AMBARI-19152.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/9608//console
This message is automatically generated.
> Perf: UI hangs after click on button, on step
> -
>
> Key: AMBARI-19152
> URL: https://issues.apache.org/jira/browse/AMBARI-19152
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.5.0
>
> Attachments: AMBARI-19152.patch
>
>
> STR:
> 1) prepare perf cluster on GCE.
> 2) Go through deploy steps to "Assign Masters" step.
> 3) Assign each master to separate host.
> 4) Click "Next" button.
> Not always, but in most of cases UI hangs. One more thing, if you will not
> assign masters to different hosts this issue will not reproduce.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19152) Perf: UI hangs after click on button, on step
[ https://issues.apache.org/jira/browse/AMBARI-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19152: -- Status: Patch Available (was: Open) > Perf: UI hangs after click on button, on step > - > > Key: AMBARI-19152 > URL: https://issues.apache.org/jira/browse/AMBARI-19152 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19152.patch > > > STR: > 1) prepare perf cluster on GCE. > 2) Go through deploy steps to "Assign Masters" step. > 3) Assign each master to separate host. > 4) Click "Next" button. > Not always, but in most of cases UI hangs. One more thing, if you will not > assign masters to different hosts this issue will not reproduce. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19152) Perf: UI hangs after click on button, on step
[ https://issues.apache.org/jira/browse/AMBARI-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19152: -- Attachment: AMBARI-19152.patch > Perf: UI hangs after click on button, on step > - > > Key: AMBARI-19152 > URL: https://issues.apache.org/jira/browse/AMBARI-19152 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19152.patch > > > STR: > 1) prepare perf cluster on GCE. > 2) Go through deploy steps to "Assign Masters" step. > 3) Assign each master to separate host. > 4) Click "Next" button. > Not always, but in most of cases UI hangs. One more thing, if you will not > assign masters to different hosts this issue will not reproduce. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19152) Perf: UI hangs after click on button, on step
[ https://issues.apache.org/jira/browse/AMBARI-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735727#comment-15735727 ] Andrii Tkach commented on AMBARI-19152: --- 19878 tests complete (27 seconds) 155 tests pending > Perf: UI hangs after click on button, on step > - > > Key: AMBARI-19152 > URL: https://issues.apache.org/jira/browse/AMBARI-19152 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19152.patch > > > STR: > 1) prepare perf cluster on GCE. > 2) Go through deploy steps to "Assign Masters" step. > 3) Assign each master to separate host. > 4) Click "Next" button. > Not always, but in most of cases UI hangs. One more thing, if you will not > assign masters to different hosts this issue will not reproduce. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19152) Perf: UI hangs after click on button, on step
Andrii Tkach created AMBARI-19152: - Summary: Perf: UI hangs after click on button, on step Key: AMBARI-19152 URL: https://issues.apache.org/jira/browse/AMBARI-19152 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.5.0 STR: 1) prepare perf cluster on GCE. 2) Go through deploy steps to "Assign Masters" step. 3) Assign each master to separate host. 4) Click "Next" button. Not always, but in most of cases UI hangs. One more thing, if you will not assign masters to different hosts this issue will not reproduce. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19077) Ambari-server: Gather dependent configuration types and password properties for a service component
[ https://issues.apache.org/jira/browse/AMBARI-19077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735698#comment-15735698 ] Hudson commented on AMBARI-19077: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #500 (See [https://builds.apache.org/job/Ambari-branch-2.5/500/]) AMBARI-19077: Ambari-server: Gather dependent configuration types and (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d22422ba18fff615416231574c45332a13c045d7]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/PropertyInfo.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java > Ambari-server: Gather dependent configuration types and password properties > for a service component > --- > > Key: AMBARI-19077 > URL: https://issues.apache.org/jira/browse/AMBARI-19077 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > Attachments: rb54357.patch > > > In the command JSON, we need the list of configurations and the corresponding > password properties on which a service component is dependent upon. This will > help ambari agent create the JCEKS provider files for just those affected > configuration types instead of for all configuration types that contain > password properties. > We also need to provide the password properties and the properties that use > it. This will ensure that we are able to correctly map the value provided by > the user property to the value provided by the password property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735694#comment-15735694 ] Hudson commented on AMBARI-1: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #500 (See [https://builds.apache.org/job/Ambari-branch-2.5/500/]) Revert "Revert "AMBARI-1: Ambari-agent: Create configuration files (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=24ac5cdae228c0f421034f5c897f0635eb9bf52e]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (edit) ambari-agent/conf/unix/ambari-agent.ini * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java * (edit) ambari-agent/src/packages/tarball/all.xml > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Attachments: rb53747.patch > > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19149:
---
Attachment: (was: AMBARI-19149-1.patch)
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19077) Ambari-server: Gather dependent configuration types and password properties for a service component
[ https://issues.apache.org/jira/browse/AMBARI-19077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-19077: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari-server: Gather dependent configuration types and password properties > for a service component > --- > > Key: AMBARI-19077 > URL: https://issues.apache.org/jira/browse/AMBARI-19077 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > Attachments: rb54357.patch > > > In the command JSON, we need the list of configurations and the corresponding > password properties on which a service component is dependent upon. This will > help ambari agent create the JCEKS provider files for just those affected > configuration types instead of for all configuration types that contain > password properties. > We also need to provide the password properties and the properties that use > it. This will ensure that we are able to correctly map the value provided by > the user property to the value provided by the password property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-1: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Attachments: rb53747.patch > > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18791) ADD configs for DRUID in KNOX service definitions
[ https://issues.apache.org/jira/browse/AMBARI-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-18791: -- Attachment: ambari-18791.patch > ADD configs for DRUID in KNOX service definitions > - > > Key: AMBARI-18791 > URL: https://issues.apache.org/jira/browse/AMBARI-18791 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-18791.patch > > > KNOX now supports proxying druid services - > https://issues.apache.org/jira/browse/KNOX-758 > Add configs for DRUID in KNOX service definitions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18791) ADD configs for DRUID in KNOX service definitions
[ https://issues.apache.org/jira/browse/AMBARI-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-18791: -- Attachment: (was: ambari-18791.patch) > ADD configs for DRUID in KNOX service definitions > - > > Key: AMBARI-18791 > URL: https://issues.apache.org/jira/browse/AMBARI-18791 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-18791.patch > > > KNOX now supports proxying druid services - > https://issues.apache.org/jira/browse/KNOX-758 > Add configs for DRUID in KNOX service definitions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19149:
---
Status: Patch Available (was: Open)
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, AMBARI-19149-1.patch,
> IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19149:
---
Attachment: AMBARI-19149-1.patch
Rebased to [current
trunk|https://git1-us-west.apache.org/repos/asf?p=ambari.git;a=commit;h=c8ae4b4]
(needed to update {{ClusterConfigEntity}} and {{AmbariServerTest}}).
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, AMBARI-19149-1.patch,
> IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19149:
---
Attachment: IDEA_Ambari_v1.xml
IntelliJ IDEA setting for imports
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19114) Update hardcoded stack version warning to be more general than saying hdp
[ https://issues.apache.org/jira/browse/AMBARI-19114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735554#comment-15735554 ] Hudson commented on AMBARI-19114: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #499 (See [https://builds.apache.org/job/Ambari-branch-2.5/499/]) AMBARI-19114. Add property existence check to druid stack advisor code (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2a840811896ddb84343dea1db12842ef35e30d3d]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py > Update hardcoded stack version warning to be more general than saying hdp > - > > Key: AMBARI-19114 > URL: https://issues.apache.org/jira/browse/AMBARI-19114 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19114.patch > > > Update hardcoded stack version warning to be more general than saying hdp -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19114) Update hardcoded stack version warning to be more general than saying hdp
[ https://issues.apache.org/jira/browse/AMBARI-19114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735549#comment-15735549 ] Hudson commented on AMBARI-19114: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6200 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6200/]) AMBARI-19114. Add property existence check to druid stack advisor code (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c8ae4b4157df72e735457e0a62d9197742e7f150]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py > Update hardcoded stack version warning to be more general than saying hdp > - > > Key: AMBARI-19114 > URL: https://issues.apache.org/jira/browse/AMBARI-19114 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19114.patch > > > Update hardcoded stack version warning to be more general than saying hdp -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19144) Add property existence check to druid stack advisor code
[ https://issues.apache.org/jira/browse/AMBARI-19144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19144: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > Add property existence check to druid stack advisor code > > > Key: AMBARI-19144 > URL: https://issues.apache.org/jira/browse/AMBARI-19144 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: 2.5.0 > > Attachments: ambari-19114.patch > > > Druid stack advisor assumes that druid-common will always be present in > configurations. Generally, we cannot assume that druid configuration is > always available.So adding a check for if "druid-common" exists in > services['configurations'] will be enough. Review the rest of the code and > ensure that there are checks for the existence of the config types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18990) Auto-fix common issues found by the DB consistency checker
[ https://issues.apache.org/jira/browse/AMBARI-18990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735520#comment-15735520 ] Hudson commented on AMBARI-18990: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6199 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6199/]) AMBARI-18990. Auto-fix common issues found by the DB consistency checker (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a8222ae3b8dd909764f90083396045c4db7dcceb]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariServerTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyChecker.java * (edit) ambari-server/src/main/python/ambari-server.py * (edit) ambari-server/src/main/python/ambari_server_main.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java > Auto-fix common issues found by the DB consistency checker > -- > > Key: AMBARI-18990 > URL: https://issues.apache.org/jira/browse/AMBARI-18990 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.5.0 > > Attachments: AMBARI-18990.patch > > > Proposed auto-fixes > *Inconsistency for table hostcomponentdesiredstate and hostcomponentstate for > stack upgrade. > *Deleted services cause config table inconsistent > *Primary key constrain issue from old Ambari version > *Schema name in postgres is not ambari > *Inconsistency view > # If there are missing states (service, component, host), etc, then > automatically add one with a value of UNKNOWN or INSTALLED. > # If there are no selected configs, then select the latest ones (could be a > bit dangerous) > # If there are multiple selected configs for the same type, then unselect all > but the most recent (could be a bit dangerous) > For dangerous options, by default fail with warning, and provide console > option to perform fixes anyway (like the fsck does) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18990) Auto-fix common issues found by the DB consistency checker
[ https://issues.apache.org/jira/browse/AMBARI-18990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18990: Resolution: Fixed Status: Resolved (was: Patch Available) Committed 66c6d56078..a8222ae3b8 trunk -> trunk 54da8c27c9..6029846c94 branch-2.5 -> branch-2.5 > Auto-fix common issues found by the DB consistency checker > -- > > Key: AMBARI-18990 > URL: https://issues.apache.org/jira/browse/AMBARI-18990 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.5.0 > > Attachments: AMBARI-18990.patch > > > Proposed auto-fixes > *Inconsistency for table hostcomponentdesiredstate and hostcomponentstate for > stack upgrade. > *Deleted services cause config table inconsistent > *Primary key constrain issue from old Ambari version > *Schema name in postgres is not ambari > *Inconsistency view > # If there are missing states (service, component, host), etc, then > automatically add one with a value of UNKNOWN or INSTALLED. > # If there are no selected configs, then select the latest ones (could be a > bit dangerous) > # If there are multiple selected configs for the same type, then unselect all > but the most recent (could be a bit dangerous) > For dangerous options, by default fail with warning, and provide console > option to perform fixes anyway (like the fsck does) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19130) Downgrade Can Create Multiple Mappings For Latest Configs
[
https://issues.apache.org/jira/browse/AMBARI-19130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19130:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Downgrade Can Create Multiple Mappings For Latest Configs
> -
>
> Key: AMBARI-19130
> URL: https://issues.apache.org/jira/browse/AMBARI-19130
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19130.patch
>
>
> During a downgrade which crosses major stack versions (such as from HDP 2.y
> to HDP 2.x), Ambari attempts to set the latest configurations from HDP 2.x as
> "current". However, after the downgrade succeeds, the database fails with the
> following consistency check:
> {code}
> ERROR - You have config(s), in cluster c1, that is(are) selected more than
> once in clusterconfigmapping table:
> ranger-storm-plugin-properties,mapred-env,webhcat-env,hive-exec-log4j,hive-log4j,webhcat-log4j,storm-env,yarn-log4j,hcat-env
> {code}
> The problem is actually not with {{clusterconfig}} but with the state of the
> {{clusterconfigmapping}} table _before_ upgrade. Apparently, it is possible
> to have multiple mappings for the same config. We match on the config type
> and tag (such as hdfs-site / version1234566789). There should never, EVER be
> duplicate mappings for the same config and version tag.
> The current downgrade code doesn't "break" after finding its first match:
> {code}
> for(ClusterConfigMappingEntity configMappingEntity:
> configMappingEntities){
> String type = configMappingEntity.getType();
> String tag = configMappingEntity.getTag();
> for (ClusterConfigMappingEntity latest : latestConfigMappingByStack) {
> String latestType = latest.getType();
> String latestTag = latest.getTag();
> // find the latest config of a given mapping entity
> if (StringUtils.equals(type, latestType) && StringUtils.equals(tag,
> latestTag)) {
> LOG.info("{} with version tag {} is selected for stack {}", type,
> tag, stackId.toString());
> configMappingEntity.setSelected(1);
> }
> }
> }
> {code}
> I'm not sure that breaking will work here since we don't know the ordering.
> We could order the results and then break on the first match. In any event,
> it's a problem. But it's only a problem for the latest version of a config
> since that's what we're going to try to make selected.
> Here's a query from a test cluster which shows that if this cluster were to
> be downgraded, 5 configs would have multiple mappings created. This is
> because for the latest config, there are multiple mappings in
> {{clusterconfigmapping}}.
> {noformat}
> SELECT
> mapping.type_name,
> mapping.version_tag,
> COUNT(*)
> FROM clusterconfigmapping mapping
> JOIN (SELECT
> config.type_name,
> config.version_tag,
> MAX(config.version) AS latest_version
> FROM clusterconfig config
> GROUP BY config.type_name) AS latestConfig
> ON latestConfig.type_name = mapping.type_name
> AND latestConfig.version_tag = mapping.version_tag
> GROUP BY
> type_name, version_tag
> HAVING COUNT(*) > 1
> +---+--+--+
> | type_name | version_tag | COUNT(*) |
> +---+--+--+
> | hcat-env | version1 |5 |
> | hive-exec-log4j | version1 |5 |
> | hive-log4j| version1 |5 |
> | ranger-hive-plugin-properties | version1436918769763 |3 |
> | webhcat-env | version1 |5 |
> +---+--+--+
> 5 rows in set (0.00 sec)
> {noformat}
> STR:
> # Install a cluster, and instrument the {{clusterconfigmapping}} table to
> have multiple mappings for a given type (with only 1 currently selected).
> # Upgrade and then downgrade
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-19066) Add more logging around status command report processing on server side
[ https://issues.apache.org/jira/browse/AMBARI-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari resolved AMBARI-19066. - Resolution: Fixed > Add more logging around status command report processing on server side > --- > > Key: AMBARI-19066 > URL: https://issues.apache.org/jira/browse/AMBARI-19066 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-18323_v2.patch, AMBARI-19066.patch > > > Add more INFO level logging in HeartbeatProcessor.processStatusReports, > AgentRequests.setExecutionDetailsRequest to be able to trace status command > report processing and agent request for execution command details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18990) Auto-fix common issues found by the DB consistency checker
[ https://issues.apache.org/jira/browse/AMBARI-18990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735368#comment-15735368 ] Hudson commented on AMBARI-18990: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #498 (See [https://builds.apache.org/job/Ambari-branch-2.5/498/]) AMBARI-18990. Auto-fix common issues found by the DB consistency checker (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6029846c94d3b9aa00bee7282071270206781688]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java * (edit) ambari-server/src/main/python/ambari_server_main.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyChecker.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariServerTest.java * (edit) ambari-server/src/main/python/ambari-server.py > Auto-fix common issues found by the DB consistency checker > -- > > Key: AMBARI-18990 > URL: https://issues.apache.org/jira/browse/AMBARI-18990 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.5.0 > > Attachments: AMBARI-18990.patch > > > Proposed auto-fixes > *Inconsistency for table hostcomponentdesiredstate and hostcomponentstate for > stack upgrade. > *Deleted services cause config table inconsistent > *Primary key constrain issue from old Ambari version > *Schema name in postgres is not ambari > *Inconsistency view > # If there are missing states (service, component, host), etc, then > automatically add one with a value of UNKNOWN or INSTALLED. > # If there are no selected configs, then select the latest ones (could be a > bit dangerous) > # If there are multiple selected configs for the same type, then unselect all > but the most recent (could be a bit dangerous) > For dangerous options, by default fail with warning, and provide console > option to perform fixes anyway (like the fsck does) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735337#comment-15735337
]
Nate Cole commented on AMBARI-19149:
+1
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735339#comment-15735339
]
Laszlo Puskas commented on AMBARI-19149:
+1. once we have all the rules in the checkstyle configuration we might export
and store (e.: on a wiki page) the adapted intellij / eclipse settings to be
used by all devs.
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735314#comment-15735314
]
Jonathan Hurley commented on AMBARI-19149:
--
+1 - Nice use of {{checkstyle}}!
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19148) Wrong filter groups names "Missing translation" on "Upgrade history" tab of Stack and Versions
[ https://issues.apache.org/jira/browse/AMBARI-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735310#comment-15735310 ] Hudson commented on AMBARI-19148: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #497 (See [https://builds.apache.org/job/Ambari-branch-2.5/497/]) AMBARI-19148 Wrong filter groups names "Missing translation" on "Upgrade (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=54da8c27c97fd1f9ff2c3bc8af5c9b882608d5aa]) * (edit) ambari-web/app/messages.js > Wrong filter groups names "Missing translation" on "Upgrade history" tab of > Stack and Versions > -- > > Key: AMBARI-19148 > URL: https://issues.apache.org/jira/browse/AMBARI-19148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19148.patch, Wrong filter groups name.png > > > STR: > # Deploy HDP 2.3 on Ambari 2.5.0.0-425 > # Enable NN HA > # Register and install HDP 2.5.3.0 > # Perform RU to the new HDP version. > # Open "Upgrade history" tab of Stack and Versions > # Open Filters > Result: There are not "Failed Upgrade" and "Failed Downgrade" in filters. > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735249#comment-15735249
]
Doroszlai, Attila edited comment on AMBARI-19149 at 12/9/16 1:24 PM:
-
I think it's easier to review if the cleanup is done in steps, grouped by the
type of change.
[^AMBARI-19149-1.patch] is the first patch, which cleans up imports:
* Remove unused imports
* Get rid of {{*}} imports
* Rearrange imports according to specified order
* Add Checkstyle check for build-time validation
Testing done:
* ran Java unit tests
{noformat}
Tests run: 4797, Failures: 0, Errors: 0, Skipped: 37
{noformat}
* ran checkstyle check:
{noformat}
[INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle) @ ambari-server ---
[INFO] Starting audit...
Audit done.
{noformat}
(Note: RAT check fails on 2 files added for AMBARI-19137.)
[~jonathan.hurley], [~ncole], [~lpuskas]
This patch is too big for ReviewBoard (got HTTP 502). Could you please review
here?
was (Author: adoroszlai):
* Remove unused imports
* Get rid of {{*}} imports
* Rearrange imports according to specified order
* Add Checkstyle check for build-time validation
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19148) Wrong filter groups names "Missing translation" on "Upgrade history" tab of Stack and Versions
[ https://issues.apache.org/jira/browse/AMBARI-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19148: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Wrong filter groups names "Missing translation" on "Upgrade history" tab of > Stack and Versions > -- > > Key: AMBARI-19148 > URL: https://issues.apache.org/jira/browse/AMBARI-19148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19148.patch, Wrong filter groups name.png > > > STR: > # Deploy HDP 2.3 on Ambari 2.5.0.0-425 > # Enable NN HA > # Register and install HDP 2.5.3.0 > # Perform RU to the new HDP version. > # Open "Upgrade history" tab of Stack and Versions > # Open Filters > Result: There are not "Failed Upgrade" and "Failed Downgrade" in filters. > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19148) Wrong filter groups names "Missing translation" on "Upgrade history" tab of Stack and Versions
[ https://issues.apache.org/jira/browse/AMBARI-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735275#comment-15735275 ] Andrii Tkach commented on AMBARI-19148: --- committed to branch-2.5 > Wrong filter groups names "Missing translation" on "Upgrade history" tab of > Stack and Versions > -- > > Key: AMBARI-19148 > URL: https://issues.apache.org/jira/browse/AMBARI-19148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19148.patch, Wrong filter groups name.png > > > STR: > # Deploy HDP 2.3 on Ambari 2.5.0.0-425 > # Enable NN HA > # Register and install HDP 2.5.3.0 > # Perform RU to the new HDP version. > # Open "Upgrade history" tab of Stack and Versions > # Open Filters > Result: There are not "Failed Upgrade" and "Failed Downgrade" in filters. > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19148) Wrong filter groups names "Missing translation" on "Upgrade history" tab of Stack and Versions
[ https://issues.apache.org/jira/browse/AMBARI-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735271#comment-15735271 ] Andrii Tkach commented on AMBARI-19148: --- Patch required only for branch-2.5. > Wrong filter groups names "Missing translation" on "Upgrade history" tab of > Stack and Versions > -- > > Key: AMBARI-19148 > URL: https://issues.apache.org/jira/browse/AMBARI-19148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19148.patch, Wrong filter groups name.png > > > STR: > # Deploy HDP 2.3 on Ambari 2.5.0.0-425 > # Enable NN HA > # Register and install HDP 2.5.3.0 > # Perform RU to the new HDP version. > # Open "Upgrade history" tab of Stack and Versions > # Open Filters > Result: There are not "Failed Upgrade" and "Failed Downgrade" in filters. > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19149:
---
Attachment: AMBARI-19149-1.patch
* Remove unused imports
* Get rid of {{*}} imports
* Rearrange imports according to specified order
* Add Checkstyle check for build-time validation
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19150) Stack Advisor Throws Exception On ZooKeeper Configs
[
https://issues.apache.org/jira/browse/AMBARI-19150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-19150:
-
Status: Patch Available (was: Open)
> Stack Advisor Throws Exception On ZooKeeper Configs
> ---
>
> Key: AMBARI-19150
> URL: https://issues.apache.org/jira/browse/AMBARI-19150
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19150.patch
>
>
> When viewing the ZooKeeper configurations, the following Python error is
> thrown:
> {code}
> Caused by:
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException:
> Stack Advisor reported an error: TypeError: 'NoneType' object has no
> attribute '__getitem__'
> {code}
> {code:title=stackadvisor.out}
> StackAdvisor implementation for stack HDP, version 2.0.6 was loaded
> StackAdvisor implementation for stack HDP, version 2.1 was loaded
> StackAdvisor implementation for stack HDP, version 2.2 was loaded
> StackAdvisor implementation for stack HDP, version 2.3 was loaded
> StackAdvisor implementation for stack HDP, version 2.4 was loaded
> Returning HDP24StackAdvisor implementation
> Error occured in stack advisor.
> Error details: 'NoneType' object has no attribute '__getitem__'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19151) New REST API in Log Search Portal that returns the log files of the host components
Miklos Gergely created AMBARI-19151: --- Summary: New REST API in Log Search Portal that returns the log files of the host components Key: AMBARI-19151 URL: https://issues.apache.org/jira/browse/AMBARI-19151 Project: Ambari Issue Type: Task Components: ambari-logsearch Affects Versions: 2.5.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.5.0 Ambari Server fetches the log file names of the host components by fetching the log entries, and get the log file field of the first entry it founds. This new API replaces this logic, it explicitly returns the log files of a host component, and thus giving the control to the Log Search server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19150) Stack Advisor Throws Exception On ZooKeeper Configs
[
https://issues.apache.org/jira/browse/AMBARI-19150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-19150:
-
Attachment: AMBARI-19150.patch
> Stack Advisor Throws Exception On ZooKeeper Configs
> ---
>
> Key: AMBARI-19150
> URL: https://issues.apache.org/jira/browse/AMBARI-19150
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19150.patch
>
>
> When viewing the ZooKeeper configurations, the following Python error is
> thrown:
> {code}
> Caused by:
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException:
> Stack Advisor reported an error: TypeError: 'NoneType' object has no
> attribute '__getitem__'
> {code}
> {code:title=stackadvisor.out}
> StackAdvisor implementation for stack HDP, version 2.0.6 was loaded
> StackAdvisor implementation for stack HDP, version 2.1 was loaded
> StackAdvisor implementation for stack HDP, version 2.2 was loaded
> StackAdvisor implementation for stack HDP, version 2.3 was loaded
> StackAdvisor implementation for stack HDP, version 2.4 was loaded
> Returning HDP24StackAdvisor implementation
> Error occured in stack advisor.
> Error details: 'NoneType' object has no attribute '__getitem__'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19147) LogSearch - generate default jks file on startup
[ https://issues.apache.org/jira/browse/AMBARI-19147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19147: -- Summary: LogSearch - generate default jks file on startup (was: LogSearch - generate jks file on startup) > LogSearch - generate default jks file on startup > > > Key: AMBARI-19147 > URL: https://issues.apache.org/jira/browse/AMBARI-19147 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19150) Stack Advisor Throws Exception On ZooKeeper Configs
Dmytro Grinenko created AMBARI-19150:
Summary: Stack Advisor Throws Exception On ZooKeeper Configs
Key: AMBARI-19150
URL: https://issues.apache.org/jira/browse/AMBARI-19150
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk, 2.5.0
Reporter: Dmytro Grinenko
Priority: Critical
Fix For: trunk, 2.5.0
When viewing the ZooKeeper configurations, the following Python error is thrown:
{code}
Caused by:
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException: Stack
Advisor reported an error: TypeError: 'NoneType' object has no attribute
'__getitem__'
{code}
{code:title=stackadvisor.out}
StackAdvisor implementation for stack HDP, version 2.0.6 was loaded
StackAdvisor implementation for stack HDP, version 2.1 was loaded
StackAdvisor implementation for stack HDP, version 2.2 was loaded
StackAdvisor implementation for stack HDP, version 2.3 was loaded
StackAdvisor implementation for stack HDP, version 2.4 was loaded
Returning HDP24StackAdvisor implementation
Error occured in stack advisor.
Error details: 'NoneType' object has no attribute '__getitem__'
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19146) Refactor widget instance view on Dashboard
[ https://issues.apache.org/jira/browse/AMBARI-19146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735203#comment-15735203 ] Hudson commented on AMBARI-19146: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6198 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6198/]) AMBARI-19146 Refactor widget instance view on Dashboard. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=66c6d5607867a95d29deee00407ef8b7ef22ee03]) * (edit) ambari-web/app/styles/dashboard.less * (edit) ambari-web/app/templates/main/dashboard/widgets/simple_text.hbs * (edit) ambari-web/app/views/main/dashboard/widget.js * (edit) ambari-web/app/templates/main/dashboard/widgets/pie_chart.hbs * (edit) ambari-web/test/views/main/dashboard/widget_test.js * (edit) ambari-web/app/templates/main/dashboard/edit_widget_popup.hbs > Refactor widget instance view on Dashboard > -- > > Key: AMBARI-19146 > URL: https://issues.apache.org/jira/browse/AMBARI-19146 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19146.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19149) Clean up Ambari Server source code warnings
Doroszlai, Attila created AMBARI-19149:
--
Summary: Clean up Ambari Server source code warnings
Key: AMBARI-19149
URL: https://issues.apache.org/jira/browse/AMBARI-19149
Project: Ambari
Issue Type: Task
Components: ambari-server
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Fix For: 3.0.0
Eclipse's default warnings generated for {{ambari-server}} number roughly over
3300. Out of these, at least half of them are:
* Unused imports
* Type safety due to forgotten {{<>}}
* Missing Serialization IDs from anonymous {{HashMap}} implementations
* Unused variables
* {{Capture}} in tests
* {{switch}} fall-through and missing {{case statements}}: *only makes changes
which won't affect existing functionality*
This makes spotting actual problems, like missing {{case}} statements a
nightmare. We need to go through and clean out as many of these warnings as
possible.
Note: With respect to the import cleanup, the IDE of choice should have the
following import order setup. They should always be expanded and never use
{{*}}.
# {{java}}
# {{javax}}
# {{org}}
# {{com}}
# other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19148) Wrong filter groups names "Missing translation" on "Upgrade history" tab of Stack and Versions
[ https://issues.apache.org/jira/browse/AMBARI-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19148: -- Status: Patch Available (was: Open) > Wrong filter groups names "Missing translation" on "Upgrade history" tab of > Stack and Versions > -- > > Key: AMBARI-19148 > URL: https://issues.apache.org/jira/browse/AMBARI-19148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19148.patch, Wrong filter groups name.png > > > STR: > # Deploy HDP 2.3 on Ambari 2.5.0.0-425 > # Enable NN HA > # Register and install HDP 2.5.3.0 > # Perform RU to the new HDP version. > # Open "Upgrade history" tab of Stack and Versions > # Open Filters > Result: There are not "Failed Upgrade" and "Failed Downgrade" in filters. > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19148) Wrong filter groups names "Missing translation" on "Upgrade history" tab of Stack and Versions
[ https://issues.apache.org/jira/browse/AMBARI-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735192#comment-15735192 ] Andrii Tkach commented on AMBARI-19148: --- 25565 tests complete (21 seconds) 57 tests pending > Wrong filter groups names "Missing translation" on "Upgrade history" tab of > Stack and Versions > -- > > Key: AMBARI-19148 > URL: https://issues.apache.org/jira/browse/AMBARI-19148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: Wrong filter groups name.png > > > STR: > # Deploy HDP 2.3 on Ambari 2.5.0.0-425 > # Enable NN HA > # Register and install HDP 2.5.3.0 > # Perform RU to the new HDP version. > # Open "Upgrade history" tab of Stack and Versions > # Open Filters > Result: There are not "Failed Upgrade" and "Failed Downgrade" in filters. > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19148) Wrong filter groups names "Missing translation" on "Upgrade history" tab of Stack and Versions
[ https://issues.apache.org/jira/browse/AMBARI-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19148: -- Attachment: Wrong filter groups name.png > Wrong filter groups names "Missing translation" on "Upgrade history" tab of > Stack and Versions > -- > > Key: AMBARI-19148 > URL: https://issues.apache.org/jira/browse/AMBARI-19148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: Wrong filter groups name.png > > > STR: > # Deploy HDP 2.3 on Ambari 2.5.0.0-425 > # Enable NN HA > # Register and install HDP 2.5.3.0 > # Perform RU to the new HDP version. > # Open "Upgrade history" tab of Stack and Versions > # Open Filters > Result: There are not "Failed Upgrade" and "Failed Downgrade" in filters. > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19148) Wrong filter groups names "Missing translation" on "Upgrade history" tab of Stack and Versions
[ https://issues.apache.org/jira/browse/AMBARI-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19148: -- Description: STR: # Deploy HDP 2.3 on Ambari 2.5.0.0-425 # Enable NN HA # Register and install HDP 2.5.3.0 # Perform RU to the new HDP version. # Open "Upgrade history" tab of Stack and Versions # Open Filters Result: There are not "Failed Upgrade" and "Failed Downgrade" in filters. Screenshot is attached. was: STR: # Deploy HDP 2.3 on Ambari 2.5.0.0-425 # Enable NN HA # Register and install HDP 2.5.3.0 # Perform RU to the new HDP version. # Open "Upgrade history" tab of Stack and Versions # Open Filters Result: There are not "Failed Upgrade" and "Failed Downgrade" in filters. > Wrong filter groups names "Missing translation" on "Upgrade history" tab of > Stack and Versions > -- > > Key: AMBARI-19148 > URL: https://issues.apache.org/jira/browse/AMBARI-19148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > > STR: > # Deploy HDP 2.3 on Ambari 2.5.0.0-425 > # Enable NN HA > # Register and install HDP 2.5.3.0 > # Perform RU to the new HDP version. > # Open "Upgrade history" tab of Stack and Versions > # Open Filters > Result: There are not "Failed Upgrade" and "Failed Downgrade" in filters. > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19148) Wrong filter groups names "Missing translation" on "Upgrade history" tab of Stack and Versions
Andrii Tkach created AMBARI-19148: - Summary: Wrong filter groups names "Missing translation" on "Upgrade history" tab of Stack and Versions Key: AMBARI-19148 URL: https://issues.apache.org/jira/browse/AMBARI-19148 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.5.0 STR: # Deploy HDP 2.3 on Ambari 2.5.0.0-425 # Enable NN HA # Register and install HDP 2.5.3.0 # Perform RU to the new HDP version. # Open "Upgrade history" tab of Stack and Versions # Open Filters Result: There are not "Failed Upgrade" and "Failed Downgrade" in filters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19147) LogSearch - generate jks file on startup
Olivér Szabó created AMBARI-19147: - Summary: LogSearch - generate jks file on startup Key: AMBARI-19147 URL: https://issues.apache.org/jira/browse/AMBARI-19147 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.4.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19012) Abillity to use external Solr for Log Search instead of AMBARI_INFRA_SOLR
[ https://issues.apache.org/jira/browse/AMBARI-19012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735152#comment-15735152 ] Hudson commented on AMBARI-19012: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #496 (See [https://builds.apache.org/job/Ambari-branch-2.5/496/]) AMBARI-19012. Abillity to use external Solr for Log Search instead of (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6150f9567f30c0952ffc9402f80b78965eb463b2]) * (edit) ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py > Abillity to use external Solr for Log Search instead of AMBARI_INFRA_SOLR > - > > Key: AMBARI-19012 > URL: https://issues.apache.org/jira/browse/AMBARI-19012 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19012.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19012) Abillity to use external Solr for Log Search instead of AMBARI_INFRA_SOLR
[ https://issues.apache.org/jira/browse/AMBARI-19012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735093#comment-15735093 ] Hudson commented on AMBARI-19012: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6197 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6197/]) AMBARI-19012. Abillity to use external Solr for Log Search instead of (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6a55220d16f04ddb3e7fc03f17d73f468ccd77c4]) * (edit) ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py > Abillity to use external Solr for Log Search instead of AMBARI_INFRA_SOLR > - > > Key: AMBARI-19012 > URL: https://issues.apache.org/jira/browse/AMBARI-19012 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19012.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19146) Refactor widget instance view on Dashboard
[ https://issues.apache.org/jira/browse/AMBARI-19146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19146: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Refactor widget instance view on Dashboard > -- > > Key: AMBARI-19146 > URL: https://issues.apache.org/jira/browse/AMBARI-19146 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19146.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19146) Refactor widget instance view on Dashboard
[ https://issues.apache.org/jira/browse/AMBARI-19146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735076#comment-15735076 ] Andrii Tkach commented on AMBARI-19146: --- committed to trunk > Refactor widget instance view on Dashboard > -- > > Key: AMBARI-19146 > URL: https://issues.apache.org/jira/browse/AMBARI-19146 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19146.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
