# Mysql Replication and Repeatable Read issue

**URL:** <https://forums.percona.com/t/mysql-replication-and-repeatable-read-issue/6345>\
**Category:** Percona Server for MySQL 5.7\
**Created:** [May 9, 2018, 7:43am UTC](https://forums.percona.com/t/mysql-replication-and-repeatable-read-issue/6345 "2018-05-09T07:43:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![b.gaifullin](https://avatars.discourse-cdn.com/v4/letter/b/d26b3c/32.png) [@b.gaifullin](https://forums.percona.com/u/b.gaifullin)\
**Post date:** [May 9, 2018, 7:43am UTC](https://forums.percona.com/t/mysql-replication-and-repeatable-read-issue/6345/1 "2018-05-09T07:43:42Z")

</div>

I observed the following case, which looks like a bug for isolation level “repeatable read” from my point of view  
I have table:

```auto

CREATE TABLE IF NOT EXISTS campaign ( id int NOT NULL AUTO_INCREMENT, status enum('active','blocked','deleted') NOT NULL DEFAULT 'active' ); 
INSERT INTO campaign (`status`) VALUES ("deleted"); 

```

[LIST=1]  
[_]  
[_]update the record

```auto
UPDATE campaign SET `status`="active" WHERE id=1;

```

[_]received this update through libslave.  
[_]create a new connection and make query “SELECT status FROM campaign WHERE id=1”  
[\*]expected that status will be “active”, but actually status is “deleted”  
[/LIST]  
if I change the isolation level to “Read-Commited”, I get the status “active” in step 5 as expected.  
Adding read lock in previous query also works. the query

```auto
SELECT status FROM campaign WHERE id=1 LOCK IN SHARE MODE;

```

also returns status “active” even isolation level is “repeatable read”