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

Andrei Mikhalev commented on HDDS-9768:
---------------------------------------

[~adoroszlai] , thanks a lot for reply. I tried to expose 9858 port for OM, but 
not for datanodes. So, now I realize the problem.

Thanks a lot!

I'll try and comment later

> Can't write file with OzoneClient RPC
> -------------------------------------
>
>                 Key: HDDS-9768
>                 URL: https://issues.apache.org/jira/browse/HDDS-9768
>             Project: Apache Ozone
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>         Environment: {*}OS{*}: Ubuntu 22.04.3 LTS,  {*}Arch{*}: 64-bit, 
> {*}Processor{*}: Intel Core i7-9750H CPU 2.6GHz x 12
> {*}OS{*}: Mac OS Ventura 13.2,  {*}Arch{*}: 64-bit, {*}Processor{*}: Intel 
> Core i9 CPU 2.3GHz x 8
>            Reporter: Andrei Mikhalev
>            Priority: Major
>         Attachments: err.log, om.log
>
>
> Try to wite a key following the docs 
> ([https://ozone.apache.org/docs/1.3.0/interface/javaapi.html)]
>  # Build apache/ozone locally as specified in 
> [https://github.com/apache/ozone/blob/master/CONTRIBUTING.md#build-the-project]
>  # Install local build to local maven (.m2)
>  # Run pseudo cluster 
> [https://github.com/apache/ozone/blob/master/CONTRIBUTING.md#running-ozone-in-docker]
>  # Run sample to a key ([https://github.com/Montura/ozone_test_client])
>  
> Faced with problems: _OzoneOutputStream_ couldn't be closed, wait in 
> _RatisBlockOutputStream::waitOnFlushFutures()_
> !https://user-images.githubusercontent.com/4503006/285421762-3b866f47-eb5e-4c1b-9f55-523ee30f78d7.png|width=958,height=260!
> _Sample output is attatched:_ *err.log*
> _Ozone manager log:_ *om.log*



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to