[
https://issues.apache.org/jira/browse/KAFKA-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Widman updated KAFKA-5584:
-------------------------------
Description:
The {{size}} of a {{Log}} is calculated incorrectly due to an Integer overflow.
For large topics (larger than 2 GB) this value overflows.
This is easily observable in the reported metrics values of the path
{{log.Log.partition.*.topic.<topicname>.Size}} (see attached screenshot).
Moreover I think this breaks the size-based retention (via
{{log.retention.bytes}} and {{retention.bytes}}) of large topics as well.
I am not sure on the recommended workflow, should I open a pull request on
github with a fix?
was:
The {{size}} of a {{Log}} is calculated incorrectly due to an Integer overflow.
For large topics (larger than 2 GB) this value overflows.
This is easily observable in the reported metrics values of the path
{{log.Log.partiion.*.topic.<topicname>.Size}} (see attached screenshot).
Moreover I think this breaks the size-based retention (via
{{log.retention.bytes}} and {{retention.bytes}}) of large topics as well.
I am not sure on the recommended workflow, should I open a pull request on
github with a fix?
> Incorrect log size for topics larger than 2 GB
> ----------------------------------------------
>
> Key: KAFKA-5584
> URL: https://issues.apache.org/jira/browse/KAFKA-5584
> Project: Kafka
> Issue Type: Bug
> Components: log
> Reporter: Gregor Uhlenheuer
> Attachments: Screen Shot 2017-07-12 at 09.10.53.png
>
>
> The {{size}} of a {{Log}} is calculated incorrectly due to an Integer
> overflow. For large topics (larger than 2 GB) this value overflows.
> This is easily observable in the reported metrics values of the path
> {{log.Log.partition.*.topic.<topicname>.Size}} (see attached screenshot).
> Moreover I think this breaks the size-based retention (via
> {{log.retention.bytes}} and {{retention.bytes}}) of large topics as well.
> I am not sure on the recommended workflow, should I open a pull request on
> github with a fix?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
