[KUDU-1936] Potential 2B max log index size

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.3.0
• Fix Version/s: n/a
• Component/s: consensus
• Assignee: Unassigned
• Reporter: Mike Percy
• Created: 13/Mar/17 20:01
• Updated: 13/Mar/17 23:31
• Resolved: 13/Mar/17 23:30

Description

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:

F0313 log_index.cc:171 Check failed: log_index > 0 (-2147483648 vs. 0) 

Issue Links

• duplicates: KUDU-1933 OpId index 32-bit overflow (was: Master crashes after too many TS re-registrations)