[jira] [Commented] (IGNITE-19447) Switch schema validation to CatalogService
[ https://issues.apache.org/jira/browse/IGNITE-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783331#comment-17783331 ] Roman Puchkovskiy commented on IGNITE-19447: Thanks > Switch schema validation to CatalogService > -- > > Key: IGNITE-19447 > URL: https://issues.apache.org/jira/browse/IGNITE-19447 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: iep-98, ignite-3 > Time Spent: 50m > Remaining Estimate: 0h > > Currently, CatalogService is 'hanging in the air' and real transaction > processing code does not use it. When CatalogService is ready, we need to > switch schema validation to use it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20540) Document configuring logging in AI3
[ https://issues.apache.org/jira/browse/IGNITE-20540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783255#comment-17783255 ] Igor Gusev commented on IGNITE-20540: - [~slava.koptilin] please review. > Document configuring logging in AI3 > --- > > Key: IGNITE-20540 > URL: https://issues.apache.org/jira/browse/IGNITE-20540 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vyacheslav Koptilin >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Need to provide all required information to properly configure logging on the > client side. > 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] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-19447) Switch schema validation to CatalogService
[ https://issues.apache.org/jira/browse/IGNITE-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783219#comment-17783219 ] Kirill Tkalenko commented on IGNITE-19447: -- Looks good! > Switch schema validation to CatalogService > -- > > Key: IGNITE-19447 > URL: https://issues.apache.org/jira/browse/IGNITE-19447 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: iep-98, ignite-3 > Time Spent: 50m > Remaining Estimate: 0h > > Currently, CatalogService is 'hanging in the air' and real transaction > processing code does not use it. When CatalogService is ready, we need to > switch schema validation to use it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20356) Sql. Rework RowHandler "set" operation.
[
https://issues.apache.org/jira/browse/IGNITE-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783213#comment-17783213
]
Maksim Zhuravkov commented on IGNITE-20356:
---
[~xtern] [~amashenkov] could you please review my PR?
> Sql. Rework RowHandler "set" operation.
> ---
>
> Key: IGNITE-20356
> URL: https://issues.apache.org/jira/browse/IGNITE-20356
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Pavel Pereslegin
>Assignee: Maksim Zhuravkov
>Priority: Major
> Labels: ignite-3
> Time Spent: 50m
> Remaining Estimate: 0h
>
> In IGNITE-19791, a wrapper over {{BinaryTuple}} was added.
> This wrapper ({{BinaryTupleRowWrapper}}) does not support the "{{set()}}"
> method
> Instead of using {{set(int, RowT, Object)}} method, we can use the
> {{append(RowT, Object)}} method to add field values sequentially.
> We need:
> * Add a new RowFactory method that will return a builder that allows you to
> append values to row and build the row.
> * Remove the {{RowHandler#set()}} method and rework all related code/tests
> to use the builder.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20617) Sql. Performance degradation in SELECTS (2 nodes VS 1 node)
[
https://issues.apache.org/jira/browse/IGNITE-20617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783211#comment-17783211
]
Pavel Tupitsyn commented on IGNITE-20617:
-
[~korlov] looks good to me.
> Sql. Performance degradation in SELECTS (2 nodes VS 1 node)
> ---
>
> Key: IGNITE-20617
> URL: https://issues.apache.org/jira/browse/IGNITE-20617
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Ivan Artiukhov
>Assignee: Konstantin Orlov
>Priority: Major
> Labels: ignite-3, performance
> Fix For: 3.0.0-beta2
>
> Attachments: 2023-11-02-15-41-10_logs.zip,
> 2023-11-02-15-41-10_run.png, 2023-11-02-15-41-10_run.txt,
> 6b6f0c-select-2srv.png, 6b6f0c-select-logs.zip.zip, echarts.png,
> ignite-config.json, image-2023-11-06-14-36-20-627.png, jdbc-1node-select.png,
> jdbc-2nodes-select.png, sql-1node-select.png, sql-2nodes-select.png,
> sql-logs-2-server-nodes.zip
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ignite 3, rev. 7d188ac7ae068bd69ff0e6e6cfe5a32ac5749d17
> Benchmark:
> [https://github.com/gridgain/YCSB/blob/ycsb-2023.3/ignite3/src/main/java/site/ycsb/db/ignite3/IgniteSqlClient.java]
>
> The benchmark establishes an SQL {{Session}} and perform {{SELECTs}} via
> {{{}preparedStatement{}}}.
>
> Steps:
> * Run an Ignite cluster of 2 nodes with the attached config
> [^ignite-config.json] .
> ** *fsync = false*
> * Run the SQL YCSB benchmark in preload mode:
> ** {{-db site.ycsb.db.ignite3.IgniteSqlClient -load -P
> /opt/pubagent/poc/config/ycsb/workloads/workloadc -threads 1 -p
> recordcount=1 -p dataintegrity=true -p measurementtype=timeseries -p
> hosts=192.168.1.60}}
> * Run the SQL YCSB benchmark in 100% read mode:
> ** {{-db site.ycsb.db.ignite3.IgniteSqlClient -t -P
> /opt/pubagent/poc/config/ycsb/workloads/workloadc -threads 1 -p
> operationcount=1 -p recordcount=1 -p dataintegrity=true -p
> measurementtype=timeseries -p hosts=192.168.1.60 -s}}
> * Observe the following average throughput on reads:
> !sql-2nodes-select.png!
> Server node's logs: [^sql-logs-2-server-nodes.zip]
> Repeat the test with only 1 server node and observe {*}~20x better throughput
> on reads{*}:
> !sql-1node-select.png!
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20617) Sql. Performance degradation in SELECTS (2 nodes VS 1 node)
[
https://issues.apache.org/jira/browse/IGNITE-20617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-20617:
--
Fix Version/s: 3.0.0-beta2
> Sql. Performance degradation in SELECTS (2 nodes VS 1 node)
> ---
>
> Key: IGNITE-20617
> URL: https://issues.apache.org/jira/browse/IGNITE-20617
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Ivan Artiukhov
>Assignee: Konstantin Orlov
>Priority: Major
> Labels: ignite-3, performance
> Fix For: 3.0.0-beta2
>
> Attachments: 2023-11-02-15-41-10_logs.zip,
> 2023-11-02-15-41-10_run.png, 2023-11-02-15-41-10_run.txt,
> 6b6f0c-select-2srv.png, 6b6f0c-select-logs.zip.zip, echarts.png,
> ignite-config.json, image-2023-11-06-14-36-20-627.png, jdbc-1node-select.png,
> jdbc-2nodes-select.png, sql-1node-select.png, sql-2nodes-select.png,
> sql-logs-2-server-nodes.zip
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ignite 3, rev. 7d188ac7ae068bd69ff0e6e6cfe5a32ac5749d17
> Benchmark:
> [https://github.com/gridgain/YCSB/blob/ycsb-2023.3/ignite3/src/main/java/site/ycsb/db/ignite3/IgniteSqlClient.java]
>
> The benchmark establishes an SQL {{Session}} and perform {{SELECTs}} via
> {{{}preparedStatement{}}}.
>
> Steps:
> * Run an Ignite cluster of 2 nodes with the attached config
> [^ignite-config.json] .
> ** *fsync = false*
> * Run the SQL YCSB benchmark in preload mode:
> ** {{-db site.ycsb.db.ignite3.IgniteSqlClient -load -P
> /opt/pubagent/poc/config/ycsb/workloads/workloadc -threads 1 -p
> recordcount=1 -p dataintegrity=true -p measurementtype=timeseries -p
> hosts=192.168.1.60}}
> * Run the SQL YCSB benchmark in 100% read mode:
> ** {{-db site.ycsb.db.ignite3.IgniteSqlClient -t -P
> /opt/pubagent/poc/config/ycsb/workloads/workloadc -threads 1 -p
> operationcount=1 -p recordcount=1 -p dataintegrity=true -p
> measurementtype=timeseries -p hosts=192.168.1.60 -s}}
> * Observe the following average throughput on reads:
> !sql-2nodes-select.png!
> Server node's logs: [^sql-logs-2-server-nodes.zip]
> Repeat the test with only 1 server node and observe {*}~20x better throughput
> on reads{*}:
> !sql-1node-select.png!
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20757) Create a module for standalone utilities
[
https://issues.apache.org/jira/browse/IGNITE-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-20757:
-
Reviewer: Roman Puchkovskiy
> Create a module for standalone utilities
>
>
> Key: IGNITE-20757
> URL: https://issues.apache.org/jira/browse/IGNITE-20757
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I think that we may need some place, where we could put standalone Java
> applications that can be useful during development and testing. An example of
> such utility can be an application that loads a given amount of random data
> into an Ignite node.
> I propose to create a Gradle module called {{ignite-utilities}} and use it to
> store such applications.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-19723) All REST endpoins should return valid Problem json
[ https://issues.apache.org/jira/browse/IGNITE-19723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Gagarkin reassigned IGNITE-19723: -- Assignee: Ivan Gagarkin > All REST endpoins should return valid Problem json > -- > > Key: IGNITE-19723 > URL: https://issues.apache.org/jira/browse/IGNITE-19723 > Project: Ignite > Issue Type: Bug > Components: rest >Reporter: Aleksandr >Assignee: Ivan Gagarkin >Priority: Major > Labels: ignite-3 > > We have to develop a common mechanism for validation that any REST endpoint > returns valid Problem json. > Here is the definition for valid Problem > https://datatracker.ietf.org/doc/html/rfc7807 > Now we do not set application/json+problem content type. Also, all cases > should be carefully reviewed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20795) Sql. QuerySplitter does not visit IgniteTableFunctionScan nodes.
[ https://issues.apache.org/jira/browse/IGNITE-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-20795: -- Labels: ignite-3 (was: ) > Sql. QuerySplitter does not visit IgniteTableFunctionScan nodes. > > > Key: IGNITE-20795 > URL: https://issues.apache.org/jira/browse/IGNITE-20795 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > > IgniteTableFunctionScan implements SourceAwareIgniteRel but returns hardcoded > sourceId that is equal to -1, because QuerySplitter does not visit nodes of > this type. > Update QuerySpliiter to visit IgniteTableFunctionScan and fix this behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20795) Sql. QuerySplitter does not visit IgniteTableFunctionScan nodes.
[ https://issues.apache.org/jira/browse/IGNITE-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-20795: -- Fix Version/s: 3.0.0-beta2 > Sql. QuerySplitter does not visit IgniteTableFunctionScan nodes. > > > Key: IGNITE-20795 > URL: https://issues.apache.org/jira/browse/IGNITE-20795 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > IgniteTableFunctionScan implements SourceAwareIgniteRel but returns hardcoded > sourceId that is equal to -1, because QuerySplitter does not visit nodes of > this type. > Update QuerySpliiter to visit IgniteTableFunctionScan and fix this behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20795) Sql. QuerySplitter does not visit IgniteTableFunctionScan nodes.
Maksim Zhuravkov created IGNITE-20795: - Summary: Sql. QuerySplitter does not visit IgniteTableFunctionScan nodes. Key: IGNITE-20795 URL: https://issues.apache.org/jira/browse/IGNITE-20795 Project: Ignite Issue Type: Improvement Components: sql Reporter: Maksim Zhuravkov IgniteTableFunctionScan implements SourceAwareIgniteRel but returns hardcoded sourceId that is equal to -1, because QuerySplitter does not visit nodes of this type. Update QuerySpliiter to visit IgniteTableFunctionScan and fix this behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20788) Make primary key indexes immediately available
[ https://issues.apache.org/jira/browse/IGNITE-20788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783180#comment-17783180 ] Roman Puchkovskiy commented on IGNITE-20788: The patch looks good to me > Make primary key indexes immediately available > -- > > Key: IGNITE-20788 > URL: https://issues.apache.org/jira/browse/IGNITE-20788 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > It is necessary to make sure that the created primary key indexes immediately > become available upon table creation and are not built, since this is not > necessary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19619) Term-bases to lease-based switch in SQL engine
[
https://issues.apache.org/jira/browse/IGNITE-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-19619:
--
Description: Sql engine must use {{PlacementDriver}} instead of
{{InternalTable#assignments}} and {{InternalTable#primaryReplicas}} Check the
related TODO in the code base. (was: Sql engine must use {{PlacementDriver}}
instead of {{InternalTable#assignments}} {{InternalTable#primaryReplicas}},
check the related TODO in the code base.)
> Term-bases to lease-based switch in SQL engine
> ---
>
> Key: IGNITE-19619
> URL: https://issues.apache.org/jira/browse/IGNITE-19619
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Alexander Lapin
>Priority: Major
> Labels: ignite-3
>
> Sql engine must use {{PlacementDriver}} instead of
> {{InternalTable#assignments}} and {{InternalTable#primaryReplicas}} Check the
> related TODO in the code base.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19619) Term-bases to lease-based switch in SQL engine
[
https://issues.apache.org/jira/browse/IGNITE-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-19619:
--
Description: Sql engine must use {{PlacementDriver}} instead of
{{InternalTable#assignments}} {{InternalTable#primaryReplicas}}, check the
related TODO in the code base.
> Term-bases to lease-based switch in SQL engine
> ---
>
> Key: IGNITE-19619
> URL: https://issues.apache.org/jira/browse/IGNITE-19619
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Alexander Lapin
>Priority: Major
> Labels: ignite-3
>
> Sql engine must use {{PlacementDriver}} instead of
> {{InternalTable#assignments}} {{InternalTable#primaryReplicas}}, check the
> related TODO in the code base.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-20784) Sql. Derive correct type for numbers manipulations operations.
[
https://issues.apache.org/jira/browse/IGNITE-20784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin resolved IGNITE-20784.
---
Resolution: Duplicate
This issue should be fixed in IGNITE-18662.
> Sql. Derive correct type for numbers manipulations operations.
> --
>
> Key: IGNITE-20784
> URL: https://issues.apache.org/jira/browse/IGNITE-20784
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Evgeny Stanilovsky
>Priority: Major
> Labels: ignite-3
>
> Both:
>
> {code:java}
> SELECT 2147483647 + 1
> SELECT (2147483647 + 1)::DECIMAL(18,0){code}
>
> returns:
> -2147483648
> due to incorrect derive type for type overflow operations.
> note: processing of mentioned cases differs between DB implementations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20757) Create a module for standalone utilities
[
https://issues.apache.org/jira/browse/IGNITE-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-20757:
-
Fix Version/s: 3.0.0-beta2
> Create a module for standalone utilities
>
>
> Key: IGNITE-20757
> URL: https://issues.apache.org/jira/browse/IGNITE-20757
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I think that we may need some place, where we could put standalone Java
> applications that can be useful during development and testing. An example of
> such utility can be an application that loads a given amount of random data
> into an Ignite node.
> I propose to create a Gradle module called {{ignite-utilities}} and use it to
> store such applications.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (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 updated IGNITE-19925:
-
Fix Version/s: 3.0.0-beta2
> 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
> Fix For: 3.0.0-beta2
>
> Attachments: NodeStoppingExceptionTest.java,
> NodeStoppingExceptionTest.log
>
> Time Spent: 2h 20m
> 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] [Updated] (IGNITE-20793) ItConnectionManagerTest#testShutdown is flaky
[
https://issues.apache.org/jira/browse/IGNITE-20793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-20793:
-
Fix Version/s: 3.0.0-beta2
> ItConnectionManagerTest#testShutdown is flaky
> -
>
> Key: IGNITE-20793
> URL: https://issues.apache.org/jira/browse/IGNITE-20793
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Sometimes this test fails with the following exception:
> {code:java}
> java.util.concurrent.ExecutionException:
> org.apache.ignite.internal.network.handshake.ChannelAlreadyExistsException
> at
> org.apache.ignite.internal.future.OrderingFuture.exceptionForThrowingFromGet(OrderingFuture.java:450)
> at
> org.apache.ignite.internal.future.OrderingFuture.get(OrderingFuture.java:437)
> at
> org.apache.ignite.internal.network.netty.ItConnectionManagerTest.testShutdown(ItConnectionManagerTest.java:190)
> at jdk.internal.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
> at
> org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:92)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:86)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:217)
> at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:213)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:138)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:68)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
> at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
> at
> org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
> at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> at
> org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.invokeAll(Sa
[jira] [Commented] (IGNITE-20793) ItConnectionManagerTest#testShutdown is flaky
[
https://issues.apache.org/jira/browse/IGNITE-20793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783167#comment-17783167
]
Aleksandr Polovtcev commented on IGNITE-20793:
--
The problem is that even if a handshake has been completed on the server side,
it doesn't mean that the channel has been created on the client side. This
means that we can still try to open two channels between two Connection
Managers and end up with this exception.
> ItConnectionManagerTest#testShutdown is flaky
> -
>
> Key: IGNITE-20793
> URL: https://issues.apache.org/jira/browse/IGNITE-20793
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Blocker
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Sometimes this test fails with the following exception:
> {code:java}
> java.util.concurrent.ExecutionException:
> org.apache.ignite.internal.network.handshake.ChannelAlreadyExistsException
> at
> org.apache.ignite.internal.future.OrderingFuture.exceptionForThrowingFromGet(OrderingFuture.java:450)
> at
> org.apache.ignite.internal.future.OrderingFuture.get(OrderingFuture.java:437)
> at
> org.apache.ignite.internal.network.netty.ItConnectionManagerTest.testShutdown(ItConnectionManagerTest.java:190)
> at jdk.internal.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
> at
> org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:92)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:86)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:217)
> at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:213)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:138)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:68)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
> at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
> at
> org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
> at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
> at
> org.junit.platf
[jira] [Updated] (IGNITE-19619) Term-bases to lease-based switch in SQL engine
[ https://issues.apache.org/jira/browse/IGNITE-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-19619: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Term-bases to lease-based switch in SQL engine > --- > > Key: IGNITE-19619 > URL: https://issues.apache.org/jira/browse/IGNITE-19619 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Alexander Lapin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-20132) Do not allow an indexed column to be dropped
[ https://issues.apache.org/jira/browse/IGNITE-20132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko resolved IGNITE-20132. -- Resolution: Invalid > Do not allow an indexed column to be dropped > > > Key: IGNITE-20132 > URL: https://issues.apache.org/jira/browse/IGNITE-20132 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > If a column is included in some index which state is STARTING/READY, an > attempt to drop such a column must be rejected -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20132) Do not allow an indexed column to be dropped
[ https://issues.apache.org/jira/browse/IGNITE-20132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko reassigned IGNITE-20132: Assignee: Kirill Tkalenko > Do not allow an indexed column to be dropped > > > Key: IGNITE-20132 > URL: https://issues.apache.org/jira/browse/IGNITE-20132 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > If a column is included in some index which state is STARTING/READY, an > attempt to drop such a column must be rejected -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20132) Do not allow an indexed column to be dropped
[ https://issues.apache.org/jira/browse/IGNITE-20132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783136#comment-17783136 ] Kirill Tkalenko commented on IGNITE-20132: -- As far as I can see, such a check already exists. *org.apache.ignite.internal.catalog.commands.AlterTableDropColumnCommand#get* *org.apache.ignite.internal.catalog.CatalogManagerSelfTest#testDropColumnWithIndexColumns* > Do not allow an indexed column to be dropped > > > Key: IGNITE-20132 > URL: https://issues.apache.org/jira/browse/IGNITE-20132 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > If a column is included in some index which state is STARTING/READY, an > attempt to drop such a column must be rejected -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20774) ItRebalanceDistributedTest#testRebalanceRetryWhenCatchupFailed is flaky on TC
[
https://issues.apache.org/jira/browse/IGNITE-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-20774:
-
Fix Version/s: 3.0.0-beta2
> ItRebalanceDistributedTest#testRebalanceRetryWhenCatchupFailed is flaky on TC
> -
>
> Key: IGNITE-20774
> URL: https://issues.apache.org/jira/browse/IGNITE-20774
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Attachments: _Integration_Tests_Module_Runner_18723.log.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Test fails with timeout in different branches including main:
> {code:java}
> java.util.concurrent.TimeoutException: after() timed out after 60 seconds
> at
> org.junit.jupiter.engine.extension.TimeoutExceptionFactory.create(TimeoutExceptionFactory.java:29)
> at
> org.junit.jupiter.engine.extension.SameThreadTimeoutInvocation.proceed(SameThreadTimeoutInvocation.java:58)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptLifecycleMethod(TimeoutExtension.java:128)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptAfterEachMethod(TimeoutExtension.java:110)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
> ...
> {code}
> From stack trace it is not clear where test timed out.
> TC run with failed test in main is available
> [here|https://ci.ignite.apache.org/viewLog.html?buildId=7593604&tab=buildResultsDiv&buildTypeId=ApacheIgnite3xGradle_Test_IntegrationTests_ModuleRunner]
> test logs are attached.
> Also TC reports NullPointerException in logs, it is not clear whether timeout
> is caused but this NPE:
> {code:java}
> [2023-10-29T00:37:45,888][ERROR][%irdt_trrwcf_2%JRaft-FSMCaller-Disruptor-_stripe_4-0][StripedDisruptor]
> Handle disruptor event error
> [name=%irdt_trrwcf_2%JRaft-FSMCaller-Disruptor-,
> event=org.apache.ignite.raft.jraft.core.FSMCallerImpl$ApplyTask@55293f4b,
> hasHandler=false]
> java.lang.NullPointerException: null
> at
> org.apache.ignite.raft.jraft.core.FSMCallerImpl.doCommitted(FSMCallerImpl.java:492)
> ~[ignite-raft-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.raft.jraft.core.FSMCallerImpl.runApplyTask(FSMCallerImpl.java:382)
> ~[ignite-raft-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.raft.jraft.core.FSMCallerImpl$ApplyTaskHandler.onEvent(FSMCallerImpl.java:136)
> ~[ignite-raft-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.raft.jraft.core.FSMCallerImpl$ApplyTaskHandler.onEvent(FSMCallerImpl.java:130)
> ~[ignite-raft-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.raft.jraft.disruptor.StripedDisruptor$StripeEntryHandler.onEvent(StripedDisruptor.java:226)
> ~[ignite-raft-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.raft.jraft.disruptor.StripedDisruptor$StripeEntryHandler.onEvent(StripedDisruptor.java:191)
> ~[ignite-raft-3.0.0-SNAPSHOT.jar:?]
> at
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:137)
> [disruptor-3.3.7.jar:?]
> at java.lang.Thread.run(Thread.java:834) [?:?]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-20676) Support cipher suites in CLI for REST and JDBC connections
[ https://issues.apache.org/jira/browse/IGNITE-20676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev reassigned IGNITE-20676: - Assignee: Vadim Pakhnushev > Support cipher suites in CLI for REST and JDBC connections > -- > > Key: IGNITE-20676 > URL: https://issues.apache.org/jira/browse/IGNITE-20676 > Project: Ignite > Issue Type: Improvement > Components: cli >Reporter: Ivan Gagarkin >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > > We currently don't have a way to specify cipher suites for CLI when > establishing REST and JDBC connections. > Acceptance Criteria: > # CLI should allow users to specify a list of supported cipher suites for > REST and JDBC connections. > # If the specified cipher suite is not supported by the system, the CLI > should throw an appropriate error message. > # Tests are written to cover the new functionality. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19807) Deprecate legacy authorization approach through Security Context.
[ https://issues.apache.org/jira/browse/IGNITE-19807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikita Amelchev updated IGNITE-19807: - Fix Version/s: 2.16 > Deprecate legacy authorization approach through Security Context. > - > > Key: IGNITE-19807 > URL: https://issues.apache.org/jira/browse/IGNITE-19807 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Fix For: 2.16 > > Time Spent: 50m > Remaining Estimate: 0h > > We currently have several ways to check if a user has permission to perform > an operation. > 1. IgniteSecurity#authorize methods that delegate permission check to > security plugin. > 2. SecurityContext#*OperationAllowed methods. They currently are used just > for one check. This approach assumes that granted permissions set is > returned during user authentication and remains immutable. > Let's deprecate the second authorization approach and migrate completely to > the first. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
