You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/04/19 10:13:41 UTC

[jira] [Commented] (IGNITE-3521) IGFS: Remove "max space" notion.

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

Vladimir Ozerov commented on IGNITE-3521:
-----------------------------------------

For total space we must rely on cache memory policy.

> IGFS: Remove "max space" notion.
> --------------------------------
>
>                 Key: IGNITE-3521
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3521
>             Project: Ignite
>          Issue Type: Task
>          Components: IGFS
>    Affects Versions: 1.6
>            Reporter: Vladimir Ozerov
>            Assignee: Taras Ledkov
>             Fix For: 2.0
>
>
> We have "max space" concept in IGFS which governs maximum amount of local data available for IGFS. This concept looks a bit weird because we do not have the same thing in caches. 
> Moreover, we have several conflicting configuration parameters:
> 1) {{IgfsPerBlockLruEvictionPolicy}} where we also can specify maximum size.
> 2) {{CacheConfiguration.offheapMaxMemory}} which also governs evictions.
> It looks like we should simply remove "max space" property from IGFS configuration and do not control it anyhow.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)