[
https://issues.apache.org/jira/browse/HDFS-11753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001008#comment-16001008
]
Doris Gu commented on HDFS-11753:
---------------------------------
Add some explanation about QA results, welcome suggestions.
1.test4tests
The patch is not that complicated, and can be verified by simple steps as
follows.
1.1 Add support -h for *hdfs journalnode*, since it only has general options, I
add a brief statement about journalnode followed the style of secondary
namenode.
1.2 I use *hdfs journalnode* with different config files, i.e. start
journalnode several times on one node, I get several journalnode daemons.
Details will be pasted soon.
2.checkstyle
Very meaningful, plan to make a new patch soon, but I haven't realized the
relationship with my patch, is there any opinions?
> Make Some Enhancements about JournalNode Daemon
> ------------------------------------------------
>
> Key: HDFS-11753
> URL: https://issues.apache.org/jira/browse/HDFS-11753
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: journal-node
> Affects Versions: 3.0.0-alpha2
> Reporter: Doris Gu
> Attachments: HDFS-11753.001.patch
>
>
> 1.Add support -h. Right now, if I use *hdfs journalnode -h* , I straightly
> start journalnode daemon. But generally speakingļ¼ I just want to look at the
> usage.
> 2.Add exception catch and termination. If I start journalnode with different
> directions stored pids, I get servel journalnode daemons that don't work for
> I config the same port.
> {quote}[hdfs@localhost ~]$ jps
> *10107 JournalNode*
> *46023 JournalNode*
> 57944 NameNode
> 46539 Jps
> 57651 DFSZKFailoverController
> 57909 DataNode
> *57739 JournalNode*
> *45721 JournalNode*{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
