Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Tue, 28 Jun 2016 08:55:57 +0000 (UTC)
From: "Vladimir Ozerov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12860108.1440772856000.4645.1467104157315@Atlassian.JIRA>
In-Reply-To: <JIRA.12860108.1440772856000@Atlassian.JIRA>
References: <JIRA.12860108.1440772856000@Atlassian.JIRA> <JIRA.12860108.1440772856414@arcas>
Subject: [jira] [Updated] (IGNITE-1326) IGFS: data write errors should be
 failed over in the level of IGFS output stream implementation.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 28 Jun 2016 08:55:59 -0000


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

Vladimir Ozerov updated IGNITE-1326:
------------------------------------
    Fix Version/s: 1.5.0.final

> IGFS: data write errors should be failed over in the level of IGFS output stream implementation.
> ------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-1326
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1326
>             Project: Ignite
>          Issue Type: Bug
>          Components: IGFS
>    Affects Versions: 1.4
>            Reporter: Ivan Veselovsky
>            Assignee: Ivan Veselovsky
>             Fix For: 1.5.0.final
>
>
> See org.apache.ignite.internal.processors.igfs.IgfsDataManager.WriteCompletionFuture#onError : currently if a node failed to receive data block, this implementation completes the write future with an Exception, so output stream method will throw exception. 
> Preferably we should do failover there , recalculate blocks affinity on the new topology and re-send the block(s) again.
> We can also just use the cache .put() functionality (manual sending of the file blocks was implemented due to performance optimization, as far I know).


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