Why does sequencer bound timestamp increment?

pdeva · May 31, 2024, 4:56pm

its this line in getVersionCxx

apple/foundationdb/blob/f1d8c5fd5ad56fbacd628bdcd3927fe88e5ed5d5/fdbserver/masterserver.actor.cpp#L177


      
          			self->version = self->recoveryTransactionVersion;
          			rep.prevVersion = self->lastEpochEnd;
          
          		} else {
          			double t1 = now();
          			if (BUGGIFY) {
          				t1 = self->lastVersionTime;
          			}
          
          			Version toAdd =
          			    std::max<Version>(1,
          			                      std::min<Version>(SERVER_KNOBS->MAX_READ_TRANSACTION_LIFE_VERSIONS,
          			                                        SERVER_KNOBS->VERSIONS_PER_SECOND * (t1 - self->lastVersionTime)));
          
          			rep.prevVersion = self->version;
          			if (self->referenceVersion.present()) {
          				self->version = figureVersion(self->version,
          				                              g_network->timer(),
          				                              self->referenceVersion.get(),
          				                              toAdd,
          				                              SERVER_KNOBS->MAX_VERSION_RATE_MODIFIER,

why is the timestamp increment bounded by MAX_READ_TRANSACTION_LIFE_VERSIONS at all? why not just have it increment by VERSIONS_PER_SECOND * (t1 - self->lastVersionTime)

Topic		Replies	Views
When does atomic op `SET_VERSIONSTAMPED_KEY ` return `versionstamp` with non-zero last 2 bytes? Using FoundationDB	2	293	July 14, 2022
Versionstamp as absolute time Using FoundationDB	3	1393	November 18, 2020
Node bindings release 0.8.0, now with Versionstamp support in the tuple layer! Using FoundationDB	13	759	January 29, 2019
Can version be used as a timestamp when i fetch a version from masterserver? Using FoundationDB bindings	3	442	February 14, 2023
Can Foundation DB / Record Layer support a sequence? Using FoundationDB	3	840	July 6, 2021

Why does sequencer bound timestamp increment?

Related topics