[jira] [Commented] (IGNITE-21295) REST API for manual raft group configuration update
[ https://issues.apache.org/jira/browse/IGNITE-21295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843810#comment-17843810 ] Roman Puchkovskiy commented on IGNITE-21295: The patch looks good to me > REST API for manual raft group configuration update > --- > > Key: IGNITE-21295 > URL: https://issues.apache.org/jira/browse/IGNITE-21295 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Philipp Shergalis >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Implement REST API for IGNITE-21284 > > URL: "reset-partitions" > Body: nullable Collection partitionIds, not null zoneName, not null > tableName (will remove later) > > Collocation is not finished yet, so we have to specify table for the update. > In target state user will specify only zone and partition ids -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22168) Fix fieldsCount in TcpCommunication messages
[
https://issues.apache.org/jira/browse/IGNITE-22168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843787#comment-17843787
]
Ignite TC Bot commented on IGNITE-22168:
{panel:title=Branch: [pull/11339/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11339/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=7855885buildTypeId=IgniteTests24Java8_RunAll]
> Fix fieldsCount in TcpCommunication messages
>
>
> Key: IGNITE-22168
> URL: https://issues.apache.org/jira/browse/IGNITE-22168
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Major
> Labels: ise
> Attachments: IGNITE-22168.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some implementations of interface Message (they are listed below) have method
> {{#fieldsCount}} which returns incorrect value. It can lead to inconsistency
> of IO operations in TcpCommunication protocol.
> ||Class||Caused by||
> |GridCacheQueryRequest|IGNITE-21345|
> |GridCacheQueryResponse|IGNITE-15530|
> |GridDhtTxFinishRequest|IGNITE-21345|
> |GridDhtTxPrepareRequest|IGNITE-21345|
> |GridH2QueryRequest|IGNITE-21345, IGNITE-21628|
> |GridNearGetRequest|IGNITE-21345|
> |GridNearSingleGetRequest|IGNITE-21345|
> |GridNearTxFinishRequest|IGNITE-21345|
> |SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744|
> Reproducer: [^IGNITE-22168.patch]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22176) Propagate Env from parent RocksDb in RocksSnapshotManager
Tiago Marques Godinho created IGNITE-22176: -- Summary: Propagate Env from parent RocksDb in RocksSnapshotManager Key: IGNITE-22176 URL: https://issues.apache.org/jira/browse/IGNITE-22176 Project: Ignite Issue Type: Improvement Affects Versions: 3.0.0-beta1 Reporter: Tiago Marques Godinho The RocsDb environment should be the same as the parent db in the RocksSnapshotManager#createSstFile method. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21295) REST API for manual raft group configuration update
[ https://issues.apache.org/jira/browse/IGNITE-21295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Shergalis updated IGNITE-21295: --- Description: Implement REST API for IGNITE-21284 URL: "reset-partitions" Body: nullable Collection partitionIds, not null zoneName, not null tableName (will remove later) Collocation is not finished yet, so we have to specify table for the update. In target state user will specify only zone and partition ids was: Implement public API for IGNITE-21284 Collocation is not finished yet, so we have to specify table for the update. In target state user will specify only zone and partition ids > REST API for manual raft group configuration update > --- > > Key: IGNITE-21295 > URL: https://issues.apache.org/jira/browse/IGNITE-21295 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Philipp Shergalis >Priority: Major > Labels: ignite-3 > Time Spent: 1h 10m > Remaining Estimate: 0h > > Implement REST API for IGNITE-21284 > > URL: "reset-partitions" > Body: nullable Collection partitionIds, not null zoneName, not null > tableName (will remove later) > > Collocation is not finished yet, so we have to specify table for the update. > In target state user will specify only zone and partition ids -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21295) REST API for manual raft group configuration update
[ https://issues.apache.org/jira/browse/IGNITE-21295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Shergalis updated IGNITE-21295: --- Summary: REST API for manual raft group configuration update (was: Public Java API for manual raft group configuration update) > REST API for manual raft group configuration update > --- > > Key: IGNITE-21295 > URL: https://issues.apache.org/jira/browse/IGNITE-21295 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Philipp Shergalis >Priority: Major > Labels: ignite-3 > Time Spent: 1h 10m > Remaining Estimate: 0h > > Implement public API for IGNITE-21284 > > Collocation is not finished yet, so we have to specify table for the update. > In target state user will specify only zone and partition ids > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22175) Improve handling for RocksDb resources on RocksDbKeyValueStorage
Tiago Marques Godinho created IGNITE-22175: -- Summary: Improve handling for RocksDb resources on RocksDbKeyValueStorage Key: IGNITE-22175 URL: https://issues.apache.org/jira/browse/IGNITE-22175 Project: Ignite Issue Type: Improvement Affects Versions: 3.0.0-beta1 Reporter: Tiago Marques Godinho Some RocksDb resources, including ColumnFamilyHandles, are not being properly closed. Rocks recommend closing these resources. So it's better to play it safe and don't risk some unwanted behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21945) Cover SQL F855(Nested in ) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky reassigned IGNITE-21945: --- Assignee: Evgeny Stanilovsky > Cover SQL F855(Nested in ) feature by > tests > --- > > Key: IGNITE-21945 > URL: https://issues.apache.org/jira/browse/IGNITE-21945 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > > We don't have at all any tests for F855(Nested in expression>) SQL feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22174) Design for UserObjectSerialization
Aleksandr created IGNITE-22174: -- Summary: Design for UserObjectSerialization Key: IGNITE-22174 URL: https://issues.apache.org/jira/browse/IGNITE-22174 Project: Ignite Issue Type: Task Reporter: Aleksandr As a result the IEP should be created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22174) Design for UserObjectSerialization
[ https://issues.apache.org/jira/browse/IGNITE-22174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr reassigned IGNITE-22174: -- Assignee: Aleksandr > Design for UserObjectSerialization > -- > > Key: IGNITE-22174 > URL: https://issues.apache.org/jira/browse/IGNITE-22174 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > > As a result the IEP should be created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19848) User object serialization
[ https://issues.apache.org/jira/browse/IGNITE-19848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr reassigned IGNITE-19848: -- Assignee: Aleksandr > User object serialization > - > > Key: IGNITE-19848 > URL: https://issues.apache.org/jira/browse/IGNITE-19848 > Project: Ignite > Issue Type: Epic >Reporter: Mikhail Pochatkin >Assignee: Aleksandr >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22173) CDC change mode log
[ https://issues.apache.org/jira/browse/IGNITE-22173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Nikolaev updated IGNITE-22173: Description: It is necessary to add logging when switching CDC modes: IGNITE_NODE_ACTIVE to CDC_UTILITY_ACTIVE (was: It is necessary to add logging to CDC modes with IGNITE_NODE_ACTIVEto CDC_UTILITY_ACTIVE) > CDC change mode log > --- > > Key: IGNITE-22173 > URL: https://issues.apache.org/jira/browse/IGNITE-22173 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Nikolaev >Assignee: Aleksandr Nikolaev >Priority: Minor > Labels: ise > Fix For: 2.17 > > > It is necessary to add logging when switching CDC modes: IGNITE_NODE_ACTIVE > to CDC_UTILITY_ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22173) CDC change mode log
[ https://issues.apache.org/jira/browse/IGNITE-22173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Nikolaev updated IGNITE-22173: Description: It is necessary to add logging to CDC modes with IGNITE_NODE_ACTIVEto CDC_UTILITY_ACTIVE (was: If) > CDC change mode log > --- > > Key: IGNITE-22173 > URL: https://issues.apache.org/jira/browse/IGNITE-22173 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Nikolaev >Assignee: Aleksandr Nikolaev >Priority: Minor > Labels: ise > Fix For: 2.17 > > > It is necessary to add logging to CDC modes with IGNITE_NODE_ACTIVEto > CDC_UTILITY_ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22173) CDC change mode log
[ https://issues.apache.org/jira/browse/IGNITE-22173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Nikolaev updated IGNITE-22173: Description: If > CDC change mode log > --- > > Key: IGNITE-22173 > URL: https://issues.apache.org/jira/browse/IGNITE-22173 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Nikolaev >Assignee: Aleksandr Nikolaev >Priority: Minor > > If -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-22167) RocksDB: cannot create a default zone just twice
[
https://issues.apache.org/jira/browse/IGNITE-22167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Khitrin resolved IGNITE-22167.
-
Resolution: Invalid
> RocksDB: cannot create a default zone just twice
>
>
> Key: IGNITE-22167
> URL: https://issues.apache.org/jira/browse/IGNITE-22167
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 3.0.0-beta2
>Reporter: Andrey Khitrin
>Priority: Critical
> Labels: 3.0.0, rocksdb
>
> Steps to reproduce:
> # Start AI3 cluster of 1 node
> # Run few simple SQL queries:
> {code:sql}
> create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
> create table ... with PRIMARY_ZONE='ROCKSDB';
> insert into table ... values(); -- probably, unneeded
> create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
> -- absolutely the same query as the 1st one
> {code}
> Expected behavior: the 2nd "create zone" query must be executed successfully
> (because a zone is already created).
> Actual behavior: the 2nd "create zone" query simply {*}hangs{*}.
> Found on commit 654a11a4a00919ce2b3ff4ca0e59e83377124dea (recent AI3 at the
> time).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22173) CDC change mode log
[ https://issues.apache.org/jira/browse/IGNITE-22173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Nikolaev updated IGNITE-22173: Labels: ise (was: ) > CDC change mode log > --- > > Key: IGNITE-22173 > URL: https://issues.apache.org/jira/browse/IGNITE-22173 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Nikolaev >Assignee: Aleksandr Nikolaev >Priority: Minor > Labels: ise > > If -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22173) CDC change mode log
Aleksandr Nikolaev created IGNITE-22173: --- Summary: CDC change mode log Key: IGNITE-22173 URL: https://issues.apache.org/jira/browse/IGNITE-22173 Project: Ignite Issue Type: Improvement Reporter: Aleksandr Nikolaev Assignee: Aleksandr Nikolaev -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22173) CDC change mode log
[ https://issues.apache.org/jira/browse/IGNITE-22173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Nikolaev updated IGNITE-22173: Fix Version/s: 2.17 > CDC change mode log > --- > > Key: IGNITE-22173 > URL: https://issues.apache.org/jira/browse/IGNITE-22173 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Nikolaev >Assignee: Aleksandr Nikolaev >Priority: Minor > Labels: ise > Fix For: 2.17 > > > If -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22167) RocksDB: cannot create a default zone just twice
[
https://issues.apache.org/jira/browse/IGNITE-22167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843729#comment-17843729
]
Andrey Khitrin commented on IGNITE-22167:
-
Caused by a configuration error in `ignite3-tests.conf` (empty profile list):
{code}
storage {
...
profiles=[]
}
{code}
> RocksDB: cannot create a default zone just twice
>
>
> Key: IGNITE-22167
> URL: https://issues.apache.org/jira/browse/IGNITE-22167
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 3.0.0-beta2
>Reporter: Andrey Khitrin
>Priority: Critical
> Labels: 3.0.0, rocksdb
>
> Steps to reproduce:
> # Start AI3 cluster of 1 node
> # Run few simple SQL queries:
> {code:sql}
> create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
> create table ... with PRIMARY_ZONE='ROCKSDB';
> insert into table ... values(); -- probably, unneeded
> create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
> -- absolutely the same query as the 1st one
> {code}
> Expected behavior: the 2nd "create zone" query must be executed successfully
> (because a zone is already created).
> Actual behavior: the 2nd "create zone" query simply {*}hangs{*}.
> Found on commit 654a11a4a00919ce2b3ff4ca0e59e83377124dea (recent AI3 at the
> time).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-22172) Make ignite-collocation-feature branch stable
[ https://issues.apache.org/jira/browse/IGNITE-22172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-22172: -- Assignee: Vladislav Pyatkov > Make ignite-collocation-feature branch stable > - > > Key: IGNITE-22172 > URL: https://issues.apache.org/jira/browse/IGNITE-22172 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > > h3. Motivation > Too many flaky tests are there. This behavior does not allow us to review a > new patch to the branch because TC is permanently red. > h3. Definition of done > Meke TC green for the ignite-collocation-feature branch. > If this point is not acceptable, we need to describe the current issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21295) Public Java API for manual raft group configuration update
[ https://issues.apache.org/jira/browse/IGNITE-21295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Shergalis updated IGNITE-21295: --- Description: Implement public API for IGNITE-21284 Collocation is not finished yet, so we have to specify table for the update. In target state user will specify only zone and partition ids was: Implement public API for IGNITE-21284 Collocation is not finished yet, so we have to specify table for the update. In target state user will specify only zone and partition ids > Public Java API for manual raft group configuration update > -- > > Key: IGNITE-21295 > URL: https://issues.apache.org/jira/browse/IGNITE-21295 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Philipp Shergalis >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Implement public API for IGNITE-21284 > > Collocation is not finished yet, so we have to specify table for the update. > In target state user will specify only zone and partition ids > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22168) Fix fieldsCount in TcpCommunication messages
[
https://issues.apache.org/jira/browse/IGNITE-22168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-22168:
---
Description:
Some implementations of interface Message (they are listed below) have method
{{#fieldsCount}} which returns incorrect value. It can lead to inconsistency of
IO operations in TcpCommunication protocol.
||Class||Caused by||
|GridCacheQueryRequest|IGNITE-21345|
|GridCacheQueryResponse|IGNITE-15530|
|GridDhtTxFinishRequest|IGNITE-21345|
|GridDhtTxPrepareRequest|IGNITE-21345|
|GridH2QueryRequest|IGNITE-21345, IGNITE-21628|
|GridNearGetRequest|IGNITE-21345|
|GridNearSingleGetRequest|IGNITE-21345|
|GridNearTxFinishRequest|IGNITE-21345|
|SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744|
Reproducer: [^IGNITE-22168.patch]
was:
Method {{Message#fieldsCount}} implementations in classes, which are listed
below, return incorrect fields count. It can lead to inconsistency of IO
operations in TcpCommunication protocol.
||Class||Caused by||
|GridCacheQueryRequest|IGNITE-21345|
|GridCacheQueryResponse|IGNITE-15530|
|GridDhtTxFinishRequest|IGNITE-21345|
|GridDhtTxPrepareRequest|IGNITE-21345|
|GridH2QueryRequest|IGNITE-21345, IGNITE-21628|
|GridNearGetRequest|IGNITE-21345|
|GridNearSingleGetRequest|IGNITE-21345|
|GridNearTxFinishRequest|IGNITE-21345|
|SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744|
Reproducer: [^IGNITE-22168.patch]
> Fix fieldsCount in TcpCommunication messages
>
>
> Key: IGNITE-22168
> URL: https://issues.apache.org/jira/browse/IGNITE-22168
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Major
> Labels: ise
> Attachments: IGNITE-22168.patch
>
>
> Some implementations of interface Message (they are listed below) have method
> {{#fieldsCount}} which returns incorrect value. It can lead to inconsistency
> of IO operations in TcpCommunication protocol.
> ||Class||Caused by||
> |GridCacheQueryRequest|IGNITE-21345|
> |GridCacheQueryResponse|IGNITE-15530|
> |GridDhtTxFinishRequest|IGNITE-21345|
> |GridDhtTxPrepareRequest|IGNITE-21345|
> |GridH2QueryRequest|IGNITE-21345, IGNITE-21628|
> |GridNearGetRequest|IGNITE-21345|
> |GridNearSingleGetRequest|IGNITE-21345|
> |GridNearTxFinishRequest|IGNITE-21345|
> |SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744|
> Reproducer: [^IGNITE-22168.patch]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22172) Make ignite-collocation-feature branch stable
[ https://issues.apache.org/jira/browse/IGNITE-22172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-22172: --- Description: h3. Motivation Too many flaky tests are there. This behavior does not allow us to review a new patch to the branch because TC is permanently red. h3. Definition of done Meke TC green for the ignite-collocation-feature branch. If this point is not acceptable, we need to describe the current issues. was: h3 Motivation Too many flaky tests are there. This behavior does not allow us to review a new patch to the branch because TC is permanently red. h3 Defenition of done Meke TC green for the ignite-collocation-feature branch. If this point is not acceptable, we need to describe the current issues. > Make ignite-collocation-feature branch stable > - > > Key: IGNITE-22172 > URL: https://issues.apache.org/jira/browse/IGNITE-22172 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > > h3. Motivation > Too many flaky tests are there. This behavior does not allow us to review a > new patch to the branch because TC is permanently red. > h3. Definition of done > Meke TC green for the ignite-collocation-feature branch. > If this point is not acceptable, we need to describe the current issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21298) CLI for disaster recovery commands
[ https://issues.apache.org/jira/browse/IGNITE-21298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Shergalis updated IGNITE-21298: --- Description: Names might change. * ignite recovery restart-partitions --nodes [--zones ] [--partitions ] [--purge] * ignite recovery reset-partitions --zone --table [--partitions ] * ignite recovery truncate-log-suffix --zone --partition --index * ignite recovery partition-states [--local [--nodes ] | --global] [--zones ] [--partitions ] was: Names might change. * ignite recovery restart-partitions --nodes [--zones ] [--partitions ] [--purge] * ignite recovery reset-lost-partitions --zone --table [--partitions ] * ignite recovery truncate-log-suffix --zone --partition --index * ignite recovery partition-states [--local [--nodes ] | --global] [--zones ] [--partitions ] > CLI for disaster recovery commands > -- > > Key: IGNITE-21298 > URL: https://issues.apache.org/jira/browse/IGNITE-21298 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Philipp Shergalis >Priority: Major > Labels: ignite-3 > > Names might change. > * ignite recovery restart-partitions --nodes [--zones ] > [--partitions ] [--purge] > * ignite recovery reset-partitions --zone --table > [--partitions ] > * ignite recovery truncate-log-suffix --zone --partition > --index > * ignite recovery partition-states [--local [--nodes ] | --global] > [--zones ] [--partitions ] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22172) Make ignite-collocation-feature branch stable
Vladislav Pyatkov created IGNITE-22172: -- Summary: Make ignite-collocation-feature branch stable Key: IGNITE-22172 URL: https://issues.apache.org/jira/browse/IGNITE-22172 Project: Ignite Issue Type: Improvement Reporter: Vladislav Pyatkov h3 Motivation Too many flaky tests are there. This behavior does not allow us to review a new patch to the branch because TC is permanently red. h3 Defenition of done Meke TC green for the ignite-collocation-feature branch. If this point is not acceptable, we need to describe the current issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22168) Fix fieldsCount in TcpCommunication messages
[
https://issues.apache.org/jira/browse/IGNITE-22168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-22168:
---
Description:
Method {{Message#fieldsCount}} implementations in classes, which are listed
below, return incorrect fields count. It can lead to inconsistency of IO
operations in TcpCommunication protocol.
||Class||Caused by||
|GridCacheQueryRequest|IGNITE-21345|
|GridCacheQueryResponse|IGNITE-15530|
|GridDhtTxFinishRequest|IGNITE-21345|
|GridDhtTxPrepareRequest|IGNITE-21345|
|GridH2QueryRequest|IGNITE-21345, IGNITE-21628|
|GridNearGetRequest|IGNITE-21345|
|GridNearSingleGetRequest|IGNITE-21345|
|GridNearTxFinishRequest|IGNITE-21345|
|SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744|
Reproducer: [^IGNITE-22168.patch]
was:
Messages listed below has incorrect fields count, because it had not been
changed during modifying of fields contents. It can lead to inconsistency of IO
operations in TcpCommunication protocol.
||Class||Caused by||
|GridCacheQueryRequest|IGNITE-21345|
|GridCacheQueryResponse|IGNITE-15530|
|GridDhtTxFinishRequest|IGNITE-21345|
|GridDhtTxPrepareRequest|IGNITE-21345|
|GridH2QueryRequest|IGNITE-21345, IGNITE-21628|
|GridNearGetRequest|IGNITE-21345|
|GridNearSingleGetRequest|IGNITE-21345|
|GridNearTxFinishRequest|IGNITE-21345|
|SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744|
Reproducer: [^IGNITE-22168.patch]
> Fix fieldsCount in TcpCommunication messages
>
>
> Key: IGNITE-22168
> URL: https://issues.apache.org/jira/browse/IGNITE-22168
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Major
> Labels: ise
> Attachments: IGNITE-22168.patch
>
>
> Method {{Message#fieldsCount}} implementations in classes, which are listed
> below, return incorrect fields count. It can lead to inconsistency of IO
> operations in TcpCommunication protocol.
> ||Class||Caused by||
> |GridCacheQueryRequest|IGNITE-21345|
> |GridCacheQueryResponse|IGNITE-15530|
> |GridDhtTxFinishRequest|IGNITE-21345|
> |GridDhtTxPrepareRequest|IGNITE-21345|
> |GridH2QueryRequest|IGNITE-21345, IGNITE-21628|
> |GridNearGetRequest|IGNITE-21345|
> |GridNearSingleGetRequest|IGNITE-21345|
> |GridNearTxFinishRequest|IGNITE-21345|
> |SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744|
> Reproducer: [^IGNITE-22168.patch]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22168) Fix fieldsCount in TcpCommunication messages
[ https://issues.apache.org/jira/browse/IGNITE-22168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-22168: --- Description: Messages listed below has incorrect fields count, because it had not been changed during modifying of fields contents. It can lead to inconsistency of IO operations in TcpCommunication protocol. ||Class||Caused by|| |GridCacheQueryRequest|IGNITE-21345| |GridCacheQueryResponse|IGNITE-15530| |GridDhtTxFinishRequest|IGNITE-21345| |GridDhtTxPrepareRequest|IGNITE-21345| |GridH2QueryRequest|IGNITE-21345, IGNITE-21628| |GridNearGetRequest|IGNITE-21345| |GridNearSingleGetRequest|IGNITE-21345| |GridNearTxFinishRequest|IGNITE-21345| |SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744| Here is a reproducer: [^IGNITE-22168.patch] was: Messages listed below has incorrect fields count, because it had not been changed during modifying of fields contents. It can lead to inconsistency of IO operations in TcpCommunication protocol. ||Class||Caused by|| |GridCacheQueryRequest|IGNITE-21345| |GridCacheQueryResponse|IGNITE-15530| |GridDhtTxFinishRequest|IGNITE-21345| |GridDhtTxPrepareRequest|IGNITE-21345| |GridH2QueryRequest|IGNITE-21345, IGNITE-21628| |GridNearGetRequest|IGNITE-21345| |GridNearSingleGetRequest|IGNITE-21345| |GridNearTxFinishRequest|IGNITE-21345| |SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744| > Fix fieldsCount in TcpCommunication messages > > > Key: IGNITE-22168 > URL: https://issues.apache.org/jira/browse/IGNITE-22168 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Major > Labels: ise > Attachments: IGNITE-22168.patch > > > Messages listed below has incorrect fields count, because it had not been > changed during modifying of fields contents. It can lead to inconsistency of > IO operations in TcpCommunication protocol. > ||Class||Caused by|| > |GridCacheQueryRequest|IGNITE-21345| > |GridCacheQueryResponse|IGNITE-15530| > |GridDhtTxFinishRequest|IGNITE-21345| > |GridDhtTxPrepareRequest|IGNITE-21345| > |GridH2QueryRequest|IGNITE-21345, IGNITE-21628| > |GridNearGetRequest|IGNITE-21345| > |GridNearSingleGetRequest|IGNITE-21345| > |GridNearTxFinishRequest|IGNITE-21345| > |SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744| > Here is a reproducer: [^IGNITE-22168.patch] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22168) Fix fieldsCount in TcpCommunication messages
[ https://issues.apache.org/jira/browse/IGNITE-22168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-22168: --- Description: Messages listed below has incorrect fields count, because it had not been changed during modifying of fields contents. It can lead to inconsistency of IO operations in TcpCommunication protocol. ||Class||Caused by|| |GridCacheQueryRequest|IGNITE-21345| |GridCacheQueryResponse|IGNITE-15530| |GridDhtTxFinishRequest|IGNITE-21345| |GridDhtTxPrepareRequest|IGNITE-21345| |GridH2QueryRequest|IGNITE-21345, IGNITE-21628| |GridNearGetRequest|IGNITE-21345| |GridNearSingleGetRequest|IGNITE-21345| |GridNearTxFinishRequest|IGNITE-21345| |SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744| Reproducer: [^IGNITE-22168.patch] was: Messages listed below has incorrect fields count, because it had not been changed during modifying of fields contents. It can lead to inconsistency of IO operations in TcpCommunication protocol. ||Class||Caused by|| |GridCacheQueryRequest|IGNITE-21345| |GridCacheQueryResponse|IGNITE-15530| |GridDhtTxFinishRequest|IGNITE-21345| |GridDhtTxPrepareRequest|IGNITE-21345| |GridH2QueryRequest|IGNITE-21345, IGNITE-21628| |GridNearGetRequest|IGNITE-21345| |GridNearSingleGetRequest|IGNITE-21345| |GridNearTxFinishRequest|IGNITE-21345| |SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744| Here is a reproducer: [^IGNITE-22168.patch] > Fix fieldsCount in TcpCommunication messages > > > Key: IGNITE-22168 > URL: https://issues.apache.org/jira/browse/IGNITE-22168 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Major > Labels: ise > Attachments: IGNITE-22168.patch > > > Messages listed below has incorrect fields count, because it had not been > changed during modifying of fields contents. It can lead to inconsistency of > IO operations in TcpCommunication protocol. > ||Class||Caused by|| > |GridCacheQueryRequest|IGNITE-21345| > |GridCacheQueryResponse|IGNITE-15530| > |GridDhtTxFinishRequest|IGNITE-21345| > |GridDhtTxPrepareRequest|IGNITE-21345| > |GridH2QueryRequest|IGNITE-21345, IGNITE-21628| > |GridNearGetRequest|IGNITE-21345| > |GridNearSingleGetRequest|IGNITE-21345| > |GridNearTxFinishRequest|IGNITE-21345| > |SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744| > Reproducer: [^IGNITE-22168.patch] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22168) Fix fieldsCount in TcpCommunication messages
[ https://issues.apache.org/jira/browse/IGNITE-22168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-22168: --- Description: Messages listed below has incorrect fields count, because it had not been changed during modifying of fields contents. It can lead to inconsistency of IO operations in TcpCommunication protocol. ||Class||Caused by|| |GridCacheQueryRequest|IGNITE-21345| |GridCacheQueryResponse|IGNITE-15530| |GridDhtTxFinishRequest|IGNITE-21345| |GridDhtTxPrepareRequest|IGNITE-21345| |GridH2QueryRequest|IGNITE-21345, IGNITE-21628| |GridNearGetRequest|IGNITE-21345| |GridNearSingleGetRequest|IGNITE-21345| |GridNearTxFinishRequest|IGNITE-21345| |SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744| > Fix fieldsCount in TcpCommunication messages > > > Key: IGNITE-22168 > URL: https://issues.apache.org/jira/browse/IGNITE-22168 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Major > Labels: ise > Attachments: IGNITE-22168.patch > > > Messages listed below has incorrect fields count, because it had not been > changed during modifying of fields contents. It can lead to inconsistency of > IO operations in TcpCommunication protocol. > ||Class||Caused by|| > |GridCacheQueryRequest|IGNITE-21345| > |GridCacheQueryResponse|IGNITE-15530| > |GridDhtTxFinishRequest|IGNITE-21345| > |GridDhtTxPrepareRequest|IGNITE-21345| > |GridH2QueryRequest|IGNITE-21345, IGNITE-21628| > |GridNearGetRequest|IGNITE-21345| > |GridNearSingleGetRequest|IGNITE-21345| > |GridNearTxFinishRequest|IGNITE-21345| > |SnapshotFilesRequestMessage|IGNITE-17610, IGNITE-15067, IGNITE-14744| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21912) Change API usage of Placement driver for InternalTableImpl interaction from TablePartitionId to ZonePartitionId
[
https://issues.apache.org/jira/browse/IGNITE-21912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843702#comment-17843702
]
Vladislav Pyatkov commented on IGNITE-21912:
Merged in the feature branch
[88e80dca5f9998ff83872539af09e1d70604ce12|https://github.com/gridgain/apache-ignite-3/commit/88e80dca5f9998ff83872539af09e1d70604ce12]
> Change API usage of Placement driver for InternalTableImpl interaction from
> TablePartitionId to ZonePartitionId
> ---
>
> Key: IGNITE-21912
> URL: https://issues.apache.org/jira/browse/IGNITE-21912
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
>
> In https://issues.apache.org/jira/browse/IGNITE-21858 we have agreed to
> decompose original task to several subtasks.
> In this ticket we need to use previously created decorator for Placement
> Driver from https://issues.apache.org/jira/browse/IGNITE-21911 for all places
> where PD was used in {{InternalTableImpl}} and other places connected to
> {{InternalTableImpl}} that are described in the spreadsheet from
> https://issues.apache.org/jira/browse/IGNITE-21858. Also zone id must be
> propagated to {{InternalTableImpl}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22171) Sql. Row cast fails with NPE.
Evgeny Stanilovsky created IGNITE-22171:
---
Summary: Sql. Row cast fails with NPE.
Key: IGNITE-22171
URL: https://issues.apache.org/jira/browse/IGNITE-22171
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 3.0.0-beta1
Reporter: Evgeny Stanilovsky
{noformat}
SELECT * FROM (VALUES ROW(CAST(ROW(1, 2.0) AS ROW(x BIGINT, y DOUBLE;
{noformat}
{noformat}
Caused by: java.lang.NullPointerException: SqlTypeFamily for RecordType(BIGINT
X, DOUBLE Y)
at java.base/java.util.Objects.requireNonNull(Objects.java:349)
at
org.apache.ignite.internal.sql.engine.exec.exp.RexToLixTranslator.scaleIntervalToNumber(RexToLixTranslator.java:1055)
at
org.apache.ignite.internal.sql.engine.exec.exp.RexToLixTranslator.translateCast(RexToLixTranslator.java:689)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21295) Public Java API for manual raft group configuration update
[ https://issues.apache.org/jira/browse/IGNITE-21295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Shergalis updated IGNITE-21295: --- Description: Implement public API for IGNITE-21284 Collocation is not finished yet, so we have to specify table for the update. In target state user will specify only zone and partition ids was:Implement public API for IGNITE-21284 > Public Java API for manual raft group configuration update > -- > > Key: IGNITE-21295 > URL: https://issues.apache.org/jira/browse/IGNITE-21295 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Philipp Shergalis >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Implement public API for IGNITE-21284 > > Collocation is not finished yet, so we have to specify table for the update. > In target state user will specify only zone and partition ids -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-22169) RocksDb: NPE on index creation
[
https://issues.apache.org/jira/browse/IGNITE-22169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Khitrin resolved IGNITE-22169.
-
Resolution: Invalid
> RocksDb: NPE on index creation
> --
>
> Key: IGNITE-22169
> URL: https://issues.apache.org/jira/browse/IGNITE-22169
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 3.0.0-beta2
>Reporter: Andrey Khitrin
>Assignee: Kirill Tkalenko
>Priority: Blocker
> Labels: 3.0.0, ignite-3, rocksdb
>
> Steps to reproduce:
> 1. Start a single 1-node cluster of AI3
> 2. Create a table in RocksDB storage:
> {code:sql}
> create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
> create table table_8214(id INTEGER not null, int_field_1 INTEGER not null,
> str_field_1 VARCHAR(50) not null, primary key (id)) with
> PRIMARY_ZONE='ROCKSDB';
> {code}
> 3. Try to create an index on this table:
> {code:sql}
> create index temp on table_8214 using SORTED (int_field_1);
> {code}
> Expected result: an index is created successfully (the same actions work on
> ai3persist).
> Actual result: index not created, no response from server to client (query
> hangs), NPE in AI3 log:
> {code}
> 2024-05-06 05:02:51:943 +
> [WARNING][%IndexTests_cluster_0%tableManager-io-0][CatalogManagerImpl] Failed
> to apply catalog update.
> java.util.concurrent.CompletionException: java.lang.NullPointerException:
> Cannot invoke "Object.hashCode()" because "pk" is null
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:674)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:662)
> at
> java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2168)
> at
> org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:693)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$startAsync$2(TableManager.java:614)
> at
> org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:91)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:562)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:529)
> at
> org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:314)
> at
> org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150)
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.lang.NullPointerException: Cannot invoke "Object.hashCode()"
> because "pk" is null
> at
> java.base/java.util.ImmutableCollections$MapN.probe(ImmutableCollections.java:1321)
> at
> java.base/java.util.ImmutableCollections$MapN.get(ImmutableCollections.java:1235)
> at
> org.apache.ignite.internal.storage.DataStorageManager.engineByStorageProfile(DataStorageManager.java:91)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableStorage(TableManager.java:1452)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1315)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableLocally$50(TableManager.java:1283)
> at
> org.apache.ignite.internal.util.IgniteUtils.inBusyLockAsync(IgniteUtils.java:890)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1267)
> at
> org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:692)
> ... 14 more
> 2024-05-06 05:02:51:945 +
> [ERROR][%IndexTests_cluster_0%tableManager-io-0][FailureProcessor] Critical
> system error detected. Will be handled accordingly to configured
[jira] [Commented] (IGNITE-22169) RocksDb: NPE on index creation
[
https://issues.apache.org/jira/browse/IGNITE-22169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843698#comment-17843698
]
Andrey Khitrin commented on IGNITE-22169:
-
Caused by a configuration error in `ignite3-tests.conf` (empty profile list):
{code}
storage {
...
profiles=[]
}
{code}
> RocksDb: NPE on index creation
> --
>
> Key: IGNITE-22169
> URL: https://issues.apache.org/jira/browse/IGNITE-22169
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 3.0.0-beta2
>Reporter: Andrey Khitrin
>Assignee: Kirill Tkalenko
>Priority: Blocker
> Labels: 3.0.0, ignite-3, rocksdb
>
> Steps to reproduce:
> 1. Start a single 1-node cluster of AI3
> 2. Create a table in RocksDB storage:
> {code:sql}
> create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
> create table table_8214(id INTEGER not null, int_field_1 INTEGER not null,
> str_field_1 VARCHAR(50) not null, primary key (id)) with
> PRIMARY_ZONE='ROCKSDB';
> {code}
> 3. Try to create an index on this table:
> {code:sql}
> create index temp on table_8214 using SORTED (int_field_1);
> {code}
> Expected result: an index is created successfully (the same actions work on
> ai3persist).
> Actual result: index not created, no response from server to client (query
> hangs), NPE in AI3 log:
> {code}
> 2024-05-06 05:02:51:943 +
> [WARNING][%IndexTests_cluster_0%tableManager-io-0][CatalogManagerImpl] Failed
> to apply catalog update.
> java.util.concurrent.CompletionException: java.lang.NullPointerException:
> Cannot invoke "Object.hashCode()" because "pk" is null
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:674)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:662)
> at
> java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2168)
> at
> org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:693)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$startAsync$2(TableManager.java:614)
> at
> org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:91)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:562)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:529)
> at
> org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:314)
> at
> org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150)
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.lang.NullPointerException: Cannot invoke "Object.hashCode()"
> because "pk" is null
> at
> java.base/java.util.ImmutableCollections$MapN.probe(ImmutableCollections.java:1321)
> at
> java.base/java.util.ImmutableCollections$MapN.get(ImmutableCollections.java:1235)
> at
> org.apache.ignite.internal.storage.DataStorageManager.engineByStorageProfile(DataStorageManager.java:91)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableStorage(TableManager.java:1452)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1315)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableLocally$50(TableManager.java:1283)
> at
> org.apache.ignite.internal.util.IgniteUtils.inBusyLockAsync(IgniteUtils.java:890)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1267)
> at
> org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:692)
> ... 14 more
> 2024-05-06 05:02:51:945 +
>
[jira] [Updated] (IGNITE-22168) Fix fieldsCount in TcpCommunication messages
[ https://issues.apache.org/jira/browse/IGNITE-22168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-22168: --- Attachment: IGNITE-22168.patch > Fix fieldsCount in TcpCommunication messages > > > Key: IGNITE-22168 > URL: https://issues.apache.org/jira/browse/IGNITE-22168 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Major > Labels: ise > Attachments: IGNITE-22168.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22169) RocksDb: NPE on index creation
[
https://issues.apache.org/jira/browse/IGNITE-22169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Khitrin updated IGNITE-22169:
Description:
Steps to reproduce:
1. Start a single 1-node cluster of AI3
2. Create a table in RocksDB storage:
{code:sql}
create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
create table table_8214(id INTEGER not null, int_field_1 INTEGER not null,
str_field_1 VARCHAR(50) not null, primary key (id)) with PRIMARY_ZONE='ROCKSDB';
{code}
3. Try to create an index on this table:
{code:sql}
create index temp on table_8214 using SORTED (int_field_1);
{code}
Expected result: an index is created successfully (the same actions work on
ai3persist).
Actual result: index not created, no response from server to client (query
hangs), NPE in AI3 log:
{code}
2024-05-06 05:02:51:943 +
[WARNING][%IndexTests_cluster_0%tableManager-io-0][CatalogManagerImpl] Failed
to apply catalog update.
java.util.concurrent.CompletionException: java.lang.NullPointerException:
Cannot invoke "Object.hashCode()" because "pk" is null
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:674)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:662)
at
java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2168)
at
org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:693)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$startAsync$2(TableManager.java:614)
at
org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
at
org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:91)
at
org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:562)
at
org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:529)
at
org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:314)
at
org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
at
org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
at
org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
at
java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150)
at
java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.lang.NullPointerException: Cannot invoke "Object.hashCode()"
because "pk" is null
at
java.base/java.util.ImmutableCollections$MapN.probe(ImmutableCollections.java:1321)
at
java.base/java.util.ImmutableCollections$MapN.get(ImmutableCollections.java:1235)
at
org.apache.ignite.internal.storage.DataStorageManager.engineByStorageProfile(DataStorageManager.java:91)
at
org.apache.ignite.internal.table.distributed.TableManager.createTableStorage(TableManager.java:1452)
at
org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1315)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableLocally$50(TableManager.java:1283)
at
org.apache.ignite.internal.util.IgniteUtils.inBusyLockAsync(IgniteUtils.java:890)
at
org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1267)
at
org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:692)
... 14 more
2024-05-06 05:02:51:945 +
[ERROR][%IndexTests_cluster_0%tableManager-io-0][FailureProcessor] Critical
system error detected. Will be handled accordingly to configured handler
[hnd=NoOpFailureHandler [], failureCtx=FailureContext [type=CRITICAL_ERROR,
err=java.lang.NullPointerException: Cannot invoke "Object.hashCode()" because
"pk" is null]]
java.lang.NullPointerException: Cannot invoke "Object.hashCode()" because "pk"
is null
at
java.base/java.util.ImmutableCollections$MapN.probe(ImmutableCollections.java:1321)
at
java.base/java.util.ImmutableCollections$MapN.get(ImmutableCollections.java:1235)
at
org.apache.ignite.internal.storage.DataStorageManager.engineByStorageProfile(DataStorageManager.java:91)
[jira] [Updated] (IGNITE-22170) Destroy CMG Raft group storages on init cancellation
[ https://issues.apache.org/jira/browse/IGNITE-22170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-22170: --- Description: ClusterManagementGroupManager#destroyCmg() does not close/destroy storages (Raft meta, log, snapshots) left after the destroyed CMG Raft group. It should destroy them. > Destroy CMG Raft group storages on init cancellation > > > Key: IGNITE-22170 > URL: https://issues.apache.org/jira/browse/IGNITE-22170 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > ClusterManagementGroupManager#destroyCmg() does not close/destroy storages > (Raft meta, log, snapshots) left after the destroyed CMG Raft group. It > should destroy them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22170) Destroy CMG Raft group storages on init cancellation
Roman Puchkovskiy created IGNITE-22170: -- Summary: Destroy CMG Raft group storages on init cancellation Key: IGNITE-22170 URL: https://issues.apache.org/jira/browse/IGNITE-22170 Project: Ignite Issue Type: Improvement Reporter: Roman Puchkovskiy Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22169) RocksDb: NPE on index creation
[
https://issues.apache.org/jira/browse/IGNITE-22169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-22169:
-
Summary: RocksDb: NPE on index creation (was: RocbsRB: NPE on index
creation)
> RocksDb: NPE on index creation
> --
>
> Key: IGNITE-22169
> URL: https://issues.apache.org/jira/browse/IGNITE-22169
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 3.0.0-beta2
>Reporter: Andrey Khitrin
>Assignee: Kirill Tkalenko
>Priority: Blocker
> Labels: 3.0.0, ignite-3, rocksdb
>
> Steps to reproduce:
> 1. Start a single 1-node cluster of AI3
> 2. Create a table in RocksDB storage:
> {code:sql}
> create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
> create table table_8214(id INTEGER not null, int_field_1 INTEGER not null,
> str_field_1 VARCHAR(50) not null, primary key (id)) with
> PRIMARY_ZONE='ROCKSDB';
> {code}
> 3. Try to create an index on this table:
> {code:sql}
> create index temp on table_8214 using SORTED (int_field_1);
> {code}
> Expected result: an index is created successfully (the same actions work on
> ai3persist).
> Actual result: index not created, no response from server to client (query
> hangs), NPE in AI3 log:
> {code}
> 2024-05-06 12:11:17:567 +0500
> [INFO][%DeleteFromWhereTests_cluster_0%metastorage-watch-executor-3][IndexManager]
> Creating local index: name=TABLE_8214_PK, id=9, tableId=8, token=23
> 2024-05-06 12:11:17:585 +0500
> [INFO][%DeleteFromWhereTests_cluster_0%metastorage-watch-executor-3][TableManager]
> Assignments calculated from data nodes [table=TABLE_8214, tableId=8,
> assignments=
> [0=[],1=[],2=[],3=[],4=[],5=[],6=[],7=[],8=[],9=[],10=[],11=[],12=[],13=[],14=[],15=[],16=[],17=[],18=[],19=[],20=[],21=[],22=[],23=[],24=[]],
> revision=23]
> 2024-05-06 12:11:17:592 +0500
> [WARNING][%DeleteFromWhereTests_cluster_0%tableManager-io-0][CatalogManagerImpl]
> Failed to apply catalog update.
> java.util.concurrent.CompletionException: java.lang.NullPointerException
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:670)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
> at
> java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
> at
> org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:689)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$start$2(TableManager.java:613)
> at
> org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:83)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:534)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:501)
> at
> org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:308)
> at
> org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.NullPointerException
> at
> java.base/java.util.ImmutableCollections$MapN.probe(ImmutableCollections.java:956)
> at
> java.base/java.util.ImmutableCollections$MapN.get(ImmutableCollections.java:876)
> at
> org.apache.ignite.internal.storage.DataStorageManager.engineByStorageProfile(DataStorageManager.java:84)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableStorage(TableManager.java:1450)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1313)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableLocally$48(TableManager.java:1281)
> at
>
[jira] [Updated] (IGNITE-22169) RocbsRB: NPE on index creation
[
https://issues.apache.org/jira/browse/IGNITE-22169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-22169:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> RocbsRB: NPE on index creation
> --
>
> Key: IGNITE-22169
> URL: https://issues.apache.org/jira/browse/IGNITE-22169
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 3.0.0-beta2
>Reporter: Andrey Khitrin
>Assignee: Kirill Tkalenko
>Priority: Blocker
> Labels: 3.0.0, ignite-3, rocksdb
>
> Steps to reproduce:
> 1. Start a single 1-node cluster of AI3
> 2. Create a table in RocksDB storage:
> {code:sql}
> create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
> create table table_8214(id INTEGER not null, int_field_1 INTEGER not null,
> str_field_1 VARCHAR(50) not null, primary key (id)) with
> PRIMARY_ZONE='ROCKSDB';
> {code}
> 3. Try to create an index on this table:
> {code:sql}
> create index temp on table_8214 using SORTED (int_field_1);
> {code}
> Expected result: an index is created successfully (the same actions work on
> ai3persist).
> Actual result: index not created, no response from server to client (query
> hangs), NPE in AI3 log:
> {code}
> 2024-05-06 12:11:17:567 +0500
> [INFO][%DeleteFromWhereTests_cluster_0%metastorage-watch-executor-3][IndexManager]
> Creating local index: name=TABLE_8214_PK, id=9, tableId=8, token=23
> 2024-05-06 12:11:17:585 +0500
> [INFO][%DeleteFromWhereTests_cluster_0%metastorage-watch-executor-3][TableManager]
> Assignments calculated from data nodes [table=TABLE_8214, tableId=8,
> assignments=
> [0=[],1=[],2=[],3=[],4=[],5=[],6=[],7=[],8=[],9=[],10=[],11=[],12=[],13=[],14=[],15=[],16=[],17=[],18=[],19=[],20=[],21=[],22=[],23=[],24=[]],
> revision=23]
> 2024-05-06 12:11:17:592 +0500
> [WARNING][%DeleteFromWhereTests_cluster_0%tableManager-io-0][CatalogManagerImpl]
> Failed to apply catalog update.
> java.util.concurrent.CompletionException: java.lang.NullPointerException
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:670)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
> at
> java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
> at
> org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:689)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$start$2(TableManager.java:613)
> at
> org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:83)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:534)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:501)
> at
> org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:308)
> at
> org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.NullPointerException
> at
> java.base/java.util.ImmutableCollections$MapN.probe(ImmutableCollections.java:956)
> at
> java.base/java.util.ImmutableCollections$MapN.get(ImmutableCollections.java:876)
> at
> org.apache.ignite.internal.storage.DataStorageManager.engineByStorageProfile(DataStorageManager.java:84)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableStorage(TableManager.java:1450)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1313)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableLocally$48(TableManager.java:1281)
> at
>
[jira] [Assigned] (IGNITE-22169) RocbsRB: NPE on index creation
[
https://issues.apache.org/jira/browse/IGNITE-22169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko reassigned IGNITE-22169:
Assignee: Kirill Tkalenko
> RocbsRB: NPE on index creation
> --
>
> Key: IGNITE-22169
> URL: https://issues.apache.org/jira/browse/IGNITE-22169
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 3.0.0-beta2
>Reporter: Andrey Khitrin
>Assignee: Kirill Tkalenko
>Priority: Blocker
> Labels: 3.0.0, rocksdb
>
> Steps to reproduce:
> 1. Start a single 1-node cluster of AI3
> 2. Create a table in RocksDB storage:
> {code:sql}
> create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
> create table table_8214(id INTEGER not null, int_field_1 INTEGER not null,
> str_field_1 VARCHAR(50) not null, primary key (id)) with
> PRIMARY_ZONE='ROCKSDB';
> {code}
> 3. Try to create an index on this table:
> {code:sql}
> create index temp on table_8214 using SORTED (int_field_1);
> {code}
> Expected result: an index is created successfully (the same actions work on
> ai3persist).
> Actual result: index not created, no response from server to client (query
> hangs), NPE in AI3 log:
> {code}
> 2024-05-06 12:11:17:567 +0500
> [INFO][%DeleteFromWhereTests_cluster_0%metastorage-watch-executor-3][IndexManager]
> Creating local index: name=TABLE_8214_PK, id=9, tableId=8, token=23
> 2024-05-06 12:11:17:585 +0500
> [INFO][%DeleteFromWhereTests_cluster_0%metastorage-watch-executor-3][TableManager]
> Assignments calculated from data nodes [table=TABLE_8214, tableId=8,
> assignments=
> [0=[],1=[],2=[],3=[],4=[],5=[],6=[],7=[],8=[],9=[],10=[],11=[],12=[],13=[],14=[],15=[],16=[],17=[],18=[],19=[],20=[],21=[],22=[],23=[],24=[]],
> revision=23]
> 2024-05-06 12:11:17:592 +0500
> [WARNING][%DeleteFromWhereTests_cluster_0%tableManager-io-0][CatalogManagerImpl]
> Failed to apply catalog update.
> java.util.concurrent.CompletionException: java.lang.NullPointerException
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:670)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
> at
> java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
> at
> org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:689)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$start$2(TableManager.java:613)
> at
> org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:83)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:534)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:501)
> at
> org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:308)
> at
> org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.NullPointerException
> at
> java.base/java.util.ImmutableCollections$MapN.probe(ImmutableCollections.java:956)
> at
> java.base/java.util.ImmutableCollections$MapN.get(ImmutableCollections.java:876)
> at
> org.apache.ignite.internal.storage.DataStorageManager.engineByStorageProfile(DataStorageManager.java:84)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableStorage(TableManager.java:1450)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1313)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableLocally$48(TableManager.java:1281)
> at
>
[jira] [Updated] (IGNITE-22169) RocbsRB: NPE on index creation
[
https://issues.apache.org/jira/browse/IGNITE-22169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-22169:
-
Labels: 3.0.0 ignite-3 rocksdb (was: 3.0.0 rocksdb)
> RocbsRB: NPE on index creation
> --
>
> Key: IGNITE-22169
> URL: https://issues.apache.org/jira/browse/IGNITE-22169
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 3.0.0-beta2
>Reporter: Andrey Khitrin
>Assignee: Kirill Tkalenko
>Priority: Blocker
> Labels: 3.0.0, ignite-3, rocksdb
>
> Steps to reproduce:
> 1. Start a single 1-node cluster of AI3
> 2. Create a table in RocksDB storage:
> {code:sql}
> create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
> create table table_8214(id INTEGER not null, int_field_1 INTEGER not null,
> str_field_1 VARCHAR(50) not null, primary key (id)) with
> PRIMARY_ZONE='ROCKSDB';
> {code}
> 3. Try to create an index on this table:
> {code:sql}
> create index temp on table_8214 using SORTED (int_field_1);
> {code}
> Expected result: an index is created successfully (the same actions work on
> ai3persist).
> Actual result: index not created, no response from server to client (query
> hangs), NPE in AI3 log:
> {code}
> 2024-05-06 12:11:17:567 +0500
> [INFO][%DeleteFromWhereTests_cluster_0%metastorage-watch-executor-3][IndexManager]
> Creating local index: name=TABLE_8214_PK, id=9, tableId=8, token=23
> 2024-05-06 12:11:17:585 +0500
> [INFO][%DeleteFromWhereTests_cluster_0%metastorage-watch-executor-3][TableManager]
> Assignments calculated from data nodes [table=TABLE_8214, tableId=8,
> assignments=
> [0=[],1=[],2=[],3=[],4=[],5=[],6=[],7=[],8=[],9=[],10=[],11=[],12=[],13=[],14=[],15=[],16=[],17=[],18=[],19=[],20=[],21=[],22=[],23=[],24=[]],
> revision=23]
> 2024-05-06 12:11:17:592 +0500
> [WARNING][%DeleteFromWhereTests_cluster_0%tableManager-io-0][CatalogManagerImpl]
> Failed to apply catalog update.
> java.util.concurrent.CompletionException: java.lang.NullPointerException
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:670)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
> at
> java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
> at
> org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:689)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$start$2(TableManager.java:613)
> at
> org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:83)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:534)
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:501)
> at
> org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:308)
> at
> org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.NullPointerException
> at
> java.base/java.util.ImmutableCollections$MapN.probe(ImmutableCollections.java:956)
> at
> java.base/java.util.ImmutableCollections$MapN.get(ImmutableCollections.java:876)
> at
> org.apache.ignite.internal.storage.DataStorageManager.engineByStorageProfile(DataStorageManager.java:84)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableStorage(TableManager.java:1450)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1313)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableLocally$48(TableManager.java:1281)
> at
>
[jira] [Updated] (IGNITE-22169) RocbsRB: NPE on index creation
[
https://issues.apache.org/jira/browse/IGNITE-22169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Khitrin updated IGNITE-22169:
Description:
Steps to reproduce:
1. Start a single 1-node cluster of AI3
2. Create a table in RocksDB storage:
{code:sql}
create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
create table table_8214(id INTEGER not null, int_field_1 INTEGER not null,
str_field_1 VARCHAR(50) not null, primary key (id)) with PRIMARY_ZONE='ROCKSDB';
{code}
3. Try to create an index on this table:
{code:sql}
create index temp on table_8214 using SORTED (int_field_1);
{code}
Expected result: an index is created successfully (the same actions work on
ai3persist).
Actual result: index not created, no response from server to client (query
hangs), NPE in AI3 log:
{code}
2024-05-06 12:11:17:567 +0500
[INFO][%DeleteFromWhereTests_cluster_0%metastorage-watch-executor-3][IndexManager]
Creating local index: name=TABLE_8214_PK, id=9, tableId=8, token=23
2024-05-06 12:11:17:585 +0500
[INFO][%DeleteFromWhereTests_cluster_0%metastorage-watch-executor-3][TableManager]
Assignments calculated from data nodes [table=TABLE_8214, tableId=8,
assignments=
[0=[],1=[],2=[],3=[],4=[],5=[],6=[],7=[],8=[],9=[],10=[],11=[],12=[],13=[],14=[],15=[],16=[],17=[],18=[],19=[],20=[],21=[],22=[],23=[],24=[]],
revision=23]
2024-05-06 12:11:17:592 +0500
[WARNING][%DeleteFromWhereTests_cluster_0%tableManager-io-0][CatalogManagerImpl]
Failed to apply catalog update.
java.util.concurrent.CompletionException: java.lang.NullPointerException
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:670)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
at
java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
at
org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:689)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$start$2(TableManager.java:613)
at
org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
at
org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:83)
at
org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:534)
at
org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:501)
at
org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:308)
at
org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
at
org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
at
org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
at
java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
at
java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.NullPointerException
at
java.base/java.util.ImmutableCollections$MapN.probe(ImmutableCollections.java:956)
at
java.base/java.util.ImmutableCollections$MapN.get(ImmutableCollections.java:876)
at
org.apache.ignite.internal.storage.DataStorageManager.engineByStorageProfile(DataStorageManager.java:84)
at
org.apache.ignite.internal.table.distributed.TableManager.createTableStorage(TableManager.java:1450)
at
org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1313)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableLocally$48(TableManager.java:1281)
at
org.apache.ignite.internal.util.IgniteUtils.inBusyLockAsync(IgniteUtils.java:889)
at
org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1265)
at
org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:688)
... 14 more
2024-05-06 12:11:17:592 +0500
[INFO][%DeleteFromWhereTests_cluster_0%JRaft-FSMCaller-Disruptor-metastorage_stripe_0-0][TableManager]
Assignments calculated from data nodes are successfully written to meta
storage [tableId=8, assignments=
[jira] [Created] (IGNITE-22169) RocbsRB: NPE on index creation
Andrey Khitrin created IGNITE-22169:
---
Summary: RocbsRB: NPE on index creation
Key: IGNITE-22169
URL: https://issues.apache.org/jira/browse/IGNITE-22169
Project: Ignite
Issue Type: Bug
Components: persistence
Affects Versions: 3.0.0-beta2
Reporter: Andrey Khitrin
Steps to reproduce:
1. Start a single 1-node cluster of AI3
2. Create a table in RocksDB storage:
{code:sql}
create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
create table table_8214(id INTEGER not null, int_field_1 INTEGER not null,
str_field_1 VARCHAR(50) not null, primary key (id)) with PRIMARY_ZONE='ROCKSDB';
{code}
3. Try to create an index on this table:
{code:sql}
create index temp on table_8214 using SORTED (int_field_1);
{code}
Expected result: an index is created successfully (the same actions work on
ai3persist).
Actual result: index not created, no response from server to client (query
"hangs"), NPE in AI3 log:
{code}
2024-05-06 12:11:17:567 +0500
[INFO][%DeleteFromWhereTests_cluster_0%metastorage-watch-executor-3][IndexManager]
Creating local index: name=TABLE_8214_PK, id=9, tableId=8, token=23
2024-05-06 12:11:17:585 +0500
[INFO][%DeleteFromWhereTests_cluster_0%metastorage-watch-executor-3][TableManager]
Assignments calculated from data nodes [table=TABLE_8214, tableId=8,
assignments=
[0=[],1=[],2=[],3=[],4=[],5=[],6=[],7=[],8=[],9=[],10=[],11=[],12=[],13=[],14=[],15=[],16=[],17=[],18=[],19=[],20=[],21=[],22=[],23=[],24=[]],
revision=23]
2024-05-06 12:11:17:592 +0500
[WARNING][%DeleteFromWhereTests_cluster_0%tableManager-io-0][CatalogManagerImpl]
Failed to apply catalog update.
java.util.concurrent.CompletionException: java.lang.NullPointerException
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:670)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
at
java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
at
org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:689)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$start$2(TableManager.java:613)
at
org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
at
org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:83)
at
org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:534)
at
org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:501)
at
org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:308)
at
org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
at
org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
at
org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
at
java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
at
java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.NullPointerException
at
java.base/java.util.ImmutableCollections$MapN.probe(ImmutableCollections.java:956)
at
java.base/java.util.ImmutableCollections$MapN.get(ImmutableCollections.java:876)
at
org.apache.ignite.internal.storage.DataStorageManager.engineByStorageProfile(DataStorageManager.java:84)
at
org.apache.ignite.internal.table.distributed.TableManager.createTableStorage(TableManager.java:1450)
at
org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1313)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableLocally$48(TableManager.java:1281)
at
org.apache.ignite.internal.util.IgniteUtils.inBusyLockAsync(IgniteUtils.java:889)
at
org.apache.ignite.internal.table.distributed.TableManager.createTableLocally(TableManager.java:1265)
at
org.apache.ignite.internal.table.distributed.TableManager.onTableCreate(TableManager.java:688)
... 14 more
2024-05-06 12:11:17:592 +0500
[INFO][%DeleteFromWhereTests_cluster_0%JRaft-FSMCaller-Disruptor-metastorage_stripe_0-0][TableManager]
[jira] [Created] (IGNITE-22168) Fix fieldsCount in TcpCommunication messages
Ilya Shishkov created IGNITE-22168: -- Summary: Fix fieldsCount in TcpCommunication messages Key: IGNITE-22168 URL: https://issues.apache.org/jira/browse/IGNITE-22168 Project: Ignite Issue Type: Bug Reporter: Ilya Shishkov Assignee: Ilya Shishkov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22167) RocksDB: cannot create a default zone just twice
[
https://issues.apache.org/jira/browse/IGNITE-22167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Khitrin updated IGNITE-22167:
Priority: Critical (was: Major)
> RocksDB: cannot create a default zone just twice
>
>
> Key: IGNITE-22167
> URL: https://issues.apache.org/jira/browse/IGNITE-22167
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 3.0.0-beta2
>Reporter: Andrey Khitrin
>Priority: Critical
> Labels: 3.0.0, rocksdb
>
> Steps to reproduce:
> # Start AI3 cluster of 1 node
> # Run few simple SQL queries:
> {code:sql}
> create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
> create table ... with PRIMARY_ZONE='ROCKSDB';
> insert into table ... values(); -- probably, unneeded
> create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
> -- absolutely the same query as the 1st one
> {code}
> Expected behavior: the 2nd "create zone" query must be executed successfully
> (because a zone is already created).
> Actual behavior: the 2nd "create zone" query simply {*}hangs{*}.
> Found on commit 654a11a4a00919ce2b3ff4ca0e59e83377124dea (recent AI3 at the
> time).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-21977) Extend test coverage for SQL F661(Simple tables)
[ https://issues.apache.org/jira/browse/IGNITE-21977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky reassigned IGNITE-21977: --- Assignee: Evgeny Stanilovsky > Extend test coverage for SQL F661(Simple tables) > > > Key: IGNITE-21977 > URL: https://issues.apache.org/jira/browse/IGNITE-21977 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > > Test coverage for SQL F661(Simple tables) is poor. > Let's increase the test coverage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22167) RocksDB: cannot create a default zone just twice
Andrey Khitrin created IGNITE-22167:
---
Summary: RocksDB: cannot create a default zone just twice
Key: IGNITE-22167
URL: https://issues.apache.org/jira/browse/IGNITE-22167
Project: Ignite
Issue Type: Bug
Components: persistence
Affects Versions: 3.0.0-beta2
Reporter: Andrey Khitrin
Steps to reproduce:
# Start AI3 cluster of 1 node
# Run few simple SQL queries:
{code:sql}
create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb';
create table ... with PRIMARY_ZONE='ROCKSDB';
insert into table ... values(); -- probably, unneeded
create zone if not exists "ROCKSDB" with storage_profiles='default_rocksdb'; --
absolutely the same query as the 1st one
{code}
Expected behavior: the 2nd "create zone" query must be executed successfully
(because a zone is already created).
Actual behavior: the 2nd "create zone" query simply {*}hangs{*}.
Found on commit 654a11a4a00919ce2b3ff4ca0e59e83377124dea (recent AI3 at the
time).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
