[jira] [Updated] (IGNITE-20740) SocketChannel May leak when connection can not be established
[ https://issues.apache.org/jira/browse/IGNITE-20740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20740: Release Note: Java thin: fixed potential SocketChannel leak on failed connection. (was: Java thin: fixed potential SocketChannel leak on failed connection) > SocketChannel May leak when connection can not be established > - > > Key: IGNITE-20740 > URL: https://issues.apache.org/jira/browse/IGNITE-20740 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.15 >Reporter: ZhangJian He >Assignee: ZhangJian He >Priority: Major > 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-20740) SocketChannel May leak when connection can not be established
[ https://issues.apache.org/jira/browse/IGNITE-20740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20740: Release Note: Java thin: fixed potential SocketChannel leak on failed connection > SocketChannel May leak when connection can not be established > - > > Key: IGNITE-20740 > URL: https://issues.apache.org/jira/browse/IGNITE-20740 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.15 >Reporter: ZhangJian He >Assignee: ZhangJian He >Priority: Major > Fix For: 2.16 > > Time Spent: 1.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20740) SocketChannel May leak when connection can not be established
[ https://issues.apache.org/jira/browse/IGNITE-20740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781102#comment-17781102 ] Pavel Tupitsyn commented on IGNITE-20740: - Merged to master: eb57f7d771430c5f3bd8e10c1c4de77b4314d8fe > SocketChannel May leak when connection can not be established > - > > Key: IGNITE-20740 > URL: https://issues.apache.org/jira/browse/IGNITE-20740 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.15 >Reporter: ZhangJian He >Assignee: ZhangJian He >Priority: Major > 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-20740) SocketChannel May leak when connection can not be established
[ https://issues.apache.org/jira/browse/IGNITE-20740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20740: Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > SocketChannel May leak when connection can not be established > - > > Key: IGNITE-20740 > URL: https://issues.apache.org/jira/browse/IGNITE-20740 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.15 >Reporter: ZhangJian He >Assignee: ZhangJian He >Priority: Major > 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-20740) SocketChannel May leak when connection can not be established
[ https://issues.apache.org/jira/browse/IGNITE-20740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20740: Component/s: thin client > SocketChannel May leak when connection can not be established > - > > Key: IGNITE-20740 > URL: https://issues.apache.org/jira/browse/IGNITE-20740 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.15 >Reporter: ZhangJian He >Assignee: ZhangJian He >Priority: Major > Fix For: 2.16 > > Time Spent: 1.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20740) SocketChannel May leak when connection can not be established
[
https://issues.apache.org/jira/browse/IGNITE-20740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781101#comment-17781101
]
Ignite TC Bot commented on IGNITE-20740:
{panel:title=Branch: [pull/11016/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 TIMEOUT , Exit Code
, TC_SERVICE_MESSAGE
|https://ci2.ignite.apache.org/viewLog.html?buildId=7584542]]
{panel}
{panel:title=Branch: [pull/11016/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=7584403&buildTypeId=IgniteTests24Java8_RunAll]
> SocketChannel May leak when connection can not be established
> -
>
> Key: IGNITE-20740
> URL: https://issues.apache.org/jira/browse/IGNITE-20740
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.15
>Reporter: ZhangJian He
>Assignee: ZhangJian He
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19897) TopologyAwareRaftGroupService#unsubscribeLeader on replica stop is not working approach
[
https://issues.apache.org/jira/browse/IGNITE-19897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781068#comment-17781068
]
Kirill Sizov commented on IGNITE-19897:
This issue leads to the following message in the logs every time a node
restarts:
{code:java}
[ERROR][%itdttntr_n_20002%Raft-Group-Client-13][ReplicaManager] Failed to stop
replica [replicaGrpId=1_part_0]
java.util.concurrent.CompletionException:
org.apache.ignite.internal.lang.NodeStoppingException: IGN-CMN-1
TraceId:ff048254-d8d7-4b8b-b7b3-5c819e599773 Operation has been cancelled (node
is stopping).
at
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
~[?:?]
at
java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:346)
~[?:?]
at
java.util.concurrent.CompletableFuture$BiRelay.tryFire(CompletableFuture.java:1423)
~[?:?]
at
java.util.concurrent.CompletableFuture$CoCompletion.tryFire(CompletableFuture.java:1144)
~[?:?]
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
~[?:?]
at
java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
~[?:?]
at
org.apache.ignite.internal.raft.client.TopologyAwareRaftGroupService.lambda$sendWithRetry$2(TopologyAwareRaftGroupService.java:237)
~[classes/:?]
at
java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
[?:?]
at
java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
[?:?]
at
java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
[?:?]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
[?:?]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[?:?]
at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: org.apache.ignite.internal.lang.NodeStoppingException: Operation has
been cancelled (node is stopping).
at
org.apache.ignite.network.DefaultMessagingService.invoke0(DefaultMessagingService.java:244)
~[classes/:?]
at
org.apache.ignite.network.DefaultMessagingService.invoke(DefaultMessagingService.java:176)
~[classes/:?]
at
org.apache.ignite.network.MessagingService.invoke(MessagingService.java:167)
~[classes/:?]
at
org.apache.ignite.internal.raft.client.TopologyAwareRaftGroupService.sendWithRetry(TopologyAwareRaftGroupService.java:211)
~[classes/:?]
at
org.apache.ignite.internal.raft.client.TopologyAwareRaftGroupService.sendSubscribeMessage(TopologyAwareRaftGroupService.java:197)
~[classes/:?]
at
org.apache.ignite.internal.raft.client.TopologyAwareRaftGroupService.unsubscribeLeader(TopologyAwareRaftGroupService.java:329)
~[classes/:?]
at
org.apache.ignite.internal.replicator.Replica.shutdown(Replica.java:294)
~[classes/:?]
at
java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
~[?:?]
at
java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
~[?:?]
at
org.apache.ignite.internal.replicator.ReplicaManager.stopReplicaInternal(ReplicaManager.java:520)
~[classes/:?]
at
org.apache.ignite.internal.replicator.ReplicaManager.stopReplica(ReplicaManager.java:495)
~[classes/:?]
at
org.apache.ignite.distributed.ItTxTestCluster.shutdownCluster(ItTxTestCluster.java:740)
~[classes/:?]
at
org.apache.ignite.distributed.ItTxDistributedTestSingleNode.after(ItTxDistributedTestSingleNode.java:155)
~[classes/:?]
at
org.apache.ignite.distributed.ItTxDistributedTestThreeNodesThreeReplicas.after(ItTxDistributedTestThreeNodesThreeReplicas.java:68)
~[classes/:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[?:?]
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[?:?]
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
~[junit-platform-commons-1.9.3.jar:1.9.3]
at
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
~[junit-jupiter-engine-5.9.3.jar:5.9.3]
at
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
~[junit
[jira] [Commented] (IGNITE-10516) Storage is corrupted after CREATE INDEX IF NOT EXISTS on different tables
[
https://issues.apache.org/jira/browse/IGNITE-10516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781040#comment-17781040
]
Ignite TC Bot commented on IGNITE-10516:
{panel:title=Branch: [pull/10940/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10940/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=7584483]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IndexWithSameNameH2Test.testSeparateRequests - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IndexWithSameNameH2Test.testMultiLineRequest - PASSED{color}
{color:#8b}Calcite SQL{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=7584446]]
* {color:#013220}IgniteCalciteTestSuite:
IndexWithSameNameCalciteTest.testSeparateRequests - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
IndexWithSameNameCalciteTest.testMultiLineRequest - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7584523&buildTypeId=IgniteTests24Java8_RunAll]
> Storage is corrupted after CREATE INDEX IF NOT EXISTS on different tables
> -
>
> Key: IGNITE-10516
> URL: https://issues.apache.org/jira/browse/IGNITE-10516
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.15
>Reporter: Stanislav Lukyanov
>Assignee: Ilya Shishkov
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
>
> Given two tables in the same schema, we can't create an index with the same
> name for both tables. In other words, the following code leads to an error -
> which is good.
> {code}
> CREATE INDEX IDX on T1 (COL);
> CREATE INDEX IDX on T2 (COL);
> {code}
> If used with `IF NOT EXISTS`, the queries pass. It might be OK or not - one
> needs to look into SQL spec to check if the second operation should be a
> no-op (because IDX exists) or fail (because IDX exists for a different table,
> so the caller is probably doing something wrong)
> {code}
> CREATE INDEX IDX on T1 (COL);
> CREATE INDEX IF NOT EXISTS IDX on T2 (COL);
> {code}
> However, if persistence is enabled, the node will fail to restart complaining
> about duplicate index names.
> {code}
> class org.apache.ignite.IgniteCheckedException: Duplicate index name
> [cache=SQL_PUBLIC_T2, schemaName=PUBLIC, idxName=IDX, existingTable=T,
> table=T2]
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1183)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2040)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1732)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:959)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:900)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:888)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:854)
> at
> org.apache.ignite.IndexWithSameNameTest.test(IndexWithSameNameTest.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteException: Duplicate index name
> [cache=SQL_PUBLIC_T2, schemaName=PUBLIC, idxName=IDX, existingTable=T,
> table=T2]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:1650)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:803)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:866)
>
[jira] [Assigned] (IGNITE-20761) Add values to the properties list command
[
https://issues.apache.org/jira/browse/IGNITE-20761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anastasia Iakimova reassigned IGNITE-20761:
---
Assignee: Anastasia Iakimova
> Add values to the properties list command
> -
>
> Key: IGNITE-20761
> URL: https://issues.apache.org/jira/browse/IGNITE-20761
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikita Amelchev
>Assignee: Anastasia Iakimova
>Priority: Minor
> Labels: ise
>
> The properties list command prints the names of properties. Values can be
> requested by one.
> I suggest adding an ability to view all values at one request for usability
> purposes. For example:
> {noformat}
> control.sh --property list --printValues
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20761) Add values to the properties list command
[
https://issues.apache.org/jira/browse/IGNITE-20761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikita Amelchev updated IGNITE-20761:
-
Labels: ise (was: )
> Add values to the properties list command
> -
>
> Key: IGNITE-20761
> URL: https://issues.apache.org/jira/browse/IGNITE-20761
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikita Amelchev
>Priority: Minor
> Labels: ise
>
> The properties list command prints the names of properties. Values can be
> requested by one.
> I suggest adding an ability to view all values at one request for usability
> purposes. For example:
> {noformat}
> control.sh --property list --printValues
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20761) Add values to the properties list command
Nikita Amelchev created IGNITE-20761:
Summary: Add values to the properties list command
Key: IGNITE-20761
URL: https://issues.apache.org/jira/browse/IGNITE-20761
Project: Ignite
Issue Type: Improvement
Reporter: Nikita Amelchev
The properties list command prints the names of properties. Values can be
requested by one.
I suggest adding an ability to view all values at one request for usability
purposes. For example:
{noformat}
control.sh --property list --printValues
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19908) Sql. EXPLAIN should return plan that actually being used for execution
[ https://issues.apache.org/jira/browse/IGNITE-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781025#comment-17781025 ] Yury Gerzhedovich commented on IGNITE-19908: [~korlov]LGTM > Sql. EXPLAIN should return plan that actually being used for execution > --- > > Key: IGNITE-19908 > URL: https://issues.apache.org/jira/browse/IGNITE-19908 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently, EXPLAIN query always avoid plan cache, while DML and QUERY plans > are cached. This may cause situation when explain reports more optimal plan > than the one actually being used for execution. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20722) Support skipCopies for DumpReader
[ https://issues.apache.org/jira/browse/IGNITE-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-20722: - Fix Version/s: 2.16 > Support skipCopies for DumpReader > - > > Key: IGNITE-20722 > URL: https://issues.apache.org/jira/browse/IGNITE-20722 > Project: Ignite > Issue Type: Task >Reporter: Yuri Naryshkin >Assignee: Yuri Naryshkin >Priority: Minor > Labels: IEP-109, ise > Fix For: 2.16 > > Time Spent: 1h > Remaining Estimate: 0h > > Dump can store several copy of each partition. > DumpReader must provide an option to skip copies and process only one copy > for each partition. > This will reduce restore time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-20731) Exception "The primary replica has changed" on big amount of rows
[
https://issues.apache.org/jira/browse/IGNITE-20731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781013#comment-17781013
]
Alexander Belyak edited comment on IGNITE-20731 at 10/30/23 1:24 PM:
-
Same error on test: create 1000 empty table with 5 column, insert 1 row,
execute 1 simple query on each. GC pauses up to 24sec.
was (Author: berkov):
Same error on test: create 1000 empty table with 5 column, insert 1 row,
execute 1 simple query on each.
> Exception "The primary replica has changed" on big amount of rows
> -
>
> Key: IGNITE-20731
> URL: https://issues.apache.org/jira/browse/IGNITE-20731
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 3.0.0-beta2
>Reporter: Igor
>Priority: Major
> Labels: ignite-3
>
> *Steps to reproduce:*
> 1. Start cluster with 1 node with JVM options: "-Xms4096m -Xmx4096m"
> 2. Execute
> {code:java}
> create table rows_capacity_table(id INTEGER not null, column_1 VARCHAR(50)
> not null, column_2 VARCHAR(50) not null, column_3 VARCHAR(50) not null,
> column_4 VARCHAR(50) not null, primary key (id)) {code}
> 3. Insert rows into table up to 1 000 000 rows.
> *Expected result:*
> Rows are inserted.
> *Actual result:*
> After 733000 rows the exception is thrown.
> Client:
> {code:java}
> java.sql.BatchUpdateException:
> org.apache.ignite.internal.replicator.exception.PrimaryReplicaMissException:
> IGN-REP-6 TraceId:9b8ef95a-bbbe-48cf-9c94-2e80d01c2033 The primary replica
> has changed [expectedLeaseholder=TablesAmountCapacityTest_cluster_0,
> currentLeaseholder=null]
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeBatch(JdbcPreparedStatement.java:155)
> {code}
> Server:
> {code:java}
> 2023-10-23 13:47:31:529 +0300
> [INFO][%TablesAmountCapacityTest_cluster_0%metastorage-watch-executor-0][PartitionReplicaListener]
> Primary replica expired [grp=5_part_12]
> 2023-10-23 13:47:31:532 +0300
> [INFO][%TablesAmountCapacityTest_cluster_0%metastorage-watch-executor-0][PartitionReplicaListener]
> Primary replica expired [grp=5_part_20]
> 2023-10-23 13:47:31:536 +0300
> [INFO][%TablesAmountCapacityTest_cluster_0%metastorage-watch-executor-0][PartitionReplicaListener]
> Primary replica expired [grp=5_part_24]
> 2023-10-23 13:47:31:539 +0300
> [INFO][%TablesAmountCapacityTest_cluster_0%metastorage-watch-executor-0][PartitionReplicaListener]
> Primary replica expired [grp=5_part_16]
> 2023-10-23 13:47:31:699 +0300
> [WARNING][%TablesAmountCapacityTest_cluster_0%metastorage-watch-executor-3][ReplicaManager]
> Failed to process replica request [request=TxFinishReplicaRequestImpl
> [commit=false, commitTimestampLong=111283931920007204, groupId=5_part_24,
> groups=HashSet [5_part_5, 5_part_4, 5_part_7, 5_part_6, 5_part_1, 5_part_0,
> 5_part_3, 5_part_2, 5_part_13, 5_part_12, 5_part_15, 5_part_14, 5_part_9,
> 5_part_8, 5_part_11, 5_part_10, 5_part_21, 5_part_20, 5_part_23, 5_part_22,
> 5_part_17, 5_part_16, 5_part_19, 5_part_18, 5_part_24],
> term=111283839559532593, timestampLong=111283932466315264,
> txId=018b5c25-7653---23c06ab5]]
> java.util.concurrent.CompletionException:
> org.apache.ignite.internal.replicator.exception.PrimaryReplicaMissException:
> IGN-REP-6 TraceId:9b8ef95a-bbbe-48cf-9c94-2e80d01c2033 The primary replica
> has changed [expectedLeaseholder=TablesAmountCapacityTest_cluster_0,
> currentLeaseholder=null]
> at
> java.base/java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:367)
> at
> java.base/java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:376)
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1074)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
> at
> org.apache.ignite.internal.util.PendingComparableValuesTracker.lambda$completeWaitersOnUpdate$0(PendingComparableValuesTracker.java:169)
> at
> java.base/java.util.concurrent.ConcurrentMap.forEach(ConcurrentMap.java:122)
> at
> org.apache.ignite.internal.util.PendingComparableValuesTracker.completeWaitersOnUpdate(PendingComparableValuesTracker.java:169)
> at
> org.apache.ignite.internal.util.PendingComparableValuesTracker.update(PendingComparableValuesTracker.java:103)
> at
> org.apache.ignite.internal.metastorage.server.time.ClusterTimeImpl.updateSafeTime(ClusterTimeImpl.java:146)
> at
> org.apache.ignite.internal.metastorage.impl.MetaStorageManagerImpl.onSafeTimeAdvanced(MetaStorageManagerImpl.java:849)
> at
> org.apache.i
[jira] [Commented] (IGNITE-20731) Exception "The primary replica has changed" on big amount of rows
[
https://issues.apache.org/jira/browse/IGNITE-20731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781013#comment-17781013
]
Alexander Belyak commented on IGNITE-20731:
---
Same error on test: create 1000 empty table with 5 column, insert 1 row,
execute 1 simple query on each.
> Exception "The primary replica has changed" on big amount of rows
> -
>
> Key: IGNITE-20731
> URL: https://issues.apache.org/jira/browse/IGNITE-20731
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 3.0.0-beta2
>Reporter: Igor
>Priority: Major
> Labels: ignite-3
>
> *Steps to reproduce:*
> 1. Start cluster with 1 node with JVM options: "-Xms4096m -Xmx4096m"
> 2. Execute
> {code:java}
> create table rows_capacity_table(id INTEGER not null, column_1 VARCHAR(50)
> not null, column_2 VARCHAR(50) not null, column_3 VARCHAR(50) not null,
> column_4 VARCHAR(50) not null, primary key (id)) {code}
> 3. Insert rows into table up to 1 000 000 rows.
> *Expected result:*
> Rows are inserted.
> *Actual result:*
> After 733000 rows the exception is thrown.
> Client:
> {code:java}
> java.sql.BatchUpdateException:
> org.apache.ignite.internal.replicator.exception.PrimaryReplicaMissException:
> IGN-REP-6 TraceId:9b8ef95a-bbbe-48cf-9c94-2e80d01c2033 The primary replica
> has changed [expectedLeaseholder=TablesAmountCapacityTest_cluster_0,
> currentLeaseholder=null]
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeBatch(JdbcPreparedStatement.java:155)
> {code}
> Server:
> {code:java}
> 2023-10-23 13:47:31:529 +0300
> [INFO][%TablesAmountCapacityTest_cluster_0%metastorage-watch-executor-0][PartitionReplicaListener]
> Primary replica expired [grp=5_part_12]
> 2023-10-23 13:47:31:532 +0300
> [INFO][%TablesAmountCapacityTest_cluster_0%metastorage-watch-executor-0][PartitionReplicaListener]
> Primary replica expired [grp=5_part_20]
> 2023-10-23 13:47:31:536 +0300
> [INFO][%TablesAmountCapacityTest_cluster_0%metastorage-watch-executor-0][PartitionReplicaListener]
> Primary replica expired [grp=5_part_24]
> 2023-10-23 13:47:31:539 +0300
> [INFO][%TablesAmountCapacityTest_cluster_0%metastorage-watch-executor-0][PartitionReplicaListener]
> Primary replica expired [grp=5_part_16]
> 2023-10-23 13:47:31:699 +0300
> [WARNING][%TablesAmountCapacityTest_cluster_0%metastorage-watch-executor-3][ReplicaManager]
> Failed to process replica request [request=TxFinishReplicaRequestImpl
> [commit=false, commitTimestampLong=111283931920007204, groupId=5_part_24,
> groups=HashSet [5_part_5, 5_part_4, 5_part_7, 5_part_6, 5_part_1, 5_part_0,
> 5_part_3, 5_part_2, 5_part_13, 5_part_12, 5_part_15, 5_part_14, 5_part_9,
> 5_part_8, 5_part_11, 5_part_10, 5_part_21, 5_part_20, 5_part_23, 5_part_22,
> 5_part_17, 5_part_16, 5_part_19, 5_part_18, 5_part_24],
> term=111283839559532593, timestampLong=111283932466315264,
> txId=018b5c25-7653---23c06ab5]]
> java.util.concurrent.CompletionException:
> org.apache.ignite.internal.replicator.exception.PrimaryReplicaMissException:
> IGN-REP-6 TraceId:9b8ef95a-bbbe-48cf-9c94-2e80d01c2033 The primary replica
> has changed [expectedLeaseholder=TablesAmountCapacityTest_cluster_0,
> currentLeaseholder=null]
> at
> java.base/java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:367)
> at
> java.base/java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:376)
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1074)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
> at
> org.apache.ignite.internal.util.PendingComparableValuesTracker.lambda$completeWaitersOnUpdate$0(PendingComparableValuesTracker.java:169)
> at
> java.base/java.util.concurrent.ConcurrentMap.forEach(ConcurrentMap.java:122)
> at
> org.apache.ignite.internal.util.PendingComparableValuesTracker.completeWaitersOnUpdate(PendingComparableValuesTracker.java:169)
> at
> org.apache.ignite.internal.util.PendingComparableValuesTracker.update(PendingComparableValuesTracker.java:103)
> at
> org.apache.ignite.internal.metastorage.server.time.ClusterTimeImpl.updateSafeTime(ClusterTimeImpl.java:146)
> at
> org.apache.ignite.internal.metastorage.impl.MetaStorageManagerImpl.onSafeTimeAdvanced(MetaStorageManagerImpl.java:849)
> at
> org.apache.ignite.internal.metastorage.impl.MetaStorageManagerImpl$1.onSafeTimeAdvanced(MetaStorageManagerImpl.java:456)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$advanceSafeTi
[jira] [Commented] (IGNITE-20740) SocketChannel May leak when connection can not be established
[
https://issues.apache.org/jira/browse/IGNITE-20740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781002#comment-17781002
]
Ignite TC Bot commented on IGNITE-20740:
{panel:title=Branch: [pull/11016/head] Base: [master] : Possible Blockers
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 TIMEOUT , Exit Code
, TC_SERVICE_MESSAGE
|https://ci2.ignite.apache.org/viewLog.html?buildId=7584368]]
{color:#d04437}Cache 1{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit
Code , Failure on metric
|https://ci2.ignite.apache.org/viewLog.html?buildId=7584301]]
{color:#d04437}Queries 1 (lazy=true){color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7584371]]
* IgniteBinaryCacheQueryLazyTestSuite:
SchemaExchangeSelfTest.testClientCacheStartDynamic - Test has low fail rate in
base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/11016/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=7584403&buildTypeId=IgniteTests24Java8_RunAll]
> SocketChannel May leak when connection can not be established
> -
>
> Key: IGNITE-20740
> URL: https://issues.apache.org/jira/browse/IGNITE-20740
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.15
>Reporter: ZhangJian He
>Assignee: ZhangJian He
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20760) Drop column error message get indexes by column name only
[
https://issues.apache.org/jira/browse/IGNITE-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Belyak updated IGNITE-20760:
--
Labels: ignite-3 (was: )
> Drop column error message get indexes by column name only
> --
>
> Key: IGNITE-20760
> URL: https://issues.apache.org/jira/browse/IGNITE-20760
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0
>Reporter: Alexander Belyak
>Priority: Major
> Labels: ignite-3
>
> If there are some index, preventing column to be dropped, then error message
> contains all indexes with all columns with the same name. Even if there is
> completely different tables with the same named columns:
> {code:java}
> drop table tab1;
> drop table tab2;
> create table tab1(id integer not null primary key, f1 int);
> create index tab1_f1 on tab1(f1);
> create table tab2(id integer not null primary key, f1 int, f2 int);
> create index tab2_f1 on tab2(f1);
> create index tab2_f12 on tab2(f1,f2);
> alter table tab2 drop column f1;
> >> Fail with wrong error message:
> >> [Code: 0, SQL State: 5] Failed to validate query. Deleting column
> >> 'F1' used by index(es) [TAB1_F1, TAB2_F1, TAB2_F12], it is not allowed
> >> Because it contains TAB1_F1 index
> drop index tab2_f12;
> drop index tab2_f1;
> alter table tab2 drop column f1
> >> Success, so the problem only on the error message generation. {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20760) Drop column error message get indexes by column name only
[
https://issues.apache.org/jira/browse/IGNITE-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Belyak updated IGNITE-20760:
--
Description:
If there are some index, preventing column to be dropped, then error message
contains all indexes with all columns with the same name. Even if there is
completely different tables with the same named columns:
{code:java}
drop table tab1;
drop table tab2;
create table tab1(id integer not null primary key, f1 int);
create index tab1_f1 on tab1(f1);
create table tab2(id integer not null primary key, f1 int, f2 int);
create index tab2_f1 on tab2(f1);
create index tab2_f12 on tab2(f1,f2);
alter table tab2 drop column f1;
>> Fail with wrong error message:
>> [Code: 0, SQL State: 5] Failed to validate query. Deleting column 'F1'
>> used by index(es) [TAB1_F1, TAB2_F1, TAB2_F12], it is not allowed
>> Because it contains TAB1_F1 index
drop index tab2_f12;
drop index tab2_f1;
alter table tab2 drop column f1
>> Success, so the problem only on the error message generation. {code}
was:
If there are some index, preventing column to be dropped, then error message
contains all indexes with all columns with the same name. Even if there is
completely different tables with the same named columns:
{code:java}
drop table tab1;
drop table tab2;
create table tab1(id integer not null primary key, f1 int);
create index tab1_f1 on tab1(f1);
create table tab2(id integer not null primary key, f1 int, f2 int);
create index tab2_f1 on tab2(f1);
create index tab2_f12 on tab2(f1,f2);
alter table tab2 drop column f1;
>> Fail with wrong error message:
>> [Code: 0, SQL State: 5] Failed to validate query. Deleting column 'F1'
>> used by index(es) [TAB1_F1, TAB2_F1, TAB2_F12], it is not allowed
>> Because it contains TAB1_F1 index
drop index tab2_f12;
drop index tab2_f1;
alter table tab2 drop column f1
>> Success, so the problem only on the error message generation. {code}
> Drop column error message get indexes by column name only
> --
>
> Key: IGNITE-20760
> URL: https://issues.apache.org/jira/browse/IGNITE-20760
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0
>Reporter: Alexander Belyak
>Priority: Major
>
> If there are some index, preventing column to be dropped, then error message
> contains all indexes with all columns with the same name. Even if there is
> completely different tables with the same named columns:
> {code:java}
> drop table tab1;
> drop table tab2;
> create table tab1(id integer not null primary key, f1 int);
> create index tab1_f1 on tab1(f1);
> create table tab2(id integer not null primary key, f1 int, f2 int);
> create index tab2_f1 on tab2(f1);
> create index tab2_f12 on tab2(f1,f2);
> alter table tab2 drop column f1;
> >> Fail with wrong error message:
> >> [Code: 0, SQL State: 5] Failed to validate query. Deleting column
> >> 'F1' used by index(es) [TAB1_F1, TAB2_F1, TAB2_F12], it is not allowed
> >> Because it contains TAB1_F1 index
> drop index tab2_f12;
> drop index tab2_f1;
> alter table tab2 drop column f1
> >> Success, so the problem only on the error message generation. {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20760) Drop column error message get indexes by column name only
[
https://issues.apache.org/jira/browse/IGNITE-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Belyak updated IGNITE-20760:
--
Description:
If there are some index, preventing column to be dropped, then error message
contains all indexes with all columns with the same name. Even if there is
completely different tables with the same named columns:
{code:java}
drop table tab1;
drop table tab2;
create table tab1(id integer not null primary key, f1 int);
create index tab1_f1 on tab1(f1);
create table tab2(id integer not null primary key, f1 int, f2 int);
create index tab2_f1 on tab2(f1);
create index tab2_f12 on tab2(f1,f2);
alter table tab2 drop column f1;
>> Fail with wrong error message:
>> [Code: 0, SQL State: 5] Failed to validate query. Deleting column 'F1'
>> used by index(es) [TAB1_F1, TAB2_F1, TAB2_F12], it is not allowed
>> Because it contains TAB1_F1 index
drop index tab2_f12;
drop index tab2_f1;
alter table tab2 drop column f1
>> Success, so the problem only on the error message generation. {code}
was:
If there are some index, preventing column to be dropped, then error message
contains all indexes with all columns with the same name. Even if there is
completely different tables with the same named columns:
{code:java}
drop table tab1;
drop table tab2;
create table tab1(id integer not null primary key, f1 int);
create index tab1_f1 on tab1(f1);create table tab2(id integer not null primary
key, f1 int, f2 int);
create index tab2_f1 on tab2(f1);
create index tab2_f12 on tab2(f1,f2);alter table tab2 drop column f1
>> Fail with wrong error message:
>> [Code: 0, SQL State: 5] Failed to validate query. Deleting column 'F1'
>> used by index(es) [TAB1_F1, TAB2_F1, TAB2_F12], it is not allowed
>> Because it contains TAB1_F1 indexdrop index tab2_f12;
drop index tab2_f1;alter table tab2 drop column f1
>> Success, so the problem only on the error message generation. {code}
> Drop column error message get indexes by column name only
> --
>
> Key: IGNITE-20760
> URL: https://issues.apache.org/jira/browse/IGNITE-20760
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0
>Reporter: Alexander Belyak
>Priority: Major
>
> If there are some index, preventing column to be dropped, then error message
> contains all indexes with all columns with the same name. Even if there is
> completely different tables with the same named columns:
> {code:java}
> drop table tab1;
> drop table tab2;
> create table tab1(id integer not null primary key, f1 int);
> create index tab1_f1 on tab1(f1);
> create table tab2(id integer not null primary key, f1 int, f2 int);
> create index tab2_f1 on tab2(f1);
> create index tab2_f12 on tab2(f1,f2);
> alter table tab2 drop column f1;
> >> Fail with wrong error message:
> >> [Code: 0, SQL State: 5] Failed to validate query. Deleting column
> >> 'F1' used by index(es) [TAB1_F1, TAB2_F1, TAB2_F12], it is not allowed
> >> Because it contains TAB1_F1 index
> drop index tab2_f12;
> drop index tab2_f1;
> alter table tab2 drop column f1
> >> Success, so the problem only on the error message generation. {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20760) Drop column error message get indexes by column name only
Alexander Belyak created IGNITE-20760:
-
Summary: Drop column error message get indexes by column name only
Key: IGNITE-20760
URL: https://issues.apache.org/jira/browse/IGNITE-20760
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 3.0
Reporter: Alexander Belyak
If there are some index, preventing column to be dropped, then error message
contains all indexes with all columns with the same name. Even if there is
completely different tables with the same named columns:
{code:java}
drop table tab1;
drop table tab2;
create table tab1(id integer not null primary key, f1 int);
create index tab1_f1 on tab1(f1);create table tab2(id integer not null primary
key, f1 int, f2 int);
create index tab2_f1 on tab2(f1);
create index tab2_f12 on tab2(f1,f2);alter table tab2 drop column f1
>> Fail with wrong error message:
>> [Code: 0, SQL State: 5] Failed to validate query. Deleting column 'F1'
>> used by index(es) [TAB1_F1, TAB2_F1, TAB2_F12], it is not allowed
>> Because it contains TAB1_F1 indexdrop index tab2_f12;
drop index tab2_f1;alter table tab2 drop column f1
>> Success, so the problem only on the error message generation. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20711) Update Ignite dependency: Apache Commons Codec to 1.16.0
[ https://issues.apache.org/jira/browse/IGNITE-20711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-20711: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Update Ignite dependency: Apache Commons Codec to 1.16.0 > > > Key: IGNITE-20711 > URL: https://issues.apache.org/jira/browse/IGNITE-20711 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Nikolaev >Assignee: Aleksandr Nikolaev >Priority: Major > Labels: ise > Fix For: 2.16 > > Time Spent: 10m > Remaining Estimate: 0h > > Update Ignite dependency: Apache Commons Codec to 1.16.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-20455) Sql. Test Framework. Add System View support.
[ https://issues.apache.org/jira/browse/IGNITE-20455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780956#comment-17780956 ] Konstantin Orlov edited comment on IGNITE-20455 at 10/30/23 10:52 AM: -- [~mzhuravkov], thanks for the contribution! Merged to [main|https://github.com/apache/ignite-3/commit/831e59b6d48ab682c37710eca971ed73083536ff]. was (Author: korlov): [~mzhuravkov], thanks for the contribution! Merged to [main}https://github.com/apache/ignite-3/commit/831e59b6d48ab682c37710eca971ed73083536ff]. > Sql. Test Framework. Add System View support. > -- > > Key: IGNITE-20455 > URL: https://issues.apache.org/jira/browse/IGNITE-20455 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Maksim Zhuravkov >Assignee: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Implement test system view builders - standalone one > (TestBuilders::systemView()) and one for test cluster > (ClusterBuilder::addSystemView()). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20455) Sql. Test Framework. Add System View support.
[ https://issues.apache.org/jira/browse/IGNITE-20455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-20455: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Sql. Test Framework. Add System View support. > -- > > Key: IGNITE-20455 > URL: https://issues.apache.org/jira/browse/IGNITE-20455 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Maksim Zhuravkov >Assignee: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Implement test system view builders - standalone one > (TestBuilders::systemView()) and one for test cluster > (ClusterBuilder::addSystemView()). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (IGNITE-20740) SocketChannel May leak when connection can not be established
[ https://issues.apache.org/jira/browse/IGNITE-20740 ]
Pavel Tupitsyn deleted comment on IGNITE-20740:
-
was (Author: ignitetcbot):
{panel:title=Branch: [pull/11016/head] Base: [master] : Possible Blockers
(7)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ CMake (Win x64 / Debug){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=7591659]]
* IgniteThinClientTest: SslTestSuite: SslConnectionErrorNonExistingKey -
History for base branch is absent.
{color:#d04437}> Build{color} [[tests 4 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=7591850]]
*
org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessorSelfTest.testConvertAfterRestoreIfNeeded
- History for base branch is absent.
*
org.apache.ignite.internal.metric.MetricsConfigurationTest.testConfigRemovedOnCacheGroupRemove
- History for base branch is absent.
* org.apache.ignite.internal.metric.MetricsConfigurationTest.testNodeRestart -
History for base branch is absent.
*
org.apache.ignite.internal.processors.cluster.GridAddressResolverSelfTest.test
- New test duration 60s is more that 1 minute
{color:#d04437}Thin Client: Java{color} [[tests 0 Exit Code , Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=7591666]]
{panel}
{panel:title=Branch: [pull/11016/head] Base: [master] : New Tests
(1736)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform C++ CMake (Win x64 / Debug){color} [[tests
1044|https://ci.ignite.apache.org/viewLog.html?buildId=7591659]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForHost - PASSED{color}
... and 1033 new tests
{color:#8b}> Build{color} [[tests
692|https://ci.ignite.apache.org/viewLog.html?buildId=7591850]]
*
{color:#013220}org.apache.ignite.internal.GridStartStopSelfTest.testStoppedState
- PASSED{color}
*
{color:#013220}org.apache.ignite.internal.GridStartStopSelfTest.testStopWhileInUse
- PASSED{color}
* {color:#013220}org.apache.ignite.internal.GridStartStopSelfTest.testStartStop
- PASSED{color}
*
{color:#013220}org.apache.ignite.internal.GridLifecycleAwareSelfTest.testLifecycleAware
- PASSED{color}
*
{color:#013220}org.apache.ignite.internal.pagemem.wal.record.WALRecordTest.testAllTestWalRecordBuilderConfigured
- PASSED{color}
*
{color:#013220}org.apache.ignite.internal.processors.continuous.GridMessageListenSelfTest.testNonNullTopic
- PASSED{color}
*
{color:#013220}org.apache.ignite.internal.processors.continuous.GridMessageListenSelfTest.testListenActor
- PASSED{color}
*
{color:#013220}org.apache.ignite.internal.processors.continuous.GridMessageListenSelfTest.testProjection
- PASSED{color}
*
{color:#013220}org.apache.ignite.internal.processors.continuous.GridMessageListenSelfTest.testNonNullTopicWithDeployment
- PASSED{color}
*
{color:#013220}org.apache.ignite.internal.processors.continuous.GridMessageListenSelfTest.testNullTopicWithDeployment
- PASSED{color}
*
{color:#013220}org.apache.ignite.internal.GridStopWithCancelSelfTest.testStopGrid
- PASSED{color}
... and 681 new tests
{panel}
[TeamCity *-> Run :: Thin Client*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=7591671&buildTypeId=IgniteTests24Java8_RunThinClient]
> SocketChannel May leak when connection can not be established
> -
>
> Key: IGNITE-20740
> URL: https://issues.apache.org/jira/browse/IGNITE-20740
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.15
>Reporter: ZhangJian He
>Assignee: ZhangJian He
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-20301) ItIgniteInMemoryNodeRestartTest tests are flaky
[ https://issues.apache.org/jira/browse/IGNITE-20301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy reassigned IGNITE-20301: -- Assignee: Roman Puchkovskiy > ItIgniteInMemoryNodeRestartTest tests are flaky > --- > > Key: IGNITE-20301 > URL: https://issues.apache.org/jira/browse/IGNITE-20301 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3, tech-debt > Fix For: 3.0.0-beta2 > > > inMemoryNodeRestartNotLeader and inMemoryNodeFullPartitionRestart fail 50/50 > on my machine. > For both tests, the following is seen in the console when they fail: > [2023-08-29T11:20:35,053][ERROR][%iiimnrt_imnfpr_3344%JRaft-Common-Executor-0][LogThreadPoolExecutor] > Uncaught exception in pool: %iiimnrt_imnfpr_3344%JRaft-Common-Executor-, > org.apache.ignite.raft.jraft.util.MetricThreadPoolExecutor@76504d30[Running, > pool size = 4, active threads = 2, queued tasks = 0, completed tasks = 1601]. > java.lang.IllegalArgumentException: null > at > org.apache.ignite.raft.jraft.util.Requires.requireTrue(Requires.java:64) > ~[main/:?] > at > org.apache.ignite.raft.jraft.core.Replicator.fillCommonFields(Replicator.java:1553) > ~[main/:?] > at > org.apache.ignite.raft.jraft.core.Replicator.sendEntries(Replicator.java:1631) > ~[main/:?] > at > org.apache.ignite.raft.jraft.core.Replicator.sendEntries(Replicator.java:1601) > ~[main/:?] > at > org.apache.ignite.raft.jraft.core.Replicator.continueSending(Replicator.java:983) > ~[main/:?] > at > org.apache.ignite.raft.jraft.core.Replicator.lambda$waitMoreEntries$9(Replicator.java:1583) > ~[main/:?] > at > org.apache.ignite.raft.jraft.storage.impl.LogManagerImpl.runOnNewLog(LogManagerImpl.java:1197) > ~[main/:?] > at > org.apache.ignite.raft.jraft.storage.impl.LogManagerImpl.lambda$wakeupAllWaiter$6(LogManagerImpl.java:398) > ~[main/:?] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?] > at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > ~[?:?] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > ~[?:?] > at java.lang.Thread.run(Thread.java:834) ~[?:?] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20711) Update Ignite dependency: Apache Commons Codec to 1.16.0
[
https://issues.apache.org/jira/browse/IGNITE-20711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780938#comment-17780938
]
Ignite TC Bot commented on IGNITE-20711:
{panel:title=Branch: [pull/11009/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}~[OBSOLETE] Cassandra Store{color} [[tests 0 Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=7580586]]
{panel}
{panel:title=Branch: [pull/11009/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=7573909&buildTypeId=IgniteTests24Java8_RunAll]
> Update Ignite dependency: Apache Commons Codec to 1.16.0
>
>
> Key: IGNITE-20711
> URL: https://issues.apache.org/jira/browse/IGNITE-20711
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr Nikolaev
>Assignee: Aleksandr Nikolaev
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
>
> Update Ignite dependency: Apache Commons Codec to 1.16.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20687) Exclude IgniteTransactions from SQL session creation API
[ https://issues.apache.org/jira/browse/IGNITE-20687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-20687: --- Description: h3. Motivation To start SQL implicit transactions, we apply a specific IgniteTransaction instance for each invocation. But the parameter should not be available through the public API because it is useless for end-users. h3. Implementation notes The easiest way is to add methods (_SessionBuilderImpl#igniteTransactions_) to the implementation of the session builder only (exclude them from the session interface). It allows you to cast directly and pass the Ignite transaction instance as needed. Also, this approach avoids adding confusing methods to the public API. Look it in detail in the PR attached. h3. Definition of done The public session interface is freed from IgniteTransactions (_SessionBuilder#igniteTransactions). was: h3. Motivation To start SQL implicit transactions, we apply a specific IgniteTransaction instance for each invocation. But the parameter should not be available through the public API because it is useless for end-users. h3. Definition on done The public session interface is freed from IgniteTransactions (_SessionBuilder#igniteTransactions_). > Exclude IgniteTransactions from SQL session creation API > > > Key: IGNITE-20687 > URL: https://issues.apache.org/jira/browse/IGNITE-20687 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > > h3. Motivation > To start SQL implicit transactions, we apply a specific IgniteTransaction > instance for each invocation. But the parameter should not be available > through the public API because it is useless for end-users. > h3. Implementation notes > The easiest way is to add methods (_SessionBuilderImpl#igniteTransactions_) > to the implementation of the session builder only (exclude them from the > session interface). It allows you to cast directly and pass the Ignite > transaction instance as needed. > Also, this approach avoids adding confusing methods to the public API. > Look it in detail in the PR attached. > h3. Definition of done > The public session interface is freed from IgniteTransactions > (_SessionBuilder#igniteTransactions). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20744) StandaloneContext should not load plugins from classpath
[ https://issues.apache.org/jira/browse/IGNITE-20744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780923#comment-17780923 ] Anton Vinogradov commented on IGNITE-20744: --- Merged to the master [~NIzhikov], thanks for the review! > StandaloneContext should not load plugins from classpath > > > Key: IGNITE-20744 > URL: https://issues.apache.org/jira/browse/IGNITE-20744 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > Only explicitly specified plugins should be loaded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-20718) DumpIterator for primary copies
[
https://issues.apache.org/jira/browse/IGNITE-20718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov resolved IGNITE-20718.
--
Resolution: Invalid
> DumpIterator for primary copies
> ---
>
> Key: IGNITE-20718
> URL: https://issues.apache.org/jira/browse/IGNITE-20718
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-109, ise
>
> Primary copies of partitions don't contain entry duplicates.
> Because, entries can be filtered based on version on the creation time.
> So, during iteration we don't need to track possible duplicates inside
> {{DumpedPartitionIterator}} implementation in {{partKeys}} variable. This
> will decrease memory consumption and improve performance of dump iteration
> and therefore dump check procedures.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-19925) NodeStoppingException upon stopping an embedded Ignite node
[
https://issues.apache.org/jira/browse/IGNITE-19925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev reassigned IGNITE-19925:
Assignee: Aleksandr Polovtcev (was: Sergey Chugunov)
> NodeStoppingException upon stopping an embedded Ignite node
> ---
>
> Key: IGNITE-19925
> URL: https://issues.apache.org/jira/browse/IGNITE-19925
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Ivan Artiukhov
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
> Attachments: NodeStoppingExceptionTest.java,
> NodeStoppingExceptionTest.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> See the attached reproducer.
> Steps:
> - Start an embedded Ignite node.
> - Create a table via key-vaue: 11 columns of type VARCHAR
> - Insert 10 sample rows
> - Stop the node via {{IgnitionManager#stop}}
> Expected result:
> No exceptions in the node's log
> Actual result:
> The following exception is seen:
> {noformat}
> Caused by: org.apache.ignite.lang.NodeStoppingException: IGN-CMN-1
> TraceId:65d933f8-94bd-41e6-928d-7defcf52744c Operation has been cancelled
> (node is stopping).
> at
> org.apache.ignite.network.DefaultMessagingService.invoke0(DefaultMessagingService.java:227)
> at
> org.apache.ignite.network.DefaultMessagingService.invoke(DefaultMessagingService.java:159)
> at
> org.apache.ignite.network.MessagingService.invoke(MessagingService.java:145)
> at
> org.apache.ignite.internal.raft.client.TopologyAwareRaftGroupService.sendWithRetry(TopologyAwareRaftGroupService.java:211)
> at
> org.apache.ignite.internal.raft.client.TopologyAwareRaftGroupService.sendSubscribeMessage(TopologyAwareRaftGroupService.java:197)
> at
> org.apache.ignite.internal.raft.client.TopologyAwareRaftGroupService.unsubscribeLeader(TopologyAwareRaftGroupService.java:329)
> at
> org.apache.ignite.internal.replicator.Replica.shutdown(Replica.java:278)
> at
> java.base/java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
> at
> java.base/java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
> at
> org.apache.ignite.internal.replicator.ReplicaManager.stopReplicaInternal(ReplicaManager.java:410)
> at
> org.apache.ignite.internal.replicator.ReplicaManager.stopReplica(ReplicaManager.java:385)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$cleanUpTablesResources$30(TableManager.java:1093)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
> at
> org.apache.ignite.internal.table.distributed.TableManager.cleanUpTablesResources(TableManager.java:1119)
> at
> org.apache.ignite.internal.table.distributed.TableManager.stop(TableManager.java:1045)
> at
> org.apache.ignite.internal.app.LifecycleManager.lambda$stopAllComponents$1(LifecycleManager.java:133)
> at java.base/java.util.Iterator.forEachRemaining(Iterator.java:133)
> at
> org.apache.ignite.internal.app.LifecycleManager.stopAllComponents(LifecycleManager.java:131)
> at
> org.apache.ignite.internal.app.LifecycleManager.stopNode(LifecycleManager.java:115)
> at org.apache.ignite.internal.app.IgniteImpl.stop(IgniteImpl.java:807)
> at
> org.apache.ignite.internal.app.IgnitionImpl.lambda$stop$0(IgnitionImpl.java:109)
> at
> java.base/java.util.concurrent.ConcurrentHashMap.computeIfPresent(ConcurrentHashMap.java:1822)
> at
> org.apache.ignite.internal.app.IgnitionImpl.stop(IgnitionImpl.java:108)
> at org.apache.ignite.IgnitionManager.stop(IgnitionManager.java:96)
> at org.apache.ignite.IgnitionManager.stop(IgnitionManager.java:82)
> at
> org.apache.ignite.example.AbstractExamplesTest.stopNode(AbstractExamplesTest.java:76)
> {noformat}
> {{git bisect}} says that the following commit introduced the bug (belongs to
> IGNITE-19199):
> {noformat}
> b6004047b3c3e9cd91b5ccf28c26ee206c1e3a7f is the first bad commit
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-20591) Connect to another cluster does not work from interactive mode
[ https://issues.apache.org/jira/browse/IGNITE-20591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev resolved IGNITE-20591. --- Resolution: Duplicate The root cause of this is when we reconnect in REPL mode, session is not set to new one, instead, warning is printed to the log only. This is fixed in the IGNITE-20705. > Connect to another cluster does not work from interactive mode > -- > > Key: IGNITE-20591 > URL: https://issues.apache.org/jira/browse/IGNITE-20591 > Project: Ignite > Issue Type: Bug > Components: cli >Affects Versions: 3.0.0-beta2 >Reporter: Aleksandr >Priority: Major > Labels: ignite-3 > Attachments: Screenshot 2023-10-06 at 19.19.19.png > > > I had two nodes (10300 and 10400), initialized one node, and wanted to > initialize the second one. It seems like connecting to another node does not > work if you are already connected to some. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20025) Command 'connect defaultNode' throws error
[
https://issues.apache.org/jira/browse/IGNITE-20025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Pakhnushev reassigned IGNITE-20025:
-
Assignee: Vadim Pakhnushev
> Command 'connect defaultNode' throws error
> --
>
> Key: IGNITE-20025
> URL: https://issues.apache.org/jira/browse/IGNITE-20025
> Project: Ignite
> Issue Type: Bug
> Components: cli
>Affects Versions: 3.0.0-beta1
>Reporter: Dmitry Baranov
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
> Attachments: image-2023-07-23-16-57-58-225.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Steps to reproduce the issue
> 1. from disconnected state execute
> {code:java}
> connect{code}
> Connected to http://localhost:10300
> 2.
> {code:java}
> disconnect{code}
> Disconnected from http://localhost:10300
> 3.
> {code:java}
> connect http://localhost:10300{code}
> Connected to http://localhost:10300
> 4. [admin:defaultNode]>
> {code:java}
> disconnect{code}
> Disconnected from http://localhost:10300
> 5. [disconnected]>
> {code:java}
> connect defaultNode{code}
> *Actual:*
> Invalid value for positional parameter at index 0 (): Node
> defaultNode not found. Provide valid name or use URL
> Usage: connect [-hv]
> Connects to Ignite 3 node
> URL or name of an Ignite node
> -h, --help Show help for the specified command
> -v, --verbose Show additional information: logs, REST calls
> {*}Expected{*}:
> Successful connection to the defaultNode
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-20696) Investigate tests slowdown on TC
[ https://issues.apache.org/jira/browse/IGNITE-20696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy resolved IGNITE-20696. Resolution: Won't Fix The slowdown is caused by an additional wait after a DDL. It has been reduced to a minimum. > Investigate tests slowdown on TC > > > Key: IGNITE-20696 > URL: https://issues.apache.org/jira/browse/IGNITE-20696 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20759) Tcp handshake in communication spi hangs on JDK 12 and later
[
https://issues.apache.org/jira/browse/IGNITE-20759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-20759:
-
Labels: ise (was: )
> Tcp handshake in communication spi hangs on JDK 12 and later
>
>
> Key: IGNITE-20759
> URL: https://issues.apache.org/jira/browse/IGNITE-20759
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.15
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Critical
> Labels: ise
>
> This issue is reproduced in {{GridTcpCommunicationSpiSslSelfTest}}. All tests
> hangs during tcp handshake process in infinite loop in
> {{org.apache.ignite.spi.communication.tcp.internal.TcpHandshakeExecutor#tcpHandshake}}.
> Seems that fixes in IGNITE-16622 are not enough
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20759) Tcp handshake in communication spi hangs on JDK 12 and later
[
https://issues.apache.org/jira/browse/IGNITE-20759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-20759:
-
Description: This issue is reproduced in
{{GridTcpCommunicationSpiSslSelfTest}}. All tests hangs during tcp handshake
process in infinite loop in
{{org.apache.ignite.spi.communication.tcp.internal.TcpHandshakeExecutor#tcpHandshake}}.
Seems that fixes in IGNITE-16622 are not enough (was: This issue is
reproduced in {{GridTcpCommunicationSpiSslSelfTest}}. All tests hangs during
tcp handshake process in infinite loop in
{{org.apache.ignite.spi.communication.tcp.internal.TcpHandshakeExecutor#tcpHandshake}})
> Tcp handshake in communication spi hangs on JDK 12 and later
>
>
> Key: IGNITE-20759
> URL: https://issues.apache.org/jira/browse/IGNITE-20759
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.15
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Critical
>
> This issue is reproduced in {{GridTcpCommunicationSpiSslSelfTest}}. All tests
> hangs during tcp handshake process in infinite loop in
> {{org.apache.ignite.spi.communication.tcp.internal.TcpHandshakeExecutor#tcpHandshake}}.
> Seems that fixes in IGNITE-16622 are not enough
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20759) Tcp handshake in communication spi hangs on JDK 12 and later
[
https://issues.apache.org/jira/browse/IGNITE-20759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-20759:
-
Description: This issue is reproduced in
{{GridTcpCommunicationSpiSslSelfTest}}. All tests hangs during tcp handshake
process in infinite loop in
{{org.apache.ignite.spi.communication.tcp.internal.TcpHandshakeExecutor#tcpHandshake}}
(was: This issue is reproduced in {{GridTcpCommunicationSpiSslSelfTest}}. )
> Tcp handshake in communication spi hangs on JDK 12 and later
>
>
> Key: IGNITE-20759
> URL: https://issues.apache.org/jira/browse/IGNITE-20759
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.15
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Critical
>
> This issue is reproduced in {{GridTcpCommunicationSpiSslSelfTest}}. All tests
> hangs during tcp handshake process in infinite loop in
> {{org.apache.ignite.spi.communication.tcp.internal.TcpHandshakeExecutor#tcpHandshake}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20758) Fix LongDestroyDurableBackgroundTaskTest
[
https://issues.apache.org/jira/browse/IGNITE-20758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-20758:
---
Labels: ise (was: )
> Fix LongDestroyDurableBackgroundTaskTest
>
>
> Key: IGNITE-20758
> URL: https://issues.apache.org/jira/browse/IGNITE-20758
> Project: Ignite
> Issue Type: Test
>Reporter: Ilya Shishkov
>Priority: Trivial
> Labels: ise
>
> Some tests fails with error:
> {code}
> java.lang.IllegalArgumentException: Value for '--check-first' property should
> be positive.
> at
> org.apache.ignite.internal.management.cache.CacheValidateIndexesCommandArg.ensurePositive(CacheValidateIndexesCommandArg.java:70)
> at
> org.apache.ignite.internal.management.cache.CacheValidateIndexesCommandArg.checkFirst(CacheValidateIndexesCommandArg.java:165)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest.validateIndexes(LongDestroyDurableBackgroundTaskTest.java:374)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest.testLongIndexDeletion(LongDestroyDurableBackgroundTaskTest.java:339)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest.testLongIndexDeletionSimple(LongDestroyDurableBackgroundTaskTest.java:630)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2499)
> 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-20759) Tcp handshake in communication spi hangs on JDK 12 and later
Ivan Daschinsky created IGNITE-20759:
Summary: Tcp handshake in communication spi hangs on JDK 12 and
later
Key: IGNITE-20759
URL: https://issues.apache.org/jira/browse/IGNITE-20759
Project: Ignite
Issue Type: Bug
Reporter: Ivan Daschinsky
Assignee: Ivan Daschinsky
This issue is reproduced in {{GridTcpCommunicationSpiSslSelfTest}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20759) Tcp handshake in communication spi hangs on JDK 12 and later
[
https://issues.apache.org/jira/browse/IGNITE-20759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-20759:
-
Affects Version/s: 2.15
> Tcp handshake in communication spi hangs on JDK 12 and later
>
>
> Key: IGNITE-20759
> URL: https://issues.apache.org/jira/browse/IGNITE-20759
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.15
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Critical
>
> This issue is reproduced in {{GridTcpCommunicationSpiSslSelfTest}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20758) Fix LongDestroyDurableBackgroundTaskTest
[
https://issues.apache.org/jira/browse/IGNITE-20758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-20758:
---
Ignite Flags: (was: Docs Required,Release Notes Required)
> Fix LongDestroyDurableBackgroundTaskTest
>
>
> Key: IGNITE-20758
> URL: https://issues.apache.org/jira/browse/IGNITE-20758
> Project: Ignite
> Issue Type: Test
>Reporter: Ilya Shishkov
>Priority: Trivial
>
> Some tests fails with error:
> {code}
> java.lang.IllegalArgumentException: Value for '--check-first' property should
> be positive.
> at
> org.apache.ignite.internal.management.cache.CacheValidateIndexesCommandArg.ensurePositive(CacheValidateIndexesCommandArg.java:70)
> at
> org.apache.ignite.internal.management.cache.CacheValidateIndexesCommandArg.checkFirst(CacheValidateIndexesCommandArg.java:165)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest.validateIndexes(LongDestroyDurableBackgroundTaskTest.java:374)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest.testLongIndexDeletion(LongDestroyDurableBackgroundTaskTest.java:339)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest.testLongIndexDeletionSimple(LongDestroyDurableBackgroundTaskTest.java:630)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2499)
> 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-20758) Fix LongDestroyDurableBackgroundTaskTest
Ilya Shishkov created IGNITE-20758:
--
Summary: Fix LongDestroyDurableBackgroundTaskTest
Key: IGNITE-20758
URL: https://issues.apache.org/jira/browse/IGNITE-20758
Project: Ignite
Issue Type: Test
Reporter: Ilya Shishkov
Some tests fails with error:
{code}
java.lang.IllegalArgumentException: Value for '--check-first' property should
be positive.
at
org.apache.ignite.internal.management.cache.CacheValidateIndexesCommandArg.ensurePositive(CacheValidateIndexesCommandArg.java:70)
at
org.apache.ignite.internal.management.cache.CacheValidateIndexesCommandArg.checkFirst(CacheValidateIndexesCommandArg.java:165)
at
org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest.validateIndexes(LongDestroyDurableBackgroundTaskTest.java:374)
at
org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest.testLongIndexDeletion(LongDestroyDurableBackgroundTaskTest.java:339)
at
org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest.testLongIndexDeletionSimple(LongDestroyDurableBackgroundTaskTest.java:630)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2499)
at java.base/java.lang.Thread.run(Thread.java:829)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
