Re: Hammer error?

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:Oh, after retry with the new IP it started in
:transactionid=3D000000000002 again, is it ok? shouldnt it start where it
:crashed?
:Sdav

    This isn't a bug but it is a missing feature.  What is happening is
    that the mirror stream is trying to eat too large a chunk (the entire
    difference between the slave and the master) in one go, and will
    not update the transaction id until the entire chunk is finished.

    Because transaction id's do not represent timestamps we need to add
    a heuristic to at least the mirror-stream implementation to not
    try to do the entire block at once.

    We also need to make a slight modificatin to the wire protocol to
    allow save points to be sent in the middle of the stream.  Right
    now only the mirror-stream protocol can do save-points, since it
    is a continuous 2-way connection.  mirror-copy cannot.

					-Matt