Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-5623

S3 Cluster Left Read-Only | BRM lock state & DBRMSnapshotInterval

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 23.02.3, 23.02.4
    • 23.02.8
    • N/A
    • None
    • Customer: 48x1024 3 node Cohesity On-prem S3 cluster
      Reproduction: Rocky 8 16x64 EC2 S3 single Node
    • 2023-11, 2023-12

    Description

      Currently an S3 cluster customer cant load data for more than ~10 days as a BRM lock state likely coincidently occurring during cpimports cascades into rollbacks and leaving the deployment in Read-Only mode until manual intervention. This is unacceptable and prevents the customer from running their production workload.

      Error

      Dec  5 04:06:27 ip-172-31-27-120 Calpont[125899]: 27.238073 |0|0|0| W 00 CAL0094: Attempting to fix the BRM lock state. Diagnostic values: r=1 rwt=0 w=0 wwt=0.

      See developer comments for reproduction

      Attachments

        Issue Links

          includes

          Bug - A problem which impairs or prevents the functions of the product. MCOL-5631 Optimize BRM load operation when StorageManager is enabled.

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          mentioned in

          Page Loading...

          Page Loading...

          Activity

            People

              denis0x0D Denis Khalikov
              allen.herrera Allen Herrera
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.