Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-4714

BlockManager should check whether blocks have already been removed Checking block is null or not after having gotten info.lock in remove block method

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 CommentsDelete
    XMLWordPrintableJSON

Details

    Description

      in removeBlock()/ dropOldBlock()/ dropFromMemory()
      all have the same logic:
      1. info = blockInfo.get(id)
      2. if (info != null)
      3. info.synchronized

      there may be a possibility that while one thread got info.lock while the previous thread already removed from blockinfo in info.lock.

      but one thing in current code, That not check info is null or not, while get info.lock to remove block, will not cause any errors.

      Attachments

        Activity

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

          People

            SuYan SuYan Assign to me
            SuYan SuYan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment