You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Hassan Eslami (JIRA)" <ji...@apache.org> on 2016/07/12 17:51:20 UTC

[jira] [Commented] (GIRAPH-1089) In fixed out-of-core policy the definition of in-memory partition is not clear

    [ https://issues.apache.org/jira/browse/GIRAPH-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373324#comment-15373324 ] 

Hassan Eslami commented on GIRAPH-1089:
---------------------------------------

https://reviews.facebook.net/D60573

> In fixed out-of-core policy the definition of in-memory partition is not clear
> ------------------------------------------------------------------------------
>
>                 Key: GIRAPH-1089
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-1089
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Hassan Eslami
>            Assignee: Hassan Eslami
>             Fix For: 1.2.0
>
>
> The fixed out-of-core policy relies on the definition for in-memory partitions. However, the definition of in-memory partition is not clear, and this leads to bugs in fixed out-of-core policy. Currently, a partition is called in-memory only if the partition itself (regardless of its messages) is in memory. We should change the policy so that only partitions that have their current messages as well as the partition data in memory be considered as in-memory partitions. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)