[jira] [Resolved] (IGNITE-21821) Error: Partition file page store is either not initialized or deleted
[
https://issues.apache.org/jira/browse/IGNITE-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko resolved IGNITE-21821.
--
Resolution: Fixed
> Error: Partition file page store is either not initialized or deleted
> -
>
> Key: IGNITE-21821
> URL: https://issues.apache.org/jira/browse/IGNITE-21821
> Project: Ignite
> Issue Type: Improvement
>Reporter: Iurii Gerzhedovich
>Assignee: Kirill Tkalenko
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> During looking into log [one of TC
> run|https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7952341?hideTestsFromDependencies=false=false=true+Inspection=true=true=true=false]
> I found Error in log, which looks dangerous
> {code:java}
> ®[2024-03-20T11:15:35,893][ERROR][checkpoint-runner-io0][FailureProcessor]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [], failureCtx=FailureContext
> [type=CRITICAL_ERROR,
> err=org.apache.ignite.internal.lang.IgniteInternalCheckedException:
> IGN-CMN-65535 TraceId:64d96aba-9a18-420d-af54-dd3679466403 Partition file
> page store is either not initialized or deleted: [groupId=81,
> partitionId=19]]]
> org.apache.ignite.internal.lang.IgniteInternalCheckedException: Partition
> file page store is either not initialized or deleted: [groupId=81,
> partitionId=19]
> at
> org.apache.ignite.internal.pagememory.persistence.store.FilePageStoreManager.getStoreWithCheckExists(FilePageStoreManager.java:298)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.store.FilePageStoreManager.allocatePage(FilePageStoreManager.java:259)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.allocatePage(PersistentPageMemory.java:513)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.allocatePageNoReuse(DataStructure.java:193)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.allocatePage(DataStructure.java:174)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.addStripe(PagesList.java:589)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.getStripeForPut(PagesList.java:711)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.put(PagesList.java:815)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList$PutBucket.run(PagesList.java:173)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList$PutBucket.run(PagesList.java:147)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.util.PageHandler.writePage(PageHandler.java:298)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.write(DataStructure.java:296)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.flushBucketsCache(PagesList.java:387)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.saveMetadata(PagesList.java:332)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.pagememory.mv.RowVersionFreeList.saveMetadata(RowVersionFreeList.java:185)
> ~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.pagememory.mv.PersistentPageMemoryMvPartitionStorage.lambda$syncMetadataOnCheckpoint$13(PersistentPageMemoryMvPartitionStorage.java:367)
> ~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.checkpoint.AwaitTasksCompletionExecutor.lambda$execute$1(AwaitTasksCompletionExecutor.java:59)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> 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:834) [?:?] stderr
> tc:parseServiceMessagesInside,ãÌ7- Ž[’à
> ‰‰[2024-03-20T11:15:35,912][INFO
> ][%sqllogic0%JRaft-FSMCaller-Disruptor_stripe_8-0][StateMachineAdapter]
>
[jira] [Updated] (IGNITE-21821) Error: Partition file page store is either not initialized or deleted
[
https://issues.apache.org/jira/browse/IGNITE-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-21821:
-
Reviewer: Ivan Bessonov
> Error: Partition file page store is either not initialized or deleted
> -
>
> Key: IGNITE-21821
> URL: https://issues.apache.org/jira/browse/IGNITE-21821
> Project: Ignite
> Issue Type: Improvement
>Reporter: Iurii Gerzhedovich
>Assignee: Kirill Tkalenko
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> During looking into log [one of TC
> run|https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7952341?hideTestsFromDependencies=false=false=true+Inspection=true=true=true=false]
> I found Error in log, which looks dangerous
> {code:java}
> ®[2024-03-20T11:15:35,893][ERROR][checkpoint-runner-io0][FailureProcessor]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [], failureCtx=FailureContext
> [type=CRITICAL_ERROR,
> err=org.apache.ignite.internal.lang.IgniteInternalCheckedException:
> IGN-CMN-65535 TraceId:64d96aba-9a18-420d-af54-dd3679466403 Partition file
> page store is either not initialized or deleted: [groupId=81,
> partitionId=19]]]
> org.apache.ignite.internal.lang.IgniteInternalCheckedException: Partition
> file page store is either not initialized or deleted: [groupId=81,
> partitionId=19]
> at
> org.apache.ignite.internal.pagememory.persistence.store.FilePageStoreManager.getStoreWithCheckExists(FilePageStoreManager.java:298)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.store.FilePageStoreManager.allocatePage(FilePageStoreManager.java:259)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.allocatePage(PersistentPageMemory.java:513)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.allocatePageNoReuse(DataStructure.java:193)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.allocatePage(DataStructure.java:174)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.addStripe(PagesList.java:589)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.getStripeForPut(PagesList.java:711)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.put(PagesList.java:815)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList$PutBucket.run(PagesList.java:173)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList$PutBucket.run(PagesList.java:147)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.util.PageHandler.writePage(PageHandler.java:298)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.write(DataStructure.java:296)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.flushBucketsCache(PagesList.java:387)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.saveMetadata(PagesList.java:332)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.pagememory.mv.RowVersionFreeList.saveMetadata(RowVersionFreeList.java:185)
> ~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.pagememory.mv.PersistentPageMemoryMvPartitionStorage.lambda$syncMetadataOnCheckpoint$13(PersistentPageMemoryMvPartitionStorage.java:367)
> ~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.checkpoint.AwaitTasksCompletionExecutor.lambda$execute$1(AwaitTasksCompletionExecutor.java:59)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> 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:834) [?:?] stderr
> tc:parseServiceMessagesInside,ãÌ7- Ž[’à
> ‰‰[2024-03-20T11:15:35,912][INFO
> ][%sqllogic0%JRaft-FSMCaller-Disruptor_stripe_8-0][StateMachineAdapter]
[jira] [Updated] (IGNITE-21821) Error: Partition file page store is either not initialized or deleted
[
https://issues.apache.org/jira/browse/IGNITE-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-21821:
-
Fix Version/s: 3.0.0-beta2
> Error: Partition file page store is either not initialized or deleted
> -
>
> Key: IGNITE-21821
> URL: https://issues.apache.org/jira/browse/IGNITE-21821
> Project: Ignite
> Issue Type: Improvement
>Reporter: Iurii Gerzhedovich
>Assignee: Kirill Tkalenko
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> During looking into log [one of TC
> run|https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7952341?hideTestsFromDependencies=false=false=true+Inspection=true=true=true=false]
> I found Error in log, which looks dangerous
> {code:java}
> ®[2024-03-20T11:15:35,893][ERROR][checkpoint-runner-io0][FailureProcessor]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [], failureCtx=FailureContext
> [type=CRITICAL_ERROR,
> err=org.apache.ignite.internal.lang.IgniteInternalCheckedException:
> IGN-CMN-65535 TraceId:64d96aba-9a18-420d-af54-dd3679466403 Partition file
> page store is either not initialized or deleted: [groupId=81,
> partitionId=19]]]
> org.apache.ignite.internal.lang.IgniteInternalCheckedException: Partition
> file page store is either not initialized or deleted: [groupId=81,
> partitionId=19]
> at
> org.apache.ignite.internal.pagememory.persistence.store.FilePageStoreManager.getStoreWithCheckExists(FilePageStoreManager.java:298)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.store.FilePageStoreManager.allocatePage(FilePageStoreManager.java:259)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.allocatePage(PersistentPageMemory.java:513)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.allocatePageNoReuse(DataStructure.java:193)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.allocatePage(DataStructure.java:174)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.addStripe(PagesList.java:589)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.getStripeForPut(PagesList.java:711)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.put(PagesList.java:815)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList$PutBucket.run(PagesList.java:173)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList$PutBucket.run(PagesList.java:147)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.util.PageHandler.writePage(PageHandler.java:298)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.write(DataStructure.java:296)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.flushBucketsCache(PagesList.java:387)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.saveMetadata(PagesList.java:332)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.pagememory.mv.RowVersionFreeList.saveMetadata(RowVersionFreeList.java:185)
> ~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.pagememory.mv.PersistentPageMemoryMvPartitionStorage.lambda$syncMetadataOnCheckpoint$13(PersistentPageMemoryMvPartitionStorage.java:367)
> ~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.checkpoint.AwaitTasksCompletionExecutor.lambda$execute$1(AwaitTasksCompletionExecutor.java:59)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> 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:834) [?:?] stderr
> tc:parseServiceMessagesInside,ãÌ7- Ž[’à
> ‰‰[2024-03-20T11:15:35,912][INFO
>
[jira] [Updated] (IGNITE-21821) Error: Partition file page store is either not initialized or deleted
[
https://issues.apache.org/jira/browse/IGNITE-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-21821:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Error: Partition file page store is either not initialized or deleted
> -
>
> Key: IGNITE-21821
> URL: https://issues.apache.org/jira/browse/IGNITE-21821
> Project: Ignite
> Issue Type: Improvement
>Reporter: Iurii Gerzhedovich
>Assignee: Kirill Tkalenko
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> During looking into log [one of TC
> run|https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7952341?hideTestsFromDependencies=false=false=true+Inspection=true=true=true=false]
> I found Error in log, which looks dangerous
> {code:java}
> ®[2024-03-20T11:15:35,893][ERROR][checkpoint-runner-io0][FailureProcessor]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [], failureCtx=FailureContext
> [type=CRITICAL_ERROR,
> err=org.apache.ignite.internal.lang.IgniteInternalCheckedException:
> IGN-CMN-65535 TraceId:64d96aba-9a18-420d-af54-dd3679466403 Partition file
> page store is either not initialized or deleted: [groupId=81,
> partitionId=19]]]
> org.apache.ignite.internal.lang.IgniteInternalCheckedException: Partition
> file page store is either not initialized or deleted: [groupId=81,
> partitionId=19]
> at
> org.apache.ignite.internal.pagememory.persistence.store.FilePageStoreManager.getStoreWithCheckExists(FilePageStoreManager.java:298)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.store.FilePageStoreManager.allocatePage(FilePageStoreManager.java:259)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.allocatePage(PersistentPageMemory.java:513)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.allocatePageNoReuse(DataStructure.java:193)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.allocatePage(DataStructure.java:174)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.addStripe(PagesList.java:589)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.getStripeForPut(PagesList.java:711)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.put(PagesList.java:815)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList$PutBucket.run(PagesList.java:173)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList$PutBucket.run(PagesList.java:147)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.util.PageHandler.writePage(PageHandler.java:298)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.write(DataStructure.java:296)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.flushBucketsCache(PagesList.java:387)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.saveMetadata(PagesList.java:332)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.pagememory.mv.RowVersionFreeList.saveMetadata(RowVersionFreeList.java:185)
> ~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.pagememory.mv.PersistentPageMemoryMvPartitionStorage.lambda$syncMetadataOnCheckpoint$13(PersistentPageMemoryMvPartitionStorage.java:367)
> ~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.checkpoint.AwaitTasksCompletionExecutor.lambda$execute$1(AwaitTasksCompletionExecutor.java:59)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> 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:834) [?:?] stderr
> tc:parseServiceMessagesInside,ãÌ7- Ž[’à
> ‰‰[2024-03-20T11:15:35,912][INFO
>
[jira] [Updated] (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 updated IGNITE-15179:
-
Labels: ignite-3 (was: iep-76 ignite-3)
> 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: 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] [Assigned] (IGNITE-21588) CMG commands idempotency is broken
[
https://issues.apache.org/jira/browse/IGNITE-21588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Shergalis reassigned IGNITE-21588:
--
Assignee: Kirill Tkalenko (was: Philipp Shergalis)
> CMG commands idempotency is broken
> --
>
> Key: IGNITE-21588
> URL: https://issues.apache.org/jira/browse/IGNITE-21588
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Bessonov
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
>
> When handling commands like {{JoinReadyCommand}} and {{NodesLeaveCommand}} we
> do the following:
> * Read local state with {{{}readLogicalTopology(){}}}.
> * Modify state according to the command.
> * {*}Increase version{*}.
> * Write new state with {{{}saveSnapshotToStorage(snapshot){}}}.
> The problem lies in reading and writing of the state - it' local, and version
> value is not replicated.
> What happens when we restart the node:
> * It starts without local storage snapshot, with appliedIndex == 0, which is
> a {*}state in the past{*}.
> * We apply commands that were already applied before restart.
> * We apply these commands to locally saved topology snapshot.
> * This logical topology snapshot has a *state in the future* when compared
> to appliedIndex == 0.
> * As a result, when we re-apply some commands, we *increase the version* one
> more time, thus breaking data consistency between nodes.
> This would have been fine if we only used this version locally. But
> distribution zones rely on the consistency of the version between all nodes
> in cluster. This might break DZ data nodes handling if any of the cluster
> nodes restarts.
> How to fix:
> * Either drop the storage if there's no storage snapshot, this will restore
> consistency
> * or never start CMG group from a snapshot, but rather start it from the
> latest storage data.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-21722) Sql. NPE in correlated nested loop join
[
https://issues.apache.org/jira/browse/IGNITE-21722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin reassigned IGNITE-21722:
-
Assignee: Pavel Pereslegin
> Sql. NPE in correlated nested loop join
> ---
>
> Key: IGNITE-21722
> URL: https://issues.apache.org/jira/browse/IGNITE-21722
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> See stack trace below:
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.sql.engine.exec.rel.CorrelatedNestedLoopJoinNode.join(CorrelatedNestedLoopJoinNode.java:362)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.CorrelatedNestedLoopJoinNode.lambda$onRequest$1(CorrelatedNestedLoopJoinNode.java:274)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:320)
> ... 4 more
> {code}
> To reproduce the issue, run TPC-H q21 with sf=0.1 on 3-node cluster
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21843) ItRebalanceDistributedTest silently fails to start TableManager
[
https://issues.apache.org/jira/browse/IGNITE-21843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830530#comment-17830530
]
Roman Puchkovskiy commented on IGNITE-21843:
The patch looks good to me
> ItRebalanceDistributedTest silently fails to start TableManager
> ---
>
> Key: IGNITE-21843
> URL: https://issues.apache.org/jira/browse/IGNITE-21843
> Project: Ignite
> Issue Type: Bug
>Reporter: Vadim Pakhnushev
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the IGNITE-21540 the txConfig for TableManager was taken from
> clusterConfigRegistry, but the registry doesn't contain it. There is a
> TransactionConfiguration injected in the field so it's probably enough to
> take it from there.
> In order to better find these errors we should replace
> {{forEach(IgniteComponent::start)}} with {{igniteComponent ->
> assertThat(igniteComponent.start(), willCompleteSuccessfully())}} in the
> {{org.apache.ignite.internal.rebalance.ItRebalanceDistributedTest.Node#start}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-21478) OOM crash with unstable topology
[
https://issues.apache.org/jira/browse/IGNITE-21478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov resolved IGNITE-21478.
Fix Version/s: 2.17
Release Note: Fixed OOM crash on unstable topology
Resolution: Fixed
[~yuri.naryshkin], looks good to me. Merged to master. Thanks for the
contribution!
> OOM crash with unstable topology
>
>
> Key: IGNITE-21478
> URL: https://issues.apache.org/jira/browse/IGNITE-21478
> Project: Ignite
> Issue Type: Bug
>Reporter: Luchnikov Alexander
>Assignee: Yuri Naryshkin
>Priority: Minor
> Labels: ise
> Fix For: 2.17
>
> Attachments: HistoMinorTop.png, histo.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> User cases:
> 1) Frequent entry/exit of a thick client into the topology leads to a crash
> of the server node due to OMM.
> 2) Frequent creation and destroy of caches leads to a server node crash due
> to OOM.
> topVer=20098
> *Real case*
> Part of the log before the OOM crash, pay attention to *topVer=20098*
> {code:java}
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=f080abcd, uptime=3 days, 09:00:55.274]
> ^-- Cluster [hosts=4, CPUs=6, servers=2, clients=2, topVer=20098,
> minorTopVer=6]
> ^-- Network [addrs=[192.168.1.2, 127.0.0.1], discoPort=47500,
> commPort=47100]
> ^-- CPU [CPUs=2, curLoad=86.83%, avgLoad=21.9%, GC=23.9%]
> ^-- Heap [used=867MB, free=15.29%, comm=1024MB]
> ^-- Outbound messages queue [size=0]
> ^-- Public thread pool [active=0, idle=7, qSize=0]
> ^-- System thread pool [active=0, idle=8, qSize=0]
> ^-- Striped thread pool [active=0, idle=8, qSize=0]
> {code}
> Histogram from heap-dump after node failed
> !histo.png!
> *MinorTop example*
> {code:java}
> @Test
> public void testMinorVer() throws Exception {
> Ignite server = startGrids(1);
> IgniteEx client = startClientGrid();
> String cacheName = "cacheName";
> for (int i = 0; i < 500; i++) {
> client.getOrCreateCache(cacheName);
> client.destroyCache(cacheName);
> }
> System.err.println("Heap dump time");
> Thread.sleep(100);
> }
> {code}
> {code:java}
> [INFO
> ][exchange-worker-#149%internal.IgniteOomTest%][GridCachePartitionExchangeManager]
> AffinityTopologyVersion [topVer=2, minorTopVer=1000],
> evt=DISCOVERY_CUSTOM_EVT, evtNode=52b4c130-1a01-4858-813a-ebc8a5dabf1e,
> client=true]
> {code}
> !HistoMinorTop.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21478) OOM crash with unstable topology
[
https://issues.apache.org/jira/browse/IGNITE-21478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830522#comment-17830522
]
Ignite TC Bot commented on IGNITE-21478:
{panel:title=Branch: [pull/11283/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11283/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 1{color} [[tests
4|https://ci2.ignite.apache.org/viewLog.html?buildId=7795436]]
* {color:#013220}IgniteBasicTestSuite:
GridHistoryAffinityAssignmentTest.testAffinityCacheSizeOnReconnect -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
GridHistoryAffinityAssignmentTest.testAffinityCacheSizeOnCacheRecreate -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
GridHistoryAffinityAssignmentTestNoOptimization.testAffinityCacheSizeOnReconnect
- PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
GridHistoryAffinityAssignmentTestNoOptimization.testAffinityCacheSizeOnCacheRecreate
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7794793buildTypeId=IgniteTests24Java8_RunAll]
> OOM crash with unstable topology
>
>
> Key: IGNITE-21478
> URL: https://issues.apache.org/jira/browse/IGNITE-21478
> Project: Ignite
> Issue Type: Bug
>Reporter: Luchnikov Alexander
>Assignee: Yuri Naryshkin
>Priority: Minor
> Labels: ise
> Attachments: HistoMinorTop.png, histo.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> User cases:
> 1) Frequent entry/exit of a thick client into the topology leads to a crash
> of the server node due to OMM.
> 2) Frequent creation and destroy of caches leads to a server node crash due
> to OOM.
> topVer=20098
> *Real case*
> Part of the log before the OOM crash, pay attention to *topVer=20098*
> {code:java}
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=f080abcd, uptime=3 days, 09:00:55.274]
> ^-- Cluster [hosts=4, CPUs=6, servers=2, clients=2, topVer=20098,
> minorTopVer=6]
> ^-- Network [addrs=[192.168.1.2, 127.0.0.1], discoPort=47500,
> commPort=47100]
> ^-- CPU [CPUs=2, curLoad=86.83%, avgLoad=21.9%, GC=23.9%]
> ^-- Heap [used=867MB, free=15.29%, comm=1024MB]
> ^-- Outbound messages queue [size=0]
> ^-- Public thread pool [active=0, idle=7, qSize=0]
> ^-- System thread pool [active=0, idle=8, qSize=0]
> ^-- Striped thread pool [active=0, idle=8, qSize=0]
> {code}
> Histogram from heap-dump after node failed
> !histo.png!
> *MinorTop example*
> {code:java}
> @Test
> public void testMinorVer() throws Exception {
> Ignite server = startGrids(1);
> IgniteEx client = startClientGrid();
> String cacheName = "cacheName";
> for (int i = 0; i < 500; i++) {
> client.getOrCreateCache(cacheName);
> client.destroyCache(cacheName);
> }
> System.err.println("Heap dump time");
> Thread.sleep(100);
> }
> {code}
> {code:java}
> [INFO
> ][exchange-worker-#149%internal.IgniteOomTest%][GridCachePartitionExchangeManager]
> AffinityTopologyVersion [topVer=2, minorTopVer=1000],
> evt=DISCOVERY_CUSTOM_EVT, evtNode=52b4c130-1a01-4858-813a-ebc8a5dabf1e,
> client=true]
> {code}
> !HistoMinorTop.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21834) Add more details to assertions in recovery handhake managers
[ https://issues.apache.org/jira/browse/IGNITE-21834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830520#comment-17830520 ] Roman Puchkovskiy commented on IGNITE-21834: Thanks > Add more details to assertions in recovery handhake managers > > > Key: IGNITE-21834 > URL: https://issues.apache.org/jira/browse/IGNITE-21834 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > An assertion happened, see IGNITE-21833. The error message it not too useful. > It would be nice to have at least the network message in the error message. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21843) ItRebalanceDistributedTest silently fails to start TableManager
[
https://issues.apache.org/jira/browse/IGNITE-21843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Pakhnushev reassigned IGNITE-21843:
-
Assignee: Vadim Pakhnushev (was: Vladislav Pyatkov)
> ItRebalanceDistributedTest silently fails to start TableManager
> ---
>
> Key: IGNITE-21843
> URL: https://issues.apache.org/jira/browse/IGNITE-21843
> Project: Ignite
> Issue Type: Bug
>Reporter: Vadim Pakhnushev
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
>
> In the IGNITE-21540 the txConfig for TableManager was taken from
> clusterConfigRegistry, but the registry doesn't contain it. There is a
> TransactionConfiguration injected in the field so it's probably enough to
> take it from there.
> In order to better find these errors we should replace
> {{forEach(IgniteComponent::start)}} with {{igniteComponent ->
> assertThat(igniteComponent.start(), willCompleteSuccessfully())}} in the
> {{org.apache.ignite.internal.rebalance.ItRebalanceDistributedTest.Node#start}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21615) Update the config updated message to correctly reflect the need to restart
[ https://issues.apache.org/jira/browse/IGNITE-21615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830499#comment-17830499 ] Mikhail Pochatkin commented on IGNITE-21615: Merged to main: c4c0811f2e24d7a3c9c11c49a67f29c48b7c471c > Update the config updated message to correctly reflect the need to restart > -- > > Key: IGNITE-21615 > URL: https://issues.apache.org/jira/browse/IGNITE-21615 > Project: Ignite > Issue Type: Task >Reporter: Igor Gusev >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently, a number of configuration updates require node restart to apply, > but the CLI message remains the same regarless. We should provide users with > more detailed information on when they need to restart the node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21843) ItRebalanceDistributedTest silently fails to start TableManager
[
https://issues.apache.org/jira/browse/IGNITE-21843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Pakhnushev updated IGNITE-21843:
--
Description:
In the IGNITE-21540 the txConfig for TableManager was taken from
clusterConfigRegistry, but the registry doesn't contain it. There is a
TransactionConfiguration injected in the field so it's probably enough to take
it from there.
In order to better find these errors we should replace
{{forEach(IgniteComponent::start)}} with {{igniteComponent ->
assertThat(igniteComponent.start(), willCompleteSuccessfully())}} in the
{{org.apache.ignite.internal.rebalance.ItRebalanceDistributedTest.Node#start}}
was:In the IGNITE-21540 the txConfig for TableManager was taken from
clusterConfigRegistry, but the registry doesn't contain it. There is a
TransactionConfiguration injected in the field so it's probably enough to take
it from there.
> ItRebalanceDistributedTest silently fails to start TableManager
> ---
>
> Key: IGNITE-21843
> URL: https://issues.apache.org/jira/browse/IGNITE-21843
> Project: Ignite
> Issue Type: Bug
>Reporter: Vadim Pakhnushev
>Assignee: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
>
> In the IGNITE-21540 the txConfig for TableManager was taken from
> clusterConfigRegistry, but the registry doesn't contain it. There is a
> TransactionConfiguration injected in the field so it's probably enough to
> take it from there.
> In order to better find these errors we should replace
> {{forEach(IgniteComponent::start)}} with {{igniteComponent ->
> assertThat(igniteComponent.start(), willCompleteSuccessfully())}} in the
> {{org.apache.ignite.internal.rebalance.ItRebalanceDistributedTest.Node#start}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21843) ItRebalanceDistributedTest silently fails to start TableManager
Vadim Pakhnushev created IGNITE-21843: - Summary: ItRebalanceDistributedTest silently fails to start TableManager Key: IGNITE-21843 URL: https://issues.apache.org/jira/browse/IGNITE-21843 Project: Ignite Issue Type: Bug Reporter: Vadim Pakhnushev Assignee: Vladislav Pyatkov In the IGNITE-21540 the txConfig for TableManager was taken from clusterConfigRegistry, but the registry doesn't contain it. There is a TransactionConfiguration injected in the field so it's probably enough to take it from there. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21469) AssertionError in checkpoint
[
https://issues.apache.org/jira/browse/IGNITE-21469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko resolved IGNITE-21469.
--
Fix Version/s: 3.0.0-beta2
Resolution: Duplicate
> AssertionError in checkpoint
>
>
> Key: IGNITE-21469
> URL: https://issues.apache.org/jira/browse/IGNITE-21469
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Bessonov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> {code:java}
> at
> java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:870)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> ~[?:?]
> at
> java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> ~[?:?]
> at
> org.apache.ignite.internal.pagememory.persistence.checkpoint.AwaitTasksCompletionExecutor.lambda$execute$1(AwaitTasksCompletionExecutor.java:63)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ~[?:?]
> ... 1 more Caused by: java.lang.AssertionError: FullPageId
> [pageId=000100020378, effectivePageId=00020378, groupId=886]
> at
> org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.acquirePage(PersistentPageMemory.java:758)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.acquirePage(PersistentPageMemory.java:641)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.acquirePage(PersistentPageMemory.java:613)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.util.PageHandler.writePage(PageHandler.java:280)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.write(DataStructure.java:296)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.flushBucketsCache(PagesList.java:387)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.saveMetadata(PagesList.java:332)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.pagememory.mv.RowVersionFreeList.saveMetadata(RowVersionFreeList.java:185)
> ~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.pagememory.mv.PersistentPageMemoryMvPartitionStorage.lambda$syncMetadataOnCheckpoint$13(PersistentPageMemoryMvPartitionStorage.java:345)
> ~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.checkpoint.AwaitTasksCompletionExecutor.lambda$execute$1(AwaitTasksCompletionExecutor.java:59)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ~[?:?]
> ... 1 more
> {code}
> [https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7820824?expandBuildDeploymentsSection=false=false=false=true=true+Inspection=true]
>
> The reason of the assertion is a bug/race in listeners unregistration for
> partitions freelists. We should do it properly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21469) AssertionError in checkpoint
[
https://issues.apache.org/jira/browse/IGNITE-21469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-21469:
-
Description:
{code:java}
at
java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:870)
~[?:?]
at
java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
~[?:?]
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
~[?:?]
at
java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
~[?:?]
at
org.apache.ignite.internal.pagememory.persistence.checkpoint.AwaitTasksCompletionExecutor.lambda$execute$1(AwaitTasksCompletionExecutor.java:63)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
~[?:?]
... 1 more Caused by: java.lang.AssertionError: FullPageId
[pageId=000100020378, effectivePageId=00020378, groupId=886]
at
org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.acquirePage(PersistentPageMemory.java:758)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.acquirePage(PersistentPageMemory.java:641)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.acquirePage(PersistentPageMemory.java:613)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.pagememory.util.PageHandler.writePage(PageHandler.java:280)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.pagememory.datastructure.DataStructure.write(DataStructure.java:296)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.pagememory.freelist.PagesList.flushBucketsCache(PagesList.java:387)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.pagememory.freelist.PagesList.saveMetadata(PagesList.java:332)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.storage.pagememory.mv.RowVersionFreeList.saveMetadata(RowVersionFreeList.java:185)
~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.storage.pagememory.mv.PersistentPageMemoryMvPartitionStorage.lambda$syncMetadataOnCheckpoint$13(PersistentPageMemoryMvPartitionStorage.java:345)
~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
at
org.apache.ignite.internal.pagememory.persistence.checkpoint.AwaitTasksCompletionExecutor.lambda$execute$1(AwaitTasksCompletionExecutor.java:59)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
~[?:?]
... 1 more
{code}
[https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7820824?expandBuildDeploymentsSection=false=false=false=true=true+Inspection=true]
The reason of the assertion is a bug/race in listeners unregistration for
partitions freelists. We should do it properly
was:
{code:java}
at
java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:870)
~[?:?] at
java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
~[?:?] at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
~[?:?] at
java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
~[?:?] at
org.apache.ignite.internal.pagememory.persistence.checkpoint.AwaitTasksCompletionExecutor.lambda$execute$1(AwaitTasksCompletionExecutor.java:63)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?] at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
~[?:?] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
~[?:?] ... 1 more Caused by: java.lang.AssertionError: FullPageId
[pageId=000100020378, effectivePageId=00020378, groupId=886]
at
org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.acquirePage(PersistentPageMemory.java:758)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?] at
org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.acquirePage(PersistentPageMemory.java:641)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?] at
org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.acquirePage(PersistentPageMemory.java:613)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?] at
org.apache.ignite.internal.pagememory.util.PageHandler.writePage(PageHandler.java:280)
~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?] at
[jira] [Updated] (IGNITE-21828) config update commands fail when no parameters are passed
[
https://issues.apache.org/jira/browse/IGNITE-21828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Pakhnushev updated IGNITE-21828:
--
Description:
{{cluster config update}} or {{node config update}} commands without parameters
fail with
{noformat}
Unknown error
Cannot invoke
"org.apache.ignite.internal.cli.call.configuration.ClusterConfigUpdateCallInput.getClusterUrl()"
because "input" is null{noformat}
The reason is {{SpacedParameterMixin.toString}} implementation when no
parameters are provided.
We should require at least one parameter.
was:
{{cluster config update}} or {{node config update}} commands without parameters
fail with
{noformat}
Unknown error
Cannot invoke
"org.apache.ignite.internal.cli.call.configuration.ClusterConfigUpdateCallInput.getClusterUrl()"
because "input" is null{noformat}
The reason is {{SpacedParameterMixin.toString}} implementation when no
parameters are provided.
We should required at least one parameter.
> config update commands fail when no parameters are passed
> -
>
> Key: IGNITE-21828
> URL: https://issues.apache.org/jira/browse/IGNITE-21828
> Project: Ignite
> Issue Type: Bug
> Components: cli
>Reporter: Vadim Pakhnushev
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
>
> {{cluster config update}} or {{node config update}} commands without
> parameters fail with
> {noformat}
> Unknown error
> Cannot invoke
> "org.apache.ignite.internal.cli.call.configuration.ClusterConfigUpdateCallInput.getClusterUrl()"
> because "input" is null{noformat}
> The reason is {{SpacedParameterMixin.toString}} implementation when no
> parameters are provided.
> We should require at least one parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-21842) Add tests for Java API Thin SQL script client
[ https://issues.apache.org/jira/browse/IGNITE-21842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy resolved IGNITE-21842. Resolution: Invalid Tests already exist > Add tests for Java API Thin SQL script client > - > > Key: IGNITE-21842 > URL: https://issues.apache.org/jira/browse/IGNITE-21842 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21842) Add tests for Java API Thin SQL script client
Roman Puchkovskiy created IGNITE-21842: -- Summary: Add tests for Java API Thin SQL script client Key: IGNITE-21842 URL: https://issues.apache.org/jira/browse/IGNITE-21842 Project: Ignite Issue Type: Improvement Reporter: Roman Puchkovskiy -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21827) Sql. Union returns incorrect result for DECIMAL and INT columns
[
https://issues.apache.org/jira/browse/IGNITE-21827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-21827:
--
Labels: calcite2-required ignite-3 (was: ignite-3)
> Sql. Union returns incorrect result for DECIMAL and INT columns
> ---
>
> Key: IGNITE-21827
> URL: https://issues.apache.org/jira/browse/IGNITE-21827
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Pereslegin
>Priority: Major
> Labels: calcite2-required, ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Union returns incorrect result for NUMERIC/DECIMAL and INT columns
> Simple reproducer:
> {code:java}
> sql("CREATE TABLE t0(id INT PRIMARY KEY, val INT)");
> sql("CREATE TABLE t1(id INT PRIMARY KEY, val DECIMAL)");
> sql("INSERT INTO t0 VALUES (1, 10)");
> sql("INSERT INTO t1 VALUES (1, 10)");
> assertQuery("SELECT id, val from t0 UNION select id, val from t1")
> .returns(1, new BigDecimal(10))
> .ordered()
> .check();
> {code}
> Check fails:
> {noformat}
> java.lang.AssertionError: Collections sizes are not equal:
> Expected: 1
> Actual: 2
> {noformat}
>
> The actual result for such a query contains duplicate values.
> {noformat}
> 1 10
> 1 10
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21831) RocksDb indexes are not table aware
[ https://issues.apache.org/jira/browse/IGNITE-21831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-21831: - Description: When implementing indexes restoration in IGNITE-21680 I messed up and didn't notice, that all indexes are stored in the RocksDB instance without any connection to their table IDs. Therefore, every table, started in the same data region, got the same (full) set of indexes recovered. Another problem is that right now it is impossible to drop a table only using its ID, needed for IGNITE-21760, because we need to know, which indexes it has. > RocksDb indexes are not table aware > --- > > Key: IGNITE-21831 > URL: https://issues.apache.org/jira/browse/IGNITE-21831 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > When implementing indexes restoration in IGNITE-21680 I messed up and didn't > notice, that all indexes are stored in the RocksDB instance without any > connection to their table IDs. Therefore, every table, started in the same > data region, got the same (full) set of indexes recovered. > Another problem is that right now it is impossible to drop a table only using > its ID, needed for IGNITE-21760, because we need to know, which indexes it > has. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21841) The FilePageStoreManager constructor should not throw an exception
[ https://issues.apache.org/jira/browse/IGNITE-21841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov updated IGNITE-21841: Labels: ignite-3 (was: ) > The FilePageStoreManager constructor should not throw an exception > -- > > Key: IGNITE-21841 > URL: https://issues.apache.org/jira/browse/IGNITE-21841 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 3.0.0-beta2 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Current implementation of FilePageStoreManager is throw an exception from > constructor, which is not recommended. > Let's create FilePageStoreFactory from the outside and pass it to the > constructor. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21841) The FilePageStoreManager constructor should not throw an exception
Andrey Novikov created IGNITE-21841: --- Summary: The FilePageStoreManager constructor should not throw an exception Key: IGNITE-21841 URL: https://issues.apache.org/jira/browse/IGNITE-21841 Project: Ignite Issue Type: Improvement Components: persistence Affects Versions: 3.0.0-beta2 Reporter: Andrey Novikov Current implementation of FilePageStoreManager is throw an exception from constructor, which is not recommended. Let's create FilePageStoreFactory from the outside and pass it to the constructor. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21841) The FilePageStoreManager constructor should not throw an exception
[ https://issues.apache.org/jira/browse/IGNITE-21841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-21841: --- Assignee: Andrey Novikov > The FilePageStoreManager constructor should not throw an exception > -- > > Key: IGNITE-21841 > URL: https://issues.apache.org/jira/browse/IGNITE-21841 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 3.0.0-beta2 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Major > > Current implementation of FilePageStoreManager is throw an exception from > constructor, which is not recommended. > Let's create FilePageStoreFactory from the outside and pass it to the > constructor. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21840) PersistentPageMemoryStorageEngine#createMvTable should return MvTableStorage
[ https://issues.apache.org/jira/browse/IGNITE-21840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov updated IGNITE-21840: Labels: ignite-3 (was: ) > PersistentPageMemoryStorageEngine#createMvTable should return MvTableStorage > > > Key: IGNITE-21840 > URL: https://issues.apache.org/jira/browse/IGNITE-21840 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 3.0.0-beta2 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Current implementation of PersistentPageMemoryStorageEngine#createMvTable > returns PersistentPageMemoryTableStorage which doesn't comply with the > contract described in StorageEngine. The use of this is not found in the code. > Let's return MvTableStorage instead of PersistentPageMemoryTableStorage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-19702) Unable to create column with default value with literal convertion
[
https://issues.apache.org/jira/browse/IGNITE-19702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830398#comment-17830398
]
Anatoli Karman commented on IGNITE-19702:
-
Somewhat similar issue has been encountered for UUID data type insert
statements that use default values.
{*}Queries to reproduce{*}:
{code:java}
create table createTableWithDefaultValues(key INTEGER not null, val UUID not
null default '4a2f1859-c73b-4eec-a29c-629ec68d8735', primary key (key));
insert into createTableWithDefaultValues(key) values (106080);{code}
Results in a _*java.lang.IllegalArgumentException*_
{code:java}
Caused by: java.lang.IllegalArgumentException
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:129)
at org.apache.calcite.rex.RexLiteral.(RexLiteral.java:231)
at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:1034)
at
org.apache.ignite.internal.sql.engine.rex.IgniteRexBuilder.makeLiteral(IgniteRexBuilder.java:55)
at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:1577)
at
org.apache.ignite.internal.sql.engine.schema.TableDescriptorImpl.newColumnDefaultValue(TableDescriptorImpl.java:121)
at
org.apache.calcite.sql2rel.SqlToRelConverter.convertColumnList(SqlToRelConverter.java:4060)
at
org.apache.calcite.sql2rel.SqlToRelConverter.convertInsert(SqlToRelConverter.java:3856)
at
org.apache.ignite.internal.sql.engine.prepare.IgniteSqlToRelConvertor.convertInsert(IgniteSqlToRelConvertor.java:117)
at
org.apache.calcite.sql2rel.SqlToRelConverter.convertQueryRecursive(SqlToRelConverter.java:3771)
at
org.apache.ignite.internal.sql.engine.prepare.IgniteSqlToRelConvertor.convertQueryRecursive(IgniteSqlToRelConvertor.java:86)
at
org.apache.calcite.sql2rel.SqlToRelConverter.convertQuery(SqlToRelConverter.java:610)
at
org.apache.ignite.internal.sql.engine.prepare.IgnitePlanner.rel(IgnitePlanner.java:342)
at
org.apache.ignite.internal.sql.engine.prepare.PlannerHelper.optimize(PlannerHelper.java:84)
at
org.apache.ignite.internal.sql.engine.prepare.PrepareServiceImpl.lambda$prepareDml$8(PrepareServiceImpl.java:400)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700){code}
> Unable to create column with default value with literal convertion
> --
>
> Key: IGNITE-19702
> URL: https://issues.apache.org/jira/browse/IGNITE-19702
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0
>Reporter: Alexander Belyak
>Priority: Major
> Labels: ignite-3
>
> DDL command to create a column with default value fails if it require some
> type of conversion (string to time, date, timestamp, uuid). For example:
> {noformat}
> create table ttt6(key int primary key, val TIMESTAMP default '2022-02-01
> 12:12:12');{noformat}
> returns
> {noformat}
> [Code: 0, SQL State: 5] Exception while executing query [query=create
> table ttt6(key int primary key, val TIMESTAMP default '2022-02-01
> 12:12:12')]. Error message:Unable co convert literal{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-21821) Error: Partition file page store is either not initialized or deleted
[
https://issues.apache.org/jira/browse/IGNITE-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko reassigned IGNITE-21821:
Assignee: Kirill Tkalenko
> Error: Partition file page store is either not initialized or deleted
> -
>
> Key: IGNITE-21821
> URL: https://issues.apache.org/jira/browse/IGNITE-21821
> Project: Ignite
> Issue Type: Improvement
>Reporter: Iurii Gerzhedovich
>Assignee: Kirill Tkalenko
>Priority: Blocker
> Labels: ignite-3
>
> During looking into log [one of TC
> run|https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7952341?hideTestsFromDependencies=false=false=true+Inspection=true=true=true=false]
> I found Error in log, which looks dangerous
> {code:java}
> ®[2024-03-20T11:15:35,893][ERROR][checkpoint-runner-io0][FailureProcessor]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [], failureCtx=FailureContext
> [type=CRITICAL_ERROR,
> err=org.apache.ignite.internal.lang.IgniteInternalCheckedException:
> IGN-CMN-65535 TraceId:64d96aba-9a18-420d-af54-dd3679466403 Partition file
> page store is either not initialized or deleted: [groupId=81,
> partitionId=19]]]
> org.apache.ignite.internal.lang.IgniteInternalCheckedException: Partition
> file page store is either not initialized or deleted: [groupId=81,
> partitionId=19]
> at
> org.apache.ignite.internal.pagememory.persistence.store.FilePageStoreManager.getStoreWithCheckExists(FilePageStoreManager.java:298)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.store.FilePageStoreManager.allocatePage(FilePageStoreManager.java:259)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.PersistentPageMemory.allocatePage(PersistentPageMemory.java:513)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.allocatePageNoReuse(DataStructure.java:193)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.allocatePage(DataStructure.java:174)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.addStripe(PagesList.java:589)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.getStripeForPut(PagesList.java:711)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.put(PagesList.java:815)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList$PutBucket.run(PagesList.java:173)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList$PutBucket.run(PagesList.java:147)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.util.PageHandler.writePage(PageHandler.java:298)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.datastructure.DataStructure.write(DataStructure.java:296)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.flushBucketsCache(PagesList.java:387)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.freelist.PagesList.saveMetadata(PagesList.java:332)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.pagememory.mv.RowVersionFreeList.saveMetadata(RowVersionFreeList.java:185)
> ~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.storage.pagememory.mv.PersistentPageMemoryMvPartitionStorage.lambda$syncMetadataOnCheckpoint$13(PersistentPageMemoryMvPartitionStorage.java:367)
> ~[ignite-storage-page-memory-3.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.pagememory.persistence.checkpoint.AwaitTasksCompletionExecutor.lambda$execute$1(AwaitTasksCompletionExecutor.java:59)
> ~[ignite-page-memory-3.0.0-SNAPSHOT.jar:?]
> 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:834) [?:?] stderr
> tc:parseServiceMessagesInside,ãÌ7- Ž[’à
> ‰‰[2024-03-20T11:15:35,912][INFO
> ][%sqllogic0%JRaft-FSMCaller-Disruptor_stripe_8-0][StateMachineAdapter]
> onLeaderStart: term=1.
> {code}
--
This message was sent by Atlassian Jira
[jira] [Assigned] (IGNITE-21840) PersistentPageMemoryStorageEngine#createMvTable should return MvTableStorage
[ https://issues.apache.org/jira/browse/IGNITE-21840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-21840: --- Assignee: Andrey Novikov > PersistentPageMemoryStorageEngine#createMvTable should return MvTableStorage > > > Key: IGNITE-21840 > URL: https://issues.apache.org/jira/browse/IGNITE-21840 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 3.0.0-beta2 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Major > Fix For: 3.0.0-beta2 > > > Current implementation of PersistentPageMemoryStorageEngine#createMvTable > returns PersistentPageMemoryTableStorage which doesn't comply with the > contract described in StorageEngine. The use of this is not found in the code. > Let's return MvTableStorage instead of PersistentPageMemoryTableStorage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21840) PersistentPageMemoryStorageEngine#createMvTable should return MvTableStorage
Andrey Novikov created IGNITE-21840: --- Summary: PersistentPageMemoryStorageEngine#createMvTable should return MvTableStorage Key: IGNITE-21840 URL: https://issues.apache.org/jira/browse/IGNITE-21840 Project: Ignite Issue Type: Improvement Components: persistence Affects Versions: 3.0.0-beta2 Reporter: Andrey Novikov Fix For: 3.0.0-beta2 Current implementation of PersistentPageMemoryStorageEngine#createMvTable returns PersistentPageMemoryTableStorage which doesn't comply with the contract described in StorageEngine. The use of this is not found in the code. Let's return MvTableStorage instead of PersistentPageMemoryTableStorage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21834) Add more details to assertions in recovery handhake managers
[ https://issues.apache.org/jira/browse/IGNITE-21834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830355#comment-17830355 ] Kirill Tkalenko commented on IGNITE-21834: -- Looks good. > Add more details to assertions in recovery handhake managers > > > Key: IGNITE-21834 > URL: https://issues.apache.org/jira/browse/IGNITE-21834 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > An assertion happened, see IGNITE-21833. The error message it not too useful. > It would be nice to have at least the network message in the error message. -- This message was sent by Atlassian Jira (v8.20.10#820010)
