[jira] [Created] (IGNITE-20421) Add security subject ID in GridRestResponse
Mikhail Petrov created IGNITE-20421: --- Summary: Add security subject ID in GridRestResponse Key: IGNITE-20421 URL: https://issues.apache.org/jira/browse/IGNITE-20421 Project: Ignite Issue Type: Task Reporter: Mikhail Petrov Let's add security subject ID in GridRestResponse just like we do it for Ignite Events. It will help those who intercept REST response to determine the ID of the REST command initiator. Let's add the security subject ID to the GridRestResponse the same way we do for Ignite Events. This will help those intercepting the REST response to determine the ID of the REST command initiator. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20341) SQL Calcite. Bump calcite version to 1.34
[
https://issues.apache.org/jira/browse/IGNITE-20341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765322#comment-17765322
]
Ignite TC Bot commented on IGNITE-20341:
{panel:title=Branch: [pull/10919/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10919/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7329227buildTypeId=IgniteTests24Java8_RunAll]
> SQL Calcite. Bump calcite version to 1.34
> -
>
> Key: IGNITE-20341
> URL: https://issues.apache.org/jira/browse/IGNITE-20341
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.15
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: calcite, calcite2-required, ise
> Fix For: 2.16
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20401) Minor refactoring of IgniteUtils
[
https://issues.apache.org/jira/browse/IGNITE-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-20401:
-
Description: When working on IGNITE-20344, I've introduced a new utility
method in {{IgniteUtils}} but decided not to use it in existing code in order
to reduce the PR size. This is a ticket that has been created to do that. While
we are at it, we can fix some minor issues as well: IntelliJ warnings, TODOs,
etc.
> Minor refactoring of IgniteUtils
>
>
> Key: IGNITE-20401
> URL: https://issues.apache.org/jira/browse/IGNITE-20401
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Trivial
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When working on IGNITE-20344, I've introduced a new utility method in
> {{IgniteUtils}} but decided not to use it in existing code in order to reduce
> the PR size. This is a ticket that has been created to do that. While we are
> at it, we can fix some minor issues as well: IntelliJ warnings, TODOs, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20413) Update ignite dependency: zstd
[
https://issues.apache.org/jira/browse/IGNITE-20413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765298#comment-17765298
]
Ignite TC Bot commented on IGNITE-20413:
{panel:title=Branch: [pull/10932/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10932/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7336807buildTypeId=IgniteTests24Java8_RunAll]
> Update ignite dependency: zstd
> --
>
> Key: IGNITE-20413
> URL: https://issues.apache.org/jira/browse/IGNITE-20413
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr Nikolaev
>Assignee: Aleksandr Nikolaev
>Priority: Minor
> Labels: ise
> Fix For: 2.16
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Update Ignite dependency: zstd 1.5.2-5 to 1.5.5-5
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20420) Streamer metrics missing in ClientMetricSource.Holder.metrics
[ https://issues.apache.org/jira/browse/IGNITE-20420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20420: Ignite Flags: (was: Docs Required,Release Notes Required) > Streamer metrics missing in ClientMetricSource.Holder.metrics > - > > Key: IGNITE-20420 > URL: https://issues.apache.org/jira/browse/IGNITE-20420 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > ClientMetricSource.Holder.metrics does not have streamer metrics > (streamerBatchesSent etc). > Add a test to check that all metrics are registered (via reflection). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20420) Streamer metrics missing in ClientMetricSource.Holder.metrics
Pavel Tupitsyn created IGNITE-20420: --- Summary: Streamer metrics missing in ClientMetricSource.Holder.metrics Key: IGNITE-20420 URL: https://issues.apache.org/jira/browse/IGNITE-20420 Project: Ignite Issue Type: Bug Components: thin client Affects Versions: 3.0.0-beta1 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-beta2 ClientMetricSource.Holder.metrics does not have streamer metrics (streamerBatchesSent etc). Add a test to check that all metrics are registered (via reflection). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20419) Raft "snapshots" are broken in aipersist
Ivan Bessonov created IGNITE-20419:
--
Summary: Raft "snapshots" are broken in aipersist
Key: IGNITE-20419
URL: https://issues.apache.org/jira/browse/IGNITE-20419
Project: Ignite
Issue Type: Bug
Reporter: Ivan Bessonov
This code:
{code:java}
storage.runConsistently(locker -> {
storage.lastApplied(maxLastAppliedIndex, maxLastAppliedTerm);
return null;
}); {code}
Here we don't touch any pages. As a result, updated index value may not be
persisted to the storage in the next checkpoint. This causes eventual exception
on restart:
{noformat}
java.lang.IllegalArgumentException: Try to truncate logs before 336, but the
firstLogIndex is 370
at
org.apache.ignite.raft.jraft.util.Requires.requireTrue(Requires.java:92)
~[main/:?]
at
org.apache.ignite.raft.jraft.storage.impl.LogManagerImpl.truncatePrefix(LogManagerImpl.java:997)
~[main/:?]
at
org.apache.ignite.raft.jraft.storage.impl.LogManagerImpl.setSnapshot(LogManagerImpl.java:654)
~[main/:?]
...{noformat}
In checkpointer, we must check for changed meta as well.
Everything here can be tested with unit tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20344) Create tests for rebalance recovery
[ https://issues.apache.org/jira/browse/IGNITE-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765188#comment-17765188 ] Kirill Gusakov commented on IGNITE-20344: - LGTM > Create tests for rebalance recovery > --- > > Key: IGNITE-20344 > URL: https://issues.apache.org/jira/browse/IGNITE-20344 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > When implementing IGNITE-20187, I've encountered multiple problems with > writing an integration test for it. Since it required multiple node restarts, > it interfered with the rebalance algorithm a lot and the test was hanging for > various reasons. This must be investigated and fixed/overcome and a proper > test must be implemented. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20418) Command 'indexes_force_rebuild' should work with several certain nodes.
Vladimir Steshin created IGNITE-20418: - Summary: Command 'indexes_force_rebuild' should work with several certain nodes. Key: IGNITE-20418 URL: https://issues.apache.org/jira/browse/IGNITE-20418 Project: Ignite Issue Type: Task Reporter: Vladimir Steshin Assignee: Vladimir Steshin Currently, control.sh's command 'indexes_force_rebuild' has no ablity to lauch index rebuild on several certain nodes. Only one node is accepted as command parameter (--node-id). It would be handy to pass several nodes to execute on like '--nodes'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20418) Command 'indexes_force_rebuild' should work with several certain nodes.
[ https://issues.apache.org/jira/browse/IGNITE-20418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-20418: -- Labels: ise (was: ) > Command 'indexes_force_rebuild' should work with several certain nodes. > --- > > Key: IGNITE-20418 > URL: https://issues.apache.org/jira/browse/IGNITE-20418 > Project: Ignite > Issue Type: Task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Labels: ise > > Currently, control.sh's command 'indexes_force_rebuild' has no ablity to > lauch index rebuild on several certain nodes. Only one node is accepted as > command parameter (--node-id). It would be handy to pass several nodes to > execute on like '--nodes'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20286) Information about REST port disappeared from logs
[
https://issues.apache.org/jira/browse/IGNITE-20286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765158#comment-17765158
]
Vyacheslav Koptilin commented on IGNITE-20286:
--
The patch only fixes an issue with tests that could lead to missed logs in some
components just because slf4j provider was not included as a dependency.
> Information about REST port disappeared from logs
> -
>
> Key: IGNITE-20286
> URL: https://issues.apache.org/jira/browse/IGNITE-20286
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-beta2
>Reporter: Igor
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Attachments: image-2023-08-25-16-20-23-118.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The information about taken REST port is disappeared from logs.
> Previously the string was present:
> {code:java}
> 2023-08-24 05:01:08:983 +0300 [INFO][main][Micronaut] Startup completed in
> 118ms. Server Running: http://5e85d1e4d3d1:10301{code}
> Now it is impossible to determine the taken port by node (because REST
> endpoint support `portRange`).
> The possible reason of the problem: IgniteRunner doesn't have SL4J
> implementations in dependencies.
> !image-2023-08-25-16-20-23-118.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20286) Information about REST port disappeared from logs
[
https://issues.apache.org/jira/browse/IGNITE-20286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765157#comment-17765157
]
Vyacheslav Koptilin commented on IGNITE-20286:
--
Well, Ignite does not provide any logging framework by default itself. It is
the users's responsibility to add it (log4j2, logback, jul, etc.) to the
classpath.
However, some 3rd party dependencies of Ignite rely on slf4j (simple logging
facade), and it is required to provide a link to a logging framework as well.
JUL:
- SLF4J JDK14 Provider should be added to the classpath -
org.slf4j:slf4j-jdk14:2.0.x
- configuration file can be specified via `java.util.logging.config.file`
property
additional details can be found here:
https://docs.oracle.com/en/java/javase/11/core/java-logging-overview.html#GUID-B83B652C-17EA-48D9-93D2-563AE1FF8EDA
LOG4J2:
- SLF4J Provider should be added to the classpath -
org.apache.logging.log4j:log4j-slf4j2-impl:2.x.x (2.20.0 or higher, for example)
- LOG4J2 API and implementation: org.apache.logging.log4j:log4j-api:2.x.x,
org.apache.logging.log4j:log4j-core:2.x.x
- LOG4J2 bridge: org.apache.logging.log4j:log4j-jpl:2.x.x
- configuration can be done via the properties file. additional details can be
found here https://logging.apache.org/log4j/2.x/manual/configuration.html
> Information about REST port disappeared from logs
> -
>
> Key: IGNITE-20286
> URL: https://issues.apache.org/jira/browse/IGNITE-20286
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-beta2
>Reporter: Igor
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
> Attachments: image-2023-08-25-16-20-23-118.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The information about taken REST port is disappeared from logs.
> Previously the string was present:
> {code:java}
> 2023-08-24 05:01:08:983 +0300 [INFO][main][Micronaut] Startup completed in
> 118ms. Server Running: http://5e85d1e4d3d1:10301{code}
> Now it is impossible to determine the taken port by node (because REST
> endpoint support `portRange`).
> The possible reason of the problem: IgniteRunner doesn't have SL4J
> implementations in dependencies.
> !image-2023-08-25-16-20-23-118.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20417) Get rid of unused code in the index module
Kirill Tkalenko created IGNITE-20417: Summary: Get rid of unused code in the index module Key: IGNITE-20417 URL: https://issues.apache.org/jira/browse/IGNITE-20417 Project: Ignite Issue Type: Improvement Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko Fix For: 3.0.0-beta2 Unused code was found in the index module and we need to get rid of it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20416) IncompatibleSchemaException thrown when schema change is compatible
[
https://issues.apache.org/jira/browse/IGNITE-20416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-20416:
---
Assignee: Roman Puchkovskiy
> IncompatibleSchemaException thrown when schema change is compatible
> ---
>
> Key: IGNITE-20416
> URL: https://issues.apache.org/jira/browse/IGNITE-20416
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Roman Puchkovskiy
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> The following code performs compatible schema change (add column with a
> default value), but causes *IncompatibleSchemaException* (add to
> *ItSqlSynchronousApiTest* and run):
> {code:java}
> @Test
> public void schemaMigration() {
> IgniteSql sql = igniteSql();
> Session ses = sql.createSession();
> checkDdl(true, ses, "CREATE TABLE TEST(ID INT PRIMARY KEY, VAL0
> INT)");
> var view = CLUSTER_NODES.get(0).tables().table("TEST").recordView();
> var upsertFut = CompletableFuture.runAsync(() -> {
> for (int i = 0; i < 1000; i++) {
> view.upsert(null, Tuple.create().set("ID", i).set("VAL0", i));
> }
> });
> checkDdl(true, ses, "ALTER TABLE TEST ADD COLUMN VAL1 INT DEFAULT
> -1");
> upsertFut.join();
> }
> {code}
> If we perform schema update before, after, or between upserts, then there is
> no error. Only when thy happen concurrently.
> *Result:*
> {code}
> java.util.concurrent.CompletionException:
> org.apache.ignite.internal.table.distributed.replicator.IncompatibleSchemaException:
> IGN-TX-12 TraceId:52bbae8c-4706-4394-8bd3-30bac5747da5 Table schema was
> updated after the transaction was started [table=1, startSchema=1,
> operationSchema=2]
> at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:683)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
> ~[?:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateAtTimestampAndBuildUpdateCommand(PartitionReplicaListener.java:2643)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateAtTimestampAndBuildUpdateCommand(PartitionReplicaListener.java:2586)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processSingleEntryAction$109(PartitionReplicaListener.java:2058)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
> ~[?:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processSingleEntryAction$112(PartitionReplicaListener.java:2058)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.continueResolvingByPk(PartitionReplicaListener.java:1448)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$resolveRowByPk$68(PartitionReplicaListener.java:1428)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
> ~[?:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.resolveRowByPk(PartitionReplicaListener.java:1419)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processSingleEntryAction(PartitionReplicaListener.java:2048)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processRequest$2(PartitionReplicaListener.java:363)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.appendTxCommand(PartitionReplicaListener.java:1494)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
>
[jira] [Assigned] (IGNITE-20415) Internal IncompatibleSchemaException is thrown from public API
[
https://issues.apache.org/jira/browse/IGNITE-20415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-20415:
---
Assignee: Roman Puchkovskiy
> Internal IncompatibleSchemaException is thrown from public API
> --
>
> Key: IGNITE-20415
> URL: https://issues.apache.org/jira/browse/IGNITE-20415
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Roman Puchkovskiy
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> The following code throws internal exception from public API (add to
> *ItSqlSynchronousApiTest* and run):
> {code:java}
> @Test
> public void schemaMigration() {
> IgniteSql sql = igniteSql();
> Session ses = sql.createSession();
> checkDdl(true, ses, "CREATE TABLE TEST(ID INT PRIMARY KEY, VAL0
> INT)");
> var view = CLUSTER_NODES.get(0).tables().table("TEST").recordView();
> var upsertFut = CompletableFuture.runAsync(() -> {
> for (int i = 0; i < 1000; i++) {
> view.upsert(null, Tuple.create().set("ID", i).set("VAL0", i));
> }
> });
> checkDdl(true, ses, "ALTER TABLE TEST ADD COLUMN VAL1 INT DEFAULT
> -1");
> upsertFut.join();
> }
> {code}
> *Result:*
> {code}
> java.util.concurrent.CompletionException:
> org.apache.ignite.internal.table.distributed.replicator.IncompatibleSchemaException:
> IGN-TX-12 TraceId:52bbae8c-4706-4394-8bd3-30bac5747da5 Table schema was
> updated after the transaction was started [table=1, startSchema=1,
> operationSchema=2]
> at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:683)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
> ~[?:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateAtTimestampAndBuildUpdateCommand(PartitionReplicaListener.java:2643)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateAtTimestampAndBuildUpdateCommand(PartitionReplicaListener.java:2586)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processSingleEntryAction$109(PartitionReplicaListener.java:2058)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
> ~[?:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processSingleEntryAction$112(PartitionReplicaListener.java:2058)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.continueResolvingByPk(PartitionReplicaListener.java:1448)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$resolveRowByPk$68(PartitionReplicaListener.java:1428)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
> ~[?:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.resolveRowByPk(PartitionReplicaListener.java:1419)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processSingleEntryAction(PartitionReplicaListener.java:2048)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processRequest$2(PartitionReplicaListener.java:363)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.appendTxCommand(PartitionReplicaListener.java:1494)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processRequest(PartitionReplicaListener.java:363)
> ~[ignite-table-3.0.0-SNAPSHOT.jar:?]
> at
>
[jira] [Updated] (IGNITE-20416) IncompatibleSchemaException thrown when schema change is compatible
[
https://issues.apache.org/jira/browse/IGNITE-20416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-20416:
Description:
The following code performs compatible schema change (add column with a default
value), but causes *IncompatibleSchemaException* (add to
*ItSqlSynchronousApiTest* and run):
{code:java}
@Test
public void schemaMigration() {
IgniteSql sql = igniteSql();
Session ses = sql.createSession();
checkDdl(true, ses, "CREATE TABLE TEST(ID INT PRIMARY KEY, VAL0 INT)");
var view = CLUSTER_NODES.get(0).tables().table("TEST").recordView();
var upsertFut = CompletableFuture.runAsync(() -> {
for (int i = 0; i < 1000; i++) {
view.upsert(null, Tuple.create().set("ID", i).set("VAL0", i));
}
});
checkDdl(true, ses, "ALTER TABLE TEST ADD COLUMN VAL1 INT DEFAULT -1");
upsertFut.join();
}
{code}
If we perform schema update before, after, or between upserts, then there is no
error. Only when thy happen concurrently.
*Result:*
{code}
java.util.concurrent.CompletionException:
org.apache.ignite.internal.table.distributed.replicator.IncompatibleSchemaException:
IGN-TX-12 TraceId:52bbae8c-4706-4394-8bd3-30bac5747da5 Table schema was
updated after the transaction was started [table=1, startSchema=1,
operationSchema=2]
at
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
~[?:?]
at
java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:683)
~[?:?]
at
java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
~[?:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateAtTimestampAndBuildUpdateCommand(PartitionReplicaListener.java:2643)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateAtTimestampAndBuildUpdateCommand(PartitionReplicaListener.java:2586)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processSingleEntryAction$109(PartitionReplicaListener.java:2058)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
~[?:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processSingleEntryAction$112(PartitionReplicaListener.java:2058)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.continueResolvingByPk(PartitionReplicaListener.java:1448)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$resolveRowByPk$68(PartitionReplicaListener.java:1428)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
~[?:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.resolveRowByPk(PartitionReplicaListener.java:1419)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processSingleEntryAction(PartitionReplicaListener.java:2048)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processRequest$2(PartitionReplicaListener.java:363)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.appendTxCommand(PartitionReplicaListener.java:1494)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processRequest(PartitionReplicaListener.java:363)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$invoke$0(PartitionReplicaListener.java:347)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
~[?:?]
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
~[?:?]
at
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
~[?:?]
at
[jira] [Updated] (IGNITE-20416) IncompatibleSchemaException thrown when schema change is compatible
[
https://issues.apache.org/jira/browse/IGNITE-20416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-20416:
Description:
The following code performs compatible schema change (add column with a default
value), but causes *IncompatibleSchemaException* (add to
*ItSqlSynchronousApiTest* and run):
{code:java}
@Test
public void schemaMigration() {
IgniteSql sql = igniteSql();
Session ses = sql.createSession();
checkDdl(true, ses, "CREATE TABLE TEST(ID INT PRIMARY KEY, VAL0 INT)");
var view = CLUSTER_NODES.get(0).tables().table("TEST").recordView();
var upsertFut = CompletableFuture.runAsync(() -> {
for (int i = 0; i < 1000; i++) {
view.upsert(null, Tuple.create().set("ID", i).set("VAL0", i));
}
});
checkDdl(true, ses, "ALTER TABLE TEST ADD COLUMN VAL1 INT DEFAULT -1");
upsertFut.join();
}
{code}
*Result:*
{code}
java.util.concurrent.CompletionException:
org.apache.ignite.internal.table.distributed.replicator.IncompatibleSchemaException:
IGN-TX-12 TraceId:52bbae8c-4706-4394-8bd3-30bac5747da5 Table schema was
updated after the transaction was started [table=1, startSchema=1,
operationSchema=2]
at
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
~[?:?]
at
java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:683)
~[?:?]
at
java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
~[?:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateAtTimestampAndBuildUpdateCommand(PartitionReplicaListener.java:2643)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateAtTimestampAndBuildUpdateCommand(PartitionReplicaListener.java:2586)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processSingleEntryAction$109(PartitionReplicaListener.java:2058)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
~[?:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processSingleEntryAction$112(PartitionReplicaListener.java:2058)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.continueResolvingByPk(PartitionReplicaListener.java:1448)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$resolveRowByPk$68(PartitionReplicaListener.java:1428)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
~[?:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.resolveRowByPk(PartitionReplicaListener.java:1419)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processSingleEntryAction(PartitionReplicaListener.java:2048)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processRequest$2(PartitionReplicaListener.java:363)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.appendTxCommand(PartitionReplicaListener.java:1494)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processRequest(PartitionReplicaListener.java:363)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$invoke$0(PartitionReplicaListener.java:347)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
~[?:?]
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
~[?:?]
at
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
~[?:?]
at
org.apache.ignite.internal.util.PendingComparableValuesTracker.lambda$completeWaitersOnUpdate$0(PendingComparableValuesTracker.java:169)
~[ignite-core-3.0.0-SNAPSHOT.jar:?]
at
[jira] [Created] (IGNITE-20416) IncompatibleSchemaException thrown when schema change is compatible
Pavel Tupitsyn created IGNITE-20416: --- Summary: IncompatibleSchemaException thrown when schema change is compatible Key: IGNITE-20416 URL: https://issues.apache.org/jira/browse/IGNITE-20416 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 3.0.0-beta1 Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20416) IncompatibleSchemaException thrown when schema change is compatible
[ https://issues.apache.org/jira/browse/IGNITE-20416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20416: Ignite Flags: (was: Release Notes Required) > IncompatibleSchemaException thrown when schema change is compatible > --- > > Key: IGNITE-20416 > URL: https://issues.apache.org/jira/browse/IGNITE-20416 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20416) IncompatibleSchemaException thrown when schema change is compatible
[ https://issues.apache.org/jira/browse/IGNITE-20416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20416: Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > IncompatibleSchemaException thrown when schema change is compatible > --- > > Key: IGNITE-20416 > URL: https://issues.apache.org/jira/browse/IGNITE-20416 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20415) Internal IncompatibleSchemaException is thrown from public API
[
https://issues.apache.org/jira/browse/IGNITE-20415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-20415:
Description:
The following code throws internal exception from public API (add to
*ItSqlSynchronousApiTest* and run):
{code:java}
@Test
public void schemaMigration() {
IgniteSql sql = igniteSql();
Session ses = sql.createSession();
checkDdl(true, ses, "CREATE TABLE TEST(ID INT PRIMARY KEY, VAL0 INT)");
var view = CLUSTER_NODES.get(0).tables().table("TEST").recordView();
var upsertFut = CompletableFuture.runAsync(() -> {
for (int i = 0; i < 1000; i++) {
view.upsert(null, Tuple.create().set("ID", i).set("VAL0", i));
}
});
checkDdl(true, ses, "ALTER TABLE TEST ADD COLUMN VAL1 INT DEFAULT -1");
upsertFut.join();
}
{code}
*Result:*
{code}
java.util.concurrent.CompletionException:
org.apache.ignite.internal.table.distributed.replicator.IncompatibleSchemaException:
IGN-TX-12 TraceId:52bbae8c-4706-4394-8bd3-30bac5747da5 Table schema was
updated after the transaction was started [table=1, startSchema=1,
operationSchema=2]
at
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
~[?:?]
at
java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:683)
~[?:?]
at
java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
~[?:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateAtTimestampAndBuildUpdateCommand(PartitionReplicaListener.java:2643)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateAtTimestampAndBuildUpdateCommand(PartitionReplicaListener.java:2586)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processSingleEntryAction$109(PartitionReplicaListener.java:2058)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
~[?:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processSingleEntryAction$112(PartitionReplicaListener.java:2058)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.continueResolvingByPk(PartitionReplicaListener.java:1448)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$resolveRowByPk$68(PartitionReplicaListener.java:1428)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
~[?:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.resolveRowByPk(PartitionReplicaListener.java:1419)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processSingleEntryAction(PartitionReplicaListener.java:2048)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processRequest$2(PartitionReplicaListener.java:363)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.appendTxCommand(PartitionReplicaListener.java:1494)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processRequest(PartitionReplicaListener.java:363)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$invoke$0(PartitionReplicaListener.java:347)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
~[?:?]
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
~[?:?]
at
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
~[?:?]
at
org.apache.ignite.internal.util.PendingComparableValuesTracker.lambda$completeWaitersOnUpdate$0(PendingComparableValuesTracker.java:169)
~[ignite-core-3.0.0-SNAPSHOT.jar:?]
at java.util.concurrent.ConcurrentMap.forEach(ConcurrentMap.java:122)
~[?:?]
at
[jira] [Updated] (IGNITE-20415) Internal IncompatibleSchemaException is thrown from public API
[
https://issues.apache.org/jira/browse/IGNITE-20415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-20415:
Description:
The following code throws internal exception from public API (add to
*ItSqlSynchronousApiTest* and run):
{java}
@Test
public void schemaMigration() {
IgniteSql sql = igniteSql();
Session ses = sql.createSession();
checkDdl(true, ses, "CREATE TABLE TEST(ID INT PRIMARY KEY, VAL0 INT)");
var view = CLUSTER_NODES.get(0).tables().table("TEST").recordView();
var upsertFut = CompletableFuture.runAsync(() -> {
for (int i = 0; i < 1000; i++) {
view.upsert(null, Tuple.create().set("ID", i).set("VAL0", i));
}
});
checkDdl(true, ses, "ALTER TABLE TEST ADD COLUMN VAL1 INT DEFAULT -1");
upsertFut.join();
}
{java}
*Result:*
{code}
java.util.concurrent.CompletionException:
org.apache.ignite.internal.table.distributed.replicator.IncompatibleSchemaException:
IGN-TX-12 TraceId:52bbae8c-4706-4394-8bd3-30bac5747da5 Table schema was
updated after the transaction was started [table=1, startSchema=1,
operationSchema=2]
at
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
~[?:?]
at
java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:683)
~[?:?]
at
java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
~[?:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateAtTimestampAndBuildUpdateCommand(PartitionReplicaListener.java:2643)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateAtTimestampAndBuildUpdateCommand(PartitionReplicaListener.java:2586)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processSingleEntryAction$109(PartitionReplicaListener.java:2058)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
~[?:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processSingleEntryAction$112(PartitionReplicaListener.java:2058)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.continueResolvingByPk(PartitionReplicaListener.java:1448)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$resolveRowByPk$68(PartitionReplicaListener.java:1428)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
~[?:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.resolveRowByPk(PartitionReplicaListener.java:1419)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processSingleEntryAction(PartitionReplicaListener.java:2048)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processRequest$2(PartitionReplicaListener.java:363)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.appendTxCommand(PartitionReplicaListener.java:1494)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processRequest(PartitionReplicaListener.java:363)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$invoke$0(PartitionReplicaListener.java:347)
~[ignite-table-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
~[?:?]
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
~[?:?]
at
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
~[?:?]
at
org.apache.ignite.internal.util.PendingComparableValuesTracker.lambda$completeWaitersOnUpdate$0(PendingComparableValuesTracker.java:169)
~[ignite-core-3.0.0-SNAPSHOT.jar:?]
at java.util.concurrent.ConcurrentMap.forEach(ConcurrentMap.java:122)
~[?:?]
at
[jira] [Updated] (IGNITE-20415) Internal IncompatibleSchemaException is thrown from public API
[ https://issues.apache.org/jira/browse/IGNITE-20415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20415: Ignite Flags: (was: Docs Required,Release Notes Required) > Internal IncompatibleSchemaException is thrown from public API > -- > > Key: IGNITE-20415 > URL: https://issues.apache.org/jira/browse/IGNITE-20415 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20415) Internal IncompatibleSchemaException is thrown from public API
Pavel Tupitsyn created IGNITE-20415: --- Summary: Internal IncompatibleSchemaException is thrown from public API Key: IGNITE-20415 URL: https://issues.apache.org/jira/browse/IGNITE-20415 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 3.0.0-beta1 Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19680) Get rid of org.apache.ignite.internal.index.event.IndexEventParameters
[ https://issues.apache.org/jira/browse/IGNITE-19680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-19680: - Description: In the process of migrating to the catalog, we need to get rid of *org.apache.ignite.internal.index.event.IndexEventParameters* (and related classes) and use a different entity when working with indexes for sql. h2. Update The index creation/destroy event can be useful when building indexes. was:In the process of migrating to the catalog, we need to get rid of *org.apache.ignite.internal.index.event.IndexEventParameters* (and related classes) and use a different entity when working with indexes for sql. > Get rid of org.apache.ignite.internal.index.event.IndexEventParameters > -- > > Key: IGNITE-19680 > URL: https://issues.apache.org/jira/browse/IGNITE-19680 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > In the process of migrating to the catalog, we need to get rid of > *org.apache.ignite.internal.index.event.IndexEventParameters* (and related > classes) and use a different entity when working with indexes for sql. > h2. Update > The index creation/destroy event can be useful when building indexes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20000) Sql. Add planner test to verify numeric type coercion in binary arithmetic
[ https://issues.apache.org/jira/browse/IGNITE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765088#comment-17765088 ] Yury Gerzhedovich commented on IGNITE-2: [~korlov][~zstan] could you please review the patch? > Sql. Add planner test to verify numeric type coercion in binary arithmetic > --- > > Key: IGNITE-2 > URL: https://issues.apache.org/jira/browse/IGNITE-2 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Assignee: Yury Gerzhedovich >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Let's add new tests to validate numeric type coercion in binary arithmetic. > The tests should be as easy as possible, every test case must answer a > question "what are expected types of each operand when we do arithmetic with > a given numeric type pair?" > Look to NumericComparisonTypeCoercionTest as example. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20394) ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication sometims fails with TimeoutException
[
https://issues.apache.org/jira/browse/IGNITE-20394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765078#comment-17765078
]
Denis Chudov commented on IGNITE-20394:
---
[~alapin] LGTM.
> ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication
> sometims fails with TimeoutException
> -
>
> Key: IGNITE-20394
> URL: https://issues.apache.org/jira/browse/IGNITE-20394
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Blocker
> Labels: ignite-3
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code:java}
> org.apache.ignite.tx.TransactionException: IGN-REP-5
> TraceId:f6ad9df9-6b21-4464-9b70-7e9aeb8b Failed to get the primary
> replica [tablePartitionId=1_part_0, awaitTimestamp=HybridTimestamp
> [time=111047427797811201, physical=1694449276700, logical=1]] at
> app//org.apache.ignite.internal.util.ExceptionUtils.lambda$withCause$1(ExceptionUtils.java:400)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCauseInternal(ExceptionUtils.java:467)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCause(ExceptionUtils.java:400)
> at
> app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$enlist$44(InternalTableImpl.java:1398)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture$Timeout.run(CompletableFuture.java:2792)
> at
> java.base@11.0.17/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at
> java.base@11.0.17/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base@11.0.17/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base@11.0.17/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base@11.0.17/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base@11.0.17/java.lang.Thread.run(Thread.java:834)Caused by:
> java.util.concurrent.TimeoutException {code}
> h3. UPD #1
> The problem is that we forgot to add {{storageIndexTracker}} update on
> * table start
> * PartitionListener#onConfigurationCommitted
> * PartitionListener#onSnapshotSave
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20353) Calcite engine. Clause 'WITH affinity_key=...' silently ignored when wrong column is specified
[
https://issues.apache.org/jira/browse/IGNITE-20353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765069#comment-17765069
]
Ignite TC Bot commented on IGNITE-20353:
{panel:title=Branch: [pull/10925/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10925/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7332817]]
* {color:#013220}IgniteCalciteTestSuite:
TableDdlIntegrationTest.createTableWithAffinity - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7332893buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Clause 'WITH affinity_key=...' silently ignored when wrong
> column is specified
> --
>
> Key: IGNITE-20353
> URL: https://issues.apache.org/jira/browse/IGNITE-20353
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite, ise
>
> Calcite-based SQL engine silently ignore clause WITH affinity_key=... when
> wrong column is specified. H2-based engine in this case throw an error:
> {noformat}
> org.apache.ignite.internal.processors.query.IgniteSQLException: Affinity key
> column with given name not found: test
> {noformat}
> Reproducer:
> {code:sql}
> CREATE TABLE order_items (id varchar, orderId int, sku varchar, PRIMARY KEY
> (id, orderId) WITH "affinity_key=test");
> {code}
> Also, there is some problem with case-sensitivity, for example:
> {code:sql}
> CREATE TABLE order_items (id varchar, orderId int, sku varchar, PRIMARY KEY
> (id, orderId) WITH "affinity_key=orderId");
> {code}
> Works well for H2-based engine ({{orderId}} in {{affinity_key}} converted to
> {{ORDERID}} and matches {{orderId}} columns alias), but silently ignired for
> Calcite-based engine ({{orderId}} in {{affinity_key}} remains without case
> change). But:
> {code:sql}
> CREATE TABLE order_items (id varchar, orderId int, sku varchar, PRIMARY KEY
> (id, orderId) WITH "affinity_key=ORDERID");
> {code}
> Works well for both engines.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20394) ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication sometims fails with TimeoutException
[
https://issues.apache.org/jira/browse/IGNITE-20394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-20394:
-
Reviewer: Denis Chudov
> ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication
> sometims fails with TimeoutException
> -
>
> Key: IGNITE-20394
> URL: https://issues.apache.org/jira/browse/IGNITE-20394
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Blocker
> Labels: ignite-3
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code:java}
> org.apache.ignite.tx.TransactionException: IGN-REP-5
> TraceId:f6ad9df9-6b21-4464-9b70-7e9aeb8b Failed to get the primary
> replica [tablePartitionId=1_part_0, awaitTimestamp=HybridTimestamp
> [time=111047427797811201, physical=1694449276700, logical=1]] at
> app//org.apache.ignite.internal.util.ExceptionUtils.lambda$withCause$1(ExceptionUtils.java:400)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCauseInternal(ExceptionUtils.java:467)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCause(ExceptionUtils.java:400)
> at
> app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$enlist$44(InternalTableImpl.java:1398)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> java.base@11.0.17/java.util.concurrent.CompletableFuture$Timeout.run(CompletableFuture.java:2792)
> at
> java.base@11.0.17/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at
> java.base@11.0.17/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base@11.0.17/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base@11.0.17/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base@11.0.17/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base@11.0.17/java.lang.Thread.run(Thread.java:834)Caused by:
> java.util.concurrent.TimeoutException {code}
> h3. UPD #1
> The problem is that we forgot to add {{storageIndexTracker}} update on
> * table start
> * PartitionListener#onConfigurationCommitted
> * PartitionListener#onSnapshotSave
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20414) Rollover test logs on startup
Vadim Pakhnushev created IGNITE-20414: - Summary: Rollover test logs on startup Key: IGNITE-20414 URL: https://issues.apache.org/jira/browse/IGNITE-20414 Project: Ignite Issue Type: Improvement Reporter: Vadim Pakhnushev Assignee: Vadim Pakhnushev In the IGNITE-19148 rollover strategy is size-based, which can lead to confusion in case a log for a test run starts in the middle of the log file. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19981) Calcite engine. Optimize mapping sending with query start request
[ https://issues.apache.org/jira/browse/IGNITE-19981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-19981: --- Ignite Flags: (was: Release Notes Required) > Calcite engine. Optimize mapping sending with query start request > - > > Key: IGNITE-19981 > URL: https://issues.apache.org/jira/browse/IGNITE-19981 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: ise > Time Spent: 50m > Remaining Estimate: 0h > > Currently we send the whole fragment mapping with query start request to each > node, but on the node we need only local mapping (we need only set of > partition to process by current node). If there are a lot of nodes and a lot > of partitions - mapping can take a lot of space -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-19981) Calcite engine. Optimize mapping sending with query start request
[ https://issues.apache.org/jira/browse/IGNITE-19981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov resolved IGNITE-19981. Resolution: Won't Fix Looks like there is no performance boost after implementation. Benchmarks show reduced network usage, but increased CPU usage and lower overall throughput. > Calcite engine. Optimize mapping sending with query start request > - > > Key: IGNITE-19981 > URL: https://issues.apache.org/jira/browse/IGNITE-19981 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: ise > Time Spent: 50m > Remaining Estimate: 0h > > Currently we send the whole fragment mapping with query start request to each > node, but on the node we need only local mapping (we need only set of > partition to process by current node). If there are a lot of nodes and a lot > of partitions - mapping can take a lot of space -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20353) Calcite engine. Clause 'WITH affinity_key=...' silently ignored when wrong column is specified
[
https://issues.apache.org/jira/browse/IGNITE-20353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765058#comment-17765058
]
Ignite TC Bot commented on IGNITE-20353:
{panel:title=Branch: [pull/10925/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS 4{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7332849]]
* IgnitePdsTestSuite4:
IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse.testActivateInReadOnlySimple_5_Servers
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/10925/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7332817]]
* {color:#013220}IgniteCalciteTestSuite:
TableDdlIntegrationTest.createTableWithAffinity - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7332893buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Clause 'WITH affinity_key=...' silently ignored when wrong
> column is specified
> --
>
> Key: IGNITE-20353
> URL: https://issues.apache.org/jira/browse/IGNITE-20353
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite, ise
>
> Calcite-based SQL engine silently ignore clause WITH affinity_key=... when
> wrong column is specified. H2-based engine in this case throw an error:
> {noformat}
> org.apache.ignite.internal.processors.query.IgniteSQLException: Affinity key
> column with given name not found: test
> {noformat}
> Reproducer:
> {code:sql}
> CREATE TABLE order_items (id varchar, orderId int, sku varchar, PRIMARY KEY
> (id, orderId) WITH "affinity_key=test");
> {code}
> Also, there is some problem with case-sensitivity, for example:
> {code:sql}
> CREATE TABLE order_items (id varchar, orderId int, sku varchar, PRIMARY KEY
> (id, orderId) WITH "affinity_key=orderId");
> {code}
> Works well for H2-based engine ({{orderId}} in {{affinity_key}} converted to
> {{ORDERID}} and matches {{orderId}} columns alias), but silently ignired for
> Calcite-based engine ({{orderId}} in {{affinity_key}} remains without case
> change). But:
> {code:sql}
> CREATE TABLE order_items (id varchar, orderId int, sku varchar, PRIMARY KEY
> (id, orderId) WITH "affinity_key=ORDERID");
> {code}
> Works well for both engines.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-17363) Update Ignite dependency: Maven Surefire Common
[ https://issues.apache.org/jira/browse/IGNITE-17363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Nikolaev resolved IGNITE-17363. - Resolution: Duplicate > Update Ignite dependency: Maven Surefire Common > --- > > Key: IGNITE-17363 > URL: https://issues.apache.org/jira/browse/IGNITE-17363 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Nikolaev >Assignee: Aleksandr Nikolaev >Priority: Minor > Labels: ise > Time Spent: 10m > Remaining Estimate: 0h > > Update Ignite dependency: Maven Surefire Common 3.0.0-M4 to 3.0.0-M7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20410) ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication fails with ReplicationTimeoutException
[
https://issues.apache.org/jira/browse/IGNITE-20410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-20410:
-
Description:
ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication
fails with ReplicationTimeoutException because of Metadata unavailability on
replication node.
With some extra debug output I got following result:
{code:java}
applyUpdateCommand
applyCmdWithExceptionHandling messageType = 43, groupType = 9
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
...
...
...
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
applyCmdWithExceptionHandling RuntimeException
Replication is timed out [replicaGrpId=1_part_0]
org.apache.ignite.tx.TransactionException: IGN-REP-3
TraceId:b5ea497a-7985-414a-8b44-8a880704bf80 Replication is timed out
[replicaGrpId=1_part_0]
at
app//org.apache.ignite.internal.util.ExceptionUtils.lambda$withCause$0(ExceptionUtils.java:378)
at
app//org.apache.ignite.internal.util.ExceptionUtils.withCauseInternal(ExceptionUtils.java:461)
at
app//org.apache.ignite.internal.util.ExceptionUtils.withCause(ExceptionUtils.java:378)
at
app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.wrapReplicationException(InternalTableImpl.java:1630)
at
app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$postEnlist$9(InternalTableImpl.java:521)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:934)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:911)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
at
app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$enlistWithRetry$5(InternalTableImpl.java:495)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:934)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:911)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
at
app//org.apache.ignite.internal.replicator.ReplicaService.lambda$sendToReplica$3(ReplicaService.java:97)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:483)
at
java.base@18.0.2/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
at
java.base@18.0.2/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
at
java.base@18.0.2/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
at
java.base@18.0.2/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
at
java.base@18.0.2/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
Caused by:
org.apache.ignite.internal.replicator.exception.ReplicationTimeoutException:
IGN-REP-3 TraceId:b5ea497a-7985-414a-8b44-8a880704bf80 Replication is timed out
[replicaGrpId=1_part_0]
... 9 more {code}
The problem occurs when test invariant is broken,
[jira] [Updated] (IGNITE-20410) ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication fails with ReplicationTimeoutException
[
https://issues.apache.org/jira/browse/IGNITE-20410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-20410:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication
> fails with ReplicationTimeoutException
> ---
>
> Key: IGNITE-20410
> URL: https://issues.apache.org/jira/browse/IGNITE-20410
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexander Lapin
>Priority: Major
> Labels: ignite-3
>
> ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication
> fails with ReplicationTimeoutException because of Metadata unavailability on
> replication node.
> With some extra debug output I got following result:
> {code:java}
> applyUpdateCommand
> applyCmdWithExceptionHandling messageType = 43, groupType = 9
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> ...
> ...
> ...
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> applyCmdWithExceptionHandling RuntimeException
> Replication is timed out [replicaGrpId=1_part_0]
> org.apache.ignite.tx.TransactionException: IGN-REP-3
> TraceId:b5ea497a-7985-414a-8b44-8a880704bf80 Replication is timed out
> [replicaGrpId=1_part_0]
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.lambda$withCause$0(ExceptionUtils.java:378)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCauseInternal(ExceptionUtils.java:461)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCause(ExceptionUtils.java:378)
> at
> app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.wrapReplicationException(InternalTableImpl.java:1630)
> at
> app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$postEnlist$9(InternalTableImpl.java:521)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:934)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:911)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
> at
> app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$enlistWithRetry$5(InternalTableImpl.java:495)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:934)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:911)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
> at
> app//org.apache.ignite.internal.replicator.ReplicaService.lambda$sendToReplica$3(ReplicaService.java:97)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:483)
> at
> java.base@18.0.2/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
> at
>
[jira] [Updated] (IGNITE-20410) ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication fails with ReplicationTimeoutException
[
https://issues.apache.org/jira/browse/IGNITE-20410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-20410:
-
Labels: ignite-3 (was: )
> ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication
> fails with ReplicationTimeoutException
> ---
>
> Key: IGNITE-20410
> URL: https://issues.apache.org/jira/browse/IGNITE-20410
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexander Lapin
>Priority: Major
> Labels: ignite-3
>
> ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication
> fails with ReplicationTimeoutException because of Metadata unavailability on
> replication node.
> With some extra debug output I got following result:
> {code:java}
> applyUpdateCommand
> applyCmdWithExceptionHandling messageType = 43, groupType = 9
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> ...
> ...
> ...
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
> available, group '1_part_0', required level 3; rejecting ActionRequest with
> EBUSY., leaderId=null], err = null
> applyCmdWithExceptionHandling RuntimeException
> Replication is timed out [replicaGrpId=1_part_0]
> org.apache.ignite.tx.TransactionException: IGN-REP-3
> TraceId:b5ea497a-7985-414a-8b44-8a880704bf80 Replication is timed out
> [replicaGrpId=1_part_0]
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.lambda$withCause$0(ExceptionUtils.java:378)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCauseInternal(ExceptionUtils.java:461)
> at
> app//org.apache.ignite.internal.util.ExceptionUtils.withCause(ExceptionUtils.java:378)
> at
> app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.wrapReplicationException(InternalTableImpl.java:1630)
> at
> app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$postEnlist$9(InternalTableImpl.java:521)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:934)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:911)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
> at
> app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$enlistWithRetry$5(InternalTableImpl.java:495)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:934)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:911)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
> at
> app//org.apache.ignite.internal.replicator.ReplicaService.lambda$sendToReplica$3(ReplicaService.java:97)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
> at
> java.base@18.0.2/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:483)
> at
> java.base@18.0.2/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
> at
>
[jira] [Updated] (IGNITE-20410) ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication fails with ReplicationTimeoutException
[
https://issues.apache.org/jira/browse/IGNITE-20410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-20410:
-
Description:
ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication
fails with ReplicationTimeoutException because of Metadata unavailability on
replication node.
With some extra debug output I got following result:
{code:java}
applyUpdateCommand
applyCmdWithExceptionHandling messageType = 43, groupType = 9
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
...
...
...
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
applyCmdWithExceptionHandling RuntimeException
Replication is timed out [replicaGrpId=1_part_0]
org.apache.ignite.tx.TransactionException: IGN-REP-3
TraceId:b5ea497a-7985-414a-8b44-8a880704bf80 Replication is timed out
[replicaGrpId=1_part_0]
at
app//org.apache.ignite.internal.util.ExceptionUtils.lambda$withCause$0(ExceptionUtils.java:378)
at
app//org.apache.ignite.internal.util.ExceptionUtils.withCauseInternal(ExceptionUtils.java:461)
at
app//org.apache.ignite.internal.util.ExceptionUtils.withCause(ExceptionUtils.java:378)
at
app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.wrapReplicationException(InternalTableImpl.java:1630)
at
app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$postEnlist$9(InternalTableImpl.java:521)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:934)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:911)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
at
app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$enlistWithRetry$5(InternalTableImpl.java:495)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:934)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:911)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
at
app//org.apache.ignite.internal.replicator.ReplicaService.lambda$sendToReplica$3(ReplicaService.java:97)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:483)
at
java.base@18.0.2/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
at
java.base@18.0.2/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
at
java.base@18.0.2/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
at
java.base@18.0.2/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
at
java.base@18.0.2/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
Caused by:
org.apache.ignite.internal.replicator.exception.ReplicationTimeoutException:
IGN-REP-3 TraceId:b5ea497a-7985-414a-8b44-8a880704bf80 Replication is timed out
[replicaGrpId=1_part_0]
... 9 more {code}
The problem occurs when test invariant is broken,
[jira] [Updated] (IGNITE-20367) ItTableRaftSnapshotsTest times out with high flaky rate
[
https://issues.apache.org/jira/browse/IGNITE-20367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-20367:
-
Description:
{code:java}
org.apache.ignite.lang.IgniteException: IGN-CMN-65535
TraceId:f1535407-3cf9-48cd-9091-825ecf308526 at
java.base@11.0.17/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710)
at
app//org.apache.ignite.internal.util.ExceptionUtils$1.copy(ExceptionUtils.java:772)
at
app//org.apache.ignite.internal.util.ExceptionUtils$ExceptionFactory.createCopy(ExceptionUtils.java:706)
at
app//org.apache.ignite.internal.util.ExceptionUtils.copyExceptionWithCause(ExceptionUtils.java:543)
at
app//org.apache.ignite.internal.util.ExceptionUtils.copyExceptionWithCauseInternal(ExceptionUtils.java:641)
at
app//org.apache.ignite.internal.util.ExceptionUtils.copyExceptionWithCause(ExceptionUtils.java:494)
at
app//org.apache.ignite.internal.sql.AbstractSession.execute(AbstractSession.java:63)
at
app//org.apache.ignite.internal.SessionUtils.executeUpdate(SessionUtils.java:38)
at
app//org.apache.ignite.internal.SessionUtils.executeUpdate(SessionUtils.java:50)
at
app//org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest.lambda$executeDmlWithRetry$1(ItTableRaftSnapshotsTest.java:231)
at app//org.apache.ignite.internal.Cluster.doInSession(Cluster.java:448) at
app//org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest.lambda$executeDmlWithRetry$2(ItTableRaftSnapshotsTest.java:230)
at
app//org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest.withRetry(ItTableRaftSnapshotsTest.java:184)
at
app//org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest.executeDmlWithRetry(ItTableRaftSnapshotsTest.java:229)
at
app//org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest.prepareClusterForInstallingSnapshotToNode2(ItTableRaftSnapshotsTest.java:351)
at
app//org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest.snapshotInstallTimeoutDoesNotBreakSubsequentInstallsWhenSecondAttemptIsIdenticalToFirst(ItTableRaftSnapshotsTest.java:685)
at
java.base@11.0.17/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method) at
java.base@11.0.17/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base@11.0.17/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base@11.0.17/java.lang.reflect.Method.invoke(Method.java:566) at
app//org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
at
app//org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
at
app//org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
at
app//org.junit.jupiter.engine.extension.SameThreadTimeoutInvocation.proceed(SameThreadTimeoutInvocation.java:45)
at
app//org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
at
app//org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
at
app//org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
at
app//org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
at
app//org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
at
app//org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
at
app//org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
at
app//org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
at
app//org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
at
app//org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:92)
at
app//org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:86)
at
app//org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:217)
at
app//org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at
app//org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:213)
at
app//org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:138)
at
app//org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:68)
at
[jira] [Updated] (IGNITE-20367) ItTableRaftSnapshotsTest times out with high flaky rate
[
https://issues.apache.org/jira/browse/IGNITE-20367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-20367:
-
Description:
{code:java}
org.apache.ignite.lang.IgniteException: IGN-CMN-65535
TraceId:f1535407-3cf9-48cd-9091-825ecf308526 at
java.base@11.0.17/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710)
at
app//org.apache.ignite.internal.util.ExceptionUtils$1.copy(ExceptionUtils.java:772)
at
app//org.apache.ignite.internal.util.ExceptionUtils$ExceptionFactory.createCopy(ExceptionUtils.java:706)
at
app//org.apache.ignite.internal.util.ExceptionUtils.copyExceptionWithCause(ExceptionUtils.java:543)
at
app//org.apache.ignite.internal.util.ExceptionUtils.copyExceptionWithCauseInternal(ExceptionUtils.java:641)
at
app//org.apache.ignite.internal.util.ExceptionUtils.copyExceptionWithCause(ExceptionUtils.java:494)
at
app//org.apache.ignite.internal.sql.AbstractSession.execute(AbstractSession.java:63)
at
app//org.apache.ignite.internal.SessionUtils.executeUpdate(SessionUtils.java:38)
at
app//org.apache.ignite.internal.SessionUtils.executeUpdate(SessionUtils.java:50)
at
app//org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest.lambda$executeDmlWithRetry$1(ItTableRaftSnapshotsTest.java:231)
at app//org.apache.ignite.internal.Cluster.doInSession(Cluster.java:448) at
app//org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest.lambda$executeDmlWithRetry$2(ItTableRaftSnapshotsTest.java:230)
at
app//org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest.withRetry(ItTableRaftSnapshotsTest.java:184)
at
app//org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest.executeDmlWithRetry(ItTableRaftSnapshotsTest.java:229)
at
app//org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest.prepareClusterForInstallingSnapshotToNode2(ItTableRaftSnapshotsTest.java:351)
at
app//org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest.snapshotInstallTimeoutDoesNotBreakSubsequentInstallsWhenSecondAttemptIsIdenticalToFirst(ItTableRaftSnapshotsTest.java:685)
at
java.base@11.0.17/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method) at
java.base@11.0.17/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base@11.0.17/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base@11.0.17/java.lang.reflect.Method.invoke(Method.java:566) at
app//org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
at
app//org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
at
app//org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
at
app//org.junit.jupiter.engine.extension.SameThreadTimeoutInvocation.proceed(SameThreadTimeoutInvocation.java:45)
at
app//org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
at
app//org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
at
app//org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
at
app//org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
at
app//org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
at
app//org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
at
app//org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
at
app//org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
at
app//org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
at
app//org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:92)
at
app//org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:86)
at
app//org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:217)
at
app//org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at
app//org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:213)
at
app//org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:138)
at
app//org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:68)
at
[jira] [Updated] (IGNITE-20407) Update Ignite dependency Snappy
[ https://issues.apache.org/jira/browse/IGNITE-20407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Nikolaev updated IGNITE-20407: Docs Text: Update Ignite dependency: Snappy to 1.1.10.3 > Update Ignite dependency Snappy > --- > > Key: IGNITE-20407 > URL: https://issues.apache.org/jira/browse/IGNITE-20407 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Nikolaev >Assignee: Aleksandr Nikolaev >Priority: Major > Labels: ise > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > Update Ignite dependency: Snappy 1.1.8.4 to 1.1.10.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20034) Implement writeIntentResolution coordinator path
[ https://issues.apache.org/jira/browse/IGNITE-20034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov updated IGNITE-20034: -- Reviewer: Vladislav Pyatkov > Implement writeIntentResolution coordinator path > > > Key: IGNITE-20034 > URL: https://issues.apache.org/jira/browse/IGNITE-20034 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Denis Chudov >Priority: Major > Labels: ignite-3, transaction, transaction3_recovery > Time Spent: 10m > Remaining Estimate: 0h > > h3. Motivation > In order to implement proper handling of a commit partition primary replica > change it's required to: > # Support local txnStateMap, in order to > # Implement writeIntentResolution coordinator path, in order to > # Calculate commitTimestamp on txn coordtinator istead of commit partition, > where we do it now. > First item is covered in IGNITE-20033 Given ticket is about second item only. > Third one will be covered in a separate ticket. > h3. Definition of Done > From the "client" side, it's required to adjust current writeIntentResolution > logic by checking local txnStateLocal map. > * If there's no corresponding transaction in given map - fallback to the > commitPartition path. > * If the state is COMMITED or ABORTED - use given value as > writeInentResolution base. Actually, by doing this we will implelent > writeIntentResolution local path. > * If the state is FINISHING - wait for outcome and return response with the > result: commit or abort. One of the most nontrivial steps, because of > awaiting logic. > * If the state is PENDING, retrieve txCoordAddr and ask tx coordinator. > ** If tx coordinator is missing or returns null fallback to the commit > partition path. > From the "server" side > * If the local txn is COMMITED or ABORTED, return the response with the > outcome: commit or abort. > * If the local txn is FINISHING ** (waiting for finish state replication), > wait for outcome and return response with the result: commit or abort > ** If the result is to commit, additional timestamp check is required: a > commit timestamp must be <= readTs. If the condition is not held, the result > is changed to abort. > * If local txn is PENDING, adjust the txn coordinator node HLC according to > readTs to make sure the txn commit timestamp is above the read timestamp. The > read timestamp must be installed before txn is started to commit, so commit > timestamp is assigned after the read timestamp. This must be achieved by some > sort of concurrency control, preferably non-blocking. In this case we must > ignore the write intent, so the outcome is to abort. > * If txn state is not found in a local cache and txn is not active, return > NULL. > h3. Implementation Notes > Open questions: > * Which component is responsible for handling TxStateReq? > * How to await FINISHING state termination? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20413) Update ignite dependency: zstd
[ https://issues.apache.org/jira/browse/IGNITE-20413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Nikolaev updated IGNITE-20413: Priority: Minor (was: Major) > Update ignite dependency: zstd > -- > > Key: IGNITE-20413 > URL: https://issues.apache.org/jira/browse/IGNITE-20413 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Nikolaev >Assignee: Aleksandr Nikolaev >Priority: Minor > Labels: ise > Fix For: 2.16 > > > Update Ignite dependency: zstd 1.5.2-5 to 1.5.5-5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20412) Fix ItIgniteDistributionZoneManagerNodeRestartTest#testScaleUpTriggeredByFilterUpdateIsRestoredAfterRestart again
Kirill Tkalenko created IGNITE-20412: Summary: Fix ItIgniteDistributionZoneManagerNodeRestartTest#testScaleUpTriggeredByFilterUpdateIsRestoredAfterRestart again Key: IGNITE-20412 URL: https://issues.apache.org/jira/browse/IGNITE-20412 Project: Ignite Issue Type: Improvement Reporter: Kirill Tkalenko Assignee: Sergey Uttsel Fix For: 3.0.0-beta2 *org.apache.ignite.internal.distribution.zones.ItIgniteDistributionZoneManagerNodeRestartTest#testScaleUpTriggeredByFilterUpdateIsRestoredAfterRestart* started to fall in the [catalog-feature|https://github.com/apache/ignite-3/tree/catalog-feature] branch, and on other branches that are created from it branch, need to fix it. https://ci.ignite.apache.org/viewLog.html?buildId=7470189=ApacheIgnite3xGradle_Test_RunAllTests=true -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20413) Update ignite dependency: zstd
Aleksandr Nikolaev created IGNITE-20413: --- Summary: Update ignite dependency: zstd Key: IGNITE-20413 URL: https://issues.apache.org/jira/browse/IGNITE-20413 Project: Ignite Issue Type: Improvement Reporter: Aleksandr Nikolaev Assignee: Aleksandr Nikolaev Fix For: 2.16 Update Ignite dependency: zstd 1.5.2-5 to 1.5.5-5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20412) Fix ItIgniteDistributionZoneManagerNodeRestartTest#testScaleUpTriggeredByFilterUpdateIsRestoredAfterRestart again
[ https://issues.apache.org/jira/browse/IGNITE-20412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-20412: - Description: *org.apache.ignite.internal.distribution.zones.ItIgniteDistributionZoneManagerNodeRestartTest#testScaleUpTriggeredByFilterUpdateIsRestoredAfterRestart* started to fall in the [catalog-feature|https://github.com/apache/ignite-3/tree/catalog-feature] branch, and on other branches that are created from it branch, need to fix it. https://ci.ignite.apache.org/viewLog.html?buildId=7501721=buildResultsDiv=ApacheIgnite3xGradle_Test_RunAllTests= was: *org.apache.ignite.internal.distribution.zones.ItIgniteDistributionZoneManagerNodeRestartTest#testScaleUpTriggeredByFilterUpdateIsRestoredAfterRestart* started to fall in the [catalog-feature|https://github.com/apache/ignite-3/tree/catalog-feature] branch, and on other branches that are created from it branch, need to fix it. https://ci.ignite.apache.org/viewLog.html?buildId=7470189=ApacheIgnite3xGradle_Test_RunAllTests=true > Fix > ItIgniteDistributionZoneManagerNodeRestartTest#testScaleUpTriggeredByFilterUpdateIsRestoredAfterRestart > again > - > > Key: IGNITE-20412 > URL: https://issues.apache.org/jira/browse/IGNITE-20412 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > *org.apache.ignite.internal.distribution.zones.ItIgniteDistributionZoneManagerNodeRestartTest#testScaleUpTriggeredByFilterUpdateIsRestoredAfterRestart* > started to fall in the > [catalog-feature|https://github.com/apache/ignite-3/tree/catalog-feature] > branch, and on other branches that are created from it branch, need to fix it. > https://ci.ignite.apache.org/viewLog.html?buildId=7501721=buildResultsDiv=ApacheIgnite3xGradle_Test_RunAllTests= -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20412) Fix ItIgniteDistributionZoneManagerNodeRestartTest#testScaleUpTriggeredByFilterUpdateIsRestoredAfterRestart again
[ https://issues.apache.org/jira/browse/IGNITE-20412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-20412: - Reviewer: (was: Mirza Aliev) > Fix > ItIgniteDistributionZoneManagerNodeRestartTest#testScaleUpTriggeredByFilterUpdateIsRestoredAfterRestart > again > - > > Key: IGNITE-20412 > URL: https://issues.apache.org/jira/browse/IGNITE-20412 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > *org.apache.ignite.internal.distribution.zones.ItIgniteDistributionZoneManagerNodeRestartTest#testScaleUpTriggeredByFilterUpdateIsRestoredAfterRestart* > started to fall in the > [catalog-feature|https://github.com/apache/ignite-3/tree/catalog-feature] > branch, and on other branches that are created from it branch, need to fix it. > https://ci.ignite.apache.org/viewLog.html?buildId=7470189=ApacheIgnite3xGradle_Test_RunAllTests=true -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19466) Empty data nodes on table creation
[
https://issues.apache.org/jira/browse/IGNITE-19466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-19466:
-
Epic Link: IGNITE-19743
> Empty data nodes on table creation
> --
>
> Key: IGNITE-19466
> URL: https://issues.apache.org/jira/browse/IGNITE-19466
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Uttsel
>Assignee: Sergey Uttsel
>Priority: Major
> Labels: ignite-3, tech-debt
>
> h3. *Motivation*
> After introducing data nodes from DistributionZoneManager on table creation
> it became possible that a table is created with an empty data nodes value and
> therefore with empty assignments. It causes an exceptions like
> {code:java}
> Caused by: org.apache.ignite.lang.IgniteException: IGN-CMN-65535
> TraceId:3ae1368c-0475-48b4-bd88-4e00b6c0fccd Peers are not ready
> [groupId=1_part_0]
> at
> org.apache.ignite.lang.IgniteExceptionUtils.wrap(IgniteExceptionUtils.java:198)
> at
> org.apache.ignite.internal.table.distributed.TableManager.getRootCause(TableManager.java:1745)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$changeTablesConfigurationOnTableCreate$63(TableManager.java:1633)
> at
> java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986)
> at
> java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:970)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2159)
> at
> org.apache.ignite.internal.configuration.ConfigurationChanger.lambda$configurationStorageListener$8(ConfigurationChanger.java:657)
> at
> java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
> at
> java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2159)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTablePartitionsLocally$15(TableManager.java:910)
> at
> java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
> at
> java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
> 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$UniCompose.tryFire(CompletableFuture.java:1159)
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
> 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:830)
> Caused by: org.apache.ignite.lang.IgniteInternalException: IGN-CMN-65535
> TraceId:3ae1368c-0475-48b4-bd88-4e00b6c0fccd Peers are not ready
> [groupId=1_part_0]
> at
> org.apache.ignite.internal.raft.RaftGroupServiceImpl.randomNode(RaftGroupServiceImpl.java:686)
> at
> org.apache.ignite.internal.raft.RaftGroupServiceImpl.randomNode(RaftGroupServiceImpl.java:670)
> at
> org.apache.ignite.internal.raft.RaftGroupServiceImpl.refreshLeader(RaftGroupServiceImpl.java:224)
> at
> org.apache.ignite.internal.raft.RaftGroupServiceImpl.start(RaftGroupServiceImpl.java:180)
> at
> org.apache.ignite.internal.raft.client.TopologyAwareRaftGroupService.start(TopologyAwareRaftGroupService.java:182)
> at
> org.apache.ignite.internal.raft.client.TopologyAwareRaftGroupServiceFactory.startRaftGroupService(TopologyAwareRaftGroupServiceFactory.java:71)
> at
> org.apache.ignite.internal.raft.Loza.startRaftGroupService(Loza.java:321)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTablePartitionsLocally$11(TableManager.java:874)
> at
> org.apache.ignite.internal.util.IgniteUtils.inBusyLock(IgniteUtils.java:893)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTablePartitionsLocally$12(TableManager.java:870)
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1146)
> ... 4 more{code}
> because there are an empty peers on RaftGroupServiceImpl#start. The proper
> solution is a table creation with empty peers but remains
[jira] [Updated] (IGNITE-19765) Throw appropriate exception on operation with not full started table
[
https://issues.apache.org/jira/browse/IGNITE-19765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-19765:
-
Epic Link: IGNITE-19743
> Throw appropriate exception on operation with not full started table
>
>
> Key: IGNITE-19765
> URL: https://issues.apache.org/jira/browse/IGNITE-19765
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Uttsel
>Priority: Major
> Labels: ignite-3, tech-debt
>
> h3. *Motivation*
> After prototyping for https://issues.apache.org/jira/browse/IGNITE-19466 I
> see that if a table is created without data nodes in zone and I try to invoke
> some operation, for example
> {code:java}
> table.recordView().insert(null, Tuple.create().set("key", 1L).set("val",
> 2));{code}
> it throws a NPE
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.enlist(InternalTableImpl.java:1233)
> at
> org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.enlistWithRetry(InternalTableImpl.java:427)
> at
> org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.enlistInTx(InternalTableImpl.java:259)
> at
> org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.insert(InternalTableImpl.java:658)
> at
> org.apache.ignite.internal.table.RecordBinaryViewImpl.insertAsync(RecordBinaryViewImpl.java:147)
> at
> org.apache.ignite.internal.table.RecordBinaryViewImpl.insert(RecordBinaryViewImpl.java:137)
> at
> org.apache.ignite.internal.table.RecordBinaryViewImpl.insert(RecordBinaryViewImpl.java:42)
> at
> org.apache.ignite.internal.runner.app.ItIgniteNodeRestartTest.test123(ItIgniteNodeRestartTest.java:1152)
> {code}
> Need to throw meaningful exception in this case with message that a table is
> not ready of operation.
>
> h3. *Definition of Done*
> If a table was created without data nodes need to throw meaningful exception
> on table operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19763) Changing empty stable assignments to not empty pending assignments.
[ https://issues.apache.org/jira/browse/IGNITE-19763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev updated IGNITE-19763: - Epic Link: IGNITE-19743 > Changing empty stable assignments to not empty pending assignments. > --- > > Key: IGNITE-19763 > URL: https://issues.apache.org/jira/browse/IGNITE-19763 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Priority: Major > Labels: ignite-3, tech-debt > > h3. *Motivation* > After https://issues.apache.org/jira/browse/IGNITE-19466 will be implemented > It will be possible to create a table without data nodes in the distribution > zone. Then we will face another issue. > Current flow of changing pending assignments: > # When the zone is updated and has a data nodes then the rebalance will > start on new data nodes. > # The method handleChangePendingAssignmentEvent receives an empty > stableAssignments and not empty pendingAssignments. > # handleChangePendingAssignmentEvent invokes startRaftGroupNode to start > raft group node with stable assignment and start Replica, > PartitionReplicaListener. > # After that starts change peers on with pendingAssignments. > It doesn't work properly because if previous stableAssignments is empty then > it is not possible to start raft group. And if raft group is not started then > it is not possible to change peers. So if stableAssignments is empty then > need to skip starting raft group with this assignments and start new raft > group with pendingAssignments. > h3. *Definition of Done* > Table without data nodes in the zone must process operations after data nodes > are appeared. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20019) Introduce SystemViewManager
[ https://issues.apache.org/jira/browse/IGNITE-20019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin reassigned IGNITE-20019: - Assignee: Pavel Pereslegin > Introduce SystemViewManager > --- > > Key: IGNITE-20019 > URL: https://issues.apache.org/jira/browse/IGNITE-20019 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Assignee: Pavel Pereslegin >Priority: Major > Labels: ignite-3 > > SystemViewManager is a component responsible for managing the system views': > * during start, any component may register view definition to the view > manager. View manager must ensure that there is no clashes in the views' > names. > * before node is going to be validated, view manager must enhance node > attributes (LogicalNode class) with list of clusterViews registered so far. > Later, sql engine will be using this information to map queries over cluster > views properly > * after node has passed validation and ready to join logical topology, view > manager must register all views to the catalog. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20411) IndexOutOfBoundsException in SqlRowHandler$BinaryTupleRowWrapper
[
https://issues.apache.org/jira/browse/IGNITE-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-20411:
Description:
*Exception:*
{code}
java.lang.IndexOutOfBoundsException: Index 2 out of bounds for length 2
at
java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at
java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at
java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
at java.base/java.util.Objects.checkIndex(Objects.java:372)
at java.base/java.util.ArrayList.get(ArrayList.java:459)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler$BinaryTupleRowWrapper.get(SqlRowHandler.java:357)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:74)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:65)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.convertRow(UpdatableTableImpl.java:337)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.insertAll(UpdatableTableImpl.java:242)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:219)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:190)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:163)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.pushUnordered(Inbox.java:344)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.push(Inbox.java:202)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.onBatchReceived(Inbox.java:180)
at
org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.onMessage(ExchangeServiceImpl.java:167)
at
org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.lambda$start$1(ExchangeServiceImpl.java:73)
at
org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:150)
at
org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.lambda$onMessage$0(MessageServiceImpl.java:119)
at
org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:81)
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:829)
{code}
*Reproducer:*
Add this test to *ItSqlSynchronousApiTest*
{code:java}
@Test
public void testUpdateTable() {
IgniteSql sql = igniteSql();
Session ses = sql.createSession();
checkDdl(true, ses, "CREATE TABLE TEST(ID INT PRIMARY KEY, VAL0 INT)");
var upsertFut = CompletableFuture.runAsync(() -> {
for (int i = 0; i < 1000; i++) {
checkDml(1, ses, "INSERT INTO TEST VALUES (?, ?)", i, i);
}
});
checkDdl(true, ses, "ALTER TABLE TEST ADD COLUMN VAL1 INT DEFAULT -1");
upsertFut.join();
}
{code}
*NOTE*
Original exception stack trace seems to be lost if you just run the test, I had
to use debugger to get it. Consider addressing this too.
was:
*Exception:*
{code}
java.lang.IndexOutOfBoundsException: Index 2 out of bounds for length 2
at
java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at
java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at
java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
at java.base/java.util.Objects.checkIndex(Objects.java:372)
at java.base/java.util.ArrayList.get(ArrayList.java:459)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler$BinaryTupleRowWrapper.get(SqlRowHandler.java:357)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:74)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:65)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.convertRow(UpdatableTableImpl.java:337)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.insertAll(UpdatableTableImpl.java:242)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:219)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:190)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:163)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.pushUnordered(Inbox.java:344)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.push(Inbox.java:202)
[jira] [Updated] (IGNITE-20411) IndexOutOfBoundsException in SqlRowHandler$BinaryTupleRowWrapper
[
https://issues.apache.org/jira/browse/IGNITE-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-20411:
Description:
*Exception:*
{code}
java.lang.IndexOutOfBoundsException: Index 2 out of bounds for length 2
at
java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at
java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at
java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
at java.base/java.util.Objects.checkIndex(Objects.java:372)
at java.base/java.util.ArrayList.get(ArrayList.java:459)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler$BinaryTupleRowWrapper.get(SqlRowHandler.java:357)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:74)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:65)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.convertRow(UpdatableTableImpl.java:337)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.insertAll(UpdatableTableImpl.java:242)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:219)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:190)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:163)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.pushUnordered(Inbox.java:344)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.push(Inbox.java:202)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.onBatchReceived(Inbox.java:180)
at
org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.onMessage(ExchangeServiceImpl.java:167)
at
org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.lambda$start$1(ExchangeServiceImpl.java:73)
at
org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:150)
at
org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.lambda$onMessage$0(MessageServiceImpl.java:119)
at
org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:81)
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:829)
{code}
*Reproducer:*
Add this test to *ItSqlSynchronousApiTest*
{code:java}
@Test
public void testUpdateTable() {
IgniteSql sql = igniteSql();
Session ses = sql.createSession();
checkDdl(true, ses, "CREATE TABLE TEST(ID INT PRIMARY KEY, VAL0 INT)");
var upsertFut = CompletableFuture.runAsync(() -> {
for (int i = 0; i < 1000; i++) {
checkDml(1, ses, "INSERT INTO TEST VALUES (?, ?)", i, i);
}
});
checkDdl(true, ses, "ALTER TABLE TEST ADD COLUMN VAL1 INT DEFAULT -1");
upsertFut.join();
}
{code}
*NOTE*
Original exception stack trace seems to be lost, I had to use debugger to get
it. Consider addressing this too.
was:
*Exception:*
{code}
java.lang.IndexOutOfBoundsException: Index 2 out of bounds for length 2
at
java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at
java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at
java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
at java.base/java.util.Objects.checkIndex(Objects.java:372)
at java.base/java.util.ArrayList.get(ArrayList.java:459)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler$BinaryTupleRowWrapper.get(SqlRowHandler.java:357)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:74)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:65)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.convertRow(UpdatableTableImpl.java:337)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.insertAll(UpdatableTableImpl.java:242)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:219)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:190)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:163)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.pushUnordered(Inbox.java:344)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.push(Inbox.java:202)
at
[jira] [Commented] (IGNITE-20407) Update Ignite dependency Snappy
[
https://issues.apache.org/jira/browse/IGNITE-20407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765029#comment-17765029
]
Ignite TC Bot commented on IGNITE-20407:
{panel:title=Branch: [pull/10930/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10930/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7335821buildTypeId=IgniteTests24Java8_RunAll]
> Update Ignite dependency Snappy
> ---
>
> Key: IGNITE-20407
> URL: https://issues.apache.org/jira/browse/IGNITE-20407
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr Nikolaev
>Assignee: Aleksandr Nikolaev
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Update Ignite dependency: Snappy 1.1.8.4 to 1.1.10.3
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20411) IndexOutOfBoundsException in SqlRowHandler$BinaryTupleRowWrapper
[
https://issues.apache.org/jira/browse/IGNITE-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-20411:
Ignite Flags: (was: Docs Required,Release Notes Required)
> IndexOutOfBoundsException in SqlRowHandler$BinaryTupleRowWrapper
>
>
> Key: IGNITE-20411
> URL: https://issues.apache.org/jira/browse/IGNITE-20411
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Tupitsyn
>Priority: Critical
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> *Exception:*
> {code}
> java.lang.IndexOutOfBoundsException: Index 2 out of bounds for length 2
> at
> java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
> at
> java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
> at
> java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
> at java.base/java.util.Objects.checkIndex(Objects.java:372)
> at java.base/java.util.ArrayList.get(ArrayList.java:459)
> at
> org.apache.ignite.internal.sql.engine.exec.SqlRowHandler$BinaryTupleRowWrapper.get(SqlRowHandler.java:357)
> at
> org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:74)
> at
> org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:65)
> at
> org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.convertRow(UpdatableTableImpl.java:337)
> at
> org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.insertAll(UpdatableTableImpl.java:242)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:219)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:190)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:163)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.Inbox.pushUnordered(Inbox.java:344)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.Inbox.push(Inbox.java:202)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.Inbox.onBatchReceived(Inbox.java:180)
> at
> org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.onMessage(ExchangeServiceImpl.java:167)
> at
> org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.lambda$start$1(ExchangeServiceImpl.java:73)
> at
> org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:150)
> at
> org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.lambda$onMessage$0(MessageServiceImpl.java:119)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:81)
> 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:829)
> {code}
> *Reproducer:*
> Add this test to *ItSqlSynchronousApiTest*
> {code:java}
> @Test
> public void testUpdateTable() {
> IgniteSql sql = igniteSql();
> Session ses = sql.createSession();
> checkDdl(true, ses, "CREATE TABLE TEST(ID INT PRIMARY KEY, VAL0
> INT)");
> var upsertFut = CompletableFuture.runAsync(() -> {
> for (int i = 0; i < 1000; i++) {
> checkDml(1, ses, "INSERT INTO TEST VALUES (?, ?)", i, i);
> }
> });
> checkDdl(true, ses, "ALTER TABLE TEST ADD COLUMN VAL1 INT DEFAULT
> -1");
> upsertFut.join();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20411) IndexOutOfBoundsException in SqlRowHandler$BinaryTupleRowWrapper
[
https://issues.apache.org/jira/browse/IGNITE-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-20411:
Description:
*Exception:*
{code}
java.lang.IndexOutOfBoundsException: Index 2 out of bounds for length 2
at
java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at
java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at
java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
at java.base/java.util.Objects.checkIndex(Objects.java:372)
at java.base/java.util.ArrayList.get(ArrayList.java:459)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler$BinaryTupleRowWrapper.get(SqlRowHandler.java:357)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:74)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:65)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.convertRow(UpdatableTableImpl.java:337)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.insertAll(UpdatableTableImpl.java:242)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:219)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:190)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:163)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.pushUnordered(Inbox.java:344)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.push(Inbox.java:202)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.onBatchReceived(Inbox.java:180)
at
org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.onMessage(ExchangeServiceImpl.java:167)
at
org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.lambda$start$1(ExchangeServiceImpl.java:73)
at
org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:150)
at
org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.lambda$onMessage$0(MessageServiceImpl.java:119)
at
org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:81)
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:829)
{code}
*Reproducer:*
Add this test to TODO
{code:java}
@Test
public void testUpdateTable() {
IgniteSql sql = igniteSql();
Session ses = sql.createSession();
checkDdl(true, ses, "CREATE TABLE TEST(ID INT PRIMARY KEY, VAL0 INT)");
var upsertFut = CompletableFuture.runAsync(() -> {
for (int i = 0; i < 1000; i++) {
checkDml(1, ses, "INSERT INTO TEST VALUES (?, ?)", i, i);
}
});
checkDdl(true, ses, "ALTER TABLE TEST ADD COLUMN VAL1 INT DEFAULT -1");
upsertFut.join();
}
{code}
was:
{code}
java.lang.IndexOutOfBoundsException: Index 2 out of bounds for length 2
at
java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at
java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at
java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
at java.base/java.util.Objects.checkIndex(Objects.java:372)
at java.base/java.util.ArrayList.get(ArrayList.java:459)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler$BinaryTupleRowWrapper.get(SqlRowHandler.java:357)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:74)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:65)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.convertRow(UpdatableTableImpl.java:337)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.insertAll(UpdatableTableImpl.java:242)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:219)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:190)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:163)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.pushUnordered(Inbox.java:344)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.push(Inbox.java:202)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.onBatchReceived(Inbox.java:180)
at
[jira] [Updated] (IGNITE-20411) IndexOutOfBoundsException in SqlRowHandler$BinaryTupleRowWrapper
[
https://issues.apache.org/jira/browse/IGNITE-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-20411:
Description:
*Exception:*
{code}
java.lang.IndexOutOfBoundsException: Index 2 out of bounds for length 2
at
java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at
java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at
java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
at java.base/java.util.Objects.checkIndex(Objects.java:372)
at java.base/java.util.ArrayList.get(ArrayList.java:459)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler$BinaryTupleRowWrapper.get(SqlRowHandler.java:357)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:74)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:65)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.convertRow(UpdatableTableImpl.java:337)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.insertAll(UpdatableTableImpl.java:242)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:219)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:190)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:163)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.pushUnordered(Inbox.java:344)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.push(Inbox.java:202)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.onBatchReceived(Inbox.java:180)
at
org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.onMessage(ExchangeServiceImpl.java:167)
at
org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.lambda$start$1(ExchangeServiceImpl.java:73)
at
org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:150)
at
org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.lambda$onMessage$0(MessageServiceImpl.java:119)
at
org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:81)
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:829)
{code}
*Reproducer:*
Add this test to *ItSqlSynchronousApiTest*
{code:java}
@Test
public void testUpdateTable() {
IgniteSql sql = igniteSql();
Session ses = sql.createSession();
checkDdl(true, ses, "CREATE TABLE TEST(ID INT PRIMARY KEY, VAL0 INT)");
var upsertFut = CompletableFuture.runAsync(() -> {
for (int i = 0; i < 1000; i++) {
checkDml(1, ses, "INSERT INTO TEST VALUES (?, ?)", i, i);
}
});
checkDdl(true, ses, "ALTER TABLE TEST ADD COLUMN VAL1 INT DEFAULT -1");
upsertFut.join();
}
{code}
was:
*Exception:*
{code}
java.lang.IndexOutOfBoundsException: Index 2 out of bounds for length 2
at
java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at
java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at
java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
at java.base/java.util.Objects.checkIndex(Objects.java:372)
at java.base/java.util.ArrayList.get(ArrayList.java:459)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler$BinaryTupleRowWrapper.get(SqlRowHandler.java:357)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:74)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:65)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.convertRow(UpdatableTableImpl.java:337)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.insertAll(UpdatableTableImpl.java:242)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:219)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:190)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:163)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.pushUnordered(Inbox.java:344)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.push(Inbox.java:202)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.onBatchReceived(Inbox.java:180)
at
[jira] [Created] (IGNITE-20411) IndexOutOfBoundsException in SqlRowHandler$BinaryTupleRowWrapper
Pavel Tupitsyn created IGNITE-20411:
---
Summary: IndexOutOfBoundsException in
SqlRowHandler$BinaryTupleRowWrapper
Key: IGNITE-20411
URL: https://issues.apache.org/jira/browse/IGNITE-20411
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Pavel Tupitsyn
Fix For: 3.0.0-beta2
{code}
java.lang.IndexOutOfBoundsException: Index 2 out of bounds for length 2
at
java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at
java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at
java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
at java.base/java.util.Objects.checkIndex(Objects.java:372)
at java.base/java.util.ArrayList.get(ArrayList.java:459)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler$BinaryTupleRowWrapper.get(SqlRowHandler.java:357)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:74)
at
org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:65)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.convertRow(UpdatableTableImpl.java:337)
at
org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.insertAll(UpdatableTableImpl.java:242)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:219)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:190)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:163)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.pushUnordered(Inbox.java:344)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.push(Inbox.java:202)
at
org.apache.ignite.internal.sql.engine.exec.rel.Inbox.onBatchReceived(Inbox.java:180)
at
org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.onMessage(ExchangeServiceImpl.java:167)
at
org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.lambda$start$1(ExchangeServiceImpl.java:73)
at
org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:150)
at
org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.lambda$onMessage$0(MessageServiceImpl.java:119)
at
org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:81)
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:829)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20410) ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication fails with ReplicationTimeoutException
Alexander Lapin created IGNITE-20410:
Summary:
ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication
fails with ReplicationTimeoutException
Key: IGNITE-20410
URL: https://issues.apache.org/jira/browse/IGNITE-20410
Project: Ignite
Issue Type: Bug
Reporter: Alexander Lapin
ItSchemaSyncAndReplicationTest#laggingSchemasPreventPartitionDataReplication
fails with ReplicationTimeoutException because of Metadata unavailability on
replication node.
With some extra debug output I got following result:
{code:java}
applyUpdateCommand
applyCmdWithExceptionHandling messageType = 43, groupType = 9
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
...
...
...
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
complete resp = ErrorResponseImpl [errorCode=1009, errorMsg=Metadata not yet
available, group '1_part_0', required level 3; rejecting ActionRequest with
EBUSY., leaderId=null], err = null
applyCmdWithExceptionHandling RuntimeException
Replication is timed out [replicaGrpId=1_part_0]
org.apache.ignite.tx.TransactionException: IGN-REP-3
TraceId:b5ea497a-7985-414a-8b44-8a880704bf80 Replication is timed out
[replicaGrpId=1_part_0]
at
app//org.apache.ignite.internal.util.ExceptionUtils.lambda$withCause$0(ExceptionUtils.java:378)
at
app//org.apache.ignite.internal.util.ExceptionUtils.withCauseInternal(ExceptionUtils.java:461)
at
app//org.apache.ignite.internal.util.ExceptionUtils.withCause(ExceptionUtils.java:378)
at
app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.wrapReplicationException(InternalTableImpl.java:1630)
at
app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$postEnlist$9(InternalTableImpl.java:521)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:934)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:911)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
at
app//org.apache.ignite.internal.table.distributed.storage.InternalTableImpl.lambda$enlistWithRetry$5(InternalTableImpl.java:495)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:934)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:911)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
at
app//org.apache.ignite.internal.replicator.ReplicaService.lambda$sendToReplica$3(ReplicaService.java:97)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
at
java.base@18.0.2/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:483)
at
java.base@18.0.2/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
at
java.base@18.0.2/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
at
java.base@18.0.2/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
at
java.base@18.0.2/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
at
java.base@18.0.2/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
Caused by:
[jira] [Updated] (IGNITE-20409) Refactor org.apache.ignite.Ignition#init
[
https://issues.apache.org/jira/browse/IGNITE-20409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Gagarkin updated IGNITE-20409:
---
Description:
In the current implementation, the method {{org.apache.ignite.Ignition#init}}
accepts an instance of {{{}org.apache.ignite.InitParameters{}}}. Within this
parameter object, there's a field called {{{}destinationNodeName{}}}. After
reviewing the API consistency and internal usage, it appears that the current
structure might be over-complicated and inconsistent with other methods of the
{{Ignition}} class.Proposed Changes: # Refactor the
{{org.apache.ignite.Ignition#init}} method to accept {{destinationNodeName}} as
a direct parameter rather than as part of the {{InitParameters}} object.
# Update the {{InitParameters}} class to remove the {{destinationNodeName}}
field.
# Update tests which are affected by these changes.
Rationale:
* Enhances API clarity by reducing the complexity of method parameters.
* Makes the method signature more consistent with other methods in the
{{Ignition}} class.
* Provides flexibility for internal usage of the {{InitParameters}} without
the node name.
was:
In the current implementation, the method {{org.apache.ignite.Ignition#init}}
accepts an instance of {{{}org.apache.ignite.InitParameters{}}}. Within this
parameter object, there's a field called {{{}destinationNodeName{}}}. After
reviewing the API consistency and internal usage, it appears that the current
structure might be over-complicated and inconsistent with other methods of the
{{Ignition}} class.Proposed Changes: # Refactor the
{{org.apache.ignite.Ignition#init}} method to accept {{destinationNodeName}} as
a direct parameter rather than as part of the {{InitParameters}} object.
# Update the {{InitParameters}} class to remove the {{destinationNodeName}}
field.
# Update tests which are affected by these changes.
Rationale: * Enhances API clarity by reducing the complexity of method
parameters.
* Makes the method signature more consistent with other methods in the
{{Ignition}} class.
* Provides flexibility for internal usage of the {{InitParameters}} without
the node name.
> Refactor org.apache.ignite.Ignition#init
>
>
> Key: IGNITE-20409
> URL: https://issues.apache.org/jira/browse/IGNITE-20409
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Gagarkin
>Assignee: Ivan Gagarkin
>Priority: Major
> Labels: ignite-3
>
> In the current implementation, the method {{org.apache.ignite.Ignition#init}}
> accepts an instance of {{{}org.apache.ignite.InitParameters{}}}. Within this
> parameter object, there's a field called {{{}destinationNodeName{}}}. After
> reviewing the API consistency and internal usage, it appears that the current
> structure might be over-complicated and inconsistent with other methods of
> the {{Ignition}} class.Proposed Changes: # Refactor the
> {{org.apache.ignite.Ignition#init}} method to accept {{destinationNodeName}}
> as a direct parameter rather than as part of the {{InitParameters}} object.
> # Update the {{InitParameters}} class to remove the {{destinationNodeName}}
> field.
> # Update tests which are affected by these changes.
> Rationale:
> * Enhances API clarity by reducing the complexity of method parameters.
> * Makes the method signature more consistent with other methods in the
> {{Ignition}} class.
> * Provides flexibility for internal usage of the {{InitParameters}} without
> the node name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-20409) Refactor org.apache.ignite.Ignition#init
[
https://issues.apache.org/jira/browse/IGNITE-20409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Gagarkin reassigned IGNITE-20409:
--
Assignee: Ivan Gagarkin
> Refactor org.apache.ignite.Ignition#init
>
>
> Key: IGNITE-20409
> URL: https://issues.apache.org/jira/browse/IGNITE-20409
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Gagarkin
>Assignee: Ivan Gagarkin
>Priority: Major
> Labels: ignite-3
>
> In the current implementation, the method {{org.apache.ignite.Ignition#init}}
> accepts an instance of {{{}org.apache.ignite.InitParameters{}}}. Within this
> parameter object, there's a field called {{{}destinationNodeName{}}}. After
> reviewing the API consistency and internal usage, it appears that the current
> structure might be over-complicated and inconsistent with other methods of
> the {{Ignition}} class.Proposed Changes: # Refactor the
> {{org.apache.ignite.Ignition#init}} method to accept {{destinationNodeName}}
> as a direct parameter rather than as part of the {{InitParameters}} object.
> # Update the {{InitParameters}} class to remove the {{destinationNodeName}}
> field.
> # Update tests which are affected by these changes.
> Rationale: * Enhances API clarity by reducing the complexity of method
> parameters.
> * Makes the method signature more consistent with other methods in the
> {{Ignition}} class.
> * Provides flexibility for internal usage of the {{InitParameters}} without
> the node name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20409) Refactor org.apache.ignite.Ignition#init
Ivan Gagarkin created IGNITE-20409:
--
Summary: Refactor org.apache.ignite.Ignition#init
Key: IGNITE-20409
URL: https://issues.apache.org/jira/browse/IGNITE-20409
Project: Ignite
Issue Type: Improvement
Reporter: Ivan Gagarkin
In the current implementation, the method {{org.apache.ignite.Ignition#init}}
accepts an instance of {{{}org.apache.ignite.InitParameters{}}}. Within this
parameter object, there's a field called {{{}destinationNodeName{}}}. After
reviewing the API consistency and internal usage, it appears that the current
structure might be over-complicated and inconsistent with other methods of the
{{Ignition}} class.Proposed Changes: # Refactor the
{{org.apache.ignite.Ignition#init}} method to accept {{destinationNodeName}} as
a direct parameter rather than as part of the {{InitParameters}} object.
# Update the {{InitParameters}} class to remove the {{destinationNodeName}}
field.
# Update tests which are affected by these changes.
Rationale: * Enhances API clarity by reducing the complexity of method
parameters.
* Makes the method signature more consistent with other methods in the
{{Ignition}} class.
* Provides flexibility for internal usage of the {{InitParameters}} without
the node name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
