[ 
https://issues.apache.org/jira/browse/IGNITE-8692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-8692:
------------------------------------
    Description: Currently TxLog may be overflowed in case a long running Tx 
prevents "vacuuming". It can be solved by enabling persistence for TxLog data 
region by default. Alternatively, we may forcibly fail such transactions with 
"history is too short" error (like in Oracle).  (was: Currently TxLog may be 
overflowed in case a long running Tx prevents "vacuuming".

It can be solved by enabling persistence for TxLog data region by default.)

> MVCC TX: Protect TX log from overflow in in-memory mode
> -------------------------------------------------------
>
>                 Key: IGNITE-8692
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8692
>             Project: Ignite
>          Issue Type: Task
>          Components: cache, mvcc
>            Reporter: Igor Seliverstov
>            Priority: Major
>
> Currently TxLog may be overflowed in case a long running Tx prevents 
> "vacuuming". It can be solved by enabling persistence for TxLog data region 
> by default. Alternatively, we may forcibly fail such transactions with 
> "history is too short" error (like in Oracle).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to