[jira] [Updated] (AMBARI-24569) Cannot deploy Hive Metastore with Kerberos without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-24569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24569:
Labels: pull-request-available (was: )
> Cannot deploy Hive Metastore with Kerberos without HDFS
> ---
>
> Key: AMBARI-24569
> URL: https://issues.apache.org/jira/browse/AMBARI-24569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
>
> In order to enable Kerberos for Hive MetaStore we need a property in
> {{core-site}}, which is ignored by Ambari if HDFS is not present. Hive
> Metastore start fails due to empty {{core-site}} with:
> {noformat}
> KeeperException$InvalidACLException: KeeperErrorCode = InvalidACL for
> /hive/cluster/delegationMETASTORE/keys
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24569) Cannot deploy Hive Metastore with Kerberos without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-24569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-24569:
---
Status: Patch Available (was: In Progress)
> Cannot deploy Hive Metastore with Kerberos without HDFS
> ---
>
> Key: AMBARI-24569
> URL: https://issues.apache.org/jira/browse/AMBARI-24569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In order to enable Kerberos for Hive MetaStore we need a property in
> {{core-site}}, which is ignored by Ambari if HDFS is not present. Hive
> Metastore start fails due to empty {{core-site}} with:
> {noformat}
> KeeperException$InvalidACLException: KeeperErrorCode = InvalidACL for
> /hive/cluster/delegationMETASTORE/keys
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (AMBARI-24569) Cannot deploy Hive Metastore with Kerberos without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-24569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila reopened AMBARI-24569:
Assignee: Doroszlai, Attila
> Cannot deploy Hive Metastore with Kerberos without HDFS
> ---
>
> Key: AMBARI-24569
> URL: https://issues.apache.org/jira/browse/AMBARI-24569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Fix For: 2.7.2
>
>
> In order to enable Kerberos for Hive MetaStore we need a property in
> {{core-site}}, which is ignored by Ambari if HDFS is not present. Hive
> Metastore start fails due to empty {{core-site}} with:
> {noformat}
> KeeperException$InvalidACLException: KeeperErrorCode = InvalidACL for
> /hive/cluster/delegationMETASTORE/keys
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24756) Restart All service on a host function not working
[ https://issues.apache.org/jira/browse/AMBARI-24756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24756: Labels: pull-request-available (was: ) > Restart All service on a host function not working > -- > > Key: AMBARI-24756 > URL: https://issues.apache.org/jira/browse/AMBARI-24756 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Jason Golieb >Assignee: Jason Golieb >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > Navigate to summary page for a single host. > Drop down Host Actions menu. > Click Restart All. > Server throws exception about missing stackId. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24756) Restart All service on a host function not working
Jason Golieb created AMBARI-24756: - Summary: Restart All service on a host function not working Key: AMBARI-24756 URL: https://issues.apache.org/jira/browse/AMBARI-24756 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Jason Golieb Assignee: Jason Golieb Fix For: 3.0.0 Navigate to summary page for a single host. Drop down Host Actions menu. Click Restart All. Server throws exception about missing stackId. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24755) Feature to trigger multiple / all service checks from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-24755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643797#comment-16643797 ] Dinesh Chitlangia commented on AMBARI-24755: [~paulcodding] - It will be great to have this feature. > Feature to trigger multiple / all service checks from Ambari > > > Key: AMBARI-24755 > URL: https://issues.apache.org/jira/browse/AMBARI-24755 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Dinesh Chitlangia >Priority: Major > Labels: service-check, usability > > During upgrades, Ambari prompts often to re-run service check for one or more > components. > This is painful as one has to go to service page for each component and > trigger service check manually. > If we can add a feature on Ambari UI or even on the command line to trigger > multiple service checks or trigger all at once, it would be great. > I have a makeshift utility that I use for my work today. > [https://community.hortonworks.com/repos/178314/trigger-ambari-service-check-for-multipleall-compo.html] > > Please see if the idea from this utility can be added to Ambari. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24755) Feature to trigger multiple / all service checks from Ambari
Dinesh Chitlangia created AMBARI-24755: -- Summary: Feature to trigger multiple / all service checks from Ambari Key: AMBARI-24755 URL: https://issues.apache.org/jira/browse/AMBARI-24755 Project: Ambari Issue Type: Improvement Components: ambari-server Reporter: Dinesh Chitlangia During upgrades, Ambari prompts often to re-run service check for one or more components. This is painful as one has to go to service page for each component and trigger service check manually. If we can add a feature on Ambari UI or even on the command line to trigger multiple service checks or trigger all at once, it would be great. I have a makeshift utility that I use for my work today. [https://community.hortonworks.com/repos/178314/trigger-ambari-service-check-for-multipleall-compo.html] Please see if the idea from this utility can be added to Ambari. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24749) Stackadvisor error while enabling HSI
[
https://issues.apache.org/jira/browse/AMBARI-24749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi resolved AMBARI-24749.
Resolution: Duplicate
> Stackadvisor error while enabling HSI
> -
>
> Key: AMBARI-24749
> URL: https://issues.apache.org/jira/browse/AMBARI-24749
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.3
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.3
>
>
> Stackadvisor error while enabling HSI
> STR:
> On a deployed cluster, enable HSI from Hive Service Page. Stackadvisor throws
> error
>
> {code}
> Traceback (most recent call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 184,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 138,
> in main
> result = stackAdvisor.validateConfigurations(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1079, in validateConfigurations
> validationItems = self.getConfigurationsValidationItems(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1463, in getConfigurationsValidationItems
> recommendations = self.recommendConfigurations(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1639, in recommendConfigurations
> serviceAdvisor.getServiceConfigurationRecommendations(configurations,
> clusterSummary, services, hosts)
> File
> "/var/lib/ambari-server/resources/stacks/HDP/3.0/services/ZEPPELIN/service_advisor.py",
> line 124, in getServiceConfigurationRecommendations
> recommender.recommendZeppelinConfigurationsFromHDP25(configurations,
> clusterData, services, hosts)
> File
> "/var/lib/ambari-server/resources/stacks/HDP/3.0/services/ZEPPELIN/service_advisor.py",
> line 190, in recommendZeppelinConfigurationsFromHDP25
> shiro_ini_content = zeppelin_shiro_ini['shiro_ini_content']
> TypeError: 'NoneType' object has no attribute '__getitem__'
> {code}
> As a result HSI start fails because of misconfiguration
> {code}
> Failed: Cache size (0B) has to be smaller than the container sizing (0B)
> java.lang.IllegalArgumentException: Cache size (0B) has to be smaller than
> the container sizing (0B)
> at com.google.common.base.Preconditions.checkArgument(Preconditions.java:122)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:248)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:120)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps
[
https://issues.apache.org/jira/browse/AMBARI-24551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643399#comment-16643399
]
ASF GitHub Bot commented on AMBARI-24551:
-
aBabiichuk commented on a change in pull request #5: [AMBARI-24551] [Log Search
UI] get rid of redundant requests after undoing or redoing several history steps
URL: https://github.com/apache/ambari-logsearch/pull/5#discussion_r223692185
##
File path: ambari-logsearch-web/src/app/services/history-manager.service.ts
##
@@ -209,18 +190,14 @@ export class HistoryManagerService {
* @returns {ListItem[]}
*/
get redoItems(): ListItem[] {
-const allItems = this.activeHistory.slice().reverse();
+const allItems = [...this.activeHistory].reverse();
let startIndex = allItems.findIndex((item: ListItem): boolean => {
-return item.value.previousChangeId === this.currentHistoryItemId &&
!item.value.isUndoOrRedo;
- }),
- endIndex = allItems.slice(startIndex + 1).findIndex((item: ListItem):
boolean => item.value.isUndoOrRedo);
+ return item.value.previousChangeId === this.currentHistoryItemId;
+});
if (startIndex === -1) {
startIndex = allItems.length;
}
-if (endIndex === -1) {
Review comment:
This isUndoOrRedo/endIndex logic shouldn't be removed here. It's needed to
handle the situation when after some undoing/redoing user goes on with
non-historical filters changes, so there's nothing to redo. Sorry for my
omission in previous comment.
P.S. Getting rid of hasNoPendingUndoOrRedo looks OK to me.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Log Search UI] get rid of redundant requests after undoing or redoing
> several history steps
>
>
> Key: AMBARI-24551
> URL: https://issues.apache.org/jira/browse/AMBARI-24551
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Original Estimate: 4h
> Time Spent: 2h 50m
> Remaining Estimate: 1h 10m
>
> After undoing or redoing more than one history items several redundant API
> requests are sent. This occurs because changes for several filter controls
> are applied step-by-step, and each control change generates new request.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps
[
https://issues.apache.org/jira/browse/AMBARI-24551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643400#comment-16643400
]
ASF GitHub Bot commented on AMBARI-24551:
-
aBabiichuk commented on a change in pull request #5: [AMBARI-24551] [Log Search
UI] get rid of redundant requests after undoing or redoing several history steps
URL: https://github.com/apache/ambari-logsearch/pull/5#discussion_r223692185
##
File path: ambari-logsearch-web/src/app/services/history-manager.service.ts
##
@@ -209,18 +190,14 @@ export class HistoryManagerService {
* @returns {ListItem[]}
*/
get redoItems(): ListItem[] {
-const allItems = this.activeHistory.slice().reverse();
+const allItems = [...this.activeHistory].reverse();
let startIndex = allItems.findIndex((item: ListItem): boolean => {
-return item.value.previousChangeId === this.currentHistoryItemId &&
!item.value.isUndoOrRedo;
- }),
- endIndex = allItems.slice(startIndex + 1).findIndex((item: ListItem):
boolean => item.value.isUndoOrRedo);
+ return item.value.previousChangeId === this.currentHistoryItemId;
+});
if (startIndex === -1) {
startIndex = allItems.length;
}
-if (endIndex === -1) {
Review comment:
This `isUndoOrRedo`/`endIndex` logic shouldn't be removed here. It's needed
to handle the situation when after some undoing/redoing user goes on with
non-historical filters changes, so there's nothing to redo. Sorry for my
omission in previous comment.
P.S. Getting rid of `hasNoPendingUndoOrRedo` looks OK to me.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Log Search UI] get rid of redundant requests after undoing or redoing
> several history steps
>
>
> Key: AMBARI-24551
> URL: https://issues.apache.org/jira/browse/AMBARI-24551
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Original Estimate: 4h
> Time Spent: 2h 50m
> Remaining Estimate: 1h 10m
>
> After undoing or redoing more than one history items several redundant API
> requests are sent. This occurs because changes for several filter controls
> are applied step-by-step, and each control change generates new request.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24752) upgrade ambari-utility and ambari-server-spi dependencies for JDK11
[
https://issues.apache.org/jira/browse/AMBARI-24752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24752:
Labels: jdk11 pull-request-available (was: jdk11)
> upgrade ambari-utility and ambari-server-spi dependencies for JDK11
> ---
>
> Key: AMBARI-24752
> URL: https://issues.apache.org/jira/browse/AMBARI-24752
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Gabor Boros
>Assignee: Gabor Boros
>Priority: Major
> Labels: jdk11, pull-request-available
> Fix For: 2.8.0
>
>
> {code}
> ± % java -version
> java version "11" 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
> ± % mvn clean test -Dgenerate.swagger.resources=true -Drat.skip -pl
> ambari-utility
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
>
> [INFO] Building ambari-utility 1.0.0.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ambari-utility ---
> [INFO] Deleting /Users/gboros/Documents/dev/ambari/ambari-utility/target
> [INFO] Deleting /Users/gboros/Documents/dev/ambari/ambari-utility (includes =
> [**/*.pyc], excludes = [])
> [INFO]
> [INFO] --- build-helper-maven-plugin:1.8:regex-property
> (parse-package-version) @ ambari-utility ---
> [INFO]
> [INFO] --- build-helper-maven-plugin:1.8:regex-property
> (parse-package-release) @ ambari-utility ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> ambari-utility ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 1 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @
> ambari-utility ---
> [INFO] Compiling 14 source files to
> /Users/gboros/Documents/dev/ambari/ambari-utility/target/classes
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
> ambari-utility ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @
> ambari-utility ---
> [INFO] Compiling 3 source files to
> /Users/gboros/Documents/dev/ambari/ambari-utility/target/test-classes
> [INFO]
> [INFO] --- maven-surefire-plugin:2.20:test (default-test) @ ambari-utility ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.ambari.swagger.AmbariSwaggerReaderTest
> [INFO] Running
> org.apache.ambari.checkstyle.UndocumentedRestApiOperationCheckTest
> [INFO] Running
> org.apache.ambari.checkstyle.AvoidTransactionalOnPrivateMethodsCheckTest
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.253
> s - in
> org.apache.ambari.checkstyle.AvoidTransactionalOnPrivateMethodsCheckTest
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.287
> s - in org.apache.ambari.checkstyle.UndocumentedRestApiOperationCheckTest
> [ERROR] Tests run: 8, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 1.479
> s <<< FAILURE! - in org.apache.ambari.swagger.AmbariSwaggerReaderTest
> [ERROR] swaggerBasicCase(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 1.21 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlRootElement
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerBasicCase(AmbariSwaggerReaderTest.java:71)
> Caused by: java.lang.ClassNotFoundException:
> javax.xml.bind.annotation.XmlRootElement
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerBasicCase(AmbariSwaggerReaderTest.java:71)
> [ERROR]
> swaggerConflictingNestedApis(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlRootElement
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApis(AmbariSwaggerReaderTest.java:86)
> [ERROR]
> swaggerConflictingNestedApisWithPreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0.004 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlRootElement
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent(AmbariSwaggerReaderTest.java:103)
> [ERROR]
> swaggerConflictingNestedApisWithSamePreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0.003 s <<< ERROR!
> java.lang.NoClassDefFoundError:
[jira] [Commented] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps
[ https://issues.apache.org/jira/browse/AMBARI-24551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643293#comment-16643293 ] ASF GitHub Bot commented on AMBARI-24551: - asfgit commented on issue #5: [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps URL: https://github.com/apache/ambari-logsearch/pull/5#issuecomment-428178681 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/9/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [Log Search UI] get rid of redundant requests after undoing or redoing > several history steps > > > Key: AMBARI-24551 > URL: https://issues.apache.org/jira/browse/AMBARI-24551 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.1 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.2 > > Original Estimate: 4h > Time Spent: 2h 50m > Remaining Estimate: 1h 10m > > After undoing or redoing more than one history items several redundant API > requests are sent. This occurs because changes for several filter controls > are applied step-by-step, and each control change generates new request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24754) Ambari should Allow creating Custom Service Users and Groups
Akhil S Naik created AMBARI-24754: - Summary: Ambari should Allow creating Custom Service Users and Groups Key: AMBARI-24754 URL: https://issues.apache.org/jira/browse/AMBARI-24754 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.6.1 Reporter: Akhil S Naik Currently, Ambari Is hardcoding the Name of Service Users and Groups many places which prevent us creating the user accounts in the Custom name . One such example will be : https://github.com/apache/ambari/blob/branch-2.6/ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/alerts/alert_spark2_livy_port.py#L40 where we are hardcoding LIVY Default user. ambari should allow to customize the user accounts and shouldnt hardcode the users and user groups in python code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24753) Ambari remove_previous_stacks doesnt work properly in SLES Operating systems
Akhil S Naik created AMBARI-24753:
-
Summary: Ambari remove_previous_stacks doesnt work properly in
SLES Operating systems
Key: AMBARI-24753
URL: https://issues.apache.org/jira/browse/AMBARI-24753
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.2
Reporter: Akhil S Naik
Ambari Supports Deleting an old HDP stack version which is not current version
with respect to Apache jira : AMBARI-18435
{code:java}
curl -u admin:asnaik -H "X-Requested-By:ambari" -i -X POST
http://172.25.39.146:8080/api/v1/clusters/c117/requests -d
'{"RequestInfo":{"context":"remove_previous_stacks", "action" :
"remove_previous_stacks", "parameters" : {"version":"2.6.5.0-292"}},
"Requests/resource_filters":
[{"hosts":"c117-node2.squadron-labs.com,c117-node3.squadron-labs.com,c117-node4.squadron-labs.com"}]}'
{code}
But for any reason if zypper refresh is failing the , the above curl command
gets picked up properly in Ambari and will show as "Succeeded," but the
operation doesn't actually remove any files or perform any other tasks.
Also the Zypper refresh may take more than 15 minutes the ambari will timeout
due to agent and we might need to retry the operation again. This 15 minutes
timeout though can be configured with agent.task.timeout in ambari.properties
there should be some provision to provide it via curl command only
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24752) upgrade ambari-utility and ambari-server-spi dependencies for JDK11
[
https://issues.apache.org/jira/browse/AMBARI-24752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Boros updated AMBARI-24752:
-
Summary: upgrade ambari-utility and ambari-server-spi dependencies for
JDK11 (was: upgrade ambari-utility dependencies for JDK11)
> upgrade ambari-utility and ambari-server-spi dependencies for JDK11
> ---
>
> Key: AMBARI-24752
> URL: https://issues.apache.org/jira/browse/AMBARI-24752
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Gabor Boros
>Assignee: Gabor Boros
>Priority: Major
> Labels: jdk11
> Fix For: 2.8.0
>
>
> {code}
> ± % java -version
> java version "11" 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
> ± % mvn clean test -Dgenerate.swagger.resources=true -Drat.skip -pl
> ambari-utility
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
>
> [INFO] Building ambari-utility 1.0.0.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ambari-utility ---
> [INFO] Deleting /Users/gboros/Documents/dev/ambari/ambari-utility/target
> [INFO] Deleting /Users/gboros/Documents/dev/ambari/ambari-utility (includes =
> [**/*.pyc], excludes = [])
> [INFO]
> [INFO] --- build-helper-maven-plugin:1.8:regex-property
> (parse-package-version) @ ambari-utility ---
> [INFO]
> [INFO] --- build-helper-maven-plugin:1.8:regex-property
> (parse-package-release) @ ambari-utility ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> ambari-utility ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 1 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @
> ambari-utility ---
> [INFO] Compiling 14 source files to
> /Users/gboros/Documents/dev/ambari/ambari-utility/target/classes
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
> ambari-utility ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @
> ambari-utility ---
> [INFO] Compiling 3 source files to
> /Users/gboros/Documents/dev/ambari/ambari-utility/target/test-classes
> [INFO]
> [INFO] --- maven-surefire-plugin:2.20:test (default-test) @ ambari-utility ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.ambari.swagger.AmbariSwaggerReaderTest
> [INFO] Running
> org.apache.ambari.checkstyle.UndocumentedRestApiOperationCheckTest
> [INFO] Running
> org.apache.ambari.checkstyle.AvoidTransactionalOnPrivateMethodsCheckTest
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.253
> s - in
> org.apache.ambari.checkstyle.AvoidTransactionalOnPrivateMethodsCheckTest
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.287
> s - in org.apache.ambari.checkstyle.UndocumentedRestApiOperationCheckTest
> [ERROR] Tests run: 8, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 1.479
> s <<< FAILURE! - in org.apache.ambari.swagger.AmbariSwaggerReaderTest
> [ERROR] swaggerBasicCase(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 1.21 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlRootElement
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerBasicCase(AmbariSwaggerReaderTest.java:71)
> Caused by: java.lang.ClassNotFoundException:
> javax.xml.bind.annotation.XmlRootElement
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerBasicCase(AmbariSwaggerReaderTest.java:71)
> [ERROR]
> swaggerConflictingNestedApis(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlRootElement
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApis(AmbariSwaggerReaderTest.java:86)
> [ERROR]
> swaggerConflictingNestedApisWithPreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0.004 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlRootElement
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent(AmbariSwaggerReaderTest.java:103)
> [ERROR]
> swaggerConflictingNestedApisWithSamePreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed:
[jira] [Created] (AMBARI-24752) upgrade ambari-utility dependencies for JDK11
Gabor Boros created AMBARI-24752:
Summary: upgrade ambari-utility dependencies for JDK11
Key: AMBARI-24752
URL: https://issues.apache.org/jira/browse/AMBARI-24752
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.1
Reporter: Gabor Boros
Assignee: Gabor Boros
Fix For: 2.8.0
{code}
± % java -version
java version "11" 2018-09-25
Java(TM) SE Runtime Environment 18.9 (build 11+28)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
± % mvn clean test -Dgenerate.swagger.resources=true -Drat.skip -pl
ambari-utility
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building ambari-utility 1.0.0.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ambari-utility ---
[INFO] Deleting /Users/gboros/Documents/dev/ambari/ambari-utility/target
[INFO] Deleting /Users/gboros/Documents/dev/ambari/ambari-utility (includes =
[**/*.pyc], excludes = [])
[INFO]
[INFO] --- build-helper-maven-plugin:1.8:regex-property (parse-package-version)
@ ambari-utility ---
[INFO]
[INFO] --- build-helper-maven-plugin:1.8:regex-property (parse-package-release)
@ ambari-utility ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
ambari-utility ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ ambari-utility
---
[INFO] Compiling 14 source files to
/Users/gboros/Documents/dev/ambari/ambari-utility/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
ambari-utility ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @
ambari-utility ---
[INFO] Compiling 3 source files to
/Users/gboros/Documents/dev/ambari/ambari-utility/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.20:test (default-test) @ ambari-utility ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.ambari.swagger.AmbariSwaggerReaderTest
[INFO] Running
org.apache.ambari.checkstyle.UndocumentedRestApiOperationCheckTest
[INFO] Running
org.apache.ambari.checkstyle.AvoidTransactionalOnPrivateMethodsCheckTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.253 s
- in org.apache.ambari.checkstyle.AvoidTransactionalOnPrivateMethodsCheckTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.287 s
- in org.apache.ambari.checkstyle.UndocumentedRestApiOperationCheckTest
[ERROR] Tests run: 8, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 1.479 s
<<< FAILURE! - in org.apache.ambari.swagger.AmbariSwaggerReaderTest
[ERROR] swaggerBasicCase(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 1.21 s <<< ERROR!
java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlRootElement
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerBasicCase(AmbariSwaggerReaderTest.java:71)
Caused by: java.lang.ClassNotFoundException:
javax.xml.bind.annotation.XmlRootElement
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerBasicCase(AmbariSwaggerReaderTest.java:71)
[ERROR]
swaggerConflictingNestedApis(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0.006 s <<< ERROR!
java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlRootElement
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApis(AmbariSwaggerReaderTest.java:86)
[ERROR]
swaggerConflictingNestedApisWithPreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0.004 s <<< ERROR!
java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlRootElement
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent(AmbariSwaggerReaderTest.java:103)
[ERROR]
swaggerConflictingNestedApisWithSamePreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0.003 s <<< ERROR!
java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlRootElement
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithSamePreferredParent(AmbariSwaggerReaderTest.java:121)
[ERROR]
swaggerConflictingNestedApisWithBadPreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0.003 s <<< ERROR!
java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlRootElement
at
[jira] [Updated] (AMBARI-24751) Cover helpers views
[ https://issues.apache.org/jira/browse/AMBARI-24751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24751: Labels: pull-request-available (was: ) > Cover helpers views > --- > > Key: AMBARI-24751 > URL: https://issues.apache.org/jira/browse/AMBARI-24751 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24751) Cover helpers views
[ https://issues.apache.org/jira/browse/AMBARI-24751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24751: Assignee: Antonenko Alexander > Cover helpers views > --- > > Key: AMBARI-24751 > URL: https://issues.apache.org/jira/browse/AMBARI-24751 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24751) Cover helpers views
Antonenko Alexander created AMBARI-24751: Summary: Cover helpers views Key: AMBARI-24751 URL: https://issues.apache.org/jira/browse/AMBARI-24751 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Antonenko Alexander -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24750) HTTP 500 internal server error caused by NPE when trying to set loglevel in logsearch
[
https://issues.apache.org/jira/browse/AMBARI-24750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643162#comment-16643162
]
Péter Gergő Barna commented on AMBARI-24750:
[https://github.com/apache/ambari/pull/2432]
> HTTP 500 internal server error caused by NPE when trying to set loglevel in
> logsearch
> -
>
> Key: AMBARI-24750
> URL: https://issues.apache.org/jira/browse/AMBARI-24750
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
>Affects Versions: 2.7.1
>Reporter: Péter Gergő Barna
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This request sometimes returns HTTP 500 internal server error:
>
> {noformat}
> curl -vv -X PUT --header 'Content-Type: application/json' --header 'Accept:
> application/json' --header 'Authorization: Basic YWRtaW46YWRtaW4=' -d
> '{"filter":{"storm_worker_event":{"hosts":[],"defaultLevels":["FATAL","ERROR","WARN","INFO","DEBUG","TRACE","UNKNOWN"],"expiryTime":null,"label":"storm_worker_event","overrideLevels":[]}}}'
>
> 'http://my.host:61888/api/v1/shipper/filters/streamline-181008-150631-i7y-1/level'{noformat}
>
> a corresponding entry appears in this log
> ambari-logsearch-portal/logsearch.json:
>
>
> {noformat}
> {"level":"WARN","file":"ShipperConfigManager.java","thread_name":"qtp1188445627-1735","line_number":142,"logger_name":"org.apache.ambari.logsearch.manager.ShipperConfigManager","logtime":"1539020343816","log_message":"Could
> not update log level filters java.lang.NullPointerException at
> org.apache.ambari.logsearch.config.zookeeper.LogLevelFilterManagerZK.setLogLevelFilters(LogLevelFilterManagerZK.java:86)
> at
> org.apache.ambari.logsearch.manager.ShipperConfigManager.setLogLevelFilters(ShipperConfigManager.java:138)
> at
> org.apache.ambari.logsearch.rest.ShipperConfigResource.setLogLevelFilter(ShipperConfigResource.java:122)
> 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
> org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
> at
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
> at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at
> org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at
> org.glassfish.jersey.internal.Errors.process(Errors.java:315) at
> org.glassfish.jersey.internal.Errors.process(Errors.java:297) at
> org.glassfish.jersey.internal.Errors.process(Errors.java:267) at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
> at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
> at
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
> at
> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)
> at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
> at
> org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:215)
> at
>
[jira] [Updated] (AMBARI-24750) HTTP 500 internal server error caused by NPE when trying to set loglevel in logsearch
[
https://issues.apache.org/jira/browse/AMBARI-24750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24750:
Labels: pull-request-available (was: )
> HTTP 500 internal server error caused by NPE when trying to set loglevel in
> logsearch
> -
>
> Key: AMBARI-24750
> URL: https://issues.apache.org/jira/browse/AMBARI-24750
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
>Affects Versions: 2.7.1
>Reporter: Péter Gergő Barna
>Priority: Major
> Labels: pull-request-available
>
> This request sometimes returns HTTP 500 internal server error:
>
> {noformat}
> curl -vv -X PUT --header 'Content-Type: application/json' --header 'Accept:
> application/json' --header 'Authorization: Basic YWRtaW46YWRtaW4=' -d
> '{"filter":{"storm_worker_event":{"hosts":[],"defaultLevels":["FATAL","ERROR","WARN","INFO","DEBUG","TRACE","UNKNOWN"],"expiryTime":null,"label":"storm_worker_event","overrideLevels":[]}}}'
>
> 'http://my.host:61888/api/v1/shipper/filters/streamline-181008-150631-i7y-1/level'{noformat}
>
> a corresponding entry appears in this log
> ambari-logsearch-portal/logsearch.json:
>
>
> {noformat}
> {"level":"WARN","file":"ShipperConfigManager.java","thread_name":"qtp1188445627-1735","line_number":142,"logger_name":"org.apache.ambari.logsearch.manager.ShipperConfigManager","logtime":"1539020343816","log_message":"Could
> not update log level filters java.lang.NullPointerException at
> org.apache.ambari.logsearch.config.zookeeper.LogLevelFilterManagerZK.setLogLevelFilters(LogLevelFilterManagerZK.java:86)
> at
> org.apache.ambari.logsearch.manager.ShipperConfigManager.setLogLevelFilters(ShipperConfigManager.java:138)
> at
> org.apache.ambari.logsearch.rest.ShipperConfigResource.setLogLevelFilter(ShipperConfigResource.java:122)
> 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
> org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
> at
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
> at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at
> org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at
> org.glassfish.jersey.internal.Errors.process(Errors.java:315) at
> org.glassfish.jersey.internal.Errors.process(Errors.java:297) at
> org.glassfish.jersey.internal.Errors.process(Errors.java:267) at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
> at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
> at
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
> at
> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)
> at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
> at
> org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:215)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
> at
>
[jira] [Created] (AMBARI-24750) HTTP 500 internal server error caused by NPE when trying to set loglevel in logsearch
Péter Gergő Barna created AMBARI-24750:
--
Summary: HTTP 500 internal server error caused by NPE when trying
to set loglevel in logsearch
Key: AMBARI-24750
URL: https://issues.apache.org/jira/browse/AMBARI-24750
Project: Ambari
Issue Type: Bug
Components: logsearch
Affects Versions: 2.7.1
Reporter: Péter Gergő Barna
This request sometimes returns HTTP 500 internal server error:
{noformat}
curl -vv -X PUT --header 'Content-Type: application/json' --header 'Accept:
application/json' --header 'Authorization: Basic YWRtaW46YWRtaW4=' -d
'{"filter":{"storm_worker_event":{"hosts":[],"defaultLevels":["FATAL","ERROR","WARN","INFO","DEBUG","TRACE","UNKNOWN"],"expiryTime":null,"label":"storm_worker_event","overrideLevels":[]}}}'
'http://my.host:61888/api/v1/shipper/filters/streamline-181008-150631-i7y-1/level'{noformat}
a corresponding entry appears in this log
ambari-logsearch-portal/logsearch.json:
{noformat}
{"level":"WARN","file":"ShipperConfigManager.java","thread_name":"qtp1188445627-1735","line_number":142,"logger_name":"org.apache.ambari.logsearch.manager.ShipperConfigManager","logtime":"1539020343816","log_message":"Could
not update log level filters java.lang.NullPointerException at
org.apache.ambari.logsearch.config.zookeeper.LogLevelFilterManagerZK.setLogLevelFilters(LogLevelFilterManagerZK.java:86)
at
org.apache.ambari.logsearch.manager.ShipperConfigManager.setLogLevelFilters(ShipperConfigManager.java:138)
at
org.apache.ambari.logsearch.rest.ShipperConfigResource.setLogLevelFilter(ShipperConfigResource.java:122)
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
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
at
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326) at
org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at
org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at
org.glassfish.jersey.internal.Errors.process(Errors.java:315) at
org.glassfish.jersey.internal.Errors.process(Errors.java:297) at
org.glassfish.jersey.internal.Errors.process(Errors.java:267) at
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
at
org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
at
org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) at
org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
at
org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:215)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
at
org.springframework.boot.web.filter.ApplicationContextHeaderFilter.doFilterInternal(ApplicationContextHeaderFilter.java:55)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
at
org.apache.ambari.logsearch.web.filters.LogSearchLogLevelFilterManagerFilter.doFilter(LogSearchLogLevelFilterManagerFilter.java:79)
at
