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

Nanda kumar commented on HDDS-216:
----------------------------------

[~bharatviswa], thanks for the catch. Yeah, you are right. we should not call 
{{setRandomContainerPort(false)}} while constructing {{MiniOzoneCluster}}.

Also in {{TestOzoneContainer#testCreateOzoneContainer}} 
{{conf.setBoolean(OzoneConfigKeys.DFS_CONTAINER_IPC_RANDOM_PORT, false)}} 
should be changed to 
{{conf.setBoolean(OzoneConfigKeys.DFS_CONTAINER_IPC_RANDOM_PORT, true)}}.

[~Sandeep Nemuri], can you also fix the same in this jira?

> hadoop-hdds unit tests should use randomized ports
> --------------------------------------------------
>
>                 Key: HDDS-216
>                 URL: https://issues.apache.org/jira/browse/HDDS-216
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: test
>            Reporter: Arpit Agarwal
>            Assignee: Sandeep Nemuri
>            Priority: Major
>              Labels: newbie, test
>             Fix For: 0.2.1
>
>         Attachments: HDDS-216.001.patch
>
>
> MiniOzoneCluster should use randomized ports by default, so individual tests 
> don't have to do anything to avoid port conflicts at runtime. e.g. 
> TestStorageContainerManagerHttpServer fails if port 9876 is in use.
> {code}
> [INFO] Running 
> org.apache.hadoop.hdds.scm.TestStorageContainerManagerHttpServer
> [ERROR] Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.084 
> s <<< FAILURE! - in 
> org.apache.hadoop.hdds.scm.TestStorageContainerManagerHttpServer
> [ERROR] 
> testHttpPolicy[0](org.apache.hadoop.hdds.scm.TestStorageContainerManagerHttpServer)
>   Time elapsed: 0.401 s  <<< ERROR!
> java.net.BindException: Port in use: 0.0.0.0:9876
> {code}



--
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