ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Taras Ledkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3521) IGFS: Remove "max space" notion.
Date Fri, 21 Apr 2017 13:17:04 GMT

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

Taras Ledkov commented on IGNITE-3521:
--------------------------------------

Waits for TC [results|http://195.239.208.174/project.html?projectId=IgniteTests&tab=projectOverview&branch_IgniteTests=pull%2F1854%2Fhead]

> 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: Alexey Kuznetsov
>             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)

Mime
View raw message