Quoting Kristian Nielsen :
Jan Lindström writes:
The point I do not understant is at ha_savepoint
we have again:
if ((err= ht->savepoint_set(ht, thd, (uchar *)(sv+1)+ht->savepoint_offset)))
(gdb) p *sv
$3 = {prev = 0xa5a5a5a5a5a5a5a5, name = 0x7f505c007390 "A", length
= 1, ha_list
= 0x
Quoting Jan Lindström :
Seppo,
Hi,
What means:
30925 15:10:36 [ERROR] Slave SQL: Could not execute Update_rows
event on table test.table10_key_pk_parts_2_int_autoinc; Can't find
record in 'table10_key_pk_parts_2_int_autoinc', Error_code: 1032;
handler error HA_ERR_KEY_NOT_FOUND; the ev
Jan,
MariaDB Galera Cluster 10 is in the pipeline. We have some serious
merge efforts remaining and first release is possible in May/June time
frame.
-seppo
Quoting Jan Kirchhoff :
Hi,
we have been playing around with 5.5.28-galera and went into more
serious testing with 5.5.29-galera.
Quoting Henrik Ingo :
Meta discussion first, replication discussion below :-)
On Mon, Mar 22, 2010 at 4:41 PM, Alex Yurchenko
wrote:
Uh, I'm not sure I can accept this proposition. At least it seems
contradictory to MariaDB's vision of being a practical, user and
customer driven, database.
Hi Kristian,
I agree with Alex's response, and I'll pick the hopefully all the
remaining questions to answer here.
Quoting Kristian Nielsen :
So the basic for such an interface would be the ability to install
hooks to be
called with row data for every handler::write_row(), handler::update_
Hi Robert,
Tungsten consistency checking technology works very well, and there
is no need to "fix it" in any way. However, this method is not directly
usable for multi master replication, because the target node(s) may
have committed some transactions not yet seen in the originating
master node,
Thanks Robert, this is comprehensive enough :)
I'll just address the consistency checking requirement here,
as I believe this is quite widely accepted goal as well.
Tungsten uses a special consistency table for passing consistency
checking information and which is treated in a special way in the
Hi Jeremy,
Thanks for the input. I'm not sure what you mean with true replication
latency here.
Anyway, the replication system can internally measure latencies
from the point where the replication event was passed for replication
until it was received/applied in the receiving end. And these laten
8 matches
Mail list logo
