[
https://issues.apache.org/jira/browse/PHOENIX-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039268#comment-16039268
]
James Taylor commented on PHOENIX-3788:
---------------------------------------
Good point, [~gjacoby]. We wouldn't know the byte size of the batches from the
client. The most we'd currently know is how many total rows were committed.
We'd need to return more data from the server if we want to report this. It's a
limitation of client-side metrics. An enhancement like this would be more of a
4.12 item. For now, not sure if we should make any change - we could report the
estimated row counts (as planned here) with a zero byte size or we could not
report anything for this particular case. Or perhaps we could filter out these
large batches from any splunk dashboards by looking at the bytes committed
(which may be zero?).
> 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.12.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)
