[
https://issues.apache.org/jira/browse/IGNITE-25511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Pligin updated IGNITE-25511:
-------------------------------------
Labels: ignite-3 (was: )
> Improve error message when a sql fragment fails because of ro tx timeout
> underneath
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-25511
> URL: https://issues.apache.org/jira/browse/IGNITE-25511
> Project: Ignite
> Issue Type: Improvement
> Components: sql ai3
> Reporter: Vladimir Pligin
> Priority: Critical
> Labels: ignite-3
>
> Currently a user would see a message like this in their logs.
> {code:java}
> Caused by:
> org.apache.ignite.internal.sql.engine.exec.RemoteFragmentExecutionException:
> IGN-TX-13 TraceId:95e939eb-e9a0-42dc-8aee-6fcbdc52ea8e Transaction is already
> finished () [txId=01961a63-27cf-0000-0642-127000000001, readOnly=true]. at
> org.apache.ignite.internal.sql.engine.exec.ExecutionServiceImpl.onMessage(ExecutionServiceImpl.java:673)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionServiceImpl.lambda$start$4(ExecutionServiceImpl.java:331)
> at
> org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:158)
> at
> org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.lambda$onMessage$2(MessageServiceImpl.java:124)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:78)
> ... 3 more{code}
> It does not give any clue about the reason why SQL engine interacts with a
> {code:java}
> Transaction is already finished (){code}
> We have to supply users with better messages, for example:
> {code:java}
> transaction timeout, increase ignite.transactions.readOnlyTimeout{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
