You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/03/11 07:19:00 UTC
[jira] [Updated] (IGNITE-9484) MVCC TX: Handling transactions from
multiple threads in jdbc requests handler.
[ https://issues.apache.org/jira/browse/IGNITE-9484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-9484:
------------------------------------
Ignite Flags: (was: Docs Required)
> MVCC TX: Handling transactions from multiple threads in jdbc requests handler.
> ------------------------------------------------------------------------------
>
> Key: IGNITE-9484
> URL: https://issues.apache.org/jira/browse/IGNITE-9484
> Project: Ignite
> Issue Type: Task
> Components: jdbc, mvcc
> Reporter: Roman Kondakov
> Priority: Major
>
> Currently JDBC/ODBC requests are handled in NioWorker threads; that means what sessions may be rebalanced between nio threads which makes impossible to associate a NearTransaction with caller thread.
> There are two possible solutions:
> # To process client messages like regular grid ones in separate thread pool in thread-per-connection basis
> # Implement Suspend/Resume functionality for pessimistic transactions like it was done for optimistic ones (only pessimistic transactions are supported by mvcc-enabled caches)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)