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/05/17 15:21:00 UTC

[jira] [Commented] (AMBARI-23879) Redo the Manage Journalnodes wizard in the context of federation changes

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

Hudson commented on AMBARI-23879:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9277 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9277/])
AMBARI-23879 Redo the Manage Journalnodes wizard in the context of (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=9671dd17d83d39589cb05e830ecaffcf2a025086])
* (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/step7.hbs
* (delete) ambari-web/app/templates/main/admin/highAvailability/journalNode/step8.hbs
* (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step4_controller.js
* (edit) ambari-web/test/controllers/main/admin/highAvailability/journalNode/step6_controller_test.js
* (edit) ambari-web/app/controllers.js
* (edit) ambari-web/app/views.js
* (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/step3.hbs
* (edit) ambari-web/test/controllers/main/admin/highAvailability/journalNode/step7_controller_test.js
* (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/step5.hbs
* (delete) ambari-web/test/controllers/main/admin/highAvailability/journalNode/step8_controller_test.js
* (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step7_controller.js
* (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step5_controller.js
* (edit) ambari-web/app/routes/manage_journalnode_routes.js
* (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/wizard.hbs
* (edit) ambari-web/app/messages.js
* (edit) ambari-web/app/assets/test/tests.js
* (edit) ambari-web/test/controllers/main/admin/highAvailability/journalNode/step4_controller_test.js
* (edit) ambari-web/app/views/main/admin/highAvailability/journalNode/step7_view.js
* (delete) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step8_controller.js
* (delete) ambari-web/app/views/main/admin/highAvailability/journalNode/step8_view.js
* (edit) ambari-web/app/views/main/admin/highAvailability/journalNode/step5_view.js
* (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step1_controller.js
* (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step6_controller.js
* (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/wizard_controller.js


> Redo the Manage Journalnodes wizard in the context of federation changes
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-23879
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23879
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.7.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> STR: Deploy a cluster with multiple namespaces via Blueprint
> Add JournalNode using the wizard
> In the format JN step {code}sudo su cstm-hdfs -l -c 'hdfs namenode -initializeSharedEdits'{code} fails with 
> {code}
> Re-format filesystem in QJM to [<ip0>:8485, <ip1>:8485, <ip2>:8485] ? (Y or N) y
> 18/05/09 18:43:02 ERROR namenode.NameNode: Could not initialize shared edits dir
> org.apache.hadoop.hdfs.qjournal.client.QuorumException: Could not format one or more JournalNodes. 1 exceptions thrown:
> <ip0>:8485: Directory /hadoop/hdfs/journal/ns1 is in an inconsistent state: Can't format the storage directory because the current directory is not empty.
> 	at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.checkEmptyCurrent(Storage.java:600)
> 	at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.analyzeStorage(Storage.java:683)
> 	at org.apache.hadoop.hdfs.qjournal.server.JNStorage.format(JNStorage.java:210)
> 	at org.apache.hadoop.hdfs.qjournal.server.Journal.format(Journal.java:235)
> 	at org.apache.hadoop.hdfs.qjournal.server.JournalNodeRpcServer.format(JournalNodeRpcServer.java:181)
> 	at org.apache.hadoop.hdfs.qjournal.protocolPB.QJournalProtocolServerSideTranslatorPB.format(QJournalProtocolServerSideTranslatorPB.java:148)
> 	at org.apache.hadoop.hdfs.qjournal.protocol.QJournalProtocolProtos$QJournalProtocolService$2.callBlockingMethod(QJournalProtocolProtos.java:27399)
> 	at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:523)
> 	at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:991)
> 	at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:872)
> 	at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:818)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at javax.security.auth.Subject.doAs(Subject.java:422)
> 	at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1682)
> 	at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2678)
> 	at org.apache.hadoop.hdfs.qjournal.client.QuorumException.create(QuorumException.java:81)
> 	at org.apache.hadoop.hdfs.qjournal.client.QuorumCall.rethrowException(QuorumCall.java:286)
> 	at org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager.format(QuorumJournalManager.java:228)
> 	at org.apache.hadoop.hdfs.server.namenode.FSEditLog.formatNonFileJournals(FSEditLog.java:426)
> 	at org.apache.hadoop.hdfs.server.namenode.NameNode.initializeSharedEdits(NameNode.java:1262)
> 	at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1619)
> 	at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1710)
> 18/05/09 18:43:02 INFO util.ExitUtil: Exiting with status 1: ExitException
> 18/05/09 18:43:02 INFO namenode.NameNode: SHUTDOWN_MSG: 
> /************************************************************
> SHUTDOWN_MSG: Shutting down NameNode at <host0>/<ip0>
> ************************************************************/
> {code}
> Solution
> Reorganize wizard steps:
> - Assign Journalnodes
> - Save Namespace
> - Add/Remove Journalnodes (no start JN)
> - Copy Journalnode directories
> - Start Journalnodes
> - Start All Services



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