You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/04/30 16:59:00 UTC

[jira] [Commented] (AMBARI-23729) Start Namenodes takes a very long time when adding a namespace

    [ https://issues.apache.org/jira/browse/AMBARI-23729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458765#comment-16458765 ] 

Hudson commented on AMBARI-23729:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9150 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9150/])
AMBARI-23729. Start Namenodes takes a very long time when adding a (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=9ccad6359549f03f9e2f4e0b1ca244aaac88e3f6])
* (edit) ambari-web/app/messages.js
* (edit) ambari-web/app/controllers/main/admin/federation/step4_controller.js
* (edit) ambari-web/app/controllers/main/admin/federation/step1_controller.js


> Start Namenodes takes a very long time when adding a namespace
> --------------------------------------------------------------
>
>                 Key: AMBARI-23729
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23729
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.7.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> On newly added nn5 and nn6 I see the Start NN call waits for JMX to return, we are not starting Ranger so NN JMX does not respond. However there seems to be logic to skip the check if Ranger Admin is not up:
> {code}
> 2018-04-20 18:34:29,072 - RangeradminV2: Skip ranger admin if it's down !
> 2018-04-20 18:34:29,093 - checked_call['/usr/bin/kinit -c /var/lib/ambari-agent/tmp/curl_krb_cache/ranger_admin_calls_hdfs_cc_91f03cfb858cf8a975f355b846c7b45988d51543f0ec7ea2d1da3738 -kt /etc/security/keytabs/nn.service.keytab nn/ctr-e138-1518143905142-250606-01-000002.hwx.site@EXAMPLE.COM > /dev/null'] {'user': 'hdfs'}
> 2018-04-20 18:34:29,183 - checked_call returned (0, '')
> {code}
> Still we are waiting for a long time and them actually succeeding.
> If Ranger being up is needed please assign this appropriately to UI team to make sure we start required services before Starting NN. If the skip check is desired behavior we should be able to proceed in that case.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)