Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4054 Multithreaded clob update with exclusive table locking causes table growth that is not reclaimed
  3. DERBY-4059

If space reclamation cannot obtain container lock it will not retry getting the lock

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.1.1
    • 10.5.1.1
    • Store
    • None
    • Patch Available

    Description

      As noted in DERBY-4054 openContainerNW throws an exception if it canno get the container lock and bypasses the retry logic. See:
      https://issues.apache.org/jira/browse/DERBY-4054?focusedCommentId=12673376#action_12673376

      We should catch the exception and retry if we can't get the container lock. This probably won't fix the repro for DERBY-4054, but should be helpful in some user scenarios.

      Attachments

        Activity

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

          People

            kmarsden Katherine Marsden
            kmarsden Katherine Marsden
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment