This avoids a scenario where we want to increment the batch size; however, the
current batch size is equal to the max and therefore triggers a decrement and
the next iteration increments. The new behavior will be that we don't trigger
this ping pong. With this change, we can track specifically when we reach the
max batch size and only log the warning once. If the batch size drops, and it
later increments, the warning will be logged again but this should be expected.
Using current batch size for comparison is wrong in case that when currentScn is topScn as described in DBZ-6155.
In the other case (when topScn is behind currentScn) can eventually lead to this situation.
when topScn would fall behind currentScn more and more as we would compare currentScn - topScn with bigger and bigger number (current batch size).
Comapring with logMiningBatchSizeMin could result in very small window which would mean we will send many small queries instead of several bigger ones during mining.
Therefore reverting back to do the adjustments based on the defaultBatchSize.
This reverts commit d38f9444c4.
As the Docker re-evalute thei decision not to provide free organizations
accounts, we will continue to publish images to Docker Hub for some
time.
QE reports that links to two SMTs from the Architecture doc are broken. To ensure that links to targets external to the current file continue to to work downstream, they must use the `{link-prefix}` attribute vs. a simple `xref` macro.
The "fetch-state" attribute was deprecated and is no longer a valid option
with Infinispan 14, which causes the tests to fail to execute. Additionally,
the "segmented" attribute must be set to true going forward as the file
store implementation no longer supports non-segmented configurations.
The configuration propery `binlog.buffer.size` is conditionalized for community use only. However, a link in the Streaming metrics topic targets the entry for the property in the configuration properties table. This change conditionalizes the sentence that contains the link.
A dash omitted from the Nebel annotation `description-of-how-the-mongodb-connector-uses-change streams-to-capture-event-records` between `change` and `streams` results in a downstream build parsing error