|
Hi
We have some tables with a few million rows. Every now and again, an update is done to the tables which results in a few thousand rows updating or being inserted.
Since I am using ROW replication, the Tungsten master fails on these with either a packet too large exception or a heap error.
I have tried 72M max_allowed_packet, and 1024M java heap size, with the same results.
I am loathe to continually push these variables higher and higher, but am hoping that tungsten has a way of breaking this up into smaller chunks that can be managed more effectively.
Are there any settings i can look at to help with this?
|
Forum
Favoured: 1
