Details
-
Bug
-
Resolution: Won't Fix
-
Test Blocker
-
None
-
DOC-2021-Mar14-S5, DOC-2021-Mar28-S6, DOC-2021-Apr11-S7, DOC-2021-Apr25-S8, DOC-2021-May09-S9, DOC-2021-May23-S10, DOC-2021-Jun06-S11, DOC-2021-Jun20-S12, DOC-2021-Jul04-S13
-
1
Description
the description here, is unclear.
https://docs.couchbase.com/elasticsearch-connector/current/configuration.html#dcp
To propagate changes immediately, disable persistence polling by setting this to '0ms'. A non-zero duration tells the connector to defer propagation until the change is persisted on all Couchbase replicas. Longer intervals reduce network traffic at the cost of increased end-to-end latency.
if the parameter is set to 0, the changes will be published from memory (without waiting for persistence), and anything above 0, the changes has to persist first on disk before the changes could be visible to the connector, the interval is how frequent the connector will be polling for the changes.
in fact 0 and above 0, has two different behaviors.
0= Changes published immediately from memory (as the DCP event occurred)
>0 = Changes are waited to be persisted, the number is the frequency of polling.
Reporter: Roi Katz
E-mail: roi.katz@Couchbase.com