[
https://issues.apache.org/jira/browse/HADOOP-17779?focusedWorklogId=618768&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-618768
]
ASF GitHub Bot logged work on HADOOP-17779:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jul/21 19:48
Start Date: 05/Jul/21 19:48
Worklog Time Spent: 10m
Work Description: steveloughran commented on pull request #3158:
URL: https://github.com/apache/hadoop/pull/3158#issuecomment-874300831
why do we need to make it uninterruptible?
Is there a risk of problems if one thread is waiting for the semaphore and
the process is exited?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 618768)
Time Spent: 50m (was: 40m)
> Lock File System Creator Semaphore Uninterruptibly
> --------------------------------------------------
>
> Key: HADOOP-17779
> URL: https://issues.apache.org/jira/browse/HADOOP-17779
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Affects Versions: 3.3.1
> Reporter: David Mollitor
> Assignee: David Mollitor
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {{FileSystem}} "creator permits" are acquired in an interruptable way. This
> changed the behavior of the call because previous callers were handling the
> IOException as a critical error. An interrupt was handled in the typical
> {{InterruptedException}} way. Lastly, there was no documentation of this new
> event so again, callers are not prepared.
> Restore the previous behavior and lock the semaphore Uninterruptibly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
