[
https://issues.apache.org/jira/browse/MESOS-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355896#comment-17355896
]
Charles Natali commented on MESOS-10216:
----------------------------------------
Tough one, although I would err on the side of safety and not backport, since
it's been present since basically forever and realistically only affects few
users.
> Replicated log key encoding overflows into negative values
> ----------------------------------------------------------
>
> Key: MESOS-10216
> URL: https://issues.apache.org/jira/browse/MESOS-10216
> Project: Mesos
> Issue Type: Bug
> Components: replicated log
> Affects Versions: 1.7.3, 1.8.1, 1.9.1, 1.11.0, 1.10.1, 1.12.0
> Reporter: Ilya
> Assignee: Charles Natali
> Priority: Major
> Fix For: 1.12.0
>
>
> LevelDB keys used by {{LevelDBStorage}} are {{uint64_t}} log positions
> encoded as strings and padded with zeroes up to a certain fixed size. The
> {{encode()}} function is incorrect because it uses the {{%d}} formatter that
> expects an {{int}}. It also limits the key size to 10 digits which is OK for
> {{UINT32_MAX}} but isn't enough for {{UINT64_MAX}}.
> Because of this the available key range is reduced, and key overflow can
> result in replica's {{METADATA}} record (position 0) being overwritten, which
> in turn may cause data loss.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
