You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2017/03/13 20:02:41 UTC

[jira] [Created] (KUDU-1936) Potential 2B max log index size

Mike Percy created KUDU-1936:
--------------------------------

             Summary: 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


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)