[jira] [Updated] (IGNITE-15293) TopHistorySize cannot be set below the default value
[ https://issues.apache.org/jira/browse/IGNITE-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Changmyung Lee updated IGNITE-15293: Affects Version/s: (was: 2.12) > TopHistorySize cannot be set below the default value > > > Key: IGNITE-15293 > URL: https://issues.apache.org/jira/browse/IGNITE-15293 > Project: Ignite > Issue Type: Improvement > Components: networking >Affects Versions: 2.10 >Reporter: Changmyung Lee >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The topology history size cannot be set below the default value of 1000 > When a client is added to the topology, the message size is too large, which > takes a long time and causes write time out. > I think users should be able to specify the size to their needs. > I propose to freely allow the size of the TopHistorySize like other settings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15293) TopHistorySize cannot be set below the default value
[ https://issues.apache.org/jira/browse/IGNITE-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Changmyung Lee updated IGNITE-15293: Affects Version/s: 2.12 > TopHistorySize cannot be set below the default value > > > Key: IGNITE-15293 > URL: https://issues.apache.org/jira/browse/IGNITE-15293 > Project: Ignite > Issue Type: Improvement > Components: networking >Affects Versions: 2.10, 2.12 >Reporter: Changmyung Lee >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The topology history size cannot be set below the default value of 1000 > When a client is added to the topology, the message size is too large, which > takes a long time and causes write time out. > I think users should be able to specify the size to their needs. > I propose to freely allow the size of the TopHistorySize like other settings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15293) TopHistorySize cannot be set below the default value
[ https://issues.apache.org/jira/browse/IGNITE-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Changmyung Lee updated IGNITE-15293: Component/s: (was: general) networking Ignite Flags: Docs Required,Release Notes Required > TopHistorySize cannot be set below the default value > > > Key: IGNITE-15293 > URL: https://issues.apache.org/jira/browse/IGNITE-15293 > Project: Ignite > Issue Type: Improvement > Components: networking >Affects Versions: 2.10 >Reporter: Changmyung Lee >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The topology history size cannot be set below the default value of 1000 > When a client is added to the topology, the message size is too large, which > takes a long time and causes write time out. > I think users should be able to specify the size to their needs. > I propose to freely allow the size of the TopHistorySize like other settings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15293) TopHistorySize cannot be set below the default value
[ https://issues.apache.org/jira/browse/IGNITE-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Changmyung Lee updated IGNITE-15293: Priority: Major (was: Minor) > TopHistorySize cannot be set below the default value > > > Key: IGNITE-15293 > URL: https://issues.apache.org/jira/browse/IGNITE-15293 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.10 >Reporter: Changmyung Lee >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The topology history size cannot be set below the default value of 1000 > When a client is added to the topology, the message size is too large, which > takes a long time and causes write time out. > I think users should be able to specify the size to their needs. > I propose to freely allow the size of the TopHistorySize like other settings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15096) Schema events processing refactoring.
[ https://issues.apache.org/jira/browse/IGNITE-15096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15096: -- Priority: Minor (was: Major) > Schema events processing refactoring. > - > > Key: IGNITE-15096 > URL: https://issues.apache.org/jira/browse/IGNITE-15096 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Minor > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > All table events with schema events are processed in TableManager listener. > Let's > * Replace ConfigurationListener with ConfigurationNamedListListener to > simplify the diff calculation between old/new configs. > * Register a separate per-table listener for schema events on table creation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15302) Enable precision for binary field
[ https://issues.apache.org/jira/browse/IGNITE-15302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-15302: Reviewer: Ivan Daschinsky > Enable precision for binary field > - > > Key: IGNITE-15302 > URL: https://issues.apache.org/jira/browse/IGNITE-15302 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > > There are 2 ways to set precision - with SQL create table clause, with > QuerySqlField annotation. > Currently precision works for Decimal and String (varchar) types. Feature of > String isn't documented. > It's proposed: > # Document precision for String (varchar) > # Enable precision for byte[] (binary, varbinary) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15025) Add Maven check scripts to VCS
[ https://issues.apache.org/jira/browse/IGNITE-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15025: -- Component/s: build > Add Maven check scripts to VCS > -- > > Key: IGNITE-15025 > URL: https://issues.apache.org/jira/browse/IGNITE-15025 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 3.0.0-alpha3 > > Time Spent: 2.5h > Remaining Estimate: 0h > > Currently, only TC has scripts for Maven checks which leads to several > problems: > # Developers can't use them to check code locally > # Scripts can be lost with TC in inaccurate configuration operation. > It is required to move scripts to Ignite's codebase and call them from TC > build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15182) Fix pmd:check execution so it can be run without compile goal in reactor
[ https://issues.apache.org/jira/browse/IGNITE-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15182: -- Component/s: build > Fix pmd:check execution so it can be run without compile goal in reactor > > > Key: IGNITE-15182 > URL: https://issues.apache.org/jira/browse/IGNITE-15182 > Project: Ignite > Issue Type: Task > Components: build >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, pmd:check must be run alongside 'compile' goal. Otherwise, > generated sources and test sources won't be checked. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15182) Fix pmd:check execution so it can be run without compile goal in reactor
[ https://issues.apache.org/jira/browse/IGNITE-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15182: -- Labels: ignite-3 (was: UX ignite-3) > Fix pmd:check execution so it can be run without compile goal in reactor > > > Key: IGNITE-15182 > URL: https://issues.apache.org/jira/browse/IGNITE-15182 > Project: Ignite > Issue Type: Task >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, pmd:check must be run alongside 'compile' goal. Otherwise, > generated sources and test sources won't be checked. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15182) Fix pmd:check execution so it can be run without compile goal in reactor
[ https://issues.apache.org/jira/browse/IGNITE-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15182: -- Fix Version/s: 3.0.0-alpha3 > Fix pmd:check execution so it can be run without compile goal in reactor > > > Key: IGNITE-15182 > URL: https://issues.apache.org/jira/browse/IGNITE-15182 > Project: Ignite > Issue Type: Task >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, pmd:check must be run alongside 'compile' goal. Otherwise, > generated sources and test sources won't be checked. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15182) Fix pmd:check execution so it can be run without compile goal in reactor
[ https://issues.apache.org/jira/browse/IGNITE-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15182: -- Labels: UX ignite-3 (was: ignite-3) > Fix pmd:check execution so it can be run without compile goal in reactor > > > Key: IGNITE-15182 > URL: https://issues.apache.org/jira/browse/IGNITE-15182 > Project: Ignite > Issue Type: Task >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: UX, ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, pmd:check must be run alongside 'compile' goal. Otherwise, > generated sources and test sources won't be checked. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15302) Enable precision for binary field
Maksim Timonin created IGNITE-15302: --- Summary: Enable precision for binary field Key: IGNITE-15302 URL: https://issues.apache.org/jira/browse/IGNITE-15302 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Assignee: Maksim Timonin There are 2 ways to set precision - with SQL create table clause, with QuerySqlField annotation. Currently precision works for Decimal and String (varchar) types. Feature of String isn't documented. It's proposed: # Document precision for String (varchar) # Enable precision for byte[] (binary, varbinary) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15025) Add Maven check scripts to VCS
[ https://issues.apache.org/jira/browse/IGNITE-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15025: -- Fix Version/s: 3.0.0-alpha3 > Add Maven check scripts to VCS > -- > > Key: IGNITE-15025 > URL: https://issues.apache.org/jira/browse/IGNITE-15025 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 3.0.0-alpha3 > > Time Spent: 2.5h > Remaining Estimate: 0h > > Currently, only TC has scripts for Maven checks which leads to several > problems: > # Developers can't use them to check code locally > # Scripts can be lost with TC in inaccurate configuration operation. > It is required to move scripts to Ignite's codebase and call them from TC > build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IGNITE-15219) Umnmute schema related tests, muted by IGNITE-14581
[
https://issues.apache.org/jira/browse/IGNITE-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reopened IGNITE-15219:
--
> Umnmute schema related tests, muted by IGNITE-14581
> ---
>
> Key: IGNITE-15219
> URL: https://issues.apache.org/jira/browse/IGNITE-15219
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Kirill Gusakov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There are four test classes that are muted by
> {code:java}
> @Disabled("https://issues.apache.org/jira/browse/IGNITE-14581;)
> {code}
> * org.apache.ignite.internal.runner.app.LiveSchemaChangeKVViewTest
> * org.apache.ignite.internal.runner.app.LiveSchemaChangeTableTest
> * org.apache.ignite.internal.runner.app.SchemaChangeKVViewTest
> * org.apache.ignite.internal.runner.app.SchemaChangeTableViewTest
> After removing disabled annotation the tests will hang
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15301) Update Ignite dependency: Bouncycastle
[ https://issues.apache.org/jira/browse/IGNITE-15301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-15301: --- Fix Version/s: 2.12 > Update Ignite dependency: Bouncycastle > -- > > Key: IGNITE-15301 > URL: https://issues.apache.org/jira/browse/IGNITE-15301 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > > Update Bouncycastle dependency 1.60 to 1.69 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15301) Update Ignite dependency: Bouncycastle
[ https://issues.apache.org/jira/browse/IGNITE-15301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-15301: --- Labels: newbie (was: ) > Update Ignite dependency: Bouncycastle > -- > > Key: IGNITE-15301 > URL: https://issues.apache.org/jira/browse/IGNITE-15301 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: newbie > > Update Bouncycastle dependency 1.60 to 1.69 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15301) Update Ignite dependency: Bouncycastle
Aleksandr created IGNITE-15301: -- Summary: Update Ignite dependency: Bouncycastle Key: IGNITE-15301 URL: https://issues.apache.org/jira/browse/IGNITE-15301 Project: Ignite Issue Type: Improvement Reporter: Aleksandr Assignee: Aleksandr Update Bouncycastle dependency 1.60 to 1.69 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15098) testChangePeersChaosWithoutSnapshot is flaky
[ https://issues.apache.org/jira/browse/IGNITE-15098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15098: - Priority: Blocker (was: Major) > testChangePeersChaosWithoutSnapshot is flaky > > > Key: IGNITE-15098 > URL: https://issues.apache.org/jira/browse/IGNITE-15098 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Scherbakov >Priority: Blocker > Labels: ignite-3 > > https://ci.ignite.apache.org/viewLog.html?buildId=6079968=buildResultsDiv=ignite3_Test_IntegrationTests_IntegrationTests > org.opentest4j.AssertionFailedError: expected: but was: > at > org.apache.ignite.raft.jraft.core.ITNodeTest.testChangePeersChaosWithoutSnapshot(ITNodeTest.java:3174) > // assertTrue(done.await().isOk()); -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15098) testChangePeersChaosWithoutSnapshot is flaky
[ https://issues.apache.org/jira/browse/IGNITE-15098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15098: - Issue Type: Bug (was: Task) > testChangePeersChaosWithoutSnapshot is flaky > > > Key: IGNITE-15098 > URL: https://issues.apache.org/jira/browse/IGNITE-15098 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > > https://ci.ignite.apache.org/viewLog.html?buildId=6079968=buildResultsDiv=ignite3_Test_IntegrationTests_IntegrationTests > org.opentest4j.AssertionFailedError: expected: but was: > at > org.apache.ignite.raft.jraft.core.ITNodeTest.testChangePeersChaosWithoutSnapshot(ITNodeTest.java:3174) > // assertTrue(done.await().isOk()); -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15300) Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
[
https://issues.apache.org/jira/browse/IGNITE-15300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398144#comment-17398144
]
Pavel Pereslegin commented on IGNITE-15300:
---
Perhaps the specified problem has already been resolved by the patch proposed
in IGNITE-14794, it is worth checking it before starting the investigation.
> Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
> -
>
> Key: IGNITE-15300
> URL: https://issues.apache.org/jira/browse/IGNITE-15300
> Project: Ignite
> Issue Type: Test
>Reporter: Maxim Muzafarov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43
>
> https://ci.ignite.apache.org/viewLog.html?buildId=6123288=buildResultsDiv=IgniteTests24Java8_ControlUtilityZookeeper#testNameId-4389213602152674112
> {code}
> [2021-08-09 22:59:49,757][ERROR][main][root] Test failed
> [test=GridCommandHandlerTest#testSnapshotRestoreCancelAndStatus,
> duration=16514]
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.ignite.testframework.GridTestUtils.assertContains(GridTestUtils.java:391)
> at
> org.apache.ignite.util.GridCommandHandlerTest.testSnapshotRestoreCancelAndStatus(GridCommandHandlerTest.java:3312)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2432)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14816) Calcite engine. Change TreeMap in sorted IndexSpoolNode to ArrayList
[
https://issues.apache.org/jira/browse/IGNITE-14816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398142#comment-17398142
]
Aleksey Plekhanov commented on IGNITE-14816:
[~tledkov-gridgain], in most cases it will give a performance boost. I see only
one disadvantage here: the use of RuntimeSortedIndex with almost unique values.
In the case of correlated NL join with unique RuntimeSortedIndex as the right
input, for example, we will do 2 times more comparisons for each row of the
left input.
> Calcite engine. Change TreeMap in sorted IndexSpoolNode to ArrayList
>
>
> Key: IGNITE-14816
> URL: https://issues.apache.org/jira/browse/IGNITE-14816
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Pavel Pereslegin
>Priority: Minor
> Labels: calcite3-required
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {{IgniteSortedIndexSpool}} assumes that the underlying input is already
> sorted, but the execution node creates {{TreeMap}} to find the rows (see
> {{IndexSpoolNode#createTreeSpool}}). This {{TreeMap}} can be replaced with
> {{ArrayList}} and binary search with the same efficiency for searching and
> lower costs for inserting data.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15232) CacheGroupKeyChangeTest.testWalArchiveCleanup is flaky on master
[ https://issues.apache.org/jira/browse/IGNITE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin reassigned IGNITE-15232: - Assignee: (was: Pavel Pereslegin) > CacheGroupKeyChangeTest.testWalArchiveCleanup is flaky on master > > > Key: IGNITE-15232 > URL: https://issues.apache.org/jira/browse/IGNITE-15232 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Pereslegin >Priority: Minor > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8==testDetails=-4474268434056559023=TEST_STATUS_DESC_IgniteTests24Java8=%3Cdefault%3E=50 > After IGNITE-14952, the test starts to fail because the test relied on a WAL > segment reservation. > We should increase the WAL archive size in this test or find a better way to > prevent WAL archive cleanup. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15300) Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
[
https://issues.apache.org/jira/browse/IGNITE-15300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin reassigned IGNITE-15300:
-
Assignee: Pavel Pereslegin
> Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
> -
>
> Key: IGNITE-15300
> URL: https://issues.apache.org/jira/browse/IGNITE-15300
> Project: Ignite
> Issue Type: Test
>Reporter: Maxim Muzafarov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43
>
> https://ci.ignite.apache.org/viewLog.html?buildId=6123288=buildResultsDiv=IgniteTests24Java8_ControlUtilityZookeeper#testNameId-4389213602152674112
> {code}
> [2021-08-09 22:59:49,757][ERROR][main][root] Test failed
> [test=GridCommandHandlerTest#testSnapshotRestoreCancelAndStatus,
> duration=16514]
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.ignite.testframework.GridTestUtils.assertContains(GridTestUtils.java:391)
> at
> org.apache.ignite.util.GridCommandHandlerTest.testSnapshotRestoreCancelAndStatus(GridCommandHandlerTest.java:3312)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2432)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15265) Update Ignite dependency: Netty
[ https://issues.apache.org/jira/browse/IGNITE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398130#comment-17398130 ] Dmitry Pavlov commented on IGNITE-15265: [~aonikolaev] , merged to master, https://github.com/apache/ignite/commit/a72ea4fa501f9aa1546802b70eb3bd2355443214 Thank you for the contribution. > Update Ignite dependency: Netty > --- > > Key: IGNITE-15265 > URL: https://issues.apache.org/jira/browse/IGNITE-15265 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > Update Netty dependency 4.1.54.Final to 4.1.66.Final > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15300) Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
Maxim Muzafarov created IGNITE-15300:
Summary: Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr
SPI environment
Key: IGNITE-15300
URL: https://issues.apache.org/jira/browse/IGNITE-15300
Project: Ignite
Issue Type: Test
Reporter: Maxim Muzafarov
https://ci.ignite.apache.org/viewLog.html?buildId=6123288=buildResultsDiv=IgniteTests24Java8_ControlUtilityZookeeper#testNameId-4389213602152674112
{code}
[2021-08-09 22:59:49,757][ERROR][main][root] Test failed
[test=GridCommandHandlerTest#testSnapshotRestoreCancelAndStatus, duration=16514]
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
org.apache.ignite.testframework.GridTestUtils.assertContains(GridTestUtils.java:391)
at
org.apache.ignite.util.GridCommandHandlerTest.testSnapshotRestoreCancelAndStatus(GridCommandHandlerTest.java:3312)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2432)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15300) Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
[
https://issues.apache.org/jira/browse/IGNITE-15300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-15300:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
> -
>
> Key: IGNITE-15300
> URL: https://issues.apache.org/jira/browse/IGNITE-15300
> Project: Ignite
> Issue Type: Test
>Reporter: Maxim Muzafarov
>Priority: Major
> Labels: iep-43
>
> https://ci.ignite.apache.org/viewLog.html?buildId=6123288=buildResultsDiv=IgniteTests24Java8_ControlUtilityZookeeper#testNameId-4389213602152674112
> {code}
> [2021-08-09 22:59:49,757][ERROR][main][root] Test failed
> [test=GridCommandHandlerTest#testSnapshotRestoreCancelAndStatus,
> duration=16514]
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.ignite.testframework.GridTestUtils.assertContains(GridTestUtils.java:391)
> at
> org.apache.ignite.util.GridCommandHandlerTest.testSnapshotRestoreCancelAndStatus(GridCommandHandlerTest.java:3312)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2432)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15292) Update Ignite dependency: httpclient&
[
https://issues.apache.org/jira/browse/IGNITE-15292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398116#comment-17398116
]
Ignite TC Bot commented on IGNITE-15292:
{panel:title=Branch: [pull/9323/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9323/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6127681buildTypeId=IgniteTests24Java8_RunAll]
> Update Ignite dependency: httpclient&
> --
>
> Key: IGNITE-15292
> URL: https://issues.apache.org/jira/browse/IGNITE-15292
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr
>Assignee: Aleksandr
>Priority: Major
> Labels: newbie
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Update httpclient dependency 4.5.1 to 4.5.13 and httpcore 4.4.3 to 4.4.14
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15283) Remove duplicated managing of CacheDataStore in offheap manager
[
https://issues.apache.org/jira/browse/IGNITE-15283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398115#comment-17398115
]
Ignite TC Bot commented on IGNITE-15283:
{panel:title=Branch: [pull/9317/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9317/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6127321buildTypeId=IgniteTests24Java8_RunAll]
> Remove duplicated managing of CacheDataStore in offheap manager
> ---
>
> Key: IGNITE-15283
> URL: https://issues.apache.org/jira/browse/IGNITE-15283
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The cache group patition topology provides the same view on created cache
> data stores. , so managing of data stores in the offeap manager can be
> omitted.
> {code}
> protected final ConcurrentMap partDataStores =
> new ConcurrentHashMap<>();
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-15290) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-15290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15290. - Resolution: Fixed Website updated with these events. > [Ignite Website] Update for events schedule > > > Key: IGNITE-15290 > URL: https://issues.apache.org/jira/browse/IGNITE-15290 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Trivial > > # Please change the top line for Watch Ignite Summit Recordings > [https://youtube.com/playlist?list=PLMc7NR20hA-KF8c_hVICKpzKnWkjzfC2V] > # Please add to the Events Schedule page these events: > *Apache Ignite. Now with CDC!* > * Saint Highload++, Nikolay Izhikov > * September 20, 2021 > Nikolay Izhikov, Apache Ignite PMC, will introduce the audience to Change > Data Capture and share how it's organized in Apache Ignite. > Learn more = [https://www.highload.ru/spb/2021/abstracts/7942] > > *Python-client for Apache Ignite Distributed DataBase* > * Moscow Python Conference 2021, Ivan Daschinsky > * September 28, 2021 > Ivan Daschinsky, Apache Ignite Committer and Python Client maintainer will > present the latest version of the Client. > Learn more = [https://conf.python.ru/moscow/2021/abstracts/7815] > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15290) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-15290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15290: --- Assignee: Mauricio Stekl > [Ignite Website] Update for events schedule > > > Key: IGNITE-15290 > URL: https://issues.apache.org/jira/browse/IGNITE-15290 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Trivial > > # Please change the top line for Watch Ignite Summit Recordings > [https://youtube.com/playlist?list=PLMc7NR20hA-KF8c_hVICKpzKnWkjzfC2V] > # Please add to the Events Schedule page these events: > *Apache Ignite. Now with CDC!* > * Saint Highload++, Nikolay Izhikov > * September 20, 2021 > Nikolay Izhikov, Apache Ignite PMC, will introduce the audience to Change > Data Capture and share how it's organized in Apache Ignite. > Learn more = [https://www.highload.ru/spb/2021/abstracts/7942] > > *Python-client for Apache Ignite Distributed DataBase* > * Moscow Python Conference 2021, Ivan Daschinsky > * September 28, 2021 > Ivan Daschinsky, Apache Ignite Committer and Python Client maintainer will > present the latest version of the Client. > Learn more = [https://conf.python.ru/moscow/2021/abstracts/7815] > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15291) [Ignite Website] Add new proven cases
[ https://issues.apache.org/jira/browse/IGNITE-15291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15291: --- Assignee: Mauricio Stekl > [Ignite Website] Add new proven cases > - > > Key: IGNITE-15291 > URL: https://issues.apache.org/jira/browse/IGNITE-15291 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > Please add new videos to the "powered by Ignite" page > [https://ignite.apache.org/use-cases/provenusecases.html] > +Please insert new cases after the 24 Fitness:+ > *JPMorgan Chase* > Exposure management poses unique technical challenges for Asset Management. > Requests involve heavy computation on top of millions of data points with > target response times of around a 1/3 second. This challenge was solved using > Apache Ignite-based platform. > [https://youtu.be/jF9T2cJB6t0] > *nference.ai* > nference.ai uses Ignite for distributed analytics in the bioinformatics > domain. Ignite as a horizontally scalable framework allows to define > different statistical analyses and execute it on TB's of numerical data in > real-time, without movement of data. > [https://youtu.be/NUxdoL-K9Ys] > +and these 2 cases let's add to the end of the list:+ > *Trimble* > Trimble built a live geospatial analytics platform for construction > productivity with Apache Ignite. Apache Ignite forms a key infrastructure > component of TRex platform. It supports real-time ingest of data from the > field along with OLTP style analytics and queries against that data such as > thematic tiling, volumes & cut/fill calculations, spatial profiling, etc. > [https://youtu.be/KLnvIiwAl2o] > *Sentienz* > Sentienz uses Apache Ignite to handle more than 1Millions Requests per > second from 10 Million devices with a single cluster IoT platform. > [https://youtu.be/_mnZQ3JDcn8] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15291) [Ignite Website] Add new proven cases
[ https://issues.apache.org/jira/browse/IGNITE-15291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15291. - Resolution: Fixed Updated the web page with these use cases. > [Ignite Website] Add new proven cases > - > > Key: IGNITE-15291 > URL: https://issues.apache.org/jira/browse/IGNITE-15291 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > Please add new videos to the "powered by Ignite" page > [https://ignite.apache.org/use-cases/provenusecases.html] > +Please insert new cases after the 24 Fitness:+ > *JPMorgan Chase* > Exposure management poses unique technical challenges for Asset Management. > Requests involve heavy computation on top of millions of data points with > target response times of around a 1/3 second. This challenge was solved using > Apache Ignite-based platform. > [https://youtu.be/jF9T2cJB6t0] > *nference.ai* > nference.ai uses Ignite for distributed analytics in the bioinformatics > domain. Ignite as a horizontally scalable framework allows to define > different statistical analyses and execute it on TB's of numerical data in > real-time, without movement of data. > [https://youtu.be/NUxdoL-K9Ys] > +and these 2 cases let's add to the end of the list:+ > *Trimble* > Trimble built a live geospatial analytics platform for construction > productivity with Apache Ignite. Apache Ignite forms a key infrastructure > component of TRex platform. It supports real-time ingest of data from the > field along with OLTP style analytics and queries against that data such as > thematic tiling, volumes & cut/fill calculations, spatial profiling, etc. > [https://youtu.be/KLnvIiwAl2o] > *Sentienz* > Sentienz uses Apache Ignite to handle more than 1Millions Requests per > second from 10 Million devices with a single cluster IoT platform. > [https://youtu.be/_mnZQ3JDcn8] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14816) Calcite engine. Change TreeMap in sorted IndexSpoolNode to ArrayList
[
https://issues.apache.org/jira/browse/IGNITE-14816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398094#comment-17398094
]
Taras Ledkov commented on IGNITE-14816:
---
[~xtern], [~alex_pl] what do you think about remove comparison with {{upper}}
for the each row at the {{RuntimeSortedIndex.Cursor#next}}. I mean calculate
upper bound one time on cursor initialization then check only index of the
upper bound.
> Calcite engine. Change TreeMap in sorted IndexSpoolNode to ArrayList
>
>
> Key: IGNITE-14816
> URL: https://issues.apache.org/jira/browse/IGNITE-14816
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Pavel Pereslegin
>Priority: Minor
> Labels: calcite3-required
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {{IgniteSortedIndexSpool}} assumes that the underlying input is already
> sorted, but the execution node creates {{TreeMap}} to find the rows (see
> {{IndexSpoolNode#createTreeSpool}}). This {{TreeMap}} can be replaced with
> {{ArrayList}} and binary search with the same efficiency for searching and
> lower costs for inserting data.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15274) Unexpected initialization of MaintainanceFileStore on client nodes
[
https://issues.apache.org/jira/browse/IGNITE-15274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398077#comment-17398077
]
Ignite TC Bot commented on IGNITE-15274:
{panel:title=Branch: [pull/9319/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9319/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Client Nodes{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6127818]]
* {color:#013220}IgniteClientNodesTestSuite:
IgnitePdsOnClientTest.testStartClientWithPersistenceConfiguration -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6127913buildTypeId=IgniteTests24Java8_RunAll]
> Unexpected initialization of MaintainanceFileStore on client nodes
> --
>
> Key: IGNITE-15274
> URL: https://issues.apache.org/jira/browse/IGNITE-15274
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.11
>Reporter: Anton Vinogradov
>Assignee: Nikolay Izhikov
>Priority: Blocker
> Labels: newbie
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Node has a client flag but fails on persistence check.
> {noformat}
> [2021-08-09 06:54:24,056][WARN ][main][MaintenanceProcessor] Caught exception
> when starting MaintenanceProcessor, maintenance mode won't be entered
> class org.apache.ignite.IgniteCheckedException: Directory does not exist and
> cannot be created: /mnt/ssd/persistence
> at
> org.apache.ignite.internal.util.IgniteUtils.resolveWorkDirectory(IgniteUtils.java:9670)
> at
> org.apache.ignite.internal.processors.cache.persistence.filename.PdsConsistentIdProcessor.resolvePersistentStoreBasePath(PdsConsistentIdProcessor.java:453)
> at
> org.apache.ignite.internal.processors.cache.persistence.filename.PdsConsistentIdProcessor.prepareNewSettings(PdsConsistentIdProcessor.java:160)
> at
> org.apache.ignite.internal.processors.cache.persistence.filename.PdsConsistentIdProcessor.resolveFolders(PdsConsistentIdProcessor.java:140)
> at
> org.apache.ignite.internal.maintenance.MaintenanceFileStore.init(MaintenanceFileStore.java:103)
> at
> org.apache.ignite.internal.maintenance.MaintenanceProcessor.start(MaintenanceProcessor.java:137)
> at
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1986)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1211)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2112)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1758)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:641)
> at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66)
> at org.apache.ignite.yardstick.IgniteNode.start(IgniteNode.java:215)
> at
> org.apache.ignite.yardstick.IgniteAbstractBenchmark.setUp(IgniteAbstractBenchmark.java:65)
> at
> org.apache.ignite.yardstick.cache.IgniteCacheAbstractBenchmark.setUp(IgniteCacheAbstractBenchmark.java:108)
> at
> org.yardstickframework.BenchmarkDriverStartUp.main(BenchmarkDriverStartUp.java:130)
> {noformat}
> Such check should not happen.
> Config which leads to the failure (this config was used at Yardstick, so
> clientMode was set by Yardstick):
> {noformat}
>
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd;>
>
> class="org.apache.ignite.configuration.IgniteConfiguration"
> parent="base-ignite.cfg">
>
>
>
>
>class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>
>class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>name="addresses">
>
>
> 10.0.0.2:47500..47509
>
> 10.0.0.3:47500..47509
>
> 10.0.0.4:47500..47509
>
>
>
>
[jira] [Created] (IGNITE-15299) Test testClusterSnapshotCheckWithNodeFilter is flaky
Maxim Muzafarov created IGNITE-15299:
Summary: Test testClusterSnapshotCheckWithNodeFilter is flaky
Key: IGNITE-15299
URL: https://issues.apache.org/jira/browse/IGNITE-15299
Project: Ignite
Issue Type: Test
Reporter: Maxim Muzafarov
Not all of snapshot temporary files removed after snapshot processing.
Investigation and fix is required.
{code}
java.lang.AssertionError: Snapshot working directory must be empty at the
moment test execution stopped:
/opt/buildagent/work/7bc1c54bc719b67c/work/db/snapshot_IgniteClusterSnapshotCheckWithIndexesTest1/snp
expected:<0> but was:<513>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at
org.apache.ignite.testframework.junits.JUnitAssertAware.assertEquals(JUnitAssertAware.java:119)
at
org.apache.ignite.internal.processors.cache.persistence.snapshot.AbstractSnapshotSelfTest.afterTestSnapshot(AbstractSnapshotSelfTest.java:163)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2432)
at java.lang.Thread.run(Thread.java:748)
{code}
See run history:
https://ci.ignite.apache.org/test/5931616805550780799?currentProjectId=IgniteTests24Java8=%3Cdefault%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15292) Update Ignite dependency: httpclient&
[ https://issues.apache.org/jira/browse/IGNITE-15292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr reassigned IGNITE-15292: -- Assignee: Aleksandr > Update Ignite dependency: httpclient& > -- > > Key: IGNITE-15292 > URL: https://issues.apache.org/jira/browse/IGNITE-15292 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > Update httpclient dependency 4.5.1 to 4.5.13 and httpcore 4.4.3 to 4.4.14 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15298) Implement RAFT snapshots for persistent partitions storage
Semyon Danilov created IGNITE-15298: --- Summary: Implement RAFT snapshots for persistent partitions storage Key: IGNITE-15298 URL: https://issues.apache.org/jira/browse/IGNITE-15298 Project: Ignite Issue Type: Bug Reporter: Semyon Danilov Assignee: Semyon Danilov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15298) Implement RAFT snapshots for persistent partitions storage
[ https://issues.apache.org/jira/browse/IGNITE-15298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semyon Danilov updated IGNITE-15298: Fix Version/s: 3.0.0-alpha3 > Implement RAFT snapshots for persistent partitions storage > --- > > Key: IGNITE-15298 > URL: https://issues.apache.org/jira/browse/IGNITE-15298 > Project: Ignite > Issue Type: Bug >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15297) Spi-wait in ConfigurationChanger should be removed
Ivan Bessonov created IGNITE-15297: -- Summary: Spi-wait in ConfigurationChanger should be removed Key: IGNITE-15297 URL: https://issues.apache.org/jira/browse/IGNITE-15297 Project: Ignite Issue Type: Bug Affects Versions: 3.0.0-alpha2 Reporter: Ivan Bessonov Assignee: Ivan Bessonov Fix For: 3.0.0-alpha3 Futures composition should be used instead -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15296) Generated change methods don't throw valid NP exceptions
Ivan Bessonov created IGNITE-15296: -- Summary: Generated change methods don't throw valid NP exceptions Key: IGNITE-15296 URL: https://issues.apache.org/jira/browse/IGNITE-15296 Project: Ignite Issue Type: Bug Affects Versions: 3.0.0-alpha2 Reporter: Ivan Bessonov Assignee: Ivan Bessonov Fix For: 3.0.0-alpha3 Bug in ConfigurationAsmGenerator -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15272) Raft group not being able to refresh leader
[ https://issues.apache.org/jira/browse/IGNITE-15272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semyon Danilov updated IGNITE-15272: Description: If a raft group is being started within a message handler the cluster will hang forever, as the raft group service constructor is sending a RefreshLeader request and waits on the response future while netty thread, managing the connection, as well as Project Reactor's DirectProcessor won't be able to process the response . We need to make this operation asynchronous. > Raft group not being able to refresh leader > --- > > Key: IGNITE-15272 > URL: https://issues.apache.org/jira/browse/IGNITE-15272 > Project: Ignite > Issue Type: Bug >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > > If a raft group is being started within a message handler the cluster will > hang forever, as the raft group service constructor is sending a > RefreshLeader request and waits on the response future while netty thread, > managing the connection, as well as Project Reactor's DirectProcessor won't > be able to process the response . We need to make this operation asynchronous. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15295) Server node that has an empty checkpoint file-XXX-START.bin does not start
[
https://issues.apache.org/jira/browse/IGNITE-15295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov updated IGNITE-15295:
--
Ignite Flags: (was: Docs Required,Release Notes Required)
> Server node that has an empty checkpoint file-XXX-START.bin does not start
> --
>
> Key: IGNITE-15295
> URL: https://issues.apache.org/jira/browse/IGNITE-15295
> Project: Ignite
> Issue Type: Improvement
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
>
> When starting a server node that has an empty checkpoint file-XXX-START.bin
> this node does not start.
> {code:java}
> 2021-06-08
> 16:00:33.383[ERROR][Thread-19][o.a.i.i.IgniteKernal%DPL_GRID%DplGridNodeName]
> Exception during start processors, node will be stopped and close connections
> 2java.nio.BufferUnderflowException: null
> 3at java.nio.Buffer.nextGetIndex(Buffer.java:532)
> 4at java.nio.HeapByteBuffer.getLong(HeapByteBuffer.java:417)
> 5at
> org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointMarkersStorage.readPointer(CheckpointMarkersStorage.java:301)
> 6at
> org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointMarkersStorage.readCheckpointStatus(CheckpointMarkersStorage.java:218)
> 7at
> org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointManager.readCheckpointStatus(CheckpointManager.java:265)
> 8at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointStatus(GridCacheDatabaseSharedManager.java:1642)
> 9at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:584)
> 10at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:2999)
> 11at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1205)
> 12at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2105)
> 13at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1768)
> 14at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1147)
> 15at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:667)
> 16at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:593)
> 17at org.apache.ignite.Ignition.start(Ignition.java:319)
> 18at
> com.sbt.ignite.factory.IgniteFactory.getOrStartIgnite(IgniteFactory.java:139)
> 19at
> com.sbt.ignite.factory.IgniteFactory.getOrStartIgnite(IgniteFactory.java:91)
> 20at
> com.sbt.ignite.manager.IgniteLifecycleManagerImpl.startIgnite(IgniteLifecycleManagerImpl.java:82)
> 21at
> com.sbt.ignite.manager.IgniteLifecycleManagerImpl.init(IgniteLifecycleManagerImpl.java:73)
> 22at
> com.sbt.dpl.gridgain.container.DPLManagerLifecycleManager.initIgniteServiceHolder(DPLManagerLifecycleManager.java:170)
> 23at
> com.sbt.dpl.gridgain.container.DPLManagerLifecycleManager.dplContextInit(DPLManagerLifecycleManager.java:145)
> 24at
> com.sbt.dpl.gridgain.container.ContainerDPLFactory.(ContainerDPLFactory.java:80)
> 25at
> com.sbt.dpl.gridgain.springsupport.SpringDPLFactory.init(SpringDPLFactory.java:74)
> {code}
> Checkpoint marker is always fully written in the temp file first, and then
> this file is renamed (see
> {noformat}
> org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointMarkersStorage#writeCheckpointEntry(java.nio.ByteBuffer,
>
> org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointEntry,
>
> org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointEntryType,
> boolean){noformat}
> )
> So the root cause of this error is not clear, unless file was changed
> somehow. We need extended information if such error will happen in future,
> but in this case we have nothing for analysis (LFS was cleared by the
> customer right after this error happened).
> In the same time we can’t guarantee correctness of work when checkpoint
> markers are inconsistent. We can’t just ignore them, if they are broken, and
> can’t recover from previous checkpoint just as simple.
> But it seems reasonable to catch all reading-related exceptions in
> org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointMarkersStorage#readPointer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15295) Server node that has an empty checkpoint file-XXX-START.bin does not start
Denis Chudov created IGNITE-15295:
-
Summary: Server node that has an empty checkpoint
file-XXX-START.bin does not start
Key: IGNITE-15295
URL: https://issues.apache.org/jira/browse/IGNITE-15295
Project: Ignite
Issue Type: Improvement
Reporter: Denis Chudov
Assignee: Denis Chudov
When starting a server node that has an empty checkpoint file-XXX-START.bin
this node does not start.
{code:java}
2021-06-08
16:00:33.383[ERROR][Thread-19][o.a.i.i.IgniteKernal%DPL_GRID%DplGridNodeName]
Exception during start processors, node will be stopped and close connections
2java.nio.BufferUnderflowException: null
3at java.nio.Buffer.nextGetIndex(Buffer.java:532)
4at java.nio.HeapByteBuffer.getLong(HeapByteBuffer.java:417)
5at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointMarkersStorage.readPointer(CheckpointMarkersStorage.java:301)
6at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointMarkersStorage.readCheckpointStatus(CheckpointMarkersStorage.java:218)
7at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointManager.readCheckpointStatus(CheckpointManager.java:265)
8at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointStatus(GridCacheDatabaseSharedManager.java:1642)
9at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:584)
10at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:2999)
11at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1205)
12at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2105)
13at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1768)
14at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1147)
15at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:667)
16at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:593)
17at org.apache.ignite.Ignition.start(Ignition.java:319)
18at
com.sbt.ignite.factory.IgniteFactory.getOrStartIgnite(IgniteFactory.java:139)
19at
com.sbt.ignite.factory.IgniteFactory.getOrStartIgnite(IgniteFactory.java:91)
20at
com.sbt.ignite.manager.IgniteLifecycleManagerImpl.startIgnite(IgniteLifecycleManagerImpl.java:82)
21at
com.sbt.ignite.manager.IgniteLifecycleManagerImpl.init(IgniteLifecycleManagerImpl.java:73)
22at
com.sbt.dpl.gridgain.container.DPLManagerLifecycleManager.initIgniteServiceHolder(DPLManagerLifecycleManager.java:170)
23at
com.sbt.dpl.gridgain.container.DPLManagerLifecycleManager.dplContextInit(DPLManagerLifecycleManager.java:145)
24at
com.sbt.dpl.gridgain.container.ContainerDPLFactory.(ContainerDPLFactory.java:80)
25at
com.sbt.dpl.gridgain.springsupport.SpringDPLFactory.init(SpringDPLFactory.java:74)
{code}
Checkpoint marker is always fully written in the temp file first, and then this
file is renamed (see
{noformat}
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointMarkersStorage#writeCheckpointEntry(java.nio.ByteBuffer,
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointEntry,
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointEntryType,
boolean){noformat}
)
So the root cause of this error is not clear, unless file was changed somehow.
We need extended information if such error will happen in future, but in this
case we have nothing for analysis (LFS was cleared by the customer right after
this error happened).
In the same time we can’t guarantee correctness of work when checkpoint markers
are inconsistent. We can’t just ignore them, if they are broken, and can’t
recover from previous checkpoint just as simple.
But it seems reasonable to catch all reading-related exceptions in
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointMarkersStorage#readPointer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15294) CopySessionTest#testOnRpcReturnedRetry flaky
Kirill Tkalenko created IGNITE-15294: Summary: CopySessionTest#testOnRpcReturnedRetry flaky Key: IGNITE-15294 URL: https://issues.apache.org/jira/browse/IGNITE-15294 Project: Ignite Issue Type: Bug Reporter: Kirill Tkalenko Fix For: 3.0.0-alpha3 https://ci.ignite.apache.org/viewLog.html?buildId=6128555=buildResultsDiv=ignite3_Test_RunUnitTests -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15254) Tuple API should be decoupled from Table
[ https://issues.apache.org/jira/browse/IGNITE-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15254: -- Labels: iep-54 ignite-3 (was: ignite-3) > Tuple API should be decoupled from Table > > > Key: IGNITE-15254 > URL: https://issues.apache.org/jira/browse/IGNITE-15254 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 3.0.0-alpha2 >Reporter: Valentin Kulichenko >Priority: Major > Labels: iep-54, ignite-3 > Fix For: 3.0.0-alpha3 > > > Currently, a tuple can be created via a builder which can be acquired from a > table. This is counterintuitive because in the general case, a tuple does not > have a direct relation with a particular table (think of a tuple that is a > part of a SQL result set, for example). > Instead, we should treat Tuple as a simple data structure that can be reused > for multiple purposes. That said, let's do the following changes to the API: > * Make Tuple mutable (i.e., add setters). > * Get rid of the builder, as it becomes redundant. > * Move tuple creation from the Table API to Ignite API. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15025) Add Maven check scripts to VCS
[ https://issues.apache.org/jira/browse/IGNITE-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398023#comment-17398023 ] Peter Ivanov commented on IGNITE-15025: --- [~amashenkov], I've updated script with all comments you've provided. Please, check. > Add Maven check scripts to VCS > -- > > Key: IGNITE-15025 > URL: https://issues.apache.org/jira/browse/IGNITE-15025 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Time Spent: 2h 20m > Remaining Estimate: 0h > > Currently, only TC has scripts for Maven checks which leads to several > problems: > # Developers can't use them to check code locally > # Scripts can be lost with TC in inaccurate configuration operation. > It is required to move scripts to Ignite's codebase and call them from TC > build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15256) ClassNotFoundException on attempt to invoke service method from Java ThinClient after cluster failover
[
https://issues.apache.org/jira/browse/IGNITE-15256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17397994#comment-17397994
]
Pavel Tupitsyn commented on IGNITE-15256:
-
[~ivan.fedorenkov] the PR looks good to me in gereral. Please see a few
comments on GitHub.
Also please update your branch from master, then re-run the CI to make sure
there are no blockers.
> ClassNotFoundException on attempt to invoke service method from Java
> ThinClient after cluster failover
> --
>
> Key: IGNITE-15256
> URL: https://issues.apache.org/jira/browse/IGNITE-15256
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.10
>Reporter: Ivan Fedorenkov
>Assignee: Ivan Fedorenkov
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Say, we have a thin client that uses some ignite service. This service
> exposes a method with an Externalizable input parameter. If cluster fails
> over after some period of successful interactions between the cluster and the
> client the following exception could be observed in cluster logs:
> {code:java}
> [2021-08-04
> 23:22:44,695][ERROR][client-connector-#114%client.ReliabilityTest%][ClientListenerNioListener]
> Failed to parse client request.
> class org.apache.ignite.binary.BinaryObjectException: Failed to unmarshal
> object with optimized marshaller
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadOptimized(BinaryUtils.java:1819)
> at
> org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:2034)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readObjectDetached(BinaryReaderExImpl.java:1341)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readObjectDetached(BinaryReaderExImpl.java:1336)
> at
> org.apache.ignite.internal.processors.platform.client.service.ClientServiceInvokeRequest.(ClientServiceInvokeRequest.java:126)
> at
> org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:486)
> at
> org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:311)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:164)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:55)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
> at
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshallerInaccessibleClassException:
> Failed to find class with given class loader for unmarshalling (make sure
> same versions of all classes are available on all nodes or enable
> peer-class-loading) [clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
> cls=Failed to resolve class name [platformId=0, platform=Java,
> typeId=-771474336]]
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.unmarshal0(OptimizedMarshaller.java:257)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.unmarshal0(OptimizedMarshaller.java:225)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadOptimized(BinaryUtils.java:1816)
> ... 16 more
> Caused by: java.lang.ClassNotFoundException: Failed to resolve class name
> [platformId=0, platform=Java, typeId=-771474336]
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(MarshallerContextImpl.java:459)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(MarshallerContextImpl.java:384)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(MarshallerContextImpl.java:371)
> at
>
[jira] [Commented] (IGNITE-13019) Unexpected JOIN result when querying a single-node cluster
[
https://issues.apache.org/jira/browse/IGNITE-13019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17397989#comment-17397989
]
Andrey Mashenkov commented on IGNITE-13019:
---
[~timonin.maksim], PR looks good, except the one thing: class name
QueryPartitionsChecker is irrelevant.
QueryPartitionsChecker is used for examining the AST tree to extract some
information, not only related to partitions.
Let's fix the class name and proceed with merging.
> Unexpected JOIN result when querying a single-node cluster
> --
>
> Key: IGNITE-13019
> URL: https://issues.apache.org/jira/browse/IGNITE-13019
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.8
>Reporter: Evgeny Stanilovsky
>Assignee: Maksim Timonin
>Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Check reproducer near,
> seems something wrong with pkey logic , if we change it - results will be ok.
> {code:java}
> @Test
> public void test() throws Exception {
> inlineSize = 10;
> startGrid(0);
> String t1 = "CREATE TABLE dept\n" +
> " (\n" +
> "deptno LONG,\n" +
> "dname VARCHAR,\n" +
> "loc VARCHAR,\n" +
> "CONSTRAINT pk_dept PRIMARY KEY (deptno)\n" +
> " );";
> execSql(t1);
> String t2 = "CREATE TABLE emp\n" +
> " (\n" +
> "empno LONG,\n" +
> "ename VARCHAR,\n" +
> "job VARCHAR,\n" +
> "mgr INTEGER,\n" +
> "hiredate DATE,\n" +
> "sal LONG,\n" +
> "comm LONG,\n" +
> "deptno LONG,\n" +
> "CONSTRAINT pk_emp PRIMARY KEY (empno)\n" +
> " );";
> execSql(t2);
> execSql("insert into dept (deptno, dname, loc) values (10,
> 'ACCOUNTING', 'NEW YORK');");
> execSql("insert into dept (deptno, dname, loc) values(20, 'RESEARCH',
> 'DALLAS');");
> execSql("insert into dept (deptno, dname, loc) values(30, 'SALES',
> 'CHICAGO');");
> execSql("insert into emp (empno, ename, job, mgr, hiredate, sal,
> comm, deptno) values(7839, 'KING', 'PRESIDENT', null,
> to_date('17-11-1981','dd-mm-'), 5000, null, 10);");
> execSql("insert into emp (empno, ename, job, mgr, hiredate, sal,
> comm, deptno) values( 7698, 'BLAKE', 'MANAGER', 7839,
> to_date('1-5-1981','dd-mm-'), 2850, null, 30);");
> execSql("insert into emp (empno, ename, job, mgr, hiredate, sal,
> comm, deptno) values(7782, 'CLARK', 'MANAGER', 7839,
> to_date('9-6-1981','dd-mm-'), 2450, null, 10);");
> List> vals1 = execSql("SELECT d.deptno,\n" +
> "e.ename\n" +
> "FROM EMP e\n" +
> "INNER JOIN dept d\n" +
> "ON e.deptno = d.deptno AND e.deptno = 10;");
> assertEquals(vals1.size(), 2);
> List> vals2 = execSql("SELECT d.deptno,\n" +
> "e.ename\n" +
> "FROM EMP e\n" +
> "INNER JOIN dept d\n" +
> "ON e.deptno = d.deptno AND d.DEPTNO = 10;");
> //assertEquals(vals2.size(), 2); <--* uncomment for fail*
> execSql("drop table dept");
> String t3 = "CREATE TABLE dept\n" +
> " (\n" +
> "deptno LONG,\n" +
> "dname VARCHAR,\n" +
> "loc VARCHAR,\n" +
> "CONSTRAINT pk_dept PRIMARY KEY (deptno, dname)\n" +
> " );";
> execSql(t3);
> execSql("insert into dept (deptno, dname, loc) values (10,
> 'ACCOUNTING', 'NEW YORK');");
> execSql("insert into dept (deptno, dname, loc) values(20, 'RESEARCH',
> 'DALLAS');");
> execSql("insert into dept (deptno, dname, loc) values(30, 'SALES',
> 'CHICAGO');");
> List> vals11 = execSql("SELECT d.deptno,\n" +
> "e.ename\n" +
> "FROM EMP e\n" +
> "INNER JOIN dept d\n" +
> "ON e.deptno = d.deptno AND e.deptno = 10;");
> assertEquals(vals11.size(), 2);
> List> vals22 = execSql("SELECT d.deptno,\n" +
> "e.ename\n" +
> "FROM EMP e\n" +
> "INNER JOIN dept d\n" +
> "ON e.deptno = d.deptno AND d.DEPTNO = 10;");
> assertEquals(vals22.size(), 2);
> }
> /** */
> private List> execSql(String qry) {
> return grid(0).context().query()
> .querySqlFields(new SqlFieldsQuery(qry).setLazy(true), false)
> .getAll();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12177) CPP: Add Java compute support
[ https://issues.apache.org/jira/browse/IGNITE-12177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17397985#comment-17397985 ] Pavel Tupitsyn commented on IGNITE-12177: - [~isapego] looks good to me, please see a few minor comments on GitHub. > CPP: Add Java compute support > - > > Key: IGNITE-12177 > URL: https://issues.apache.org/jira/browse/IGNITE-12177 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.7.5 >Reporter: Alexandr Shapkin >Assignee: Igor Sapego >Priority: Major > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently compute.h contains only platform-specific API declaration (C++). > But Ignite does allow a native Java task execution. This feature already has > been implemented for .NET platform. > Lets port the same changes to C++ client (use PlatformCompute#OP_EXEC_NATIVE). > > This would help us to create a workaround for a mixed platform cluster that > requires a compute calls. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15244) testLearnerServices is still flaky
[
https://issues.apache.org/jira/browse/IGNITE-15244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-15244:
Fix Version/s: 3.0.0-alpha3
> testLearnerServices is still flaky
> --
>
> Key: IGNITE-15244
> URL: https://issues.apache.org/jira/browse/IGNITE-15244
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Scherbakov
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> It seems the elected leader has stepped down because it decides all other
> nodes are dead, which means no hearbeats has been acked [1].
> another problem - after joining a new learner cluster state is not the same.
> Aug 03, 2021 5:54:46 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Start ensureSame, leader=JRaftNode
> [nodeId=]
> Aug 03, 2021 5:55:06 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: End ensureSame, leader=JRaftNode
> [nodeId=]
> [1]
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ignite.raft.jraft.core.ITCliServiceTest.sendTestTaskAndWait(ITCliServiceTest.java:178)
> at
> org.apache.ignite.raft.jraft.core.ITCliServiceTest.testLearnerServices(ITCliServiceTest.java:187)
> --- Stderr: ---
> Aug 03, 2021 7:31:39 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: >>> Start test method: testLearnerServices()
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Connection created [address=/0.0.0.0:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=1]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Starts FSMCaller successfully.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> WARNING: No data for snapshot reader
> target/work/ITCliServiceTest/testLearnerServices_1628008299722/172.17.0.6_5003/snapshot.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node init, term=0, lastLogId=LogId
> [index=0, term=0],
> conf=172.17.0.6:5003,172.17.0.6:5004,172.17.0.6:5005,172.17.0.6:5103/learner,172.17.0.6:5104/learner,
> oldConf=.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Start the RaftGroupService successfully
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Connection created [address=/0.0.0.0:5004]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=2]
> ^-- ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=1]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=2]
> ^-- ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Starts FSMCaller successfully.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> WARNING: No data for snapshot reader
> target/work/ITCliServiceTest/testLearnerServices_1628008299722/172.17.0.6_5004/snapshot.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node init, term=0, lastLogId=LogId
> [index=0, term=0],
> conf=172.17.0.6:5003,172.17.0.6:5004,172.17.0.6:5005,172.17.0.6:5103/learner,172.17.0.6:5104/learner,
> oldConf=.
> Aug 03, 2021 7:31:41 PM
[jira] [Updated] (IGNITE-15244) testLearnerServices is still flaky
[
https://issues.apache.org/jira/browse/IGNITE-15244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-15244:
Priority: Blocker (was: Major)
> testLearnerServices is still flaky
> --
>
> Key: IGNITE-15244
> URL: https://issues.apache.org/jira/browse/IGNITE-15244
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Scherbakov
>Priority: Blocker
> Labels: ignite-3
>
> It seems the elected leader has stepped down because it decides all other
> nodes are dead, which means no hearbeats has been acked [1].
> another problem - after joining a new learner cluster state is not the same.
> Aug 03, 2021 5:54:46 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Start ensureSame, leader=JRaftNode
> [nodeId=]
> Aug 03, 2021 5:55:06 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: End ensureSame, leader=JRaftNode
> [nodeId=]
> [1]
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ignite.raft.jraft.core.ITCliServiceTest.sendTestTaskAndWait(ITCliServiceTest.java:178)
> at
> org.apache.ignite.raft.jraft.core.ITCliServiceTest.testLearnerServices(ITCliServiceTest.java:187)
> --- Stderr: ---
> Aug 03, 2021 7:31:39 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: >>> Start test method: testLearnerServices()
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Connection created [address=/0.0.0.0:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=1]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Starts FSMCaller successfully.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> WARNING: No data for snapshot reader
> target/work/ITCliServiceTest/testLearnerServices_1628008299722/172.17.0.6_5003/snapshot.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node init, term=0, lastLogId=LogId
> [index=0, term=0],
> conf=172.17.0.6:5003,172.17.0.6:5004,172.17.0.6:5005,172.17.0.6:5103/learner,172.17.0.6:5104/learner,
> oldConf=.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Start the RaftGroupService successfully
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Connection created [address=/0.0.0.0:5004]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=2]
> ^-- ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=1]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=2]
> ^-- ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Starts FSMCaller successfully.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> WARNING: No data for snapshot reader
> target/work/ITCliServiceTest/testLearnerServices_1628008299722/172.17.0.6_5004/snapshot.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node init, term=0, lastLogId=LogId
> [index=0, term=0],
> conf=172.17.0.6:5003,172.17.0.6:5004,172.17.0.6:5005,172.17.0.6:5103/learner,172.17.0.6:5104/learner,
> oldConf=.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
>
[jira] [Commented] (IGNITE-15004) Calcite engine. LIKE ESCAPE fails with empty escape string
[
https://issues.apache.org/jira/browse/IGNITE-15004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17397946#comment-17397946
]
Aleksey Plekhanov commented on IGNITE-15004:
Some vendors don't support empty escape characters too (for example Oracle) and
it's not a bug from the Calcite point of view (there is explicit check for
length == 1), but our current H2 engine support it, and some other RDBMS
support it (PostgreSQL, MySQL).
> Calcite engine. LIKE ESCAPE fails with empty escape string
> --
>
> Key: IGNITE-15004
> URL: https://issues.apache.org/jira/browse/IGNITE-15004
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> {{SELECT '%_' LIKE '%_' ESCAPE ''}}
> error:
> {code}
> class org.apache.ignite.IgniteException: Unexpected exception
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:244)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:68)
> 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)
> Caused by: java.lang.RuntimeException: Invalid escape character ''
> at org.apache.calcite.runtime.Like.invalidEscapeCharacter(Like.java:104)
> at org.apache.calcite.runtime.Like.sqlToRegexLike(Like.java:56)
> at org.apache.calcite.runtime.SqlFunctions.like(SqlFunctions.java:594)
> at SC.execute(Unknown Source)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.ExpressionFactoryImpl$ProjectImpl.apply(ExpressionFactoryImpl.java:387)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ProjectNode.push(ProjectNode.java:63)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ScanNode.push(ScanNode.java:107)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:239)
> ... 4 more
> {code}
> Test:
> {{function/string/test_like_escape.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14808) Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
[
https://issues.apache.org/jira/browse/IGNITE-14808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov reassigned IGNITE-14808:
-
Assignee: Konstantin Orlov (was: Evgeny Stanilovsky)
> Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
> -
>
> Key: IGNITE-14808
> URL: https://issues.apache.org/jira/browse/IGNITE-14808
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Evgeny Stanilovsky
>Assignee: Konstantin Orlov
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> queries like
> {noformat}
> FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k ORDER BY i
> NULLS FIRST
> {noformat} will bring to erroneous results. Also some tests from /sql/join*
> have no ordering thus results are not equal to pattern.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14808) Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
[
https://issues.apache.org/jira/browse/IGNITE-14808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17397943#comment-17397943
]
Konstantin Orlov commented on IGNITE-14808:
---
[~tledkov-gridgain], [~alexpl], folks, could you please do a review? I've
reworked the patch a bit.
> Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
> -
>
> Key: IGNITE-14808
> URL: https://issues.apache.org/jira/browse/IGNITE-14808
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> queries like
> {noformat}
> FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k ORDER BY i
> NULLS FIRST
> {noformat} will bring to erroneous results. Also some tests from /sql/join*
> have no ordering thus results are not equal to pattern.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15270) Fix rebalance test
[ https://issues.apache.org/jira/browse/IGNITE-15270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17397913#comment-17397913 ] Anton Vinogradov commented on IGNITE-15270: --- Merged to master branch. [~map7000], thanks for your contribution! > Fix rebalance test > -- > > Key: IGNITE-15270 > URL: https://issues.apache.org/jira/browse/IGNITE-15270 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Ducktape rebalance test don't work on dev version because it tries to read > cache statistics on deactivated cluster. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15265) Update Ignite dependency: Netty
[ https://issues.apache.org/jira/browse/IGNITE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17397871#comment-17397871 ] Aleksandr commented on IGNITE-15265: [~dpavlov] I removed the documentation and additionally renamed the dependency name from azure.netty to netty. . > Update Ignite dependency: Netty > --- > > Key: IGNITE-15265 > URL: https://issues.apache.org/jira/browse/IGNITE-15265 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > > Update Netty dependency 4.1.54.Final to 4.1.66.Final > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15196) Null seems to be an unexpected result for ScaleCubeMessagingService#invoke() on node stopping
[
https://issues.apache.org/jira/browse/IGNITE-15196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-15196:
---
Labels: iep-67 ignite-3 (was: ignite-3)
> Null seems to be an unexpected result for ScaleCubeMessagingService#invoke()
> on node stopping
> --
>
> Key: IGNITE-15196
> URL: https://issues.apache.org/jira/browse/IGNITE-15196
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexander Lapin
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: iep-67, ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In case of node stop it's possible to get null as a result of an invoke
> operation.
> {code:java}
> return cluster
> .requestResponse(fromNetworkAddress(addr), message)
> .timeout(Duration.ofMillis(timeout))
> .toFuture()
> .thenApply(m -> m == null ? null : m.data()); // The result can be null
> on node stopping.
> {code}
> It's a rather confusing behavior that produces NPE. See IGNITE-15195 for more
> details. In order not not fail with NPE I've updated null handling in a
> following way
> {code:java}
> return cluster
> .requestResponse(fromNetworkAddress(addr), message)
> .timeout(Duration.ofMillis(timeout))
> .toFuture()
> .thenApply(m -> {
> if (m == null)
> throw new CompletionException(new NodeStoppingCheckedException());
> else
> return m.data();
> }); // The result can be null on node stopping.{code}
> within IGNITE-15148
> In order to reproduce given issue restore original
> {code:java}
> .thenApply(m -> m == null ? null : m.data());
> {code}
> and run
> {code:java}
>
> org.apache.ignite.internal.runner.app.IgnitionTest#testNodeStartWithoutBootstrapConfiguration{code}
> several times.
> As a result NPE will be logged on node stop:
> {code:java}
> SEVERE: Unexpected exception
> class org.apache.ignite.lang.IgniteInternalException:
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.metastorage.client.CursorImpl$InnerIterator.hasNext(CursorImpl.java:109)
> at
> org.apache.ignite.internal.metastorage.client.MetaStorageServiceImpl$WatchProcessor$Watcher.run(MetaStorageServiceImpl.java:446)
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.NullPointerException
> at
> java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
> at
> java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999)
> at
> org.apache.ignite.internal.metastorage.client.CursorImpl$InnerIterator.hasNext(CursorImpl.java:101)
> ... 1 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.raft.client.service.impl.RaftGroupServiceImpl.lambda$run$15(RaftGroupServiceImpl.java:323)
> at
> java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
> at
> org.apache.ignite.raft.client.service.impl.RaftGroupServiceImpl$1.accept(RaftGroupServiceImpl.java:406)
> at
> org.apache.ignite.raft.client.service.impl.RaftGroupServiceImpl$1.accept(RaftGroupServiceImpl.java:360)
> at
> java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
> at
> java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
> at
> reactor.core.publisher.MonoToCompletableFuture.onComplete(MonoToCompletableFuture.java:83)
> at
> reactor.core.publisher.SerializedSubscriber.onComplete(SerializedSubscriber.java:146)
> at
> reactor.core.publisher.FluxTimeout$TimeoutMainSubscriber.onComplete(FluxTimeout.java:228)
> at
> reactor.core.publisher.MonoCreate$DefaultMonoSink.success(MonoCreate.java:129)
> at
> reactor.core.publisher.LambdaSubscriber.onComplete(LambdaSubscriber.java:132)
> at
> reactor.core.publisher.FluxTake$TakeFuseableSubscriber.onComplete(FluxTake.java:423)
> at
> reactor.core.publisher.FluxFilterFuseable$FilterFuseableSubscriber.onComplete(FluxFilterFuseable.java:165)
> at
> reactor.core.publisher.FluxFilterFuseable$FilterFuseableConditionalSubscriber.onComplete(FluxFilterFuseable.java:384)
> at
>
[jira] [Updated] (IGNITE-15196) Null seems to be an unexpected result for ScaleCubeMessagingService#invoke() on node stopping
[
https://issues.apache.org/jira/browse/IGNITE-15196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-15196:
---
Affects Version/s: 3.0.0-alpha2
> Null seems to be an unexpected result for ScaleCubeMessagingService#invoke()
> on node stopping
> --
>
> Key: IGNITE-15196
> URL: https://issues.apache.org/jira/browse/IGNITE-15196
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha2
>Reporter: Alexander Lapin
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: iep-67, ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In case of node stop it's possible to get null as a result of an invoke
> operation.
> {code:java}
> return cluster
> .requestResponse(fromNetworkAddress(addr), message)
> .timeout(Duration.ofMillis(timeout))
> .toFuture()
> .thenApply(m -> m == null ? null : m.data()); // The result can be null
> on node stopping.
> {code}
> It's a rather confusing behavior that produces NPE. See IGNITE-15195 for more
> details. In order not not fail with NPE I've updated null handling in a
> following way
> {code:java}
> return cluster
> .requestResponse(fromNetworkAddress(addr), message)
> .timeout(Duration.ofMillis(timeout))
> .toFuture()
> .thenApply(m -> {
> if (m == null)
> throw new CompletionException(new NodeStoppingCheckedException());
> else
> return m.data();
> }); // The result can be null on node stopping.{code}
> within IGNITE-15148
> In order to reproduce given issue restore original
> {code:java}
> .thenApply(m -> m == null ? null : m.data());
> {code}
> and run
> {code:java}
>
> org.apache.ignite.internal.runner.app.IgnitionTest#testNodeStartWithoutBootstrapConfiguration{code}
> several times.
> As a result NPE will be logged on node stop:
> {code:java}
> SEVERE: Unexpected exception
> class org.apache.ignite.lang.IgniteInternalException:
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.metastorage.client.CursorImpl$InnerIterator.hasNext(CursorImpl.java:109)
> at
> org.apache.ignite.internal.metastorage.client.MetaStorageServiceImpl$WatchProcessor$Watcher.run(MetaStorageServiceImpl.java:446)
> Caused by: java.util.concurrent.ExecutionException:
> java.lang.NullPointerException
> at
> java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
> at
> java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999)
> at
> org.apache.ignite.internal.metastorage.client.CursorImpl$InnerIterator.hasNext(CursorImpl.java:101)
> ... 1 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.raft.client.service.impl.RaftGroupServiceImpl.lambda$run$15(RaftGroupServiceImpl.java:323)
> at
> java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
> at
> org.apache.ignite.raft.client.service.impl.RaftGroupServiceImpl$1.accept(RaftGroupServiceImpl.java:406)
> at
> org.apache.ignite.raft.client.service.impl.RaftGroupServiceImpl$1.accept(RaftGroupServiceImpl.java:360)
> at
> java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
> at
> java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
> at
> reactor.core.publisher.MonoToCompletableFuture.onComplete(MonoToCompletableFuture.java:83)
> at
> reactor.core.publisher.SerializedSubscriber.onComplete(SerializedSubscriber.java:146)
> at
> reactor.core.publisher.FluxTimeout$TimeoutMainSubscriber.onComplete(FluxTimeout.java:228)
> at
> reactor.core.publisher.MonoCreate$DefaultMonoSink.success(MonoCreate.java:129)
> at
> reactor.core.publisher.LambdaSubscriber.onComplete(LambdaSubscriber.java:132)
> at
> reactor.core.publisher.FluxTake$TakeFuseableSubscriber.onComplete(FluxTake.java:423)
> at
> reactor.core.publisher.FluxFilterFuseable$FilterFuseableSubscriber.onComplete(FluxFilterFuseable.java:165)
> at
> reactor.core.publisher.FluxFilterFuseable$FilterFuseableConditionalSubscriber.onComplete(FluxFilterFuseable.java:384)
> at
>
