[
https://issues.apache.org/jira/browse/KUDU-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Percy resolved KUDU-1936.
------------------------------
Resolution: Duplicate
Fix Version/s: n/a
> Potential 2B max log index size
> -------------------------------
>
> Key: KUDU-1936
> URL: https://issues.apache.org/jira/browse/KUDU-1936
> Project: Kudu
> Issue Type: Bug
> Components: consensus
> Affects Versions: 1.3.0
> Reporter: Mike Percy
> Fix For: n/a
>
>
> We have a report of a potential truncation of a 64 bit integer to 32 bits on
> a log index. This effectively means we can only update a tablet 2B times
> before crashing on an integer overflow.
> I'm currently investigating and working on reproducing this.
> Log message looks like this:
> {noformat}
> F0313 log_index.cc:171 Check failed: log_index > 0 (-2147483648 vs. 0)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
