. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Why throttler: maintaining low replication lag . . . . . . . . . . . . . . . . . . . . . . . . . . . . keyrange. Thus: -80 == 00-80 == 0000-8000 == 000000-800000 80- is not the same as 80-FF. This is why: 80-FF == 8000-FF00. Therefore FFFF will be out of the 80-FF range. 80- means: ‘anything greater start by creating an RFC (Request for Commnent) issue - this is where you can discuss the feature and why it’s important. Once that is in place, you can create the PR, as a solution to the problem described

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Why throttler: maintaining shard health via low replication lag . . . . . . . . . . . . . . . . . . . 0000-8000 == 000000-800000 == 0000000000000000-8000000000000000 80- is not the same as 80-FF. This is why: 80-FF == 8000-FF00. Therefore FFFF will be out of the 80-FF range. 80- means: ‘anything greater start by creating an RFC (Request for Commnent) issue - this is where you can discuss the feature and why it’s important. Once that is in place, you can create the PR, as a solution to the problem described

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Why throttler: maintaining shard health via low replication lag . . . . . . . . . . . . . . . . . . . 0000-8000 == 000000-800000 == 0000000000000000-8000000000000000 80- is not the same as 80-FF. This is why: 80-FF == 8000-FF00. Therefore FFFF will be out of the 80-FF range. 80- means: ‘anything greater start by creating an RFC (Request for Commnent) issue - this is where you can discuss the feature and why it’s important. Once that is in place, you can create the PR, as a solution to the problem described

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Why throttler: maintaining shard health via low replication lag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 Why . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 Why not . . . . . . . . . . . . . . 0000-8000 == 000000-800000 == 0000000000000000-8000000000000000 80- is not the same as 80-FF. This is why: 80-FF == 8000-FF00. Therefore FFFF will be out of the 80-FF range. 80- means: ‘anything greater

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Why throttler: maintaining low replication lag . . . . . . . . . . . . . . . . . . . . . . . . . . . . keyrange. Thus: -80 == 00-80 == 0000-8000 == 000000-800000 80- is not the same as 80-FF. This is why: 80-FF == 8000-FF00. Therefore FFFF will be out of the 80-FF range. 80- means: ‘anything greater changes, it is a good idea to start by creating an issue - this is where you can discuss the feature and why it’s important. Once that is in place, you can create the PR, as a solution to the problem described

keyrange. Thus: -80 == 00-80 == 0000-8000 == 000000-800000 80- is not the same as 80-FF. This is why: 80-FF == 8000-FF00. Therefore FFFF will be out of the 80-FF range. 80- means: ‘anything greater Sometimes this message can also contain more material for reference e.g. benchmark numbers to justify why the change was implemented in this way. • Comments – // Prefer complete sentences when possible. starting the commit process, and also clean them up after a successful commit. This is the reason why it is a separate option instead of being always on. Isolation 2PC transactions guarantee atomicity:

Sometimes this message can also contain more material for reference e.g. benchmark numbers to justify why the change was implemented in this way. • Comments – // Prefer complete sentences when possible. does this mean: -80 == 00-80 == 0000-8000 == 000000-800000 80- is not the same as 80-FF. This is why: 80-FF == 8000-FF00. Therefore FFFF will be out of the 80-FF range. 80- means: ‘anything greater starting the commit process, and also clean them up after a successful commit. This is the reason why it is a separate option instead of being always on. Isolation 2PC transactions guarantee atomicity:

keyrange. Thus: -80 == 00-80 == 0000-8000 == 000000-800000 80- is not the same as 80-FF. This is why: 13 80-FF == 8000-FF00. Therefore FFFF will be out of the 80-FF range. 80- means: ‘anything greater Sometimes this message can also contain more material for reference e.g. benchmark numbers to justify why the change was implemented in this way. • Comments – // Prefer complete sentences when possible. starting the commit process, and also clean them up after a successful commit. This is the reason why it is a separate option instead of being always on. Isolation 2PC transactions guarantee atomicity: