← Back to team overview

linux-traipu team mailing list archive

[Bug 990863] [NEW] slave doesn't work with filtered_replicator because the latter writes invalid replication events

 

Public bug reported:

The slave plugin doesn't work with the filtered_replicator plugin in 7.1
because the replicator writes invalid replication events:

drizzle> select * from data_dictionary.innodb_replication_log\G
*************************** 1. row ***************************
            TRANSACTION_ID: 800
    TRANSACTION_SEGMENT_ID: 0
                 COMMIT_ID: 0
             END_TIMESTAMP: 1335659685463387
   ORIGINATING_SERVER_UUID: 8666E171-1415-4792-B36C-52B2EFEE1AF9
     ORIGINATING_COMMIT_ID: 0
TRANSACTION_MESSAGE_STRING: transaction_context {
  server_id: 1
  transaction_id: 800
  start_timestamp: 1335659685463363
  end_timestamp: 1335659685463387
}
statement {
  type: CREATE_SCHEMA

The zeros values for segment ID, commit ID, etc. are invalid.
Consequently, the slave plugin never sees any new commit IDs to read.

** Affects: drizzle
     Importance: High
         Status: Confirmed


** Tags: filtered-replicator-plugin replication slave-plugin

** Description changed:

- The filtered_replicator plugin doesn't work in 7.1.  It seems to not
- create proper replication events:
- 
+ The slave plugin doesn't work with the filtered_replicator plugin in 7.1
+ because the replicator writes invalid replication events:
  
  drizzle> select * from data_dictionary.innodb_replication_log\G
  *************************** 1. row ***************************
-             TRANSACTION_ID: 800
-     TRANSACTION_SEGMENT_ID: 0
-                  COMMIT_ID: 0
-              END_TIMESTAMP: 1335659685463387
-    ORIGINATING_SERVER_UUID: 8666E171-1415-4792-B36C-52B2EFEE1AF9
-      ORIGINATING_COMMIT_ID: 0
+             TRANSACTION_ID: 800
+     TRANSACTION_SEGMENT_ID: 0
+                  COMMIT_ID: 0
+              END_TIMESTAMP: 1335659685463387
+    ORIGINATING_SERVER_UUID: 8666E171-1415-4792-B36C-52B2EFEE1AF9
+      ORIGINATING_COMMIT_ID: 0
  TRANSACTION_MESSAGE_STRING: transaction_context {
-   server_id: 1
-   transaction_id: 800
-   start_timestamp: 1335659685463363
-   end_timestamp: 1335659685463387
+   server_id: 1
+   transaction_id: 800
+   start_timestamp: 1335659685463363
+   end_timestamp: 1335659685463387
  }
  statement {
-   type: CREATE_SCHEMA
+   type: CREATE_SCHEMA
  
- All zeros for segment ID, commit ID, etc.  Consequently, the slave
- plugin never sees any new commit IDs to read.
+ The zeros values for segment ID, commit ID, etc. are invalid.
+ Consequently, the slave plugin never sees any new commit IDs to read.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/990863

Title:
  slave doesn't work with filtered_replicator because the latter writes
  invalid replication events

Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
  Confirmed

Bug description:
  The slave plugin doesn't work with the filtered_replicator plugin in
  7.1 because the replicator writes invalid replication events:

  drizzle> select * from data_dictionary.innodb_replication_log\G
  *************************** 1. row ***************************
              TRANSACTION_ID: 800
      TRANSACTION_SEGMENT_ID: 0
                   COMMIT_ID: 0
               END_TIMESTAMP: 1335659685463387
     ORIGINATING_SERVER_UUID: 8666E171-1415-4792-B36C-52B2EFEE1AF9
       ORIGINATING_COMMIT_ID: 0
  TRANSACTION_MESSAGE_STRING: transaction_context {
    server_id: 1
    transaction_id: 800
    start_timestamp: 1335659685463363
    end_timestamp: 1335659685463387
  }
  statement {
    type: CREATE_SCHEMA

  The zeros values for segment ID, commit ID, etc. are invalid.
  Consequently, the slave plugin never sees any new commit IDs to read.

To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/990863/+subscriptions


Follow ups

References