You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Kobe <rk...@mailcity.com> on 2016/02/18 01:02:15 UTC
Re: IGFS: Writing to a nonexistent file: "Failed to append to the
file due to secondary file system exception"
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.
Re: IGFS: Writing to a nonexistent file: "Failed to append to the
file due to secondary file system exception"
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Kobe,
Append and create operations cannot use the same code path since append
operation require some additional synchronization between primary and
secondary file systems. Anyway, the problem is known and will be fixed.
Vladimir.
On Thu, Feb 18, 2016 at 8:24 PM, Kobe <rk...@mailcity.com> wrote:
> I was able to sidestep the problem by using create(), however, this bothers
> me since,
> I would have expected update() and create() to be based on same set of
> underlying code.
>
> Thanks,
>
>
>
> Ivan Veselovsky wrote
> > Hi, Kobe,
> > yes, please use #create() method as a workaround, that should work.
> >
> > On Thu, Feb 18, 2016 at 3:02 AM, Kobe <
>
> > rk_@
>
> > > wrote:
> >
> >> 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.
> >>
>
>
>
>
>
> --
> 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-tp3065p3086.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: IGFS: Writing to a nonexistent file: "Failed to append to the
file due to secondary file system exception"
Posted by Kobe <rk...@mailcity.com>.
I was able to sidestep the problem by using create(), however, this bothers
me since,
I would have expected update() and create() to be based on same set of
underlying code.
Thanks,
Ivan Veselovsky wrote
> Hi, Kobe,
> yes, please use #create() method as a workaround, that should work.
>
> On Thu, Feb 18, 2016 at 3:02 AM, Kobe <
> rk_@
> > wrote:
>
>> 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.
>>
--
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-tp3065p3086.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: IGFS: Writing to a nonexistent file: "Failed to append to the
file due to secondary file system exception"
Posted by "Ivan V." <iv...@gridgain.com>.
Hi, Kobe,
yes, please use #create() method as a workaround, that should work.
On Thu, Feb 18, 2016 at 3:02 AM, Kobe <rk...@mailcity.com> wrote:
> 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.
>