[jira] [Updated] (AMBARI-24283) DB consistency warning due to config group without service name
[
https://issues.apache.org/jira/browse/AMBARI-24283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krisztian Kasa updated AMBARI-24283:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> DB consistency warning due to config group without service name
> ---
>
> Key: AMBARI-24283
> URL: https://issues.apache.org/jira/browse/AMBARI-24283
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Doroszlai, Attila
>Assignee: Krisztian Kasa
>Priority: Minor
> Labels: pull-request-available
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> STR:
> 1. Deploy ZooKeeper with Ambari 2.5.2
> 2. Create config group on UI
> 3. Upgrade to Ambari 2.6.x
> {noformat}
> group_id | group_name |tag| service_name
> --++---+--
> 3 | asdf | ZOOKEEPER |
> {noformat}
> Result: DB consistency check during startup after the upgrade produces false
> positive warning about the config group
> {noformat}
> WARN - You have config groups present in the database with no corresponding
> service found, [(ConfigGroup, Service) => ( asdf, null )]. Run
> --auto-fix-database to fix this automatically.
> {noformat}
> Following the instructions ({{--auto-fix-database}}) leads to deleting the
> config group.
> This check was added for the case where the service the config group belongs
> to was deleted from the cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24386) [Log Search] Input config validator unable to parse any log entry
[
https://issues.apache.org/jira/browse/AMBARI-24386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krisztian Kasa updated AMBARI-24386:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> [Log Search] Input config validator unable to parse any log entry
> -
>
> Key: AMBARI-24386
> URL: https://issues.apache.org/jira/browse/AMBARI-24386
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
>Affects Versions: 2.7.1
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> 1. Login to Logsearch portal
> 2. Select "Configuration Editor" from the right upper corner menu
> 3. Select an input config from "All Configuration" (ambari)
> 4. Enter a "Component Name" on the "Validator" section (ambari_agent)
> 5. Enter a log entry to the "Sample Data" text area
> {code}
> INFO 2018-07-31 06:14:06,550 security.py:67 - SSL connection established.
> Two-way SSL authentication is turned off on the server.
> {code}
> 6. Click "Test"
> 7. The result is the configuration is not valid
> Validator throws java.lang.NullPointerException
> {code}
> /var/log/ambari-logsearch-portal/logsearch.log
> {code}
> {code}
> 2018-07-31 06:27:54,674 [qtp1933799970-15] ERROR
> apache.ambari.logfeeder.plugin.input.Input (Input.java:193) - Error during
> filter apply: {}
> java.lang.NullPointerException
> at
> org.apache.ambari.logfeeder.output.OutputManagerImpl.getDefaultLogLevels(OutputManagerImpl.java:165)
> at
> org.apache.ambari.logfeeder.output.OutputManagerImpl.write(OutputManagerImpl.java:147)
> at
> org.apache.ambari.logfeeder.plugin.filter.Filter.apply(Filter.java:121)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.applyMessage(FilterGrok.java:278)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.apply(FilterGrok.java:206)
> at
> org.apache.ambari.logfeeder.plugin.input.Input.outputLine(Input.java:191)
> at
> org.apache.ambari.logfeeder.common.LogEntryParseTester.parse(LogEntryParseTester.java:136)
> at
> org.apache.ambari.logsearch.manager.ShipperConfigManager.testShipperConfig(ShipperConfigManager.java:113)
> at
> org.apache.ambari.logsearch.rest.ShipperConfigResource.testShipperConfig(ShipperConfigResource.java:105)
> 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
>
[jira] [Commented] (AMBARI-24283) DB consistency warning due to config group without service name
[
https://issues.apache.org/jira/browse/AMBARI-24283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564776#comment-16564776
]
Hudson commented on AMBARI-24283:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #94 (See
[https://builds.apache.org/job/Ambari-branch-2.7/94/])
AMBARI-24283 - DB consistency warning due to config group without (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1c25b1019b8eaa6b03882ae4ee7bdd99b9ae1d5d])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog271.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog271Test.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelperTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
> DB consistency warning due to config group without service name
> ---
>
> Key: AMBARI-24283
> URL: https://issues.apache.org/jira/browse/AMBARI-24283
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Doroszlai, Attila
>Assignee: Krisztian Kasa
>Priority: Minor
> Labels: pull-request-available
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> STR:
> 1. Deploy ZooKeeper with Ambari 2.5.2
> 2. Create config group on UI
> 3. Upgrade to Ambari 2.6.x
> {noformat}
> group_id | group_name |tag| service_name
> --++---+--
> 3 | asdf | ZOOKEEPER |
> {noformat}
> Result: DB consistency check during startup after the upgrade produces false
> positive warning about the config group
> {noformat}
> WARN - You have config groups present in the database with no corresponding
> service found, [(ConfigGroup, Service) => ( asdf, null )]. Run
> --auto-fix-database to fix this automatically.
> {noformat}
> Following the instructions ({{--auto-fix-database}}) leads to deleting the
> config group.
> This check was added for the case where the service the config group belongs
> to was deleted from the cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24389) Update Ambari Single Sign-on Configuration documentation to include Kerberos options
[ https://issues.apache.org/jira/browse/AMBARI-24389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-24389: -- Status: Patch Available (was: In Progress) > Update Ambari Single Sign-on Configuration documentation to include Kerberos > options > > > Key: AMBARI-24389 > URL: https://issues.apache.org/jira/browse/AMBARI-24389 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Critical > Labels: documentation, pull-request-available > Fix For: 2.7.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Update Ambari Single Sign-on Configuration documentation to include Kerberos > options. > See > https://github.com/apache/ambari/blob/branch-2.7/ambari-server/docs/security/sso/index.md. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24389) Update Ambari Single Sign-on Configuration documentation to include Kerberos options
[ https://issues.apache.org/jira/browse/AMBARI-24389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24389: Labels: documentation pull-request-available (was: documentation) > Update Ambari Single Sign-on Configuration documentation to include Kerberos > options > > > Key: AMBARI-24389 > URL: https://issues.apache.org/jira/browse/AMBARI-24389 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Critical > Labels: documentation, pull-request-available > Fix For: 2.7.1 > > > Update Ambari Single Sign-on Configuration documentation to include Kerberos > options. > See > https://github.com/apache/ambari/blob/branch-2.7/ambari-server/docs/security/sso/index.md. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24392) Align the entries in drop downs of Ambari UI left hand side pane
[ https://issues.apache.org/jira/browse/AMBARI-24392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564405#comment-16564405 ] Hudson commented on AMBARI-24392: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9708 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9708/]) AMBARI-24392. Align the entries in drop downs of Ambari UI left hand (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=aaebbe8c528667e70219545582dfddbe36fe6b9e]) * (edit) ambari-web/app/styles/bootstrap_overrides.less > Align the entries in drop downs of Ambari UI left hand side pane > > > Key: AMBARI-24392 > URL: https://issues.apache.org/jira/browse/AMBARI-24392 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: Cluster-Admin.png, Services.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > See !Cluster-Admin.png! - it would be good to right align the entries in > the drop down > The Service pane looks better !Services.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24391) Properties filter in Customize Services Page brings up LOGDIRS and PIDDIRS even if they dont qualify
[ https://issues.apache.org/jira/browse/AMBARI-24391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564404#comment-16564404 ] Hudson commented on AMBARI-24391: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9708 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9708/]) AMBARI-24391. Properties filter in Customize Services Page brings up (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=731f7bfdb5d1fcc8e84defec41af0f6fc6bd11d7]) * (edit) ambari-web/app/templates/wizard/step7/directories_theme_layout.hbs > Properties filter in Customize Services Page brings up LOGDIRS and PIDDIRS > even if they dont qualify > > > Key: AMBARI-24391 > URL: https://issues.apache.org/jira/browse/AMBARI-24391 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > - At customize services page - Directories tab - use properties filter to > show 'Property issues' and 'Final properties'. In both cases LOGDIR and > PIDDIR shows up as show in screenshot. There is no property in that panel but > they do show up -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24383) A NPE occurs if a Kerberos identity descriptor is missing a Keytab specification
[
https://issues.apache.org/jira/browse/AMBARI-24383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564361#comment-16564361
]
Hudson commented on AMBARI-24383:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9707 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9707/])
AMBARI-24383. A NPE occurs if a Kerberos identity descriptor is missing
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=4348275a08d036a9b1cded285b685ae6e4ee7c3c])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
> A NPE occurs if a Kerberos identity descriptor is missing a Keytab
> specification
>
>
> Key: AMBARI-24383
> URL: https://issues.apache.org/jira/browse/AMBARI-24383
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Denis Tarasyuk
>Assignee: Dmitry Lysnichenko
>Priority: Major
> Labels: kerberos, pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> A NPE occurs if a Kerberos identity descriptor is missing a Keytab
> specification. For example, if the Kerberos identity descriptor is as
> follows:
> {code}
> {
> "name": "druid",
> "principal": {
> "value": "druid_124@${realm}",
> "type": "user"
> }
> }
> {code}
> {noformat:title=Log Message}
> 2018-07-30 12:58:33,332 WARN [Server Action Executor Worker 265]
> ServerActionExecutor:471 - Task #265 failed to complete execution due to
> thrown exception: java.lang.NullPointerException:null
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.addIdentities(KerberosHelperImpl.java:1603)
> at
> org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponents(AbstractPrepareKerberosServerAction.java:168)
> at
> org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponentHosts(AbstractPrepareKerberosServerAction.java:94)
> at
> org.apache.ambari.server.serveraction.kerberos.PrepareKerberosIdentitiesServerAction.execute(PrepareKerberosIdentitiesServerAction.java:129)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> *Note*: This is technically an unexpected Kerberos identity specification
> since the identity will be unusable. However Ambari should not encounter a
> NPE because of it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24391) Properties filter in Customize Services Page brings up LOGDIRS and PIDDIRS even if they dont qualify
[ https://issues.apache.org/jira/browse/AMBARI-24391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24391. -- Resolution: Fixed > Properties filter in Customize Services Page brings up LOGDIRS and PIDDIRS > even if they dont qualify > > > Key: AMBARI-24391 > URL: https://issues.apache.org/jira/browse/AMBARI-24391 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > - At customize services page - Directories tab - use properties filter to > show 'Property issues' and 'Final properties'. In both cases LOGDIR and > PIDDIR shows up as show in screenshot. There is no property in that panel but > they do show up -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24392) Align the entries in drop downs of Ambari UI left hand side pane
[ https://issues.apache.org/jira/browse/AMBARI-24392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24392. -- Resolution: Fixed > Align the entries in drop downs of Ambari UI left hand side pane > > > Key: AMBARI-24392 > URL: https://issues.apache.org/jira/browse/AMBARI-24392 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: Cluster-Admin.png, Services.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > See !Cluster-Admin.png! - it would be good to right align the entries in > the drop down > The Service pane looks better !Services.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24396) Service theme call failing
[ https://issues.apache.org/jira/browse/AMBARI-24396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24396: Labels: pull-request-available (was: ) > Service theme call failing > -- > > Key: AMBARI-24396 > URL: https://issues.apache.org/jira/browse/AMBARI-24396 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > pon clicking service summary page themes call is failing. > ../api/v1/stacks/ODS/versions/1.0.0-b483/services/ZOOKEEPER/themes?ThemeInfo/default=true > for ODS mpack zookeeper is being checked for theme info which is incorrect -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24396) Service theme call failing
Ishan Bhatt created AMBARI-24396: Summary: Service theme call failing Key: AMBARI-24396 URL: https://issues.apache.org/jira/browse/AMBARI-24396 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 3.0.0 pon clicking service summary page themes call is failing. ../api/v1/stacks/ODS/versions/1.0.0-b483/services/ZOOKEEPER/themes?ThemeInfo/default=true for ODS mpack zookeeper is being checked for theme info which is incorrect -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24395) Upgrade AMS hadoop dependency build number to the latest.
[ https://issues.apache.org/jira/browse/AMBARI-24395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564232#comment-16564232 ] Hudson commented on AMBARI-24395: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9706 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9706/]) AMBARI-24395 : Upgrade AMS hadoop dependency build number to the latest. (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=23a87a2092afdb01367f88add11ed0dc1a5327f6]) * (edit) ambari-metrics/ambari-metrics-timelineservice/pom.xml * (edit) ambari-metrics/pom.xml > Upgrade AMS hadoop dependency build number to the latest. > - > > Key: AMBARI-24395 > URL: https://issues.apache.org/jira/browse/AMBARI-24395 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Labels: pull-request-available > Fix For: trunk, 2.7.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24395) Upgrade AMS hadoop dependency build number to the latest.
[ https://issues.apache.org/jira/browse/AMBARI-24395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564138#comment-16564138 ] Hudson commented on AMBARI-24395: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #93 (See [https://builds.apache.org/job/Ambari-branch-2.7/93/]) AMBARI-24395 : Upgrade AMS hadoop dependency build number to the latest. (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1b01587292560419d11deb9a69fb2d5162f86635]) * (edit) ambari-metrics/ambari-metrics-timelineservice/pom.xml * (edit) ambari-metrics/pom.xml > Upgrade AMS hadoop dependency build number to the latest. > - > > Key: AMBARI-24395 > URL: https://issues.apache.org/jira/browse/AMBARI-24395 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Labels: pull-request-available > Fix For: trunk, 2.7.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24395) Upgrade AMS hadoop dependency build number to the latest.
[ https://issues.apache.org/jira/browse/AMBARI-24395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24395. Resolution: Fixed Pushed to both the branches. > Upgrade AMS hadoop dependency build number to the latest. > - > > Key: AMBARI-24395 > URL: https://issues.apache.org/jira/browse/AMBARI-24395 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Labels: pull-request-available > Fix For: trunk, 2.7.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-24393) Ambari Config Group - allow override of GUI main settings
[ https://issues.apache.org/jira/browse/AMBARI-24393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563852#comment-16563852 ] Hari Sekhon edited comment on AMBARI-24393 at 7/31/18 5:03 PM: --- Actually please ignore, I was being too hasty reacting to an event at work, it does allow this via the plus symbol that appears if you hover over a setting. was (Author: harisekhon): Actually please ignore, I was being too hasty reacting to an event at work, it does allow this via the plus symbol next to the setting. > Ambari Config Group - allow override of GUI main settings > - > > Key: AMBARI-24393 > URL: https://issues.apache.org/jira/browse/AMBARI-24393 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Hari Sekhon >Priority: Major > > When using Ambari config groups, and selecting the config group from the drop > down above to do an override, it greys out all the main settings on the > Config -> Settings page for HBase and does not allow overriding the sliders, > for example for Number of Handlers per RegionServer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24395) Upgrade AMS hadoop dependency build number to the latest.
[ https://issues.apache.org/jira/browse/AMBARI-24395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24395: Labels: pull-request-available (was: ) > Upgrade AMS hadoop dependency build number to the latest. > - > > Key: AMBARI-24395 > URL: https://issues.apache.org/jira/browse/AMBARI-24395 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Labels: pull-request-available > Fix For: trunk, 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-24393) Ambari Config Group - allow override of GUI main settings
[ https://issues.apache.org/jira/browse/AMBARI-24393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563852#comment-16563852 ] Hari Sekhon edited comment on AMBARI-24393 at 7/31/18 5:01 PM: --- Actually please ignore, I was being too hasty reacting to an event at work, it does allow this via the plus symbol next to the setting. was (Author: harisekhon): Actually I was dealing with this too quickly, it does allow this via the plus symbol next to the setting, please ignore. > Ambari Config Group - allow override of GUI main settings > - > > Key: AMBARI-24393 > URL: https://issues.apache.org/jira/browse/AMBARI-24393 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Hari Sekhon >Priority: Major > > When using Ambari config groups, and selecting the config group from the drop > down above to do an override, it greys out all the main settings on the > Config -> Settings page for HBase and does not allow overriding the sliders, > for example for Number of Handlers per RegionServer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24395) Upgrade AMS hadoop dependency build number to the latest.
Aravindan Vijayan created AMBARI-24395: -- Summary: Upgrade AMS hadoop dependency build number to the latest. Key: AMBARI-24395 URL: https://issues.apache.org/jira/browse/AMBARI-24395 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.1 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: trunk, 2.7.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24394) Ambari Revision Control across Config Groups - show all changes across all Config Groups
Hari Sekhon created AMBARI-24394: Summary: Ambari Revision Control across Config Groups - show all changes across all Config Groups Key: AMBARI-24394 URL: https://issues.apache.org/jira/browse/AMBARI-24394 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.5.2 Reporter: Hari Sekhon When using config groups and making changes to a config group, then selecting default, it doesn't show any configuration change because none was applied to default. This is not good because when reviewing the configs it looks like no change was made recently, only when selecting the other config group drop down does a newer revision change become visible in the version slider near the top of the config page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-24382) Ambari shouldn't deployed "Undefined" Config Values
[
https://issues.apache.org/jira/browse/AMBARI-24382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563846#comment-16563846
]
Hari Sekhon edited comment on AMBARI-24382 at 7/31/18 3:41 PM:
---
This keeps happening if any change is introduced at the default config group
level.
I've even tried moving the HMasters to their own sub-group not in default
config group, but the same thing happens, all values undefined for their group
are picked up and inserted with literal "Undefined" values.
was (Author: harisekhon):
This keeps happening if any change is introduced at the default config group
level.
I've even tried moving the HMasters to their own sub-group not in default
config group, but the same thing happens, all values undefined for their group
are picked up and inserted with literal "Undefined" values.
When combined with the limitation in AMBARI-24393, it means I cannot apply main
settings to HBase any more without completely breaking the HMasters
site-hbase.xml eg. I cannot change the handler count or anything else on the
main HBase Settings page.
> Ambari shouldn't deployed "Undefined" Config Values
> ---
>
> Key: AMBARI-24382
> URL: https://issues.apache.org/jira/browse/AMBARI-24382
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Hari Sekhon
>Priority: Blocker
>
> Ambari should not deploy any properties with "Undefined" value (breaks HBase
> Master as shown below).
> When using a config group for HBase RegionServers to only enable Bucket Cache
> on RegionServers (see AMBARI-24370), and then enabling a bunch of settings
> related to using the bucket cache in the default config, Ambari will infer
> that there should be a bucketcache setting and injects the following
> properties with a literal value of "Undefined" in hbase-site.xml:
> {code:java}
>
> hbase.bucketcache.ioengine
> Undefined
>
>
> hbase.bucketcache.size
> Undefined
> {code}
> which breaks HMaster restart:
> {code:java}
> 2018-07-30 13:26:08,283 ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Failed construction of Master: class
> org.apache.hadoop.hbase.master.HMaster
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2824)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:235)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
> at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2838)
> Caused by: java.lang.NumberFormatException: For input string: "Undefined"
> at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2043)
> at sun.misc.FloatingDecimal.parseFloat(FloatingDecimal.java:122)
> at java.lang.Float.parseFloat(Float.java:451)
> at org.apache.hadoop.conf.Configuration.getFloat(Configuration.java:1400)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.getBucketCache(CacheConfig.java:597)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.getL2(CacheConfig.java:566)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.instantiateBlockCache(CacheConfig.java:650)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.(CacheConfig.java:239)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:591)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:425)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2819)
> ... 5 more
> {code}
> The above two settings are only added to a config group RegionServers, but
> when the following settings are applied to the default config group thinking
> they should be ignored by Masters because bucket cache isn't enabled on
> Master, it turns out that Ambari infers they should exist, leaves them
> Undefined but deploys them anyway (these settings are from the OpenTSDB HBase
> performance tuning guide btw):
> {code:java}
> hbase.rs.cacheblocksonwrite=true
> hbase.rs.evictblocksonclose=false
> hfile.block.bloom.cacheonwrite=true
> hfile.block.index.cacheonwrite=true
> hbase.block.data.cachecompressed=true
> hbase.bucketcache.blockcache.single.percentage=.99
> hbase.bucketcache.blockcache.multi.percentage=0
> hbase.bucketcache.blockcache.memory.percentage=.01
> {code}
> I've worked around
[jira] [Resolved] (AMBARI-24393) Ambari Config Group - allow override of GUI main settings
[ https://issues.apache.org/jira/browse/AMBARI-24393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon resolved AMBARI-24393. -- Resolution: Invalid Actually I was dealing with this too quickly, it does allow this via the plus symbol next to the setting, please ignore. > Ambari Config Group - allow override of GUI main settings > - > > Key: AMBARI-24393 > URL: https://issues.apache.org/jira/browse/AMBARI-24393 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Hari Sekhon >Priority: Blocker > > When using Ambari config groups, and selecting the config group from the drop > down above to do an override, it greys out all the main settings on the > Config -> Settings page for HBase and does not allow overriding the sliders, > for example for Number of Handlers per RegionServer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24393) Ambari Config Group - allow override of GUI main settings
[ https://issues.apache.org/jira/browse/AMBARI-24393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-24393: - Priority: Major (was: Blocker) > Ambari Config Group - allow override of GUI main settings > - > > Key: AMBARI-24393 > URL: https://issues.apache.org/jira/browse/AMBARI-24393 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Hari Sekhon >Priority: Major > > When using Ambari config groups, and selecting the config group from the drop > down above to do an override, it greys out all the main settings on the > Config -> Settings page for HBase and does not allow overriding the sliders, > for example for Number of Handlers per RegionServer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-24382) Ambari shouldn't deployed "Undefined" Config Values
[
https://issues.apache.org/jira/browse/AMBARI-24382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563846#comment-16563846
]
Hari Sekhon edited comment on AMBARI-24382 at 7/31/18 3:38 PM:
---
This keeps happening if any change is introduced at the default config group
level.
I've even tried moving the HMasters to their own sub-group not in default
config group, but the same thing happens, all values undefined for their group
are picked up and inserted with literal "Undefined" values.
When combined with the limitation in AMBARI-24393, it means I cannot apply main
settings to HBase any more without completely breaking the HMasters
site-hbase.xml eg. I cannot change the handler count or anything else on the
main HBase Settings page.
was (Author: harisekhon):
This keeps happening if any change is introduced at the default config group
level.
I've even tried moving the HMasters to their own sub-group not in default
config group, but the same thing happens, all values undefined for their group
are picked up and inserted with literal "Undefined" values.
> Ambari shouldn't deployed "Undefined" Config Values
> ---
>
> Key: AMBARI-24382
> URL: https://issues.apache.org/jira/browse/AMBARI-24382
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Hari Sekhon
>Priority: Critical
>
> Ambari should not deploy any properties with "Undefined" value (breaks HBase
> Master as shown below).
> When using a config group for HBase RegionServers to only enable Bucket Cache
> on RegionServers (see AMBARI-24370), and then enabling a bunch of settings
> related to using the bucket cache in the default config, Ambari will infer
> that there should be a bucketcache setting and injects the following
> properties with a literal value of "Undefined" in hbase-site.xml:
> {code:java}
>
> hbase.bucketcache.ioengine
> Undefined
>
>
> hbase.bucketcache.size
> Undefined
> {code}
> which breaks HMaster restart:
> {code:java}
> 2018-07-30 13:26:08,283 ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Failed construction of Master: class
> org.apache.hadoop.hbase.master.HMaster
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2824)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:235)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
> at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2838)
> Caused by: java.lang.NumberFormatException: For input string: "Undefined"
> at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2043)
> at sun.misc.FloatingDecimal.parseFloat(FloatingDecimal.java:122)
> at java.lang.Float.parseFloat(Float.java:451)
> at org.apache.hadoop.conf.Configuration.getFloat(Configuration.java:1400)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.getBucketCache(CacheConfig.java:597)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.getL2(CacheConfig.java:566)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.instantiateBlockCache(CacheConfig.java:650)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.(CacheConfig.java:239)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:591)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:425)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2819)
> ... 5 more
> {code}
> The above two settings are only added to a config group RegionServers, but
> when the following settings are applied to the default config group thinking
> they should be ignored by Masters because bucket cache isn't enabled on
> Master, it turns out that Ambari infers they should exist, leaves them
> Undefined but deploys them anyway (these settings are from the OpenTSDB HBase
> performance tuning guide btw):
> {code:java}
> hbase.rs.cacheblocksonwrite=true
> hbase.rs.evictblocksonclose=false
> hfile.block.bloom.cacheonwrite=true
> hfile.block.index.cacheonwrite=true
> hbase.block.data.cachecompressed=true
> hbase.bucketcache.blockcache.single.percentage=.99
> hbase.bucketcache.blockcache.multi.percentage=0
> hbase.bucketcache.blockcache.memory.percentage=.01
> {code}
> I've worked around
[jira] [Updated] (AMBARI-24382) Ambari shouldn't deployed "Undefined" Config Values
[
https://issues.apache.org/jira/browse/AMBARI-24382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated AMBARI-24382:
-
Priority: Blocker (was: Critical)
> Ambari shouldn't deployed "Undefined" Config Values
> ---
>
> Key: AMBARI-24382
> URL: https://issues.apache.org/jira/browse/AMBARI-24382
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Hari Sekhon
>Priority: Blocker
>
> Ambari should not deploy any properties with "Undefined" value (breaks HBase
> Master as shown below).
> When using a config group for HBase RegionServers to only enable Bucket Cache
> on RegionServers (see AMBARI-24370), and then enabling a bunch of settings
> related to using the bucket cache in the default config, Ambari will infer
> that there should be a bucketcache setting and injects the following
> properties with a literal value of "Undefined" in hbase-site.xml:
> {code:java}
>
> hbase.bucketcache.ioengine
> Undefined
>
>
> hbase.bucketcache.size
> Undefined
> {code}
> which breaks HMaster restart:
> {code:java}
> 2018-07-30 13:26:08,283 ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Failed construction of Master: class
> org.apache.hadoop.hbase.master.HMaster
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2824)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:235)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
> at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2838)
> Caused by: java.lang.NumberFormatException: For input string: "Undefined"
> at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2043)
> at sun.misc.FloatingDecimal.parseFloat(FloatingDecimal.java:122)
> at java.lang.Float.parseFloat(Float.java:451)
> at org.apache.hadoop.conf.Configuration.getFloat(Configuration.java:1400)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.getBucketCache(CacheConfig.java:597)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.getL2(CacheConfig.java:566)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.instantiateBlockCache(CacheConfig.java:650)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.(CacheConfig.java:239)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:591)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:425)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2819)
> ... 5 more
> {code}
> The above two settings are only added to a config group RegionServers, but
> when the following settings are applied to the default config group thinking
> they should be ignored by Masters because bucket cache isn't enabled on
> Master, it turns out that Ambari infers they should exist, leaves them
> Undefined but deploys them anyway (these settings are from the OpenTSDB HBase
> performance tuning guide btw):
> {code:java}
> hbase.rs.cacheblocksonwrite=true
> hbase.rs.evictblocksonclose=false
> hfile.block.bloom.cacheonwrite=true
> hfile.block.index.cacheonwrite=true
> hbase.block.data.cachecompressed=true
> hbase.bucketcache.blockcache.single.percentage=.99
> hbase.bucketcache.blockcache.multi.percentage=0
> hbase.bucketcache.blockcache.memory.percentage=.01
> {code}
> I've worked around it by moving the config to the regionservers config group,
> but ran in to AMBARI-24371 again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24393) Ambari Config Group - allow override of GUI main settings
[ https://issues.apache.org/jira/browse/AMBARI-24393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-24393: - Priority: Blocker (was: Major) > Ambari Config Group - allow override of GUI main settings > - > > Key: AMBARI-24393 > URL: https://issues.apache.org/jira/browse/AMBARI-24393 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Hari Sekhon >Priority: Blocker > > When using Ambari config groups, and selecting the config group from the drop > down above to do an override, it greys out all the main settings on the > Config -> Settings page for HBase and does not allow overriding the sliders, > for example for Number of Handlers per RegionServer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24382) Ambari shouldn't deployed "Undefined" Config Values
[
https://issues.apache.org/jira/browse/AMBARI-24382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563846#comment-16563846
]
Hari Sekhon commented on AMBARI-24382:
--
This keeps happening if any change is introduced at the default config group
level.
I've even tried moving the HMasters to their own sub-group not in default
config group, but the same thing happens, all values undefined for their group
are picked up and inserted with literal "Undefined" values.
> Ambari shouldn't deployed "Undefined" Config Values
> ---
>
> Key: AMBARI-24382
> URL: https://issues.apache.org/jira/browse/AMBARI-24382
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Hari Sekhon
>Priority: Critical
>
> Ambari should not deploy any properties with "Undefined" value (breaks HBase
> Master as shown below).
> When using a config group for HBase RegionServers to only enable Bucket Cache
> on RegionServers (see AMBARI-24370), and then enabling a bunch of settings
> related to using the bucket cache in the default config, Ambari will infer
> that there should be a bucketcache setting and injects the following
> properties with a literal value of "Undefined" in hbase-site.xml:
> {code:java}
>
> hbase.bucketcache.ioengine
> Undefined
>
>
> hbase.bucketcache.size
> Undefined
> {code}
> which breaks HMaster restart:
> {code:java}
> 2018-07-30 13:26:08,283 ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Failed construction of Master: class
> org.apache.hadoop.hbase.master.HMaster
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2824)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:235)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
> at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2838)
> Caused by: java.lang.NumberFormatException: For input string: "Undefined"
> at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2043)
> at sun.misc.FloatingDecimal.parseFloat(FloatingDecimal.java:122)
> at java.lang.Float.parseFloat(Float.java:451)
> at org.apache.hadoop.conf.Configuration.getFloat(Configuration.java:1400)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.getBucketCache(CacheConfig.java:597)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.getL2(CacheConfig.java:566)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.instantiateBlockCache(CacheConfig.java:650)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.(CacheConfig.java:239)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:591)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:425)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2819)
> ... 5 more
> {code}
> The above two settings are only added to a config group RegionServers, but
> when the following settings are applied to the default config group thinking
> they should be ignored by Masters because bucket cache isn't enabled on
> Master, it turns out that Ambari infers they should exist, leaves them
> Undefined but deploys them anyway (these settings are from the OpenTSDB HBase
> performance tuning guide btw):
> {code:java}
> hbase.rs.cacheblocksonwrite=true
> hbase.rs.evictblocksonclose=false
> hfile.block.bloom.cacheonwrite=true
> hfile.block.index.cacheonwrite=true
> hbase.block.data.cachecompressed=true
> hbase.bucketcache.blockcache.single.percentage=.99
> hbase.bucketcache.blockcache.multi.percentage=0
> hbase.bucketcache.blockcache.memory.percentage=.01
> {code}
> I've worked around it by moving the config to the regionservers config group,
> but ran in to AMBARI-24371 again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24393) Ambari Config Group - allow override of GUI main settings
Hari Sekhon created AMBARI-24393: Summary: Ambari Config Group - allow override of GUI main settings Key: AMBARI-24393 URL: https://issues.apache.org/jira/browse/AMBARI-24393 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.5.2 Reporter: Hari Sekhon When using Ambari config groups, and selecting the config group from the drop down above to do an override, it greys out all the main settings on the Config -> Settings page for HBase and does not allow overriding the sliders, for example for Number of Handlers per RegionServer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24326) Upgrade creates flume kerberos principal, after removing flume service
[ https://issues.apache.org/jira/browse/AMBARI-24326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563835#comment-16563835 ] Hudson commented on AMBARI-24326: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9705 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9705/]) AMBARI-24326. Upgrade creates flume kerberos principal, after removing (dlysnichenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=48c92cdf6acca316e6a88a3966915cb2a920fcb5]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/KerberosServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/stageutils/KerberosKeytabController.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/publishers/AgentCommandsPublisher.java AMBARI-24326. Upgrade creates flume kerberos principal, after removig (dlysnichenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=a091011d02211f74ba01247931ed9833446f9a1e]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/publishers/AgentCommandsPublisher.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/KerberosServerAction.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/kerberos/KerberosServerActionTest.java > Upgrade creates flume kerberos principal, after removing flume service > -- > > Key: AMBARI-24326 > URL: https://issues.apache.org/jira/browse/AMBARI-24326 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > HDP Upgrade appears to create an additional flume principal, after ambari > removes the service (as flume is no longer supported in hdp 3.0.0). This > requirement can be problematic for clusters integrated with kerberos using > manual management. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24388) Install HSI using Add HiveServer2 Interactive button failing
[ https://issues.apache.org/jira/browse/AMBARI-24388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563836#comment-16563836 ] Hudson commented on AMBARI-24388: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9705 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9705/]) AMBARI-24388. Install HSI using Add HiveServer2 Interactive button (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=2eaeeebefdff3b2d5da51ea2ca2cba3507dae771]) * (edit) ambari-web/app/mixins.js * (add) ambari-web/app/mixins/main/service/configs/hive_interactive_check.js * (edit) ambari-web/app/views/main/host/summary.js * (edit) ambari-web/app/views/main/service/item.js > Install HSI using Add HiveServer2 Interactive button failing > > > Key: AMBARI-24388 > URL: https://issues.apache.org/jira/browse/AMBARI-24388 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Hide 'Add hiveserver interactive' option if 'Enable Interactive Query ' is > disabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24391) Properties filter in Customize Services Page brings up LOGDIRS and PIDDIRS even if they dont qualify
[ https://issues.apache.org/jira/browse/AMBARI-24391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24391: Labels: pull-request-available (was: ) > Properties filter in Customize Services Page brings up LOGDIRS and PIDDIRS > even if they dont qualify > > > Key: AMBARI-24391 > URL: https://issues.apache.org/jira/browse/AMBARI-24391 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > > - At customize services page - Directories tab - use properties filter to > show 'Property issues' and 'Final properties'. In both cases LOGDIR and > PIDDIR shows up as show in screenshot. There is no property in that panel but > they do show up -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24392) Align the entries in drop downs of Ambari UI left hand side pane
[ https://issues.apache.org/jira/browse/AMBARI-24392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24392: Labels: pull-request-available (was: ) > Align the entries in drop downs of Ambari UI left hand side pane > > > Key: AMBARI-24392 > URL: https://issues.apache.org/jira/browse/AMBARI-24392 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: Cluster-Admin.png, Services.png > > > See !Cluster-Admin.png! - it would be good to right align the entries in > the drop down > The Service pane looks better !Services.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24392) Align the entries in drop downs of Ambari UI left hand side pane
[ https://issues.apache.org/jira/browse/AMBARI-24392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24392: - Description: See !Cluster-Admin.png! - it would be good to right align the entries in the drop down The Service pane looks better !Services.png! was: See !Cluster-Admin.png! - it would be good to right align the entries in the drop down The Service pane looks better !Services.png! cc - [~paul] > Align the entries in drop downs of Ambari UI left hand side pane > > > Key: AMBARI-24392 > URL: https://issues.apache.org/jira/browse/AMBARI-24392 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Fix For: 3.0.0 > > Attachments: Cluster-Admin.png, Services.png > > > See !Cluster-Admin.png! - it would be good to right align the entries in > the drop down > The Service pane looks better !Services.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24392) Align the entries in drop downs of Ambari UI left hand side pane
[ https://issues.apache.org/jira/browse/AMBARI-24392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24392: - Description: See !Cluster-Admin.png! - it would be good to right align the entries in the drop down The Service pane looks better !Services.png! cc - [~paul] was: See !Cluster-Admin.png|thumbnail! - it would be good to right align the entries in the drop down The Service pane looks better !Services.png|thumbnail! cc - [~paul] > Align the entries in drop downs of Ambari UI left hand side pane > > > Key: AMBARI-24392 > URL: https://issues.apache.org/jira/browse/AMBARI-24392 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Fix For: 3.0.0 > > Attachments: Cluster-Admin.png, Services.png > > > See !Cluster-Admin.png! - it would be good to right align the entries in > the drop down > The Service pane looks better !Services.png! > cc - [~paul] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24392) Align the entries in drop downs of Ambari UI left hand side pane
Aleksandr Kovalenko created AMBARI-24392: Summary: Align the entries in drop downs of Ambari UI left hand side pane Key: AMBARI-24392 URL: https://issues.apache.org/jira/browse/AMBARI-24392 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 Attachments: Cluster-Admin.png, Services.png See !Cluster-Admin.png|thumbnail! - it would be good to right align the entries in the drop down The Service pane looks better !Services.png|thumbnail! cc - [~paul] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24391) Properties filter in Customize Services Page brings up LOGDIRS and PIDDIRS even if they dont qualify
Aleksandr Kovalenko created AMBARI-24391: Summary: Properties filter in Customize Services Page brings up LOGDIRS and PIDDIRS even if they dont qualify Key: AMBARI-24391 URL: https://issues.apache.org/jira/browse/AMBARI-24391 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 - At customize services page - Directories tab - use properties filter to show 'Property issues' and 'Final properties'. In both cases LOGDIR and PIDDIR shows up as show in screenshot. There is no property in that panel but they do show up -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24390) Filter services eligible for Ambari Single Sign-on Configuration if Kerberos is required but not enabled
Robert Levas created AMBARI-24390:
-
Summary: Filter services eligible for Ambari Single Sign-on
Configuration if Kerberos is required but not enabled
Key: AMBARI-24390
URL: https://issues.apache.org/jira/browse/AMBARI-24390
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.1
Reporter: Robert Levas
Assignee: Attila Magyar
Fix For: 2.7.1
Filter services from Ambari CLI when setting up SSO if not eligible when
Kerberos is not enabled.
In Ambari 2.7, services that are eligible for Ambari to manage their SSO
configurations specify this in their metainfo file using like:
{code}
true
application-properties/atlas.sso.knox.enabled
{code}
See AMBARI-23253
See [Ambari Single Sign-on
Configuration|https://github.com/apache/ambari/blob/branch-2.7/ambari-server/docs/security/sso/index.md]
documentation
However some services require Kerberos to be enabled for SSO to work. For
example, HDFS, Yarn, and Oozie. For this case, the metadata is enhanced
allowing for the metadata to indicate whether Kerberos is required
(AMBARI-24335) and whether Kerberos is enabled (AMBARI-24384) for that service.
This information can be found in the service resource data
{code:title=GET /api/v1/clusters/CLUSTERNAME/services/OOZIE}
{
"href" : "http://ambari_host:8080/api/v1/clusters/CLUSTERNAME/services/OOZIE;,
"ServiceInfo" : {
...
"kerberos_enabled" : true,
...
"sso_integration_desired": false,
"sso_integration_enabled": false,
"sso_integration_requires_kerberos": true,
"sso_integration_supported": true,
...
},
...
}
{code}
Using this information, services may be included in or excluded from the list
of services a user can choose for enabling SSO integration.
For example
||sso_integration_supported||sso_integration_requires_kerberos||kerberos_enabled||Can
Enable SSO||
|true|true|true|yes
|true|true|false|no
|true|false|true|yes
|true|false|false|yes
|false|true|true|no
|false|true|false|no
|false|false|true|no
|false|false|false|no
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24283) DB consistency warning due to config group without service name
[
https://issues.apache.org/jira/browse/AMBARI-24283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563759#comment-16563759
]
Hudson commented on AMBARI-24283:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9704 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9704/])
AMBARI-24283 - DB consistency warning due to config group without (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=048b0d49b173d02cc0bad89135e3100b6e1df3f1])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelperTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog271.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog271Test.java
> DB consistency warning due to config group without service name
> ---
>
> Key: AMBARI-24283
> URL: https://issues.apache.org/jira/browse/AMBARI-24283
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Doroszlai, Attila
>Assignee: Krisztian Kasa
>Priority: Minor
> Labels: pull-request-available
> Time Spent: 6.5h
> Remaining Estimate: 0h
>
> STR:
> 1. Deploy ZooKeeper with Ambari 2.5.2
> 2. Create config group on UI
> 3. Upgrade to Ambari 2.6.x
> {noformat}
> group_id | group_name |tag| service_name
> --++---+--
> 3 | asdf | ZOOKEEPER |
> {noformat}
> Result: DB consistency check during startup after the upgrade produces false
> positive warning about the config group
> {noformat}
> WARN - You have config groups present in the database with no corresponding
> service found, [(ConfigGroup, Service) => ( asdf, null )]. Run
> --auto-fix-database to fix this automatically.
> {noformat}
> Following the instructions ({{--auto-fix-database}}) leads to deleting the
> config group.
> This check was added for the case where the service the config group belongs
> to was deleted from the cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24383) A NPE occurs if a Kerberos identity descriptor is missing a Keytab specification
[
https://issues.apache.org/jira/browse/AMBARI-24383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24383:
Labels: kerberos pull-request-available (was: kerberos)
> A NPE occurs if a Kerberos identity descriptor is missing a Keytab
> specification
>
>
> Key: AMBARI-24383
> URL: https://issues.apache.org/jira/browse/AMBARI-24383
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Denis Tarasyuk
>Assignee: Dmitry Lysnichenko
>Priority: Major
> Labels: kerberos, pull-request-available
> Fix For: 2.7.1
>
>
> A NPE occurs if a Kerberos identity descriptor is missing a Keytab
> specification. For example, if the Kerberos identity descriptor is as
> follows:
> {code}
> {
> "name": "druid",
> "principal": {
> "value": "druid_124@${realm}",
> "type": "user"
> }
> }
> {code}
> {noformat:title=Log Message}
> 2018-07-30 12:58:33,332 WARN [Server Action Executor Worker 265]
> ServerActionExecutor:471 - Task #265 failed to complete execution due to
> thrown exception: java.lang.NullPointerException:null
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.KerberosHelperImpl.addIdentities(KerberosHelperImpl.java:1603)
> at
> org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponents(AbstractPrepareKerberosServerAction.java:168)
> at
> org.apache.ambari.server.serveraction.kerberos.AbstractPrepareKerberosServerAction.processServiceComponentHosts(AbstractPrepareKerberosServerAction.java:94)
> at
> org.apache.ambari.server.serveraction.kerberos.PrepareKerberosIdentitiesServerAction.execute(PrepareKerberosIdentitiesServerAction.java:129)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> *Note*: This is technically an unexpected Kerberos identity specification
> since the identity will be unusable. However Ambari should not encounter a
> NPE because of it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24389) Update Ambari Single Sign-on Configuration documentation to include Kerberos options
Robert Levas created AMBARI-24389: - Summary: Update Ambari Single Sign-on Configuration documentation to include Kerberos options Key: AMBARI-24389 URL: https://issues.apache.org/jira/browse/AMBARI-24389 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.1 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.7.1 Update Ambari Single Sign-on Configuration documentation to include Kerberos options. See https://github.com/apache/ambari/blob/branch-2.7/ambari-server/docs/security/sso/index.md. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24388) Install HSI using Add HiveServer2 Interactive button failing
[ https://issues.apache.org/jira/browse/AMBARI-24388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-24388. -- Resolution: Fixed Committed to trunk > Install HSI using Add HiveServer2 Interactive button failing > > > Key: AMBARI-24388 > URL: https://issues.apache.org/jira/browse/AMBARI-24388 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Hide 'Add hiveserver interactive' option if 'Enable Interactive Query ' is > disabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24384) Logic and declaration used to determine if Kerberos is enabled for a service
[
https://issues.apache.org/jira/browse/AMBARI-24384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24384:
--
Description:
Add logic and declaration used to determine if Kerberos is enabled for a
service.
To support a robust method to determine whether Kerberos is enabled or not, a
new attribute should be added - {{kerberosEnabledTest}}.
The {{kerberosEnabledTest}} attribute is to contain a JSON document that can be
_compiled_ into a {{org.apache.commons.collections.Predicate}} (ideally using
{{org.apache.ambari.server.collections.PredicateUtils#fromJSON}}). For example
{code}
true
true
...
{
"equals": [
"service-properties/kerberos.enabled",
"true"
]
}
{code}
{code}
true
true
...
{
"or": [
{
"equals": [
"oozie-site/oozie.authentication.type",
"kerberos"
]
},
{
"equals": [
"oozie-site/oozie.authentication.type",
"org.apache.hadoop.security.authentication.server.JWTRedirectAuthenticationHandler"
]
}
]
}
{code}
The result of the test, is to be available via the services REST API:
{code:title=GET /api/v1/clusters/CLUSTERNAME/services/OOZIE}
{
"href" : "http://ambari_host:8080/api/v1/clusters/CLUSTERNAME/services/OOZIE;,
"ServiceInfo" : {
...
"kerberos_enabled" : true,
...
},
...
}
{code}
was:
Add logic and declaration used to determine if Kerberos is enabled for a
service.
To support a robust method to determine whether Kerberos is enabled or not, a
new attribute should be added - {{kerberosEnabledTest}}.
The {{kerberosEnabledTest}} attribute is to contain a JSON document that can be
_compiled_ into a {{org.apache.commons.collections.Predicate}} (ideally using
{{org.apache.ambari.server.collections.PredicateUtils#fromJSON}}). For example
{code}
true
{
"equals": [
"service-properties/kerberos.enabled",
"true"
]
}
{code}
{code}
true
{
"or": [
{
"equals": [
"oozie-site/oozie.authentication.type",
"kerberos"
]
},
{
"equals": [
"oozie-site/oozie.authentication.type",
"org.apache.hadoop.security.authentication.server.JWTRedirectAuthenticationHandler"
]
}
]
}
{code}
The result of the test, is to be available via the services REST API:
{code:title=GET /api/v1/clusters/CLUSTERNAME/services/OOZIE}
{
"href" : "http://ambari_host:8080/api/v1/clusters/CLUSTERNAME/services/OOZIE;,
"ServiceInfo" : {
...
"kerberos_enabled" : true,
...
},
...
}
{code}
> Logic and declaration used to determine if Kerberos is enabled for a service
>
>
> Key: AMBARI-24384
> URL: https://issues.apache.org/jira/browse/AMBARI-24384
> Project: Ambari
> Issue Type: Bug
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Add logic and declaration used to determine if Kerberos is enabled for a
> service.
> To support a robust method to determine whether Kerberos is enabled or not, a
> new attribute should be added - {{kerberosEnabledTest}}.
> The {{kerberosEnabledTest}} attribute is to contain a JSON document that can
> be _compiled_ into a {{org.apache.commons.collections.Predicate}} (ideally
> using {{org.apache.ambari.server.collections.PredicateUtils#fromJSON}}). For
> example
> {code}
>
> true
> true
> ...
>
>
> {
> "equals": [
> "service-properties/kerberos.enabled",
> "true"
> ]
> }
>
> {code}
> {code}
>
> true
> true
> ...
>
>
> {
> "or": [
> {
> "equals": [
> "oozie-site/oozie.authentication.type",
> "kerberos"
> ]
> },
> {
> "equals": [
> "oozie-site/oozie.authentication.type",
>
> "org.apache.hadoop.security.authentication.server.JWTRedirectAuthenticationHandler"
> ]
> }
> ]
> }
>
> {code}
> The result of the test, is to be available via the services REST API:
> {code:title=GET /api/v1/clusters/CLUSTERNAME/services/OOZIE}
> {
> "href" :
> "http://ambari_host:8080/api/v1/clusters/CLUSTERNAME/services/OOZIE;,
> "ServiceInfo" : {
> ...
> "kerberos_enabled" : true,
> ...
>},
>...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24382) Ambari shouldn't deployed "Undefined" Config Values
[
https://issues.apache.org/jira/browse/AMBARI-24382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563672#comment-16563672
]
Hari Sekhon commented on AMBARI-24382:
--
It looks like making any change to the default config group will result in it
re-interpreting and deploying Undefined values, so I'm having to revert the
change and then put the changes in the regionservers sub config group, but this
implies that I can no longer make any changes to the default config group to
the HMasters as they will pick up Undefined values and break.
> Ambari shouldn't deployed "Undefined" Config Values
> ---
>
> Key: AMBARI-24382
> URL: https://issues.apache.org/jira/browse/AMBARI-24382
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Hari Sekhon
>Priority: Critical
>
> Ambari should not deploy any properties with "Undefined" value (breaks HBase
> Master as shown below).
> When using a config group for HBase RegionServers to only enable Bucket Cache
> on RegionServers (see AMBARI-24370), and then enabling a bunch of settings
> related to using the bucket cache in the default config, Ambari will infer
> that there should be a bucketcache setting and injects the following
> properties with a literal value of "Undefined" in hbase-site.xml:
> {code:java}
>
> hbase.bucketcache.ioengine
> Undefined
>
>
> hbase.bucketcache.size
> Undefined
> {code}
> which breaks HMaster restart:
> {code:java}
> 2018-07-30 13:26:08,283 ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Failed construction of Master: class
> org.apache.hadoop.hbase.master.HMaster
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2824)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:235)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
> at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2838)
> Caused by: java.lang.NumberFormatException: For input string: "Undefined"
> at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2043)
> at sun.misc.FloatingDecimal.parseFloat(FloatingDecimal.java:122)
> at java.lang.Float.parseFloat(Float.java:451)
> at org.apache.hadoop.conf.Configuration.getFloat(Configuration.java:1400)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.getBucketCache(CacheConfig.java:597)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.getL2(CacheConfig.java:566)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.instantiateBlockCache(CacheConfig.java:650)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.(CacheConfig.java:239)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:591)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:425)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2819)
> ... 5 more
> {code}
> The above two settings are only added to a config group RegionServers, but
> when the following settings are applied to the default config group thinking
> they should be ignored by Masters because bucket cache isn't enabled on
> Master, it turns out that Ambari infers they should exist, leaves them
> Undefined but deploys them anyway (these settings are from the OpenTSDB HBase
> performance tuning guide btw):
> {code:java}
> hbase.rs.cacheblocksonwrite=true
> hbase.rs.evictblocksonclose=false
> hfile.block.bloom.cacheonwrite=true
> hfile.block.index.cacheonwrite=true
> hbase.block.data.cachecompressed=true
> hbase.bucketcache.blockcache.single.percentage=.99
> hbase.bucketcache.blockcache.multi.percentage=0
> hbase.bucketcache.blockcache.memory.percentage=.01
> {code}
> I've worked around it by moving the config to the regionservers config group,
> but ran in to AMBARI-24371 again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24382) Ambari shouldn't deployed "Undefined" Config Values
[
https://issues.apache.org/jira/browse/AMBARI-24382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563660#comment-16563660
]
Hari Sekhon commented on AMBARI-24382:
--
It looks like this is a more severe issue than I thought, even setting
something in the default config group which seems unrelated to bucket cache
settings, such as
{code:java}
hbase.ipc.server.callqueue.read.ratio{code}
still causes the new HMaster config to pick up all the Undefined values that
only exist in the regionservers config group and write them literally in to the
hbase-site.xml for HMaster when restarting ... again breaking the HMaster. The
hbase-site.xml then contains the following config it should have omitted:
{code:java}
hbase.block.data.cachecompressed
Undefined
hbase.bucketcache.blockcache.memory.percentage
Undefined
hbase.bucketcache.blockcache.multi.percentage
Undefined
hbase.bucketcache.blockcache.single.percentage
Undefined
hbase.bucketcache.combinedcache.enabled
Undefined
hbase.bucketcache.ioengine
Undefined
hbase.bucketcache.size
Undefined
...
hbase.rs.cacheblocksonwrite
Undefined
hbase.rs.evictblocksonclose
Undefined
...
hfile.block.bloom.cacheonwrite
Undefined
{code}
> Ambari shouldn't deployed "Undefined" Config Values
> ---
>
> Key: AMBARI-24382
> URL: https://issues.apache.org/jira/browse/AMBARI-24382
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Hari Sekhon
>Priority: Critical
>
> Ambari should not deploy any properties with "Undefined" value (breaks HBase
> Master as shown below).
> When using a config group for HBase RegionServers to only enable Bucket Cache
> on RegionServers (see AMBARI-24370), and then enabling a bunch of settings
> related to using the bucket cache in the default config, Ambari will infer
> that there should be a bucketcache setting and injects the following
> properties with a literal value of "Undefined" in hbase-site.xml:
> {code:java}
>
> hbase.bucketcache.ioengine
> Undefined
>
>
> hbase.bucketcache.size
> Undefined
> {code}
> which breaks HMaster restart:
> {code:java}
> 2018-07-30 13:26:08,283 ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Failed construction of Master: class
> org.apache.hadoop.hbase.master.HMaster
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2824)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:235)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
> at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2838)
> Caused by: java.lang.NumberFormatException: For input string: "Undefined"
> at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2043)
> at sun.misc.FloatingDecimal.parseFloat(FloatingDecimal.java:122)
> at java.lang.Float.parseFloat(Float.java:451)
> at org.apache.hadoop.conf.Configuration.getFloat(Configuration.java:1400)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.getBucketCache(CacheConfig.java:597)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.getL2(CacheConfig.java:566)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.instantiateBlockCache(CacheConfig.java:650)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.(CacheConfig.java:239)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:591)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:425)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2819)
> ... 5 more
> {code}
> The above two settings are only added to a config group RegionServers, but
> when the following settings are applied to the default config group thinking
> they should be ignored by Masters because bucket cache isn't enabled on
> Master, it turns out that Ambari infers they should exist, leaves them
> Undefined but deploys them anyway (these settings are from the OpenTSDB HBase
> performance tuning guide btw):
> {code:java}
> hbase.rs.cacheblocksonwrite=true
> hbase.rs.evictblocksonclose=false
> hfile.block.bloom.cacheonwrite=true
> hfile.block.index.cacheonwrite=true
> hbase.block.data.cachecompressed=true
> hbase.bucketcache.blockcache.single.percentage=.99
>
[jira] [Updated] (AMBARI-24382) Ambari shouldn't deployed "Undefined" Config Values
[
https://issues.apache.org/jira/browse/AMBARI-24382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated AMBARI-24382:
-
Priority: Critical (was: Major)
> Ambari shouldn't deployed "Undefined" Config Values
> ---
>
> Key: AMBARI-24382
> URL: https://issues.apache.org/jira/browse/AMBARI-24382
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Hari Sekhon
>Priority: Critical
>
> Ambari should not deploy any properties with "Undefined" value (breaks HBase
> Master as shown below).
> When using a config group for HBase RegionServers to only enable Bucket Cache
> on RegionServers (see AMBARI-24370), and then enabling a bunch of settings
> related to using the bucket cache in the default config, Ambari will infer
> that there should be a bucketcache setting and injects the following
> properties with a literal value of "Undefined" in hbase-site.xml:
> {code:java}
>
> hbase.bucketcache.ioengine
> Undefined
>
>
> hbase.bucketcache.size
> Undefined
> {code}
> which breaks HMaster restart:
> {code:java}
> 2018-07-30 13:26:08,283 ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Failed construction of Master: class
> org.apache.hadoop.hbase.master.HMaster
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2824)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:235)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
> at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2838)
> Caused by: java.lang.NumberFormatException: For input string: "Undefined"
> at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2043)
> at sun.misc.FloatingDecimal.parseFloat(FloatingDecimal.java:122)
> at java.lang.Float.parseFloat(Float.java:451)
> at org.apache.hadoop.conf.Configuration.getFloat(Configuration.java:1400)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.getBucketCache(CacheConfig.java:597)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.getL2(CacheConfig.java:566)
> at
> org.apache.hadoop.hbase.io.hfile.CacheConfig.instantiateBlockCache(CacheConfig.java:650)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.(CacheConfig.java:239)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:591)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:425)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2819)
> ... 5 more
> {code}
> The above two settings are only added to a config group RegionServers, but
> when the following settings are applied to the default config group thinking
> they should be ignored by Masters because bucket cache isn't enabled on
> Master, it turns out that Ambari infers they should exist, leaves them
> Undefined but deploys them anyway (these settings are from the OpenTSDB HBase
> performance tuning guide btw):
> {code:java}
> hbase.rs.cacheblocksonwrite=true
> hbase.rs.evictblocksonclose=false
> hfile.block.bloom.cacheonwrite=true
> hfile.block.index.cacheonwrite=true
> hbase.block.data.cachecompressed=true
> hbase.bucketcache.blockcache.single.percentage=.99
> hbase.bucketcache.blockcache.multi.percentage=0
> hbase.bucketcache.blockcache.memory.percentage=.01
> {code}
> I've worked around it by moving the config to the regionservers config group,
> but ran in to AMBARI-24371 again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24364) Mpack Instance Manager Not Listing Versions Correctly
[ https://issues.apache.org/jira/browse/AMBARI-24364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24364: Labels: pull-request-available (was: ) > Mpack Instance Manager Not Listing Versions Correctly > - > > Key: AMBARI-24364 > URL: https://issues.apache.org/jira/browse/AMBARI-24364 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Scott Duan >Assignee: Scott Duan >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDPCORE/1.0.0-b450/services/ZOOKEEPER/package/scripts/zookeeper_server.py", > line 124, in > ZookeeperServer().execute() > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", > line 352, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDPCORE/1.0.0-b450/services/ZOOKEEPER/package/scripts/zookeeper_server.py", > line 106, in statusimport status_params > File > "/var/lib/ambari-agent/cache/stacks/HDPCORE/1.0.0-b450/services/ZOOKEEPER/package/scripts/status_params.py", > line 43, in > component_instance_name=component_instance_name) > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/mpack_manager_helper.py", > line 45, in get_component_conf_pathreturn > conf_json[COMPONENTS_PLURAL_KEY_NAME][components_instance_type.lower()][COMPONENT_INSTANCES_PLURAL_KEY_NAME][ > KeyError: 'components' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (AMBARI-13769) Ambari Automated Install with IPv6 hosts
[ https://issues.apache.org/jira/browse/AMBARI-13769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-13769: - Comment: was deleted (was: Hi [~qzzeng] Could you please tell me whether ambari support IPv6 hosts in your deployed cluster? ) > Ambari Automated Install with IPv6 hosts > > > Key: AMBARI-13769 > URL: https://issues.apache.org/jira/browse/AMBARI-13769 > Project: Ambari > Issue Type: Test > Components: ambari-agent, ambari-server >Affects Versions: 2.1.2 > Environment: CentOS 7, IPv6 >Reporter: zeng qijia >Priority: Trivial > > All of the hosts are using IPv6 address with Cent OS 7, Cluster Install > Wizard ->Confirm Host section failed, log shows ambari agent can't access the > ambari host, but I just confirmed that log in from agent to server via > browser, and ssh without password are successful. Everything is okay if I > assign IPv4 address to hosts instead. I assume that it is cause by some hard > codes only works for IPv4 addresses in configure scripts. > Here is the error in log: > == > Running setup agent script... > == > Command start time 2015-11-06 08:50:12 > Host registration aborted. Ambari Agent host cannot reach Ambari Server > 'm1.hdp2:8080'. Please check the network connectivity between the Ambari > Agent host and the Ambari Server > Connection to m2.hdp2 closed. > SSH command execution finished > host=m2.hdp2, exitcode=1 > Command end time 2015-11-06 08:50:12 > ERROR: Bootstrap of host m2.hdp2 fails because previous action finished with > non-zero exit code (1) > ERROR MESSAGE: Connection to m2.hdp2 closed. > STDOUT: Host registration aborted. Ambari Agent host cannot reach Ambari > Server 'm1.hdp2:8080'. Please check the network connectivity between the > Ambari Agent host and the Ambari Server > Connection to m2.hdp2 closed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24387) Support YARN Application timeout feature in Ambari Capacity Scheduler View
[
https://issues.apache.org/jira/browse/AMBARI-24387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-24387:
--
Fix Version/s: 2.7.1
Status: Patch Available (was: In Progress)
> Support YARN Application timeout feature in Ambari Capacity Scheduler View
> --
>
> Key: AMBARI-24387
> URL: https://issues.apache.org/jira/browse/AMBARI-24387
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The CapacityScheduler supports the following parameters to lifetime of an
> application:
> At high level, we need a mechanism to set timeout values for each leaf queue
> from Capacity Scheduler view. The sample configuration that should reflected
> in backend is
> {code:java}
> yarn.scheduler.capacity.root.default.maximum-application-lifetime= seconds>
> yarn.scheduler.capacity.root.default.default-application-lifetime= seconds>
> {code}
> Capacity Scheduler view should support following tags.
> description of this tags can be found in :
> https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24388) Install HSI using Add HiveServer2 Interactive button failing
[ https://issues.apache.org/jira/browse/AMBARI-24388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24388: Labels: pull-request-available (was: ) > Install HSI using Add HiveServer2 Interactive button failing > > > Key: AMBARI-24388 > URL: https://issues.apache.org/jira/browse/AMBARI-24388 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > > Hide 'Add hiveserver interactive' option if 'Enable Interactive Query ' is > disabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24387) Support YARN Application timeout feature in Ambari Capacity Scheduler View
[
https://issues.apache.org/jira/browse/AMBARI-24387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24387:
Labels: pull-request-available (was: )
> Support YARN Application timeout feature in Ambari Capacity Scheduler View
> --
>
> Key: AMBARI-24387
> URL: https://issues.apache.org/jira/browse/AMBARI-24387
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
>
> The CapacityScheduler supports the following parameters to lifetime of an
> application:
> At high level, we need a mechanism to set timeout values for each leaf queue
> from Capacity Scheduler view. The sample configuration that should reflected
> in backend is
> {code:java}
> yarn.scheduler.capacity.root.default.maximum-application-lifetime= seconds>
> yarn.scheduler.capacity.root.default.default-application-lifetime= seconds>
> {code}
> Capacity Scheduler view should support following tags.
> description of this tags can be found in :
> https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-24388) Install HSI using Add HiveServer2 Interactive button failing
[ https://issues.apache.org/jira/browse/AMBARI-24388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24388: Assignee: Antonenko Alexander > Install HSI using Add HiveServer2 Interactive button failing > > > Key: AMBARI-24388 > URL: https://issues.apache.org/jira/browse/AMBARI-24388 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.1 > > > Hide 'Add hiveserver interactive' option if 'Enable Interactive Query ' is > disabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24388) Install HSI using Add HiveServer2 Interactive button failing
Antonenko Alexander created AMBARI-24388: Summary: Install HSI using Add HiveServer2 Interactive button failing Key: AMBARI-24388 URL: https://issues.apache.org/jira/browse/AMBARI-24388 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.1 Hide 'Add hiveserver interactive' option if 'Enable Interactive Query ' is disabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24387) Support YARN Application timeout feature in Ambari Capacity Scheduler View
Akhil S Naik created AMBARI-24387:
-
Summary: Support YARN Application timeout feature in Ambari
Capacity Scheduler View
Key: AMBARI-24387
URL: https://issues.apache.org/jira/browse/AMBARI-24387
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.7.0
Reporter: Akhil S Naik
Assignee: Akhil S Naik
The CapacityScheduler supports the following parameters to lifetime of an
application:
At high level, we need a mechanism to set timeout values for each leaf queue
from Capacity Scheduler view. The sample configuration that should reflected in
backend is
{code:java}
yarn.scheduler.capacity.root.default.maximum-application-lifetime=
yarn.scheduler.capacity.root.default.default-application-lifetime=
{code}
Capacity Scheduler view should support following tags.
description of this tags can be found in :
https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24386) [Log Search] Input config validator unable to parse any log entry
[
https://issues.apache.org/jira/browse/AMBARI-24386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563449#comment-16563449
]
Hudson commented on AMBARI-24386:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9703 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9703/])
AMBARI-24386 - [Log Search] Input config validator unable to parse any (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=b69df91e999f2900f0876ee6a535a4bbdb8a6555])
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogEntryParseTester.java
> [Log Search] Input config validator unable to parse any log entry
> -
>
> Key: AMBARI-24386
> URL: https://issues.apache.org/jira/browse/AMBARI-24386
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
>Affects Versions: 2.7.1
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 1. Login to Logsearch portal
> 2. Select "Configuration Editor" from the right upper corner menu
> 3. Select an input config from "All Configuration" (ambari)
> 4. Enter a "Component Name" on the "Validator" section (ambari_agent)
> 5. Enter a log entry to the "Sample Data" text area
> {code}
> INFO 2018-07-31 06:14:06,550 security.py:67 - SSL connection established.
> Two-way SSL authentication is turned off on the server.
> {code}
> 6. Click "Test"
> 7. The result is the configuration is not valid
> Validator throws java.lang.NullPointerException
> {code}
> /var/log/ambari-logsearch-portal/logsearch.log
> {code}
> {code}
> 2018-07-31 06:27:54,674 [qtp1933799970-15] ERROR
> apache.ambari.logfeeder.plugin.input.Input (Input.java:193) - Error during
> filter apply: {}
> java.lang.NullPointerException
> at
> org.apache.ambari.logfeeder.output.OutputManagerImpl.getDefaultLogLevels(OutputManagerImpl.java:165)
> at
> org.apache.ambari.logfeeder.output.OutputManagerImpl.write(OutputManagerImpl.java:147)
> at
> org.apache.ambari.logfeeder.plugin.filter.Filter.apply(Filter.java:121)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.applyMessage(FilterGrok.java:278)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.apply(FilterGrok.java:206)
> at
> org.apache.ambari.logfeeder.plugin.input.Input.outputLine(Input.java:191)
> at
> org.apache.ambari.logfeeder.common.LogEntryParseTester.parse(LogEntryParseTester.java:136)
> at
> org.apache.ambari.logsearch.manager.ShipperConfigManager.testShipperConfig(ShipperConfigManager.java:113)
> at
> org.apache.ambari.logsearch.rest.ShipperConfigResource.testShipperConfig(ShipperConfigResource.java:105)
> 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
>
[jira] [Updated] (AMBARI-24386) [Log Search] Input config validator unable to parse any log entry
[
https://issues.apache.org/jira/browse/AMBARI-24386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krisztian Kasa updated AMBARI-24386:
Status: Patch Available (was: Open)
> [Log Search] Input config validator unable to parse any log entry
> -
>
> Key: AMBARI-24386
> URL: https://issues.apache.org/jira/browse/AMBARI-24386
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
>Affects Versions: 2.7.1
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 1. Login to Logsearch portal
> 2. Select "Configuration Editor" from the right upper corner menu
> 3. Select an input config from "All Configuration" (ambari)
> 4. Enter a "Component Name" on the "Validator" section (ambari_agent)
> 5. Enter a log entry to the "Sample Data" text area
> {code}
> INFO 2018-07-31 06:14:06,550 security.py:67 - SSL connection established.
> Two-way SSL authentication is turned off on the server.
> {code}
> 6. Click "Test"
> 7. The result is the configuration is not valid
> Validator throws java.lang.NullPointerException
> {code}
> /var/log/ambari-logsearch-portal/logsearch.log
> {code}
> {code}
> 2018-07-31 06:27:54,674 [qtp1933799970-15] ERROR
> apache.ambari.logfeeder.plugin.input.Input (Input.java:193) - Error during
> filter apply: {}
> java.lang.NullPointerException
> at
> org.apache.ambari.logfeeder.output.OutputManagerImpl.getDefaultLogLevels(OutputManagerImpl.java:165)
> at
> org.apache.ambari.logfeeder.output.OutputManagerImpl.write(OutputManagerImpl.java:147)
> at
> org.apache.ambari.logfeeder.plugin.filter.Filter.apply(Filter.java:121)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.applyMessage(FilterGrok.java:278)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.apply(FilterGrok.java:206)
> at
> org.apache.ambari.logfeeder.plugin.input.Input.outputLine(Input.java:191)
> at
> org.apache.ambari.logfeeder.common.LogEntryParseTester.parse(LogEntryParseTester.java:136)
> at
> org.apache.ambari.logsearch.manager.ShipperConfigManager.testShipperConfig(ShipperConfigManager.java:113)
> at
> org.apache.ambari.logsearch.rest.ShipperConfigResource.testShipperConfig(ShipperConfigResource.java:105)
> 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
>
[jira] [Updated] (AMBARI-24187) Ambari Server Setup LDAP Label Updates
[
https://issues.apache.org/jira/browse/AMBARI-24187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krisztian Kasa updated AMBARI-24187:
Description:
Ask users to select ldap type ( AD, IPA, generic ldap) and provide inteligent
defaults based on their choice:
Active Directory
{code:java}
# ambari-server setup-ldap
Using python /usr/bin/python
Currently 'no auth method' is configured, do you wish to use LDAP instead [y/n]
(y)?
Primary LDAP Host:
Primary LDAP Port:
Secondary LDAP Host :
Secondary LDAP Port :
Use SSL [true/false] (false):
User object class (user):
User ID attribute (sAMAccountName):
Group object class (group):
Group name attribute (cn):
Group member attribute (member):
Distinguished name attribute (distinguishedName):
Search Base (dc=ambari,dc=apache,dc=org):
User Search Base (ou=users,dc=ambari,dc=apache,dc=org):
Group Search Base (ou=groups,dc=ambari,dc=apache,dc=org):
Referral method [follow/ignore] (follow):
Bind anonymously [true/false] (false):
Bind DN (cn=ldapbind,dc=ambari,dc=apache,dc=org):
Enter Bind DN Password:
Confirm Bind DN Password:
Handling behavior for username collisions [convert/skip] for LDAP sync (skip):
Force lower-case user names [true/false] (true):
Results from LDAP are paginated when requested [true/false] (false):
{code}
IPA (very similar to generic ldap, but needs explicit search customization into
cn=accounts (or cn=compat) else it returns 2 search results which tends to
cause problems)
{code:java}
{code:java}
# ambari-server setup-ldap
Using python /usr/bin/python
Currently 'no auth method' is configured, do you wish to use LDAP instead [y/n]
(y)?
Primary LDAP Host (ipa.ambari.apache.org):
Primary LDAP Port (636):
Secondary LDAP Host :
Secondary LDAP Port :
Use SSL [true/false] (true):
Do you want to provide custom TrustStore for Ambari [y/n] (y)?
TrustStore type [jks/jceks/pkcs12] (jks):
Path to TrustStore file (/etc/pki/java/cacerts):
Password for TrustStore (changeit):
User object class (posixUser):
User ID attribute (uid):
Group object class (posixGroup):
Group name attribute (cn):
Group member attribute (memberUid):
Distinguished name attribute (dn):
Search Base (dc=ambari,dc=apache,dc=org):
User Search Base (cn=users,cn=accounts,dc=ambari,dc=apache,dc=org):
Group Search Base (cn=groups,cn=accounts,dc=ambari,dc=apache,dc=org):
Referral method [follow/ignore] (follow):
Bind anonymously [true/false] (false):
Bind DN ( uid=ldapbind,cn=users,cn=accounts,dc=ambari,dc=apache,dc=org):
Enter Bind DN Password:
Confirm Bind DN Password:
Handling behavior for username collisions [convert/skip] for LDAP sync (skip):
{code}
Generic LDAP (defaults here need validation, i'm not as familiar with this one)
{code:java}
# ambari-server setup-ldap
Using python /usr/bin/python
Currently 'no auth method' is configured, do you wish to use LDAP instead [y/n]
(y)?
Primary LDAP Host (ldap.ambari.apache.org):
Primary LDAP Port (389):
Secondary LDAP Host :
Secondary LDAP Port :
Use SSL [true/false] (false):
Do you want to provide custom TrustStore for Ambari [y/n] (n)?
User object class (posixUser):
User ID attribute (uid):
Group object class (posixGroup):
Group name attribute (cn):
Group member attribute (memberUid):
Distinguished name attribute (dn):
Search Base (dc=ambari,dc=apache,dc=org):
User Search Base (cn=users,dc=ambari,dc=apache,dc=org):
Group Search Base (cn=groups,dc=ambari,dc=apache,dc=org):
Referral method [follow/ignore] (follow):
Bind anonymously [true/false] (false):
Bind DN ( uid=ldapbind,cn=users,dc=ambari,dc=apache,dc=org):
Enter Bind DN Password:
Confirm Bind DN Password:
Handling behavior for username collisions [convert/skip] for LDAP sync (skip):
{code}
was:
It was noticed in the bug bash that there were issues with label names and
defaults. In an effort to make them easier to read and fix the issues
identified, the following labels, default values, and spacing before ':'
changes need to be made. Please make the wizard look just like the text below:
{code}
# ambari-server setup-ldap
Using python /usr/bin/python
Currently 'no auth method' is configured, do you wish to use LDAP instead [y/n]
(y)?
Primary LDAP Host:
Primary LDAP Port:
Secondary LDAP Host :
Secondary LDAP Port :
Use SSL [true/false] (false):
User object class (user):
User ID attribute (sAMAccountName):
Group object class (group):
Group name attribute (cn):
Group member attribute (member):
Distinguished name attribute (distinguishedName):
Search Base (dc=ambari,dc=apache,dc=org):
Referral method [follow/ignore] (follow):
Bind anonymously [true/false] (false):
Bind DN (cn=ldapbind,dc=ambari,dc=apache,dc=org):
Enter Bind DN Password:
Confirm Bind DN Password:
Handling behavior for username collisions [convert/skip] for LDAP sync (skip):
Force lower-case user names [true/false] (true):
Results from LDAP are paginated when requested [true/false] (false):
[jira] [Updated] (AMBARI-24386) [Log Search] Input config validator unable to parse any log entry
[
https://issues.apache.org/jira/browse/AMBARI-24386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24386:
Labels: pull-request-available (was: )
> [Log Search] Input config validator unable to parse any log entry
> -
>
> Key: AMBARI-24386
> URL: https://issues.apache.org/jira/browse/AMBARI-24386
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
>Affects Versions: 2.7.1
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> 1. Login to Logsearch portal
> 2. Select "Configuration Editor" from the right upper corner menu
> 3. Select an input config from "All Configuration" (ambari)
> 4. Enter a "Component Name" on the "Validator" section (ambari_agent)
> 5. Enter a log entry to the "Sample Data" text area
> {code}
> INFO 2018-07-31 06:14:06,550 security.py:67 - SSL connection established.
> Two-way SSL authentication is turned off on the server.
> {code}
> 6. Click "Test"
> 7. The result is the configuration is not valid
> Validator throws java.lang.NullPointerException
> {code}
> /var/log/ambari-logsearch-portal/logsearch.log
> {code}
> {code}
> 2018-07-31 06:27:54,674 [qtp1933799970-15] ERROR
> apache.ambari.logfeeder.plugin.input.Input (Input.java:193) - Error during
> filter apply: {}
> java.lang.NullPointerException
> at
> org.apache.ambari.logfeeder.output.OutputManagerImpl.getDefaultLogLevels(OutputManagerImpl.java:165)
> at
> org.apache.ambari.logfeeder.output.OutputManagerImpl.write(OutputManagerImpl.java:147)
> at
> org.apache.ambari.logfeeder.plugin.filter.Filter.apply(Filter.java:121)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.applyMessage(FilterGrok.java:278)
> at
> org.apache.ambari.logfeeder.filter.FilterGrok.apply(FilterGrok.java:206)
> at
> org.apache.ambari.logfeeder.plugin.input.Input.outputLine(Input.java:191)
> at
> org.apache.ambari.logfeeder.common.LogEntryParseTester.parse(LogEntryParseTester.java:136)
> at
> org.apache.ambari.logsearch.manager.ShipperConfigManager.testShipperConfig(ShipperConfigManager.java:113)
> at
> org.apache.ambari.logsearch.rest.ShipperConfigResource.testShipperConfig(ShipperConfigResource.java:105)
> 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
>
[jira] [Created] (AMBARI-24386) [Log Search] Input config validator unable to parse any log entry
Krisztian Kasa created AMBARI-24386:
---
Summary: [Log Search] Input config validator unable to parse any
log entry
Key: AMBARI-24386
URL: https://issues.apache.org/jira/browse/AMBARI-24386
Project: Ambari
Issue Type: Bug
Components: logsearch
Affects Versions: 2.7.1
Reporter: Krisztian Kasa
Assignee: Krisztian Kasa
Fix For: 2.7.1
1. Login to Logsearch portal
2. Select "Configuration Editor" from the right upper corner menu
3. Select an input config from "All Configuration" (ambari)
4. Enter a "Component Name" on the "Validator" section (ambari_agent)
5. Enter a log entry to the "Sample Data" text area
{code}
INFO 2018-07-31 06:14:06,550 security.py:67 - SSL connection established.
Two-way SSL authentication is turned off on the server.
{code}
6. Click "Test"
7. The result is the configuration is not valid
Validator throws java.lang.NullPointerException
{code}
/var/log/ambari-logsearch-portal/logsearch.log
{code}
{code}
2018-07-31 06:27:54,674 [qtp1933799970-15] ERROR
apache.ambari.logfeeder.plugin.input.Input (Input.java:193) - Error during
filter apply: {}
java.lang.NullPointerException
at
org.apache.ambari.logfeeder.output.OutputManagerImpl.getDefaultLogLevels(OutputManagerImpl.java:165)
at
org.apache.ambari.logfeeder.output.OutputManagerImpl.write(OutputManagerImpl.java:147)
at
org.apache.ambari.logfeeder.plugin.filter.Filter.apply(Filter.java:121)
at
org.apache.ambari.logfeeder.filter.FilterGrok.applyMessage(FilterGrok.java:278)
at
org.apache.ambari.logfeeder.filter.FilterGrok.apply(FilterGrok.java:206)
at
org.apache.ambari.logfeeder.plugin.input.Input.outputLine(Input.java:191)
at
org.apache.ambari.logfeeder.common.LogEntryParseTester.parse(LogEntryParseTester.java:136)
at
org.apache.ambari.logsearch.manager.ShipperConfigManager.testShipperConfig(ShipperConfigManager.java:113)
at
org.apache.ambari.logsearch.rest.ShipperConfigResource.testShipperConfig(ShipperConfigResource.java:105)
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
[jira] [Commented] (AMBARI-24378) Updating LDAPSettings section for Ranger in Advanced config section
[
https://issues.apache.org/jira/browse/AMBARI-24378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563192#comment-16563192
]
Hudson commented on AMBARI-24378:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #92 (See
[https://builds.apache.org/job/Ambari-branch-2.7/92/])
AMBARI-24378 Updating LDAPSettings section for Ranger in Advanced config
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=26a48eac0cc06c534da51c057d71d895465919e1])
* (edit) ambari-web/app/data/configs/services/ranger_properties.js
* (edit) ambari-web/app/models/stack_service.js
> Updating LDAPSettings section for Ranger in Advanced config section
> ---
>
> Key: AMBARI-24378
> URL: https://issues.apache.org/jira/browse/AMBARI-24378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.7.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Adding {{ranger.ldap.group.searchbase}}, {{ranger.ldap.group.searchfilter}}
> configs in LDAP category.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24378) Updating LDAPSettings section for Ranger in Advanced config section
[
https://issues.apache.org/jira/browse/AMBARI-24378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563191#comment-16563191
]
Hudson commented on AMBARI-24378:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9700 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9700/])
AMBARI-24378 Updating LDAPSettings section for Ranger in Advanced config
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=b38bb9f6ecb9116a251d17c083d286a63d3f47ec])
* (edit) ambari-web/app/data/configs/services/ranger_properties.js
* (edit) ambari-web/app/models/stack_service.js
> Updating LDAPSettings section for Ranger in Advanced config section
> ---
>
> Key: AMBARI-24378
> URL: https://issues.apache.org/jira/browse/AMBARI-24378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.7.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Adding {{ranger.ldap.group.searchbase}}, {{ranger.ldap.group.searchfilter}}
> configs in LDAP category.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
