Skip to content
  • Parveez Baig's avatar
    6c53f7a5
    Bug#27589007 : RPL_PERFSCHEMA_APPLIER_STATUS_BY_WORKER_GTID_SKIPPED_TRANSACTION FAILING ON PB2 · 6c53f7a5
    Parveez Baig authored
     The test saves the value of  LAST_APPLIED_TRANSACTION from the P_S table
    performance_schema.replication_applier_status_by_worker before skipping
    some GTID and asserts after skipping th GTID that LAST_APPLIED_TRANSACTION
    value has not been changed. The assert fails. The issue is that when the
    LAST_APPLIED_TRANSACTION value is saved before the GTID is skipped the P_S
    table was not still updated.
    
    Fix: included wait_for_slave_param.inc to wait until Slave_SQL_Running_State
    is set to 'Slave has read all relay log; waiting for more updates'
    Before getting the 'LAST_APPLIED_TRANSACTION'.
    6c53f7a5
    Bug#27589007 : RPL_PERFSCHEMA_APPLIER_STATUS_BY_WORKER_GTID_SKIPPED_TRANSACTION FAILING ON PB2
    Parveez Baig authored
     The test saves the value of  LAST_APPLIED_TRANSACTION from the P_S table
    performance_schema.replication_applier_status_by_worker before skipping
    some GTID and asserts after skipping th GTID that LAST_APPLIED_TRANSACTION
    value has not been changed. The assert fails. The issue is that when the
    LAST_APPLIED_TRANSACTION value is saved before the GTID is skipped the P_S
    table was not still updated.
    
    Fix: included wait_for_slave_param.inc to wait until Slave_SQL_Running_State
    is set to 'Slave has read all relay log; waiting for more updates'
    Before getting the 'LAST_APPLIED_TRANSACTION'.
Loading