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

Primary Node Failover in a cluster with S3 is left in an unusable state at times

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 5.4.3
    • Fix Version/s: 5.6.1
    • Component/s: Storage Manager
    • Labels:
      None

      Description

      After a primary node failover, non-primary nodes are occasionally failing to loadbrm.
      The mcs-loadbrm.service outputs the following:

      Mar 22 21:22:04 pm3 mcs-loadbrm.py[29596]: Loading BRM snapshot failed (/tmp/columnstore_tmp_files/rdwrscratch/BRM_saves)
      Mar 22 21:22:04 pm3 mcs-loadbrm.py[29596]: ExtentMap::load(): That file is not a valid ExtentMap image

      There are no other indications that there was an error, until queries are attempted on the system.

      The workaround is to restart the cluster via cmapi cluster/stop, cluster/start

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              drrtuy Roman
              Reporter:
              jrojas Jose Rojas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration