Add documentation for MilliSecondsBehindSource growing exponentially.

[rnatarajan]

No description provided.

[gunnarmorling]

Thanks for this change, this sounds a bit concerning though. Can you provide some more context about this situation: what's your change event rate and your set-up in general? I don't quite agree to the statement on roundtrip times below; the connection throughput may be a limiting factor, but latency itself should be constant, also with larger roundtrip times between the DB and the Kafka Connect host.

[rnatarajan]

Hi @gunnarmorling ,

Thanks for your comments.
MilliSecondsBehindSource growing exponentially issue occurred in our environment and I had reached out to Jiri Pechanec about this issue. Link to Gitter Thread with details - https://gitter.im/debezium/user?at=6050ec1ed1aee44e2def7b89

Created this pull request as Jiri had recommended contributing to the documentation.

Please let me know if you need more details.

[Naros]

Hi @rnatarajan so I definitely think adding an FAQ entry, particularly when MilliSecondsBehindSource is high is worthwhile given the scenario you describe, but I think perhaps the way this is conveyed, particularly with the use of "exponentially" gives a bad impression.

Perhaps, this could be reworded to something like "High MilliSecondsBehindSource when connector deployed with WAN connection to database" or similar. I think speaking in terms of higher than usual latency when using a WAN connection rather than a LAN connection is what we should strive for on this PR.

[rnatarajan]

@Naros Thanks for the comment. I can reword the README.

[Naros]

Awesome, once you have, if you could just request a re-review of the PR that'd be wonderful.

[Naros]

❌ Developer Certificate of Origin (DCO) check failed.

Hi @rnatarajan, please sign off all commits with:

git commit -s

If pull request commits are not signed off, the pull request cannot be merged. For more information about why this is required, please see our blog about contribution requirement changes.

[github-actions]

⚡️ Deploying PR Preview...

[Naros]

Hi @rnatarajan please remove the merge commit.

[rnatarajan]

Hi @rnatarajan please remove the merge commit.

Working on removing the merge commit.

[github-actions]

❌ Developer Certificate of Origin (DCO) check failed.

Hi @rnatarajan, please sign off all commits with:

git commit -s

If pull request commits are not signed off, the pull request cannot be merged. For more information about why this is required, please see our blog about contribution requirement changes.

[github-actions]

❌ Developer Certificate of Origin (DCO) check failed.

Hi @rnatarajan, please sign off all commits with:

git commit -s

If pull request commits are not signed off, the pull request cannot be merged. For more information about why this is required, please see our blog about contribution requirement changes.

[rnatarajan]

@Naros , Rather than using the command line, I had used Git Web rebase + sign-off which has caused the Merge commit.
It would be straightforward to get the latest changes from develop and create a MR with just the comment added.