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

Bharat Viswanadham edited comment on HDDS-665 at 10/16/18 10:37 PM:
--------------------------------------------------------------------

Thank You [~arpitagarwal] and [~elek] for reviews.

I have committed this to trunk and ozone-0.3

Ran smoke tests multiple times, they all are passing with the patch.

Attached the output of the smoke test run.

 


was (Author: bharatviswa):
Thank You [~arpitagarwal] and [~elek] for reviews.

I have committed this to trunk and ozone-0.3

Ran smoke tests multiple times, they all are passing with the patch.

 

> Add hdds.datanode.dir to docker-config
> --------------------------------------
>
>                 Key: HDDS-665
>                 URL: https://issues.apache.org/jira/browse/HDDS-665
>             Project: Hadoop Distributed Data Store
>          Issue Type: Task
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>             Fix For: 0.3.0, 0.4.0
>
>         Attachments: HDDS-665.00.patch, HDDS-665.01.patch, smoketest-run.txt
>
>
> Currently hdds.datanode.dir property is missing. So, datanode data dir is 
> pointing to location /tmp/<<dir>>/hdds.
>  
> Some times with this approach we can face issues, as this points to default 
> mount point from docker. On my local setup, because of this I am facing issue 
> like create container is failing with DISK full.
>  
> This also helps in knowing where the datanode dir location, instead of 
> guesswork /remembering default dfs.datanode.dir.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to