[jira] [Commented] (IGNITE-16072) Add configurable throttling for the spanshot process
[
https://issues.apache.org/jira/browse/IGNITE-16072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501184#comment-17501184
]
Ignite TC Bot commented on IGNITE-16072:
{panel:title=Branch: [pull/9833/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9833/head] Base: [master] : New Tests
(30)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 2{color} [[tests
30|https://ci.ignite.apache.org/viewLog.html?buildId=6444031]]
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testCdcSingleton[specificConsistentId=false,walMode=FSYNC,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/791412502@296e281a,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testMultiNodeConsumption[specificConsistentId=false,walMode=FSYNC,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/791412502@296e281a,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testMultiNodeConsumption[specificConsistentId=true,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/791412502@296e281a,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReReadWhenStateWasNotStored[specificConsistentId=true,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/791412502@296e281a,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadBeforeGracefulShutdown[specificConsistentId=true,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/791412502@296e281a,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadAllKeys[specificConsistentId=true,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/791412502@296e281a,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReReadWhenStateWasNotStored[specificConsistentId=false,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/791412502@296e281a,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadBeforeGracefulShutdown[specificConsistentId=false,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/791412502@296e281a,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadAllKeys[specificConsistentId=false,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/791412502@296e281a,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testCdcSingleton[specificConsistentId=true,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/791412502@296e281a,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadBeforeGracefulShutdown[specificConsistentId=true,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/791412502@296e281a,pageSz=8,192]
- PASSED{color}
... and 19 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6444076buildTypeId=IgniteTests24Java8_RunAll]
> Add configurable throttling for the spanshot process
>
>
> Key: IGNITE-16072
> URL: https://issues.apache.org/jira/browse/IGNITE-16072
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43, ise
> Fix For: 2.13
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We want to add configurable throttling to the number of threads that perform
> a snapshot operation. The IGNITE-16014 have introduced the pool size
> configuration property, however, it is still possible that a node can become
> overloaded and unresponsive due to its attempts to copy data files on very
> slow HDDs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16653) Fix flaky ItBplusTreeFakeReuseSelfTest#testPutSizeLivelock
[ https://issues.apache.org/jira/browse/IGNITE-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-16653: - Epic Link: IGNITE-16232 > Fix flaky ItBplusTreeFakeReuseSelfTest#testPutSizeLivelock > -- > > Key: IGNITE-16653 > URL: https://issues.apache.org/jira/browse/IGNITE-16653 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Attachments: _Integration_Tests_Module_Page_Memory_72.log.zip > > > Flaky > [ItBplusTreeFakeReuseSelfTest#testPutSizeLivelock|https://ci.ignite.apache.org/viewLog.html?buildId=6445190=buildResultsDiv=ignite3_Test_IntegrationTests_ModulePageMemory#testNameId-8377900828894907526] > found, I'm attaching the > [^_Integration_Tests_Module_Page_Memory_72.log.zip]. > It is necessary to understand the reason and add a timeout for executing > tests and dumping threads. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16653) Fix flaky ItBplusTreeFakeReuseSelfTest#testPutSizeLivelock
Kirill Tkalenko created IGNITE-16653: Summary: Fix flaky ItBplusTreeFakeReuseSelfTest#testPutSizeLivelock Key: IGNITE-16653 URL: https://issues.apache.org/jira/browse/IGNITE-16653 Project: Ignite Issue Type: Task Reporter: Kirill Tkalenko Fix For: 3.0.0-alpha5 Attachments: _Integration_Tests_Module_Page_Memory_72.log.zip Flaky [ItBplusTreeFakeReuseSelfTest#testPutSizeLivelock|https://ci.ignite.apache.org/viewLog.html?buildId=6445190=buildResultsDiv=ignite3_Test_IntegrationTests_ModulePageMemory#testNameId-8377900828894907526] found, I'm attaching the [^_Integration_Tests_Module_Page_Memory_72.log.zip]. It is necessary to understand the reason and add a timeout for executing tests and dumping threads. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16645) Sql. Adoption of a bunch of calcite related tickets from Ignite-2 part2.
[ https://issues.apache.org/jira/browse/IGNITE-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-16645: Summary: Sql. Adoption of a bunch of calcite related tickets from Ignite-2 part2. (was: Sql. SetOp execution node cannot be rewinded.) > Sql. Adoption of a bunch of calcite related tickets from Ignite-2 part2. > > > Key: IGNITE-16645 > URL: https://issues.apache.org/jira/browse/IGNITE-16645 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Evgeny Stanilovsky >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > [SetOp execution node cannot be > rewinded|https://issues.apache.org/jira/browse/IGNITE-16228] > [Unexpected result of COUNT with multiple > parameters|https://issues.apache.org/jira/browse/IGNITE-16191] > [Memory leak in RelOptCluster during > mapping|https://issues.apache.org/jira/browse/IGNITE-16354] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16072) Add configurable throttling for the spanshot process
[ https://issues.apache.org/jira/browse/IGNITE-16072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501175#comment-17501175 ] Pavel Pereslegin commented on IGNITE-16072: --- [~alex_pl], thanks for the review! > Add configurable throttling for the spanshot process > > > Key: IGNITE-16072 > URL: https://issues.apache.org/jira/browse/IGNITE-16072 > Project: Ignite > Issue Type: Improvement >Reporter: Maxim Muzafarov >Assignee: Pavel Pereslegin >Priority: Major > Labels: iep-43, ise > Fix For: 2.13 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > We want to add configurable throttling to the number of threads that perform > a snapshot operation. The IGNITE-16014 have introduced the pool size > configuration property, however, it is still possible that a node can become > overloaded and unresponsive due to its attempts to copy data files on very > slow HDDs. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16640) Peer class loading failure should not be treated as a critical node failure
[
https://issues.apache.org/jira/browse/IGNITE-16640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501173#comment-17501173
]
Ignite TC Bot commented on IGNITE-16640:
{panel:title=Branch: [pull/9864/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9864/head] Base: [master] : New Tests
(34)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 2{color} [[tests
30|https://ci.ignite.apache.org/viewLog.html?buildId=6444386]]
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadBeforeGracefulShutdown[specificConsistentId=true,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadAllKeys[specificConsistentId=true,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testCdcSingleton[specificConsistentId=false,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testMultiNodeConsumption[specificConsistentId=false,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadAllKeys[specificConsistentId=false,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testCdcSingleton[specificConsistentId=true,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testMultiNodeConsumption[specificConsistentId=true,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReReadWhenStateWasNotStored[specificConsistentId=true,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testCdcSingleton[specificConsistentId=false,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testMultiNodeConsumption[specificConsistentId=false,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReReadWhenStateWasNotStored[specificConsistentId=false,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76,pageSz=8,192]
- PASSED{color}
... and 19 new tests
{color:#8b}Basic 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6444327]]
* {color:#013220}IgniteBasicTestSuite:
CommonFailureHandlerTest.nonP2PNoClassDefFoundErrorIsCritical - PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
P2PClassLoadingFailureHandlingTest.p2pClassLoadingProblemShouldNotCauseFailureHandling
- PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
CommonFailureHandlerTest.nonSpecificThrowableIsCritical - PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
CommonFailureHandlerTest.p2pNoClassDefFoundErrorIsNotCritical - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=631buildTypeId=IgniteTests24Java8_RunAll]
> Peer class loading failure should not be treated as a critical node failure
> ---
>
> Key: IGNITE-16640
> URL: https://issues.apache.org/jira/browse/IGNITE-16640
> Project: Ignite
> Issue Type: Bug
> Components: compute, persistence
>Affects Versions: 2.12
>Reporter: Roman Puchkovskiy
>Assignee: Roman Puchkovskiy
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The problematic scenario:
> # Enable p2p class-loading in the cluster
> # Create a cache
> # From a client, obtain a dataStreamer on that cache and set a receiver()
> which class is only present on the client (so that it is forced to be loaded
> using p2p)
> # The receiver class, during its operation (inside its receive() method),
> should initiate loading of another class only present on the client
> # If at the moment, when an attempt is made to load the class mentioned in
> item 4, the client is not available
[jira] [Commented] (IGNITE-16626) Mark the ignite-log4j as deprecated.
[ https://issues.apache.org/jira/browse/IGNITE-16626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501045#comment-17501045 ] Sergei Ryzhov commented on IGNITE-16626: [~namelchev] Thanks for the review > Mark the ignite-log4j as deprecated. > > > Key: IGNITE-16626 > URL: https://issues.apache.org/jira/browse/IGNITE-16626 > Project: Ignite > Issue Type: Improvement >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Minor > Labels: ise > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > Mark the ignite-log4j as deprecated. > will be removed later. > log4j 1.2.17 is not supported and contains critical vulnerabilities > Direct vulnerabilities: > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16626) Mark the ignite-log4j as deprecated.
[
https://issues.apache.org/jira/browse/IGNITE-16626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501039#comment-17501039
]
Ignite TC Bot commented on IGNITE-16626:
{panel:title=Branch: [pull/9861/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9861/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6331281buildTypeId=IgniteTests24Java8_RunAll]
> Mark the ignite-log4j as deprecated.
>
>
> Key: IGNITE-16626
> URL: https://issues.apache.org/jira/browse/IGNITE-16626
> Project: Ignite
> Issue Type: Improvement
>Reporter: Sergei Ryzhov
>Assignee: Sergei Ryzhov
>Priority: Minor
> Labels: ise
> Fix For: 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Mark the ignite-log4j as deprecated.
> will be removed later.
> log4j 1.2.17 is not supported and contains critical vulnerabilities
> Direct vulnerabilities:
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (IGNITE-16632) Calcite engine. Add calcite dependencies to TC build
[
https://issues.apache.org/jira/browse/IGNITE-16632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501012#comment-17501012
]
Aleksey Plekhanov edited comment on IGNITE-16632 at 3/3/22, 8:50 PM:
-
[~vveider], tests passed, thanks for the fix!
was (Author: alex_pl):
[~alex_pl] tests passed, thanks for the fix!
> Calcite engine. Add calcite dependencies to TC build
>
>
> Key: IGNITE-16632
> URL: https://issues.apache.org/jira/browse/IGNITE-16632
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksey Plekhanov
>Assignee: Petr Ivanov
>Priority: Major
> Labels: build, calcite
>
> Currently, a limited set of JARs is included in build artifacts
> ([https://ci.ignite.apache.org/admin/editRunType.html?id=buildType:IgniteTests24Java8_Build=RUNNER_286]).
> There are some new external dependencies for the new calcite module, that
> should be added too. Some test suites can't pass without these dependencies
> (C++ for example: [https://ci.ignite.apache.org/viewLog.html?buildId=6435330])
> {noformat}
> zip -ur run modules/calcite/target/libs/calcite-*.jar \
> modules/calcite/target/libs/avatica-*.jar \
> modules/calcite/target/libs/checker-qual-*.jar \
> modules/calcite/target/libs/commons-compiler-*.jar \
> modules/calcite/target/libs/esri-geometry-*.jar \
> modules/calcite/target/libs/guava-*.jar \
> modules/calcite/target/libs/janino-*.jar \
> modules/calcite/target/libs/json-path-*.jar {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16632) Calcite engine. Add calcite dependencies to TC build
[
https://issues.apache.org/jira/browse/IGNITE-16632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501012#comment-17501012
]
Aleksey Plekhanov commented on IGNITE-16632:
[~alex_pl] tests passed, thanks for the fix!
> Calcite engine. Add calcite dependencies to TC build
>
>
> Key: IGNITE-16632
> URL: https://issues.apache.org/jira/browse/IGNITE-16632
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksey Plekhanov
>Assignee: Petr Ivanov
>Priority: Major
> Labels: build, calcite
>
> Currently, a limited set of JARs is included in build artifacts
> ([https://ci.ignite.apache.org/admin/editRunType.html?id=buildType:IgniteTests24Java8_Build=RUNNER_286]).
> There are some new external dependencies for the new calcite module, that
> should be added too. Some test suites can't pass without these dependencies
> (C++ for example: [https://ci.ignite.apache.org/viewLog.html?buildId=6435330])
> {noformat}
> zip -ur run modules/calcite/target/libs/calcite-*.jar \
> modules/calcite/target/libs/avatica-*.jar \
> modules/calcite/target/libs/checker-qual-*.jar \
> modules/calcite/target/libs/commons-compiler-*.jar \
> modules/calcite/target/libs/esri-geometry-*.jar \
> modules/calcite/target/libs/guava-*.jar \
> modules/calcite/target/libs/janino-*.jar \
> modules/calcite/target/libs/json-path-*.jar {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-16652) Calcite engine. Fix minor issues for green TC bot visa
Aleksey Plekhanov created IGNITE-16652:
--
Summary: Calcite engine. Fix minor issues for green TC bot visa
Key: IGNITE-16652
URL: https://issues.apache.org/jira/browse/IGNITE-16652
Project: Ignite
Issue Type: Task
Reporter: Aleksey Plekhanov
* JDBC compatibility test fails for 2.9+ Ignite versions
* STATISTICS_GLOBAL_DATA system view should be added to tests
* .NET tests failed due to missing {{org.hamcrest}} dependency
* JavaDoc suite failed due to incorrect {{@inheritDoc}} tag usage
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IGNITE-16652) Calcite engine. Fix minor issues for green TC bot visa
[
https://issues.apache.org/jira/browse/IGNITE-16652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov reassigned IGNITE-16652:
--
Assignee: Aleksey Plekhanov
> Calcite engine. Fix minor issues for green TC bot visa
> --
>
> Key: IGNITE-16652
> URL: https://issues.apache.org/jira/browse/IGNITE-16652
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required
>
> * JDBC compatibility test fails for 2.9+ Ignite versions
> * STATISTICS_GLOBAL_DATA system view should be added to tests
> * .NET tests failed due to missing {{org.hamcrest}} dependency
> * JavaDoc suite failed due to incorrect {{@inheritDoc}} tag usage
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16530) Java thin: implement heartbeats
[
https://issues.apache.org/jira/browse/IGNITE-16530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500902#comment-17500902
]
Ignite TC Bot commented on IGNITE-16530:
{panel:title=Branch: [pull/9863/head] Base: [master] : Possible Blockers
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Basic 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6444144]]
{color:#d04437}Platform .NET (Windows){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6443456]]
* dll: EntityFrameworkCacheTest.TestOldEntriesCleanupMultithreaded - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}JDBC Driver{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6444187]]
* IgniteJdbcDriverTestSuite:
JdbcThinJdbcToCacheDataTypesCoverageTest.testIntDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false,
useBinaryArrays=false] - Test has low fail rate in base branch 0,0% and is not
flaky
{color:#d04437}Cache (Restarts) 2{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=6444155]]
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithPutSixNodesTwoBackups - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithPutFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithPutFourNodesNoBackups - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithPutTenNodesTwoBackups - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithPutEightNodesTwoBackups - Test
has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9863/head] Base: [master] : New Tests
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Thin Client: Java{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=6444196]]
* {color:#013220}ClientTestSuite:
ReliabilityTest.testServerDoesNotDisconnectIdleClientWithHeartbeats -
PASSED{color}
* {color:#013220}ClientTestSuite:
ReliabilityTestAsync.testServerDoesNotDisconnectIdleClientWithHeartbeats -
PASSED{color}
* {color:#013220}ClientTestSuite:
ReliabilityTestPartitionAware.testServerDoesNotDisconnectIdleClientWithHeartbeats
- PASSED{color}
* {color:#013220}ClientTestSuite:
ReliabilityTestPartitionAwareAsync.testServerDoesNotDisconnectIdleClientWithHeartbeats
- PASSED{color}
* {color:#013220}ClientTestSuite:
ClientConfigurationTest.testInvalidHeartbeatIntervalThrows - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6444248buildTypeId=IgniteTests24Java8_RunAll]
> Java thin: implement heartbeats
> ---
>
> Key: IGNITE-16530
> URL: https://issues.apache.org/jira/browse/IGNITE-16530
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: iep-83
> Fix For: 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Implement heartbeats as described in [IEP-83 Thin Client
> Keepalive|https://cwiki.apache.org/confluence/display/IGNITE/IEP-83+Thin+Client+Keepalive].
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16650) Exclude ignite-log4j, log4j 1.2.17
[ https://issues.apache.org/jira/browse/IGNITE-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-16650: --- Labels: ise (was: ) > Exclude ignite-log4j, log4j 1.2.17 > -- > > Key: IGNITE-16650 > URL: https://issues.apache.org/jira/browse/IGNITE-16650 > Project: Ignite > Issue Type: Bug >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Major > Labels: ise > > log4j 1.2.17 is not supported and contains critical vulnerabilities > https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces > I suggest excluding the ignite-log4j module from ignite > Direct vulnerabilities: > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16651) [nodejs-thin-client] replace logger with ignite-log4j2
[ https://issues.apache.org/jira/browse/IGNITE-16651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-16651: --- Labels: ise (was: ) > [nodejs-thin-client] replace logger with ignite-log4j2 > -- > > Key: IGNITE-16651 > URL: https://issues.apache.org/jira/browse/IGNITE-16651 > Project: Ignite > Issue Type: Improvement >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Major > Labels: ise > > module ignite-log4j deprecated and will be removed > nodejs-thin-client use it > therefore, need to replace the deprecated logger -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16651) [nodejs-thin-client] replace logger with ignite-log4j2
Sergei Ryzhov created IGNITE-16651: -- Summary: [nodejs-thin-client] replace logger with ignite-log4j2 Key: IGNITE-16651 URL: https://issues.apache.org/jira/browse/IGNITE-16651 Project: Ignite Issue Type: Improvement Reporter: Sergei Ryzhov Assignee: Sergei Ryzhov module ignite-log4j deprecated and will be removed nodejs-thin-client use it therefore, need to replace the deprecated logger -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16650) Exclude ignite-log4j, log4j 1.2.17
Sergei Ryzhov created IGNITE-16650: -- Summary: Exclude ignite-log4j, log4j 1.2.17 Key: IGNITE-16650 URL: https://issues.apache.org/jira/browse/IGNITE-16650 Project: Ignite Issue Type: Bug Reporter: Sergei Ryzhov Assignee: Sergei Ryzhov log4j 1.2.17 is not supported and contains critical vulnerabilities https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces I suggest excluding the ignite-log4j module from ignite Direct vulnerabilities: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16440) Split suites to achieve 1 hour per suite run
[ https://issues.apache.org/jira/browse/IGNITE-16440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-16440: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Split suites to achieve 1 hour per suite run > > > Key: IGNITE-16440 > URL: https://issues.apache.org/jira/browse/IGNITE-16440 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > As of now the following suites taking more than 1 hour: > *Queries 1,* > *Queries 1 (lazy=true),* > *Queries 2,* > *Queries 2 (lazy=true),* > *Intercepter Cache (Full API Config Variations / Basic),* > *PDS (Indexing),* > *PDS,* > *SPI,* > *Cache 1,* > *Cache (Full API Multi JVM)* > *Cache 9,* > *Cache 7,* > *Cache 5* > Let's dividing each of them in half. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16631) ODBC: Add ability to set default query, calcite or H2, engine on DSN configuration or connection string
[ https://issues.apache.org/jira/browse/IGNITE-16631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500832#comment-17500832 ] Ivan Daschinsky commented on IGNITE-16631: -- [~alex_pl] [~amashenkov] [~korlov] [~isapego] Could you please review it? > ODBC: Add ability to set default query, calcite or H2, engine on DSN > configuration or connection string > --- > > Key: IGNITE-16631 > URL: https://issues.apache.org/jira/browse/IGNITE-16631 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Labels: calcite, calcite2-required > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16649) .NET: Doesn't sent updated schema when changed fields of IBinarilizable
[
https://issues.apache.org/jira/browse/IGNITE-16649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-16649:
-
Description:
When putting IBinarilizable instance with different field set, schema is not
sent to cluster, leading to failure if another node tries to get value from
cache.
{code}
Apache.Ignite.Core.Binary.BinaryObjectException : Cannot find schema for object
with compact footer [typeId=-1422440667, schemaId=-935090685]
at
Apache.Ignite.Core.Impl.Binary.BinaryObjectSchemaSerializer.GetFieldIds(BinaryObjectHeader
hdr, IIgniteInternal ignite) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/BinaryObjectSchemaSerializer.cs:line
307
at
Apache.Ignite.Core.Impl.Binary.BinaryObjectSchemaSerializer.GetFieldIds(BinaryObjectHeader
hdr, IIgniteInternal ignite, IBinaryStream stream, Int32 objectPos) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/BinaryObjectSchemaSerializer.cs:line
262
at
Apache.Ignite.Core.Impl.Binary.BinaryReader.SetCurSchema(IBinaryTypeDescriptor
desc) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/BinaryReader.cs:line
803
at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos,
Type typeOverride) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/BinaryReader.cs:line
751
at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res,
Type typeOverride) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/BinaryReader.cs:line
577
at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type
typeOverride) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/BinaryReader.cs:line
536
at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadBinaryObject[T](Boolean
doDetach) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/BinaryReader.cs:line
635
at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res,
Type typeOverride) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/BinaryReader.cs:line
582
at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type
typeOverride) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/BinaryReader.cs:line
536
at Apache.Ignite.Core.Impl.Binary.Marshaller.Unmarshal[T](IBinaryStream
stream, BinaryMode mode, BinaryObjectBuilder builder) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/Marshaller.cs:line
295
at Apache.Ignite.Core.Impl.Binary.Marshaller.Unmarshal[T](IBinaryStream
stream, Boolean keepBinary) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/Marshaller.cs:line
268
at Apache.Ignite.Core.Impl.Cache.CacheImpl`2.Unmarshal[T](IBinaryStream
stream) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Cache/CacheImpl.cs:line
1750
at
Apache.Ignite.Core.Impl.Cache.CacheImpl`2.<>c__DisplayClass146_0.b__1(IBinaryStream
stream, Int64 res) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Cache/CacheImpl.cs:line
1907
at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutLong[TR](Int32 type,
Func`2 outAction, Func`3 inAction, Func`2 readErrorAction) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/PlatformJniTarget.cs:line
214
at Apache.Ignite.Core.Impl.PlatformTargetAdapter.DoOutInOpX[TR](Int32 type,
Action`1 outAction, Func`3 inAction, Func`2 inErrorAction) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/PlatformTargetAdapter.cs:line
236
at Apache.Ignite.Core.Impl.Cache.CacheImpl`2.DoOutInOpNullable(CacheOp
cacheOp, TK x) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Cache/CacheImpl.cs:line
1905
at Apache.Ignite.Core.Impl.Cache.CacheImpl`2.TryGet(TK key, TV& value) in
/home/ivandasch/Job/ignite-pmdk/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Cache/CacheImpl.cs:line
592
{code}
> .NET: Doesn't sent updated schema when changed fields of IBinarilizable
> ---
>
> Key: IGNITE-16649
> URL: https://issues.apache.org/jira/browse/IGNITE-16649
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Attachments: BinaryChangeSchemaTest.cs
>
>
> When putting IBinarilizable instance with different field set, schema is not
> sent to cluster, leading to
[jira] [Commented] (IGNITE-15131) Provide any method to receive node configs from public Java API
[ https://issues.apache.org/jira/browse/IGNITE-15131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500822#comment-17500822 ] Aleksandr Polovtcev commented on IGNITE-15131: -- I've added some related methods in [https://github.com/apache/ignite-3/pull/659,] but I think it would be better to group these properties together in a class, e.g. `LocalNode`. > Provide any method to receive node configs from public Java API > --- > > Key: IGNITE-15131 > URL: https://issues.apache.org/jira/browse/IGNITE-15131 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > We need to implement a way to receive configs of started ignite node from the > Java API. > It can be used for getting any auto-discovered ports and etc. in integration > tests and client code. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16649) .NET: Doesn't sent updated schema when changed fields of IBinarilizable
Ivan Daschinsky created IGNITE-16649: Summary: .NET: Doesn't sent updated schema when changed fields of IBinarilizable Key: IGNITE-16649 URL: https://issues.apache.org/jira/browse/IGNITE-16649 Project: Ignite Issue Type: Bug Components: platforms Reporter: Ivan Daschinsky Assignee: Ivan Daschinsky Attachments: BinaryChangeSchemaTest.cs -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16649) .NET: Doesn't sent updated schema when changed fields of IBinarilizable
[ https://issues.apache.org/jira/browse/IGNITE-16649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-16649: - Attachment: BinaryChangeSchemaTest.cs > .NET: Doesn't sent updated schema when changed fields of IBinarilizable > --- > > Key: IGNITE-16649 > URL: https://issues.apache.org/jira/browse/IGNITE-16649 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Attachments: BinaryChangeSchemaTest.cs > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16072) Add configurable throttling for the spanshot process
[ https://issues.apache.org/jira/browse/IGNITE-16072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500785#comment-17500785 ] Aleksey Plekhanov commented on IGNITE-16072: [~xtern], LGTM > Add configurable throttling for the spanshot process > > > Key: IGNITE-16072 > URL: https://issues.apache.org/jira/browse/IGNITE-16072 > Project: Ignite > Issue Type: Improvement >Reporter: Maxim Muzafarov >Assignee: Pavel Pereslegin >Priority: Major > Labels: iep-43, ise > Fix For: 2.13 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > We want to add configurable throttling to the number of threads that perform > a snapshot operation. The IGNITE-16014 have introduced the pool size > configuration property, however, it is still possible that a node can become > overloaded and unresponsive due to its attempts to copy data files on very > slow HDDs. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16648) Add histogram metrics for thread pools tasks
[ https://issues.apache.org/jira/browse/IGNITE-16648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-16648: --- Labels: ise (was: ) > Add histogram metrics for thread pools tasks > > > Key: IGNITE-16648 > URL: https://issues.apache.org/jira/browse/IGNITE-16648 > Project: Ignite > Issue Type: Improvement >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > > Right now, we don't have a way to estimate the speed of task execution for a > thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1] are not > enough > > Suggestions: add histogram[2] metrics for thread pools tasks. Similar to > PutTime/GetTime/etc... for caches > > [1] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] > [2] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16648) Add histogram metrics for thread pools tasks
[ https://issues.apache.org/jira/browse/IGNITE-16648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-16648: --- Description: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1] are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] was: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1]are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > Add histogram metrics for thread pools tasks > > > Key: IGNITE-16648 > URL: https://issues.apache.org/jira/browse/IGNITE-16648 > Project: Ignite > Issue Type: Improvement >Reporter: Stepanov Ilya >Priority: Minor > > Right now, we don't have a way to estimate the speed of task execution for a > thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1] are not > enough > > Suggestions: add histogram[2] metrics for thread pools tasks. Similar to > PutTime/GetTime/etc... for caches > > [1] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] > [2] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16648) Add histogram metrics for thread pools tasks
[ https://issues.apache.org/jira/browse/IGNITE-16648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-16648: --- Description: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1]are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] was: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1] are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > Add histogram metrics for thread pools tasks > > > Key: IGNITE-16648 > URL: https://issues.apache.org/jira/browse/IGNITE-16648 > Project: Ignite > Issue Type: Improvement >Reporter: Stepanov Ilya >Priority: Minor > > Right now, we don't have a way to estimate the speed of task execution for a > thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1]are not > enough > > Suggestions: add histogram[2] metrics for thread pools tasks. Similar to > PutTime/GetTime/etc... for caches > > [1] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] > [2] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16648) Add histogram metrics for thread pools tasks
[ https://issues.apache.org/jira/browse/IGNITE-16648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-16648: --- Description: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1] are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] was: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount" [1] are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > Add histogram metrics for thread pools tasks > > > Key: IGNITE-16648 > URL: https://issues.apache.org/jira/browse/IGNITE-16648 > Project: Ignite > Issue Type: Improvement >Reporter: Stepanov Ilya >Priority: Minor > > Right now, we don't have a way to estimate the speed of task execution for a > thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1] are > not enough > > Suggestions: add histogram[2] metrics for thread pools tasks. Similar to > PutTime/GetTime/etc... for caches > > [1] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] > [2] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16648) Add histogram metrics for thread pools tasks
[ https://issues.apache.org/jira/browse/IGNITE-16648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-16648: --- Description: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount" [1] are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] was: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount" are not enough [1] Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms|https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > Add histogram metrics for thread pools tasks > > > Key: IGNITE-16648 > URL: https://issues.apache.org/jira/browse/IGNITE-16648 > Project: Ignite > Issue Type: Improvement >Reporter: Stepanov Ilya >Priority: Minor > > Right now, we don't have a way to estimate the speed of task execution for a > thread pools. Metrics such as "QueueSize" and "CompletedTaskCount" [1] are > not enough > > Suggestions: add histogram[2] metrics for thread pools tasks. Similar to > PutTime/GetTime/etc... for caches > > [1] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] > [2] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16648) Add histogram metrics for thread pools tasks
Stepanov Ilya created IGNITE-16648: -- Summary: Add histogram metrics for thread pools tasks Key: IGNITE-16648 URL: https://issues.apache.org/jira/browse/IGNITE-16648 Project: Ignite Issue Type: Improvement Reporter: Stepanov Ilya Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount" are not enough [1] Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms|https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16530) Java thin: implement heartbeats
[ https://issues.apache.org/jira/browse/IGNITE-16530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500778#comment-17500778 ] Igor Sapego commented on IGNITE-16530: -- [~ptupitsyn] reviewed. See my comments inline, please. > Java thin: implement heartbeats > --- > > Key: IGNITE-16530 > URL: https://issues.apache.org/jira/browse/IGNITE-16530 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: iep-83 > Fix For: 2.13 > > Time Spent: 10m > Remaining Estimate: 0h > > Implement heartbeats as described in [IEP-83 Thin Client > Keepalive|https://cwiki.apache.org/confluence/display/IGNITE/IEP-83+Thin+Client+Keepalive]. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16645) Sql. SetOp execution node cannot be rewinded.
[ https://issues.apache.org/jira/browse/IGNITE-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-16645: Description: [SetOp execution node cannot be rewinded|https://issues.apache.org/jira/browse/IGNITE-16228] [Unexpected result of COUNT with multiple parameters|https://issues.apache.org/jira/browse/IGNITE-16191] [Memory leak in RelOptCluster during mapping|https://issues.apache.org/jira/browse/IGNITE-16354] was: [SetOp execution node cannot be rewinded|https://issues.apache.org/jira/browse/IGNITE-16228] [Unexpected result of COUNT with multiple parameters|https://issues.apache.org/jira/browse/IGNITE-16191] > Sql. SetOp execution node cannot be rewinded. > - > > Key: IGNITE-16645 > URL: https://issues.apache.org/jira/browse/IGNITE-16645 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Evgeny Stanilovsky >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > [SetOp execution node cannot be > rewinded|https://issues.apache.org/jira/browse/IGNITE-16228] > [Unexpected result of COUNT with multiple > parameters|https://issues.apache.org/jira/browse/IGNITE-16191] > [Memory leak in RelOptCluster during > mapping|https://issues.apache.org/jira/browse/IGNITE-16354] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-16541) 'Invalid cross-device link error' if cdcWalPath and walArchivePath point to different file system partitions
[
https://issues.apache.org/jira/browse/IGNITE-16541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita reassigned IGNITE-16541:
Assignee: Amelchev Nikita
> 'Invalid cross-device link error' if cdcWalPath and walArchivePath point to
> different file system partitions
>
>
> Key: IGNITE-16541
> URL: https://issues.apache.org/jira/browse/IGNITE-16541
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ilya Shishkov
>Assignee: Amelchev Nikita
>Priority: Minor
> Labels: IEP-59, ise
>
> Currently, if CDC is turned on and {{cdcWalPath}} and {{walArchivePath}}
> point to different file system partitions, server node fails on a first
> attempt to archive segment, but not during a startup.
> Because cluster may be under load, in order to prevent data loss or
> corruption we should fail before cluster activation. Server node should
> check {{cdcWalPath}} and {{walArchivePath}} during the startup, and prevent
> further starting if they point to different file system partitions.
> {code}
> [ERROR]wal-file-archiver%null-#108[] Critical system error detected. Will be
> handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler
> [tryStop=false, timeout=0, super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class
> o.a.i.i.processors.cache.persistence.StorageException: Failed to archive WAL
> segment [srcFile=/ignite/work/db/wal/consistent_Id/.wal,
> dstFile=/ignite/work/db/wal/archive/consistent_Id/.wal.tmp]]]
> org.apache.ignite.internal.processors.cache.persistence.StorageException:
> Failed to archive WAL segment
> [srcFile=/ignite/work/db/wal/consistent_Id/.wal,
> dstFile=/ignite/work/db/wal/archive/consistent_Id/.wal.tmp]
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.archiveSegment(FileWriteAheadLogManager.java:2074)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.body(FileWriteAheadLogManager.java:1934)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
> at java.lang.Thread.run(Thread.java:829) [?:?]
> Caused by: java.nio.file.FileSystemException:
> /ignite/data/work/db/wal/cdc/consistent_Id/.wal ->
> /ignite/work/db/wal/archive/consistent_Id/.wal: Invalid
> cross-device link
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:100)
> at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> sun.nio.fs.UnixFileSystemProvider.createLink(UnixFileSystemProvider.java:481)
> at java.nio.file.Files.createLink(Files.java:1102)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.archiveSegment(FileWriteAheadLogManager.java:2058)
> ... 3 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IGNITE-15000) putAllConflict removeAllConfict support in thin client
[
https://issues.apache.org/jira/browse/IGNITE-15000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov reassigned IGNITE-15000:
---
Assignee: Mikhail Petrov (was: Amelchev Nikita)
> putAllConflict removeAllConfict support in thin client
> --
>
> Key: IGNITE-15000
> URL: https://issues.apache.org/jira/browse/IGNITE-15000
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Mikhail Petrov
>Priority: Major
> Labels: IEP-59
>
> {{IgniteInternalCache}} contains methods {{putAllConfict}},
> {{removeAllConfict}} that can be used to perform put, remove operations with
> entry {{GridCacheVersion}}.
> To implement multi-cluster replication using thin clients we need to add
> these methods to the thin client protocol.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16622) Add support for JDK 17
[ https://issues.apache.org/jira/browse/IGNITE-16622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-16622: --- Reviewer: Roman Puchkovskiy > Add support for JDK 17 > -- > > Key: IGNITE-16622 > URL: https://issues.apache.org/jira/browse/IGNITE-16622 > Project: Ignite > Issue Type: Improvement >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > According to > [https://www.oracle.com/java/technologies/java-se-support-roadmap.html] Java > 17 is the current LTS version. We need to investigate and add support for > Java 17 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16622) Add support for JDK 17
[ https://issues.apache.org/jira/browse/IGNITE-16622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500743#comment-17500743 ] Roman Puchkovskiy commented on IGNITE-16622: The patch looks good to me. Thanks for the contribution! > Add support for JDK 17 > -- > > Key: IGNITE-16622 > URL: https://issues.apache.org/jira/browse/IGNITE-16622 > Project: Ignite > Issue Type: Improvement >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > According to > [https://www.oracle.com/java/technologies/java-se-support-roadmap.html] Java > 17 is the current LTS version. We need to investigate and add support for > Java 17 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16626) Mark the ignite-log4j as deprecated.
[ https://issues.apache.org/jira/browse/IGNITE-16626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-16626: --- Labels: ise (was: ) > Mark the ignite-log4j as deprecated. > > > Key: IGNITE-16626 > URL: https://issues.apache.org/jira/browse/IGNITE-16626 > Project: Ignite > Issue Type: Improvement >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Minor > Labels: ise > Time Spent: 20m > Remaining Estimate: 0h > > Mark the ignite-log4j as deprecated. > will be removed later. > log4j 1.2.17 is not supported and contains critical vulnerabilities > Direct vulnerabilities: > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16626) Mark the ignite-log4j as deprecated.
[ https://issues.apache.org/jira/browse/IGNITE-16626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-16626: --- Fix Version/s: 2.13 > Mark the ignite-log4j as deprecated. > > > Key: IGNITE-16626 > URL: https://issues.apache.org/jira/browse/IGNITE-16626 > Project: Ignite > Issue Type: Improvement >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Minor > Labels: ise > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > Mark the ignite-log4j as deprecated. > will be removed later. > log4j 1.2.17 is not supported and contains critical vulnerabilities > Direct vulnerabilities: > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16626) Mark the ignite-log4j as deprecated.
[ https://issues.apache.org/jira/browse/IGNITE-16626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-16626: --- Issue Type: Improvement (was: Bug) > Mark the ignite-log4j as deprecated. > > > Key: IGNITE-16626 > URL: https://issues.apache.org/jira/browse/IGNITE-16626 > Project: Ignite > Issue Type: Improvement >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Mark the ignite-log4j as deprecated. > will be removed later. > log4j 1.2.17 is not supported and contains critical vulnerabilities > Direct vulnerabilities: > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16626) Mark the ignite-log4j as deprecated.
[ https://issues.apache.org/jira/browse/IGNITE-16626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-16626: --- Priority: Minor (was: Major) > Mark the ignite-log4j as deprecated. > > > Key: IGNITE-16626 > URL: https://issues.apache.org/jira/browse/IGNITE-16626 > Project: Ignite > Issue Type: Improvement >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Mark the ignite-log4j as deprecated. > will be removed later. > log4j 1.2.17 is not supported and contains critical vulnerabilities > Direct vulnerabilities: > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16622) Add support for JDK 17
[
https://issues.apache.org/jira/browse/IGNITE-16622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500731#comment-17500731
]
Ignite TC Bot commented on IGNITE-16622:
{panel:title=Branch: [pull/9849/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9849/head] Base: [master] : New Tests
(30)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 2{color} [[tests
30|https://ci.ignite.apache.org/viewLog.html?buildId=6431979]]
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReReadWhenStateWasNotStored[specificConsistentId=false,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1977493952@59cda16e,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadBeforeGracefulShutdown[specificConsistentId=false,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1977493952@59cda16e,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadAllKeys[specificConsistentId=false,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1977493952@59cda16e,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testCdcSingleton[specificConsistentId=true,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1977493952@59cda16e,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadBeforeGracefulShutdown[specificConsistentId=true,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1977493952@59cda16e,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadAllKeys[specificConsistentId=true,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1977493952@59cda16e,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testCdcSingleton[specificConsistentId=false,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1977493952@59cda16e,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testMultiNodeConsumption[specificConsistentId=false,walMode=BACKGROUND,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1977493952@59cda16e,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadAllKeys[specificConsistentId=false,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1977493952@59cda16e,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testCdcSingleton[specificConsistentId=true,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1977493952@59cda16e,pageSz=8,192]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testMultiNodeConsumption[specificConsistentId=true,walMode=LOG_ONLY,metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1977493952@59cda16e,pageSz=8,192]
- PASSED{color}
... and 19 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6431678buildTypeId=IgniteTests24Java8_RunAll]
> Add support for JDK 17
> --
>
> Key: IGNITE-16622
> URL: https://issues.apache.org/jira/browse/IGNITE-16622
> Project: Ignite
> Issue Type: Improvement
>Reporter: Semyon Danilov
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> According to
> [https://www.oracle.com/java/technologies/java-se-support-roadmap.html] Java
> 17 is the current LTS version. We need to investigate and add support for
> Java 17
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16501) TX Recovery protocol in Cockroach
[ https://issues.apache.org/jira/browse/IGNITE-16501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-16501: --- Description: The flowchart [^Cockroach transaction status recovery.pdf] describe transaction recovery if txn coordinator was failed. The following questions remained: Where are intents stored before they are replicated? If in the main storage, then how do they get there if they have not yet been replicated? How is it checked that the intent is replicated? Need to investigate other failures: a txn record leaseholder fail, a write intent leaseholder fail and etc. was: The flowchart [^Cockroach transaction status recovery.pdf] describe transaction recovery if txn coordinator was failed. Need to investigate other failures: txn record leaseholder fail, write intent leaseholder fail and etc. > TX Recovery protocol in Cockroach > - > > Key: IGNITE-16501 > URL: https://issues.apache.org/jira/browse/IGNITE-16501 > Project: Ignite > Issue Type: Task >Reporter: Vyacheslav Koptilin >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Attachments: Cockroach transaction status recovery.pdf > > > The flowchart [^Cockroach transaction status recovery.pdf] describe > transaction recovery if txn coordinator was failed. > The following questions remained: > Where are intents stored before they are replicated? If in the main storage, > then how do they get there if they have not yet been replicated? > How is it checked that the intent is replicated? > Need to investigate other failures: a txn record leaseholder fail, a write > intent leaseholder fail and etc. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16501) TX Recovery protocol in Cockroach
[ https://issues.apache.org/jira/browse/IGNITE-16501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-16501: --- Description: The flowchart [^Cockroach transaction status recovery.pdf] describe transaction recovery if txn coordinator was failed. Need to investigate other failures: txn record leaseholder fail, write intent leaseholder fail and etc. > TX Recovery protocol in Cockroach > - > > Key: IGNITE-16501 > URL: https://issues.apache.org/jira/browse/IGNITE-16501 > Project: Ignite > Issue Type: Task >Reporter: Vyacheslav Koptilin >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Attachments: Cockroach transaction status recovery.pdf > > > The flowchart [^Cockroach transaction status recovery.pdf] describe > transaction recovery if txn coordinator was failed. > Need to investigate other failures: txn record leaseholder fail, write intent > leaseholder fail and etc. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16647) in-memory storage configuration
Sergey Chugunov created IGNITE-16647: Summary: in-memory storage configuration Key: IGNITE-16647 URL: https://issues.apache.org/jira/browse/IGNITE-16647 Project: Ignite Issue Type: Improvement Reporter: Sergey Chugunov We need to define how in-memory storage should be configured in Ignite 3. Whether it is something similar to DataRegions in Ignite 2.x or something new, corresponding configuration classes should be developed and integrated with in-memory storage. Particular type of underlying storage (MV-storage, snaptree storage) may be taken into account. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16306) snaptree-based in-memory storage
[ https://issues.apache.org/jira/browse/IGNITE-16306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-16306: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > snaptree-based in-memory storage > > > Key: IGNITE-16306 > URL: https://issues.apache.org/jira/browse/IGNITE-16306 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha3 >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: iep-74, ignite-3 > > Until a full-fledged MV store is implemented we can implement in-memory > storage on a snaptree library [1] that represents a concurrent AVL tree with > support of snapshots. > In this ticket we need to integrate the library with our existing storage > APIs (refine API if necessary), integrate its snapshot API with Raft > snapshots and provide configuration if necessary. > [1] https://github.com/nbronson/snaptree -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16306) snaptree-based in-memory storage
[ https://issues.apache.org/jira/browse/IGNITE-16306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-16306: - Description: Until a full-fledged MV store is implemented we can implement in-memory storage on a snaptree library [1] that represents a concurrent AVL tree with support of snapshots. In this ticket we need to integrate the library with our existing storage APIs (refine API if necessary), integrate its snapshot API with Raft snapshots and provide configuration if necessary. [1] https://github.com/nbronson/snaptree was: Until a full-fledged MV store is implemented we can implement in-memory storage on a snaptree library [1] that represents a concurrent AVL tree with support of snapshots. [1] https://github.com/nbronson/snaptree > snaptree-based in-memory storage > > > Key: IGNITE-16306 > URL: https://issues.apache.org/jira/browse/IGNITE-16306 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha3 >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: iep-74, ignite-3 > > Until a full-fledged MV store is implemented we can implement in-memory > storage on a snaptree library [1] that represents a concurrent AVL tree with > support of snapshots. > In this ticket we need to integrate the library with our existing storage > APIs (refine API if necessary), integrate its snapshot API with Raft > snapshots and provide configuration if necessary. > [1] https://github.com/nbronson/snaptree -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16306) snaptree-based in-memory storage
[ https://issues.apache.org/jira/browse/IGNITE-16306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-16306: - Epic Link: IGNITE-16646 > snaptree-based in-memory storage > > > Key: IGNITE-16306 > URL: https://issues.apache.org/jira/browse/IGNITE-16306 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha3 >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: iep-74, ignite-3 > > Until a full-fledged MV store is implemented we can implement in-memory > storage on a snaptree library [1] that represents a concurrent AVL tree with > support of snapshots. > [1] https://github.com/nbronson/snaptree -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16306) snaptree-based in-memory storage
[ https://issues.apache.org/jira/browse/IGNITE-16306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-16306: - Description: Until a full-fledged MV store is implemented we can implement in-memory storage on a snaptree library [1] that represents a concurrent AVL tree with support of snapshots. [1] https://github.com/nbronson/snaptree was: h3. Goals We need an in-memory store, similar to Ignite-2. This store must reuse common replication infrastructure, in other words, be integrated into raft STM and support transactions. The raft protocol implies some persistent state: metadata, logs, snapshot. Simplest solution - write a raft persistent state on disk (this is already implemented for org.apache.ignite.internal.storage.basic.ConcurrentHashMapPartitionStorage). Drawback - not fully in-memory solution, doesn't much differ from a database cache We can go the pure in-memory way - keep all raft state in a volatile store. h3. Raft metadata Must not be persisted for a pure in-memory cluster, because the state is always lost on restart. Note: a node must always be removed from the raft group when it’s removed from baseline by auto adjust and should join as new (in-memory always works with auto-adjust similarly to Ignite 2). *Out of scope.* h3. Log store Has working in-memory implementation (currently used in tests): org.apache.ignite.raft.jraft.storage.impl.LocalLogStorage Note: generally speaking, log is only required for "historical rebalancing" after the snapshot rebalance. It won't be needed at all once it is possible to apply snapshot and concurrent updates at the same time, for example when a solution like mvcc is implemented. h3. Snapshots Can be implemented over any kv store extended with some kind of Copy-On-Write support. Not implemented currently. More details below. h3. COW buffer To create an in-memory snapshot, the snapshot data is written to a separate in-memory buffer. The buffer is populated from the state machine update thread either by the update operations or by a snapshot advance mini-task which is submitted to the state machine update thread as needed. To maintain a snapshot, the state machine needs to keep an snapshot iterator boundary key. If a key being updated is smaller or equal than the boundary key, there is no need in any additional action because the snapshot iterator has already processed this key. If a key being updated is larger than the boundary key, the old version of the key is eagerly put to the snapshot buffer and the key is marked with snapshot ID (so that the key is skipped during further iteration). Snapshot advance mini-task iterates over a next batch of the keys starting from the boundary key and puts to the snapshot buffer only keys that are not yet marked by the snapshot ID. This approach has similar memory requirements to the first alternative, but does not require to modify the storage tree so that it can store multiple versions of the same key. This approach, however, allows for transparent snapshot buffer offloading to disk which can reduce memory requirements. It is also simpler in implementation because the code is essentially single-threaded and only requires synchronization for the in-memory buffer. The downside is that snapshot advance tasks will increase tail latency of state machine update operations. Can be implemented on top of any kv store. Note: we should consider the possibility of streaming the snapshot instead of storing it in memory until it is completed. > snaptree-based in-memory storage > > > Key: IGNITE-16306 > URL: https://issues.apache.org/jira/browse/IGNITE-16306 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha3 >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: iep-74, ignite-3 > > Until a full-fledged MV store is implemented we can implement in-memory > storage on a snaptree library [1] that represents a concurrent AVL tree with > support of snapshots. > [1] https://github.com/nbronson/snaptree -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16306) snaptree-based in-memory storage
[ https://issues.apache.org/jira/browse/IGNITE-16306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-16306: - Summary: snaptree-based in-memory storage (was: [POC] In-Memory storage integration) > snaptree-based in-memory storage > > > Key: IGNITE-16306 > URL: https://issues.apache.org/jira/browse/IGNITE-16306 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha3 >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: iep-74, ignite-3 > > h3. Goals > We need an in-memory store, similar to Ignite-2. This store must reuse common > replication infrastructure, in other words, be integrated into raft STM and > support transactions. > The raft protocol implies some persistent state: metadata, logs, snapshot. > Simplest solution - write a raft persistent state on disk (this is already > implemented for > org.apache.ignite.internal.storage.basic.ConcurrentHashMapPartitionStorage). > Drawback - not fully in-memory solution, doesn't much differ from a database > cache > We can go the pure in-memory way - keep all raft state in a volatile store. > h3. Raft metadata > Must not be persisted for a pure in-memory cluster, because the state is > always lost on restart. > Note: a node must always be removed from the raft group when it’s removed > from baseline by auto adjust and should join as new (in-memory always works > with auto-adjust similarly to Ignite 2). *Out of scope.* > h3. Log store > Has working in-memory implementation (currently used in tests): > org.apache.ignite.raft.jraft.storage.impl.LocalLogStorage > Note: generally speaking, log is only required for "historical rebalancing" > after the snapshot rebalance. It won't be needed at all once it is possible > to apply snapshot and concurrent updates at the same time, for example when a > solution like mvcc is implemented. > h3. Snapshots > Can be implemented over any kv store extended with some kind of Copy-On-Write > support. Not implemented currently. More details below. > h3. COW buffer > To create an in-memory snapshot, the snapshot data is written to a separate > in-memory buffer. The buffer is populated from the state machine update > thread either by the update operations or by a snapshot advance mini-task > which is submitted to the state machine update thread as needed. > To maintain a snapshot, the state machine needs to keep an snapshot iterator > boundary key. If a key being updated is smaller or equal than the boundary > key, there is no need in any additional action because the snapshot iterator > has already processed this key. If a key being updated is larger than the > boundary key, the old version of the key is eagerly put to the snapshot > buffer and the key is marked with snapshot ID (so that the key is skipped > during further iteration). Snapshot advance mini-task iterates over a next > batch of the keys starting from the boundary key and puts to the snapshot > buffer only keys that are not yet marked by the snapshot ID. > This approach has similar memory requirements to the first alternative, but > does not require to modify the storage tree so that it can store multiple > versions of the same key. This approach, however, allows for transparent > snapshot buffer offloading to disk which can reduce memory requirements. It > is also simpler in implementation because the code is essentially > single-threaded and only requires synchronization for the in-memory buffer. > The downside is that snapshot advance tasks will increase tail latency of > state machine update operations. > Can be implemented on top of any kv store. > Note: we should consider the possibility of streaming the snapshot instead of > storing it in memory until it is completed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16646) In-memory store
Sergey Chugunov created IGNITE-16646: Summary: In-memory store Key: IGNITE-16646 URL: https://issues.apache.org/jira/browse/IGNITE-16646 Project: Ignite Issue Type: Epic Reporter: Sergey Chugunov h3. Goals We need an in-memory store, similar to Ignite-2. This store must reuse common replication infrastructure, in other words, be integrated into raft STM and support transactions. The raft protocol implies some persistent state: metadata, logs, snapshot. Simplest solution - write a raft persistent state on disk (this is already implemented for org.apache.ignite.internal.storage.basic.ConcurrentHashMapPartitionStorage). Drawback - not fully in-memory solution, doesn't much differ from a database cache We can go the pure in-memory way - keep all raft state in a volatile store. h3. Raft metadata Must not be persisted for a pure in-memory cluster, because the state is always lost on restart. Note: a node must always be removed from the raft group when it’s removed from baseline by auto adjust and should join as new (in-memory always works with auto-adjust similarly to Ignite 2). *Out of scope.* h3. Log store Has working in-memory implementation (currently used in tests): org.apache.ignite.raft.jraft.storage.impl.LocalLogStorage Note: generally speaking, log is only required for "historical rebalancing" after the snapshot rebalance. It won't be needed at all once it is possible to apply snapshot and concurrent updates at the same time, for example when a solution like mvcc is implemented. h3. Snapshots Can be implemented over any kv store extended with some kind of Copy-On-Write support. Not implemented currently. More details below. h3. COW buffer To create an in-memory snapshot, the snapshot data is written to a separate in-memory buffer. The buffer is populated from the state machine update thread either by the update operations or by a snapshot advance mini-task which is submitted to the state machine update thread as needed. To maintain a snapshot, the state machine needs to keep an snapshot iterator boundary key. If a key being updated is smaller or equal than the boundary key, there is no need in any additional action because the snapshot iterator has already processed this key. If a key being updated is larger than the boundary key, the old version of the key is eagerly put to the snapshot buffer and the key is marked with snapshot ID (so that the key is skipped during further iteration). Snapshot advance mini-task iterates over a next batch of the keys starting from the boundary key and puts to the snapshot buffer only keys that are not yet marked by the snapshot ID. This approach has similar memory requirements to the first alternative, but does not require to modify the storage tree so that it can store multiple versions of the same key. This approach, however, allows for transparent snapshot buffer offloading to disk which can reduce memory requirements. It is also simpler in implementation because the code is essentially single-threaded and only requires synchronization for the in-memory buffer. The downside is that snapshot advance tasks will increase tail latency of state machine update operations. Can be implemented on top of any kv store. Note: we should consider the possibility of streaming the snapshot instead of storing it in memory until it is completed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15585) Calcite. Unexpected result with EXIST and subquery.
[
https://issues.apache.org/jira/browse/IGNITE-15585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-15585:
Labels: calcite calcite3-required (was: calcite calcite2-required
calcite3-required ignite-3)
> Calcite. Unexpected result with EXIST and subquery.
> ---
>
> Key: IGNITE-15585
> URL: https://issues.apache.org/jira/browse/IGNITE-15585
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Evgeny Stanilovsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: calcite, calcite3-required
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {noformat}
> statement ok
> CREATE TABLE integers(i INTEGER)
> statement ok
> INSERT INTO integers VALUES (1), (2), (3), (NULL)
> query IT
> SELECT i, EXISTS(SELECT i FROM integers WHERE i=i1.i) FROM integers i1 ORDER
> BY i NULLS FIRST;
>
> NULL false
> 1 true
> 2 true
> 3 true
> {noformat}
> {noformat}
> /subquery/exists/test_correlated_exists.test[_ignore]
> {noformat}
> {noformat}
> statement ok
> CREATE TABLE integers(i INTEGER)
> statement ok
> INSERT INTO integers VALUES (1), (2), (3), (NULL)
> # SUM on exists
> query R
> SELECT SUM(CASE WHEN EXISTS(SELECT i FROM integers WHERE i=i1.i) THEN 1 ELSE
> 0 END) FROM integers i1;
>
> 3.00
> {noformat}
> checked with mysql, all ok there.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15585) Calcite. Unexpected result with EXIST and subquery.
[
https://issues.apache.org/jira/browse/IGNITE-15585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-15585:
Labels: calcite (was: calcite calcite3-required)
> Calcite. Unexpected result with EXIST and subquery.
> ---
>
> Key: IGNITE-15585
> URL: https://issues.apache.org/jira/browse/IGNITE-15585
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Evgeny Stanilovsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: calcite
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {noformat}
> statement ok
> CREATE TABLE integers(i INTEGER)
> statement ok
> INSERT INTO integers VALUES (1), (2), (3), (NULL)
> query IT
> SELECT i, EXISTS(SELECT i FROM integers WHERE i=i1.i) FROM integers i1 ORDER
> BY i NULLS FIRST;
>
> NULL false
> 1 true
> 2 true
> 3 true
> {noformat}
> {noformat}
> /subquery/exists/test_correlated_exists.test[_ignore]
> {noformat}
> {noformat}
> statement ok
> CREATE TABLE integers(i INTEGER)
> statement ok
> INSERT INTO integers VALUES (1), (2), (3), (NULL)
> # SUM on exists
> query R
> SELECT SUM(CASE WHEN EXISTS(SELECT i FROM integers WHERE i=i1.i) THEN 1 ELSE
> 0 END) FROM integers i1;
>
> 3.00
> {noformat}
> checked with mysql, all ok there.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15584) Calcite. Failed to parse query with IN and simple subquery.
[
https://issues.apache.org/jira/browse/IGNITE-15584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-15584:
Labels: calcite calcite3-required (was: calcite calcite2-required
calcite3-required ignite-3)
> Calcite. Failed to parse query with IN and simple subquery.
> ---
>
> Key: IGNITE-15584
> URL: https://issues.apache.org/jira/browse/IGNITE-15584
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Evgeny Stanilovsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: calcite, calcite3-required
>
> {noformat}
> query I
> SELECT 1 AS one WHERE 1 IN (SELECT 1);
>
> 1
> statement ok
> CREATE TABLE tbl(a TINYINT, b SMALLINT, c INTEGER, d BIGINT, e VARCHAR, f
> DATE, g TIMESTAMP)
> statement ok
> INSERT INTO tbl VALUES (1, 2, 3, 4, '5', DATE '1992-01-01', TIMESTAMP
> '1992-01-01 00:00:00')
> query T
> SELECT EXISTS(SELECT t1.c,t1.d WHERE t1.d<100) FROM tbl t1
>
> true
> {noformat}
> {noformat}
> class org.apache.ignite.IgniteException: Error at: (t.test:14). sql: SELECT 1
> AS one WHERE 1 IN (SELECT 1);
> at
> org.apache.ignite.internal.processors.query.calcite.logical.SqlScriptRunner$Query.execute(SqlScriptRunner.java:562)
> at
> org.apache.ignite.internal.processors.query.calcite.logical.SqlScriptRunner.run(SqlScriptRunner.java:115)
> at
> org.apache.ignite.internal.processors.query.calcite.logical.ScriptTestRunner$1.run(ScriptTestRunner.java:219)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
> parse query.
> at
> org.apache.ignite.internal.processors.query.calcite.util.Commons.parse(Commons.java:205)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executeQuery(ExecutionServiceImpl.java:390)
> at
> org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.query(CalciteQueryProcessor.java:276)
> {noformat}
> {noformat}
> /any_all/test_simple_not_in.test[_ignore]
> /subquery/scalar/test_complex_nested_correlated_subquery.test[_ignore]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16645) Sql. SetOp execution node cannot be rewinded.
[ https://issues.apache.org/jira/browse/IGNITE-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-16645: Description: [SetOp execution node cannot be rewinded|https://issues.apache.org/jira/browse/IGNITE-16228] [Unexpected result of COUNT with multiple parameters|https://issues.apache.org/jira/browse/IGNITE-16191] was:[SetOp execution node cannot be rewinded|https://issues.apache.org/jira/browse/IGNITE-16228] > Sql. SetOp execution node cannot be rewinded. > - > > Key: IGNITE-16645 > URL: https://issues.apache.org/jira/browse/IGNITE-16645 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Evgeny Stanilovsky >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > > [SetOp execution node cannot be > rewinded|https://issues.apache.org/jira/browse/IGNITE-16228] > [Unexpected result of COUNT with multiple > parameters|https://issues.apache.org/jira/browse/IGNITE-16191] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16645) Sql. SetOp execution node cannot be rewinded.
[ https://issues.apache.org/jira/browse/IGNITE-16645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-16645: Description: [SetOp execution node cannot be rewinded|https://issues.apache.org/jira/browse/IGNITE-16228] > Sql. SetOp execution node cannot be rewinded. > - > > Key: IGNITE-16645 > URL: https://issues.apache.org/jira/browse/IGNITE-16645 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Evgeny Stanilovsky >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > > [SetOp execution node cannot be > rewinded|https://issues.apache.org/jira/browse/IGNITE-16228] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16440) Split suites to achieve 1 hour per suite run
[ https://issues.apache.org/jira/browse/IGNITE-16440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500685#comment-17500685 ] Taras Ledkov commented on IGNITE-16440: --- [~jooger], OK with me. > Split suites to achieve 1 hour per suite run > > > Key: IGNITE-16440 > URL: https://issues.apache.org/jira/browse/IGNITE-16440 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Fix For: 2.13 > > Time Spent: 10m > Remaining Estimate: 0h > > As of now the following suites taking more than 1 hour: > *Queries 1,* > *Queries 1 (lazy=true),* > *Queries 2,* > *Queries 2 (lazy=true),* > *Intercepter Cache (Full API Config Variations / Basic),* > *PDS (Indexing),* > *PDS,* > *SPI,* > *Cache 1,* > *Cache (Full API Multi JVM)* > *Cache 9,* > *Cache 7,* > *Cache 5* > Let's dividing each of them in half. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16645) Sql. SetOp execution node cannot be rewinded.
Evgeny Stanilovsky created IGNITE-16645: --- Summary: Sql. SetOp execution node cannot be rewinded. Key: IGNITE-16645 URL: https://issues.apache.org/jira/browse/IGNITE-16645 Project: Ignite Issue Type: Improvement Components: sql Reporter: Evgeny Stanilovsky Assignee: Evgeny Stanilovsky -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16633) Adoption of a bunch of calcite related tickets from Ignite-2
[ https://issues.apache.org/jira/browse/IGNITE-16633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500663#comment-17500663 ] Evgeny Stanilovsky commented on IGNITE-16633: - [~korlov], [~tledkov-gridgain] can u review it ? thanks ! > Adoption of a bunch of calcite related tickets from Ignite-2 > > > Key: IGNITE-16633 > URL: https://issues.apache.org/jira/browse/IGNITE-16633 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Evgeny Stanilovsky >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > [TIMESTAMPDIFF for MICROSECOND unit doesn't > work|https://issues.apache.org/jira/browse/IGNITE-15109] > [Introduce suppot INTERVAL > type|https://issues.apache.org/jira/browse/IGNITE-14975] > [java.lang.Integer cannot be cast to java.lang.Long with JOIN and > EXISTS|https://issues.apache.org/jira/browse/IGNITE-15596] > [RelJsonReader can't deserialize > enums|https://issues.apache.org/jira/browse/IGNITE-16129] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (IGNITE-16628) Regression: Failed to parse query. Column "_0__Z0.C3" not found
[
https://issues.apache.org/jira/browse/IGNITE-16628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich resolved IGNITE-16628.
Resolution: Duplicate
> Regression: Failed to parse query. Column "_0__Z0.C3" not found
> ---
>
> Key: IGNITE-16628
> URL: https://issues.apache.org/jira/browse/IGNITE-16628
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10, 2.11, 2.12
>Reporter: YuJue Li
>Priority: Critical
> Fix For: 2.13
>
>
> create table t_test
> (
> c1 char(1),
> c2 char(2),
> constraint pk_test primary key (c1)
> );
> insert into t_test values('1','1');
> select * from (
> SELECT c1 as c3 FROM t_test
> );
> This issue did not exist in versions before 2.10.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16633) Adoption of a bunch of calcite related tickets from Ignite-2
[ https://issues.apache.org/jira/browse/IGNITE-16633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-16633: Description: [TIMESTAMPDIFF for MICROSECOND unit doesn't work|https://issues.apache.org/jira/browse/IGNITE-15109] [Introduce suppot INTERVAL type|https://issues.apache.org/jira/browse/IGNITE-14975] [java.lang.Integer cannot be cast to java.lang.Long with JOIN and EXISTS|https://issues.apache.org/jira/browse/IGNITE-15596] [RelJsonReader can't deserialize enums|https://issues.apache.org/jira/browse/IGNITE-16129] was: [TIMESTAMPDIFF for MICROSECOND unit doesn't work|https://issues.apache.org/jira/browse/IGNITE-15109] [Introduce suppot INTERVAL type|https://issues.apache.org/jira/browse/IGNITE-14975] [java.lang.Integer cannot be cast to java.lang.Long with JOIN and EXISTS|https://issues.apache.org/jira/browse/IGNITE-15596] > Adoption of a bunch of calcite related tickets from Ignite-2 > > > Key: IGNITE-16633 > URL: https://issues.apache.org/jira/browse/IGNITE-16633 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Evgeny Stanilovsky >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > [TIMESTAMPDIFF for MICROSECOND unit doesn't > work|https://issues.apache.org/jira/browse/IGNITE-15109] > [Introduce suppot INTERVAL > type|https://issues.apache.org/jira/browse/IGNITE-14975] > [java.lang.Integer cannot be cast to java.lang.Long with JOIN and > EXISTS|https://issues.apache.org/jira/browse/IGNITE-15596] > [RelJsonReader can't deserialize > enums|https://issues.apache.org/jira/browse/IGNITE-16129] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (IGNITE-12586) Calcite integration. NodesMapping simplification.
[
https://issues.apache.org/jira/browse/IGNITE-12586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich resolved IGNITE-12586.
Assignee: (was: Andrey Mashenkov)
Resolution: Duplicate
> Calcite integration. NodesMapping simplification.
> -
>
> Key: IGNITE-12586
> URL: https://issues.apache.org/jira/browse/IGNITE-12586
> Project: Ignite
> Issue Type: Improvement
>Reporter: Igor Seliverstov
>Priority: Minor
> Labels: calcite2-required, calcite3-required
>
> Seems turning {{List assignments}} to {{Map
> assignments}} may significantly reduce occupied memory.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-12586) Calcite integration. NodesMapping simplification.
[
https://issues.apache.org/jira/browse/IGNITE-12586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-12586:
---
Labels: (was: calcite2-required calcite3-required)
> Calcite integration. NodesMapping simplification.
> -
>
> Key: IGNITE-12586
> URL: https://issues.apache.org/jira/browse/IGNITE-12586
> Project: Ignite
> Issue Type: Improvement
>Reporter: Igor Seliverstov
>Priority: Minor
>
> Seems turning {{List assignments}} to {{Map
> assignments}} may significantly reduce occupied memory.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16642) [Native Persistence 3.0] Support indexes for B+Tree-based storage
[ https://issues.apache.org/jira/browse/IGNITE-16642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-16642: - Fix Version/s: (was: 3.0.0-alpha5) > [Native Persistence 3.0] Support indexes for B+Tree-based storage > - > > Key: IGNITE-16642 > URL: https://issues.apache.org/jira/browse/IGNITE-16642 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > > Need to support indexes for B+Tree-based storage. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16644) [Native Persistence 3.0] Support snapshots B+Tree-based storage
Kirill Tkalenko created IGNITE-16644: Summary: [Native Persistence 3.0] Support snapshots B+Tree-based storage Key: IGNITE-16644 URL: https://issues.apache.org/jira/browse/IGNITE-16644 Project: Ignite Issue Type: Task Reporter: Kirill Tkalenko Need to support snapshots for B+Tree-based storage. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16643) Attempt to reduce the execution time of current integration tests
Kirill Tkalenko created IGNITE-16643: Summary: Attempt to reduce the execution time of current integration tests Key: IGNITE-16643 URL: https://issues.apache.org/jira/browse/IGNITE-16643 Project: Ignite Issue Type: Task Reporter: Kirill Tkalenko At the moment, some integration tests work for a long time, we need to find ways to optimize it, for example, through the configuration on TC, maven plugins, and so on. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (IGNITE-16548) Move BplusTree testing to load testing
[ https://issues.apache.org/jira/browse/IGNITE-16548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko resolved IGNITE-16548. -- Resolution: Won't Fix Leave it as integration tests for now. > Move BplusTree testing to load testing > -- > > Key: IGNITE-16548 > URL: https://issues.apache.org/jira/browse/IGNITE-16548 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Need to move tests from integration testing to load testing: > * > *src/integrationTest/java/org/apache/ignite/internal/pagememory/tree/ItBplusTree*Test* -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16379) Extend raft configuration changes' listener with onReconfigurationError
[
https://issues.apache.org/jira/browse/IGNITE-16379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500586#comment-17500586
]
Kirill Gusakov commented on IGNITE-16379:
-
Thanks! Merged to integration branch ignite-14209
> Extend raft configuration changes' listener with onReconfigurationError
> ---
>
> Key: IGNITE-16379
> URL: https://issues.apache.org/jira/browse/IGNITE-16379
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Gusakov
>Assignee: Kirill Gusakov
>Priority: Major
> Labels: ignite-3
>
> We need to extend raft change configurations listener with
> {{onReconfigurationError(errorContext)}} event.
> It must be invoked on any issues, which will be occurred when
> ChangePeersRequest has already been processed and provide the context of
> error: RaftError and message.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16498) Add ability to add handlers to RestModule from other Ignite modules
[ https://issues.apache.org/jira/browse/IGNITE-16498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500585#comment-17500585 ] Aleksandr Polovtcev commented on IGNITE-16498: -- LGTM, thank you! > Add ability to add handlers to RestModule from other Ignite modules > --- > > Key: IGNITE-16498 > URL: https://issues.apache.org/jira/browse/IGNITE-16498 > Project: Ignite > Issue Type: Improvement > Components: rest >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Currently, RestModule defines a handful of REST handlers hard-coded inside > the RestModule itselt. > The idea is to let other Ignite modules add their own REST handlers that > would use RestModule's infrastructure at runtime. Such handlers could be > added as plugins (for example, using ServiceLoader). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16379) Extend raft configuration changes' listener with onReconfigurationError
[
https://issues.apache.org/jira/browse/IGNITE-16379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500580#comment-17500580
]
Mirza Aliev commented on IGNITE-16379:
--
LGTM, added reminder about failover scenario when leader reelected
https://issues.apache.org/jira/browse/IGNITE-14873?focusedCommentId=17500578=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17500578
> Extend raft configuration changes' listener with onReconfigurationError
> ---
>
> Key: IGNITE-16379
> URL: https://issues.apache.org/jira/browse/IGNITE-16379
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Gusakov
>Assignee: Kirill Gusakov
>Priority: Major
> Labels: ignite-3
>
> We need to extend raft change configurations listener with
> {{onReconfigurationError(errorContext)}} event.
> It must be invoked on any issues, which will be occurred when
> ChangePeersRequest has already been processed and provide the context of
> error: RaftError and message.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16632) Calcite engine. Add calcite dependencies to TC build
[
https://issues.apache.org/jira/browse/IGNITE-16632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500579#comment-17500579
]
Petr Ivanov commented on IGNITE-16632:
--
Added rules to ignite.zip (run is used only for starting nodes from console).
[~alex_pl], check, please.
> Calcite engine. Add calcite dependencies to TC build
>
>
> Key: IGNITE-16632
> URL: https://issues.apache.org/jira/browse/IGNITE-16632
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksey Plekhanov
>Assignee: Petr Ivanov
>Priority: Major
> Labels: build, calcite
>
> Currently, a limited set of JARs is included in build artifacts
> ([https://ci.ignite.apache.org/admin/editRunType.html?id=buildType:IgniteTests24Java8_Build=RUNNER_286]).
> There are some new external dependencies for the new calcite module, that
> should be added too. Some test suites can't pass without these dependencies
> (C++ for example: [https://ci.ignite.apache.org/viewLog.html?buildId=6435330])
> {noformat}
> zip -ur run modules/calcite/target/libs/calcite-*.jar \
> modules/calcite/target/libs/avatica-*.jar \
> modules/calcite/target/libs/checker-qual-*.jar \
> modules/calcite/target/libs/commons-compiler-*.jar \
> modules/calcite/target/libs/esri-geometry-*.jar \
> modules/calcite/target/libs/guava-*.jar \
> modules/calcite/target/libs/janino-*.jar \
> modules/calcite/target/libs/json-path-*.jar {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (IGNITE-14873) Failover scenarios
[
https://issues.apache.org/jira/browse/IGNITE-14873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500578#comment-17500578
]
Mirza Aliev edited comment on IGNITE-14873 at 3/3/22, 8:24 AM:
---
Reminder:
We need to add a test for the scenario when leader reelection happens during
the change peers process, so we could check {{RaftGroupEventsListener}}
functionality
was (Author: maliev):
Reminder:
We need to add a test for the scenario when leader reelection happens during
the change peers process, so we could check RaftGroupEventsListener
functionality
> Failover scenarios
> --
>
> Key: IGNITE-14873
> URL: https://issues.apache.org/jira/browse/IGNITE-14873
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
>
> Need to implement a comprehensive set of tests in order to cover data
> rebalancing.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-14873) Failover scenarios
[ https://issues.apache.org/jira/browse/IGNITE-14873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500578#comment-17500578 ] Mirza Aliev commented on IGNITE-14873: -- Reminder: We need to add a test for the scenario when leader reelection happens during the change peers process, so we could check RaftGroupEventsListener functionality > Failover scenarios > -- > > Key: IGNITE-14873 > URL: https://issues.apache.org/jira/browse/IGNITE-14873 > Project: Ignite > Issue Type: Improvement >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > > Need to implement a comprehensive set of tests in order to cover data > rebalancing. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16642) [Native Persistence 3.0] Support indexes for B+Tree-based storage
Kirill Tkalenko created IGNITE-16642: Summary: [Native Persistence 3.0] Support indexes for B+Tree-based storage Key: IGNITE-16642 URL: https://issues.apache.org/jira/browse/IGNITE-16642 Project: Ignite Issue Type: Task Reporter: Kirill Tkalenko Fix For: 3.0.0-alpha5 Need to support indexes for B+Tree-based storage. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16641) [Native Persistence 3.0] Support persistent B+Tree-based storage
Kirill Tkalenko created IGNITE-16641: Summary: [Native Persistence 3.0] Support persistent B+Tree-based storage Key: IGNITE-16641 URL: https://issues.apache.org/jira/browse/IGNITE-16641 Project: Ignite Issue Type: Task Reporter: Kirill Tkalenko Fix For: 3.0.0-alpha5 Need to support the persistent B+Tree-based storage case. -- This message was sent by Atlassian Jira (v8.20.1#820001)
