Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6660

missing grastate.dat + broken innodb prevents node startup

        Details

        • Type: Bug
        • Status: Open
        • Priority: Major
        • Resolution: Unresolved
        • Affects Version/s: 5.5.39-galera
        • Fix Version/s: None
        • Component/s: None
        • Labels:

          Description

          In a crash when grastate.dat is not written and the InnoDB tablespace is damaged in some way, starting the server using mysqld_safe will fail.

          mysqld_safe starts the server with the --wsrep-recover option. In that case, when grastate.dat is missing, InnoDB is initialized. If InnoDB can't start, the only resolution is to manually empty the datadir to force an SST.

          example:

          140828 13:31:29 [Warning] No argument was provided to --log-bin and neither --log-basename or --log-bin-index where used;  This may cause repliction to break when this server acts as a master and has its hostname changed! Please use '--log-basename=db1' or '--log-bin=db1-recover-bin' to avoid this problem.
140828 13:31:29 InnoDB: The InnoDB memory heap is disabled
140828 13:31:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140828 13:31:29 InnoDB: Compressed tables use zlib 1.2.3
140828 13:31:29 InnoDB: Using Linux native AIO
140828 13:31:29 InnoDB: Initializing buffer pool, size = 128.0M
140828 13:31:29 InnoDB: Completed initialization of buffer pool
140828 13:31:29 InnoDB: highest supported file format is Barracuda.
InnoDB: Transaction 149EE8 was in the XA prepared state.
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 14A000
140828 13:31:29  InnoDB: Waiting for the background threads to start
InnoDB: Starting in background the rollback of uncommitted transactions
140828 13:31:29  InnoDB: Rollback of non-prepared transactions completed
140828 13:31:30 Percona XtraDB (http://www.percona.com) 5.5.38-MariaDB-35.2 started; log sequence number 640493839
140828 13:31:30 [Note] Plugin 'FEEDBACK' is disabled.
140828 13:31:30  InnoDB: Starting recovery for XA transactions...
140828 13:31:30  InnoDB: Transaction 149EE8 in prepared state after recovery
140828 13:31:30  InnoDB: Transaction contains changes to 1 rows
140828 13:31:30  InnoDB: 1 transactions in prepared state after recovery
140828 13:31:30 [Note] Found 1 prepared transaction(s) in InnoDB
140828 13:31:30 [ERROR] Found 1 prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or tc.log file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.
140828 13:31:30 [ERROR] Aborting

            Gliffy Diagrams

              Attachments

                Activity

                There are no comments yet on this issue.

                  People

                  • Assignee:
                    nirbhay_c Nirbhay Choubey
                    Reporter:
                    kolbe Kolbe Kegel
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated: