SPECIAL NOTE: Percona XtraDB Cluster 5.5 has reached End of Life and is no longer supported.
For specific information please visit - https://www.percona.com/services/policies/percona-software-platform-lifecycle

Index of files created by PXC

  • GRA_*.log

    These files contain binlog events in ROW format representing the failed transaction. That means that the slave thread was not able to apply one of the transactions. For each of those file, a corresponding warning or error message is present in the mysql error log file. Those error can also be false positives like a bad DDL statement (dropping a table that doesn’t exists for example) and therefore nothing to worry about. However it’s always recommended to check these log to understand what’s is happening.

    To be able to analyze these files binlog header needs to be added to the log file.

    $ cat GRA-header > /var/lib/mysql/GRA_1_2-bin.log
    $ cat /var/lib/mysql/GRA_1_2.log >> /var/lib/mysql/GRA_1_2-bin.log
    $ mysqlbinlog -vvv /var/lib/mysql/GRA_1_2-bin.log
    /*!40019 SET @@session.max_insert_delayed_threads=0*/;
    DELIMITER /*!*/;
    # at 4
    #120715  9:45:56 server id 1  end_log_pos 107     Start: binlog v 4, server v 5.5.25-debug-log created 120715  9:45:56 at startup
    # Warning: this binlog is either in use or was not closed properly.
    BINLOG '
    # at 107
    #130226 11:48:50 server id 1  end_log_pos 83      Query   thread_id=3     exec_time=0     error_code=0
    use `test`/*!*/;
    SET TIMESTAMP=1361875730/*!*/;
    SET @@session.pseudo_thread_id=3/*!*/;
    SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=0, @@session.unique_checks=1, @@session.autocommit=1/*!*/;
    SET @@session.sql_mode=1437073440/*!*/;
    SET @@session.auto_increment_increment=3, @@session.auto_increment_offset=2/*!*/;
    /*!\C utf8 *//*!*/;
    SET @@session.character_set_client=33,@@session.collation_connection=33,@@session.collation_server=8/*!*/;
    SET @@session.lc_time_names=0/*!*/;
    SET @@session.collation_database=DEFAULT/*!*/;
    drop table test
    # End of log file
    ROLLBACK /* added by mysqlbinlog */;

    This information can be used for checking the MySQL error log for the corresponding error message.

    130226 11:48:50 [ERROR] Slave SQL: Error 'Unknown table 'test'' on query. Default database: 'test'. Query: 'drop table test', Error_code: 1051
    130226 11:48:50 [Warning] WSREP: RBR event 1 Query apply warning: 1, 3
    130226 11:48:50 [Warning] WSREP: Ignoring error for TO isolated action: source: dd40ad88-7ff9-11e2-0800-e93cbffe93d7 version: 2 local: 0 state: APPLYING flags: 65 conn_id: 3 trx_id: -1 seqnos (l: 5, g: 3, s: 2, d: 2, ts: 1361875730070283555)

    In this example DROP TABLE statement was executed on a table that doesn’t exist.

  • galera.cache

    This file is used as a main writeset store. It’s implemented as a permanent ring-buffer file that is preallocated on disk when the node is initialized. File size can be controlled with the variable gcache.size. If this value is bigger, more writesets are cached and chances are better that the re-joining node will get IST instead of SST. Filename can be changed with the gcache.name variable.

  • grastate.dat

    This file contains the Galera state information.

    • version - grastate version
    • uuid - a unique identifier for the state and the sequence of changes it undergoes
    • seqno - Ordinal Sequence Number, a 64-bit signed integer used to denote the position of the change in the sequence. seqno is 0 when no writesets have been generated or applied on that node, i.e., not applied/generated across the lifetime of a grastate file. -1 is a special value for the seqno that is kept in the grastate.dat while the server is running to allow Galera to distinguish between a clean and an unclean shutdown. Upon a clean shutdown, the correct seqno value is written to the file. So, when the server is brought back up, if the value is still -1 , this means that the server did not shut down cleanly. If the value is greater than 0, this means that the shutdown was clean. -1 is then written again to the file in order to allow the server to correctly detect if the next shutdown was clean in the same manner.
    • cert_index - cert index restore through grastate is not implemented yet

    Examples of this file look like this:

    In case server node has this state when not running it means that that node crashed during the transaction processing.

    # GALERA saved state
    version: 2.1
    uuid:    1917033b-7081-11e2-0800-707f5d3b106b
    seqno:   -1

    In case server node has this state when not running it means that the node was gracefully shut down.

    # GALERA saved state
    version: 2.1
    uuid:    1917033b-7081-11e2-0800-707f5d3b106b
    seqno:   5192193423942

    In case server node has this state when not running it means that the node crashed during the DDL.

    # GALERA saved state
    version: 2.1
    uuid:    00000000-0000-0000-0000-000000000000
    seqno:   -1

Contact Us

For free technical help, visit the Percona Community Forum.
To report bugs or submit feature requests, open a JIRA ticket.
For paid support and managed or professional services, contact Percona Sales.