mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-993) Performance issue during replicated log catch-up when the initial log position is large
Date Mon, 24 Feb 2014 19:41:20 GMT

     [ https://issues.apache.org/jira/browse/MESOS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jie Yu updated MESOS-993:
-------------------------

    Fix Version/s:     (was: 0.18.0)
                   0.17.0

> 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.17.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)

Mime
View raw message