Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 324C818A8C for ; Thu, 18 Feb 2016 00:14:14 +0000 (UTC) Received: (qmail 13114 invoked by uid 500); 18 Feb 2016 00:14:13 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 13069 invoked by uid 500); 18 Feb 2016 00:14:13 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 13059 invoked by uid 99); 18 Feb 2016 00:14:13 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Feb 2016 00:14:13 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 73503180470 for ; Thu, 18 Feb 2016 00:14:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.972 X-Spam-Level: X-Spam-Status: No, score=0.972 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id RPkLVhT2YBi8 for ; Thu, 18 Feb 2016 00:14:12 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTP id 0ADD05F119 for ; Thu, 18 Feb 2016 00:14:11 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 9818D20F8605 for ; Wed, 17 Feb 2016 16:07:29 -0800 (PST) Date: Wed, 17 Feb 2016 16:02:15 -0800 (PST) From: Kobe To: user@ignite.apache.org Message-ID: <1455753735540-3067.post@n6.nabble.com> In-Reply-To: <1455749358346-3065.post@n6.nabble.com> References: <1455749358346-3065.post@n6.nabble.com> Subject: Re: IGFS: Writing to a nonexistent file: "Failed to append to the file due to secondary file system exception" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I see that this is a known issue: https://issues.apache.org/jira/browse/IGNITE-1631 and is planned to be resolved in 1.6 What is the workaround? Should I choose not to use DUAL_SYNC? If I create the file using IgniteFileSystem.create() would that sidestep this problem? Thanks, Rk x77309 -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/IGFS-Writing-to-a-nonexistent-file-Failed-to-append-to-the-file-due-to-secondary-file-system-excepti-tp3065p3067.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.