[jira] [Commented] (IGNITE-18766) Incorrect id check in ClusterGroupAdapter.forNodeId
[
https://issues.apache.org/jira/browse/IGNITE-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710274#comment-17710274
]
Ignite TC Bot commented on IGNITE-18766:
{panel:title=Branch: [pull/10640/head] Base: [master] : Possible Blockers
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7132577]]
* IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeAndHistoryCleanup -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 12{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7132571]]
* IgniteCacheTestSuite12:
TxCrossCacheRemoteMultiplePartitionReservationTest.testRemoteCommitPartitionReservations
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache (Failover) 1{color} [[tests 0 TIMEOUT , Exit Code ,
Failure on metric |https://ci2.ignite.apache.org/viewLog.html?buildId=7132583]]
{color:#d04437}PDS 5{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7132630]]
* IgnitePdsTestSuite5:
SegmentAwareTest.testFinishWaitNextAbsoluteIndex_WhenSetToArchivedFirst - Test
has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/10640/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 1{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7132563]]
* {color:#013220}IgniteBasicTestSuite:
GridProjectionForCachesSelfTest.testProjectionWithBadId - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7132674buildTypeId=IgniteTests24Java8_RunAll]
> Incorrect id check in ClusterGroupAdapter.forNodeId
> ---
>
> Key: IGNITE-18766
> URL: https://issues.apache.org/jira/browse/IGNITE-18766
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.14
>Reporter: Pavel Tupitsyn
>Assignee: Denis Kuznetsov
>Priority: Minor
> Labels: ise, newbie
> Fix For: 2.15
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ClusterGroup.forNodeId checks *id* in a loop instead of *id0*:
> {code:java}
> for (UUID id0 : ids) {
> if (contains(id))
> nodeIds.add(id0);
> }
> {code}
> https://github.com/apache/ignite/blob/3de1dc44f53ea510328badf6cb6b423fe6975bd8/modules/core/src/main/java/org/apache/ignite/internal/cluster/ClusterGroupAdapter.java#L461
> The following unit test demonstrates the problem:
> {code:java}
> @Test
> public void testProjectionWithBadId() {
> ClusterNode locNode = ignite.cluster().localNode();
> ClusterGroup prj = ignite.cluster().forNodeId(UUID.randomUUID(),
> locNode.id());
> Collection nodes = prj.nodes();
> assertEquals(1, nodes.size());
> }
> {code}
> (add to GridProjectionForCachesSelfTest)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-16160) [ignite-extensions] Failed CdcKafkaReplicationTest.testActivePassiveReplication
[
https://issues.apache.org/jira/browse/IGNITE-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710189#comment-17710189
]
Ilya Shishkov commented on IGNITE-16160:
[~RyzhovSV], [~dpavlov], issue have nor detailed information about failure, nor
build log. But it is expected that such failure also have stacktrace, obtained
from future of corresponding thread. Issue looks similar to IGNITE-18995
(description contains stacktraces from failed threads).
WDYT, if we close this issue as incomplete or duplicate of IGNITE-18995.
> [ignite-extensions] Failed
> CdcKafkaReplicationTest.testActivePassiveReplication
> ---
>
> Key: IGNITE-16160
> URL: https://issues.apache.org/jira/browse/IGNITE-16160
> Project: Ignite
> Issue Type: Test
> Components: extensions
>Reporter: Sergei Ryzhov
>Priority: Major
> Labels: IEP-59, ise
>
> https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc?branch=%3Cdefault%3E=builds#all-projects
> Log:
> {code:java}
> [2022-04-16
> 06:13:32,532][ERROR][async-runnable-runner-1][IgniteTestResources] Cdc error
> class org.apache.ignite.IgniteInterruptedException: Got interrupted
> while waiting for future to complete.
> at
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:947)
> at
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:945)
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1130)
> at org.apache.ignite.Ignition.start(Ignition.java:331)
> at
> org.apache.ignite.cdc.IgniteToIgniteCdcStreamer.start(IgniteToIgniteCdcStreamer.java:114)
> at
> org.apache.ignite.internal.cdc.WalRecordsConsumer.start(WalRecordsConsumer.java:148)
> at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:283)
> at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:230)
> at
> org.apache.ignite.cdc.CdcIgniteToIgniteReplicationTest.lambda$igniteToIgnite$0(CdcIgniteToIgniteReplicationTest.java:83)
> at
> org.apache.ignite.testframework.GridTestUtils$RunnableX.run(GridTestUtils.java:2569)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$3(GridTestUtils.java:1161)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$4(GridTestUtils.java:1217)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:1538)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:88)
> [2022-04-16
> 06:13:32,550][ERROR][async-runnable-runner-1][IgniteTestResources] Cdc error
> class org.apache.ignite.IgniteException: sleep interrupted
> at
> org.apache.ignite.internal.cdc.CdcMain.consumeWalSegmentsUntilStopped(CdcMain.java:414)
> at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:286)
> at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:230)
> at
> org.apache.ignite.cdc.CdcIgniteToIgniteReplicationTest.lambda$igniteToIgnite$0(CdcIgniteToIgniteReplicationTest.java:83)
> at
> org.apache.ignite.testframework.GridTestUtils$RunnableX.run(GridTestUtils.java:2569)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$3(GridTestUtils.java:1161)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$4(GridTestUtils.java:1217)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:1538)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:88)
> Caused by: class
> org.apache.ignite.internal.IgniteInterruptedCheckedException: sleep
> interrupted
> at
> org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:8252)
> at
> org.apache.ignite.internal.cdc.CdcMain.consumeWalSegmentsUntilStopped(CdcMain.java:410)
> ... 8 more
> Caused by: java.lang.InterruptedException: sleep interrupted
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:8247)
> ... 9 more
> [2022-04-16
> 06:13:32,564][ERROR][async-runnable-runner-1][IgniteTestResources] Cdc error
> class org.apache.ignite.IgniteException: sleep interrupted
> at
> org.apache.ignite.internal.cdc.CdcMain.consumeWalSegmentsUntilStopped(CdcMain.java:414)
> at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:286)
> at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:230)
> at
> org.apache.ignite.cdc.CdcIgniteToIgniteReplicationTest.lambda$igniteToIgnite$0(CdcIgniteToIgniteReplicationTest.java:83)
> at
>
[jira] [Created] (IGNITE-19268) Wrong error TraceId
Alexander Belyak created IGNITE-19268:
-
Summary: Wrong error TraceId
Key: IGNITE-19268
URL: https://issues.apache.org/jira/browse/IGNITE-19268
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 3.0
Reporter: Alexander Belyak
Example of broken query:
drop table if exists t;
CREATE TABLE t (id varchar default gen_random_uuid primary key, val int);
insert into t(id, val) values('40e6215d-b5c6-4896-987c-f30f3678f608', 'val1');
Sql output (throw JDBC):
[Code: 0, SQL State: 5] Exception while executing query [query=insert into
t(id, val) values('40e6215d-b5c6-4896-987c-f30f3678f608', 'val1')]. Error
message:IGN-CMN-65535 TraceId:ede42a06-41da-4373-8174-d70029b18901 Remote query
execution
but in server log there is no such trace id, but there are the following
exception:
{code:java}
2023-04-10 18:01:05:443 +0300
[DEBUG][%node0%sql-execution-pool-3][QueryTaskExecutorImpl] Uncaught exception
org.apache.ignite.lang.IgniteInternalException: IGN-CMN-1
TraceId:3199170b-b51b-4061-9892-21026df58cf6 Unexpected exception
at
org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:320)
at
org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:80)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.NumberFormatException: For input string: "val1"
at
java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.base/java.lang.Integer.parseInt(Integer.java:652)
at java.base/java.lang.Integer.parseInt(Integer.java:770)
at org.apache.calcite.runtime.SqlFunctions.toInt(SqlFunctions.java:2293)
at SC.execute(Unknown Source)
at
org.apache.ignite.internal.sql.engine.exec.exp.ExpressionFactoryImpl$ProjectImpl.apply(ExpressionFactoryImpl.java:654)
at
org.apache.ignite.internal.sql.engine.exec.rel.ProjectNode.push(ProjectNode.java:69)
at
org.apache.ignite.internal.sql.engine.exec.rel.ScanNode.push(ScanNode.java:111)
at
org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:315)
... 4 more
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19266) Sonar Analysis fails with Java heap space
[
https://issues.apache.org/jira/browse/IGNITE-19266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-19266:
-
Fix Version/s: 2.15
(was: 2.16)
> Sonar Analysis fails with Java heap space
> -
>
> Key: IGNITE-19266
> URL: https://issues.apache.org/jira/browse/IGNITE-19266
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.15
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
> {code}
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
> This sink will not be analyzed any further.
> [INFO] Time spent writing ucfgs 0ms
> Error: Exception in thread "HttpClient-1-Worker-5"
> java.lang.OutOfMemoryError: Java heap space
> [INFO]
>
> [INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
> [INFO]
> {code}
> Host runners for GitHub:
> https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
> Reference for OOM:
> https://community.sonarsource.com/t/oome-in-analysis/79571
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-17244) .NET: Thin 3.0: Optimize async request handling
[ https://issues.apache.org/jira/browse/IGNITE-17244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Stronchinskiy reassigned IGNITE-17244: - Assignee: Sergey Stronchinskiy (was: Pavel Tupitsyn) > .NET: Thin 3.0: Optimize async request handling > --- > > Key: IGNITE-17244 > URL: https://issues.apache.org/jira/browse/IGNITE-17244 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Sergey Stronchinskiy >Priority: Minor > Labels: .NET, ignite-3 > > Reduce allocations when handling async requests in *ClientSocket*. > Look into combining the following functionality into a single object that can > be pooled: > * IBufferWriter - to write the request > * IValueTaskSource - to represent the task completion > * IThreadPoolWorkItem - to handle response on thread pool efficiently > See PoolingAsyncValueTaskMethodBuilder details: > https://devblogs.microsoft.com/dotnet/how-async-await-really-works/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19178) Add Sonar to Ignite project to analyze sources
[ https://issues.apache.org/jira/browse/IGNITE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-19178: - Fix Version/s: 2.15 (was: 2.16) > Add Sonar to Ignite project to analyze sources > -- > > Key: IGNITE-19178 > URL: https://issues.apache.org/jira/browse/IGNITE-19178 > Project: Ignite > Issue Type: Task > Components: build >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.15 > > Time Spent: 20m > Remaining Estimate: 0h > > Sonar is a code quality and security tool that is free to open-source > projects and recommended by the INFRA team the link for documentation: > https://cwiki.apache.org/confluence/display/INFRA/SonarCloud+for+ASF+projects > Despite in commonly used by many of the ASF projects, it can have the > following benefits for us: > - visualise simple problems for newcomers to work on; > - see the trends in the source code; > - add an extra layer of static code analysis; > The INFRA ticket: > https://issues.apache.org/jira/browse/INFRA-24415 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-19267) Implement local Low Watermark propagation
Ivan Bessonov created IGNITE-19267:
--
Summary: Implement local Low Watermark propagation
Key: IGNITE-19267
URL: https://issues.apache.org/jira/browse/IGNITE-19267
Project: Ignite
Issue Type: Improvement
Reporter: Ivan Bessonov
Fix For: 3.0.0-beta2
According to the IEP-91, we can delete old data, once it becomes older than the
certain threshold. At the moment, we can consider this threshold to be shared
between different tables, but be unique on individual nodes. It's called a Low
Watermark (LW).
The way the value is chosen is the following:
* There's the {_}data availability time{_}, that can be configured by the
user. This is a cluster configuration. It has a value of, for example, 45
minutes. Valid values - {{{}[0, +INF){}}}.
* There's a {_}GC frequency{_}, that's also a cluster configuration. For
example, 5 minuter. Range of valid values should be more strict.
* Last LW value is persisted in Vault.
* Every 5 minutes, we assign a new "lwCandidate{{{} = now() - 45min -
maxClockSkew"{}}}.
** If there are no running transactions with timestamp below
{{{}lwCandidate{}}}, we promote the candidate into a real LW value.
** Otherwise, we trigger GC with timestamp of the transaction with the oldest
timestamp (and promoting LW to that timestamp), and raising the bar every time*
that transaction is completed. Eventually, we will reach the point where there
are running transactions with timestamp below {{{}lwCandidate{}}}.
* it's not necessary to do it every time. But, once the timestamp of the oldest
RO transaction is above or equal to {{{}lwCandidate{}}}, we must guarantee its
promotion. Everything else is optimization.
* If there's a new RO transaction with timestamp below {{{}lwCandidate{}}}, we
fail it.
Promoted LW value cannot become smaller no matter what. All data below LW is
considered to be invalid, maybe broken and completely invisible to user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-19222) .NET: Add IgniteClientConfiguration.EnableClusterDiscovery
[ https://issues.apache.org/jira/browse/IGNITE-19222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-19222: --- Assignee: (was: Pavel Tupitsyn) > .NET: Add IgniteClientConfiguration.EnableClusterDiscovery > -- > > Key: IGNITE-19222 > URL: https://issues.apache.org/jira/browse/IGNITE-19222 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Affects Versions: 2.14 >Reporter: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.15 > > > Cluster discovery is always enabled currently, which can be undesirable in > some use cases. Add a config property to disable discovery. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-19266) Sonar Analysis fails with Java heap space
[
https://issues.apache.org/jira/browse/IGNITE-19266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov resolved IGNITE-19266.
--
Resolution: Fixed
[~NSAmelchev] thank you for the review. Merged to the master branch.
> Sonar Analysis fails with Java heap space
> -
>
> Key: IGNITE-19266
> URL: https://issues.apache.org/jira/browse/IGNITE-19266
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
> {code}
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
> This sink will not be analyzed any further.
> [INFO] Time spent writing ucfgs 0ms
> Error: Exception in thread "HttpClient-1-Worker-5"
> java.lang.OutOfMemoryError: Java heap space
> [INFO]
>
> [INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
> [INFO]
> {code}
> Host runners for GitHub:
> https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
> Reference for OOM:
> https://community.sonarsource.com/t/oome-in-analysis/79571
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19126) Make ItTableRaftSnapshotsTest less invasive
[ https://issues.apache.org/jira/browse/IGNITE-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710135#comment-17710135 ] Roman Puchkovskiy commented on IGNITE-19126: Thanks! > Make ItTableRaftSnapshotsTest less invasive > --- > > Key: IGNITE-19126 > URL: https://issues.apache.org/jira/browse/IGNITE-19126 > Project: Ignite > Issue Type: Bug >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > The current approach to make sure a follower does not get any logs entries > from the leader is to drop messages. This approach is too invasive (as some > other code might rely on those messages); also, it will stop working after > IGNITE-18712. > We should either drop only the vare minimum of the messages, or switch to > stopping a node to make sure it does not get log entries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18800) Create better DEVNOTES for Gradle build
[ https://issues.apache.org/jira/browse/IGNITE-18800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18800: -- Assignee: Mikhail Pochatkin > Create better DEVNOTES for Gradle build > - > > Key: IGNITE-18800 > URL: https://issues.apache.org/jira/browse/IGNITE-18800 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Modify DEVNOTES and describe better ussual command for build, test, > integrationTest, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-15962) CacheEntryRemovedListener makes the PUT operation to create ENTRY CREATED events
[
https://issues.apache.org/jira/browse/IGNITE-15962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710128#comment-17710128
]
Denis Chudov commented on IGNITE-15962:
---
The reproducer is too strict and fails even without the listener configurated.
But the truth is that the ContinuousEntry is created for the events that are
not configured, However the old value is not passed to this entry (and we see
it on the screenshots, that's because of isOldValueRequired == false). Also,
the event filter is used only to notify the exact configured event, everything
else happens by the same flow (including creation of ContinuousEntry).
> CacheEntryRemovedListener makes the PUT operation to create ENTRY CREATED
> events
>
>
> Key: IGNITE-15962
> URL: https://issues.apache.org/jira/browse/IGNITE-15962
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.11
>Reporter: Alexey Kukushkin
>Priority: Major
> Labels: cggg
> Attachments: CacheContinuousQueryEntry-HeapDump.png,
> CacheContinuousQueryEntry-StackTrace.png, EventListenerHeapUsage.java,
> IgniteServer.java, build.gradle
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> {{CacheEntryRemovedListener}} configured with
> {{MutableCacheEntryListenerConfiguration.isOldValueRequired = false}} makes
> the {{Cache#put}} operation to create {{CREATED}} events on the primary
> server for a short period of time. This is inefficient when working with
> large objects: our application running with limited heap memory fails with
> {{java.lang.OutOfMemoryError: Java heap space}} after executing a {{PUT}}
> operation since the entry referencing the object is "stuck" on the heap.
> h2. Reproducer
> h3. Steps
> We need two Ignite server nodes to demonstrate the problem. A cache is
> deployed on both the nodes and both the nodes listen to the {{ENTRY REMOVED}}
> events. Both the nodes disable fetching the {{CacheEntryEvent#getOldValue}}
> by setting {{MutableCacheEntryListenerConfiguration.isOldValueRequired =
> false}}
> # Build and run the attached [^IgniteServer.java]. This server is configured
> like described above and runs until manually terminated.
> # Build the run the attached test [^EventListenerHeapUsage.java] . This test:
> ## Starts another server configured like described above
> ## Puts a large object taking 35% of the free memory. This is done in an
> isolated scope so the memory after the operation is garbage collected,
> ## Attempts to allocate 70% of the heap.
> h3. Expected
> The last "allocate 70% of the heap" operation should succeed.
> h3. Actual
> {noformat}
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at
> apache.ignite.issues.EventListenerHeapUsage.entryRemovedEventListenerFetchesValueOnHeap(EventListenerHeapUsage.java:33)
> {noformat}
> h2 Analysis
> For some reason configuring the event listener makes the {{IgniteCache#put}}
> operation to create and attach an instance of {{CacheContinuousQueryEntry}}
> with {{evtType=CREATED}} and {{newObject}} referencing the entry.
> The attached heap dump !CacheContinuousQueryEntry-HeapDump.png! collected on
> the {{OutOfMemoryError}} demonstrates the large object "stuck" on the heap.
> The attached {{CacheContinuousQueryEntry}} initialization
> !CacheContinuousQueryEntry-StackTrace.png! proves the {{ENTRY CREATED}} event
> is being created even though we did not configure it.
> It seems wrong that Ignite needs to attached the {{ENTRY CREATED}} event to
> the "update" message. Please enhance Ignite to not be doing that or explain
> why Ignite must do that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19187) Sql. Handle StorageRebalanceException during rowsCount estimation
[
https://issues.apache.org/jira/browse/IGNITE-19187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710126#comment-17710126
]
Yury Gerzhedovich commented on IGNITE-19187:
[~xtern] LGTM.
> Sql. Handle StorageRebalanceException during rowsCount estimation
> -
>
> Key: IGNITE-19187
> URL: https://issues.apache.org/jira/browse/IGNITE-19187
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> We need to handle StorageRebalanceException which may be thrown from
> {{org.apache.ignite.internal.storage.MvPartitionStorage#rowsCount}} during
> row count estimation
> ({{org.apache.ignite.internal.sql.engine.schema.IgniteTableImpl.StatisticsImpl#getRowCount}}).
> {code:java}
> Caused by: org.apache.ignite.internal.storage.StorageRebalanceException:
> IGN-STORAGE-4 TraceId:a943b5f5-8018-4c4b-9e66-cc5060796848 Storage in the
> process of rebalancing: [table=TEST, partitionId=0]
> at
> app//org.apache.ignite.internal.storage.util.StorageUtils.throwExceptionDependingOnStorageState(StorageUtils.java:129)
> at
> app//org.apache.ignite.internal.storage.util.StorageUtils.throwExceptionIfStorageNotInRunnableState(StorageUtils.java:51)
> at
> app//org.apache.ignite.internal.storage.pagememory.mv.AbstractPageMemoryMvPartitionStorage.throwExceptionIfStorageNotInRunnableState(AbstractPageMemoryMvPartitionStorage.java:894)
> at
> app//org.apache.ignite.internal.storage.pagememory.mv.AbstractPageMemoryMvPartitionStorage.lambda$rowsCount$24(AbstractPageMemoryMvPartitionStorage.java:707)
> at
> app//org.apache.ignite.internal.storage.pagememory.mv.AbstractPageMemoryMvPartitionStorage.busy(AbstractPageMemoryMvPartitionStorage.java:785)
> at
> app//org.apache.ignite.internal.storage.pagememory.mv.AbstractPageMemoryMvPartitionStorage.rowsCount(AbstractPageMemoryMvPartitionStorage.java:706)
> at
> app//org.apache.ignite.internal.sql.engine.schema.IgniteTableImpl$StatisticsImpl.getRowCount(IgniteTableImpl.java:551)
> at
> app//org.apache.calcite.prepare.RelOptTableImpl.getRowCount(RelOptTableImpl.java:238)
> at
> app//org.apache.ignite.internal.sql.engine.rel.ProjectableFilterableTableScan.computeSelfCost(ProjectableFilterableTableScan.java:156)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19264) Simplify C++ Binary Tuple code
[ https://issues.apache.org/jira/browse/IGNITE-19264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Demakov updated IGNITE-19264: - Description: Some binary tuple code turned out to be useless for the C++ client lib. It is better to be removed to simplify maintenance. (was: Some binary tuple code turned out to be useless for the C++ client lib. It is better to be removed to simplify maintenence.) > Simplify C++ Binary Tuple code > -- > > Key: IGNITE-19264 > URL: https://issues.apache.org/jira/browse/IGNITE-19264 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 3.0.0-beta2 >Reporter: Aleksey Demakov >Assignee: Aleksey Demakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Some binary tuple code turned out to be useless for the C++ client lib. It is > better to be removed to simplify maintenance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19264) Simplify C++ Binary Tuple code
[ https://issues.apache.org/jira/browse/IGNITE-19264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Demakov updated IGNITE-19264: - Ignite Flags: (was: Docs Required,Release Notes Required) > Simplify C++ Binary Tuple code > -- > > Key: IGNITE-19264 > URL: https://issues.apache.org/jira/browse/IGNITE-19264 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 3.0.0-beta2 >Reporter: Aleksey Demakov >Assignee: Aleksey Demakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Some binary tuple code turned out to be useless for the C++ client lib. It is > better to be removed to simplify maintenence. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19266) Sonar Analysis fails with Java heap space
[
https://issues.apache.org/jira/browse/IGNITE-19266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-19266:
-
Fix Version/s: 2.16
> Sonar Analysis fails with Java heap space
> -
>
> Key: IGNITE-19266
> URL: https://issues.apache.org/jira/browse/IGNITE-19266
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
> {code}
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
> This sink will not be analyzed any further.
> [INFO] Time spent writing ucfgs 0ms
> Error: Exception in thread "HttpClient-1-Worker-5"
> java.lang.OutOfMemoryError: Java heap space
> [INFO]
>
> [INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
> [INFO]
> {code}
> Host runners for GitHub:
> https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
> Reference for OOM:
> https://community.sonarsource.com/t/oome-in-analysis/79571
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-18311) AssertionError in SQL on subquery with offset and limit
[
https://issues.apache.org/jira/browse/IGNITE-18311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710125#comment-17710125
]
Yury Gerzhedovich commented on IGNITE-18311:
After upgrading Calcite to ver 1.34 the issue is dissappear
> AssertionError in SQL on subquery with offset and limit
> ---
>
> Key: IGNITE-18311
> URL: https://issues.apache.org/jira/browse/IGNITE-18311
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Tupitsyn
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> *Query*
> {code}
> select _T0.KEY from (select _T1.KEY, _T1.VAL from PUBLIC.TBL1 as _T1 order by
> (_T1.KEY) desc limit ? offset ?) as _T0
> {code}
> *Error*
> {code}
> java.lang.AssertionError: rowType: RecordType(BIGINT KEY, VARCHAR(65536)
> VAL), mapping: [size=1, sourceCount=2, targetCount=1, elements=[0:0]]
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer$TrimResult.(RelFieldTrimmer.java:1342)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.result(RelFieldTrimmer.java:337)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.trimFields(RelFieldTrimmer.java:672)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.apache.calcite.util.ReflectUtil$2.invoke(ReflectUtil.java:531)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.dispatchTrimFields(RelFieldTrimmer.java:284)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.trimChild(RelFieldTrimmer.java:226)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.trimFields(RelFieldTrimmer.java:498)
> at jdk.internal.reflect.GeneratedMethodAccessor47.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.apache.calcite.util.ReflectUtil$2.invoke(ReflectUtil.java:531)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.dispatchTrimFields(RelFieldTrimmer.java:284)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.trim(RelFieldTrimmer.java:171)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.trimUnusedFields(SqlToRelConverter.java:549)
> at
> org.apache.ignite.internal.sql.engine.prepare.IgnitePlanner.trimUnusedFields(IgnitePlanner.java:351)
> at
> org.apache.ignite.internal.sql.engine.prepare.PlannerHelper.optimize(PlannerHelper.java:76)
> at
> org.apache.ignite.internal.sql.engine.prepare.PrepareServiceImpl.lambda$prepareQuery$1(PrepareServiceImpl.java:231)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-18664) Sql. subquery with OFFSET is not supported
[
https://issues.apache.org/jira/browse/IGNITE-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich resolved IGNITE-18664.
Fix Version/s: (was: 3.0.0-beta2)
Resolution: Duplicate
> Sql. subquery with OFFSET is not supported
> --
>
> Key: IGNITE-18664
> URL: https://issues.apache.org/jira/browse/IGNITE-18664
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-beta2
>Reporter: Maksim Zhuravkov
>Priority: Major
> Labels: calcite2-required, calcite3-required, ignite-3
>
> The following query is not supported
> {code:java}
> SELECT i, (WITH i2 AS (SELECT i+i1.i FROM integers LIMIT 1 OFFSET 1) SELECT *
> FROM i2) AS j FROM integers i1 ORDER BY i;
> {code}
> Expected result:
> {code:java}
> i j
> 1 3
> 2 4
> 3 5
> null null
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-18665) Sql. subquery with ORDER BY is not supported
[
https://issues.apache.org/jira/browse/IGNITE-18665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich resolved IGNITE-18665.
Fix Version/s: (was: 3.0.0-beta2)
Resolution: Duplicate
> Sql. subquery with ORDER BY is not supported
>
>
> Key: IGNITE-18665
> URL: https://issues.apache.org/jira/browse/IGNITE-18665
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Priority: Minor
> Labels: calcite2-required, calcite3-required, ignite-3
>
> The following query is not supported:
> {code:java}
> SELECT i, (WITH i2 AS (SELECT i+i1.i FROM integers ORDER BY 1 LIMIT 1 OFFSET
> 1) SELECT * FROM i2) AS j FROM integers i1 ORDER BY i;
> {code}
> {code:java}
> i j
> 1 3
> 2 4
> 3 5
> null null
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19266) Sonar Analysis fails with Java heap space
[
https://issues.apache.org/jira/browse/IGNITE-19266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-19266:
-
Description:
https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
{code}
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
This sink will not be analyzed any further.
[INFO] Time spent writing ucfgs 0ms
Error: Exception in thread "HttpClient-1-Worker-5" java.lang.OutOfMemoryError:
Java heap space
[INFO]
[INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
[INFO]
{code}
Host runners for GitHub:
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
Reference for OOM:
https://community.sonarsource.com/t/oome-in-analysis/79571
was:
https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
{code}
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
This sink will not be analyzed any further.
[INFO] Time spent writing ucfgs 0ms
Error: Exception in thread "HttpClient-1-Worker-5" java.lang.OutOfMemoryError:
Java heap space
[INFO]
[INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
[INFO]
{code}
Host runners for GitHub:
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
> Sonar Analysis fails with Java heap space
> -
>
> Key: IGNITE-19266
> URL: https://issues.apache.org/jira/browse/IGNITE-19266
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
>
> https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
> {code}
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
> This sink will not be analyzed any further.
[jira] [Updated] (IGNITE-19266) Sonar Analysis fails with Java heap space
[
https://issues.apache.org/jira/browse/IGNITE-19266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-19266:
-
Description:
https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
{code}
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
This sink will not be analyzed any further.
[INFO] Time spent writing ucfgs 0ms
Error: Exception in thread "HttpClient-1-Worker-5" java.lang.OutOfMemoryError:
Java heap space
[INFO]
[INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
[INFO]
{code}
Host runners for GitHub:
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
was:
https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
{code}
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
This sink will not be analyzed any further.
[INFO] Time spent writing ucfgs 0ms
Error: Exception in thread "HttpClient-1-Worker-5" java.lang.OutOfMemoryError:
Java heap space
[INFO]
[INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
[INFO]
{code}
> Sonar Analysis fails with Java heap space
> -
>
> Key: IGNITE-19266
> URL: https://issues.apache.org/jira/browse/IGNITE-19266
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
>
> https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
> {code}
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
> This sink will not be analyzed any further.
> [INFO] Time spent writing ucfgs 0ms
> Error: Exception in thread "HttpClient-1-Worker-5"
> java.lang.OutOfMemoryError: Java heap space
> [INFO]
>
[jira] [Updated] (IGNITE-19266) Sonar Analysis fails with Java heap space
[
https://issues.apache.org/jira/browse/IGNITE-19266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-19266:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Sonar Analysis fails with Java heap space
> -
>
> Key: IGNITE-19266
> URL: https://issues.apache.org/jira/browse/IGNITE-19266
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
>
> https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
> {code}
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
> This sink will not be analyzed any further.
> [INFO] Time spent writing ucfgs 0ms
> Error: Exception in thread "HttpClient-1-Worker-5"
> java.lang.OutOfMemoryError: Java heap space
> [INFO]
>
> [INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
> [INFO]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-19266) Sonar Analysis fails with Java heap space
Maxim Muzafarov created IGNITE-19266:
Summary: Sonar Analysis fails with Java heap space
Key: IGNITE-19266
URL: https://issues.apache.org/jira/browse/IGNITE-19266
Project: Ignite
Issue Type: Task
Affects Versions: 2.16
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
{code}
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
This sink will not be analyzed any further.
[INFO] Time spent writing ucfgs 0ms
Error: Exception in thread "HttpClient-1-Worker-5" java.lang.OutOfMemoryError:
Java heap space
[INFO]
[INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
[INFO]
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-19265) [ducktape] Refactoring ContinuousDataLoadApplication
Maksim Timonin created IGNITE-19265: --- Summary: [ducktape] Refactoring ContinuousDataLoadApplication Key: IGNITE-19265 URL: https://issues.apache.org/jira/browse/IGNITE-19265 Project: Ignite Issue Type: Improvement Reporter: Maksim Timonin Assignee: Maksim Timonin Currently we have 2 different applications to load data: # ContinuousDataLoadApplication # DataGenerationApplication They both have different patterns for loading: CDLA loads to pre-existing cache, while DGA creates configured number of caches, indexes, and load with . DGA is more general, it's proposed to refactor CDLA to reuse approach of DGA. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19243) C++ 3.0: propagate table schema updates to client on write-only operations
[ https://issues.apache.org/jira/browse/IGNITE-19243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-19243: Assignee: Igor Sapego (was: Pavel Tupitsyn) > C++ 3.0: propagate table schema updates to client on write-only operations > -- > > Key: IGNITE-19243 > URL: https://issues.apache.org/jira/browse/IGNITE-19243 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Igor Sapego >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Currently, C++ client receives table schema updates when write-read requests > are performed. For example, client performs TUPLE_GET request, sends key > tuple using old schema version, receives result tuple with the latest schema > version, and retrieves the latest schema. > However, some requests are "write-only": client sends a tuple, but does not > receive one back, like TUPLE_UPSERT. No schema updates are performed in this > case. > To fix this, include the latest schema version into all write-only operation > responses: > * TUPLE_UPSERT > * TUPLE_UPSERT_ALL > * TUPLE_INSERT > * TUPLE_INSERT_ALL > * TUPLE_REPLACE > * TUPLE_REPLACE_EXACT > * TUPLE_DELETE > * TUPLE_DELETE_ALL > * TUPLE_DELETE_EXACT > * TUPLE_DELETE_ALL_EXACT > * TUPLE_CONTAINS_KEY > Client will compare this version to the known one and perform a background > update, if necessary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-19264) Simplify C++ Binary Tuple code
Aleksey Demakov created IGNITE-19264: Summary: Simplify C++ Binary Tuple code Key: IGNITE-19264 URL: https://issues.apache.org/jira/browse/IGNITE-19264 Project: Ignite Issue Type: Improvement Components: platforms Affects Versions: 3.0.0-beta2 Reporter: Aleksey Demakov Assignee: Aleksey Demakov Fix For: 3.0.0-beta2 Some binary tuple code turned out to be useless for the C++ client lib. It is better to be removed to simplify maintenence. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19101) C++: Thin 3.0: Support basic authentication
[ https://issues.apache.org/jira/browse/IGNITE-19101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-19101: Assignee: Igor Sapego > C++: Thin 3.0: Support basic authentication > --- > > Key: IGNITE-19101 > URL: https://issues.apache.org/jira/browse/IGNITE-19101 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Affects Versions: 3.0.0-beta1 >Reporter: Mikhail Pochatkin >Assignee: Igor Sapego >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18311) AssertionError in SQL on subquery with offset and limit
[
https://issues.apache.org/jira/browse/IGNITE-18311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich reassigned IGNITE-18311:
--
Assignee: Yury Gerzhedovich
> AssertionError in SQL on subquery with offset and limit
> ---
>
> Key: IGNITE-18311
> URL: https://issues.apache.org/jira/browse/IGNITE-18311
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Pavel Tupitsyn
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> *Query*
> {code}
> select _T0.KEY from (select _T1.KEY, _T1.VAL from PUBLIC.TBL1 as _T1 order by
> (_T1.KEY) desc limit ? offset ?) as _T0
> {code}
> *Error*
> {code}
> java.lang.AssertionError: rowType: RecordType(BIGINT KEY, VARCHAR(65536)
> VAL), mapping: [size=1, sourceCount=2, targetCount=1, elements=[0:0]]
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer$TrimResult.(RelFieldTrimmer.java:1342)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.result(RelFieldTrimmer.java:337)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.trimFields(RelFieldTrimmer.java:672)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.apache.calcite.util.ReflectUtil$2.invoke(ReflectUtil.java:531)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.dispatchTrimFields(RelFieldTrimmer.java:284)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.trimChild(RelFieldTrimmer.java:226)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.trimFields(RelFieldTrimmer.java:498)
> at jdk.internal.reflect.GeneratedMethodAccessor47.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.apache.calcite.util.ReflectUtil$2.invoke(ReflectUtil.java:531)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.dispatchTrimFields(RelFieldTrimmer.java:284)
> at
> org.apache.calcite.sql2rel.RelFieldTrimmer.trim(RelFieldTrimmer.java:171)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.trimUnusedFields(SqlToRelConverter.java:549)
> at
> org.apache.ignite.internal.sql.engine.prepare.IgnitePlanner.trimUnusedFields(IgnitePlanner.java:351)
> at
> org.apache.ignite.internal.sql.engine.prepare.PlannerHelper.optimize(PlannerHelper.java:76)
> at
> org.apache.ignite.internal.sql.engine.prepare.PrepareServiceImpl.lambda$prepareQuery$1(PrepareServiceImpl.java:231)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-17880) Topology version must be extended with topology epoch
[ https://issues.apache.org/jira/browse/IGNITE-17880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov reassigned IGNITE-17880: -- Assignee: (was: Ilya Shishkov) > Topology version must be extended with topology epoch > - > > Key: IGNITE-17880 > URL: https://issues.apache.org/jira/browse/IGNITE-17880 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Priority: Major > Labels: ise > > Epoch must be presented as a timestamp and version pair. > Epoch timestamp must represent epoch start time. > Epoch major version must be incremented each time when topology version > changed from 0 to 1 (when the cluster started or restarted). > Epoch minor version should be changed on every baseline change. > Node's epoch version must be increased or keeped as is on node join. > Each decreasing must be logged as an error. > Epoch (version and timestamp) must be logged at every topology version change. > This will > - help to determine how many times the cluster was restarted (and make it > easier to determine when) > - checks that the part of the cluster which was restarted several times as a > standalone/segmented cluster will never join the rest of the cluster with the > lower epoch (check some segmentation and management problems) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18548) Fix CdcIgniteToIgniteReplicationTest#testActivePassiveReplication flakiness
[
https://issues.apache.org/jira/browse/IGNITE-18548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710100#comment-17710100
]
Ilya Shishkov commented on IGNITE-18548:
Problem is still actual:
#
https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7175027?hideProblemsFromDependencies=false=false=true=true
#
https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7124411?hideProblemsFromDependencies=false=false=true
> Fix CdcIgniteToIgniteReplicationTest#testActivePassiveReplication flakiness
> ---
>
> Key: IGNITE-18548
> URL: https://issues.apache.org/jira/browse/IGNITE-18548
> Project: Ignite
> Issue Type: Test
> Components: extensions
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Minor
> Labels: IEP-59, ise
> Attachments: _TESTS_CDC_342.log.zip, _TESTS_CDC_402.log.zip,
> _TESTS_CDC_405.log.zip, _TESTS_CDC_410.log.zip
>
>
> A {{CdcIgniteToIgniteReplicationTest#testActivePassiveReplication}} test is
> flaky. Sometimes it fails with reason as below:
> {code}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.ignite.testframework.junits.JUnitAssertAware.assertTrue(JUnitAssertAware.java:35)
> at
> org.apache.ignite.cdc.AbstractReplicationTest.checkMetrics(AbstractReplicationTest.java:621)
> at
> org.apache.ignite.cdc.AbstractReplicationTest.checkMetrics(AbstractReplicationTest.java:589)
> at
> org.apache.ignite.cdc.AbstractReplicationTest.testActivePassiveReplication(AbstractReplicationTest.java:283)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2504)
> at java.lang.Thread.run(Thread.java:750)
> {code}
> Reason should be investigated and fixed.
> Fails of the
> {{CdcIgniteToIgniteReplicationTest#testActivePassiveReplication}} can occur
> with different test parameters:
> # [clientType=CLIENT_NODE, atomicity=ATOMIC, mode=REPLICATED, backupCnt=0]:
> [TC2 Build #342 at 12 Jan
> 11:09|https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/6995624?hideProblemsFromDependencies=false=false=true=true],
> build log: [^_TESTS_CDC_342.log.zip]
> # [clientType=THIN_CLIENT, atomicity=TRANSACTIONAL, mode=REPLICATED,
> backupCnt=0]:
> [TC1 Build #410 at 11 Jan
> 08:00|https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7000973?hideProblemsFromDependencies=false=false=true=true],
> build log: [^_TESTS_CDC_410.log.zip]
> # [clientType=THIN_CLIENT, atomicity=ATOMIC, mode=REPLICATED, backupCnt=0],
> [clientType=THIN_CLIENT, atomicity=TRANSACTIONAL, mode=PARTITIONED,
> backupCnt=1]:
> [TC1 Build #405 at 9 Jan
> 11:55|https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/6996965?hideProblemsFromDependencies=false=false=true=true],
> build log: [^_TESTS_CDC_405.log.zip]
> # [clientType=THIN_CLIENT, atomicity=ATOMIC, mode=PARTITIONED, backupCnt=1]:
> [TC1 Build #402 at 31 Dec 22
> 08:02|https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/6986312?hideProblemsFromDependencies=false=false=true=true],
> build log: [^_TESTS_CDC_402.log.zip]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-18548) Fix CdcIgniteToIgniteReplicationTest#testActivePassiveReplication flakiness
[
https://issues.apache.org/jira/browse/IGNITE-18548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov reassigned IGNITE-18548:
--
Assignee: Ilya Shishkov
> Fix CdcIgniteToIgniteReplicationTest#testActivePassiveReplication flakiness
> ---
>
> Key: IGNITE-18548
> URL: https://issues.apache.org/jira/browse/IGNITE-18548
> Project: Ignite
> Issue Type: Test
> Components: extensions
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Minor
> Labels: IEP-59, ise
> Attachments: _TESTS_CDC_342.log.zip, _TESTS_CDC_402.log.zip,
> _TESTS_CDC_405.log.zip, _TESTS_CDC_410.log.zip
>
>
> A {{CdcIgniteToIgniteReplicationTest#testActivePassiveReplication}} test is
> flaky. Sometimes it fails with reason as below:
> {code}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.ignite.testframework.junits.JUnitAssertAware.assertTrue(JUnitAssertAware.java:35)
> at
> org.apache.ignite.cdc.AbstractReplicationTest.checkMetrics(AbstractReplicationTest.java:621)
> at
> org.apache.ignite.cdc.AbstractReplicationTest.checkMetrics(AbstractReplicationTest.java:589)
> at
> org.apache.ignite.cdc.AbstractReplicationTest.testActivePassiveReplication(AbstractReplicationTest.java:283)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2504)
> at java.lang.Thread.run(Thread.java:750)
> {code}
> Reason should be investigated and fixed.
> Fails of the
> {{CdcIgniteToIgniteReplicationTest#testActivePassiveReplication}} can occur
> with different test parameters:
> # [clientType=CLIENT_NODE, atomicity=ATOMIC, mode=REPLICATED, backupCnt=0]:
> [TC2 Build #342 at 12 Jan
> 11:09|https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/6995624?hideProblemsFromDependencies=false=false=true=true],
> build log: [^_TESTS_CDC_342.log.zip]
> # [clientType=THIN_CLIENT, atomicity=TRANSACTIONAL, mode=REPLICATED,
> backupCnt=0]:
> [TC1 Build #410 at 11 Jan
> 08:00|https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/7000973?hideProblemsFromDependencies=false=false=true=true],
> build log: [^_TESTS_CDC_410.log.zip]
> # [clientType=THIN_CLIENT, atomicity=ATOMIC, mode=REPLICATED, backupCnt=0],
> [clientType=THIN_CLIENT, atomicity=TRANSACTIONAL, mode=PARTITIONED,
> backupCnt=1]:
> [TC1 Build #405 at 9 Jan
> 11:55|https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/6996965?hideProblemsFromDependencies=false=false=true=true],
> build log: [^_TESTS_CDC_405.log.zip]
> # [clientType=THIN_CLIENT, atomicity=ATOMIC, mode=PARTITIONED, backupCnt=1]:
> [TC1 Build #402 at 31 Dec 22
> 08:02|https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/6986312?hideProblemsFromDependencies=false=false=true=true],
> build log: [^_TESTS_CDC_402.log.zip]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-18574) CDC: add documentation about Kafka request timeouts
[ https://issues.apache.org/jira/browse/IGNITE-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710094#comment-17710094 ] Ilya Shishkov commented on IGNITE-18574: I updated PR, [~timonin.maksim], can you take a look, please? > CDC: add documentation about Kafka request timeouts > --- > > Key: IGNITE-18574 > URL: https://issues.apache.org/jira/browse/IGNITE-18574 > Project: Ignite > Issue Type: Task > Components: documentation, extensions >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Minor > Labels: IEP-59, ise > Time Spent: 0.5h > Remaining Estimate: 0h > > We need to add more information information about timeouts configuration for > the CDC through Kafka. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19263) Complete future at Checkpointer#syncUpdatedPageStores when Checkpointer shuts down
[
https://issues.apache.org/jira/browse/IGNITE-19263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-19263:
-
Summary: Complete future at Checkpointer#syncUpdatedPageStores when
Checkpointer shuts down (was: Don't complete future at
Checkpointer#syncUpdatedPageStores when Checkpointer shuts down)
> Complete future at Checkpointer#syncUpdatedPageStores when Checkpointer shuts
> down
> --
>
> Key: IGNITE-19263
> URL: https://issues.apache.org/jira/browse/IGNITE-19263
> Project: Ignite
> Issue Type: Bug
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It was found that the future did not complete on the *Checkpointer* shuts
> down, which can lead to hangs.
> *org.apache.ignite.internal.pagememory.persistence.checkpoint.Checkpointer#syncUpdatedPageStores*
> {code:java}
> for (int i = 0; i < checkpointThreads; i++) {
> int threadIdx = i;
> pageWritePool.execute(() -> {
> Map.Entry entry =
> queue.poll();
> try {
> while (entry != null) {
> if (shutdownNow) {
> return;
> }
> fsyncDeltaFile(currentCheckpointProgress,
> entry.getKey(), entry.getValue());
> entry = queue.poll();
> }
> futures[threadIdx].complete(null);
> } catch (Throwable t) {
> futures[threadIdx].completeExceptionally(t);
> }
> });
> }
> blockingSectionBegin();
> try {
> // Hangs there.
> CompletableFuture.allOf(futures).join();
> } finally {
> blockingSectionEnd();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19263) Don't complete future at Checkpointer#syncUpdatedPageStores when Checkpointer shuts down
[
https://issues.apache.org/jira/browse/IGNITE-19263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710089#comment-17710089
]
Roman Puchkovskiy commented on IGNITE-19263:
LGTM
> Don't complete future at Checkpointer#syncUpdatedPageStores when Checkpointer
> shuts down
>
>
> Key: IGNITE-19263
> URL: https://issues.apache.org/jira/browse/IGNITE-19263
> Project: Ignite
> Issue Type: Bug
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It was found that the future did not complete on the *Checkpointer* shuts
> down, which can lead to hangs.
> *org.apache.ignite.internal.pagememory.persistence.checkpoint.Checkpointer#syncUpdatedPageStores*
> {code:java}
> for (int i = 0; i < checkpointThreads; i++) {
> int threadIdx = i;
> pageWritePool.execute(() -> {
> Map.Entry entry =
> queue.poll();
> try {
> while (entry != null) {
> if (shutdownNow) {
> return;
> }
> fsyncDeltaFile(currentCheckpointProgress,
> entry.getKey(), entry.getValue());
> entry = queue.poll();
> }
> futures[threadIdx].complete(null);
> } catch (Throwable t) {
> futures[threadIdx].completeExceptionally(t);
> }
> });
> }
> blockingSectionBegin();
> try {
> // Hangs there.
> CompletableFuture.allOf(futures).join();
> } finally {
> blockingSectionEnd();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-16905) Sql. ClassCastException when deserialising TIMESTAMP literal
[
https://issues.apache.org/jira/browse/IGNITE-16905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov reassigned IGNITE-16905:
-
Assignee: (was: Andrey Mashenkov)
> Sql. ClassCastException when deserialising TIMESTAMP literal
>
>
> Key: IGNITE-16905
> URL: https://issues.apache.org/jira/browse/IGNITE-16905
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Priority: Major
> Labels: calcite, ignite-3
>
> The problem appears to be caused by an inconsistency of RelReader and
> RexBuilder: RelReader diserializes every integer value as a value of type
> Integer, but the RexBuilder assumes that for TIMESTAMP literal a value of
> type Long will be passed, and make the explicit cast:
> {code:java}
> // RexBuilder#clean(Object, RelDataType)
> case TIMESTAMP:
> if (o instanceof TimestampString) {
> return o;
> } else if (o instanceof Calendar) {
> if (!((Calendar) o).getTimeZone().equals(DateTimeUtils.UTC_ZONE)) {
> throw new AssertionError();
> }
> return TimestampString.fromCalendarFields((Calendar) o);
> } else {
> return TimestampString.fromMillisSinceEpoch((Long) o);
> } {code}
>
> Here is a stack trace:
> {noformat}
> Caused by: java.lang.ClassCastException: class java.lang.Integer cannot be
> cast to class java.lang.Long (java.lang.Integer and java.lang.Long are in
> module java.base of loader 'bootstrap')
> at org.apache.calcite.rex.RexBuilder.clean(RexBuilder.java:1780)
> at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:1558)
> at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:1520)
> at
> org.apache.ignite.internal.sql.engine.externalize.RelJson.toRex(RelJson.java:759)
> at
> org.apache.ignite.internal.sql.engine.externalize.RelJsonReader$RelInputImpl.getTuple(RelJsonReader.java:367)
> at
> org.apache.ignite.internal.sql.engine.externalize.RelJsonReader$RelInputImpl.getTuples(RelJsonReader.java:347)
> ... 24 more {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-19263) Don't complete future at Checkpointer#syncUpdatedPageStores when Checkpointer shuts down
Kirill Tkalenko created IGNITE-19263:
Summary: Don't complete future at
Checkpointer#syncUpdatedPageStores when Checkpointer shuts down
Key: IGNITE-19263
URL: https://issues.apache.org/jira/browse/IGNITE-19263
Project: Ignite
Issue Type: Bug
Reporter: Kirill Tkalenko
Assignee: Kirill Tkalenko
Fix For: 3.0.0-beta2
It was found that the future did not complete on the *Checkpointer* shuts down,
which can lead to hangs.
*org.apache.ignite.internal.pagememory.persistence.checkpoint.Checkpointer#syncUpdatedPageStores*
{code:java}
for (int i = 0; i < checkpointThreads; i++) {
int threadIdx = i;
pageWritePool.execute(() -> {
Map.Entry entry = queue.poll();
try {
while (entry != null) {
if (shutdownNow) {
return;
}
fsyncDeltaFile(currentCheckpointProgress,
entry.getKey(), entry.getValue());
entry = queue.poll();
}
futures[threadIdx].complete(null);
} catch (Throwable t) {
futures[threadIdx].completeExceptionally(t);
}
});
}
blockingSectionBegin();
try {
// Hangs there.
CompletableFuture.allOf(futures).join();
} finally {
blockingSectionEnd();
}
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19262) Sql. DDL silently ignores transaction
[
https://issues.apache.org/jira/browse/IGNITE-19262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-19262:
Description:
In *ItSqlSynchronousApiTest*, update *checkDdl*:
{code:java}
private static void checkDdl(boolean expectedApplied, Session ses, String
sql) {
Transaction tx = CLUSTER_NODES.get(0).transactions().begin();
ResultSet res = ses.execute(
tx,
sql
);
assertEquals(expectedApplied, res.wasApplied());
assertFalse(res.hasRowSet());
assertEquals(-1, res.affectedRows());
res.close();
tx.rollback();
}
{code}
All tests pass, even though we call rollback.
DDL does not support transactions. We should throw an exception when *tx* is
not null with a DDL statement to make this clear to the users.
> Sql. DDL silently ignores transaction
> -
>
> Key: IGNITE-19262
> URL: https://issues.apache.org/jira/browse/IGNITE-19262
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> In *ItSqlSynchronousApiTest*, update *checkDdl*:
> {code:java}
> private static void checkDdl(boolean expectedApplied, Session ses, String
> sql) {
> Transaction tx = CLUSTER_NODES.get(0).transactions().begin();
> ResultSet res = ses.execute(
> tx,
> sql
> );
> assertEquals(expectedApplied, res.wasApplied());
> assertFalse(res.hasRowSet());
> assertEquals(-1, res.affectedRows());
> res.close();
> tx.rollback();
> }
> {code}
> All tests pass, even though we call rollback.
> DDL does not support transactions. We should throw an exception when *tx* is
> not null with a DDL statement to make this clear to the users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-19262) Sql. DDL silently ignores transaction
Pavel Tupitsyn created IGNITE-19262: --- Summary: Sql. DDL silently ignores transaction Key: IGNITE-19262 URL: https://issues.apache.org/jira/browse/IGNITE-19262 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 3.0.0-beta1 Reporter: Pavel Tupitsyn Fix For: 3.0.0-beta2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-14266) System views for page statistics must include the buckets sizes
[
https://issues.apache.org/jira/browse/IGNITE-14266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710079#comment-17710079
]
Ignite TC Bot commented on IGNITE-14266:
{panel:title=Branch: [pull/10631/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10631/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=7127574buildTypeId=IgniteTests24Java8_RunAll]
> System views for page statistics must include the buckets sizes
> ---
>
> Key: IGNITE-14266
> URL: https://issues.apache.org/jira/browse/IGNITE-14266
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.15
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Affected system views: CACHE_GROUP_PAGE_LISTS, DATA_REGION_PAGE_LISTS
> The bucket index corresponds to the interval of free space on pages it
> contains. We must add this info to the system views.
> [1]
> https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#page_lists
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19231) Change thread pool for metastore raft group
[ https://issues.apache.org/jira/browse/IGNITE-19231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710075#comment-17710075 ] Roman Puchkovskiy commented on IGNITE-19231: The patch looks good to me > Change thread pool for metastore raft group > --- > > Key: IGNITE-19231 > URL: https://issues.apache.org/jira/browse/IGNITE-19231 > Project: Ignite > Issue Type: Bug >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 3h > Remaining Estimate: 0h > > It was discovered that the common thread pool is used for raft group the > metastorage and partitions, which can lead to deadlocks. The metastorage > needs its own thread pool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
