New: during xfer, cmd_undump should call sync_log

h
ttp://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2957

           Summary: during xfer, cmd_undump should call
sync_log
           Product: Cyrus IMAP
           Version: 2.3.x
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: bug
          Priority: P2
         Component: IMAP
        AssignedTo: murchandrew.cmu.edu
        ReportedBy: wesumich.edu
         QAContact: cyrus-bugzillalists.andrew.cmu.edu
                CC: pturgyanumich.edu


During xfer, LOCALCREATE is called, followed quickly by
UNDUMP.  LOCALCREATE
calls sync_log, but UNDUMP does not.  If sync_client begins
reading cyrus.cache
before it's completely written by UNDUMP, sync_client will
core.  It's not clear
whether interlocking is a possible solution to this problem.
 The attached patch
removes the sync_log from LOCALCREATE and adds one to
UNDUMP.  This seems to
better reflect the intent of how xfer should work.  It has
the nice side effect
of not changing the mailbox ID during xfer, which suppresses
the (bogus) RESET
that sync_client issues to sync_server -- the RESET causes
everything but the
INBOX to be deleted and resent, perhaps why xfer in a
replicated environment
appears to consume approximately three times the IO-size of
the users being
xfer'd instead of two times.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA
contact.