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

BlockSender performance regression due to volume scanner edge case

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Critical
    • Resolution: Won't Fix
    • 2.8.0
    • None
    • datanode
    • None

    Description

      HDFS-11160 attempted to fix a volume scan race for a file appended mid-scan by reading the last checksum of finalized blocks within the BlockSender ctor. Unfortunately it's holding the exclusive dataset lock to open and read the metafile multiple times Block sender instantiation becomes serialized.

      Performance completely collapses under heavy disk i/o utilization or high xceiver activity. Ex. lost node replication, balancing, or decommissioning. The xceiver threads congest creating block senders and impair the heartbeat processing that is contending for the same lock. Combined with other lock contention issues, pipelines break and nodes sporadically go dead.

      Attachments

        Issue Links

        Activity

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

          People

            daryn Daryn Sharp Assign to me
            daryn Daryn Sharp
            Votes:
            0 Vote for this issue
            Watchers:
            22 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment