Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-14497

Write lock held by metasave impact following RPC processing

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.3.0, 3.1.4, 3.2.2
    • namenode
    • None

    Description

      NameNode meta save hold global write lock currently, so following RPC r/w request or inner-thread of NameNode could be paused if they try to acquire global read/write lock and have to wait before metasave release it.
      I propose to change write lock to read lock and let some read request could be process normally. I think it could not change informations which meta save try to get if we try to open read request.
      Actually, we need ensure that there are only one thread to execute metaSave, otherwise, output streams could meet exception especially both streams hold the same file handle or some other same output stream.

      Attachments

        1. HDFS-14497.001.patch
          6 kB
          Xiaoqiao He
        2. HDFS-14497-addendum.001.patch
          0.8 kB
          Xiaoqiao He

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            hexiaoqiao Xiaoqiao He
            hexiaoqiao Xiaoqiao He
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment