Jesse Seldess (jseldess) commented:
We need a recommendation against letting a single row get close to 64MB (the default size at which we split a range). In addition to the current row data, all historical versions of the row that have not been garbage collected count toward the overall size.
Normally, a range contains many rows, in which case when the range gets to the limit, we split into 2 ranges. If a single row takes up all of a range, however, we won't split the range but rather let it get larger than the max limit.
- As the row size increases further, memory usage may get spikier (eventually reaching a point where servers will start running out of memory and dying).
- At some point, we’ll stop rebalancing the range as well because it is too large.
Jira Issue: DOC-125
Jesse Seldess (jseldess) commented:
We need a recommendation against letting a single row get close to 64MB (the default size at which we split a range). In addition to the current row data, all historical versions of the row that have not been garbage collected count toward the overall size.
Normally, a range contains many rows, in which case when the range gets to the limit, we split into 2 ranges. If a single row takes up all of a range, however, we won't split the range but rather let it get larger than the max limit.
Jira Issue: DOC-125