[
https://issues.apache.org/jira/browse/HDDS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518723#comment-16518723
]
Elek, Marton commented on HDDS-94:
----------------------------------
Thank you very much to do this [~Sandeep Nemuri].
I did a quick survey offline and asked multiple people. Most of the people
voted to use the datanode as the command line name of the standalone ozone
datanode. (ozone datanode instead of ozone hddsdn). I propose to replace the
original datanode subcommand instead of creataing hddsdn (sorry for not
including this info in the original description).
I also propose to update the docker-compose files:
./hadoop-ozone/acceptance-test/src/test/acceptance/basic/docker-compose.yaml
./hadoop-dist/src/main/compose/ozoneperf/docker-compose.yaml
./hadoop-dist/src/main/compose/ozone/docker-compose.yaml
The namenode service could be removed from them (they use "ozone datanode"
which should ok after the change). It could be done in other jira, but I prefer
to do this in one step to make it easier to test.
(BTW, I tested it with modifying the docker-compose files locally and it worked
very well).
Thanks, again.
> Change ozone datanode command to start the standalone datanode plugin
> ---------------------------------------------------------------------
>
> Key: HDDS-94
> URL: https://issues.apache.org/jira/browse/HDDS-94
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Reporter: Elek, Marton
> Assignee: Sandeep Nemuri
> Priority: Major
> Labels: newbie
> Fix For: 0.2.1
>
> Attachments: HDDS-94.001.patch
>
>
> The current ozone datanode command starts the regular hdfs datanode with an
> enabled HddsDatanodeService as a datanode plugin.
> The goal is to start only the HddsDatanodeService.java (main function is
> already there but GenericOptionParser should be adopted).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
