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 2016/07/21 10:07:20 UTC
[jira] [Resolved] (IGNITE-182) Free space handling is incorrect
when colocated=true in IgniteFS file create request
[ 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)