phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-3612) Make tracking of max allowed number of mutations bytes based instead of row based
Date Thu, 19 Jan 2017 23:32:26 GMT
James Taylor created PHOENIX-3612:
-------------------------------------

             Summary: Make tracking of max allowed number of mutations bytes based instead
of row based
                 Key: PHOENIX-3612
                 URL: https://issues.apache.org/jira/browse/PHOENIX-3612
             Project: Phoenix
          Issue Type: Bug
            Reporter: James Taylor


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.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message