Multi-message Transactions not handled
Bug #655720 reported by
David Shrewsbury
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| RabbitReplication |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
A single database transaction can possibly be broken up into multiple Transaction protobuf messages if the transaction is very large. RR currently assumes 1 protobuf message per db transaction, which is how it used to be.
Also, Transaction protobuf messages from different db transactions can be intermingled, so we need to handle this case as well.
| Changed in rabbitreplication: | |
| status: | New → Confirmed |
| assignee: | nobody → David Shrewsbury (dshrews) |
Revision history for this message
| David Shrewsbury (dshrews) wrote | #1 |
| Changed in rabbitreplication: | |
| assignee: | David Shrewsbury (dshrews) → nobody |
To post a comment you must log in.
We should use the new Drizzle java tools at some point.