Regarding TRANSACTIONAL_SNAPSHOT

classic Classic list List threaded Threaded
4 messages Options
VeenaMithare VeenaMithare
Reply | Threaded
Open this post in threaded view
|

Regarding TRANSACTIONAL_SNAPSHOT

Hi,

1. We wanted to try TRANSACTIONAL_SNAPSHOT Atomicity Mode. Wanted to know if
it is production version ?Asking since I noticed the below in the
documentation . Not sure if this applies for the  TRANSACTIONAL_SNAPSHOT
atomicity mode as well .

(https://apacheignite.readme.io/docs/transactions)
Beta version of Transactional SQL and MVCC
In Ignite v2.7, Transactional SQL and MVCC are released as beta versions to
allow users to experiment and share feedback. This version of Transactional
SQL and MVCC should not be considered for production.

2.  I enabled the TRANSACTIONAL_SNAPSHOT mode and did an insert of a record
from DBeaver. I did not get  a CACHE_PUT event. The only two events I can
see are TX_STARTED, TX_COMMITTED.
What other events can we expect if a insert sql is executed and cache is in
TRANSACTIONAL_SNAPSHOT mode.





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Roman Kondakov Roman Kondakov
Reply | Threaded
Open this post in threaded view
|

Re: Regarding TRANSACTIONAL_SNAPSHOT

Hi,

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.


--
Kind Regards
Roman Kondakov


On 18.02.2020 20:11, VeenaMithare wrote:

> Hi,
>
> 1. We wanted to try TRANSACTIONAL_SNAPSHOT Atomicity Mode. Wanted to know if
> it is production version ?Asking since I noticed the below in the
> documentation . Not sure if this applies for the  TRANSACTIONAL_SNAPSHOT
> atomicity mode as well .
>
> (https://apacheignite.readme.io/docs/transactions)
> Beta version of Transactional SQL and MVCC
> In Ignite v2.7, Transactional SQL and MVCC are released as beta versions to
> allow users to experiment and share feedback. This version of Transactional
> SQL and MVCC should not be considered for production.
>
> 2.  I enabled the TRANSACTIONAL_SNAPSHOT mode and did an insert of a record
> from DBeaver. I did not get  a CACHE_PUT event. The only two events I can
> see are TX_STARTED, TX_COMMITTED.
> What other events can we expect if a insert sql is executed and cache is in
> TRANSACTIONAL_SNAPSHOT mode.
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
danami danami
Reply | Threaded
Open this post in threaded view
|

Re: Regarding TRANSACTIONAL_SNAPSHOT

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/
dmagda dmagda
Reply | Threaded
Open this post in threaded view
|

Re: Regarding TRANSACTIONAL_SNAPSHOT

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 <[hidden email]> 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/