[
https://issues.apache.org/jira/browse/IGNITE-15750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
vikram updated IGNITE-15750:
----------------------------
Summary: Ignite Read Write through with RDBMS based Cache Store (was:
Ignite Read Write through with Database backup)
> Ignite Read Write through with RDBMS based Cache Store
> ------------------------------------------------------
>
> Key: IGNITE-15750
> URL: https://issues.apache.org/jira/browse/IGNITE-15750
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.10, 2.11
> Reporter: vikram
> Priority: Critical
>
> When we configure ignite as read write through cache in container managed
> setup, JTA support appears buggy. Expectation and behaviour seen are
> described below
> Given
> -----
> CMT setup with necessary configurations like
> a. JTA transaction manager
> b. Tta synchronisation
> and
> c. Cache Store based on JDBC drivers
>
> Expectations:
> # When JTA transaction commits the write to database should be part of same
> transaction
> # Similarly behaviour in case of rollbacks
>
> Behaviour seen
> 1. Ignite write store is initiated post JTA commit
> This means the write to backend database is not in sync to replicated
> cache changes
> across cluster.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
