ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-182) Free space handling is incorrect when colocated=true in IgniteFS file create request
Date Thu, 21 Jul 2016 10:07:20 GMT

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

Vladimir Ozerov resolved IGNITE-182.
------------------------------------
    Resolution: Won't Fix

We will remove "free space" notion from IGFS altogether soon and will only rely on eviction
policies. Hence, closing the issue.

> Free space handling is incorrect when colocated=true in IgniteFS file create request
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-182
>                 URL: https://issues.apache.org/jira/browse/IGNITE-182
>             Project: Ignite
>          Issue Type: Task
>          Components: hadoop
>    Affects Versions: sprint-1
>            Reporter: Alexey Kuznetsov
>            Assignee: Ivan Veselovsky
>
> Set collocated flag to true and copy several large files in grid with more than 1 node
with igniteFS.
> The issue is caused by mistakenly set colocated=true flag. In this case space handling
should be different and take into account current free space on node.
> Also estimated free space for GGFS should be calculated more accurate and allocate less
space when heap is small.



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

Mime
View raw message