Database where replication document came from.
Replication document ID.
Consecutive errors count. Indicates how many times in a row this replication has crashed. Replication will be retried with an exponential backoff based on this number. As soon as the replication succeeds this count is reset to 0. To can be used to get an idea why a particular replication is not making progress.
Replication ID, or null if state is completed or failed.
Schema for scheduler document information. A JSON object that may contain additional information about the state. For error states this will contain an error field and string value.
Timestamp of last state update.
Cluster node where the job is running.
Replication source.
Address of the (http or socks5 protocol) proxy server through which replication with the source database occurs.
Timestamp of when the replication was started.
Schema for replication state.
Replication target.
Address of the (http or socks5 protocol) proxy server through which replication with the target database occurs.
Generated using TypeDoc
Schema for a replication scheduler document.