[ https://issues.apache.org/jira/browse/PHOENIX-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014333#comment-16014333 ]
Geoffrey Jacoby commented on PHOENIX-3788: ------------------------------------------ What are the consequences of the client and server logging separate mutation sizes? The only times I've needed to look at GLOBAL_MUTATION_BATCH_SIZE it's been on the region servers, not the client. What do clients use them for? (Of course, there are also cases where a region server is a client, such as in some upsert selects.) > GLOBAL_MUTATION_BATCH_SIZE should reflect size of chunked batches > ----------------------------------------------------------------- > > Key: PHOENIX-3788 > URL: https://issues.apache.org/jira/browse/PHOENIX-3788 > Project: Phoenix > Issue Type: Bug > Affects Versions: 4.10.0 > Reporter: Geoffrey Jacoby > Assignee: Geoffrey Jacoby > Fix For: 4.11.0 > > Attachments: PHOENIX-3788.patch > > > As part of PHOENIX-541, we started chunking large MutationStates into > multiple smaller batches transparently. However, the relevant metric, > GLOBAL_MUTATION_BATCH_SIZE, still is updated with the total batch size, not > the size of each chunk. This means you can't see the actual batch sizes which > are being submitted to HBase. -- This message was sent by Atlassian JIRA (v6.3.15#6346)