[ 
https://issues.apache.org/jira/browse/HDFS-16551?focusedWorklogId=761392&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-761392
 ]

ASF GitHub Bot logged work on HDFS-16551:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/Apr/22 03:28
            Start Date: 24/Apr/22 03:28
    Worklog Time Spent: 10m 
      Work Description: prasad-acit commented on PR #4227:
URL: https://github.com/apache/hadoop/pull/4227#issuecomment-1107699554

   Thanks @jojochuang, failures not related to the changes done. 
   Also, i dont see any issue with the branch also. I can compile locally 
successfully. Issue is something related to build environment.
   Separate PR to be raised for branch 2.10? Or same can be cherry-picked?




Issue Time Tracking
-------------------

    Worklog Id:     (was: 761392)
    Time Spent: 1h 20m  (was: 1h 10m)

> Backport HADOOP-17588 to 3.3 and other active old branches.
> -----------------------------------------------------------
>
>                 Key: HDFS-16551
>                 URL: https://issues.apache.org/jira/browse/HDFS-16551
>             Project: Hadoop HDFS
>          Issue Type: Task
>            Reporter: Renukaprasad C
>            Assignee: Renukaprasad C
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.3.4
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> This random issue has been handled in trunk, same needs to be backported to 
> active branches.
> org.apache.hadoop.crypto.CryptoInputStream.close() - when 2 threads try to 
> close the stream second thread, fails with error.
> This operation should be synchronized to avoid multiple threads to perform 
> the close operation concurrently.
> [~Hemanth Boyina] 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

Reply via email to