Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-65262

Expand usage of WT numerical timestamp API

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.1, 4.4.16, 5.0.11, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible
    • v6.0, v5.0, v4.4
    • Execution Team 2022-05-16

      In SERVER-64797, we converted our usages of timestamp_transaction to timestamp_transaction_uint. However, for instances where we use commit_transaction (for example on secondaries), we're still serializing the timestamps into a string. We should try to avoid the serialization for this case as well.

      One option is to call timestamp_transaction_uint twice before commit_transaction, something like:

      s->timestamp_transaction(s, "commit_timestamp=1");
      s->timestamp_transaction(s, "durable_timestamp=2");
      s->commit_transaction(s, nullptr);

      A potential downside is that there may be some extra overhead from this approach, since the timestamps will be validated twice: once when set and once when committing.

      Another option is to look into adding a new interface from the WT side for this purpose.

            gregory.noma@mongodb.com Gregory Noma
            gregory.noma@mongodb.com Gregory Noma
            0 Vote for this issue
            4 Start watching this issue