[
https://issues.apache.org/jira/browse/MESOS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone resolved MESOS-993.
------------------------------
Resolution: Fixed
Im resolving this because we have a committed a version of the fix.
Can you please open a new one for the refactor?
commit 6eb9c50fde4ebfb0a3047535bfcbe5bc9c349dc6
Author: Jie Yu <[email protected]>
Date: Thu Feb 13 14:43:03 2014 -0800
Used interval set to store holes and unlearned positions in replica.
Review: https://reviews.apache.org/r/18062
commit db6974bb10612bc3e9a012364cb108ab9bd2c72a
Author: Jie Yu <[email protected]>
Date: Thu Feb 13 14:41:53 2014 -0800
Updated boost library to include files for interval set.
> Performance issue during replicated log catch-up when the initial log
> position is large
> ---------------------------------------------------------------------------------------
>
> Key: MESOS-993
> URL: https://issues.apache.org/jira/browse/MESOS-993
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.17.0
> Reporter: Jie Yu
> Assignee: Jie Yu
> Fix For: 0.18.0
>
>
> Inside Replica::persist(const Action& action), we update the in-memory
> 'holes' data structure
> // Update holes if we just wrote many positions past the last end.
> for (uint64_t position = end + 1; position < action.position(); position++)
> {
> holes.insert(position);
> }
> During catch-up (starts with an empty log), if the 'position' is very large,
> we may spend a lot of time in this loop. Also, the data structure 'holes'
> might become extremely large.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
