Howard Chu authored Oct 01, 2020 and Quanah Gibson-Mount committed Oct 01, 2020

if the entryCSN is older. Previous patch breaks if writes are
received out of order, e.g. during a refresh.

Howard Chu authored Sep 30, 2020 and Quanah Gibson-Mount committed Sep 30, 2020

This check is only needed for ops received without a CSN in their cookie.
This only occurs when the ops completed out of order on the provider.

Howard Chu authored Sep 10, 2020 and Quanah Gibson-Mount committed Sep 10, 2020

Fix a regression in delta-sync, was returning error on old
CSNs instead of ignoring them

Howard Chu authored Sep 09, 2020 and Quanah Gibson-Mount committed Sep 09, 2020

Using cs_pmutex. Reverts the addition of cs_modmutex in ITS#9330,
use cs_pmutex for both delta and plain writes.

Note that plain syncrepl already used cs_pmutex when a cookie CSN
was present in the op. Now it is used for all writes, regardless
of presence of cookie.

Howard Chu authored Aug 19, 2020 and Quanah Gibson-Mount committed Sep 09, 2020

Don't depend on accesslog overlay's serialization

Howard Chu authored Aug 31, 2020 and Quanah Gibson-Mount committed Aug 31, 2020

Don't assume si_cookieState is always newer

Howard Chu authored Aug 31, 2020 and Quanah Gibson-Mount committed Aug 31, 2020

In a standard Refresh present phase, the provider sends no cookie
since it is only listing the entries that existed as of the time
in the cookie the consumer sent. In this case the consumer only
needs to check entryCSNs against its last sent cookie.

Howard Chu authored Aug 26, 2020 and Quanah Gibson-Mount committed Aug 26, 2020

A bit uglier but more straightforward.

Howard Chu authored Aug 22, 2020 and Quanah Gibson-Mount committed Aug 24, 2020

Just poll for available data, same as Persist mode.
Clarify retry/return states from do_syncrep2

Howard Chu authored Jul 29, 2020 and Quanah Gibson-Mount committed Jul 29, 2020

For delta-sync as well as regular sync

Howard Chu authored Feb 22, 2018 and Quanah Gibson-Mount committed Feb 28, 2018

And try another approach. Always write contextCSN updates, but
don't set dont_replicate for updates we want propagated.

Howard Chu authored Jan 31, 2018 and Quanah Gibson-Mount committed Feb 21, 2018

If syncprov is present, only write contextCSN attribute on
actual state changes, not on per-entry modifications.
Continue to update in-memory cookieState. Saves overhead,
syncprov will eventually checkpoint it into the DB anyway.

Howard Chu authored Oct 13, 2017 and Quanah Gibson-Mount committed Oct 17, 2017

Must release cookieState->cs_mutex before invoking backend.
Add a condvar to serialize calls of updateCookie, so we can
release the mutex and still update sequentially.

Also added tid logging, useful in conjunction with
7ab0e1aff0cc48cdfb299ca7dbd27900a9e3d1a8

Howard Chu authored Oct 05, 2017 and Quanah Gibson-Mount committed Oct 17, 2017

Make sure it's last in callback stack

Ondřej Kuzník authored Apr 04, 2017 and Quanah Gibson-Mount committed Apr 07, 2017

Make two successive modifications of the same attribute separate. This
lets the consumer interpret the log entry the same way as the server
that produced it.

Still depends on the log entry attributes being read in the same order
as they were written.

Howard Chu authored Apr 28, 2016 and Quanah Gibson-Mount committed Oct 17, 2016

Filter needs AttributeAssertions