Hi Sergey, Just FYI: a similar problem with replicated caches has been fixed in SQL [1]. If you have a reproducer, you may check whether your issue is still actual.
[1]: https://issues.apache.org/jira/browse/IGNITE-12482 On Thu, Jan 16, 2020 at 1:51 PM Sergey-A Kosarev <sergey-a.kosa...@db.com> wrote: > Classification: Public > Hello, Igniters, > > Recently I've came across a problem with REPLICATED caches, so I've > created an issue: > https://issues.apache.org/jira/browse/IGNITE-12549 > > Please look at this. I believe, it's a bug. > > Not sure I could fix it quickly, feel free to take it if you like. > > And as workaround I think PARTITIONED caches with Integer.MAX_VALUE > backups can be used instead of REPLICATED caches. > > Will be glad for any feedback. > > Kind regards, > Sergey Kosarev > > > > > --- > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and delete this e-mail. Any > unauthorized copying, disclosure or distribution of the material in this > e-mail is strictly forbidden. > > Please refer to https://www.db.com/disclosures for additional EU > corporate and regulatory disclosures and to > http://www.db.com/unitedkingdom/content/privacy.htm for information about > privacy. > -- Best Regards, Ivan Rakov
