[jira] [Commented] (IGNITE-20497) Fix broken logger settings
[ https://issues.apache.org/jira/browse/IGNITE-20497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769417#comment-17769417 ] Kirill Tkalenko commented on IGNITE-20497: -- Looks good. > Fix broken logger settings > -- > > Key: IGNITE-20497 > URL: https://issues.apache.org/jira/browse/IGNITE-20497 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > I broke logger formatter in https://issues.apache.org/jira/browse/IGNITE-20480 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20497) Fix broken logger settings
[ https://issues.apache.org/jira/browse/IGNITE-20497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-20497: - Reviewer: Kirill Tkalenko > Fix broken logger settings > -- > > Key: IGNITE-20497 > URL: https://issues.apache.org/jira/browse/IGNITE-20497 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > I broke logger formatter in https://issues.apache.org/jira/browse/IGNITE-20480 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20500) NullPointerException when restarting node with custom region
[
https://issues.apache.org/jira/browse/IGNITE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-20500:
-
Fix Version/s: 3.0.0-beta2
> NullPointerException when restarting node with custom region
>
>
> Key: IGNITE-20500
> URL: https://issues.apache.org/jira/browse/IGNITE-20500
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Tiago Marques Godinho
>Priority: Major
> Fix For: 3.0.0-beta2
>
> Attachments: assert, full
>
>
> I've encountered this exception when restarting a node with data on a custom
> region:
> {code:java}
> SEVERE: Error starting tables
> ...
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
> at
> org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
> at
> org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
> ... 44 more {code}
>
> Steps to reproduce:
> # Start a cluster from scratch (can be a single node).
> # Initialise the cluster.
> # Update the cluster configurations with a custom region:
> {code:java}
> {"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
> # Create a Distribution Zone on that data region:
> {code:java}
> CREATE ZONE MY_ZONE ENGINE aipersist WITH
> DATAREGION='persistentDataRegionCfg', REPLICAS=1;{code}
> # Shutdown the node using SIGINT
> # Start the node again
> Tested with:
> [d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
> Notes:
> * Added [^full]
> * Added [^assert] when assertions where enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20500) NullPointerException when restarting node with custom region
[
https://issues.apache.org/jira/browse/IGNITE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-20500:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> NullPointerException when restarting node with custom region
>
>
> Key: IGNITE-20500
> URL: https://issues.apache.org/jira/browse/IGNITE-20500
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Tiago Marques Godinho
>Priority: Major
> Attachments: assert, full
>
>
> I've encountered this exception when restarting a node with data on a custom
> region:
> {code:java}
> SEVERE: Error starting tables
> ...
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
> at
> org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
> at
> org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
> ... 44 more {code}
>
> Steps to reproduce:
> # Start a cluster from scratch (can be a single node).
> # Initialise the cluster.
> # Update the cluster configurations with a custom region:
> {code:java}
> {"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
> # Create a Distribution Zone on that data region:
> {code:java}
> CREATE ZONE MY_ZONE ENGINE aipersist WITH
> DATAREGION='persistentDataRegionCfg', REPLICAS=1;{code}
> # Shutdown the node using SIGINT
> # Start the node again
> Tested with:
> [d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
> Notes:
> * Added [^full]
> * Added [^assert] when assertions where enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-20500) NullPointerException when restarting node with custom region
[
https://issues.apache.org/jira/browse/IGNITE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko reassigned IGNITE-20500:
Assignee: Kirill Tkalenko
> NullPointerException when restarting node with custom region
>
>
> Key: IGNITE-20500
> URL: https://issues.apache.org/jira/browse/IGNITE-20500
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Tiago Marques Godinho
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 3.0.0-beta2
>
> Attachments: assert, full
>
>
> I've encountered this exception when restarting a node with data on a custom
> region:
> {code:java}
> SEVERE: Error starting tables
> ...
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
> at
> org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
> at
> org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
> ... 44 more {code}
>
> Steps to reproduce:
> # Start a cluster from scratch (can be a single node).
> # Initialise the cluster.
> # Update the cluster configurations with a custom region:
> {code:java}
> {"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
> # Create a Distribution Zone on that data region:
> {code:java}
> CREATE ZONE MY_ZONE ENGINE aipersist WITH
> DATAREGION='persistentDataRegionCfg', REPLICAS=1;{code}
> # Shutdown the node using SIGINT
> # Start the node again
> Tested with:
> [d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
> Notes:
> * Added [^full]
> * Added [^assert] when assertions where enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20501) Calcite engine. Memory leak in MailboxRegistryImpl#remotes on JOINs
Aleksey Plekhanov created IGNITE-20501:
--
Summary: Calcite engine. Memory leak in
MailboxRegistryImpl#remotes on JOINs
Key: IGNITE-20501
URL: https://issues.apache.org/jira/browse/IGNITE-20501
Project: Ignite
Issue Type: Bug
Reporter: Aleksey Plekhanov
Assignee: Aleksey Plekhanov
When JOIN relational operator is executed, downstream of JOIN can be closed if
only one side of JOIN is already drained (see last lines of
{{MergeJoinNode.InnerJoin#join}}, for example). In this case query can be
prematurely closed, and after this, message for another side of join can arrive
and register new {{Inbox}} (see {{ExchangeServiceImpl#onMessage(UUID,
QueryBatchMessage)}}), that never will be unregistered.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20499) Ability to obtain actual cluster configuration values during startup.
[ https://issues.apache.org/jira/browse/IGNITE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-20499: -- Description: The value of the configuration parameter can be changed during cluster initialization (IgniteImpl#init). System components do not see the actual configuration values at startup (since locally this values is applied later). This can cause confusion when a component reads a default configuration value at startup, which then changes when the distributed configuration is applied on the local node. was: The value of the configuration parameter can be changed during cluster initialization (IgniteImpl#init). At the moment, system components do not see the actual configuration values at startup (since locally this values is applied later). In the case of reading an immutable config parameter with default value, this can lead to confusion. Since the component at startup will read the default configuration value, which then changes when the distributed configuration is applied on the local node. > Ability to obtain actual cluster configuration values during startup. > - > > Key: IGNITE-20499 > URL: https://issues.apache.org/jira/browse/IGNITE-20499 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Pereslegin >Priority: Major > Labels: configuration, ignite-3 > > The value of the configuration parameter can be changed during cluster > initialization (IgniteImpl#init). System components do not see the actual > configuration values at startup (since locally this values is applied later). > This can cause confusion when a component reads a default configuration value > at startup, which then changes when the distributed configuration is applied > on the local node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-20493) Ignite website shows downloading version 2.11 as latest version
[ https://issues.apache.org/jira/browse/IGNITE-20493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-20493. -- > Ignite website shows downloading version 2.11 as latest version > --- > > Key: IGNITE-20493 > URL: https://issues.apache.org/jira/browse/IGNITE-20493 > Project: Ignite > Issue Type: Task >Reporter: Erlan Aytpaev >Assignee: Erlan Aytpaev >Priority: Major > > !https://lists.apache.org/api/email.lua?attachment=true=1c01nt4nol691fxz5k71zpwd5r60d0ql=08cc11e094cb73962012551428c510b4c62b6064ee6e2e07737241c552039874! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20500) NullPointerException when restarting node with custom region
[
https://issues.apache.org/jira/browse/IGNITE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tiago Marques Godinho updated IGNITE-20500:
---
Description:
I've encountered this exception when restarting a node with data on a custom
region:
{code:java}
SEVERE: Error starting tables
...
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
at
org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
at
org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
... 44 more {code}
Steps to reproduce:
# Start a cluster from scratch (can be a single node).
# Initialise the cluster.
# Update the cluster configurations with a custom region:
{code:java}
{"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
# Create a Distribution Zone on that data region:
{code:java}
CREATE ZONE MY_ZONE ENGINE aipersist WITH DATAREGION='persistentDataRegionCfg',
REPLICAS=1;{code}
# Shutdown the node using SIGINT
# Start the node again
Tested with:
[d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
Notes:
* Added full log
* Added error when assertions where enabled.
was:
I've encountered this exception when restarting a node with data on a custom
region:
{code:java}
SEVERE: Error starting tables
...
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
at
org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
at
org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
... 44 more {code}
Steps to reproduce:
# Start a cluster from scratch (can be a single node).
# Initialise the cluster.
# Update the cluster configurations with a custom region:
{code:java}
{"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
# Create a Distribution Zone on that data region:
{code:java}
CREATE ZONE MY_ZONE ENGINE aipersist WITH DATAREGION='persistentDataRegionCfg',
REPLICAS=1;{code}
# Shutdown the node using SIGINT
# Start the node again
Tested with:
[d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
> NullPointerException when restarting node with custom region
>
>
> Key: IGNITE-20500
> URL: https://issues.apache.org/jira/browse/IGNITE-20500
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Tiago Marques Godinho
>Priority: Major
> Attachments: assert, full
>
>
> I've encountered this exception when restarting a node with data on a custom
> region:
> {code:java}
> SEVERE: Error starting tables
> ...
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
> at
>
[jira] [Updated] (IGNITE-20500) NullPointerException when restarting node with custom region
[
https://issues.apache.org/jira/browse/IGNITE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tiago Marques Godinho updated IGNITE-20500:
---
Description:
I've encountered this exception when restarting a node with data on a custom
region:
{code:java}
SEVERE: Error starting tables
...
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
at
org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
at
org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
... 44 more {code}
Steps to reproduce:
# Start a cluster from scratch (can be a single node).
# Initialise the cluster.
# Update the cluster configurations with a custom region:
{code:java}
{"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
# Create a Distribution Zone on that data region:
{code:java}
CREATE ZONE MY_ZONE ENGINE aipersist WITH DATAREGION='persistentDataRegionCfg',
REPLICAS=1;{code}
# Shutdown the node using SIGINT
# Start the node again
Tested with:
[d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
Notes:
* Added [^full]
* Added [^assert] when assertions where enabled.
was:
I've encountered this exception when restarting a node with data on a custom
region:
{code:java}
SEVERE: Error starting tables
...
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
at
org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
at
org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
... 44 more {code}
Steps to reproduce:
# Start a cluster from scratch (can be a single node).
# Initialise the cluster.
# Update the cluster configurations with a custom region:
{code:java}
{"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
# Create a Distribution Zone on that data region:
{code:java}
CREATE ZONE MY_ZONE ENGINE aipersist WITH DATAREGION='persistentDataRegionCfg',
REPLICAS=1;{code}
# Shutdown the node using SIGINT
# Start the node again
Tested with:
[d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
Notes:
* Added [^full]
* Added error when assertions where enabled.
> NullPointerException when restarting node with custom region
>
>
> Key: IGNITE-20500
> URL: https://issues.apache.org/jira/browse/IGNITE-20500
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Tiago Marques Godinho
>Priority: Major
> Attachments: assert, full
>
>
> I've encountered this exception when restarting a node with data on a custom
> region:
> {code:java}
> SEVERE: Error starting tables
> ...
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
> at
>
[jira] [Updated] (IGNITE-20500) NullPointerException when restarting node with custom region
[
https://issues.apache.org/jira/browse/IGNITE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tiago Marques Godinho updated IGNITE-20500:
---
Description:
I've encountered this exception when restarting a node with data on a custom
region:
{code:java}
SEVERE: Error starting tables
...
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
at
org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
at
org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
... 44 more {code}
Steps to reproduce:
# Start a cluster from scratch (can be a single node).
# Initialise the cluster.
# Update the cluster configurations with a custom region:
{code:java}
{"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
# Create a Distribution Zone on that data region:
{code:java}
CREATE ZONE MY_ZONE ENGINE aipersist WITH DATAREGION='persistentDataRegionCfg',
REPLICAS=1;{code}
# Shutdown the node using SIGINT
# Start the node again
Tested with:
[d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
Notes:
* Added [^full]
* Added error when assertions where enabled.
was:
I've encountered this exception when restarting a node with data on a custom
region:
{code:java}
SEVERE: Error starting tables
...
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
at
org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
at
org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
... 44 more {code}
Steps to reproduce:
# Start a cluster from scratch (can be a single node).
# Initialise the cluster.
# Update the cluster configurations with a custom region:
{code:java}
{"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
# Create a Distribution Zone on that data region:
{code:java}
CREATE ZONE MY_ZONE ENGINE aipersist WITH DATAREGION='persistentDataRegionCfg',
REPLICAS=1;{code}
# Shutdown the node using SIGINT
# Start the node again
Tested with:
[d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
Notes:
* Added full log
* Added error when assertions where enabled.
> NullPointerException when restarting node with custom region
>
>
> Key: IGNITE-20500
> URL: https://issues.apache.org/jira/browse/IGNITE-20500
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Tiago Marques Godinho
>Priority: Major
> Attachments: assert, full
>
>
> I've encountered this exception when restarting a node with data on a custom
> region:
> {code:java}
> SEVERE: Error starting tables
> ...
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
> at
>
[jira] [Updated] (IGNITE-20500) NullPointerException when restarting node with custom region
[
https://issues.apache.org/jira/browse/IGNITE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tiago Marques Godinho updated IGNITE-20500:
---
Attachment: assert
> NullPointerException when restarting node with custom region
>
>
> Key: IGNITE-20500
> URL: https://issues.apache.org/jira/browse/IGNITE-20500
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Tiago Marques Godinho
>Priority: Major
> Attachments: assert, full
>
>
> I've encountered this exception when restarting a node with data on a custom
> region:
> {code:java}
> SEVERE: Error starting tables
> ...
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
> at
> org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
> at
> org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
> ... 44 more {code}
>
> Steps to reproduce:
> # Start a cluster from scratch (can be a single node).
> # Initialise the cluster.
> # Update the cluster configurations with a custom region:
> {code:java}
> {"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
> # Create a Distribution Zone on that data region:
> {code:java}
> CREATE ZONE MY_ZONE ENGINE aipersist WITH
> DATAREGION='persistentDataRegionCfg', REPLICAS=1;{code}
> # Shutdown the node using SIGINT
> # Start the node again
> Tested with:
> [d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20500) NullPointerException when restarting node with custom region
[
https://issues.apache.org/jira/browse/IGNITE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tiago Marques Godinho updated IGNITE-20500:
---
Attachment: full
> NullPointerException when restarting node with custom region
>
>
> Key: IGNITE-20500
> URL: https://issues.apache.org/jira/browse/IGNITE-20500
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Tiago Marques Godinho
>Priority: Major
> Attachments: assert, full
>
>
> I've encountered this exception when restarting a node with data on a custom
> region:
> {code:java}
> SEVERE: Error starting tables
> ...
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
> at
> org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
> at
> org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
> ... 44 more {code}
>
> Steps to reproduce:
> # Start a cluster from scratch (can be a single node).
> # Initialise the cluster.
> # Update the cluster configurations with a custom region:
> {code:java}
> {"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
> # Create a Distribution Zone on that data region:
> {code:java}
> CREATE ZONE MY_ZONE ENGINE aipersist WITH
> DATAREGION='persistentDataRegionCfg', REPLICAS=1;{code}
> # Shutdown the node using SIGINT
> # Start the node again
> Tested with:
> [d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20500) NullPointerException when restarting node with custom region
[
https://issues.apache.org/jira/browse/IGNITE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tiago Marques Godinho updated IGNITE-20500:
---
Summary: NullPointerException when restarting node with custom region
(was: NullPointException when restarting node with custom region)
> NullPointerException when restarting node with custom region
>
>
> Key: IGNITE-20500
> URL: https://issues.apache.org/jira/browse/IGNITE-20500
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Tiago Marques Godinho
>Priority: Major
>
> I've encountered this exception when restarting a node with data on a custom
> region:
> {code:java}
> SEVERE: Error starting tables
> ...
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
> at
> org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
> at
> org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
> at
> org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
> ... 44 more {code}
>
> Steps to reproduce:
> # Start a cluster from scratch (can be a single node).
> # Initialise the cluster.
> # Update the cluster configurations with a custom region:
> {code:java}
> {"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
> # Create a Distribution Zone on that data region:
> {code:java}
> CREATE ZONE MY_ZONE ENGINE aipersist WITH
> DATAREGION='persistentDataRegionCfg', REPLICAS=1;{code}
> # Shutdown the node using SIGINT
> # Start the node again
> Tested with:
> [d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20500) NullPointException when restarting node with custom region
Tiago Marques Godinho created IGNITE-20500:
--
Summary: NullPointException when restarting node with custom region
Key: IGNITE-20500
URL: https://issues.apache.org/jira/browse/IGNITE-20500
Project: Ignite
Issue Type: Bug
Components: general
Reporter: Tiago Marques Godinho
I've encountered this exception when restarting a node with data on a custom
region:
{code:java}
SEVERE: Error starting tables
...
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.ensurePartitionFilePageStoreExists(PersistentPageMemoryTableStorage.java:144)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.getOrCreatePartitionMetaOnCreatePartition(PersistentPageMemoryTableStorage.java:500)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:107)
at
org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage.createMvPartitionStorage(PersistentPageMemoryTableStorage.java:54)
at
org.apache.ignite.internal.storage.pagememory.AbstractPageMemoryTableStorage.lambda$createMvPartition$4(AbstractPageMemoryTableStorage.java:164)
at
org.apache.ignite.internal.storage.util.MvPartitionStorages.lambda$create$1(MvPartitionStorages.java:121)
at
java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
... 44 more {code}
Steps to reproduce:
# Start a cluster from scratch (can be a single node).
# Initialise the cluster.
# Update the cluster configurations with a custom region:
{code:java}
{"aipersist":{"regions":[{"memoryAllocator":{"type":"unsafe"},"name":"persistentDataRegionCfg","replacementMode":"CLOCK","size":6871947673}]}}{code}
# Create a Distribution Zone on that data region:
{code:java}
CREATE ZONE MY_ZONE ENGINE aipersist WITH DATAREGION='persistentDataRegionCfg',
REPLICAS=1;{code}
# Shutdown the node using SIGINT
# Start the node again
Tested with:
[d7970190|https://github.com/apache/ignite-3/commit/d7970190a48b999d0adddfd5906d691b050576d2]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20499) Ability to obtain actual cluster configuration values during startup.
[ https://issues.apache.org/jira/browse/IGNITE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-20499: -- Summary: Ability to obtain actual cluster configuration values during startup. (was: Ability to obtain actual cluster configuration values during startup of system components.) > Ability to obtain actual cluster configuration values during startup. > - > > Key: IGNITE-20499 > URL: https://issues.apache.org/jira/browse/IGNITE-20499 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Pereslegin >Priority: Major > Labels: configuration, ignite-3 > > The value of the configuration parameter can be changed during cluster > initialization (IgniteImpl#init). At the moment, system components do not see > the actual configuration values at startup (since locally this values is > applied later). > In the case of reading an immutable config parameter with default value, this > can lead to confusion. Since the component at startup will read the default > configuration value, which then changes when the distributed configuration is > applied on the local node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20499) Ability to obtain actual cluster configuration values during startup of system components.
Pavel Pereslegin created IGNITE-20499: - Summary: Ability to obtain actual cluster configuration values during startup of system components. Key: IGNITE-20499 URL: https://issues.apache.org/jira/browse/IGNITE-20499 Project: Ignite Issue Type: Improvement Reporter: Pavel Pereslegin The value of the configuration parameter can be changed during cluster initialization (IgniteImpl#init). At the moment, system components do not see the actual configuration values at startup (since locally this values is applied later). In the case of reading an immutable config parameter with default value, this can lead to confusion. Since the component at startup will read the default configuration value, which then changes when the distributed configuration is applied on the local node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20498) Prevent potential catalog version order violations.
[
https://issues.apache.org/jira/browse/IGNITE-20498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-20498:
--
Labels: catalog ignite-3 (was: ignite-3)
> Prevent potential catalog version order violations.
> ---
>
> Key: IGNITE-20498
> URL: https://issues.apache.org/jira/browse/IGNITE-20498
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Pereslegin
>Priority: Major
> Labels: catalog, ignite-3
>
> Currently, catalog versions are stored in an ordered structure. The
> activation timestamp is used as a key, which depends on the configuration
> property "schemaSync.delayDuration".
> Changes to "delayDuration" parameter in runtime may lead to a violation of
> the order in which catalog versions are stored. That is, the old version may
> be saved with a larger timestamp than the newer one.
> As a result, the manager can return incorrect (older) version of the catalog
> using a timestamp.
> reproducer:
> {code:java}
> public class CatalogDelayDurationChangeTest extends BaseIgniteAbstractTest {
> private static final String NODE_NAME = "node1";
> private static final String TABLE_NAME = "test1";
> private final HybridClock clock = new HybridClockImpl();
> private final AtomicLong delayFromConfig = new AtomicLong();
> @Test
> public void testChangeDelayDuration() {
> CatalogManager catalogMgr = createManager();
> // Prepare schema changes.
> ColumnParams column =
> ColumnParams.builder().name("ID").type(ColumnType.INT32).build();
> CatalogCommand cmd1 =
> BaseCatalogManagerTest.createTableCommand(TABLE_NAME, List.of(column),
> List.of("ID"), null);
> CatalogCommand cmd2 =
> BaseCatalogManagerTest.createTableCommand("test2", List.of(column),
> List.of("ID"), null);
> // Make first schema change with delay = 1000.
> delayFromConfig.set(1_000);
> CompletableFuture schemaChangeFuture0 =
> catalogMgr.execute(cmd1);
> // Make second schema change with delay = 100.
> delayFromConfig.set(1);
> CompletableFuture schemaChangeFuture1 =
> catalogMgr.execute(cmd2);
> assertThat(schemaChangeFuture0, willCompleteSuccessfully());
> assertThat(schemaChangeFuture1, willCompleteSuccessfully());
> // Make sure that we are getting the latest version of the schema
> using current timestamp.
> int latestVer = catalogMgr.latestCatalogVersion();
> int currentTsVer =
> catalogMgr.activeCatalogVersion(clock.now().longValue());
> assertThat(currentTsVer, equalTo(latestVer));
> }
> private CatalogManager createManager() {
> VaultManager vault = new VaultManager(new InMemoryVaultService());
> MetaStorageManager metastore =
> StandaloneMetaStorageManager.create(vault, new
> SimpleInMemoryKeyValueStorage(NODE_NAME));
> UpdateLog updateLog = spy(new UpdateLogImpl(metastore));
> ClockWaiter clockWaiter = spy(new ClockWaiter(NODE_NAME, clock));
> CatalogManager manager = new CatalogManagerImpl(updateLog,
> clockWaiter, delayFromConfig::get);
> vault.start();
> metastore.start();
> clockWaiter.start();
> manager.start();
> metastore.deployWatches().join();
> return manager;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20499) Ability to obtain actual cluster configuration values during startup of system components.
[ https://issues.apache.org/jira/browse/IGNITE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-20499: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Ability to obtain actual cluster configuration values during startup of > system components. > -- > > Key: IGNITE-20499 > URL: https://issues.apache.org/jira/browse/IGNITE-20499 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Pereslegin >Priority: Major > Labels: configuration, ignite-3 > > The value of the configuration parameter can be changed during cluster > initialization (IgniteImpl#init). At the moment, system components do not see > the actual configuration values at startup (since locally this values is > applied later). > In the case of reading an immutable config parameter with default value, this > can lead to confusion. Since the component at startup will read the default > configuration value, which then changes when the distributed configuration is > applied on the local node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20498) Prevent potential catalog version order violations.
Pavel Pereslegin created IGNITE-20498:
-
Summary: Prevent potential catalog version order violations.
Key: IGNITE-20498
URL: https://issues.apache.org/jira/browse/IGNITE-20498
Project: Ignite
Issue Type: Bug
Reporter: Pavel Pereslegin
Currently, catalog versions are stored in an ordered structure. The activation
timestamp is used as a key, which depends on the configuration property
"schemaSync.delayDuration".
Changes to "delayDuration" parameter in runtime may lead to a violation of the
order in which catalog versions are stored. That is, the old version may be
saved with a larger timestamp than the newer one.
As a result, the manager can return incorrect (older) version of the catalog
using a timestamp.
reproducer:
{code:java}
public class CatalogDelayDurationChangeTest extends BaseIgniteAbstractTest {
private static final String NODE_NAME = "node1";
private static final String TABLE_NAME = "test1";
private final HybridClock clock = new HybridClockImpl();
private final AtomicLong delayFromConfig = new AtomicLong();
@Test
public void testChangeDelayDuration() {
CatalogManager catalogMgr = createManager();
// Prepare schema changes.
ColumnParams column =
ColumnParams.builder().name("ID").type(ColumnType.INT32).build();
CatalogCommand cmd1 =
BaseCatalogManagerTest.createTableCommand(TABLE_NAME, List.of(column),
List.of("ID"), null);
CatalogCommand cmd2 =
BaseCatalogManagerTest.createTableCommand("test2", List.of(column),
List.of("ID"), null);
// Make first schema change with delay = 1000.
delayFromConfig.set(1_000);
CompletableFuture schemaChangeFuture0 = catalogMgr.execute(cmd1);
// Make second schema change with delay = 100.
delayFromConfig.set(1);
CompletableFuture schemaChangeFuture1 = catalogMgr.execute(cmd2);
assertThat(schemaChangeFuture0, willCompleteSuccessfully());
assertThat(schemaChangeFuture1, willCompleteSuccessfully());
// Make sure that we are getting the latest version of the schema using
current timestamp.
int latestVer = catalogMgr.latestCatalogVersion();
int currentTsVer =
catalogMgr.activeCatalogVersion(clock.now().longValue());
assertThat(currentTsVer, equalTo(latestVer));
}
private CatalogManager createManager() {
VaultManager vault = new VaultManager(new InMemoryVaultService());
MetaStorageManager metastore =
StandaloneMetaStorageManager.create(vault, new
SimpleInMemoryKeyValueStorage(NODE_NAME));
UpdateLog updateLog = spy(new UpdateLogImpl(metastore));
ClockWaiter clockWaiter = spy(new ClockWaiter(NODE_NAME, clock));
CatalogManager manager = new CatalogManagerImpl(updateLog, clockWaiter,
delayFromConfig::get);
vault.start();
metastore.start();
clockWaiter.start();
manager.start();
metastore.deployWatches().join();
return manager;
}
}
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20497) Fix broken logger settings
[ https://issues.apache.org/jira/browse/IGNITE-20497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-20497: --- Fix Version/s: 3.0.0-beta2 > Fix broken logger settings > -- > > Key: IGNITE-20497 > URL: https://issues.apache.org/jira/browse/IGNITE-20497 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > I broke logger formatter in https://issues.apache.org/jira/browse/IGNITE-20480 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20497) Fix broken logger settings
[ https://issues.apache.org/jira/browse/IGNITE-20497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-20497: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Fix broken logger settings > -- > > Key: IGNITE-20497 > URL: https://issues.apache.org/jira/browse/IGNITE-20497 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > I broke logger formatter in https://issues.apache.org/jira/browse/IGNITE-20480 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20497) Fix broken logger settings
[ https://issues.apache.org/jira/browse/IGNITE-20497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov reassigned IGNITE-20497: -- Assignee: Ivan Bessonov > Fix broken logger settings > -- > > Key: IGNITE-20497 > URL: https://issues.apache.org/jira/browse/IGNITE-20497 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > I broke logger formatter in https://issues.apache.org/jira/browse/IGNITE-20480 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20468) .NET: Thin 3.0: Intermittent timeouts on TC
[ https://issues.apache.org/jira/browse/IGNITE-20468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769224#comment-17769224 ] Pavel Tupitsyn commented on IGNITE-20468: - Merged to main: aebca24f0a39aa195cea97e540419482f1753fb8 > .NET: Thin 3.0: Intermittent timeouts on TC > --- > > Key: IGNITE-20468 > URL: https://issues.apache.org/jira/browse/IGNITE-20468 > Project: Ignite > Issue Type: Bug > Components: platforms, thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Critical > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > Increased number of .NET TC builds fail with timeout errors. Investigate > whether some specific test or behavior is causing this, whether this is a > problem on server side, etc > * > https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunNetTests?branch=%3Cdefault%3E=builds#all-projects > * `Fail to issue RPC to > org.apache.ignite.internal.runner.app.PlatformTestNodeRunner_2, > consecutiveErrorTimes=10, error=Status[ETIMEDOUT<1010>: RPC exception:null]` > * `OneTimeSetUp: System.TimeoutException : The operation has timed out.` > ** Which operation? Why is there no stack trace? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20468) .NET: Thin 3.0: Intermittent timeouts on TC
[ https://issues.apache.org/jira/browse/IGNITE-20468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769216#comment-17769216 ] Igor Sapego commented on IGNITE-20468: -- Looks good to me. > .NET: Thin 3.0: Intermittent timeouts on TC > --- > > Key: IGNITE-20468 > URL: https://issues.apache.org/jira/browse/IGNITE-20468 > Project: Ignite > Issue Type: Bug > Components: platforms, thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Critical > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > Increased number of .NET TC builds fail with timeout errors. Investigate > whether some specific test or behavior is causing this, whether this is a > problem on server side, etc > * > https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunNetTests?branch=%3Cdefault%3E=builds#all-projects > * `Fail to issue RPC to > org.apache.ignite.internal.runner.app.PlatformTestNodeRunner_2, > consecutiveErrorTimes=10, error=Status[ETIMEDOUT<1010>: RPC exception:null]` > * `OneTimeSetUp: System.TimeoutException : The operation has timed out.` > ** Which operation? Why is there no stack trace? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20497) Fix broken logger settings
Ivan Bessonov created IGNITE-20497: -- Summary: Fix broken logger settings Key: IGNITE-20497 URL: https://issues.apache.org/jira/browse/IGNITE-20497 Project: Ignite Issue Type: Bug Reporter: Ivan Bessonov I broke logger formatter in https://issues.apache.org/jira/browse/IGNITE-20480 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20496) Integrate & test Logit log storage
Ivan Bessonov created IGNITE-20496: -- Summary: Integrate & test Logit log storage Key: IGNITE-20496 URL: https://issues.apache.org/jira/browse/IGNITE-20496 Project: Ignite Issue Type: Improvement Reporter: Ivan Bessonov Assignee: Ivan Bessonov https://issues.apache.org/jira/browse/IGNITE-19806 We need to test Ignite with alternative log storage implementation and check the performance benefits. In order to do that, we need to properly integrate this implementation into the system. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-16763) TableManager doesn't throw exception on table create, if something goes wrong in configuration listener for updateAssignments
[ https://issues.apache.org/jira/browse/IGNITE-16763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769191#comment-17769191 ] Andrey Mashenkov edited comment on IGNITE-16763 at 9/26/23 1:58 PM: [~Denis Chudov] is it still actual? I just found this ticket is mentioned in a code, but we don't use Configuration events anymore. Also, I see ticket description and `rebalance.md` documentation both refer to `TableManager.onUpdateAssignments` method, which is no longer exists. Seems, the documentation and ticket description should be actualized. was (Author: amashenkov): [~Denis Chudov] is it still actual? > TableManager doesn't throw exception on table create, if something goes wrong > in configuration listener for updateAssignments > - > > Key: IGNITE-16763 > URL: https://issues.apache.org/jira/browse/IGNITE-16763 > Project: Ignite > Issue Type: Bug >Reporter: Denis Chudov >Priority: Major > Labels: ignite-3 > > Scenario: > Start a node, try to create a table. Inside of TableManager the listener > onTableCreate is successfully executed. Then, an exception happens inside of > TableManager#onUpdateAssignments > configuration listener, which is triggered after the completion of > onTableCreate listener. To reproduce the issue need to add an exception > throwing in TableManager#onUpdateAssignments and create a table. > Expected behavior: > There is no operational instance of the newly created table on the node that > initiated creation of the table, because onUpdateAssignments had failed. > "Create table" operation should fail with exception. > Actual: > "Create table" operation succeeds, as onTableCreate listener in TableManager > had succeeded. > Suggested fix: > onUpdateAssignments should save exception to versioned values in > TableManager, as it updates these versioned values. Thus, the following > VersionedValue#get will throw an exception, and table creation future will be > completed exceptionally (see TableManager#completeApiCreateFuture ). However, > we should think about how further updates of these versioned values will > happen. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-16763) TableManager doesn't throw exception on table create, if something goes wrong in configuration listener for updateAssignments
[ https://issues.apache.org/jira/browse/IGNITE-16763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769191#comment-17769191 ] Andrey Mashenkov commented on IGNITE-16763: --- [~Denis Chudov] is it still actual? > TableManager doesn't throw exception on table create, if something goes wrong > in configuration listener for updateAssignments > - > > Key: IGNITE-16763 > URL: https://issues.apache.org/jira/browse/IGNITE-16763 > Project: Ignite > Issue Type: Bug >Reporter: Denis Chudov >Priority: Major > Labels: ignite-3 > > Scenario: > Start a node, try to create a table. Inside of TableManager the listener > onTableCreate is successfully executed. Then, an exception happens inside of > TableManager#onUpdateAssignments > configuration listener, which is triggered after the completion of > onTableCreate listener. To reproduce the issue need to add an exception > throwing in TableManager#onUpdateAssignments and create a table. > Expected behavior: > There is no operational instance of the newly created table on the node that > initiated creation of the table, because onUpdateAssignments had failed. > "Create table" operation should fail with exception. > Actual: > "Create table" operation succeeds, as onTableCreate listener in TableManager > had succeeded. > Suggested fix: > onUpdateAssignments should save exception to versioned values in > TableManager, as it updates these versioned values. Thus, the following > VersionedValue#get will throw an exception, and table creation future will be > completed exceptionally (see TableManager#completeApiCreateFuture ). However, > we should think about how further updates of these versioned values will > happen. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20494) sql command does not enter repl
[
https://issues.apache.org/jira/browse/IGNITE-20494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Pakhnushev updated IGNITE-20494:
--
Fix Version/s: (was: 3.0.0-beta2)
Ignite Flags: (was: Docs Required,Release Notes Required)
Description:
{code:bash}
[node]> sql -f=foo
Unknown error
File with command not found
[node]> sql< here type exactly 3 letters and hit enter
Unknown error
File with command not found {code}
I would expect to enter the repl, but I get the same error message that I've
got before.
This is exact same issue of the IGNITE-19038
was:
{code:bash}
[defaultNode]> sql "create table test(i int primary key)"
SQL query execution error
Exception while executing query [query="create table test(i int primary key)"].
Error message:IGN-SQL-3 TraceId:9f1d43d1-5f6d-4319-94a1-2225e931a80d IGN-SQL-3
TraceId:9f1d43d1-5f6d-4319-94a1-2225e931a80d Failed to parse query: Non-query
expression encountered in illegal context <--- Why I get this error?
[defaultNode]> SQL< here type exactly 3 letters and hit enter
SQL query execution error
Exception while executing query [query="create table test(i int primary key)"].
Error message:IGN-SQL-3 TraceId:801a965d-3adf-443c-8028-d080fa894fb8 IGN-SQL-3
TraceId:801a965d-3adf-443c-8028-d080fa894fb8 Failed to parse query: Non-query
expression encountered in illegal context
{code}
I would expect to enter the repl, but I get the same error message that I've
got before.
Also, the first error I've got seems strange, exactly the same query works in
the repl.
Note: if I type "sql " with the space after -- it enters the repl.
> sql command does not enter repl
> ---
>
> Key: IGNITE-20494
> URL: https://issues.apache.org/jira/browse/IGNITE-20494
> Project: Ignite
> Issue Type: Bug
> Components: cli
>Reporter: Vadim Pakhnushev
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
>
> {code:bash}
> [node]> sql -f=foo
> Unknown error
> File with command not found
> [node]> sql< here type exactly 3 letters and hit enter
> Unknown error
> File with command not found {code}
> I would expect to enter the repl, but I get the same error message that I've
> got before.
> This is exact same issue of the IGNITE-19038
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19112) Get rid of MvTableStorage#getOrCreateIndex
[ https://issues.apache.org/jira/browse/IGNITE-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-19112: - Description: Get rid of methods: * org.apache.ignite.internal.storage.engine.MvTableStorage#getOrCreateIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#getOrCreateHashIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#getOrCreateSortedIndex and make new ones: * org.apache.ignite.internal.storage.engine.MvTableStorage#createIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#getIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#createHashIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#getHashIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#createSortedIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#getSortedIndex was: Get rid of methods: * org.apache.ignite.internal.storage.engine.MvTableStorage#getOrCreateIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#getOrCreateHashIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#getOrCreateSortedIndex and make new ones: * org.apache.ignite.internal.storage.engine.MvTableStorage#createIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#getOrCreateIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#createHashIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#getHashIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#createSortedIndex * org.apache.ignite.internal.storage.engine.MvTableStorage#getSortedIndex > Get rid of MvTableStorage#getOrCreateIndex > -- > > Key: IGNITE-19112 > URL: https://issues.apache.org/jira/browse/IGNITE-19112 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Get rid of methods: > * org.apache.ignite.internal.storage.engine.MvTableStorage#getOrCreateIndex > * > org.apache.ignite.internal.storage.engine.MvTableStorage#getOrCreateHashIndex > * > org.apache.ignite.internal.storage.engine.MvTableStorage#getOrCreateSortedIndex > and make new ones: > * org.apache.ignite.internal.storage.engine.MvTableStorage#createIndex > * org.apache.ignite.internal.storage.engine.MvTableStorage#getIndex > * org.apache.ignite.internal.storage.engine.MvTableStorage#createHashIndex > * org.apache.ignite.internal.storage.engine.MvTableStorage#getHashIndex > * org.apache.ignite.internal.storage.engine.MvTableStorage#createSortedIndex > * org.apache.ignite.internal.storage.engine.MvTableStorage#getSortedIndex -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20495) Sql. Provide IgniteTableModify with source id
Konstantin Orlov created IGNITE-20495:
-
Summary: Sql. Provide IgniteTableModify with source id
Key: IGNITE-20495
URL: https://issues.apache.org/jira/browse/IGNITE-20495
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Konstantin Orlov
Currently, IgniteTableModify doesn't implement interface SourceAwareIgniteRel,
and, as a result, is not being assigned its own source id, although requires to
be mapped on particular set of nodes with regards to the distribution of the
table it modifies.
To fully integrate TableModify into mapping process, let's make it implement
SourceAwareIgniteRel. This id should be used during mapping phase to create
colocation group properly, and inside execution to acquire assignments. See
usages of {{UpdatableTableImpl#MODIFY_NODE_SOURCE_ID}} to find all places that
should be changed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20467) Use replica message instead of directly using raft client when building indexes
[ https://issues.apache.org/jira/browse/IGNITE-20467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769116#comment-17769116 ] Roman Puchkovskiy commented on IGNITE-20467: The patch looks good to me > Use replica message instead of directly using raft client when building > indexes > --- > > Key: IGNITE-20467 > URL: https://issues.apache.org/jira/browse/IGNITE-20467 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > *org.apache.ignite.internal.table.distributed.index.IndexBuilder* uses a raft > client, I think it’s worth changing this to using a replication message to > get rid of the implementation of the replication protocol. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20411) IndexOutOfBoundsException in SqlRowHandler$BinaryTupleRowWrapper
[
https://issues.apache.org/jira/browse/IGNITE-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov reassigned IGNITE-20411:
-
Assignee: Maksim Zhuravkov
> IndexOutOfBoundsException in SqlRowHandler$BinaryTupleRowWrapper
>
>
> Key: IGNITE-20411
> URL: https://issues.apache.org/jira/browse/IGNITE-20411
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Tupitsyn
>Assignee: Maksim Zhuravkov
>Priority: Critical
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> *Exception:*
> {code}
> java.lang.IndexOutOfBoundsException: Index 2 out of bounds for length 2
> at
> java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
> at
> java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
> at
> java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
> at java.base/java.util.Objects.checkIndex(Objects.java:372)
> at java.base/java.util.ArrayList.get(ArrayList.java:459)
> at
> org.apache.ignite.internal.sql.engine.exec.SqlRowHandler$BinaryTupleRowWrapper.get(SqlRowHandler.java:357)
> at
> org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:74)
> at
> org.apache.ignite.internal.sql.engine.exec.SqlRowHandler.get(SqlRowHandler.java:65)
> at
> org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.convertRow(UpdatableTableImpl.java:337)
> at
> org.apache.ignite.internal.sql.engine.exec.UpdatableTableImpl.insertAll(UpdatableTableImpl.java:242)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:219)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:190)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:163)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.Inbox.pushUnordered(Inbox.java:344)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.Inbox.push(Inbox.java:202)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.Inbox.onBatchReceived(Inbox.java:180)
> at
> org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.onMessage(ExchangeServiceImpl.java:167)
> at
> org.apache.ignite.internal.sql.engine.exec.ExchangeServiceImpl.lambda$start$1(ExchangeServiceImpl.java:73)
> at
> org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:150)
> at
> org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.lambda$onMessage$0(MessageServiceImpl.java:119)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:81)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
> *Reproducer:*
> Add this test to *ItSqlSynchronousApiTest*
> {code:java}
> @Test
> public void testUpdateTable() {
> IgniteSql sql = igniteSql();
> Session ses = sql.createSession();
> checkDdl(true, ses, "CREATE TABLE TEST(ID INT PRIMARY KEY, VAL0
> INT)");
> var upsertFut = CompletableFuture.runAsync(() -> {
> for (int i = 0; i < 1000; i++) {
> checkDml(1, ses, "INSERT INTO TEST VALUES (?, ?)", i, i);
> }
> });
> checkDdl(true, ses, "ALTER TABLE TEST ADD COLUMN VAL1 INT DEFAULT
> -1");
> upsertFut.join();
> }
> {code}
> *NOTE*
> Original exception stack trace seems to be lost if you just run the test, I
> had to use debugger to get it. Consider addressing this too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20490) Update the snappy dependency in order to fix CVEs
[ https://issues.apache.org/jira/browse/IGNITE-20490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-20490: - Affects Version/s: 2.15 > Update the snappy dependency in order to fix CVEs > - > > Key: IGNITE-20490 > URL: https://issues.apache.org/jira/browse/IGNITE-20490 > Project: Ignite > Issue Type: Task >Affects Versions: 2.15 >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > The dependency needs to be updated to fix CVE: > https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20490) Update the snappy dependency in order to fix CVEs
[ https://issues.apache.org/jira/browse/IGNITE-20490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-20490: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Update the snappy dependency in order to fix CVEs > - > > Key: IGNITE-20490 > URL: https://issues.apache.org/jira/browse/IGNITE-20490 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > The dependency needs to be updated to fix CVE: > https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20490) Update the snappy dependency in order to fix CVEs
[ https://issues.apache.org/jira/browse/IGNITE-20490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-20490: - Release Note: Updates snappy java dependency up to the latest 1.1.10.4 > Update the snappy dependency in order to fix CVEs > - > > Key: IGNITE-20490 > URL: https://issues.apache.org/jira/browse/IGNITE-20490 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > The dependency needs to be updated to fix CVE: > https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20490) Update the snappy dependency in order to fix CVEs
[ https://issues.apache.org/jira/browse/IGNITE-20490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769101#comment-17769101 ] Maxim Muzafarov commented on IGNITE-20490: -- Merged to the master branch. [~NIzhikov] thank you for the review. > Update the snappy dependency in order to fix CVEs > - > > Key: IGNITE-20490 > URL: https://issues.apache.org/jira/browse/IGNITE-20490 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > The dependency needs to be updated to fix CVE: > https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20490) Update the snappy dependency in order to fix CVEs
[ https://issues.apache.org/jira/browse/IGNITE-20490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-20490: - Release Note: (was: Merged to the master branch. [~NIzhikov] thank you for the review.) > Update the snappy dependency in order to fix CVEs > - > > Key: IGNITE-20490 > URL: https://issues.apache.org/jira/browse/IGNITE-20490 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > The dependency needs to be updated to fix CVE: > https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19226) Fetch table schema by timestamp
[ https://issues.apache.org/jira/browse/IGNITE-19226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy reassigned IGNITE-19226: -- Assignee: Roman Puchkovskiy > Fetch table schema by timestamp > --- > > Key: IGNITE-19226 > URL: https://issues.apache.org/jira/browse/IGNITE-19226 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: iep-98, ignite-3 > > Currently, when obtaining a schema, its latest (from the local point of view) > version is returned. > # Table schema must always be obtained using a timestamp > # This might require a wait (until MetaStorage's SafeTime >= schemaTs-DD, > see > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-98%3A+Schema+Synchronization#IEP98:SchemaSynchronization-Waitingforsafetimeinthepast] > ) > This includes the mechanisms that allow clients obtain 'current' schema (like > 'DESCRIBE ', 'list tables', etc). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20494) sql command does not enter repl
Vadim Pakhnushev created IGNITE-20494:
-
Summary: sql command does not enter repl
Key: IGNITE-20494
URL: https://issues.apache.org/jira/browse/IGNITE-20494
Project: Ignite
Issue Type: Bug
Components: cli
Reporter: Vadim Pakhnushev
Assignee: Vadim Pakhnushev
Fix For: 3.0.0-beta2
{code:bash}
[defaultNode]> sql "create table test(i int primary key)"
SQL query execution error
Exception while executing query [query="create table test(i int primary key)"].
Error message:IGN-SQL-3 TraceId:9f1d43d1-5f6d-4319-94a1-2225e931a80d IGN-SQL-3
TraceId:9f1d43d1-5f6d-4319-94a1-2225e931a80d Failed to parse query: Non-query
expression encountered in illegal context <--- Why I get this error?
[defaultNode]> SQL< here type exactly 3 letters and hit enter
SQL query execution error
Exception while executing query [query="create table test(i int primary key)"].
Error message:IGN-SQL-3 TraceId:801a965d-3adf-443c-8028-d080fa894fb8 IGN-SQL-3
TraceId:801a965d-3adf-443c-8028-d080fa894fb8 Failed to parse query: Non-query
expression encountered in illegal context
{code}
I would expect to enter the repl, but I get the same error message that I've
got before.
Also, the first error I've got seems strange, exactly the same query works in
the repl.
Note: if I type "sql " with the space after -- it enters the repl.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17931) Blocking code inside SchemaRegistryImpl#schema(int), need to be refactored.
[ https://issues.apache.org/jira/browse/IGNITE-17931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769095#comment-17769095 ] Roman Puchkovskiy commented on IGNITE-17931: This will *most likely* be fixed in IGNITE-19226 > Blocking code inside SchemaRegistryImpl#schema(int), need to be refactored. > --- > > Key: IGNITE-17931 > URL: https://issues.apache.org/jira/browse/IGNITE-17931 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha5 >Reporter: Evgeny Stanilovsky >Priority: Blocker > Labels: ignite-3 > > Previously blocking fut.join() contains in SchemaManager#tableSchema after > refactoring it moves into SchemaRegistryImpl#schema(int) [1], it`s necessary > to remove blocking approach. > [1] > https://github.com/apache/ignite-3/blob/7b0b3395de97db09896272e03322bba302c0b556/modules/schema/src/main/java/org/apache/ignite/internal/schema/registry/SchemaRegistryImpl.java#L93 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-20493) Ignite website shows downloading version 2.11 as latest version
[ https://issues.apache.org/jira/browse/IGNITE-20493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev resolved IGNITE-20493. Resolution: Fixed > Ignite website shows downloading version 2.11 as latest version > --- > > Key: IGNITE-20493 > URL: https://issues.apache.org/jira/browse/IGNITE-20493 > Project: Ignite > Issue Type: Task >Reporter: Erlan Aytpaev >Assignee: Erlan Aytpaev >Priority: Major > > !https://lists.apache.org/api/email.lua?attachment=true=1c01nt4nol691fxz5k71zpwd5r60d0ql=08cc11e094cb73962012551428c510b4c62b6064ee6e2e07737241c552039874! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20493) Ignite website shows downloading version 2.11 as latest version
[ https://issues.apache.org/jira/browse/IGNITE-20493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev updated IGNITE-20493: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Ignite website shows downloading version 2.11 as latest version > --- > > Key: IGNITE-20493 > URL: https://issues.apache.org/jira/browse/IGNITE-20493 > Project: Ignite > Issue Type: Task >Reporter: Erlan Aytpaev >Assignee: Erlan Aytpaev >Priority: Major > > !https://lists.apache.org/api/email.lua?attachment=true=1c01nt4nol691fxz5k71zpwd5r60d0ql=08cc11e094cb73962012551428c510b4c62b6064ee6e2e07737241c552039874! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20493) Ignite website shows downloading version 2.11 as latest version
[ https://issues.apache.org/jira/browse/IGNITE-20493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev reassigned IGNITE-20493: -- Assignee: Erlan Aytpaev > Ignite website shows downloading version 2.11 as latest version > --- > > Key: IGNITE-20493 > URL: https://issues.apache.org/jira/browse/IGNITE-20493 > Project: Ignite > Issue Type: Task >Reporter: Erlan Aytpaev >Assignee: Erlan Aytpaev >Priority: Major > > !https://lists.apache.org/api/email.lua?attachment=true=1c01nt4nol691fxz5k71zpwd5r60d0ql=08cc11e094cb73962012551428c510b4c62b6064ee6e2e07737241c552039874! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20493) Ignite website shows downloading version 2.11 as latest version
Erlan Aytpaev created IGNITE-20493: -- Summary: Ignite website shows downloading version 2.11 as latest version Key: IGNITE-20493 URL: https://issues.apache.org/jira/browse/IGNITE-20493 Project: Ignite Issue Type: Task Reporter: Erlan Aytpaev !https://lists.apache.org/api/email.lua?attachment=true=1c01nt4nol691fxz5k71zpwd5r60d0ql=08cc11e094cb73962012551428c510b4c62b6064ee6e2e07737241c552039874! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20448) Implement strategies for failure handling
[ https://issues.apache.org/jira/browse/IGNITE-20448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel reassigned IGNITE-20448: -- Assignee: Sergey Uttsel > Implement strategies for failure handling > - > > Key: IGNITE-20448 > URL: https://issues.apache.org/jira/browse/IGNITE-20448 > Project: Ignite > Issue Type: Improvement >Reporter: Vyacheslav Koptilin >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > > Need to implement the following strategies for failure handling: > - StopNodeFailureHandler This handler should stop the node in case of a > critical error > - StopNodeOrHaltFailureHandler This handler should try to stop the node. If > the node cannot be stopped during a timeout, then the JVM process should be > stopped forcibly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20447) Introduce a new failure handling component
[ https://issues.apache.org/jira/browse/IGNITE-20447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-20447: --- Reviewer: Mirza Aliev > Introduce a new failure handling component > -- > > Key: IGNITE-20447 > URL: https://issues.apache.org/jira/browse/IGNITE-20447 > Project: Ignite > Issue Type: Improvement >Reporter: Vyacheslav Koptilin >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Let's add a new component `failure` to Apache Ignite 3 and add base > interfaces to this component. > *Definition of done:* > - introduced a new module to Ignite 3 codebase > - introduced a new Ignite component - _FailureProcessor _with minimal no-op > implementation. This component is responsible for processing critical errors. > - introduced a new _FailureHandler _interface. An implementation of this > interface represents a concrete strategy for handling errors. > - introduced a new enum _FailureType _that describes a possible type of > failure. The following types can be considered as a starting point: > _CRITICAL_ERROR_, _SYSTEM_WORKER_TERMINATION_, _SYSTEM_WORKER_BLOCKED_, > _SYSTEM_CRITICAL_OPERATION_TIMEOUT_ > - introduced a new class _FailureContext _that contains information about > failure type and exception. > *Implemenattion notes:* > All these classes and interfaces should be a part of internal API due to > the end user should not provide a custom implementation of the failure > handler, Apache Ignite should provide a closed list of handlers out of the > box. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20336) Sql. Remove conversion from java types to TypeSpec.
[ https://issues.apache.org/jira/browse/IGNITE-20336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-20336: Ignite Flags: (was: Docs Required,Release Notes Required) > Sql. Remove conversion from java types to TypeSpec. > --- > > Key: IGNITE-20336 > URL: https://issues.apache.org/jira/browse/IGNITE-20336 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Maksim Zhuravkov >Assignee: Evgeny Stanilovsky >Priority: Minor > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 40m > Remaining Estimate: 0h > > JavaTypes are no longer used by execution engine, but they remain in > execution node tests and TypeUtils::convertToTypeSpec. > - Update unit not to use TypeUtils::createRowType(TypeFactory, Class... > fields). > - Remove conversion from JavaType from TypeUtils::convertToTypeSpec. > - Remove TypeUtils::createRowType(TypeFactory, Class... fields) as it is > no longer needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
