Menu

Post image 1
Post image 2
1 / 2
0

Ensuring Replication Consistency in GBase 8s: cdr repair vs cdr sync

DEV Community·Michael·23 days ago
#FL4cVHqT
#method#gbase#database#software#repair#repl
Reading 0:00
15s threshold

In an Enterprise Replication (ER) environment on GBase 8s, performing large DML operations before a replicate is fully active can leave standby nodes with missing rows. The cdr utility provides two repair mechanisms — cdr check repl --repair and cdr sync repl . This post demonstrates both, using the cdrtime column to reveal their different approaches. Test Setup Create a table with conflict resolution columns ( CRCOLS ) and a replicate across three nodes (er01, er02, er03). CREATE TABLE t5 ( id INT , col DECIMAL ( 6 , 2 ), PRIMARY KEY ( id )) WITH CRCOLS ; Enter fullscreen mode Exit fullscreen mode Method 1: cdr check repl --repair This command repairs inconsistent data by re‑executing the missing operations. As a result, the cdrtime column is refreshed to the current timestamp. Start the replicate, insert rows before and after activation. er02 and er03 are missing the first two rows.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More