Hi Dana, Here you can find a list of known high-level limitations: https://apacheignite.readme.io/docs/multiversion-concurrency-control#limitations
Also, the performance might not be satisfactory and not all the cluster failure scenarios might be covered. Generally, as of know, I would advise you to use the key-value transactions of Ignite that are battle-tested and used in productions since the inception of Ignite. - Denis On Thu, Sep 3, 2020 at 6:41 AM danami <danash...@gmail.com> wrote: > Roman Kondakov wrote > > 1. TRANSACTIONAL_SNAPSHOT is still in beta version. Perhaps the current > > version of MVCC will be completely redone in the future. So, it is not a > > good idea to use it in production systems right now. > > > > 2. Events are not implemented for MVCC yet. As well as several other > > features that presented in conventional TRANSACTIONAL cache: > > interceptors, recovery, etc. > > > Hi all, > > Can someone elaborate on the missing features of TRANSACTIONAL_SNAPSHOT > cache mode or point me to some source of information that elaborates them? > > Are there any known bugs related to it in current Ignite version? > > Besides the possibility of it completely getting redone in the future, what > would other major throwbacks be if it were used in production? > > Thank you very much, > Dana > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
