[ 
https://issues.apache.org/jira/browse/HDDS-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz-wo Sze updated HDDS-6126:
-----------------------------
    Description: 
The following problem was discovered in the Streaming Branch (HDDS-4454).  The 
same problem can also be reproduced in the master branch.

----

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}

  was:
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}

        Summary: MR Acceptance test failure  (was: MR Acceptance test failure 
on Streaming Branch (HDDS-4454))

> MR Acceptance test failure
> --------------------------
>
>                 Key: HDDS-6126
>                 URL: https://issues.apache.org/jira/browse/HDDS-6126
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Sadanand Shenoy
>            Assignee: Sadanand Shenoy
>            Priority: Major
>         Attachments: NM-jstack.txt, nm_logs.log
>
>
> The following problem was discovered in the Streaming Branch (HDDS-4454).  
> The same problem can also be reproduced in the master branch.
> ----
> 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]

Reply via email to