Hi Val, Do you mean by > switching marshaller cache to persistence instead of using these files makes perfect sense to me, using 'metastore' for marshaller cache?
Sincerely, Dmitriy Pavlov пт, 9 февр. 2018 г. в 1:05, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Sergey, > > These mappings are supposed to be the same on all nodes, so if the file > already exists, we can safely ignore this, or use a lock to avoid > concurrent access. Actually, I think we already fixed this in the past, > it's weird that issue came up again. > > But in any case, switching marshaller cache to persistence instead of using > these files makes perfect sense to me, and we definitely should do that. > > -Val > > On Tue, Feb 6, 2018 at 1:04 AM, Sergey Chugunov <sergey.chugu...@gmail.com > > > wrote: > > > Folks, > > > > There are several things here. > > > > Firstly user asked the initial question is sitting on Apache 1.x; it is > > clear from exception stack trace he provided. > > So although the issue exists for a while it looks like it doesn't hurt > > users a lot. > > > > Secondly I examined the code managing marshaller mappings and can say > that > > it the issue is still here even in the latest version; thus I filed a > > ticket [1] to address it. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-7635 > > > > Thanks, > > Sergey. > > >
