[
https://issues.apache.org/jira/browse/HDDS-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17632068#comment-17632068
]
Sadanand Shenoy commented on HDDS-6126:
---------------------------------------
The feature is enabled in the acceptance test environment .
{code:java}
docker exec -it hadoop27_om_1 /bin/bash
bash-4.2$ ozone getconf -confKey dfs.container.ratis.datastream.enable
true
bash-4.2$ ozone getconf -confKey ozone.fs.datastream.enable
true {code}
{quote}Indeed, there is an NPE; filed HDDS-7478.
{quote}
Thanks [~szetszwo] for filing this issue , I have already fixed the NPE issue
in my test branch
([https://github.com/sadanand48/hadoop-ozone/commit/2baabe94369a83f0fa622c762876260ada2b341b])
and its unrelated to the acceptance test failure, I suspect it has to be
something to do with hadoop2 compatibility , will debug further.
> MR Acceptance test failure on Streaming Branch (HDDS-4454)
> ----------------------------------------------------------
>
> Key: HDDS-6126
> URL: https://issues.apache.org/jira/browse/HDDS-6126
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Sadanand Shenoy
> Assignee: Sadanand Shenoy
> Priority: Major
> Attachments: NM-jstack.txt, nm_logs.log
>
>
> The ozone MR Acceptance fails on the streaming branch if
> ozone.fs.datastream.enable is set to true.
> The test basically runs a yarn wordcount job and the observation here is
> that the job doesn’t release the Application master (AM container ) as soon
> as the job is done and the job counters are displayed which is why the second
> job waits for a long time ~10 min for the AM container to be released.
> Tried with enabling streaming and disabling streaming and verified that the
> problem occurs only when ozone.fs.datastream.enable=true
> {code:java}
> yarn jar
> /opt/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-examples-2.7.3.jar pi -D
> fs.defaultFS=o3fs://bucket1.volume1.om/ -D ozone.fs.datastream.enable=true
> 3 3{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
