[jira] [Updated] (IGNITE-21678) IgniteToIgniteCdcStreamer fails if BinaryConfiguration is specified in config
[
https://issues.apache.org/jira/browse/IGNITE-21678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Korotkov updated IGNITE-21678:
-
Priority: Major (was: Minor)
> IgniteToIgniteCdcStreamer fails if BinaryConfiguration is specified in config
> -
>
> Key: IGNITE-21678
> URL: https://issues.apache.org/jira/browse/IGNITE-21678
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Korotkov
>Assignee: Sergey Korotkov
>Priority: Major
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The below exception occurs if destination cluster has the explicit
> BinaryConfiguration instance included into the IgniteConfiguration:
> {noformat}
> 2024-03-04T12:14:31,777][INFO ][Thread-0][] Ignite Change Data Capture
> Application stopped.
> [2024-03-04T12:14:31,782][ERROR][Thread-0][] Cdc error
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1163)
> ~[classes/:?]
> at org.apache.ignite.Ignition.start(Ignition.java:303) ~[classes/:?]
> at
> org.apache.ignite.cdc.IgniteToIgniteCdcStreamer.start(IgniteToIgniteCdcStreamer.java:86)
> ~[ignite-cdc-ext-1.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.cdc.WalRecordsConsumer.start(WalRecordsConsumer.java:192)
> ~[classes/:?]
> at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:360)
> ~[classes/:?]
> at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:306)
> [classes/:?]
> at java.base/java.lang.Thread.run(Thread.java:829) [?:?]
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1777)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1159)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1089)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:625)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:547)
> ~[classes/:?]
> at org.apache.ignite.Ignition.start(Ignition.java:300) ~[classes/:?]
> ... 5 more
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start SPI:
> TcpDiscoverySpi [addrRslvr=null, addressFilter=null, sockTimeout=5000,
> ackTimeout=5000, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@5f243268],
> reconCnt=10, reconDelay=2000, maxAckTimeout=60, soLinger=0,
> forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null,
> skipAddrsRandomization=false]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:280)
> ~[classes/:?]
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:1072)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1772)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1159)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1089)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:625)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:547)
> ~[classes/:?]
> at org.apache.ignite.Ignition.start(Ignition.java:300) ~[classes/:?]
> ... 5 more
> Caused by: org.apache.ignite.spi.IgniteSpiException: Local node's binary
> configuration is not equal to remote node's binary configuration
> [locNodeId=6eb40fd6-b20e-4485-a7f7-bb62e7e96abf,
> rmtNodeId=e2f49ba1-6f99-4b75-8476-8bc925639527, locBinaryCfg=null,
> rmtBinaryCfg={globIdMapper=null, compactFooter=true, globSerializer=null}]
> at
>
[jira] [Updated] (IGNITE-21678) IgniteToIgniteCdcStreamer fails if BinaryConfiguration is specified in config
[
https://issues.apache.org/jira/browse/IGNITE-21678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Korotkov updated IGNITE-21678:
-
Fix Version/s: 2.17
> IgniteToIgniteCdcStreamer fails if BinaryConfiguration is specified in config
> -
>
> Key: IGNITE-21678
> URL: https://issues.apache.org/jira/browse/IGNITE-21678
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Korotkov
>Assignee: Sergey Korotkov
>Priority: Minor
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The below exception occurs if destination cluster has the explicit
> BinaryConfiguration instance included into the IgniteConfiguration:
> {noformat}
> 2024-03-04T12:14:31,777][INFO ][Thread-0][] Ignite Change Data Capture
> Application stopped.
> [2024-03-04T12:14:31,782][ERROR][Thread-0][] Cdc error
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1163)
> ~[classes/:?]
> at org.apache.ignite.Ignition.start(Ignition.java:303) ~[classes/:?]
> at
> org.apache.ignite.cdc.IgniteToIgniteCdcStreamer.start(IgniteToIgniteCdcStreamer.java:86)
> ~[ignite-cdc-ext-1.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.cdc.WalRecordsConsumer.start(WalRecordsConsumer.java:192)
> ~[classes/:?]
> at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:360)
> ~[classes/:?]
> at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:306)
> [classes/:?]
> at java.base/java.lang.Thread.run(Thread.java:829) [?:?]
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1777)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1159)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1089)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:625)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:547)
> ~[classes/:?]
> at org.apache.ignite.Ignition.start(Ignition.java:300) ~[classes/:?]
> ... 5 more
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start SPI:
> TcpDiscoverySpi [addrRslvr=null, addressFilter=null, sockTimeout=5000,
> ackTimeout=5000, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@5f243268],
> reconCnt=10, reconDelay=2000, maxAckTimeout=60, soLinger=0,
> forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null,
> skipAddrsRandomization=false]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:280)
> ~[classes/:?]
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:1072)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1772)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1159)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1089)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:625)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:547)
> ~[classes/:?]
> at org.apache.ignite.Ignition.start(Ignition.java:300) ~[classes/:?]
> ... 5 more
> Caused by: org.apache.ignite.spi.IgniteSpiException: Local node's binary
> configuration is not equal to remote node's binary configuration
> [locNodeId=6eb40fd6-b20e-4485-a7f7-bb62e7e96abf,
> rmtNodeId=e2f49ba1-6f99-4b75-8476-8bc925639527, locBinaryCfg=null,
> rmtBinaryCfg={globIdMapper=null, compactFooter=true, globSerializer=null}]
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:2131)
>
[jira] [Updated] (IGNITE-21678) IgniteToIgniteCdcStreamer fails if BinaryConfiguration is specified in config
[
https://issues.apache.org/jira/browse/IGNITE-21678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Korotkov updated IGNITE-21678:
-
Labels: ise (was: )
> IgniteToIgniteCdcStreamer fails if BinaryConfiguration is specified in config
> -
>
> Key: IGNITE-21678
> URL: https://issues.apache.org/jira/browse/IGNITE-21678
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Korotkov
>Assignee: Sergey Korotkov
>Priority: Minor
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The below exception occurs if destination cluster has the explicit
> BinaryConfiguration instance included into the IgniteConfiguration:
> {noformat}
> 2024-03-04T12:14:31,777][INFO ][Thread-0][] Ignite Change Data Capture
> Application stopped.
> [2024-03-04T12:14:31,782][ERROR][Thread-0][] Cdc error
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1163)
> ~[classes/:?]
> at org.apache.ignite.Ignition.start(Ignition.java:303) ~[classes/:?]
> at
> org.apache.ignite.cdc.IgniteToIgniteCdcStreamer.start(IgniteToIgniteCdcStreamer.java:86)
> ~[ignite-cdc-ext-1.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.cdc.WalRecordsConsumer.start(WalRecordsConsumer.java:192)
> ~[classes/:?]
> at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:360)
> ~[classes/:?]
> at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:306)
> [classes/:?]
> at java.base/java.lang.Thread.run(Thread.java:829) [?:?]
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1777)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1159)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1089)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:625)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:547)
> ~[classes/:?]
> at org.apache.ignite.Ignition.start(Ignition.java:300) ~[classes/:?]
> ... 5 more
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start SPI:
> TcpDiscoverySpi [addrRslvr=null, addressFilter=null, sockTimeout=5000,
> ackTimeout=5000, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@5f243268],
> reconCnt=10, reconDelay=2000, maxAckTimeout=60, soLinger=0,
> forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null,
> skipAddrsRandomization=false]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:280)
> ~[classes/:?]
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:1072)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1772)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1159)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
> ~[classes/:?]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1089)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:625)
> ~[classes/:?]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:547)
> ~[classes/:?]
> at org.apache.ignite.Ignition.start(Ignition.java:300) ~[classes/:?]
> ... 5 more
> Caused by: org.apache.ignite.spi.IgniteSpiException: Local node's binary
> configuration is not equal to remote node's binary configuration
> [locNodeId=6eb40fd6-b20e-4485-a7f7-bb62e7e96abf,
> rmtNodeId=e2f49ba1-6f99-4b75-8476-8bc925639527, locBinaryCfg=null,
> rmtBinaryCfg={globIdMapper=null, compactFooter=true, globSerializer=null}]
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:2131)
> ~[classes/:?]
> at
[jira] [Updated] (IGNITE-21677) Fix NPE in ActiveActorTest
[ https://issues.apache.org/jira/browse/IGNITE-21677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21677: --- Description: An NPE is thrown when ActiveActorTest is run, it happens during AssignmentsTracker recovery because the mocked MetaStorageManager returns a null Cursor. Also, if an exception happens during AssignmentsTracker recovery, it is not logged and is not propagated anywhere. was:An NPE is thrown when ActiveActorTest is run, it happens during AssignmentsTracker recovery because the mocked MetaStorageManager returns a null Cursor. > Fix NPE in ActiveActorTest > -- > > Key: IGNITE-21677 > URL: https://issues.apache.org/jira/browse/IGNITE-21677 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > An NPE is thrown when ActiveActorTest is run, it happens during > AssignmentsTracker recovery because the mocked MetaStorageManager returns a > null Cursor. > Also, if an exception happens during AssignmentsTracker recovery, it is not > logged and is not propagated anywhere. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21679) Add gatling plugin for load testing to extensions
Sergey Korotkov created IGNITE-21679: Summary: Add gatling plugin for load testing to extensions Key: IGNITE-21679 URL: https://issues.apache.org/jira/browse/IGNITE-21679 Project: Ignite Issue Type: Task Reporter: Sergey Korotkov Assignee: Sergey Korotkov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21523) ItNodeRestartsTest.testRestarts is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823482#comment-17823482
]
Roman Puchkovskiy commented on IGNITE-21523:
Thanks!
> ItNodeRestartsTest.testRestarts is flaky
>
>
> Key: IGNITE-21523
> URL: https://issues.apache.org/jira/browse/IGNITE-21523
> Project: Ignite
> Issue Type: Bug
>Reporter: Roman Puchkovskiy
>Assignee: Roman Puchkovskiy
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After running the test repeatedly, the following happened: after a restart of
> 2 clusterServices, one of the restarted cluster services (port 3344) and one
> of not restarted cluster services (port 3345) could not 'see' each other due
> to metadata obtaining timeout:
> [2024-02-12T14:16:54,968][WARN ][sc-cluster-3345-1409][MetadataStore]
> [default:inrt_tr_3345:13b7bdae21a14c86@127.0.1.1:3345][56ad9288-7ce4-4f67-b11c-8e1eaf6d6612]
> Timeout getting GetMetadataResp from 127.0.1.1:3344 within 1000 ms, cause:
> java.util.concurrent.TimeoutException: Did not observe any item or terminal
> signal within 1000ms in 'source(MonoDefer)' (and no fallback has been
> configured)
> [2024-02-12T14:16:54,968][WARN ][sc-cluster-3345-1409][MembershipProtocol]
> [default:inrt_tr_3345:13b7bdae21a14c86@127.0.1.1:3345][updateMembership][SYNC]
> Skipping to add/update member: \{m:
> default:inrt_tr_3344:788fea0a8f9b4251@127.0.1.1:3344, s: ALIVE, inc: 0}, due
> to failed fetchMetadata call (cause: java.util.concurrent.TimeoutException:
> Did not observe any item or terminal signal within 1000ms in
> 'source(MonoDefer)' (and no fallback has been configured))
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21670) Remove MvTableStorage#start method
[ https://issues.apache.org/jira/browse/IGNITE-21670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-21670: - Fix Version/s: 3.0.0-beta2 > Remove MvTableStorage#start method > -- > > Key: IGNITE-21670 > URL: https://issues.apache.org/jira/browse/IGNITE-21670 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > This method is probably some legacy remnant after table schema has been moved > away from the configuration. Currently this method is always called after an > instance of MvTableStorage is created and does nothing useful, all its code > can be moved to the corresponding constructors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21670) Remove MvTableStorage#start method
[ https://issues.apache.org/jira/browse/IGNITE-21670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-21670: - Labels: ignite-3 (was: ) > Remove MvTableStorage#start method > -- > > Key: IGNITE-21670 > URL: https://issues.apache.org/jira/browse/IGNITE-21670 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > > This method is probably some legacy remnant after table schema has been moved > away from the configuration. Currently this method is always called after an > instance of MvTableStorage is created and does nothing useful, all its code > can be moved to the corresponding constructors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21670) Remove MvTableStorage#start method
[ https://issues.apache.org/jira/browse/IGNITE-21670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-21670: - Ignite Flags: (was: Docs Required,Release Notes Required) > Remove MvTableStorage#start method > -- > > Key: IGNITE-21670 > URL: https://issues.apache.org/jira/browse/IGNITE-21670 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Major > > This method is probably some legacy remnant after table schema has been moved > away from the configuration. Currently this method is always called after an > instance of MvTableStorage is created and does nothing useful, all its code > can be moved to the corresponding constructors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21670) Remove MvTableStorage#start method
Aleksandr Polovtcev created IGNITE-21670: Summary: Remove MvTableStorage#start method Key: IGNITE-21670 URL: https://issues.apache.org/jira/browse/IGNITE-21670 Project: Ignite Issue Type: Improvement Reporter: Aleksandr Polovtcev Assignee: Aleksandr Polovtcev This method is probably some legacy remnant after table schema has been moved away from the configuration. Currently this method is always called after an instance of MvTableStorage is created and does nothing useful, all its code can be moved to the corresponding constructors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21501) Create index storages for new partitions on rebalance
[
https://issues.apache.org/jira/browse/IGNITE-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko reassigned IGNITE-21501:
Assignee: Kirill Tkalenko
> Create index storages for new partitions on rebalance
> -
>
> Key: IGNITE-21501
> URL: https://issues.apache.org/jira/browse/IGNITE-21501
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Bessonov
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
>
> It appears that we only create index storages during the "table creation",
> not during the "partition creation" if it's performed in isolation.
> Even if we did,
> {{org.apache.ignite.internal.table.distributed.index.IndexUpdateHandler#waitIndexes}}
> is still badly designed, because it waits for indexes of the initial
> partitions distribution and cannot provide any guarantees when assignments
> are changed.
> This leads to NPEs or bizarre assertions, related to aforementioned method.
> What we need to do is:
> * Get rid of the faulty index awaiting mechanizm.
> * Create index storages before starting raft group.
> * [optional] There might be naturally occurring "races" between catalog
> updates (index creation) and rebalance. Right now they are resolved by the
> fact that these processes are linearized in watch processing, but that's not
> the best approach. If we could provide something more robust, that would have
> been nice. Let's think about it at least.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21501) Create index storages for new partitions on rebalance
[
https://issues.apache.org/jira/browse/IGNITE-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-21501:
-
Fix Version/s: 3.0.0-beta2
> Create index storages for new partitions on rebalance
> -
>
> Key: IGNITE-21501
> URL: https://issues.apache.org/jira/browse/IGNITE-21501
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Bessonov
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> It appears that we only create index storages during the "table creation",
> not during the "partition creation" if it's performed in isolation.
> Even if we did,
> {{org.apache.ignite.internal.table.distributed.index.IndexUpdateHandler#waitIndexes}}
> is still badly designed, because it waits for indexes of the initial
> partitions distribution and cannot provide any guarantees when assignments
> are changed.
> This leads to NPEs or bizarre assertions, related to aforementioned method.
> What we need to do is:
> * Get rid of the faulty index awaiting mechanizm.
> * Create index storages before starting raft group.
> * [optional] There might be naturally occurring "races" between catalog
> updates (index creation) and rebalance. Right now they are resolved by the
> fact that these processes are linearized in watch processing, but that's not
> the best approach. If we could provide something more robust, that would have
> been nice. Let's think about it at least.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21671) Remove destroyed indexes on recovery
Aleksandr Polovtcev created IGNITE-21671: Summary: Remove destroyed indexes on recovery Key: IGNITE-21671 URL: https://issues.apache.org/jira/browse/IGNITE-21671 Project: Ignite Issue Type: Improvement Reporter: Aleksandr Polovtcev Assignee: Aleksandr Polovtcev -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-15179) Thin 3.0: Implement createTable
[
https://issues.apache.org/jira/browse/IGNITE-15179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego resolved IGNITE-15179.
--
Resolution: Won't Fix
There is not going to be createTable. Instead, user can use SQL API or ORM for
table creation.
> Thin 3.0: Implement createTable
> ---
>
> Key: IGNITE-15179
> URL: https://issues.apache.org/jira/browse/IGNITE-15179
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 3.0.0-alpha3
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: iep-76, ignite-3
>
> Implement {{IgniteTables#createTable}} with full configuration support.
> Investigate whether {{Consumer}} API should be changed - there
> were some plans for that on the dev list.
> https://lists.apache.org/thread.html/rc8b28cf0ae7988831ea3867793a5ea72dfd062e8769c1d32f371fc16%40%3Cdev.ignite.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21651) Fix ItSslClientHandlerTest on Java 21
[ https://issues.apache.org/jira/browse/IGNITE-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823551#comment-17823551 ] Roman Puchkovskiy commented on IGNITE-21651: Thank you > Fix ItSslClientHandlerTest on Java 21 > - > > Key: IGNITE-21651 > URL: https://issues.apache.org/jira/browse/IGNITE-21651 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > Netty uses OpenJDK internal classes to implement TLS; doing so, it uses > Reflection to invoke their methods. In Java 21, one of the needed methods > (set()) does not exist anymore, so OpenJDK's classes cannot be used anymore. > > We should switch to BouncyCastle by adding it to the classpath. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21526) .NET: Clean up IEP-54 leftovers
[ https://issues.apache.org/jira/browse/IGNITE-21526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823561#comment-17823561 ] Igor Sapego commented on IGNITE-21526: -- Looks good to me. > .NET: Clean up IEP-54 leftovers > --- > > Key: IGNITE-21526 > URL: https://issues.apache.org/jira/browse/IGNITE-21526 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > Implement IGNITE-19744 for .NET Client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21458) Up to 25% performance drop in key-value operations (embedded node)
[
https://issues.apache.org/jira/browse/IGNITE-21458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823576#comment-17823576
]
Ivan Artiukhov commented on IGNITE-21458:
-
It looks like the issue is fixed by IGNITE-20373.
> Up to 25% performance drop in key-value operations (embedded node)
> --
>
> Key: IGNITE-21458
> URL: https://issues.apache.org/jira/browse/IGNITE-21458
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Ivan Artiukhov
>Priority: Major
> Labels: ignite-3, performance
> Attachments: 1-put-3cbec4fe80878765a50beeae09f6b352ebf718ec.png,
> 2-get-3cbec4fe80878765a50beeae09f6b352ebf718ec.png,
> 3-put-721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06.png,
> 4-get-721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06.png
>
>
> AI3 rev.
> 3cbec4fe80878765a50beeae09f6b352ebf718ec and
> 721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06
>
> Benchmark:
> [https://github.com/gridgain/YCSB/blob/ycsb-2024.1/ignite3/src/main/java/site/ycsb/db/ignite3/IgniteClient.java]
>
> The benchmark is started with {{{}useEmbedded=true{}}}, i.e. the Ignite 3
> node and the benchmark is started within the same JVM.
> The benchmark uses single key-value {{get}} and {{{}put{}}}.
> h1. Steps:
> Run the benchmark in {{load}} mode to put 300k entries using single key-value
> get() in 1 thread:
> {noformat}
> -db site.ycsb.db.ignite3.IgniteClient -load -P
> /opt/pubagent/poc/config/ycsb/workloads/workloadc -threads 1 -p
> recordcount=25 -p warmupops=5 -p dataintegrity=true -p
> measurementtype=timeseries -p status.interval=1 -p useEmbedded=true -p
> workDir=ignite3-work -p hosts=192.168.1.35 -s{noformat}
> Using the same persistence directory run the benchmark to get 300k entries
> using single key-value {{get():}}
> {noformat}
> -db site.ycsb.db.ignite3.IgniteClient -t -P
> /opt/pubagent/poc/config/ycsb/workloads/workloadc -threads 1 -p
> operationcount=25 -p recordcount=25 -p warmupops=5 -p
> dataintegrity=true -p measurementtype=timeseries -p status.interval=1 -p
> useEmbedded=true -p workDir=ignite3-work -p hosts=192.168.1.35 -s{noformat}
> h1. Results
> ||Operation||721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06||3cbec4fe80878765a50beeae09f6b352ebf718ec||
> |put()|!3-put-721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06.png!|!1-put-3cbec4fe80878765a50beeae09f6b352ebf718ec.png!|
> |get()|!4-get-721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06.png!|!2-get-3cbec4fe80878765a50beeae09f6b352ebf718ec.png!|
> See the drop the performance in
> 3cbec4fe80878765a50beeae09f6b352ebf718ec.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21673) Sql. Do not allow duplicate column names in unique column list of a primary key constraint.
[ https://issues.apache.org/jira/browse/IGNITE-21673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-21673: -- Description: SQL standard does not allow to include the same column multiple times in column list of a primary key. AI-3 accepts multiple columns with the same name, because it deduplicates them. Let's update DDL command to catalog command conversion to be consistent with the standard. was: SQL standard does not allows to include the same column multiple times in column list of a primary key. AI-3 accepts multiple columns, because it it deduplicates them. Let's update DDL command to catalog command convertion to be consistent with the standard. > Sql. Do not allow duplicate column names in unique column list of a primary > key constraint. > > > Key: IGNITE-21673 > URL: https://issues.apache.org/jira/browse/IGNITE-21673 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > > SQL standard does not allow to include the same column multiple times in > column list of a primary key. > AI-3 accepts multiple columns with the same name, because it deduplicates > them. Let's update DDL command to catalog command conversion to be consistent > with the standard. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21671) Remove destroyed PageMemory indexes on recovery
[
https://issues.apache.org/jira/browse/IGNITE-21671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-21671:
-
Description:
When {{AbstractPageMemoryMvPartitionStorage}} is started, we need to perform
the following recovery actions:
# Scan the index meta tree;
# Check the observable Catalog history (i.e. up to the LWM value);
# If an index is present in the meta tree, but not in the Catalog - destroy it.
> Remove destroyed PageMemory indexes on recovery
> ---
>
> Key: IGNITE-21671
> URL: https://issues.apache.org/jira/browse/IGNITE-21671
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> When {{AbstractPageMemoryMvPartitionStorage}} is started, we need to perform
> the following recovery actions:
> # Scan the index meta tree;
> # Check the observable Catalog history (i.e. up to the LWM value);
> # If an index is present in the meta tree, but not in the Catalog - destroy
> it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21634) NPE in HeapLockManager
[
https://issues.apache.org/jira/browse/IGNITE-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823530#comment-17823530
]
Mirza Aliev commented on IGNITE-21634:
--
Seems like fix is trivial,
{code:java}
locks.compute(key, (k, v) -> {
if (v == null) {
v = empty.poll();
if (v == null) {
res[0] = slots[index];
} else {
v.markedForRemove = false;
v.key = k;
res[0] = v;
}
} else {
res[0] = v;
}
return v;
});
{code}
> NPE in HeapLockManager
> --
>
> Key: IGNITE-21634
> URL: https://issues.apache.org/jira/browse/IGNITE-21634
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Priority: Major
> Labels: ignite-3
>
> {code:java}
> Caused by: java.lang.NullPointerException at
> org.apache.ignite.internal.tx.impl.HeapLockManager.lambda$lockState$4(HeapLockManager.java:297)
> ~[main/:?] at
> java.util.concurrent.ConcurrentHashMap.compute(ConcurrentHashMap.java:1908)
> ~[?:?] at
> org.apache.ignite.internal.tx.impl.HeapLockManager.lockState(HeapLockManager.java:291)
> ~[main/:?] at
> org.apache.ignite.internal.tx.impl.HeapLockManager.acquire(HeapLockManager.java:172)
> ~[main/:?] at
> org.apache.ignite.internal.table.distributed.SortedIndexLocker.lambda$locksForInsert$4(SortedIndexLocker.java:169)
> ~[main/:?] at
> java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
> ~[?:?] ... 29 more{code}
> on the line {{v.markedForRemove = false;}}
> {code:java}
> private LockState lockState(LockKey key) {
> int h = spread(key.hashCode());
> int index = h & (slots.length - 1);
> LockState[] res = new LockState[1];
> locks.compute(key, (k, v) -> {
> if (v == null) {
> if (empty.isEmpty()) {
> res[0] = slots[index];
> } else {
> v = empty.poll();
> v.markedForRemove = false;
> v.key = k;
> res[0] = v;
> }
> } else {
> res[0] = v;
> }
> return v;
> });
> return res[0];
> } {code}
> The problem can be reproduced on main(71b4fb34) with following test
> (probably, fsync should be turned off):
> {code}
> @Test
> void test() {
> sql("CREATE TABLE test("
> + "c1 INT PRIMARY KEY, c2 INT, c3 INT, c4 INT, c5 INT,"
> + "c6 INT, c7 INT, c8 INT, c9 INT, c10 INT)"
> );
> for (int i = 2; i <= 10; i++) {
> sql(format("CREATE INDEX c{}_idx ON test (c{})", i, i));
> }
> sql("INSERT INTO test"
> + " SELECT x as c1, x as c2, x as c3, x as c4, x as c5, "
> + "x as c6, x as c7, x as c8, x as c9, x as c10"
> + " FROM TABLE (system_range(1, 10))");
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-21641) OOM in PartitionReplicaListenerTest
[
https://issues.apache.org/jira/browse/IGNITE-21641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov reassigned IGNITE-21641:
-
Assignee: Denis Chudov
> OOM in PartitionReplicaListenerTest
> ---
>
> Key: IGNITE-21641
> URL: https://issues.apache.org/jira/browse/IGNITE-21641
> Project: Ignite
> Issue Type: Bug
>Reporter: Mirza Aliev
>Assignee: Denis Chudov
>Priority: Major
> Labels: ignite-3
> Attachments: image-2024-03-01-12-22-32-053.png,
> image-2024-03-01-20-36-08-577.png
>
>
> TC run failed with OOM
> Problem occurred after
> PartitionReplicaListenerTest.testReadOnlyGetAfterRowRewrite run,
> {noformat}
> [2024-03-01T05:12:50,629][INFO ][Test worker][PartitionReplicaListenerTest]
> >>> Starting test:
> PartitionReplicaListenerTest#testReadOnlyGetAfterRowRewrite, displayName:
> [14] true, true, false, true
> [2024-03-01T05:12:50,629][INFO ][Test worker][PartitionReplicaListenerTest]
> workDir:
> build/work/PartitionReplicaListenerTest/testReadOnlyGetAfterRowRewrite_33496469368142283
> [2024-03-01T05:12:50,638][INFO ][Test worker][PartitionReplicaListenerTest]
> >>> Stopping test:
> PartitionReplicaListenerTest#testReadOnlyGetAfterRowRewrite, displayName:
> [14] true, true, false, true, cost: 8ms.
> [05:12:50] : [testReadOnlyGetAfterRowRewrite(boolean,
> boolean, boolean, boolean)]
> org.apache.ignite.internal.table.distributed.replication.PartitionReplicaListenerTest.testReadOnlyGetAfterRowRewrite([15]
> true, true, true, false) (10m:22s)
> [05:12:50] : [:ignite-table:test] PartitionReplicaListenerTest >
> testReadOnlyGetAfterRowRewrite(boolean, boolean, boolean, boolean) > [15]
> true, true, true, false STANDARD_OUT
> [05:12:50] : [:ignite-table:test]
> [2024-03-01T05:12:50,648][INFO ][Test worker][PartitionReplicaListenerTest]
> >>> Starting test:
> PartitionReplicaListenerTest#testReadOnlyGetAfterRowRewrite, displayName:
> [15] true, true, true, false
> [05:12:50] : [:ignite-table:test]
> [2024-03-01T05:12:50,648][INFO ][Test worker][PartitionReplicaListenerTest]
> workDir:
> build/work/PartitionReplicaListenerTest/testReadOnlyGetAfterRowRewrite_33496469386328241
> [05:18:42] : [:ignite-table:test] java.lang.OutOfMemoryError: Java
> heap space
> [05:18:42] : [:ignite-table:test] Dumping heap to
> java_pid2349600.hprof ...
> [05:19:06] : [:ignite-table:test] Heap dump file created
> [3645526743 bytes in 24.038 secs]
> {noformat}
> https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7898564?hideTestsFromDependencies=false=false+Inspection=true=true=true=false
> After analysing heap dump it appears that the reason of OOM is a problem with
> Mockito.
> !image-2024-03-01-12-22-32-053.png!
> We need to investigate the reason of a problem with Mockito
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21120) Add a system view to list available indexes
[ https://issues.apache.org/jira/browse/IGNITE-21120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21120: --- Description: The view should be called 'indexes'. It will only display the indexes which are currently alive (that is, REGISTERED, BUILDING or AVAILABLE). The view should contain the following columns: # index_id (INT) # index_name (VARCHAR) # table_id (INT) # table_name (VARCHAR) [at the moment of the query to the view is executed] # schema_id (INT) # schema_name (VARCHAR) # type (VARCHAR, allowed values are 'hash' or 'sorted') # is_unique (BOOLEAN) # columns (VARCHAR) (for a hash index, just a list of column names separated with commas [like 'first_name, last_name']; for a sorted index, a list of column names with their collations, like 'first_name ASC, last_name DESC') # status (VARCHAR) was: The view should be called 'indexes'. It will only display the indexes which are currently alive (that is, REGISTERED, BUILDING or AVAILABLE). The view should contain the following columns: # index_id (INT) # index_name (VARCHAR) # table_id (INT) # table_name (VARCHAR) [at the moment of the query to the view is executed] # schema_id (INT) # schema_name (VARCHAR) # type (VARCHAR, allowed values are 'hash' or 'sorted') # unique (BOOLEAN) # columns (VARCHAR) (for a hash index, just a list of column names separated with commas [like 'first_name, last_name']; for a sorted index, a list of column names with their collations, like 'first_name ASC, last_name DESC') # status (VARCHAR) > Add a system view to list available indexes > --- > > Key: IGNITE-21120 > URL: https://issues.apache.org/jira/browse/IGNITE-21120 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Philipp Shergalis >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The view should be called 'indexes'. It will only display the indexes which > are currently alive (that is, REGISTERED, BUILDING or AVAILABLE). > The view should contain the following columns: > # index_id (INT) > # index_name (VARCHAR) > # table_id (INT) > # table_name (VARCHAR) [at the moment of the query to the view is executed] > # schema_id (INT) > # schema_name (VARCHAR) > # type (VARCHAR, allowed values are 'hash' or 'sorted') > # is_unique (BOOLEAN) > # columns (VARCHAR) (for a hash index, just a list of column names separated > with commas [like 'first_name, last_name']; for a sorted index, a list of > column names with their collations, like 'first_name ASC, last_name DESC') > # status (VARCHAR) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21576) Unmute tests after index removal API is implemented
[ https://issues.apache.org/jira/browse/IGNITE-21576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-21576: - Fix Version/s: 3.0.0-beta2 > Unmute tests after index removal API is implemented > --- > > Key: IGNITE-21576 > URL: https://issues.apache.org/jira/browse/IGNITE-21576 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > I've disabled some tests with a link pointing to this ticket. These tests > must be unmuted after IGNITE-21574 and IGNITE-21583 are fixed -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21673) Sql. Do not allow duplicate column names in unique column list of a primary key constraint.
[ https://issues.apache.org/jira/browse/IGNITE-21673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-21673: -- Issue Type: Improvement (was: Bug) > Sql. Do not allow duplicate column names in unique column list of a primary > key constraint. > > > Key: IGNITE-21673 > URL: https://issues.apache.org/jira/browse/IGNITE-21673 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > > SQL standard does not allows to include the same column multiple times in > column list of a primary key. > AI-3 accepts multiple columns, because it it deduplicates them. Let's update > DDL command to catalog command convertion to be consistent with the standard. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21673) Sql. Do not allow duplicate column names in unique column list of a primary key constraint.
[ https://issues.apache.org/jira/browse/IGNITE-21673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-21673: -- Labels: ignite-3 (was: ) > Sql. Do not allow duplicate column names in unique column list of a primary > key constraint. > > > Key: IGNITE-21673 > URL: https://issues.apache.org/jira/browse/IGNITE-21673 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > > SQL standard does not allows to include the same column multiple times in > column list of a primary key. > AI-3 accepts multiple columns, because it it deduplicates them. Let's update > DDL command to catalog command convertion to be consistent with the standard. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-17134) Thin 3.0: Implement client SQL session management
[ https://issues.apache.org/jira/browse/IGNITE-17134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego resolved IGNITE-17134. -- Resolution: Won't Fix It was decided to remove SQL sessions altogether: IGNITE-21669 > Thin 3.0: Implement client SQL session management > - > > Key: IGNITE-17134 > URL: https://issues.apache.org/jira/browse/IGNITE-17134 > Project: Ignite > Issue Type: Improvement > Components: sql, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Minor > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Close all active cursors and cancel queries when client SQL session is closed -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-3) Need to add separate configuration bean to all the SPIs
[ https://issues.apache.org/jira/browse/IGNITE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-3: -- Labels: IGNITE-20970 IGNITE-21657 IGNITE-21672 (was: IGNITE-20970 IGNITE-21657) > Need to add separate configuration bean to all the SPIs > --- > > Key: IGNITE-3 > URL: https://issues.apache.org/jira/browse/IGNITE-3 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Setrakyan >Assignee: Dmitriy Setrakyan >Priority: Major > Labels: IGNITE-20970, IGNITE-21657, IGNITE-21672 > Fix For: sprint-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21672) Sql. Support NULLS FIRST / NULLS LAST options in primary key / index definition.
Maksim Zhuravkov created IGNITE-21672: - Summary: Sql. Support NULLS FIRST / NULLS LAST options in primary key / index definition. Key: IGNITE-21672 URL: https://issues.apache.org/jira/browse/IGNITE-21672 Project: Ignite Issue Type: Improvement Components: sql Reporter: Maksim Zhuravkov Add support for NULLS FIRST / NULLS LASTS options in SQL for both primary key and index definition, when storage index API is ready. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21672) Sql. Support NULLS FIRST / NULLS LAST options in primary key / index definition.
[ https://issues.apache.org/jira/browse/IGNITE-21672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-21672: -- Fix Version/s: 3.0.0-beta2 > Sql. Support NULLS FIRST / NULLS LAST options in primary key / index > definition. > - > > Key: IGNITE-21672 > URL: https://issues.apache.org/jira/browse/IGNITE-21672 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Add support for NULLS FIRST / NULLS LASTS options in SQL for both primary key > and index definition, when storage index API is ready. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-3) Need to add separate configuration bean to all the SPIs
[ https://issues.apache.org/jira/browse/IGNITE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-3: -- Labels: (was: IGNITE-20970 IGNITE-21657 IGNITE-21672) > Need to add separate configuration bean to all the SPIs > --- > > Key: IGNITE-3 > URL: https://issues.apache.org/jira/browse/IGNITE-3 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Setrakyan >Assignee: Dmitriy Setrakyan >Priority: Major > Fix For: sprint-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21672) Sql. Support NULLS FIRST / NULLS LAST options in primary key / index definition.
[ https://issues.apache.org/jira/browse/IGNITE-21672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-21672: -- Labels: ignite-3 (was: ) > Sql. Support NULLS FIRST / NULLS LAST options in primary key / index > definition. > - > > Key: IGNITE-21672 > URL: https://issues.apache.org/jira/browse/IGNITE-21672 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > > Add support for NULLS FIRST / NULLS LASTS options in SQL for both primary key > and index definition, when storage index API is ready. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21667) It is impossible to use NetworkMessage implementatation with 0 fields
[
https://issues.apache.org/jira/browse/IGNITE-21667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-21667:
---
Labels: ignite-3 tech-debt (was: ignite-3)
> It is impossible to use NetworkMessage implementatation with 0 fields
> -
>
> Key: IGNITE-21667
> URL: https://issues.apache.org/jira/browse/IGNITE-21667
> Project: Ignite
> Issue Type: Bug
> Components: networking
>Reporter: Roman Puchkovskiy
>Priority: Major
> Labels: ignite-3, tech-debt
>
> public interface ProbeMessage extends InternalMessage {
> }
> When sending such a message, the receiving side fails:
>
> io.netty.handler.codec.DecoderException: InboundDecoder.decode() did not read
> anything but decoded a message.
> at
> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:488)
> ~[netty-codec-4.1.107.Final.jar:4.1.107.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:290)
> ~[netty-codec-4.1.107.Final.jar:4.1.107.Final]
>
> If there is at least one field, everything works.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21673) Sql. Do not allow duplicate column names in unique column list of a primary key constraint.
Maksim Zhuravkov created IGNITE-21673: - Summary: Sql. Do not allow duplicate column names in unique column list of a primary key constraint. Key: IGNITE-21673 URL: https://issues.apache.org/jira/browse/IGNITE-21673 Project: Ignite Issue Type: Bug Components: sql Reporter: Maksim Zhuravkov SQL standard does not allows to include the same column multiple times in column list of a primary key. AI-3 accepts multiple columns, because it it deduplicates them. Let's update DDL command to catalog command convertion to be consistent with the standard. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-21458) Up to 25% performance drop in key-value operations (embedded node)
[
https://issues.apache.org/jira/browse/IGNITE-21458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Artiukhov closed IGNITE-21458.
---
> Up to 25% performance drop in key-value operations (embedded node)
> --
>
> Key: IGNITE-21458
> URL: https://issues.apache.org/jira/browse/IGNITE-21458
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Ivan Artiukhov
>Priority: Major
> Labels: ignite-3, performance
> Attachments: 1-put-3cbec4fe80878765a50beeae09f6b352ebf718ec.png,
> 2-get-3cbec4fe80878765a50beeae09f6b352ebf718ec.png,
> 3-put-721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06.png,
> 4-get-721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06.png
>
>
> AI3 rev.
> 3cbec4fe80878765a50beeae09f6b352ebf718ec and
> 721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06
>
> Benchmark:
> [https://github.com/gridgain/YCSB/blob/ycsb-2024.1/ignite3/src/main/java/site/ycsb/db/ignite3/IgniteClient.java]
>
> The benchmark is started with {{{}useEmbedded=true{}}}, i.e. the Ignite 3
> node and the benchmark is started within the same JVM.
> The benchmark uses single key-value {{get}} and {{{}put{}}}.
> h1. Steps:
> Run the benchmark in {{load}} mode to put 300k entries using single key-value
> get() in 1 thread:
> {noformat}
> -db site.ycsb.db.ignite3.IgniteClient -load -P
> /opt/pubagent/poc/config/ycsb/workloads/workloadc -threads 1 -p
> recordcount=25 -p warmupops=5 -p dataintegrity=true -p
> measurementtype=timeseries -p status.interval=1 -p useEmbedded=true -p
> workDir=ignite3-work -p hosts=192.168.1.35 -s{noformat}
> Using the same persistence directory run the benchmark to get 300k entries
> using single key-value {{get():}}
> {noformat}
> -db site.ycsb.db.ignite3.IgniteClient -t -P
> /opt/pubagent/poc/config/ycsb/workloads/workloadc -threads 1 -p
> operationcount=25 -p recordcount=25 -p warmupops=5 -p
> dataintegrity=true -p measurementtype=timeseries -p status.interval=1 -p
> useEmbedded=true -p workDir=ignite3-work -p hosts=192.168.1.35 -s{noformat}
> h1. Results
> ||Operation||721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06||3cbec4fe80878765a50beeae09f6b352ebf718ec||
> |put()|!3-put-721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06.png!|!1-put-3cbec4fe80878765a50beeae09f6b352ebf718ec.png!|
> |get()|!4-get-721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06.png!|!2-get-3cbec4fe80878765a50beeae09f6b352ebf718ec.png!|
> See the drop the performance in
> 3cbec4fe80878765a50beeae09f6b352ebf718ec.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-21458) Up to 25% performance drop in key-value operations (embedded node)
[
https://issues.apache.org/jira/browse/IGNITE-21458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Artiukhov resolved IGNITE-21458.
-
Resolution: Cannot Reproduce
> Up to 25% performance drop in key-value operations (embedded node)
> --
>
> Key: IGNITE-21458
> URL: https://issues.apache.org/jira/browse/IGNITE-21458
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Ivan Artiukhov
>Priority: Major
> Labels: ignite-3, performance
> Attachments: 1-put-3cbec4fe80878765a50beeae09f6b352ebf718ec.png,
> 2-get-3cbec4fe80878765a50beeae09f6b352ebf718ec.png,
> 3-put-721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06.png,
> 4-get-721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06.png
>
>
> AI3 rev.
> 3cbec4fe80878765a50beeae09f6b352ebf718ec and
> 721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06
>
> Benchmark:
> [https://github.com/gridgain/YCSB/blob/ycsb-2024.1/ignite3/src/main/java/site/ycsb/db/ignite3/IgniteClient.java]
>
> The benchmark is started with {{{}useEmbedded=true{}}}, i.e. the Ignite 3
> node and the benchmark is started within the same JVM.
> The benchmark uses single key-value {{get}} and {{{}put{}}}.
> h1. Steps:
> Run the benchmark in {{load}} mode to put 300k entries using single key-value
> get() in 1 thread:
> {noformat}
> -db site.ycsb.db.ignite3.IgniteClient -load -P
> /opt/pubagent/poc/config/ycsb/workloads/workloadc -threads 1 -p
> recordcount=25 -p warmupops=5 -p dataintegrity=true -p
> measurementtype=timeseries -p status.interval=1 -p useEmbedded=true -p
> workDir=ignite3-work -p hosts=192.168.1.35 -s{noformat}
> Using the same persistence directory run the benchmark to get 300k entries
> using single key-value {{get():}}
> {noformat}
> -db site.ycsb.db.ignite3.IgniteClient -t -P
> /opt/pubagent/poc/config/ycsb/workloads/workloadc -threads 1 -p
> operationcount=25 -p recordcount=25 -p warmupops=5 -p
> dataintegrity=true -p measurementtype=timeseries -p status.interval=1 -p
> useEmbedded=true -p workDir=ignite3-work -p hosts=192.168.1.35 -s{noformat}
> h1. Results
> ||Operation||721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06||3cbec4fe80878765a50beeae09f6b352ebf718ec||
> |put()|!3-put-721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06.png!|!1-put-3cbec4fe80878765a50beeae09f6b352ebf718ec.png!|
> |get()|!4-get-721b7ad6fc507c5f5e3b0129a68c5ed25ee14c06.png!|!2-get-3cbec4fe80878765a50beeae09f6b352ebf718ec.png!|
> See the drop the performance in
> 3cbec4fe80878765a50beeae09f6b352ebf718ec.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21671) Remove destroyed PageMemory indexes on recovery
[ https://issues.apache.org/jira/browse/IGNITE-21671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-21671: - Summary: Remove destroyed PageMemory indexes on recovery (was: Remove destroyed indexes on recovery) > Remove destroyed PageMemory indexes on recovery > --- > > Key: IGNITE-21671 > URL: https://issues.apache.org/jira/browse/IGNITE-21671 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21671) Remove destroyed indexes on recovery
[ https://issues.apache.org/jira/browse/IGNITE-21671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-21671: - Fix Version/s: 3.0.0-beta2 > Remove destroyed indexes on recovery > > > Key: IGNITE-21671 > URL: https://issues.apache.org/jira/browse/IGNITE-21671 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21672) Sql. Support NULLS FIRST / NULLS LAST options in primary key / index definition.
[ https://issues.apache.org/jira/browse/IGNITE-21672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-21672: -- Fix Version/s: (was: 3.0.0-beta2) > Sql. Support NULLS FIRST / NULLS LAST options in primary key / index > definition. > - > > Key: IGNITE-21672 > URL: https://issues.apache.org/jira/browse/IGNITE-21672 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > > Add support for NULLS FIRST / NULLS LASTS options in SQL for both primary key > and index definition, when storage index API is ready. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21674) Subcommand completion is broken in CLI
Aleksandr created IGNITE-21674: -- Summary: Subcommand completion is broken in CLI Key: IGNITE-21674 URL: https://issues.apache.org/jira/browse/IGNITE-21674 Project: Ignite Issue Type: Bug Components: cli Reporter: Aleksandr Steps to reproduce: - build cli from main - run interactive mode - (all commands are suggested, it is ok) - choose "cluster" - only one subcommand are completed (all cluster * subcommands expected) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21526) .NET: Clean up IEP-54 leftovers
[ https://issues.apache.org/jira/browse/IGNITE-21526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823581#comment-17823581 ] Pavel Tupitsyn commented on IGNITE-21526: - Merged to main: e7746cf275a65a611b83ca6453aee2c3be08c000 > .NET: Clean up IEP-54 leftovers > --- > > Key: IGNITE-21526 > URL: https://issues.apache.org/jira/browse/IGNITE-21526 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > Implement IGNITE-19744 for .NET Client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21120) Add a system view to list available indexes
[ https://issues.apache.org/jira/browse/IGNITE-21120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823656#comment-17823656 ] Roman Puchkovskiy commented on IGNITE-21120: The patch looks good to me > Add a system view to list available indexes > --- > > Key: IGNITE-21120 > URL: https://issues.apache.org/jira/browse/IGNITE-21120 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Philipp Shergalis >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 1h > Remaining Estimate: 0h > > The view should be called 'indexes'. It will only display the indexes which > are currently alive (that is, REGISTERED, BUILDING or AVAILABLE). > The view should contain the following columns: > # index_id (INT) > # index_name (VARCHAR) > # table_id (INT) > # table_name (VARCHAR) [at the moment of the query to the view is executed] > # schema_id (INT) > # schema_name (VARCHAR) > # type (VARCHAR, allowed values are 'hash' or 'sorted') > # is_unique (BOOLEAN) > # columns (VARCHAR) (for a hash index, just a list of column names separated > with commas [like 'first_name, last_name']; for a sorted index, a list of > column names with their collations, like 'first_name ASC, last_name DESC') > # status (VARCHAR) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21676) Sql. Move system view definitions to a separate package of a catalog module
[ https://issues.apache.org/jira/browse/IGNITE-21676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-21676: -- Labels: ignite-3 (was: ) > Sql. Move system view definitions to a separate package of a catalog module > --- > > Key: IGNITE-21676 > URL: https://issues.apache.org/jira/browse/IGNITE-21676 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Maksim Zhuravkov >Priority: Minor > Labels: ignite-3 > > Let's move code related to system view definitions to a separate package, so > CatalogManagerImpl > only contains an implementation of SystemViewProvider interface/or a list of > a "imports" of system view definitions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21676) Sql. Move system view definitions to a separate package of a catalog module
Maksim Zhuravkov created IGNITE-21676: - Summary: Sql. Move system view definitions to a separate package of a catalog module Key: IGNITE-21676 URL: https://issues.apache.org/jira/browse/IGNITE-21676 Project: Ignite Issue Type: Improvement Components: sql Reporter: Maksim Zhuravkov Let's move code related to system view definitions to a separate package, so CatalogManagerImpl only contains an implementation of SystemViewProvider interface/or a list of a "imports" of system view definitions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IGNITE-21668) Sql. Deadlock in sorted exchange
[
https://issues.apache.org/jira/browse/IGNITE-21668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov reopened IGNITE-21668:
---
> Sql. Deadlock in sorted exchange
>
>
> Key: IGNITE-21668
> URL: https://issues.apache.org/jira/browse/IGNITE-21668
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Assume the following execution graph:
> {code:java}
> f1n1 f1n2
>| X |
> f2n3 f2n4
> {code}
> For simplicity, let there be only one column of type integer. If data both
> distributed and sorted by this very column, then we may end up in a
> situation, where exchange won't be able to proceed because every fragment
> will be blocked by another party. In the example above, let f1n1 expects odd
> numbers, while f1n2 expects even. If f2n3 contains only odd numbers, and f2n4
> contains only even numbers, then both exchanges will never get response from
> another party, thus won't be able to proceed.
> Proposed solution is to disable order-preserving exchange in cases where
> target distribution is not single.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21677) Fix NPE in ActiveActorTest
Roman Puchkovskiy created IGNITE-21677: -- Summary: Fix NPE in ActiveActorTest Key: IGNITE-21677 URL: https://issues.apache.org/jira/browse/IGNITE-21677 Project: Ignite Issue Type: Bug Reporter: Roman Puchkovskiy Assignee: Roman Puchkovskiy Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21677) Fix NPE in ActiveActorTest
[ https://issues.apache.org/jira/browse/IGNITE-21677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-21677: --- Description: An NPE is thrown when ActiveActorTest is run, it happens during AssignmentsTracker recovery because the mocked MetaStorageManager returns a null Cursor. > Fix NPE in ActiveActorTest > -- > > Key: IGNITE-21677 > URL: https://issues.apache.org/jira/browse/IGNITE-21677 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > An NPE is thrown when ActiveActorTest is run, it happens during > AssignmentsTracker recovery because the mocked MetaStorageManager returns a > null Cursor. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20870) Partition replica listener skips taking snapshot lock
[ https://issues.apache.org/jira/browse/IGNITE-20870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Pligin reassigned IGNITE-20870: Assignee: Roman Puchkovskiy > Partition replica listener skips taking snapshot lock > - > > Key: IGNITE-20870 > URL: https://issues.apache.org/jira/browse/IGNITE-20870 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > > See `SnapshotAwarePartitionDataStorage#acquirePartitionSnapshotsReadLock`. > Right now the data, that's being sent by snapshot reader, might be > inconsistent, because reads are not synchronized with writes. > There's a proposal to hide this lock somewhere inside data storage instance, > if possible. Anyway, data consistency must be fixed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21593) Update website docs search index
[ https://issues.apache.org/jira/browse/IGNITE-21593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Gusev resolved IGNITE-21593. - Resolution: Fixed > Update website docs search index > > > Key: IGNITE-21593 > URL: https://issues.apache.org/jira/browse/IGNITE-21593 > Project: Ignite > Issue Type: Improvement > Components: documentation, website >Reporter: Alexey Alexandrov >Priority: Major > > Current index of docs search returns unwanted results, for example > alternative results with 2.11.1 version for many queries, while we expect to > receive only the latest version results. > Let's replace it with the correct one. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21593) Update website docs search index
[ https://issues.apache.org/jira/browse/IGNITE-21593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Gusev reassigned IGNITE-21593: --- Assignee: Igor Gusev > Update website docs search index > > > Key: IGNITE-21593 > URL: https://issues.apache.org/jira/browse/IGNITE-21593 > Project: Ignite > Issue Type: Improvement > Components: documentation, website >Reporter: Alexey Alexandrov >Assignee: Igor Gusev >Priority: Major > > Current index of docs search returns unwanted results, for example > alternative results with 2.11.1 version for many queries, while we expect to > receive only the latest version results. > Let's replace it with the correct one. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21415) Remote nodes are not added to NodeManager
[ https://issues.apache.org/jira/browse/IGNITE-21415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov resolved IGNITE-21415. - Resolution: Invalid Actually, NodeManager must manage ony local nodes and it is not an issue > Remote nodes are not added to NodeManager > - > > Key: IGNITE-21415 > URL: https://issues.apache.org/jira/browse/IGNITE-21415 > Project: Ignite > Issue Type: Bug >Reporter: Denis Chudov >Priority: Major > Labels: ignite-3 > > org.apache.ignite.raft.jraft.NodeManager has the internal data structures > (groups to lists of nodes mapping, etc.) that are used for different > purposes, including processing the requests. But the remote nodes are not > adding to these mappings. See the usages of NodeManager#add method: it is > called only from RaftGroupService#start to add the local node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21291) Scan cursors do not close when an RO transaction is finalized
[ https://issues.apache.org/jira/browse/IGNITE-21291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823639#comment-17823639 ] Vladislav Pyatkov commented on IGNITE-21291: Merged 7bb9ecf6c53cf94b6ea105872831538b5912e455 > Scan cursors do not close when an RO transaction is finalized > - > > Key: IGNITE-21291 > URL: https://issues.apache.org/jira/browse/IGNITE-21291 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Kirill Sizov >Priority: Major > Labels: ignite-3 > Time Spent: 2h 50m > Remaining Estimate: 0h > > h3. Motivation > The cursors are opened on the server side and take up extra memory. When an > RW transaction is committed, we send the transaction cleanup messages to all > transaction participants. But the state of the RO transaction is strung > locally, so do not send any messages to the transaction participants (where > the cursors were opened). > h3. Definition of done > Cursors that were created by an RO transaction should be closed when the > transaction is no longer in use. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-20184) Move dataStorage configuration from zone to table configuration config
[ https://issues.apache.org/jira/browse/IGNITE-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov resolved IGNITE-20184. - Resolution: Won't Fix dataStorage configuration and params are not exist anymore, after IGNITE-21594 > Move dataStorage configuration from zone to table configuration config > --- > > Key: IGNITE-20184 > URL: https://issues.apache.org/jira/browse/IGNITE-20184 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > After IGNITE-19002 we decided to move the dataStorage configuration back, > because the clarification in the design of table-zone relations. Appropriate > tests for table dataStorage configuration should be restored too -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21675) Prevent Ignite threads from being leaked to user via async public APIs
Roman Puchkovskiy created IGNITE-21675: -- Summary: Prevent Ignite threads from being leaked to user via async public APIs Key: IGNITE-21675 URL: https://issues.apache.org/jira/browse/IGNITE-21675 Project: Ignite Issue Type: Improvement Reporter: Roman Puchkovskiy Assignee: Roman Puchkovskiy Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21678) IgniteToIgniteCdcStreamer fails if BinaryConfiguration is specified in config
Sergey Korotkov created IGNITE-21678:
Summary: IgniteToIgniteCdcStreamer fails if BinaryConfiguration is
specified in config
Key: IGNITE-21678
URL: https://issues.apache.org/jira/browse/IGNITE-21678
Project: Ignite
Issue Type: Bug
Reporter: Sergey Korotkov
Assignee: Sergey Korotkov
The below exception occurs:
{noformat}
2024-03-04T12:14:31,777][INFO ][Thread-0][] Ignite Change Data Capture
Application stopped.
[2024-03-04T12:14:31,782][ERROR][Thread-0][] Cdc error
org.apache.ignite.IgniteException: Failed to start manager: GridManagerAdapter
[enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1163)
~[classes/:?]
at org.apache.ignite.Ignition.start(Ignition.java:303) ~[classes/:?]
at
org.apache.ignite.cdc.IgniteToIgniteCdcStreamer.start(IgniteToIgniteCdcStreamer.java:86)
~[ignite-cdc-ext-1.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.cdc.WalRecordsConsumer.start(WalRecordsConsumer.java:192)
~[classes/:?]
at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:360)
~[classes/:?]
at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:306)
[classes/:?]
at java.base/java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
GridManagerAdapter [enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1777)
~[classes/:?]
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1159)
~[classes/:?]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
~[classes/:?]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
~[classes/:?]
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1089)
~[classes/:?]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:625)
~[classes/:?]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:547)
~[classes/:?]
at org.apache.ignite.Ignition.start(Ignition.java:300) ~[classes/:?]
... 5 more
Caused by: org.apache.ignite.IgniteCheckedException: Failed to start SPI:
TcpDiscoverySpi [addrRslvr=null, addressFilter=null, sockTimeout=5000,
ackTimeout=5000, marsh=JdkMarshaller
[clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@5f243268],
reconCnt=10, reconDelay=2000, maxAckTimeout=60, soLinger=0,
forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null,
skipAddrsRandomization=false]
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:280)
~[classes/:?]
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:1072)
~[classes/:?]
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1772)
~[classes/:?]
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1159)
~[classes/:?]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
~[classes/:?]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
~[classes/:?]
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1089)
~[classes/:?]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:625)
~[classes/:?]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:547)
~[classes/:?]
at org.apache.ignite.Ignition.start(Ignition.java:300) ~[classes/:?]
... 5 more
Caused by: org.apache.ignite.spi.IgniteSpiException: Local node's binary
configuration is not equal to remote node's binary configuration
[locNodeId=6eb40fd6-b20e-4485-a7f7-bb62e7e96abf,
rmtNodeId=e2f49ba1-6f99-4b75-8476-8bc925639527, locBinaryCfg=null,
rmtBinaryCfg={globIdMapper=null, compactFooter=true, globSerializer=null}]
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:2131)
~[classes/:?]
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1993)
~[classes/:?]
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
~[classes/:?]
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$1.body(ClientImpl.java:317)
~[classes/:?]
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:58)
~[classes/:?]
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21678) IgniteToIgniteCdcStreamer fails if BinaryConfiguration is specified in config
[
https://issues.apache.org/jira/browse/IGNITE-21678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Korotkov updated IGNITE-21678:
-
Description:
The below exception occurs if destination cluster has the explicit
BinaryConfiguration instance included into the IgniteConfiguration:
{noformat}
2024-03-04T12:14:31,777][INFO ][Thread-0][] Ignite Change Data Capture
Application stopped.
[2024-03-04T12:14:31,782][ERROR][Thread-0][] Cdc error
org.apache.ignite.IgniteException: Failed to start manager: GridManagerAdapter
[enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1163)
~[classes/:?]
at org.apache.ignite.Ignition.start(Ignition.java:303) ~[classes/:?]
at
org.apache.ignite.cdc.IgniteToIgniteCdcStreamer.start(IgniteToIgniteCdcStreamer.java:86)
~[ignite-cdc-ext-1.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.cdc.WalRecordsConsumer.start(WalRecordsConsumer.java:192)
~[classes/:?]
at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:360)
~[classes/:?]
at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:306)
[classes/:?]
at java.base/java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
GridManagerAdapter [enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1777)
~[classes/:?]
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1159)
~[classes/:?]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
~[classes/:?]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
~[classes/:?]
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1089)
~[classes/:?]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:625)
~[classes/:?]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:547)
~[classes/:?]
at org.apache.ignite.Ignition.start(Ignition.java:300) ~[classes/:?]
... 5 more
Caused by: org.apache.ignite.IgniteCheckedException: Failed to start SPI:
TcpDiscoverySpi [addrRslvr=null, addressFilter=null, sockTimeout=5000,
ackTimeout=5000, marsh=JdkMarshaller
[clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@5f243268],
reconCnt=10, reconDelay=2000, maxAckTimeout=60, soLinger=0,
forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null,
skipAddrsRandomization=false]
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:280)
~[classes/:?]
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:1072)
~[classes/:?]
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1772)
~[classes/:?]
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1159)
~[classes/:?]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
~[classes/:?]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
~[classes/:?]
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1089)
~[classes/:?]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:625)
~[classes/:?]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:547)
~[classes/:?]
at org.apache.ignite.Ignition.start(Ignition.java:300) ~[classes/:?]
... 5 more
Caused by: org.apache.ignite.spi.IgniteSpiException: Local node's binary
configuration is not equal to remote node's binary configuration
[locNodeId=6eb40fd6-b20e-4485-a7f7-bb62e7e96abf,
rmtNodeId=e2f49ba1-6f99-4b75-8476-8bc925639527, locBinaryCfg=null,
rmtBinaryCfg={globIdMapper=null, compactFooter=true, globSerializer=null}]
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:2131)
~[classes/:?]
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1993)
~[classes/:?]
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
~[classes/:?]
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$1.body(ClientImpl.java:317)
~[classes/:?]
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:58)
~[classes/:?]
{noformat}
was:
The below exception occurs:
{noformat}
2024-03-04T12:14:31,777][INFO ][Thread-0][] Ignite Change Data Capture
Application stopped.
[2024-03-04T12:14:31,782][ERROR][Thread-0][] Cdc error
org.apache.ignite.IgniteException: Failed to start manager: GridManagerAdapter
[enabled=true,
