[jira] [Updated] (AMBARI-23974) Add hidden attribute to mpack module, stack services and cluster services
[ https://issues.apache.org/jira/browse/AMBARI-23974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23974: Labels: pull-request-available (was: ) > Add hidden attribute to mpack module, stack services and cluster services > - > > Key: AMBARI-23974 > URL: https://issues.apache.org/jira/browse/AMBARI-23974 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23974) Add hidden attribute to mpack module, stack services and cluster services
Jayush Luniya created AMBARI-23974: -- Summary: Add hidden attribute to mpack module, stack services and cluster services Key: AMBARI-23974 URL: https://issues.apache.org/jira/browse/AMBARI-23974 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23957) Spark2 Thrift Server fails to start if LLAP and parallel execution are enabled
[
https://issues.apache.org/jira/browse/AMBARI-23957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila resolved AMBARI-23957.
Resolution: Fixed
Fix Version/s: trunk
> Spark2 Thrift Server fails to start if LLAP and parallel execution are enabled
> --
>
> Key: AMBARI-23957
> URL: https://issues.apache.org/jira/browse/AMBARI-23957
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> STR:
> # Enable parallel execution in Ambari Agent
> # Deploy cluster via blueprint, placing Spark2 Thrift Server on the same node
> as Hive Server Interactive
> Result: Spark2 Thrift Server runs into the following error during startup:
> {noformat}
> ZooKeeperHiveClientException: Unable to read HiveServer2 configs from
> ZooKeeper
> ...
> KeeperErrorCode = NoNode for /hiveserver2-hive2
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23973) Pre Upgrade check for AMS hadoop sink in HDP 2.6 to 3.0 EU.
[ https://issues.apache.org/jira/browse/AMBARI-23973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23973: Labels: pull-request-available (was: ) > Pre Upgrade check for AMS hadoop sink in HDP 2.6 to 3.0 EU. > --- > > Key: AMBARI-23973 > URL: https://issues.apache.org/jira/browse/AMBARI-23973 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > > Add a pre upgrade check to verify that the version of hadoop-sink package on > ALL hosts is 2.7.0.0. > * Create a custom command which checks the version of hadoop-sink. > * Create a server side request in the pre-upgrade check which invokes the > command in all hosts and collects the results. > * All hosts MUST have upgraded versions of hadoop 2.7.0.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23973) Pre Upgrade check for AMS hadoop sink in HDP 2.6 to 3.0 EU.
Aravindan Vijayan created AMBARI-23973: -- Summary: Pre Upgrade check for AMS hadoop sink in HDP 2.6 to 3.0 EU. Key: AMBARI-23973 URL: https://issues.apache.org/jira/browse/AMBARI-23973 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.0 Add a pre upgrade check to verify that the version of hadoop-sink package on ALL hosts is 2.7.0.0. * Create a custom command which checks the version of hadoop-sink. * Create a server side request in the pre-upgrade check which invokes the command in all hosts and collects the results. * All hosts MUST have upgraded versions of hadoop 2.7.0.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23949) Accessing Swagger API when Ambari Server is configured for HTTPS
[ https://issues.apache.org/jira/browse/AMBARI-23949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494242#comment-16494242 ] Hudson commented on AMBARI-23949: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9356 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9356/]) AMBARI-23949. Accessing Swagger API when Ambari Server is configured for (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1fc1a554841e837cad6a70cf030a0849302d7f44]) * (edit) ambari-server/docs/api/generated/swagger.json * (edit) ambari-web/api-docs/swagger-ui.js * (edit) ambari-web/api-docs/swagger-ui.min.js * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/ServiceService.java * (edit) ambari-web/api-docs/css/api-explorer.css * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/ClusterService.java * (edit) ambari-server/pom.xml * (edit) ambari-server/docs/api/generated/index.html > Accessing Swagger API when Ambari Server is configured for HTTPS > > > Key: AMBARI-23949 > URL: https://issues.apache.org/jira/browse/AMBARI-23949 > Project: Ambari > Issue Type: Bug > Components: ambari-sever, ambari-web >Affects Versions: 2.7.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The api-docs end-point is available but the Try button doesn't work when the > Ambari Server is configured for HTTPS. > STR: > # Install Ambari Server > # Use /api-docs Try button on any API and notice that it works > # Configure Ambari Server to use SSL on port 8443 > # Try to use /api-docs Try button now and notice it picks up the right port > (8443) but the protocol is (http://) instead of (https://) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23966) Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP 3.0
[ https://issues.apache.org/jira/browse/AMBARI-23966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494243#comment-16494243 ] Hudson commented on AMBARI-23966: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9356 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9356/]) [AMBARI-23966] Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8a92f3726c8d6d29e84bce97c3489b66f6c52138]) * (add) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/CreateZeppelinSiteConfig.java > Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP 3.0 > --- > > Key: AMBARI-23966 > URL: https://issues.apache.org/jira/browse/AMBARI-23966 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP 3.0 > Configuration changes/ any data migration changes needed to upgrade using > express from HDP 2.6 to HDP 3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23972) Update code for : (1). 'mpack-recommendations' directory creation and (2). putting 'mpack_advisor_wrapper.py' in '/var/lib/ambari-server/resources/scripts/' folder.
[ https://issues.apache.org/jira/browse/AMBARI-23972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23972: - Description: (was: *Background on Mpack Advisor: * AMBARI-23870 - Implemented 3.0 Mpack Advisor's Host Component Layout Recommendation and Validations API Server code. - Pull Request: https://github.com/apache/ambari/pull/1296 AMBARI-23923 - Implement 3.0 Mpack Advisor's Configuration Recommendation API Server code for "Cluster Create". - https://github.com/apache/ambari/pull/1348 - *Current Task:* Implements : - 3.0 Mpack Advisor's Configuration "Validations", and - updates the code for Component Layout "Validations" checked in AMBARI-23870.) > Update code for : (1). 'mpack-recommendations' directory creation and (2). > putting 'mpack_advisor_wrapper.py' in > '/var/lib/ambari-server/resources/scripts/' folder. > - > > Key: AMBARI-23972 > URL: https://issues.apache.org/jira/browse/AMBARI-23972 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23972) Update code for : (1). 'mpack-recommendations' directory creation and (2). putting 'mpack_advisor_wrapper.py' in '/var/lib/ambari-server/resources/scripts/' folder.
Swapan Shridhar created AMBARI-23972: Summary: Update code for : (1). 'mpack-recommendations' directory creation and (2). putting 'mpack_advisor_wrapper.py' in '/var/lib/ambari-server/resources/scripts/' folder. Key: AMBARI-23972 URL: https://issues.apache.org/jira/browse/AMBARI-23972 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 3.0.0 *Background on Mpack Advisor: * AMBARI-23870 - Implemented 3.0 Mpack Advisor's Host Component Layout Recommendation and Validations API Server code. - Pull Request: https://github.com/apache/ambari/pull/1296 AMBARI-23923 - Implement 3.0 Mpack Advisor's Configuration Recommendation API Server code for "Cluster Create". - https://github.com/apache/ambari/pull/1348 - *Current Task:* Implements : - 3.0 Mpack Advisor's Configuration "Validations", and - updates the code for Component Layout "Validations" checked in AMBARI-23870. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23949) Accessing Swagger API when Ambari Server is configured for HTTPS
[ https://issues.apache.org/jira/browse/AMBARI-23949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-23949: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Accessing Swagger API when Ambari Server is configured for HTTPS > > > Key: AMBARI-23949 > URL: https://issues.apache.org/jira/browse/AMBARI-23949 > Project: Ambari > Issue Type: Bug > Components: ambari-sever, ambari-web >Affects Versions: 2.7.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The api-docs end-point is available but the Try button doesn't work when the > Ambari Server is configured for HTTPS. > STR: > # Install Ambari Server > # Use /api-docs Try button on any API and notice that it works > # Configure Ambari Server to use SSL on port 8443 > # Try to use /api-docs Try button now and notice it picks up the right port > (8443) but the protocol is (http://) instead of (https://) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23968) Log Search portal has too many open sessions with Ambari
[ https://issues.apache.org/jira/browse/AMBARI-23968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494144#comment-16494144 ] Hudson commented on AMBARI-23968: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9355 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9355/]) AMBARI-23968. Log Search portal has too many open sessions with Ambari. (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=575f126295177297ff43e4d602d5efb4e8fed5d9]) * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/SecurityConfig.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/web/filters/LogsearchKRBAuthenticationFilter.java > Log Search portal has too many open sessions with Ambari > - > > Key: AMBARI-23968 > URL: https://issues.apache.org/jira/browse/AMBARI-23968 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23969) UI should load stack services from multiple mpacks
[ https://issues.apache.org/jira/browse/AMBARI-23969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-23969. -- Resolution: Fixed > UI should load stack services from multiple mpacks > -- > > Key: AMBARI-23969 > URL: https://issues.apache.org/jira/browse/AMBARI-23969 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Currently Ambari Web loads stack services from a single stack (eg: HDP). But > in a multi-mpack environment this behavior needs to change to get stack > services from all mpacks which are being used for installing services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23971) Capacity Scheduler View: Not allowed to set a queue/leafs to 0% capacity
[ https://issues.apache.org/jira/browse/AMBARI-23971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Roberts updated AMBARI-23971: -- Summary: Capacity Scheduler View: Not allowed to set a queue/leafs to 0% capacity (was: Capacity Scheduler View: Not allowed to set a sub-queue to 0% capacity) > Capacity Scheduler View: Not allowed to set a queue/leafs to 0% capacity > > > Key: AMBARI-23971 > URL: https://issues.apache.org/jira/browse/AMBARI-23971 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.2 >Reporter: Sean Roberts >Priority: Major > > The "Capacity Scheduler" View doesn't allow setting queues or sub-queues to > 0%. Setting to 0% is a valid configuration and use case in YARN. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23971) Capacity Scheduler View: Not allowed to set a sub-queue to 0% capacity
Sean Roberts created AMBARI-23971: - Summary: Capacity Scheduler View: Not allowed to set a sub-queue to 0% capacity Key: AMBARI-23971 URL: https://issues.apache.org/jira/browse/AMBARI-23971 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.6.2 Reporter: Sean Roberts The "Capacity Scheduler" View doesn't allow setting queues or sub-queues to 0%. Setting to 0% is a valid configuration and use case in YARN. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23971) Capacity Scheduler View: Not allowed to set a sub-queue to 0% capacity
[ https://issues.apache.org/jira/browse/AMBARI-23971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Roberts updated AMBARI-23971: -- Attachment: (was: image-2018-05-29-20-28-14-975.png) > Capacity Scheduler View: Not allowed to set a sub-queue to 0% capacity > -- > > Key: AMBARI-23971 > URL: https://issues.apache.org/jira/browse/AMBARI-23971 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.2 >Reporter: Sean Roberts >Priority: Major > > The "Capacity Scheduler" View doesn't allow setting queues or sub-queues to > 0%. Setting to 0% is a valid configuration and use case in YARN. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23971) Capacity Scheduler View: Not allowed to set a sub-queue to 0% capacity
[ https://issues.apache.org/jira/browse/AMBARI-23971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Roberts updated AMBARI-23971: -- Attachment: (was: image-2018-05-29-20-28-04-845.png) > Capacity Scheduler View: Not allowed to set a sub-queue to 0% capacity > -- > > Key: AMBARI-23971 > URL: https://issues.apache.org/jira/browse/AMBARI-23971 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.2 >Reporter: Sean Roberts >Priority: Major > > The "Capacity Scheduler" View doesn't allow setting queues or sub-queues to > 0%. Setting to 0% is a valid configuration and use case in YARN. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23970) Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver fails to start because DN's are not up
Vivek Rathod created AMBARI-23970:
-
Summary: Broken RCO in Add Namespace Wizards Restart Required
Services, Hiveserver fails to start because DN's are not up
Key: AMBARI-23970
URL: https://issues.apache.org/jira/browse/AMBARI-23970
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Vivek Rathod
Fix For: 2.7.0
Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver fails
to start because DN's are not up
{code}
{ "RemoteException": {"exception": "IOException", "javaClassName":
"java.io.IOException", "message": "Failed to find datanode, suggest to
check cluster health. excludeDatanodes=null" }
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23969) UI should load stack services from multiple mpacks
[ https://issues.apache.org/jira/browse/AMBARI-23969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23969: Labels: pull-request-available (was: ) > UI should load stack services from multiple mpacks > -- > > Key: AMBARI-23969 > URL: https://issues.apache.org/jira/browse/AMBARI-23969 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > Currently Ambari Web loads stack services from a single stack (eg: HDP). But > in a multi-mpack environment this behavior needs to change to get stack > services from all mpacks which are being used for installing services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23969) UI should load stack services from multiple mpacks
Ishan Bhatt created AMBARI-23969: Summary: UI should load stack services from multiple mpacks Key: AMBARI-23969 URL: https://issues.apache.org/jira/browse/AMBARI-23969 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 3.0.0 Currently Ambari Web loads stack services from a single stack (eg: HDP). But in a multi-mpack environment this behavior needs to change to get stack services from all mpacks which are being used for installing services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23968) Log Search portal has too many open sessions with Ambari
[ https://issues.apache.org/jira/browse/AMBARI-23968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23968: Labels: pull-request-available (was: ) > Log Search portal has too many open sessions with Ambari > - > > Key: AMBARI-23968 > URL: https://issues.apache.org/jira/browse/AMBARI-23968 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23968) Log Search portal has too many open sessions with Ambari
Olivér Szabó created AMBARI-23968: - Summary: Log Search portal has too many open sessions with Ambari Key: AMBARI-23968 URL: https://issues.apache.org/jira/browse/AMBARI-23968 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23964) Disable Kerberos has the wrong styles
[ https://issues.apache.org/jira/browse/AMBARI-23964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493836#comment-16493836 ] Hudson commented on AMBARI-23964: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9354 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9354/]) AMBARI-23964. Disable Kerberos has the wrong styles (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1af26043d8de792bc4b5f588944776e6e9cf7911]) * (edit) ambari-web/app/routes/main.js * (edit) ambari-web/app/styles/modal_popups.less > Disable Kerberos has the wrong styles > - > > Key: AMBARI-23964 > URL: https://issues.apache.org/jira/browse/AMBARI-23964 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: DisableKerberos.jpg > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23967) Dashboard,component information for few componets is not able to load after Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-23967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493837#comment-16493837 ] Hudson commented on AMBARI-23967: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9354 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9354/]) AMBARI-23967. Dashboard,component information for few componets is not (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7b893f083bf476c5179d182b034fed59192ed53a]) * (edit) ambari-web/app/mappers/service_metrics_mapper.js > Dashboard,component information for few componets is not able to load after > Ambari Upgrade > -- > > Key: AMBARI-23967 > URL: https://issues.apache.org/jira/browse/AMBARI-23967 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > 1) Upgrade Ambari from 2.6.1.5 to 2.7.0.0 > 2) Upgrade Ambari Infra and Logsearch > Post this, Ambari Dashboard is unable to load. Also for many components , the > component information is missing. Actions Menu keeps loading on clicking. > Quick links also do not load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23967) Dashboard,component information for few componets is not able to load after Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-23967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-23967. -- Resolution: Fixed > Dashboard,component information for few componets is not able to load after > Ambari Upgrade > -- > > Key: AMBARI-23967 > URL: https://issues.apache.org/jira/browse/AMBARI-23967 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > 1) Upgrade Ambari from 2.6.1.5 to 2.7.0.0 > 2) Upgrade Ambari Infra and Logsearch > Post this, Ambari Dashboard is unable to load. Also for many components , the > component information is missing. Actions Menu keeps loading on clicking. > Quick links also do not load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23962) Improvements for credential_store_helper to include all features
[ https://issues.apache.org/jira/browse/AMBARI-23962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493721#comment-16493721 ] Hudson commented on AMBARI-23962: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9353 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9353/]) [AMBARI-23962] Improvements for credential_store_helper to include all (m.magyar3: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=9a728ffb083ee7de6dd46a8973df5517cd241d18]) * (edit) ambari-common/src/main/python/ambari_commons/credential_store_helper.py > Improvements for credential_store_helper to include all features > > > Key: AMBARI-23962 > URL: https://issues.apache.org/jira/browse/AMBARI-23962 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Amer Issa >Priority: Major > Labels: pull-request-available > Time Spent: 2h 10m > Remaining Estimate: 0h > > CredentialApi.jar includes features: > # Create Alias and password > # Get Password > # Delete Alias > # List Alias > However, the python wrapper only has the get password feature. > > This adds all of the above features and be used by other python scripts -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23964) Disable Kerberos has the wrong styles
[ https://issues.apache.org/jira/browse/AMBARI-23964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23964: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Disable Kerberos has the wrong styles > - > > Key: AMBARI-23964 > URL: https://issues.apache.org/jira/browse/AMBARI-23964 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: DisableKerberos.jpg > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23967) Dashboard,component information for few componets is not able to load after Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-23967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23967: Labels: pull-request-available (was: ) > Dashboard,component information for few componets is not able to load after > Ambari Upgrade > -- > > Key: AMBARI-23967 > URL: https://issues.apache.org/jira/browse/AMBARI-23967 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > > 1) Upgrade Ambari from 2.6.1.5 to 2.7.0.0 > 2) Upgrade Ambari Infra and Logsearch > Post this, Ambari Dashboard is unable to load. Also for many components , the > component information is missing. Actions Menu keeps loading on clicking. > Quick links also do not load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22642) LDAPS sync Connection Refused
[
https://issues.apache.org/jira/browse/AMBARI-22642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493645#comment-16493645
]
David F. Quiroga commented on AMBARI-22642:
---
New [PR #1398|https://github.com/apache/ambari/pull/1398]
> LDAPS sync Connection Refused
> --
>
> Key: AMBARI-22642
> URL: https://issues.apache.org/jira/browse/AMBARI-22642
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
> Environment: java version "1.8.0_121"
> Java(TM) SE Runtime Environment (build 1.8.0_121-tdc1-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
> AD Domain Controllers
> LDAP v.3
> 2012 R2 OS
>Reporter: David F. Quiroga
>Assignee: David F. Quiroga
>Priority: Minor
> Labels: easyfix, patch, pull-request-available
> Fix For: 2.7.0
>
> Attachments: ambari-22642.patch
>
> Original Estimate: 24h
> Time Spent: 2h 40m
> Remaining Estimate: 21h 20m
>
> Ambari server configured to use "secure" ldap authentication.
> authentication.ldap.primaryUrl=:636
> authentication.ldap.useSSL=true
> We call the ldap_sync_events REST endpoint frequently to synchronize
> existing groups and a specific list groups. We had no issues with this until
> mid-October at which point we began to see:
> {code}
> "status" : "ERROR",
> "status_detail" : "Caught exception running LDAP sync. simple bind
> failed: **:636; nested exception is
> javax.naming.CommunicationException: simple bind failed: **:636 [Root
> exception is java.net.SocketException: Connection reset]",
> {code}
> Troubleshooting:
> * We saw random success and failure when attempting to sync a single group.
> * With useSSL=false and an updated port ldap sync was consistently successful.
> Cause:
> * By default, ldap connection only uses pooled connections when connecting to
> a directory server over LDAP. Enabling SSL causes it to disable the pooling,
> resulting in poorer performance and failures due to connection resets.
> * Around mid-October we increased the number of groups defined on the system
> (50+), this pushed us outside the "safe zone".
> Fix:
> Enable the SSL connections pooling by adding the below argument to startup
> options.
> -Dcom.sun.jndi.ldap.connect.pool.protocol='plain ssl'
> Reference:
> [https://confluence.atlassian.com/jirakb/connecting-jira-to-active-directory-over-ldaps-fails-with-connection-reset-763004137.htm]
> [https://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23967) Dashboard,component information for few componets is not able to load after Ambari Upgrade
Aleksandr Kovalenko created AMBARI-23967: Summary: Dashboard,component information for few componets is not able to load after Ambari Upgrade Key: AMBARI-23967 URL: https://issues.apache.org/jira/browse/AMBARI-23967 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 1) Upgrade Ambari from 2.6.1.5 to 2.7.0.0 2) Upgrade Ambari Infra and Logsearch Post this, Ambari Dashboard is unable to load. Also for many components , the component information is missing. Actions Menu keeps loading on clicking. Quick links also do not load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23920) Ambari 2way SSL does not work if CA signed certs are used
[
https://issues.apache.org/jira/browse/AMBARI-23920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493566#comment-16493566
]
Hudson commented on AMBARI-23920:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9352 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9352/])
[AMBARI-23920] Ambari 2way SSL does not work if CA signed certs are used
(rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=36e41b962c08173227bdc6e140228cb9eef72981])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/unsecured/rest/CertificateDownload.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/security/CertificateManagerTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/CertificateManager.java
> Ambari 2way SSL does not work if CA signed certs are used
> -
>
> Key: AMBARI-23920
> URL: https://issues.apache.org/jira/browse/AMBARI-23920
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: amarnath reddy pappu
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Enable 2 way SSL between Ambari server and agent using CA Signed
> certificates. Communication fails with below error/Exception
> {noformat}
> ERROR 2018-05-21 15:57:35,357 Controller.py:226 - Unable to connect to:
> https://apappu4.hdp.com:8441/agent/v1/register/apappu4.hdp.com
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line
> 175, in registerWithServer
> ret = self.sendRequest(self.registerUrl, data)
> File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line
> 549, in sendRequest
> raise IOError('Request to {0} failed due to {1}'.format(url,
> str(exception)))
> IOError: Request to
> https://apappu4.hdp.com:8441/agent/v1/register/apappu4.hdp.com failed due to
> [Errno 1] _ssl.c:492: error:14090086:SSL
> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
> ERROR 2018-05-21 15:57:35,357 Controller.py:227 - Error:Request to
> https://apappu4.hdp.com:8441/agent/v1/register/apappu4.hdp.com failed due to
> [Errno 1] _ssl.c:492: error:14090086:SSL
> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
> {noformat}
> Root cause: As part of the setup - CA Root and CA Cert chains are imported to
> PKCS file. but Ambari server is not pushing these root/chain to Ambari agents
> and Agents are unable to trust the server certs.
> *+Workaround:+*
> Combine certs, Chains, root and then copy to agent hosts.
> {noformat}
> cat certchain.pem servercert.pem root.pem > caroot.pem
> {noformat}
> then copy this file to
> {noformat}
> cp caroot.pem /var/lib/ambari-agent/keys/ca.crt
> {noformat}
> Restarting agent should resolve the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23966) Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP 3.0
[ https://issues.apache.org/jira/browse/AMBARI-23966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-23966: --- Status: Patch Available (was: Open) > Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP 3.0 > --- > > Key: AMBARI-23966 > URL: https://issues.apache.org/jira/browse/AMBARI-23966 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP 3.0 > Configuration changes/ any data migration changes needed to upgrade using > express from HDP 2.6 to HDP 3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23966) Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP 3.0
[ https://issues.apache.org/jira/browse/AMBARI-23966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23966: Labels: pull-request-available (was: ) > Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP 3.0 > --- > > Key: AMBARI-23966 > URL: https://issues.apache.org/jira/browse/AMBARI-23966 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > > Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP 3.0 > Configuration changes/ any data migration changes needed to upgrade using > express from HDP 2.6 to HDP 3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23966) Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP 3.0
Vitaly Brodetskyi created AMBARI-23966: -- Summary: Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP 3.0 Key: AMBARI-23966 URL: https://issues.apache.org/jira/browse/AMBARI-23966 Project: Ambari Issue Type: Bug Components: ambari-sever Affects Versions: 2.7.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Fix For: 2.7.0 Upgrade Spark/Zeppelin/Livy from HDP 2.6 to HDP 3.0 Configuration changes/ any data migration changes needed to upgrade using express from HDP 2.6 to HDP 3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23963) Logfeeder errors out with OOM GC overhead limit exceeded (~500 MB LRU cache size)
[ https://issues.apache.org/jira/browse/AMBARI-23963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493526#comment-16493526 ] Hudson commented on AMBARI-23963: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9351 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9351/]) AMBARI-23963. Logfeeder errors out with OOM GC overhead limit exceeded (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=e410e8c8370430e82105dd371038b77078af8d91]) * (edit) ambari-logsearch/ambari-logsearch-logfeeder-plugin-api/src/main/java/org/apache/ambari/logfeeder/plugin/input/cache/LRUCache.java > Logfeeder errors out with OOM GC overhead limit exceeded (~500 MB LRU cache > size) > - > > Key: AMBARI-23963 > URL: https://issues.apache.org/jira/browse/AMBARI-23963 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23965) Unable to add new members to LDAP Group via UI
[ https://issues.apache.org/jira/browse/AMBARI-23965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493503#comment-16493503 ] Robert Levas commented on AMBARI-23965: --- [~aantonenko] is a user supposed to be able to do this? LDAP groups should be managed by the LDAP server via the LDAP sync process. By manually changing an LDAP group Ambari becomes out of sync with the configured LDAP server and will be reverted back once an LDAP sync operation is executed. > Unable to add new members to LDAP Group via UI > -- > > Key: AMBARI-23965 > URL: https://issues.apache.org/jira/browse/AMBARI-23965 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23920) Ambari 2way SSL does not work if CA signed certs are used
[
https://issues.apache.org/jira/browse/AMBARI-23920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-23920.
---
Resolution: Fixed
> Ambari 2way SSL does not work if CA signed certs are used
> -
>
> Key: AMBARI-23920
> URL: https://issues.apache.org/jira/browse/AMBARI-23920
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: amarnath reddy pappu
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Enable 2 way SSL between Ambari server and agent using CA Signed
> certificates. Communication fails with below error/Exception
> {noformat}
> ERROR 2018-05-21 15:57:35,357 Controller.py:226 - Unable to connect to:
> https://apappu4.hdp.com:8441/agent/v1/register/apappu4.hdp.com
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line
> 175, in registerWithServer
> ret = self.sendRequest(self.registerUrl, data)
> File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line
> 549, in sendRequest
> raise IOError('Request to {0} failed due to {1}'.format(url,
> str(exception)))
> IOError: Request to
> https://apappu4.hdp.com:8441/agent/v1/register/apappu4.hdp.com failed due to
> [Errno 1] _ssl.c:492: error:14090086:SSL
> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
> ERROR 2018-05-21 15:57:35,357 Controller.py:227 - Error:Request to
> https://apappu4.hdp.com:8441/agent/v1/register/apappu4.hdp.com failed due to
> [Errno 1] _ssl.c:492: error:14090086:SSL
> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
> {noformat}
> Root cause: As part of the setup - CA Root and CA Cert chains are imported to
> PKCS file. but Ambari server is not pushing these root/chain to Ambari agents
> and Agents are unable to trust the server certs.
> *+Workaround:+*
> Combine certs, Chains, root and then copy to agent hosts.
> {noformat}
> cat certchain.pem servercert.pem root.pem > caroot.pem
> {noformat}
> then copy this file to
> {noformat}
> cp caroot.pem /var/lib/ambari-agent/keys/ca.crt
> {noformat}
> Restarting agent should resolve the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23957) Spark2 Thrift Server fails to start if LLAP and parallel execution are enabled
[
https://issues.apache.org/jira/browse/AMBARI-23957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493496#comment-16493496
]
Hudson commented on AMBARI-23957:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9350 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9350/])
AMBARI-23957. Spark2 Thrift Server fails to start if LLAP and parallel (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=40eae549c564d9fbc632bfd4bb6d2dfa5541d3b0])
* (edit) ambari-server/src/main/resources/stacks/HDP/2.5/role_command_order.json
> Spark2 Thrift Server fails to start if LLAP and parallel execution are enabled
> --
>
> Key: AMBARI-23957
> URL: https://issues.apache.org/jira/browse/AMBARI-23957
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> STR:
> # Enable parallel execution in Ambari Agent
> # Deploy cluster via blueprint, placing Spark2 Thrift Server on the same node
> as Hive Server Interactive
> Result: Spark2 Thrift Server runs into the following error during startup:
> {noformat}
> ZooKeeperHiveClientException: Unable to read HiveServer2 configs from
> ZooKeeper
> ...
> KeeperErrorCode = NoNode for /hiveserver2-hive2
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23963) Logfeeder errors out with OOM GC overhead limit exceeded (~500 MB LRU cache size)
[ https://issues.apache.org/jira/browse/AMBARI-23963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23963. --- Resolution: Fixed > Logfeeder errors out with OOM GC overhead limit exceeded (~500 MB LRU cache > size) > - > > Key: AMBARI-23963 > URL: https://issues.apache.org/jira/browse/AMBARI-23963 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23965) Unable to add new members to LDAP Group via UI
[ https://issues.apache.org/jira/browse/AMBARI-23965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23965: Labels: pull-request-available (was: ) > Unable to add new members to LDAP Group via UI > -- > > Key: AMBARI-23965 > URL: https://issues.apache.org/jira/browse/AMBARI-23965 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23965) Unable to add new members to LDAP Group via UI
[ https://issues.apache.org/jira/browse/AMBARI-23965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23965: Assignee: Antonenko Alexander > Unable to add new members to LDAP Group via UI > -- > > Key: AMBARI-23965 > URL: https://issues.apache.org/jira/browse/AMBARI-23965 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23965) Unable to add new members to LDAP Group via UI
Antonenko Alexander created AMBARI-23965: Summary: Unable to add new members to LDAP Group via UI Key: AMBARI-23965 URL: https://issues.apache.org/jira/browse/AMBARI-23965 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23964) Disable Kerberos has the wrong styles
[ https://issues.apache.org/jira/browse/AMBARI-23964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23964: - Attachment: DisableKerberos.jpg > Disable Kerberos has the wrong styles > - > > Key: AMBARI-23964 > URL: https://issues.apache.org/jira/browse/AMBARI-23964 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: DisableKerberos.jpg > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23964) Disable Kerberos has the wrong styles
[ https://issues.apache.org/jira/browse/AMBARI-23964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23964: - Status: Patch Available (was: Open) > Disable Kerberos has the wrong styles > - > > Key: AMBARI-23964 > URL: https://issues.apache.org/jira/browse/AMBARI-23964 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: DisableKerberos.jpg > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23964) Disable Kerberos has the wrong styles
[ https://issues.apache.org/jira/browse/AMBARI-23964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23964: Labels: pull-request-available (was: ) > Disable Kerberos has the wrong styles > - > > Key: AMBARI-23964 > URL: https://issues.apache.org/jira/browse/AMBARI-23964 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23964) Disable Kerberos has the wrong styles
[ https://issues.apache.org/jira/browse/AMBARI-23964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23964: Assignee: Antonenko Alexander > Disable Kerberos has the wrong styles > - > > Key: AMBARI-23964 > URL: https://issues.apache.org/jira/browse/AMBARI-23964 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23964) Disable Kerberos has the wrong styles
Antonenko Alexander created AMBARI-23964: Summary: Disable Kerberos has the wrong styles Key: AMBARI-23964 URL: https://issues.apache.org/jira/browse/AMBARI-23964 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23943) Hiveserver2 fails to start on viewFS enabled cluster: {hive_server2_zookeeper_namespace} is not ready yet
[
https://issues.apache.org/jira/browse/AMBARI-23943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493436#comment-16493436
]
Hudson commented on AMBARI-23943:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9349 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9349/])
AMBARI-23943. Hiveserver2 fails to start on viewFS enabled cluster (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=70f95fa544211d7e87b8910e8f099540f02f491b])
* (edit)
ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
* (edit) ambari-server/src/test/python/stacks/2.5/ZEPPELIN/test_zeppelin_060.py
* (edit) ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py
* (edit)
ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py
* (edit) ambari-server/src/test/python/common-services/HAWQ/test_hawqmaster.py
* (edit)
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/SLIDER/0.60.0.2.2/package/scripts/params_linux.py
* (edit) ambari-server/src/test/python/stacks/2.6/ZEPPELIN/test_zeppelin_070.py
* (edit)
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/PXF/3.0.0/package/scripts/params.py
* (edit)
ambari-agent/src/test/python/ambari_agent/dummy_files/alert_definitions.json
* (edit)
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0/package/scripts/params.py
> Hiveserver2 fails to start on viewFS enabled cluster:
> {hive_server2_zookeeper_namespace} is not ready yet
> -
>
> Key: AMBARI-23943
> URL: https://issues.apache.org/jira/browse/AMBARI-23943
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23943.patch, AMBARI-23943.patch,
> AMBARI-23943.patch, AMBARI-23943.patch, AMBARI-23943.patch
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> * Tried to deploy a cluster with viewFS enabled via blueprint
> * HiveServer2 is failing to start with below error
>
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 137, in
> HiveServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 53, in start
> hive_service('hiveserver2', action = 'start',
> upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_service.py",
> line 102, in hive_service
> wait_for_znode()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/decorator.py",
> line 62, in wrapper
> return function(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_service.py",
> line 191, in wait_for_znode
> raise Fail(format("ZooKeeper node /{hive_server2_zookeeper_namespace}
> is not ready yet"))
> resource_management.core.exceptions.Fail: ZooKeeper node /hiveserver2 is
> not ready yet
>
> out log has a reference to hdfs:// Filesystem
>
>
> 2018-05-17 23:54:17,398 - Skipping fs root check as fs_root does not
> start with hdfs://
> 2018-05-17 23:54:17,399 -
> Execute['/var/lib/ambari-agent/tmp/start_hiveserver2_script
> /grid/0/log/hive/hive-server2.out /grid/0/log/hive/hive-server2.err
> /var/run/hive/hive-server.pid /usr/hdp/current/hive-server2/conf/
> /grid/0/log/hive'] {'environment': {'HIVE_BIN': 'hive', 'JAVA_HOME':
> u'/usr/lib/jvm/java-openjdk', 'HADOOP_HOME':
> u'/usr/hdp/current/hadoop-client'}, 'not_if': 'ls
> /var/run/hive/hive-server.pid >/dev/null 2>&1 && ps -p >/dev/null 2>&1',
> 'user': 'hive', 'path':
>
[jira] [Updated] (AMBARI-23963) Logfeeder errors out with OOM GC overhead limit exceeded (~500 MB LRU cache size)
[ https://issues.apache.org/jira/browse/AMBARI-23963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23963: Labels: pull-request-available (was: ) > Logfeeder errors out with OOM GC overhead limit exceeded (~500 MB LRU cache > size) > - > > Key: AMBARI-23963 > URL: https://issues.apache.org/jira/browse/AMBARI-23963 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23943) Hiveserver2 fails to start on viewFS enabled cluster: {hive_server2_zookeeper_namespace} is not ready yet
[
https://issues.apache.org/jira/browse/AMBARI-23943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-23943:
-
Attachment: AMBARI-23943.patch
> Hiveserver2 fails to start on viewFS enabled cluster:
> {hive_server2_zookeeper_namespace} is not ready yet
> -
>
> Key: AMBARI-23943
> URL: https://issues.apache.org/jira/browse/AMBARI-23943
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23943.patch, AMBARI-23943.patch,
> AMBARI-23943.patch, AMBARI-23943.patch, AMBARI-23943.patch
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> * Tried to deploy a cluster with viewFS enabled via blueprint
> * HiveServer2 is failing to start with below error
>
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 137, in
> HiveServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 53, in start
> hive_service('hiveserver2', action = 'start',
> upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_service.py",
> line 102, in hive_service
> wait_for_znode()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/decorator.py",
> line 62, in wrapper
> return function(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_service.py",
> line 191, in wait_for_znode
> raise Fail(format("ZooKeeper node /{hive_server2_zookeeper_namespace}
> is not ready yet"))
> resource_management.core.exceptions.Fail: ZooKeeper node /hiveserver2 is
> not ready yet
>
> out log has a reference to hdfs:// Filesystem
>
>
> 2018-05-17 23:54:17,398 - Skipping fs root check as fs_root does not
> start with hdfs://
> 2018-05-17 23:54:17,399 -
> Execute['/var/lib/ambari-agent/tmp/start_hiveserver2_script
> /grid/0/log/hive/hive-server2.out /grid/0/log/hive/hive-server2.err
> /var/run/hive/hive-server.pid /usr/hdp/current/hive-server2/conf/
> /grid/0/log/hive'] {'environment': {'HIVE_BIN': 'hive', 'JAVA_HOME':
> u'/usr/lib/jvm/java-openjdk', 'HADOOP_HOME':
> u'/usr/hdp/current/hadoop-client'}, 'not_if': 'ls
> /var/run/hive/hive-server.pid >/dev/null 2>&1 && ps -p >/dev/null 2>&1',
> 'user': 'hive', 'path':
> [u'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/var/lib/ambari-agent:/usr/hdp/current/hive-server2/bin:/usr/hdp/3.0.0.0-1345/hadoop/bin']}
> 2018-05-17 23:54:17,507 - Execute['/usr/lib/jvm/java-openjdk/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/hive-server2/lib/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://ctr-e138-1518143905142-317960-01-06.hwx.site/hivedb?createDatabaseIfNotExist=true'
> hiveuser [PROTECTED] com.mysql.jdbc.Driver'] {'path':
> ['/usr/sbin:/sbin:/usr/local/bin:/bin:/usr/bin'], 'tries': 5, 'try_sleep': 10}
> 2018-05-17 23:54:18,156 -
> call['/usr/hdp/current/zookeeper-client/bin/zkCli.sh -server
> ctr-e138-1518143905142-317960-01-05.hwx.site:2181,ctr-e138-1518143905142-317960-01-06.hwx.site:2181,ctr-e138-1518143905142-317960-01-07.hwx.site:2181
> ls /hiveserver2 | grep '\[serverUri=''] {}
> 2018-05-17 23:54:19,032 - call returned (1, 'Node does not exist:
> /hiveserver2')
> 2018-05-17 23:54:19,033 - Will retry 29 time(s), caught exception:
> ZooKeeper node /hiveserver2 is not ready yet. Sleeping for 5 sec(s)
> 2018-05-17 23:54:24,038 -
> call['/usr/hdp/current/zookeeper-client/bin/zkCli.sh -server
> ctr-e138-1518143905142-317960-01-05.hwx.site:2181,ctr-e138-1518143905142-317960-01-06.hwx.site:2181,ctr-e138-1518143905142-317960-01-07.hwx.site:2181
> ls /hiveserver2 | grep '\[serverUri=''] {}
> 2018-05-17 23:54:24,842 - call returned (1, 'Node does not exist:
> /hiveserver2')
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23960) Change HDFS Daemon Commands For HDP 3.0
[
https://issues.apache.org/jira/browse/AMBARI-23960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko resolved AMBARI-23960.
--
Resolution: Fixed
> Change HDFS Daemon Commands For HDP 3.0
> ---
>
> Key: AMBARI-23960
> URL: https://issues.apache.org/jira/browse/AMBARI-23960
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
>
> Some hadoop start commands are deprecated and need to be changed. For example:
> {code}
> 'export HADOOP_LIBEXEC_DIR=/usr/hdp/3.0.0.0-1329/hadoop/libexec &&
> /usr/hdp/3.0.0.0-1329/hadoop-yarn/sbin/yarn-daemon.sh --config
> /usr/hdp/3.0.0.0-1329/hadoop/conf stop nodemanager' returned 1.
> WARNING: Use of this script to start YARN daemons is deprecated.
> WARNING: Attempting to execute replacement "yarn --daemon start" instead.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
