[
https://issues.apache.org/jira/browse/IGNITE-23455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-23455:
----------------------------------------
Description:
Case: _Fragment is sent to worker node but no response Is obtained and NodeLeft
event is triggered. No information is available about fragment execution
progress here, but we know that no data is passed from such a node._
1. In case of RO Tx only this fragment(s) can be remapped if no rows have been
sent to the client, for example some kind of aggregate query (we have no such
mechanisms for now) .
2. Implicit RW tx - tx need to be rolled back, execution must be restarted from
the mapping phase.
3. Explicit RW tx - not recoverable. Need to close cursor with informative
exception.
was:
Case: _Fragment is sent to worker node but no response Is obtained and NodeLeft
event is triggered. No information is available about fragment execution
progress here, but we know that no data is passed from such a node._
1. In case of RO Tx only this fragment(s) can be remapped (we have no such
mechanisms for now) .
2. Implicit RW tx - tx need to be rolled back, execution must be restarted from
the mapping phase.
3. Explicit RW tx - not recoverable. Need to close cursor with informative
exception.
> Sql. Fragment is sent to worker node, no response is obtained instead
> NodeLeft Is triggered
> -------------------------------------------------------------------------------------------
>
> Key: IGNITE-23455
> URL: https://issues.apache.org/jira/browse/IGNITE-23455
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 3.0.0-beta1
> Reporter: Evgeny Stanilovsky
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
>
> Case: _Fragment is sent to worker node but no response Is obtained and
> NodeLeft event is triggered. No information is available about fragment
> execution progress here, but we know that no data is passed from such a node._
> 1. In case of RO Tx only this fragment(s) can be remapped if no rows have
> been sent to the client, for example some kind of aggregate query (we have no
> such mechanisms for now) .
> 2. Implicit RW tx - tx need to be rolled back, execution must be restarted
> from the mapping phase.
> 3. Explicit RW tx - not recoverable. Need to close cursor with informative
> exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
