Hi Igniters, As far as I remember, matching workDir for different nodes in marshaller context are protected by file locks to avoid concurrent file modifications.
Sergey C. what do you think? Or am I confuse Marhsaller Context with Binary Meta? Sincerely, Dmitry Pavlov чт, 1 февр. 2018 г. в 5:18, Dmitriy Setrakyan <dsetrak...@apache.org>: > Cross sending to dev@. > > Would be nice to hear from the Ignite community. How critical is this issue > and does it still exist? > > D. > > ---------- Forwarded message ---------- > From: Denis Magda <dma...@apache.org> > Date: Tue, Jan 9, 2018 at 2:28 PM > Subject: Re: Ignite work directory usage? > To: u...@ignite.apache.org > > > It needs to be fixed if the users constantly bump into this issue. However, > I guess it’s not a matter of urgency now. > > — > Denis > > > On Jan 8, 2018, at 6:30 AM, ilya.kasnacheev <ilya.kasnach...@gmail.com> > wrote: > > > > Hello Denis! > > > > There seems to be cases where matching workDir for different nodes > > (including client nodes) will cause problems: > > > > http://apache-ignite-users.70518.x6.nabble.com/MarshallerCon > textImpl-Failed-to-write-class-name-to-file-td18439.html > > > > There, on Windows, two nodes try to update binary marshaller cache on > disk > > at the same time, but, this being on Windows, one of them fails to open > file > > for writing. > > > > On other OSes there also exists case where one instance would open file > for > > writing, and other one, seeing that there is already a file present, > tries > > to read it, reads zero bytes and fails at that. > > > > WDYT about this case? > > > > Regards, > > > > > > > > -- > > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
