0

We are running EE 2 and Stash, 2 DB's: 1 master, 1 slave. The master-slave relationship keeps breaking with the following error:

CRITICAL - Slave sql is not running. Last error: Could not execute Delete_rows_v1 event on table co_site.exp_stash: Can't find record in 'exp_stash', Error_code: 1032: handler error HA_ERR_KEY_NOT_FOUND: the event's master log mysql-master-db-binlog.000001, end_log_pos 55763226

My question is two-fold:
1. Should tables exp_stash and exp_stash_bundles be replicated?
2. If they should, has this issue come up before and is there a fix that will allow our replication working without these errors?

Many Thanks,

Studio1057

Improve this question

2 Answers 2

Reset to default
0

I wouldn't think there's anything special about those two tables with regard to MySQL. If you are doing replication on the other tables then these should be replicated as well.

Is it possible that you are doing some delete operation on the slave without meaning to? (perhaps some kind of script to clear caches or something?)

Improve this answer
2
  • It is almost like if stash pruning is happening on the slave database, even though all web servers are pointing to the master.
    – studio1057
    Dec 19, 2017 at 16:51
  • I believe such an action would be logged. You might want to ask for details of how to track this down on a different Stack.
    – AllInOne
    Dec 19, 2017 at 17:39
0

Stash is a cache plugin for EE. The solution is to exclude it from replication:

replicate-ignore-table = [your_database].exp_stash

This will inhibit this table from replicating. It cannot be done on the binlog level on the master unless the stash has it's own database.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.