Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-714

Row store read/update not isolated on Journal

    Details

    • Type: Bug
    • Status: Done
    • Resolution: Done
    • Affects Version/s: BIGDATA_RELEASE_1_2_2
    • Fix Version/s: None
    • Component/s: Journal

      Description

      The row store operations are not isolated on the journal. These operations were written to depend on the ConcurrencyManager and are ACID on a cluster, but they are not run on the ConcurrencyManager for a Journal and hence lack appropriate isolation. This problem exists in all versions, but rarely shows up because the row store is mainly used for KB creation metadata and we rarely have concurrent create / discover / destroy operations for KBs.

        Activity

        Hide
        bryanthompson bryanthompson added a comment -

        GlobalRowStoreHelper has been modified to use AbstractRelation.getIndex(...) to wrap a live index view with an UnisolatedReadWriteIndex. This is the same code path that is used to protect normal named indices used by relations on the Journal. This code change fixes problems that had been observed with TestConcurrentKBCreate that were clearly related to the lack of isolation for the live view of the global row store. However, there is still a test failure mode for TestConcurrentKBCreate that appears to be related to the default resource locator cache.

        Committed revision r6706.

        Show
        bryanthompson bryanthompson added a comment - GlobalRowStoreHelper has been modified to use AbstractRelation.getIndex(...) to wrap a live index view with an UnisolatedReadWriteIndex. This is the same code path that is used to protect normal named indices used by relations on the Journal. This code change fixes problems that had been observed with TestConcurrentKBCreate that were clearly related to the lack of isolation for the live view of the global row store. However, there is still a test failure mode for TestConcurrentKBCreate that appears to be related to the default resource locator cache. Committed revision r6706.

          People

          • Assignee:
            bryanthompson bryanthompson
            Reporter:
            bryanthompson bryanthompson
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: