[jira] [Created] (IGNITE-21900) meta --remove does not delete the .classname0 file from db/marshaller causing errors on subsequent type re-registration
Evgeny Stanilovsky created IGNITE-21900:
---
Summary: meta --remove does not delete the .classname0
file from db/marshaller causing errors on subsequent type re-registration
Key: IGNITE-21900
URL: https://issues.apache.org/jira/browse/IGNITE-21900
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 2.16
Reporter: Evgeny Stanilovsky
Assignee: Evgeny Stanilovsky
meta --remove command deletes the type from db// but not
from db/marshaller -
This causes errors if the server tries to re-create the type w/the same name
but different case.
say the user created the type model.Account (upper case A)
CREATE TABLE my_table(..) WITH
key_type=model.Accountkey,value_type=model.Account
then dropped the table, DROP TABLE my_table.
and ran a --meta remove --typeName mode.Account
If the users change the case of the type say from model.Account to
model.account – one letter to lowercase
and then does a subsequent:
CREATE TABLE my_table(..) WITH
key_type=model.accountkey,value_type=model.account
then does an INSERT, the server will come back with “Failed to register class”
{noformat}
Caused by: org.apache.ignite.internal.DuplicateTypeIdException: Duplicate ID
[platformId=0, typeId=1853064544,
oldCls=com.ual.cfa.fa.model.CFAFaPairNonFltDutyHistKey,
newCls=com.ual.cfa.fa.model.CFAFaPairNonfltDutyHistKey]
at
org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:223)
~[ignite-core.jar]
at
org.apache.ignite.internal.binary.BinaryContext.registerUserClassName(BinaryContext.java:1185)
~[ignite-core-.jar]
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21899) Fix for TC Bot with Ignite version 2.16
Oleg Valuyskiy created IGNITE-21899: --- Summary: Fix for TC Bot with Ignite version 2.16 Key: IGNITE-21899 URL: https://issues.apache.org/jira/browse/IGNITE-21899 Project: Ignite Issue Type: Task Reporter: Oleg Valuyskiy Assignee: Oleg Valuyskiy -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21445) IndexQuery ignores pageSize if setLocal=true is set
[ https://issues.apache.org/jira/browse/IGNITE-21445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy reassigned IGNITE-21445: --- Assignee: Oleg Valuyskiy > IndexQuery ignores pageSize if setLocal=true is set > --- > > Key: IGNITE-21445 > URL: https://issues.apache.org/jira/browse/IGNITE-21445 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.14 >Reporter: Maksim Timonin >Assignee: Oleg Valuyskiy >Priority: Major > Labels: ise > > In 2.14, see GridCacheQueryManager#runQuery:L1323 > If query is local it just collects all possible data. > For ScanQuery this code doesn't work, as it directly uses local > scanQueryIterator that returns entry one by one. > Solution: > # Prepare page for iterating > # Use the same logic as ScanQuery for local queries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21897) Sql. Invalid collation passthrough for sorted aggregates.
[
https://issues.apache.org/jira/browse/IGNITE-21897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-21897:
--
Priority: Minor (was: Major)
> Sql. Invalid collation passthrough for sorted aggregates.
> -
>
> Key: IGNITE-21897
> URL: https://issues.apache.org/jira/browse/IGNITE-21897
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Andrey Mashenkov
>Assignee: Andrey Mashenkov
>Priority: Minor
> Labels: ignite-3
> Fix For: 3.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> `IgniteSortAggregateBase.passThroughCollation` returns wrong collation in
> some cases.
> This results in bad plan, e.g. the next query has unexpected Exchanges for
> Distribution.SINGLE.
> {code:java}
> SELECT COUNT(val0), COUNT(DISTINCT(val1)) from test
> {code}
> The test `MapReduceSortAggregatePlannerTest.countDistinctGroupSetSingle`
> returns plan:
> {noformat}
> Project(EXPR$0=[CAST($0):BIGINT NOT NULL], EXPR$1=[$1])
> Project(EXPR$0=[$0], EXPR$1=[CAST($1):BIGINT NOT NULL])
> ReduceSortAggregate(group=[{}], EXPR$0=[$SUM0($0)],
> COUNT_1_MAP_SUM=[$SUM0($1)], collation=[[]])
> MapSortAggregate(group=[{}], EXPR$0=[$SUM0($1)], EXPR$1=[COUNT($0)],
> collation=[[]])
> Project(VAL1=[$0], EXPR$0=[CAST($1):BIGINT NOT NULL])
> ReduceSortAggregate(group=[{0}], COUNT_1_MAP_SUM=[$SUM0($1)],
> collation=[[0]])
> Exchange(distribution=[single])
> MapSortAggregate(group=[{1}], EXPR$0=[COUNT($0)],
> collation=[[1]])
> Sort(sort0=[$1], dir0=[ASC])
> Exchange(distribution=[random])
> TableScan(table=[[PUBLIC, TEST]], requiredColumns=[{1,
> 2}])
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-21897) Sql. Invalid collation passthrough for sorted aggregates.
[
https://issues.apache.org/jira/browse/IGNITE-21897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov reassigned IGNITE-21897:
-
Assignee: Andrey Mashenkov
> Sql. Invalid collation passthrough for sorted aggregates.
> -
>
> Key: IGNITE-21897
> URL: https://issues.apache.org/jira/browse/IGNITE-21897
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Andrey Mashenkov
>Assignee: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
>
> `IgniteSortAggregateBase.passThroughCollation` returns wrong collation in
> some cases.
> This results in bad plan, e.g. the next query has unexpected Exchanges for
> Distribution.SINGLE.
> {code:java}
> SELECT COUNT(val0), COUNT(DISTINCT(val1)) from test
> {code}
> The test `MapReduceSortAggregatePlannerTest.countDistinctGroupSetSingle`
> returns plan:
> {noformat}
> Project(EXPR$0=[CAST($0):BIGINT NOT NULL], EXPR$1=[$1])
> Project(EXPR$0=[$0], EXPR$1=[CAST($1):BIGINT NOT NULL])
> ReduceSortAggregate(group=[{}], EXPR$0=[$SUM0($0)],
> COUNT_1_MAP_SUM=[$SUM0($1)], collation=[[]])
> MapSortAggregate(group=[{}], EXPR$0=[$SUM0($1)], EXPR$1=[COUNT($0)],
> collation=[[]])
> Project(VAL1=[$0], EXPR$0=[CAST($1):BIGINT NOT NULL])
> ReduceSortAggregate(group=[{0}], COUNT_1_MAP_SUM=[$SUM0($1)],
> collation=[[0]])
> Exchange(distribution=[single])
> MapSortAggregate(group=[{1}], EXPR$0=[COUNT($0)],
> collation=[[1]])
> Sort(sort0=[$1], dir0=[ASC])
> Exchange(distribution=[random])
> TableScan(table=[[PUBLIC, TEST]], requiredColumns=[{1,
> 2}])
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-21898) Remove reactive methods from AntiHijackingIgniteSql
[ https://issues.apache.org/jira/browse/IGNITE-21898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov resolved IGNITE-21898. Reviewer: Ivan Bessonov Resolution: Fixed > Remove reactive methods from AntiHijackingIgniteSql > --- > > Key: IGNITE-21898 > URL: https://issues.apache.org/jira/browse/IGNITE-21898 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > They were removed from IgniteSql interface. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21675) Prevent Ignite threads from being leaked to user via async public APIs
[ https://issues.apache.org/jira/browse/IGNITE-21675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy resolved IGNITE-21675. Resolution: Fixed Fixed under tickets split from this one > Prevent Ignite threads from being leaked to user via async public APIs > -- > > Key: IGNITE-21675 > URL: https://issues.apache.org/jira/browse/IGNITE-21675 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IGNITE-21896) Close RocksDB flush listener on stop
[ https://issues.apache.org/jira/browse/IGNITE-21896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy reopened IGNITE-21896: > Close RocksDB flush listener on stop > > > Key: IGNITE-21896 > URL: https://issues.apache.org/jira/browse/IGNITE-21896 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > RocksDbFlushListener is an instance of RocksDB's AbstractEventListener which > needs to be explicitly closed to prevent resource leaks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21898) Remove reactive methods from AntiHijackingIgniteSql
[ https://issues.apache.org/jira/browse/IGNITE-21898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21898: --- Description: They were removed from IgniteSql interface. > Remove reactive methods from AntiHijackingIgniteSql > --- > > Key: IGNITE-21898 > URL: https://issues.apache.org/jira/browse/IGNITE-21898 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > They were removed from IgniteSql interface. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-21879) Sql. Jdbc IdbcStatementSelfTest testOpenCursorsPureQuery is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832857#comment-17832857
]
Pavel Pereslegin edited comment on IGNITE-21879 at 4/1/24 2:18 PM:
---
Unfortunately I can't reproduce such failure locally.
Fortunately, I don't see such failures on the main branch... yet :(.
One of the clues may be that the following warnings are present in the log of
TeamCity ("_Cluster ID mismatch_"):
{noformat}
[org.apache.ignite.jdbc.ItJdbcStatementSelfTest.testOpenCursorsPureQuery()]
[Test Error Output]
[2024-03-27T06:57:59,583][WARN
][ForkJoinPool.commonPool-worker-3][ReliableChannel] Failed to establish
connection to 127.0.0.1:10800:
org.apache.ignite.client.IgniteClientConnectionException: IGN-CLIENT-8
TraceId:4ee58442-c349-4d7d-a79a-8243a263ab7c Cluster ID mismatch:
expected=9726af0d-d291-485f-8cfb-327641f51f5c,
actual=3923c0c5-5383-4d03-b845-a063fc121633
java.util.concurrent.CompletionException:
org.apache.ignite.client.IgniteClientConnectionException: IGN-CLIENT-8
TraceId:4ee58442-c349-4d7d-a79a-8243a263ab7c Cluster ID mismatch:
expected=9726af0d-d291-485f-8cfb-327641f51f5c,
actual=3923c0c5-5383-4d03-b845-a063fc121633
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:645)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
[?:?]
at
java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)
[?:?]
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:649)
[?:?]
at
java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
[?:?]
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) [?:?]
at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
[?:?]
at
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656) [?:?]
at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
[?:?]
at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
[?:?]
Caused by: org.apache.ignite.client.IgniteClientConnectionException: Cluster ID
mismatch: expected=9726af0d-d291-485f-8cfb-327641f51f5c,
actual=3923c0c5-5383-4d03-b845-a063fc121633
at
org.apache.ignite.internal.client.ReliableChannel$ClientChannelHolder.lambda$getOrCreateChannelAsync$2(ReliableChannel.java:797)
~[ignite-client-3.0.0-SNAPSHOT.jar:?]
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
~[?:?]
... 9 more
[2024-03-27T06:58:00,679][WARN
][ForkJoinPool.commonPool-worker-3][ReliableChannel] Failed to establish
connection to 127.0.0.1:10800:
org.apache.ignite.client.IgniteClientConnectionException: IGN-CLIENT-8
TraceId:58f0672a-d198-4269-b26a-10d437378bab Cluster ID mismatch:
expected=9726af0d-d291-485f-8cfb-327641f51f5c,
actual=3923c0c5-5383-4d03-b845-a063fc121633
java.util.concurrent.CompletionException:
org.apache.ignite.client.IgniteClientConnectionException: IGN-CLIENT-8
TraceId:58f0672a-d198-4269-b26a-10d437378bab Cluster ID mismatch:
expected=9726af0d-d291-485f-8cfb-327641f51f5c,
actual=3923c0c5-5383-4d03-b845-a063fc121633
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:645)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
[?:?]
at
java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)
[?:?]
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:649)
[?:?]
at
java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
[?:?]
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) [?:?]
at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
[?:?]
at
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656) [?:?]
at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
[?:?]
at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
[?:?]
Caused by:
[jira] [Commented] (IGNITE-21879) Sql. Jdbc IdbcStatementSelfTest testOpenCursorsPureQuery is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832857#comment-17832857
]
Pavel Pereslegin commented on IGNITE-21879:
---
Unfortunately I can't reproduce such failure locally.
Fortunately, I don't see such failures on the main branch... yet :(.
One of the clues may be that the following warnings are present in the log of
TeamCity:
{noformat}
[org.apache.ignite.jdbc.ItJdbcStatementSelfTest.testOpenCursorsPureQuery()]
[Test Error Output]
[2024-03-27T06:57:59,583][WARN
][ForkJoinPool.commonPool-worker-3][ReliableChannel] Failed to establish
connection to 127.0.0.1:10800:
org.apache.ignite.client.IgniteClientConnectionException: IGN-CLIENT-8
TraceId:4ee58442-c349-4d7d-a79a-8243a263ab7c Cluster ID mismatch:
expected=9726af0d-d291-485f-8cfb-327641f51f5c,
actual=3923c0c5-5383-4d03-b845-a063fc121633
java.util.concurrent.CompletionException:
org.apache.ignite.client.IgniteClientConnectionException: IGN-CLIENT-8
TraceId:4ee58442-c349-4d7d-a79a-8243a263ab7c Cluster ID mismatch:
expected=9726af0d-d291-485f-8cfb-327641f51f5c,
actual=3923c0c5-5383-4d03-b845-a063fc121633
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:645)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
[?:?]
at
java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)
[?:?]
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:649)
[?:?]
at
java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
[?:?]
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) [?:?]
at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
[?:?]
at
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656) [?:?]
at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
[?:?]
at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
[?:?]
Caused by: org.apache.ignite.client.IgniteClientConnectionException: Cluster ID
mismatch: expected=9726af0d-d291-485f-8cfb-327641f51f5c,
actual=3923c0c5-5383-4d03-b845-a063fc121633
at
org.apache.ignite.internal.client.ReliableChannel$ClientChannelHolder.lambda$getOrCreateChannelAsync$2(ReliableChannel.java:797)
~[ignite-client-3.0.0-SNAPSHOT.jar:?]
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
~[?:?]
... 9 more
[2024-03-27T06:58:00,679][WARN
][ForkJoinPool.commonPool-worker-3][ReliableChannel] Failed to establish
connection to 127.0.0.1:10800:
org.apache.ignite.client.IgniteClientConnectionException: IGN-CLIENT-8
TraceId:58f0672a-d198-4269-b26a-10d437378bab Cluster ID mismatch:
expected=9726af0d-d291-485f-8cfb-327641f51f5c,
actual=3923c0c5-5383-4d03-b845-a063fc121633
java.util.concurrent.CompletionException:
org.apache.ignite.client.IgniteClientConnectionException: IGN-CLIENT-8
TraceId:58f0672a-d198-4269-b26a-10d437378bab Cluster ID mismatch:
expected=9726af0d-d291-485f-8cfb-327641f51f5c,
actual=3923c0c5-5383-4d03-b845-a063fc121633
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:645)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
[?:?]
at
java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)
[?:?]
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:649)
[?:?]
at
java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
[?:?]
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) [?:?]
at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
[?:?]
at
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656) [?:?]
at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
[?:?]
at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
[?:?]
Caused by: org.apache.ignite.client.IgniteClientConnectionException: Cluster ID
mismatch:
[jira] [Resolved] (IGNITE-21896) Close RocksDB flush listener on stop
[ https://issues.apache.org/jira/browse/IGNITE-21896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko resolved IGNITE-21896. -- Resolution: Invalid > Close RocksDB flush listener on stop > > > Key: IGNITE-21896 > URL: https://issues.apache.org/jira/browse/IGNITE-21896 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > RocksDbFlushListener is an instance of RocksDB's AbstractEventListener which > needs to be explicitly closed to prevent resource leaks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21898) Remove reactive methods from AntiHijackingIgniteSql
Roman Puchkovskiy created IGNITE-21898: -- Summary: Remove reactive methods from AntiHijackingIgniteSql Key: IGNITE-21898 URL: https://issues.apache.org/jira/browse/IGNITE-21898 Project: Ignite Issue Type: Improvement Reporter: Roman Puchkovskiy Assignee: Roman Puchkovskiy Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21897) Sql. Invalid collation passthrough for sorted aggregates.
Andrey Mashenkov created IGNITE-21897:
-
Summary: Sql. Invalid collation passthrough for sorted aggregates.
Key: IGNITE-21897
URL: https://issues.apache.org/jira/browse/IGNITE-21897
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Andrey Mashenkov
`IgniteSortAggregateBase.passThroughCollation` returns wrong collation in some
cases.
This results in bad plan, e.g. the next query has unexpected Exchanges for
Distribution.SINGLE.
{code:java}
SELECT COUNT(val0), COUNT(DISTINCT(val1)) from test
{code}
The test `MapReduceSortAggregatePlannerTest.countDistinctGroupSetSingle`
returns plan:
{noformat}
Project(EXPR$0=[CAST($0):BIGINT NOT NULL], EXPR$1=[$1])
Project(EXPR$0=[$0], EXPR$1=[CAST($1):BIGINT NOT NULL])
ReduceSortAggregate(group=[{}], EXPR$0=[$SUM0($0)],
COUNT_1_MAP_SUM=[$SUM0($1)], collation=[[]])
MapSortAggregate(group=[{}], EXPR$0=[$SUM0($1)], EXPR$1=[COUNT($0)],
collation=[[]])
Project(VAL1=[$0], EXPR$0=[CAST($1):BIGINT NOT NULL])
ReduceSortAggregate(group=[{0}], COUNT_1_MAP_SUM=[$SUM0($1)],
collation=[[0]])
Exchange(distribution=[single])
MapSortAggregate(group=[{1}], EXPR$0=[COUNT($0)], collation=[[1]])
Sort(sort0=[$1], dir0=[ASC])
Exchange(distribution=[random])
TableScan(table=[[PUBLIC, TEST]], requiredColumns=[{1, 2}])
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-21580) Sql. Unable to optimise query using only two phase aggregates
[
https://issues.apache.org/jira/browse/IGNITE-21580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov reassigned IGNITE-21580:
-
Assignee: Andrey Mashenkov (was: Maksim Zhuravkov)
> Sql. Unable to optimise query using only two phase aggregates
> -
>
> Key: IGNITE-21580
> URL: https://issues.apache.org/jira/browse/IGNITE-21580
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
>
> As for now, query planner returns following plan for q1 from TPC H suite:
> {code:java}
> IgniteColocatedSortAggregate
> IgniteExchange(distribution=[single])
> IgniteSort
> IgniteIndexScan(index=[L_SD], searchBounds=[[RangeBounds
> [lowerBound=null, upperBound=-(1998-12-01, 777600:INTERVAL DAY),
> lowerInclude=true, upperInclude=true]]])
> {code}
> The first problem is it's not even optimal variant from possible ones. By
> simply excluding {{SortAggregateConverterRule.COLOCATED}} from planning
> phase, we will get plan as follow:
> {code:java}
> IgniteSort
> IgniteColocatedHashAggregate
> IgniteExchange(distribution=[single])
> IgniteIndexScan(index=[L_SD], searchBounds=[[RangeBounds
> [lowerBound=null, upperBound=-(1998-12-01, 777600:INTERVAL DAY),
> lowerInclude=true, upperInclude=true]]])
> {code}
> Latter plan is executed ~40% faster than the first one.
> Seems, it's possible to reduce time even further by taking an advantage of
> two-phase aggregates, but disabling both version of colocated aggregates
> results in an exception during planning phase.
> Within this ticket, let's address the issue preventing optimiser from usage
> of two-phase aggregates, and also tweak cost function to make optimiser
> choose better plan.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21896) Close RocksDB flush listener on stop
[ https://issues.apache.org/jira/browse/IGNITE-21896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21896: --- Description: RocksDbFlushListener is an instance of RocksDB's AbstractEventListener which needs to be explicitly closed to prevent resource leaks. > Close RocksDB flush listener on stop > > > Key: IGNITE-21896 > URL: https://issues.apache.org/jira/browse/IGNITE-21896 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > RocksDbFlushListener is an instance of RocksDB's AbstractEventListener which > needs to be explicitly closed to prevent resource leaks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19758) Delete "StorageSortedIndexColumnDescriptor#name"
[ https://issues.apache.org/jira/browse/IGNITE-19758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-19758: - Assignee: (was: Andrey Mashenkov) > Delete "StorageSortedIndexColumnDescriptor#name" > > > Key: IGNITE-19758 > URL: https://issues.apache.org/jira/browse/IGNITE-19758 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Priority: Major > Labels: ignite-3 > > It's only really used in tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21896) Close RocksDB flush listener on stop
[ https://issues.apache.org/jira/browse/IGNITE-21896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy reassigned IGNITE-21896: -- Assignee: Roman Puchkovskiy > Close RocksDB flush listener on stop > > > Key: IGNITE-21896 > URL: https://issues.apache.org/jira/browse/IGNITE-21896 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21896) Close RocksDB flush listener on stop
Roman Puchkovskiy created IGNITE-21896: -- Summary: Close RocksDB flush listener on stop Key: IGNITE-21896 URL: https://issues.apache.org/jira/browse/IGNITE-21896 Project: Ignite Issue Type: Bug Reporter: Roman Puchkovskiy Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21895) Assertion rarely raised on LimitExecutionTest.testLimit
[ https://issues.apache.org/jira/browse/IGNITE-21895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-21895: Description: Unexpected exception: java.lang.AssertionError: expThread=%fake-test-node%sqlTestExec-0, actThread=%fake-test-node%sqlTestExec-1, qryId=aff12da0-7a28-4be8-9 379-47ca4b50ff44, fragmentId=0 > Assertion rarely raised on LimitExecutionTest.testLimit > --- > > Key: IGNITE-21895 > URL: https://issues.apache.org/jira/browse/IGNITE-21895 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 3.0.0-beta1 >Reporter: Evgeny Stanilovsky >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Unexpected exception: > java.lang.AssertionError: expThread=%fake-test-node%sqlTestExec-0, > actThread=%fake-test-node%sqlTestExec-1, qryId=aff12da0-7a28-4be8-9 > 379-47ca4b50ff44, fragmentId=0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21895) Assertion rarely raised on LimitExecutionTest.testLimit
Evgeny Stanilovsky created IGNITE-21895: --- Summary: Assertion rarely raised on LimitExecutionTest.testLimit Key: IGNITE-21895 URL: https://issues.apache.org/jira/browse/IGNITE-21895 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 3.0.0-beta1 Reporter: Evgeny Stanilovsky Assignee: Evgeny Stanilovsky -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21894) Undescriptive error when restart cluster node during open JDBC transaction
[
https://issues.apache.org/jira/browse/IGNITE-21894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-21894:
--
Summary: Undescriptive error when restart cluster node during open JDBC
transaction (was: Undescriptive error when restart cluster during open JDBC
transaction)
> Undescriptive error when restart cluster node during open JDBC transaction
> --
>
> Key: IGNITE-21894
> URL: https://issues.apache.org/jira/browse/IGNITE-21894
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, sql
>Affects Versions: 3.0.0-beta1
> Environment: 2 nodes cluster
>Reporter: Igor
>Priority: Minor
> Labels: ignite-3
>
> *Steps to reproduce:*
> 1. Start 2 nodes cluster.
> 2. Open JDBC connection, start transaction (using `.setAutoCommit(false)`).
> 3. Execute some insert queries. Do not commit the transaction.
> 4. Restart server node where connection was established.
> 5. Close JDBC statement and connection.
> *Expected:*
> Connection is closed with understandable error or without any error.
> *Actual:*
> Unclear exception on server side while closing the connection:
> {code:java}
> 2024-04-01 00:55:28:399 +
> [WARNING][ClusterFailoverMultiNodeTest_cluster_0-srv-worker-3][ClientInboundMessageHandler]
> Error processing client request [connectionId=1, id=1, op=55,
> remoteAddress=/127.0.0.1:59430]:Failed to find resource with id: 1
> org.apache.ignite.internal.lang.IgniteInternalException: IGN-CMN-65535
> TraceId:fe67e0da-5839-48c7-a59e-ca3465491698 Failed to find resource with id:
> 1
> at
> org.apache.ignite.client.handler.ClientResourceRegistry.get(ClientResourceRegistry.java:82)
> at
> org.apache.ignite.client.handler.JdbcQueryEventHandlerImpl.finishTxAsync(JdbcQueryEventHandlerImpl.java:390)
> at
> org.apache.ignite.client.handler.requests.jdbc.ClientJdbcFinishTxRequest.process(ClientJdbcFinishTxRequest.java:42)
> at
> org.apache.ignite.client.handler.ClientInboundMessageHandler.processOperation(ClientInboundMessageHandler.java:785)
> at
> org.apache.ignite.client.handler.ClientInboundMessageHandler.processOperation(ClientInboundMessageHandler.java:581)
> at
> org.apache.ignite.client.handler.ClientInboundMessageHandler.lambda$channelRead$2(ClientInboundMessageHandler.java:328)
> at
> org.gridgain.internal.security.context.SecuredRunnable.run(SecuredRunnable.java:34)
> at
> org.apache.ignite.client.handler.ClientInboundMessageHandler.channelRead(ClientInboundMessageHandler.java:328)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346)
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:318)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
> at
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:834) {code}
> The exception on client side:
> {code:java}
>
[jira] [Commented] (IGNITE-21567) Sql. Conversion from TIMESTAMP to TIMESTAMP_WITH_LOCAL_TIME_ZONE trims millis
[
https://issues.apache.org/jira/browse/IGNITE-21567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832792#comment-17832792
]
Pavel Pereslegin commented on IGNITE-21567:
---
[~zstan], [~amashenkov],
do a review of the proposed changes, please.
> Sql. Conversion from TIMESTAMP to TIMESTAMP_WITH_LOCAL_TIME_ZONE trims millis
> -
>
> Key: IGNITE-21567
> URL: https://issues.apache.org/jira/browse/IGNITE-21567
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Conversion from TIMESTAMP to TIMESTAMP_WITH_LOCAL_TIME_ZONE loses precision
> {code:java}
> String ts = "1992-01-18 02:30:00.123";
> assertQuery(format("select TIMESTAMP '{}'::TIMESTAMP WITH LOCAL TIME ZONE ",
> ts))
> .returns(LocalDateTime.parse(ts,
> DateTimeFormatter.ofPattern("-MM-dd HH:mm:ss.SSS"))
> .atZone(ZoneId.systemDefault())
> .toInstant())
> .check();
> // Expected: 1992-01-17T22:30:00.123Z
> // Actual: 1992-01-17T22:30:00Z
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21799) A transaction rollback fails with assertion error
[
https://issues.apache.org/jira/browse/IGNITE-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-21799:
--
Description:
A transaction rollback fails with
{noformat}
java.lang.AssertionError: Thread does not have allowed operations
{noformat}
Here is a simple reproducer below.
You can use an`ItCommonsApiTest` to reproduce.
{code:java}
@Test
public void rollbackAsync() {
Ignite node = CLUSTER.aliveNode();
sql("CREATE TABLE IF NOT EXISTS TEST(ID INT PRIMARY KEY, VAL0 INT)");
KeyValueView view1 =
node.tables().table("TEST").keyValueView();
AtomicReference> rollbackFut = new
AtomicReference<>();
Transaction tx = node.transactions().begin();
view1.getAsync(tx, Tuple.create().set("id", 101))
.handle((unused, err) -> {
rollbackFut.set(tx.rollbackAsync()); // unconditional roll
back
return null;
}).join();
rollbackFut.get().join(); // <- FAILS
}
}
{code}
was:
A transaction rollback fails with
{noformat}
java.lang.AssertionError: Thread does not have allowed operations
{noformat}
Here is a simple reproducer below.
You can use an`ItCommonTest` to reproduce.
{code:java}
@Test
public void rollbackAsync() {
Ignite node = CLUSTER.aliveNode();
sql("CREATE TABLE IF NOT EXISTS TEST(ID INT PRIMARY KEY, VAL0 INT)");
KeyValueView view1 =
node.tables().table("TEST").keyValueView();
AtomicReference> rollbackFut = new
AtomicReference<>();
Transaction tx = node.transactions().begin();
view1.getAsync(tx, makeKey(101))
.handle((unused, err) -> {
rollbackFut.set(tx.rollbackAsync()); // unconditional roll
back
return null;
}).join();
rollbackFut.get().join(); // <- FAILS
}
}
{code}
> A transaction rollback fails with assertion error
> -
>
> Key: IGNITE-21799
> URL: https://issues.apache.org/jira/browse/IGNITE-21799
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> A transaction rollback fails with
> {noformat}
> java.lang.AssertionError: Thread does not have allowed operations
> {noformat}
> Here is a simple reproducer below.
> You can use an`ItCommonsApiTest` to reproduce.
> {code:java}
> @Test
> public void rollbackAsync() {
> Ignite node = CLUSTER.aliveNode();
> sql("CREATE TABLE IF NOT EXISTS TEST(ID INT PRIMARY KEY, VAL0 INT)");
> KeyValueView view1 =
> node.tables().table("TEST").keyValueView();
> AtomicReference> rollbackFut = new
> AtomicReference<>();
>
> Transaction tx = node.transactions().begin();
> view1.getAsync(tx, Tuple.create().set("id", 101))
> .handle((unused, err) -> {
> rollbackFut.set(tx.rollbackAsync()); // unconditional
> roll back
> return null;
> }).join();
> rollbackFut.get().join(); // <- FAILS
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21894) Undescriptive error when restart cluster during open JDBC transaction
[
https://issues.apache.org/jira/browse/IGNITE-21894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-21894:
--
Description:
*Steps to reproduce:*
1. Start 2 nodes cluster.
2. Open JDBC connection, start transaction (using `.setAutoCommit(false)`).
3. Execute some insert queries. Do not commit the transaction.
4. Restart server node where connection was established.
5. Close JDBC statement and connection.
*Expected:*
Connection is closed with understandable error or without any error.
*Actual:*
Unclear exception on server side:
{code:java}
2024-04-01 00:55:28:399 +
[WARNING][ClusterFailoverMultiNodeTest_cluster_0-srv-worker-3][ClientInboundMessageHandler]
Error processing client request [connectionId=1, id=1, op=55,
remoteAddress=/127.0.0.1:59430]:Failed to find resource with id: 1
org.apache.ignite.internal.lang.IgniteInternalException: IGN-CMN-65535
TraceId:fe67e0da-5839-48c7-a59e-ca3465491698 Failed to find resource with id: 1
at
org.apache.ignite.client.handler.ClientResourceRegistry.get(ClientResourceRegistry.java:82)
at
org.apache.ignite.client.handler.JdbcQueryEventHandlerImpl.finishTxAsync(JdbcQueryEventHandlerImpl.java:390)
at
org.apache.ignite.client.handler.requests.jdbc.ClientJdbcFinishTxRequest.process(ClientJdbcFinishTxRequest.java:42)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.processOperation(ClientInboundMessageHandler.java:785)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.processOperation(ClientInboundMessageHandler.java:581)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.lambda$channelRead$2(ClientInboundMessageHandler.java:328)
at
org.gridgain.internal.security.context.SecuredRunnable.run(SecuredRunnable.java:34)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.channelRead(ClientInboundMessageHandler.java:328)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346)
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:318)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:834) {code}
The exception on client side:
{code:java}
java.sql.SQLException: The transaction rollback request failed.
at
org.apache.ignite.internal.jdbc.JdbcConnection.finishTx(JdbcConnection.java:425)
at
org.apache.ignite.internal.jdbc.JdbcConnection.close(JdbcConnection.java:441)
at
org.gridgain.ai3tests.tests.ThinClientRollbackTests.test(ThinClientRollbackTests.java:109)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.util.concurrent.ExecutionException:
[jira] [Updated] (IGNITE-21894) Undescriptive error when restart cluster during open JDBC transaction
[
https://issues.apache.org/jira/browse/IGNITE-21894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-21894:
--
Description:
*Steps to reproduce:*
1. Start 2 nodes cluster.
2. Open JDBC connection, start transaction (using `.setAutoCommit(false)`).
3. Execute some insert queries. Do not commit the transaction.
4. Restart server node where connection was established.
5. Close JDBC statement and connection.
*Expected:*
Connection is closed with understandable error or without any error.
*Actual:*
Unclear exception on server side while closing the connection:
{code:java}
2024-04-01 00:55:28:399 +
[WARNING][ClusterFailoverMultiNodeTest_cluster_0-srv-worker-3][ClientInboundMessageHandler]
Error processing client request [connectionId=1, id=1, op=55,
remoteAddress=/127.0.0.1:59430]:Failed to find resource with id: 1
org.apache.ignite.internal.lang.IgniteInternalException: IGN-CMN-65535
TraceId:fe67e0da-5839-48c7-a59e-ca3465491698 Failed to find resource with id: 1
at
org.apache.ignite.client.handler.ClientResourceRegistry.get(ClientResourceRegistry.java:82)
at
org.apache.ignite.client.handler.JdbcQueryEventHandlerImpl.finishTxAsync(JdbcQueryEventHandlerImpl.java:390)
at
org.apache.ignite.client.handler.requests.jdbc.ClientJdbcFinishTxRequest.process(ClientJdbcFinishTxRequest.java:42)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.processOperation(ClientInboundMessageHandler.java:785)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.processOperation(ClientInboundMessageHandler.java:581)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.lambda$channelRead$2(ClientInboundMessageHandler.java:328)
at
org.gridgain.internal.security.context.SecuredRunnable.run(SecuredRunnable.java:34)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.channelRead(ClientInboundMessageHandler.java:328)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346)
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:318)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:834) {code}
The exception on client side:
{code:java}
java.sql.SQLException: The transaction rollback request failed.
at
org.apache.ignite.internal.jdbc.JdbcConnection.finishTx(JdbcConnection.java:425)
at
org.apache.ignite.internal.jdbc.JdbcConnection.close(JdbcConnection.java:441)
at
org.gridgain.ai3tests.tests.ThinClientRollbackTests.test(ThinClientRollbackTests.java:109)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by:
[jira] [Commented] (IGNITE-21799) A transaction rollback fails with assertion error
[
https://issues.apache.org/jira/browse/IGNITE-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832788#comment-17832788
]
Andrey Mashenkov commented on IGNITE-21799:
---
Test fails with 100% rate on latest commit
a5c0973bf499f01352dc20438601e1ffca0d5b99
> A transaction rollback fails with assertion error
> -
>
> Key: IGNITE-21799
> URL: https://issues.apache.org/jira/browse/IGNITE-21799
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> A transaction rollback fails with
> {noformat}
> java.lang.AssertionError: Thread does not have allowed operations
> {noformat}
> Here is a simple reproducer below.
> You can use an`ItCommonTest` to reproduce.
> {code:java}
> @Test
> public void rollbackAsync() {
> Ignite node = CLUSTER.aliveNode();
> sql("CREATE TABLE IF NOT EXISTS TEST(ID INT PRIMARY KEY, VAL0 INT)");
> KeyValueView view1 =
> node.tables().table("TEST").keyValueView();
> AtomicReference> rollbackFut = new
> AtomicReference<>();
>
> Transaction tx = node.transactions().begin();
> view1.getAsync(tx, makeKey(101))
> .handle((unused, err) -> {
> rollbackFut.set(tx.rollbackAsync()); // unconditional
> roll back
> return null;
> }).join();
> rollbackFut.get().join(); // <- FAILS
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21894) Undescriptive error when restart cluster during open JDBC transaction
Igor created IGNITE-21894:
-
Summary: Undescriptive error when restart cluster during open JDBC
transaction
Key: IGNITE-21894
URL: https://issues.apache.org/jira/browse/IGNITE-21894
Project: Ignite
Issue Type: Bug
Components: jdbc, sql
Affects Versions: 3.0.0-beta1
Environment: 2 nodes cluster
Reporter: Igor
*Steps to reproduce:*
1. Start 2 nodes cluster.
2. Open JDBC connection, start transaction (using `.setAutoCommit(false)`).
3. Restart server node where connection was established.
4. Close JDBC statement and connection.
*Expected:*
Connection is closed with understandable error or without any error.
*Actual:*
Unclear exception on server side:
{code:java}
2024-04-01 00:55:28:399 +
[WARNING][ClusterFailoverMultiNodeTest_cluster_0-srv-worker-3][ClientInboundMessageHandler]
Error processing client request [connectionId=1, id=1, op=55,
remoteAddress=/127.0.0.1:59430]:Failed to find resource with id: 1
org.apache.ignite.internal.lang.IgniteInternalException: IGN-CMN-65535
TraceId:fe67e0da-5839-48c7-a59e-ca3465491698 Failed to find resource with id: 1
at
org.apache.ignite.client.handler.ClientResourceRegistry.get(ClientResourceRegistry.java:82)
at
org.apache.ignite.client.handler.JdbcQueryEventHandlerImpl.finishTxAsync(JdbcQueryEventHandlerImpl.java:390)
at
org.apache.ignite.client.handler.requests.jdbc.ClientJdbcFinishTxRequest.process(ClientJdbcFinishTxRequest.java:42)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.processOperation(ClientInboundMessageHandler.java:785)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.processOperation(ClientInboundMessageHandler.java:581)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.lambda$channelRead$2(ClientInboundMessageHandler.java:328)
at
org.gridgain.internal.security.context.SecuredRunnable.run(SecuredRunnable.java:34)
at
org.apache.ignite.client.handler.ClientInboundMessageHandler.channelRead(ClientInboundMessageHandler.java:328)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346)
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:318)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:834) {code}
The exception on client side:
{code:java}
java.sql.SQLException: The transaction rollback request failed.
at
org.apache.ignite.internal.jdbc.JdbcConnection.finishTx(JdbcConnection.java:425)
at
org.apache.ignite.internal.jdbc.JdbcConnection.close(JdbcConnection.java:441)
at
org.gridgain.ai3tests.tests.ThinClientRollbackTests.test(ThinClientRollbackTests.java:109)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
[jira] [Assigned] (IGNITE-21301) Sync raft log before flush in all storage engines
[ https://issues.apache.org/jira/browse/IGNITE-21301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Shergalis reassigned IGNITE-21301: -- Assignee: Philipp Shergalis > Sync raft log before flush in all storage engines > - > > Key: IGNITE-21301 > URL: https://issues.apache.org/jira/browse/IGNITE-21301 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Philipp Shergalis >Priority: Major > Labels: ignite-3 > > Checkpoints and RocsDB's flush actions should sync log before completing > writing data to disk, if "fsync" is disabled -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21799) A transaction rollback fails with assertion error
[
https://issues.apache.org/jira/browse/IGNITE-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832764#comment-17832764
]
Vladislav Pyatkov commented on IGNITE-21799:
This issue is not reproducible.
[~amashenkov] Probably, it is already fixed. Could you please take a look?
> A transaction rollback fails with assertion error
> -
>
> Key: IGNITE-21799
> URL: https://issues.apache.org/jira/browse/IGNITE-21799
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> A transaction rollback fails with
> {noformat}
> java.lang.AssertionError: Thread does not have allowed operations
> {noformat}
> Here is a simple reproducer below.
> You can use an`ItCommonTest` to reproduce.
> {code:java}
> @Test
> public void rollbackAsync() {
> Ignite node = CLUSTER.aliveNode();
> sql("CREATE TABLE IF NOT EXISTS TEST(ID INT PRIMARY KEY, VAL0 INT)");
> KeyValueView view1 =
> node.tables().table("TEST").keyValueView();
> AtomicReference> rollbackFut = new
> AtomicReference<>();
>
> Transaction tx = node.transactions().begin();
> view1.getAsync(tx, makeKey(101))
> .handle((unused, err) -> {
> rollbackFut.set(tx.rollbackAsync()); // unconditional
> roll back
> return null;
> }).join();
> rollbackFut.get().join(); // <- FAILS
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21893) ItConnectionManagerTest.testConnectMisconfiguredServer() is flaky
Roman Puchkovskiy created IGNITE-21893: -- Summary: ItConnectionManagerTest.testConnectMisconfiguredServer() is flaky Key: IGNITE-21893 URL: https://issues.apache.org/jira/browse/IGNITE-21893 Project: Ignite Issue Type: Bug Reporter: Roman Puchkovskiy -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21893) ItConnectionManagerTest.testConnectMisconfiguredServer() is flaky
[ https://issues.apache.org/jira/browse/IGNITE-21893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21893: --- Description: java.lang.AssertionError: Expected: is an instance of java.io.IOException but: is a org.apache.ignite.internal.network.handshake.HandshakeException java.lang.AssertionError: Expected: is an instance of java.io.IOException but: is a org.apache.ignite.internal.network.handshake.HandshakeException at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6) at org.apache.ignite.internal.network.netty.ItConnectionManagerTest.testConnectMisconfiguredServer(ItConnectionManagerTest.java:283) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.base/java.util.ArrayList.forEach(ArrayList.java:1541) at java.base/java.util.ArrayList.forEach(ArrayList.java:1541) > ItConnectionManagerTest.testConnectMisconfiguredServer() is flaky > - > > Key: IGNITE-21893 > URL: https://issues.apache.org/jira/browse/IGNITE-21893 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > > java.lang.AssertionError: Expected: is an instance of java.io.IOException > but: Channel has been closed before handshake has finished or handshake has > failed> is a org.apache.ignite.internal.network.handshake.HandshakeException > java.lang.AssertionError: Expected: is an instance of java.io.IOException > but: Channel has been closed before handshake has finished or handshake has > failed> is a org.apache.ignite.internal.network.handshake.HandshakeException > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) at > org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6) at > org.apache.ignite.internal.network.netty.ItConnectionManagerTest.testConnectMisconfiguredServer(ItConnectionManagerTest.java:283) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) at > java.base/java.util.ArrayList.forEach(ArrayList.java:1541) at > java.base/java.util.ArrayList.forEach(ArrayList.java:1541) -- This message was sent by Atlassian Jira (v8.20.10#820010)
