[GOBBLIN-1995]Kill the writer thread when timeout happens to release the lock

[ZihanLi58]

Dear Gobblin maintainers,

Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!

JIRA

• My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
  • https://issues.apache.org/jira/browse/GOBBLIN-1995

Description

• Here are some details about my PR, including screenshots (if applicable):
  Now when there is timeout happens talking with HDFS, we timeout and fail the job but the thread won't be killed in this case, and all other calls to HDFS will be blocked by this hanging thread. 

Tests

• My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

[homatthew]

Does this have the intended effect? In the issues you were seeing, did we see threads that are sleeping / waiting on IO, which need to be interrupted via cancel?

I am asking this because if the thread needs to actively check if it's being requested to cancel (unless it's actively waiting / sleeping).

Read the below to see what I am describing
https://stackoverflow.com/questions/28043225/future-cancel-does-not-work

[ZihanLi58]

@homatthew thanks for the information. The thread here is blocking on getting the HDFS mount table which is an IO operation. I also did a test to do a for loop to talk with HDFS and do timeout, and make sure cancel can work correctly in this case.