Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DocDB][xCluster][DDL] Replication halts even if schema matches but the schema was evolved with different steps on source and target #16640

Open
1 task done
Arjun-yb opened this issue Mar 31, 2023 · 1 comment
Assignees
Labels
area/docdb YugabyteDB core features kind/bug This issue is a bug priority/medium Medium priority issue qa_itest-system Bugs identified in itest-system automation xCluster Label for xCluster related issues/improvements

Comments

@Arjun-yb
Copy link
Contributor

Arjun-yb commented Mar 31, 2023

Jira Link: DB-6027

Description

Replication is halted even when schema matches on both source and target.

Version: 2.19.x

Create table at both sides

create table t1(id int primary key, name text);

setup replication and insert some rows and read at target ---- works

At source:

insert into t1(id, name) values(1,'Arjun');
insert into t1(id, name) values(2,'Sandeep');

At target:

select * from t1;
 id |  name
----+---------
  1 | Arjun
  2 | Sandeep

then alter table at source:

alter table t1 add column c1 text; ----- here type is text

and insert some rows

insert into t1(id, name, c1) values(3,'Hari','a');
insert into t1(id, name, c1) values(4,'Julien','b');
insert into t1(id, name, c1) values(5,'New','c');

here data is not replicated --- expected as there is mismatch in schema

then alter table at target

alter table t1 add column c1 int; ------ here type is int

data is not replicated ----- expected

alter at target

alter table t1 drop column c1
alter table t1 add column c1 text; ------ made it to text

here replication is not happened ------ expected as the alter id is different

then alter at source

alter table t1 drop column c1;
alter table t1 add column c1 text;
insert into t1(id, name, c1) values(6,'New','d');
demo1=# select * from t1;
 id |  name   | c1
----+---------+----
  5 | New     |
  1 | Arjun   |
  6 | New     | d
  4 | Julien  |
  2 | Sandeep |
  3 | Hari    |

after this replication should happen as both table has same schema
but it is not happening

demo1=# select * from t1;
 id |  name   | c1
----+---------+----
  1 | Arjun   |
  2 | Sandeep |

Expected: Replication should happen as schemas as compatible but they are not happening.

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.
@Arjun-yb Arjun-yb added area/docdb YugabyteDB core features status/awaiting-triage Issue awaiting triage labels Mar 31, 2023
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue labels Mar 31, 2023
@Arjun-yb Arjun-yb added the xCluster Label for xCluster related issues/improvements label Mar 31, 2023
@Arjun-yb Arjun-yb added this to To do in xCluster replication via automation Mar 31, 2023
@yugabyte-ci yugabyte-ci removed the status/awaiting-triage Issue awaiting triage label Apr 4, 2023
@yugabyte-ci yugabyte-ci added priority/high High Priority and removed priority/medium Medium priority issue labels Sep 22, 2023
@lingamsandeep lingamsandeep changed the title [DocDB][xCluster][DDL] Replication is not in halted state on incorrect DDL at target and it is replicating incorrect data [DocDB][xCluster][DDL] Replication is halted unexpectedly Nov 9, 2023
@rajapriya371
Copy link

Observing this issue on 2.19.3.0-b140,2.18.5.0-b63

@Arjun-yb Arjun-yb added the qa_itest-system Bugs identified in itest-system automation label Dec 11, 2023
@yugabyte-ci yugabyte-ci added priority/medium Medium priority issue and removed priority/high High Priority labels Jan 29, 2024
@lingamsandeep lingamsandeep changed the title [DocDB][xCluster][DDL] Replication is halted unexpectedly [DocDB][xCluster][DDL] Replication halts even if schema matches but the schema was evolved with different steps on source and target Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docdb YugabyteDB core features kind/bug This issue is a bug priority/medium Medium priority issue qa_itest-system Bugs identified in itest-system automation xCluster Label for xCluster related issues/improvements
Projects
Development

No branches or pull requests

4 participants