[PHOENIX-3612] Make tracking of max allowed number of mutations bytes based instead of row based

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.11.0
• Assignee: Thomas D'Silva
• Reporter: James R. Taylor
• Created: 19/Jan/17 23:32
• Updated: 02/Jun/17 22:24
• Resolved: 02/Jun/17 21:23

Description

Some remaining work related to PHOENIX-541 to track the byte-size of all mutations being buffered instead of the number of rows:

• Make similar changes QueryServices.MAX_MUTATION_SIZE_ATTRIB - making it byte-based instead of row-count-based. Usage of this config parameter would be isolated to MutationState, I believe. We should be able to come up with an accurate size based on the underlying Mutation and/or Delete info we store in PRowImpl.
• Have a reasonable (smaller) default for the new QueryServices.MAX_MUTATION_SIZE_BYTES_ATTRIB
  This is essentially a guard on the memory usage. It could potentially leverage our MemoryManager.