[jira] [Created] (IGNITE-17167) Simplify the configuration asm generator
Kirill Tkalenko created IGNITE-17167: Summary: Simplify the configuration asm generator Key: IGNITE-17167 URL: https://issues.apache.org/jira/browse/IGNITE-17167 Project: Ignite Issue Type: Task Reporter: Kirill Tkalenko Fix For: 3.0.0-alpha6 At the moment, the *org.apache.ignite.internal.configuration.asm.ConfigurationAsmGenerator* looks complicated due to the addition of internal, polymorphic and abstract configuration, the code has become harder to read and edit. It is proposed to think about how and to divide this class into methods or subclasses for each type of configuration. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17166) Simplify the configuration annotation processor
Kirill Tkalenko created IGNITE-17166: Summary: Simplify the configuration annotation processor Key: IGNITE-17166 URL: https://issues.apache.org/jira/browse/IGNITE-17166 Project: Ignite Issue Type: Task Reporter: Kirill Tkalenko Fix For: 3.0.0-alpha6 At the moment, the *org.apache.ignite.internal.configuration.processor.Processor* looks complicated due to the addition of internal, polymorphic and abstract configuration, the code has become harder to read and edit. It is proposed to think about how and to divide this class into methods or subclasses for each type of configuration. It would also be nice to write validation for class fields, for example that a field (if not static) can only have one of the annotations *Value*, *ConfigValue* and *NamedConfigValue*, etc. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17163) Broken table in data region documentation page
[ https://issues.apache.org/jira/browse/IGNITE-17163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554266#comment-17554266 ] Andrey N. Gura commented on IGNITE-17163: - [~igusev] LGTM. Merged to main branch. Thanks for contribution! > Broken table in data region documentation page > -- > > Key: IGNITE-17163 > URL: https://issues.apache.org/jira/browse/IGNITE-17163 > Project: Ignite > Issue Type: Bug > Components: site >Affects Versions: 3.0.0-alpha5 >Reporter: Andrey N. Gura >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > > The table with data regions parameters is broken on the website. > https://ignite.apache.org/docs/3.0.0-alpha/config/data-region -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] (IGNITE-16038) Java Thin Client: Retrieve binary configuration from server
[ https://issues.apache.org/jira/browse/IGNITE-16038 ]
Pavel Tupitsyn deleted comment on IGNITE-16038:
-
was (Author: ignitetcbot):
{panel:title=Branch: [pull/10076/head] Base: [master] : Possible Blockers
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cassandra Store{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627293]]
* IgniteCassandraStoreTestSuite:
IgnitePersistentStoreTest.directPersistenceConfigTest - Test has low fail rate
in base branch 0,0% and is not flaky
{color:#d04437}Calcite SQL{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6627366]]
{color:#d04437}SPI (Discovery){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627358]]
* IgniteSpiDiscoverySelfTestSuite:
TcpDiscoverySegmentationPolicyTest.testStopOnSegmentation - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 1 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6627331]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testConnectionRestore1 -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Examples{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6627338]]
{color:#d04437}Java Client{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627861]]
* IgniteClientTestSuite:
ClientTcpSslDirectMultiNodeSelfTest.testTopologyListener - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1 (lazy=true){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627362]]
* IgniteBinaryCacheQueryLazyTestSuite:
DynamicIndexServerCoordinatorBasicSelfTest.testCreateIndexWithParallelismPartitionedTransactional
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform C++ CMake (Linux Clang){color} [[tests 1 JVM CRASH
|https://ci.ignite.apache.org/viewLog.html?buildId=6627340]]
* IgniteCoreTest: ComputeTestSuite: IgniteBroadcastRemoteError - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Compute (Grid){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627292]]
* IgniteBinaryObjectsComputeGridTestSuite:
GridMultinodeRedeployIsolatedModeSelfTest.testIsolatedMode - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Continuous Query 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627296]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryBufferLimitTest.testContinuousQueryPendingBufferLimit[cacheMode=REPLICATED,
atomicityMode=ATOMIC] - Test has low fail rate in base branch 0,0% and is not
flaky
{panel}
{panel:title=Branch: [pull/10076/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=6627481]]
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testAutoBinaryConfigurationEnabledOverridesExplicitClientSettings
- PASSED{color}
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testCustomMapperOnServerCustomMapperOnClientDoesNotThrow
- PASSED{color}
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testAutoBinaryConfigurationDisabledKeepsClientSettingsAsIs
- PASSED{color}
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testCustomMapperOnServerDefaultMapperOnClientThrows -
PASSED{color}
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testAutoBinaryConfigurationEnabledRetrievesValuesFromServer
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6627367buildTypeId=IgniteTests24Java8_RunAll]
> Java Thin Client: Retrieve binary configuration from server
> ---
>
> Key: IGNITE-16038
> URL: https://issues.apache.org/jira/browse/IGNITE-16038
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.11
>Reporter: Alexandr Shapkin
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Thin clients require manual binary configuration currently. Settings like
> compact footer and simple/full name mapper should be set to match the cluster
> settings. Extend the protocol to retrieve those settings automatically on
> start.
>
> I.e. it's impossible to read a value inserted by a thick client with java
> thin client without specifying compactFooter=true
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-16038) Java Thin Client: Retrieve binary configuration from server
[
https://issues.apache.org/jira/browse/IGNITE-16038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554252#comment-17554252
]
Ignite TC Bot commented on IGNITE-16038:
{panel:title=Branch: [pull/10076/head] Base: [master] : Possible Blockers
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cassandra Store{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627293]]
* IgniteCassandraStoreTestSuite:
IgnitePersistentStoreTest.directPersistenceConfigTest - Test has low fail rate
in base branch 0,0% and is not flaky
{color:#d04437}Calcite SQL{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6627366]]
{color:#d04437}SPI (Discovery){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627358]]
* IgniteSpiDiscoverySelfTestSuite:
TcpDiscoverySegmentationPolicyTest.testStopOnSegmentation - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 1 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6627331]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testConnectionRestore1 -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Examples{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6627338]]
{color:#d04437}Java Client{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627861]]
* IgniteClientTestSuite:
ClientTcpSslDirectMultiNodeSelfTest.testTopologyListener - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1 (lazy=true){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627362]]
* IgniteBinaryCacheQueryLazyTestSuite:
DynamicIndexServerCoordinatorBasicSelfTest.testCreateIndexWithParallelismPartitionedTransactional
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform C++ CMake (Linux Clang){color} [[tests 1 JVM CRASH
|https://ci.ignite.apache.org/viewLog.html?buildId=6627340]]
* IgniteCoreTest: ComputeTestSuite: IgniteBroadcastRemoteError - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Compute (Grid){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627292]]
* IgniteBinaryObjectsComputeGridTestSuite:
GridMultinodeRedeployIsolatedModeSelfTest.testIsolatedMode - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Continuous Query 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627296]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryBufferLimitTest.testContinuousQueryPendingBufferLimit[cacheMode=REPLICATED,
atomicityMode=ATOMIC] - Test has low fail rate in base branch 0,0% and is not
flaky
{panel}
{panel:title=Branch: [pull/10076/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=6627481]]
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testAutoBinaryConfigurationEnabledOverridesExplicitClientSettings
- PASSED{color}
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testCustomMapperOnServerCustomMapperOnClientDoesNotThrow
- PASSED{color}
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testAutoBinaryConfigurationDisabledKeepsClientSettingsAsIs
- PASSED{color}
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testCustomMapperOnServerDefaultMapperOnClientThrows -
PASSED{color}
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testAutoBinaryConfigurationEnabledRetrievesValuesFromServer
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6627367buildTypeId=IgniteTests24Java8_RunAll]
> Java Thin Client: Retrieve binary configuration from server
> ---
>
> Key: IGNITE-16038
> URL: https://issues.apache.org/jira/browse/IGNITE-16038
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.11
>Reporter: Alexandr Shapkin
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Thin clients require manual binary configuration currently. Settings like
> compact footer and simple/full name mapper should be set to match the cluster
> settings. Extend the protocol to retrieve those settings automatically on
> start.
>
> I.e. it's impossible to read a value inserted by a thick client with java
> thin client without specifying compactFooter=true
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-16038) Java Thin Client: Retrieve binary configuration from server
[
https://issues.apache.org/jira/browse/IGNITE-16038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554246#comment-17554246
]
Ignite TC Bot commented on IGNITE-16038:
{panel:title=Branch: [pull/10076/head] Base: [master] : Possible Blockers
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cassandra Store{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627293]]
* IgniteCassandraStoreTestSuite:
IgnitePersistentStoreTest.directPersistenceConfigTest - Test has low fail rate
in base branch 0,0% and is not flaky
{color:#d04437}Calcite SQL{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6627366]]
{color:#d04437}SPI (Discovery){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627358]]
* IgniteSpiDiscoverySelfTestSuite:
TcpDiscoverySegmentationPolicyTest.testStopOnSegmentation - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 1 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6627331]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testConnectionRestore1 -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Examples{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6627338]]
{color:#d04437}Java Client{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627861]]
* IgniteClientTestSuite:
ClientTcpSslDirectMultiNodeSelfTest.testTopologyListener - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1 (lazy=true){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627362]]
* IgniteBinaryCacheQueryLazyTestSuite:
DynamicIndexServerCoordinatorBasicSelfTest.testCreateIndexWithParallelismPartitionedTransactional
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform C++ CMake (Linux Clang){color} [[tests 1 JVM CRASH
|https://ci.ignite.apache.org/viewLog.html?buildId=6627340]]
* IgniteCoreTest: ComputeTestSuite: IgniteBroadcastRemoteError - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Compute (Grid){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627292]]
* IgniteBinaryObjectsComputeGridTestSuite:
GridMultinodeRedeployIsolatedModeSelfTest.testIsolatedMode - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Continuous Query 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6627296]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryBufferLimitTest.testContinuousQueryPendingBufferLimit[cacheMode=REPLICATED,
atomicityMode=ATOMIC] - Test has low fail rate in base branch 0,0% and is not
flaky
{panel}
{panel:title=Branch: [pull/10076/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=6627481]]
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testAutoBinaryConfigurationEnabledOverridesExplicitClientSettings
- PASSED{color}
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testCustomMapperOnServerCustomMapperOnClientDoesNotThrow
- PASSED{color}
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testAutoBinaryConfigurationDisabledKeepsClientSettingsAsIs
- PASSED{color}
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testCustomMapperOnServerDefaultMapperOnClientThrows -
PASSED{color}
* {color:#013220}ClientTestSuite:
BinaryConfigurationTest.testAutoBinaryConfigurationEnabledRetrievesValuesFromServer
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6627367buildTypeId=IgniteTests24Java8_RunAll]
> Java Thin Client: Retrieve binary configuration from server
> ---
>
> Key: IGNITE-16038
> URL: https://issues.apache.org/jira/browse/IGNITE-16038
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.11
>Reporter: Alexandr Shapkin
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Thin clients require manual binary configuration currently. Settings like
> compact footer and simple/full name mapper should be set to match the cluster
> settings. Extend the protocol to retrieve those settings automatically on
> start.
>
> I.e. it's impossible to read a value inserted by a thick client with java
> thin client without specifying compactFooter=true
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-15655) Random tests fail due to TimeoutException while waiting for a response
[
https://issues.apache.org/jira/browse/IGNITE-15655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15655:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Random tests fail due to TimeoutException while waiting for a response
> --
>
> Key: IGNITE-15655
> URL: https://issues.apache.org/jira/browse/IGNITE-15655
> Project: Ignite
> Issue Type: Bug
>Reporter: Konstantin Orlov
>Assignee: Vyacheslav Koptilin
>Priority: Blocker
> Labels: ignite-3
> Attachments: _Integration_Tests_Integration_Tests_3305.log.zip,
> _Integration_Tests_Integration_Tests_3322.log.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. Problem
> Sometimes tests fails on main branch with an abstract "{{Caused by:
> java.util.concurrent.TimeoutException: Did not observe any item or terminal
> signal within 1000ms in 'source(MonoDefer)' (and no fallback has been
> configured)"}} reason.
> Need to investigate and fix the root cause of this fails.
>
> Test
> {{org.apache.ignite.internal.runner.app.ITSchemaChangeKVViewTest.testRenameColumn()}}
> in [^_Integration_Tests_Integration_Tests_3305.log.zip]
> Test
> {{org.apache.ignite.internal.runner.app.ITSchemaChangeKVViewTest.testMergeChangesAddDropAdd()}}
> in [^_Integration_Tests_Integration_Tests_3322.log.zip]
> h3. Upd 1
> Quick research revealed that the main reason for mentioned above
> _TimeoutException_ is a poor consistency of raft timeouts .
> Most of jraft timeouts are based on electionTimeoutMs.
> {code:java}
> // A follower would become a candidate if it doesn't receive any message
> // from the leader in |election_timeout_ms| milliseconds
> // Default: 1000 (1s)
> private int electionTimeoutMs = 1000; // follower to candidate timeout
> {code}
> For example both voteTime and electionTime use exact value of
> getElectionTimeoutMs (1000 ms):
> {code:java}
> String name = "JRaft-VoteTimer-" + suffix;
> this.voteTimer = new RepeatedTimer(name,
> options.getElectionTimeoutMs(), timerFactory.getVoteTimer(name)) {...};
> name = "JRaft-ElectionTimer-" + suffix;
> electionTimer = new RepeatedTimer(name,
> options.getElectionTimeoutMs(), timerFactory.getElectionTimer(name)) {...};
> {code}
> It actually means that Loza#TIMEOUT that was also initially set to 1000 ms
> just won't be enough in some cases. Seems that "operation timeout
> (LOZA#TIMEOUT)" should be an order of magnitude more than election timeout.
> During the implementation of [naive data
> rebalance|https://issues.apache.org/jira/browse/IGNITE-15491] LOZA#TIMEOUT
> was set to 10_000 to satisfy this need. Also a
> [ticket|https://issues.apache.org/jira/browse/IGNITE-15705] for timeouts
> research and consolidation was created.
> So, taking into consideration that raft operation timeout was already
> increased from 1 second to 10 it worth to just enable all tests that were
> disabled under IGNITE-15655 and check whether they are still failing.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17165) ItProjectScanMergeRuleTest fails on Windows platform
Vyacheslav Koptilin created IGNITE-17165:
Summary: ItProjectScanMergeRuleTest fails on Windows platform
Key: IGNITE-17165
URL: https://issues.apache.org/jira/browse/IGNITE-17165
Project: Ignite
Issue Type: Bug
Reporter: Vyacheslav Koptilin
The ItProjectScanMergeRuleTest.testProjects fails with the following error
message:
{noformat}
java.lang.AssertionError: Invalid plan:
IgniteExchange(distribution=[single]): rowcount = 1.0, cumulative cost =
IgniteCost [rowCount=2.0, cpu=5.0, memory=0.0, io=0.0, network=4.0], id = 23507
IgniteTableScan(table=[[PUBLIC, PRODUCTS]],
tableId=[feaccfde-5e54-4e25-a911-7f7015c9a81e], tableVer=[1], filters=[>($t0,
1)], projects=[[$t1]], requiredColumns=[{2, 5}]): rowcount = 1.0, cumulative
cost = IgniteCost [rowCount=1.0, cpu=4.0, memory=0.0, io=0.0, network=0.0], id
= 23504
Expected: a string contains ".*Ignite(Table|Index)Scan\\(table=\\[\\[PUBLIC,
PRODUCTS\\]\\], .*requiredColumns=\\[\\{2, 5\\}\\].*"
but: was "IgniteExchange(distribution=[single]): rowcount = 1.0,
cumulative cost = IgniteCost [rowCount=2.0, cpu=5.0, memory=0.0, io=0.0,
network=4.0], id = 23507
IgniteTableScan(table=[[PUBLIC, PRODUCTS]],
tableId=[feaccfde-5e54-4e25-a911-7f7015c9a81e], tableVer=[1], filters=[>($t0,
1)], projects=[[$t1]], requiredColumns=[{2, 5}]): rowcount = 1.0, cumulative
cost = IgniteCost [rowCount=1.0, cpu=4.0, memory=0.0, io=0.0, network=0.0], id
= 23504
"
{noformat}
The root cause is that _QueryChecker_ uses "\n" as a line separator instead of
"\r\n"
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17164) Absorb RAFT/in-memory/rebalance details
Roman Puchkovskiy created IGNITE-17164: -- Summary: Absorb RAFT/in-memory/rebalance details Key: IGNITE-17164 URL: https://issues.apache.org/jira/browse/IGNITE-17164 Project: Ignite Issue Type: Task Components: persistence Reporter: Roman Puchkovskiy Assignee: Roman Puchkovskiy Fix For: 3.0.0-alpha5 There is a design described in IGNITE-16668. To implement the required changes, it is required to read the RAFT paper, see what problems it can cause for volatile cases and how the proposed design solves the problems with the rebalance in volatile RAFT cases. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17163) Broken table in data region documentation page
[ https://issues.apache.org/jira/browse/IGNITE-17163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554241#comment-17554241 ] Igor Gusev commented on IGNITE-17163: - [~agura] please check the attached PR. > Broken table in data region documentation page > -- > > Key: IGNITE-17163 > URL: https://issues.apache.org/jira/browse/IGNITE-17163 > Project: Ignite > Issue Type: Bug > Components: site >Affects Versions: 3.0.0-alpha5 >Reporter: Andrey N. Gura >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > > The table with data regions parameters is broken on the website. > https://ignite.apache.org/docs/3.0.0-alpha/config/data-region -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17163) Broken table in data region documentation page
[ https://issues.apache.org/jira/browse/IGNITE-17163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey N. Gura updated IGNITE-17163: Fix Version/s: (was: 3.0.0-alpha5) > Broken table in data region documentation page > -- > > Key: IGNITE-17163 > URL: https://issues.apache.org/jira/browse/IGNITE-17163 > Project: Ignite > Issue Type: Bug > Components: site >Affects Versions: 3.0.0-alpha5 >Reporter: Andrey N. Gura >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > > The table with data regions parameters is broken on the website. > https://ignite.apache.org/docs/3.0.0-alpha/config/data-region -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17163) Broken table in data region documentation page
[ https://issues.apache.org/jira/browse/IGNITE-17163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey N. Gura updated IGNITE-17163: Labels: ignite-3 (was: ) > Broken table in data region documentation page > -- > > Key: IGNITE-17163 > URL: https://issues.apache.org/jira/browse/IGNITE-17163 > Project: Ignite > Issue Type: Bug > Components: site >Affects Versions: 3.0.0-alpha5 >Reporter: Andrey N. Gura >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > The table with data regions parameters is broken on the website. > https://ignite.apache.org/docs/3.0.0-alpha/config/data-region -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17163) Broken table in data region documentation page
[ https://issues.apache.org/jira/browse/IGNITE-17163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey N. Gura updated IGNITE-17163: Ignite Flags: (was: Docs Required,Release Notes Required) > Broken table in data region documentation page > -- > > Key: IGNITE-17163 > URL: https://issues.apache.org/jira/browse/IGNITE-17163 > Project: Ignite > Issue Type: Bug > Components: site >Affects Versions: 3.0.0-alpha5 >Reporter: Andrey N. Gura >Assignee: Igor Gusev >Priority: Major > Fix For: 3.0.0-alpha5 > > > The table with data regions parameters is broken on the website. > https://ignite.apache.org/docs/3.0.0-alpha/config/data-region -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17163) Broken table in data region documentation page
Andrey N. Gura created IGNITE-17163: --- Summary: Broken table in data region documentation page Key: IGNITE-17163 URL: https://issues.apache.org/jira/browse/IGNITE-17163 Project: Ignite Issue Type: Bug Components: site Affects Versions: 3.0.0-alpha5 Reporter: Andrey N. Gura Assignee: Igor Gusev Fix For: 3.0.0-alpha5 The table with data regions parameters is broken on the website. https://ignite.apache.org/docs/3.0.0-alpha/config/data-region -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16038) Java Thin Client: Retrieve binary configuration from server
[ https://issues.apache.org/jira/browse/IGNITE-16038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554181#comment-17554181 ] Pavel Tupitsyn commented on IGNITE-16038: - PR is ready for review. [~isapego] [~ashapkin] [~alex_pl] please have a look. > Java Thin Client: Retrieve binary configuration from server > --- > > Key: IGNITE-16038 > URL: https://issues.apache.org/jira/browse/IGNITE-16038 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.11 >Reporter: Alexandr Shapkin >Assignee: Pavel Tupitsyn >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Thin clients require manual binary configuration currently. Settings like > compact footer and simple/full name mapper should be set to match the cluster > settings. Extend the protocol to retrieve those settings automatically on > start. > > I.e. it's impossible to read a value inserted by a thick client with java > thin client without specifying compactFooter=true -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16038) Java Thin Client: Retrieve binary configuration from server
[ https://issues.apache.org/jira/browse/IGNITE-16038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-16038: Fix Version/s: 2.14 > Java Thin Client: Retrieve binary configuration from server > --- > > Key: IGNITE-16038 > URL: https://issues.apache.org/jira/browse/IGNITE-16038 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.11 >Reporter: Alexandr Shapkin >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Thin clients require manual binary configuration currently. Settings like > compact footer and simple/full name mapper should be set to match the cluster > settings. Extend the protocol to retrieve those settings automatically on > start. > > I.e. it's impossible to read a value inserted by a thick client with java > thin client without specifying compactFooter=true -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16038) Java Thin Client: Retrieve binary configuration from server
[ https://issues.apache.org/jira/browse/IGNITE-16038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-16038: Release Note: Java thin: Added automatic binary configuration. Name mapper and compact footer settings will be set according to cluster configuration. > Java Thin Client: Retrieve binary configuration from server > --- > > Key: IGNITE-16038 > URL: https://issues.apache.org/jira/browse/IGNITE-16038 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.11 >Reporter: Alexandr Shapkin >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Thin clients require manual binary configuration currently. Settings like > compact footer and simple/full name mapper should be set to match the cluster > settings. Extend the protocol to retrieve those settings automatically on > start. > > I.e. it's impossible to read a value inserted by a thick client with java > thin client without specifying compactFooter=true -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-8038) DynamicColumnsConcurrentTransactionalPartitionedSelfTest#testDropColumnCoordinatorChange is flaky
[
https://issues.apache.org/jira/browse/IGNITE-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Pavlov resolved IGNITE-8038.
---
Resolution: Cannot Reproduce
The issue seems to be not actual. Tests passed, resolving as can't reproduce.
> DynamicColumnsConcurrentTransactionalPartitionedSelfTest#testDropColumnCoordinatorChange
> is flaky
> -
>
> Key: IGNITE-8038
> URL: https://issues.apache.org/jira/browse/IGNITE-8038
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
>
> Test fails on TC as well as locally with the following error:
> {noformat}
> SchemaOperationException [code=1, msg=Cache doesn't exist: SQL_PUBLIC_PERSON
> ]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processSchemaOperationLocal(GridQueryProcessor.java:1419)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaOperationWorker.body(SchemaOperationWorker.java:108)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745){noformat}
> No other important exceptions are in the log.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (IGNITE-9813) Unstable behaviour in GridQueryProcessor#processSchemaOperationLocal. Node stop must be checked
[
https://issues.apache.org/jira/browse/IGNITE-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Pavlov resolved IGNITE-9813.
---
Release Note: The issue seems to be not actual. Tests passed, resolving as
can't reproduce.
Resolution: Cannot Reproduce
> Unstable behaviour in GridQueryProcessor#processSchemaOperationLocal. Node
> stop must be checked
> ---
>
> Key: IGNITE-9813
> URL: https://issues.apache.org/jira/browse/IGNITE-9813
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.6
>Reporter: Taras Ledkov
>Assignee: Aleksandr
>Priority: Major
> Labels: newbie, stability
>
> The test
> {{DynamicColumnsAbstractConcurrentSelfTest#testDropColumnCoordinatorChange}}
> periodically fails with exception {{SchemaOperationException: cache not
> found}}
> because we don't check the node state at the
> {{GridQueryProcessor#processSchemaOperationLocal}}. The node's stop must be
> checked here (e.g. by {{GridQueryProcessor#busyLock}}).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17162) Fix init cluster command options
[ https://issues.apache.org/jira/browse/IGNITE-17162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev updated IGNITE-17162: -- Description: Currently "cluster init" command uses --node-endpoint option which requires passing endpoint without the URL schema. It should use --cluster-url option as stated in the IEP. was: Now "ignite status" will display the status based on local running nodes and some hacks. There should be a special endpoint to get the cluster status. CLI should call this endpoint. * create a REST endpoint * Implement status command based on new endpoint The status command has to display at least: a cluster name, a number of nodes, initialized/not initialized. > Fix init cluster command options > > > Key: IGNITE-17162 > URL: https://issues.apache.org/jira/browse/IGNITE-17162 > Project: Ignite > Issue Type: Task >Reporter: Vadim Pakhnushev >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > Currently "cluster init" command uses --node-endpoint option which requires > passing endpoint without the URL schema. > It should use --cluster-url option as stated in the IEP. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17162) Fix init cluster command options
Vadim Pakhnushev created IGNITE-17162: - Summary: Fix init cluster command options Key: IGNITE-17162 URL: https://issues.apache.org/jira/browse/IGNITE-17162 Project: Ignite Issue Type: Task Reporter: Vadim Pakhnushev Now "ignite status" will display the status based on local running nodes and some hacks. There should be a special endpoint to get the cluster status. CLI should call this endpoint. * create a REST endpoint * Implement status command based on new endpoint The status command has to display at least: a cluster name, a number of nodes, initialized/not initialized. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-14524) Historical rebalance doesn't work if cache has configured rebalanceDelay
[ https://issues.apache.org/jira/browse/IGNITE-14524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-14524: - Labels: ise (was: ) > Historical rebalance doesn't work if cache has configured rebalanceDelay > > > Key: IGNITE-14524 > URL: https://issues.apache.org/jira/browse/IGNITE-14524 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Dmitry Lazurkin >Priority: Major > Labels: ise > > I have big cache with configured rebalanceMode = ASYNC, rebalanceDelay = > 10_000ms. Persistence is enabled, maxWalArchiveSize = 10GB. And I passed > -DIGNITE_PREFER_WAL_REBALANCE=true and -DIGNITE_PDS_WAL_REBALANCE_THRESHOLD=1 > to Ignite. So node should use historical rebalance if there is enough WAL. > But it doesn't. After investigation I found that > GridDhtPreloader#generateAssignments always get called with exchFut = null, > and this method can't set histPartitions without exchFut. I think, that > problem in GridCachePartitionExchangeManager > (https://github.com/apache/ignite/blob/bc24f6baf3e9b4f98cf98cc5df67fb5deb5ceb6c/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCachePartitionExchangeManager.java#L3486). > It doesn't call generateAssignments without forcePreload if rebalanceDelay > is configured. > Historical rebalance works after removing rebalanceDelay. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17161) index-reader contains repeated stack trace
[
https://issues.apache.org/jira/browse/IGNITE-17161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov reassigned IGNITE-17161:
Assignee: Nikolay Izhikov
> index-reader contains repeated stack trace
> --
>
> Key: IGNITE-17161
> URL: https://issues.apache.org/jira/browse/IGNITE-17161
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
>
> index-reader log looks a bit overwhelmed.
> The same stack trace repeated 40k times with the only difference in pageId.
> It seems we can keep one line for each error and don't repeat whole stack
> trace.
> {noformat}
> ---These pages types were encountered during sequential scan:
> TrackingPageIO: 61
> PageMetaIOV2: 1
> InlineInnerIO: 50885
> MetaStoreLeafIO: 47
> BPlusMetaIO: 170
> PagesListNodeIO: 1671
> MetaStoreInnerIO: 15
> InlineLeafIO: 928993
> PagesListMetaIO: 1
> ---
> Errors:
> class org.apache.ignite.IgniteException: Exception occurred on step 271:
> Possibly orphan InlineInnerIO page, pageId=844420635164943
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373)
> Caused by: class org.apache.ignite.IgniteException: Possibly orphan
> InlineInnerIO page, pageId=844420635164943
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554)
> ... 4 more
> class org.apache.ignite.IgniteException: Exception occurred on step 981775:
> Possibly orphan InlineInnerIO page, pageId=844420636146447
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373)
> Caused by: class org.apache.ignite.IgniteException: Possibly orphan
> InlineInnerIO page, pageId=844420636146447
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554)
> ... 4 more
> ...
> class org.apache.ignite.IgniteException: Exception occurred on step 981790:
> Possibly orphan InlineInnerIO page, pageId=844420636146462
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373)
> Caused by: class org.apache.ignite.IgniteException: Possibly orphan
> InlineInnerIO page, pageId=844420636146462
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554)
> ... 4 more
> ---
> Total pages encountered during sequential scan: 981844
> Total errors occurred during sequential scan: 44853
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17161) index-reader contains repeated stack trace
[
https://issues.apache.org/jira/browse/IGNITE-17161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-17161:
-
Priority: Minor (was: Major)
> index-reader contains repeated stack trace
> --
>
> Key: IGNITE-17161
> URL: https://issues.apache.org/jira/browse/IGNITE-17161
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Priority: Minor
>
> index-reader log looks a bit overwhelmed.
> The same stack trace repeated 40k times with the only difference in pageId.
> It seems we can keep one line for each error and don't repeat whole stack
> trace.
> {noformat}
> ---These pages types were encountered during sequential scan:
> TrackingPageIO: 61
> PageMetaIOV2: 1
> InlineInnerIO: 50885
> MetaStoreLeafIO: 47
> BPlusMetaIO: 170
> PagesListNodeIO: 1671
> MetaStoreInnerIO: 15
> InlineLeafIO: 928993
> PagesListMetaIO: 1
> ---
> Errors:
> class org.apache.ignite.IgniteException: Exception occurred on step 271:
> Possibly orphan InlineInnerIO page, pageId=844420635164943
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373)
> Caused by: class org.apache.ignite.IgniteException: Possibly orphan
> InlineInnerIO page, pageId=844420635164943
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554)
> ... 4 more
> class org.apache.ignite.IgniteException: Exception occurred on step 981775:
> Possibly orphan InlineInnerIO page, pageId=844420636146447
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373)
> Caused by: class org.apache.ignite.IgniteException: Possibly orphan
> InlineInnerIO page, pageId=844420636146447
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554)
> ... 4 more
> class org.apache.ignite.IgniteException: Exception occurred on step 981790:
> Possibly orphan InlineInnerIO page, pageId=844420636146462
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373)
> Caused by: class org.apache.ignite.IgniteException: Possibly orphan
> InlineInnerIO page, pageId=844420636146462
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417)
> at
> org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554)
> ... 4 more
> ---
> Total pages encountered during sequential scan: 981844
> Total errors occurred during sequential scan: 44853
> {nofomrat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-16920) Calcite Engine. COUNT(*) lacks trivial optimization.
[ https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-16920: -- Summary: Calcite Engine. COUNT(*) lacks trivial optimization. (was: Calcite Engine. COUNT() lacks trivial optimization.) > Calcite Engine. COUNT(*) lacks trivial optimization. > > > Key: IGNITE-16920 > URL: https://issues.apache.org/jira/browse/IGNITE-16920 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.13 >Reporter: YuJue Li >Assignee: Vladimir Steshin >Priority: Major > Labels: calcite2-required, calcite3-required > Fix For: 2.14 > > Attachments: PI_COM_DAY.sql, example-calcite.xml, > image-2022-05-01-13-35-59-275.png > > Time Spent: 10m > Remaining Estimate: 0h > > !image-2022-05-01-13-35-59-275.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17161) index-reader contains repeated stack trace
Nikolay Izhikov created IGNITE-17161:
Summary: index-reader contains repeated stack trace
Key: IGNITE-17161
URL: https://issues.apache.org/jira/browse/IGNITE-17161
Project: Ignite
Issue Type: Improvement
Reporter: Nikolay Izhikov
index-reader log looks a bit overwhelmed.
The same stack trace repeated 40k times with the only difference in pageId.
It seems we can keep one line for each error and don't repeat whole stack trace.
{noformat}
---These pages types were encountered during sequential scan:
TrackingPageIO: 61
PageMetaIOV2: 1
InlineInnerIO: 50885
MetaStoreLeafIO: 47
BPlusMetaIO: 170
PagesListNodeIO: 1671
MetaStoreInnerIO: 15
InlineLeafIO: 928993
PagesListMetaIO: 1
---
Errors:
class org.apache.ignite.IgniteException: Exception occurred on step 271:
Possibly orphan InlineInnerIO page, pageId=844420635164943
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373)
Caused by: class org.apache.ignite.IgniteException: Possibly orphan
InlineInnerIO page, pageId=844420635164943
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554)
... 4 more
class org.apache.ignite.IgniteException: Exception occurred on step 981775:
Possibly orphan InlineInnerIO page, pageId=844420636146447
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373)
Caused by: class org.apache.ignite.IgniteException: Possibly orphan
InlineInnerIO page, pageId=844420636146447
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554)
... 4 more
class org.apache.ignite.IgniteException: Exception occurred on step 981790:
Possibly orphan InlineInnerIO page, pageId=844420636146462
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373)
Caused by: class org.apache.ignite.IgniteException: Possibly orphan
InlineInnerIO page, pageId=844420636146462
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554)
... 4 more
---
Total pages encountered during sequential scan: 981844
Total errors occurred during sequential scan: 44853
{nofomrat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17161) index-reader contains repeated stack trace
[
https://issues.apache.org/jira/browse/IGNITE-17161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-17161:
-
Description:
index-reader log looks a bit overwhelmed.
The same stack trace repeated 40k times with the only difference in pageId.
It seems we can keep one line for each error and don't repeat whole stack trace.
{noformat}
---These pages types were encountered during sequential scan:
TrackingPageIO: 61
PageMetaIOV2: 1
InlineInnerIO: 50885
MetaStoreLeafIO: 47
BPlusMetaIO: 170
PagesListNodeIO: 1671
MetaStoreInnerIO: 15
InlineLeafIO: 928993
PagesListMetaIO: 1
---
Errors:
class org.apache.ignite.IgniteException: Exception occurred on step 271:
Possibly orphan InlineInnerIO page, pageId=844420635164943
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373)
Caused by: class org.apache.ignite.IgniteException: Possibly orphan
InlineInnerIO page, pageId=844420635164943
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554)
... 4 more
class org.apache.ignite.IgniteException: Exception occurred on step 981775:
Possibly orphan InlineInnerIO page, pageId=844420636146447
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373)
Caused by: class org.apache.ignite.IgniteException: Possibly orphan
InlineInnerIO page, pageId=844420636146447
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554)
... 4 more
...
class org.apache.ignite.IgniteException: Exception occurred on step 981790:
Possibly orphan InlineInnerIO page, pageId=844420636146462
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373)
Caused by: class org.apache.ignite.IgniteException: Possibly orphan
InlineInnerIO page, pageId=844420636146462
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417)
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554)
... 4 more
---
Total pages encountered during sequential scan: 981844
Total errors occurred during sequential scan: 44853
{noformat}
was:
index-reader log looks a bit overwhelmed.
The same stack trace repeated 40k times with the only difference in pageId.
It seems we can keep one line for each error and don't repeat whole stack trace.
{noformat}
---These pages types were encountered during sequential scan:
TrackingPageIO: 61
PageMetaIOV2: 1
InlineInnerIO: 50885
MetaStoreLeafIO: 47
BPlusMetaIO: 170
PagesListNodeIO: 1671
MetaStoreInnerIO: 15
InlineLeafIO: 928993
PagesListMetaIO: 1
---
Errors:
class org.apache.ignite.IgniteException: Exception occurred on step 271:
Possibly orphan InlineInnerIO page, pageId=844420635164943
at
org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560)
at
[jira] [Resolved] (IGNITE-17160) Minor improvements in index-reader
[ https://issues.apache.org/jira/browse/IGNITE-17160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov resolved IGNITE-17160. -- Resolution: Fixed > Minor improvements in index-reader > -- > > Key: IGNITE-17160 > URL: https://issues.apache.org/jira/browse/IGNITE-17160 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Priority: Trivial > Time Spent: 20m > Remaining Estimate: 0h > > Code of index reader contains many compiler and IDE warnings that can be > easily fixed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17160) Minor improvements in index-reader
[ https://issues.apache.org/jira/browse/IGNITE-17160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-17160: - Fix Version/s: 2.14 > Minor improvements in index-reader > -- > > Key: IGNITE-17160 > URL: https://issues.apache.org/jira/browse/IGNITE-17160 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Priority: Trivial > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Code of index reader contains many compiler and IDE warnings that can be > easily fixed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17160) Minor improvements in index-reader
Nikolay Izhikov created IGNITE-17160: Summary: Minor improvements in index-reader Key: IGNITE-17160 URL: https://issues.apache.org/jira/browse/IGNITE-17160 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov Code of index reader contains many compiler and IDE warnings that can be easily fixed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-17138) IndexKeyFactory can't register custom index types
[
https://issues.apache.org/jira/browse/IGNITE-17138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov resolved IGNITE-17138.
Resolution: Fixed
[~mmuzaf], thanks for the review, merged to master.
> IndexKeyFactory can't register custom index types
> -
>
> Key: IGNITE-17138
> URL: https://issues.apache.org/jira/browse/IGNITE-17138
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.14
>Reporter: Maxim Muzafarov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code}
> [14:57:27][Step 3/3] symbol: method register(int,(k)->new G[...]ry)k))
> [14:57:27][Step 3/3] location: class
> org.apache.ignite.internal.cache.query.index.sorted.keys.IndexKeyFactory
> [14:57:27][Step 3/3] [INFO] 1 error
> [14:57:27][Step 3/3] [INFO]
> -
> [14:57:27][Step 3/3] Compiler
> [14:57:27][Compiler] Compilation failure
> /opt/buildagent/work/9319dd66c384518/modules/geospatial-ext/geospatial/src/main/java/org/apache/ignite/internal/processors/query/h2/opt/GeoSpatialUtils.java:[45,24]
> cannot find symbol
> symbol: method register(int,(k)->new G[...]ry)k))
> location: class
> org.apache.ignite.internal.cache.query.index.sorted.keys.IndexKeyFactory
> [14:57:27][Step 3/3] [INFO]
>
> [14:57:27][Step 3/3] [INFO] Reactor Summary for
> ignite-geospatial-parent-ext 1.0.0-SNAPSHOT:
> [14:57:27][Step 3/3] [INFO]
> [14:57:27][Step 3/3] [INFO] ignite-geospatial-parent-ext
> ... SUCCESS [ 3.145 s]
> [14:57:27][Step 3/3] [INFO] ignite-geospatial-ext
> .. FAILURE [ 3.208 s]
> [14:57:27][Step 3/3] [INFO] ignite-geospatial-ext-examples
> . SKIPPED
> [14:57:27][Step 3/3] [INFO]
>
> [14:57:27][Step 3/3] [INFO] BUILD FAILURE
> [14:57:27][Step 3/3] [INFO]
>
> [14:57:27][Step 3/3] [INFO] Total time: 7.728 s
> [14:57:27][Step 3/3] [INFO] Finished at: 2022-06-07T14:57:27+03:00
> [14:57:27][Step 3/3] [INFO]
>
> [14:57:27][Step 3/3] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile
> (default-compile) on project ignite-geospatial-ext: Compilation failure
> [14:57:27][Step 3/3] [ERROR]
> /opt/buildagent/work/9319dd66c384518/modules/geospatial-ext/geospatial/src/main/java/org/apache/ignite/internal/processors/query/h2/opt/GeoSpatialUtils.java:[45,24]
> cannot find symbol
> {code}
> https://ci.ignite.apache.org/viewLog.html?buildId=6615340=IgniteExtensions_Tests_Geospatial=buildLog
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17138) IndexKeyFactory can't register custom index types
[
https://issues.apache.org/jira/browse/IGNITE-17138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554087#comment-17554087
]
Ignite TC Bot commented on IGNITE-17138:
{panel:title=Branch: [pull/10089/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10089/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: Basic Tests*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6626748buildTypeId=IgniteTests24Java8_RunBasicTests]
> IndexKeyFactory can't register custom index types
> -
>
> Key: IGNITE-17138
> URL: https://issues.apache.org/jira/browse/IGNITE-17138
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.14
>Reporter: Maxim Muzafarov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> [14:57:27][Step 3/3] symbol: method register(int,(k)->new G[...]ry)k))
> [14:57:27][Step 3/3] location: class
> org.apache.ignite.internal.cache.query.index.sorted.keys.IndexKeyFactory
> [14:57:27][Step 3/3] [INFO] 1 error
> [14:57:27][Step 3/3] [INFO]
> -
> [14:57:27][Step 3/3] Compiler
> [14:57:27][Compiler] Compilation failure
> /opt/buildagent/work/9319dd66c384518/modules/geospatial-ext/geospatial/src/main/java/org/apache/ignite/internal/processors/query/h2/opt/GeoSpatialUtils.java:[45,24]
> cannot find symbol
> symbol: method register(int,(k)->new G[...]ry)k))
> location: class
> org.apache.ignite.internal.cache.query.index.sorted.keys.IndexKeyFactory
> [14:57:27][Step 3/3] [INFO]
>
> [14:57:27][Step 3/3] [INFO] Reactor Summary for
> ignite-geospatial-parent-ext 1.0.0-SNAPSHOT:
> [14:57:27][Step 3/3] [INFO]
> [14:57:27][Step 3/3] [INFO] ignite-geospatial-parent-ext
> ... SUCCESS [ 3.145 s]
> [14:57:27][Step 3/3] [INFO] ignite-geospatial-ext
> .. FAILURE [ 3.208 s]
> [14:57:27][Step 3/3] [INFO] ignite-geospatial-ext-examples
> . SKIPPED
> [14:57:27][Step 3/3] [INFO]
>
> [14:57:27][Step 3/3] [INFO] BUILD FAILURE
> [14:57:27][Step 3/3] [INFO]
>
> [14:57:27][Step 3/3] [INFO] Total time: 7.728 s
> [14:57:27][Step 3/3] [INFO] Finished at: 2022-06-07T14:57:27+03:00
> [14:57:27][Step 3/3] [INFO]
>
> [14:57:27][Step 3/3] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile
> (default-compile) on project ignite-geospatial-ext: Compilation failure
> [14:57:27][Step 3/3] [ERROR]
> /opt/buildagent/work/9319dd66c384518/modules/geospatial-ext/geospatial/src/main/java/org/apache/ignite/internal/processors/query/h2/opt/GeoSpatialUtils.java:[45,24]
> cannot find symbol
> {code}
> https://ci.ignite.apache.org/viewLog.html?buildId=6615340=IgniteExtensions_Tests_Geospatial=buildLog
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-16967) SQL API: Implement server-side query context.
[ https://issues.apache.org/jira/browse/IGNITE-16967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554084#comment-17554084 ] Andrey Mashenkov commented on IGNITE-16967: --- [~korlov], I've left few comments to the PR. > SQL API: Implement server-side query context. > - > > Key: IGNITE-16967 > URL: https://issues.apache.org/jira/browse/IGNITE-16967 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > Implement server-side session management. > Avoid session parameters sending on each query start. > Close session on client disconnect. > Close queries when session has been closed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17109) Error handling for invalid url passed to any command
[
https://issues.apache.org/jira/browse/IGNITE-17109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554073#comment-17554073
]
Vadim Pakhnushev commented on IGNITE-17109:
---
After the IGNITE-17093, first two messages would be:
{code:java}
Expected URL scheme 'http' or 'https' but no colon was found {code}
and
{code:java}
Could not determine IP address when connecting to URL:
http://thsjdfksjdfkjd:10300 {code}
> Error handling for invalid url passed to any command
>
>
> Key: IGNITE-17109
> URL: https://issues.apache.org/jira/browse/IGNITE-17109
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3
>
> h2. Description
> Different commands given the wrong URL display different messages. For example
>
> {code:java}
> disconnected]> connect lkhjasdflkjhhasdf
> 2022-06-06 10:41:04:665 +0100 [ERROR][main][ExceptionHandler] Unhandled
> exception
> java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but
> no colon was found
> at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1260)
> at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1633)
> at okhttp3.Request$Builder.url(Request.kt:184)
> ...
> Internal error! {code}
>
> {code:java}
> [disconnected]> connect http://kjhasdflkjhhasdf:10300/
> Api error: null
> {code}
>
> {code:java}
> [disconnected]> sql -u=hdbkljghhgasdflkjhasdf
> Connection failed. {code}
> h2. To-Do
> * Test all possible variations of incorrect URLs with integration/interface
> tests
> * Define a single error handler for the wrong URL, port, etc.
> As a result, all variations of wrong data passed should be handled on a
> consistent way. The user has to see the same messages for the same mistakes
> regardless of the command is used.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17142) Docs: Review the AI 3.0.0 Alpha 5 documentation
[ https://issues.apache.org/jira/browse/IGNITE-17142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-17142: - Labels: docuentation documentaion documentation ignite-3 (was: docuentation documentaion documentation) > Docs: Review the AI 3.0.0 Alpha 5 documentation > --- > > Key: IGNITE-17142 > URL: https://issues.apache.org/jira/browse/IGNITE-17142 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 3.0.0-alpha5 >Reporter: Nikita A. Safonov >Assignee: Nikita A. Safonov >Priority: Major > Labels: docuentation, documentaion, documentation, ignite-3 > Fix For: 3.0.0-alpha5 > > > We need to check the new sections throughout the documentation. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17142) Docs: Review the AI 3.0.0 Alpha 5 documentation
[ https://issues.apache.org/jira/browse/IGNITE-17142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-17142: - Labels: documentation ignite-3 (was: docuentation documentaion documentation ignite-3) > Docs: Review the AI 3.0.0 Alpha 5 documentation > --- > > Key: IGNITE-17142 > URL: https://issues.apache.org/jira/browse/IGNITE-17142 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 3.0.0-alpha5 >Reporter: Nikita A. Safonov >Assignee: Nikita A. Safonov >Priority: Major > Labels: documentation, ignite-3 > Fix For: 3.0.0-alpha5 > > > We need to check the new sections throughout the documentation. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17152) Improve logging levels for situations when dealing with a client node
[ https://issues.apache.org/jira/browse/IGNITE-17152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554066#comment-17554066 ] Roman Puchkovskiy commented on IGNITE-17152: Thank you guys! > Improve logging levels for situations when dealing with a client node > - > > Key: IGNITE-17152 > URL: https://issues.apache.org/jira/browse/IGNITE-17152 > Project: Ignite > Issue Type: Improvement > Components: networking >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > An example follows: > [2022-04-27T23:01:17,872][ERROR][query-#17069%nebula-node%][TcpCommunicationSpi] > Failed to send message to remote node [node=TcpDiscoveryNode > [id=67cf0e5e-974c-463a-a1f2-915fe3cdd3e7, consistentId=67cf0e5e-974c- > 2463a-a1f2-915fe3cdd3e7, addrs=ArrayList [0:0:0:0:0:0:0:1%lo0, 127.0.0.1, > 127.94.0.1, 192.168.1.35], sockAddrs=HashSet [/127.0.0.1:0, > 0:0:0:0:0:0:0:1%lo0:0, /192.168.1.35:0, /127.94.0.1:0], discPort=0, order=25, > 3intOrder=15, lastExchangeTime=1651100317979, loc=false, > ver=8.8.14#20220124-sha1:53de42db, isClient=true], msg=GridIoMessage [plc=10, > topic=TOPIC_QUERY, topicOrd=19, ordered=false, timeout=0, skipOnTimeout=false > 4, msg=GridQueryFailResponse [qryReqId=1, errMsg=Failed to wait for > establishing inverse connection (node left topology): > 67cf0e5e-974c-463a-a1f2-915fe3cdd3e7, failCode=0, sqlErrCode=0]]] > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed to > wait for establishing inverse connection (node left topology): > 67cf0e5e-974c-463a-a1f2-915fe3cdd3e7 > Here, a client has left the topology, hence we were not able to send it some > message. The resulting problem is not the server internal problem, it is just > a consequence of a client leaving (which is normal). So in this case the > problem should not be logged as an ERROR to avoid too much noise in the log. > > Another similar log is > [2022-04-27T23:01:17,872][ERROR][query-#17069%xxx-node%][GridMapQueryExecutor] > Failed to send error message. > 2org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed > to wait for establishing inverse connection (node left topology): > 67cf0e5e-974c-463a-a1f2-915fe3cdd3e7 3 > > Here, an error message was tried to be sent to a client, but it has already > left. Similar reasoning implies that we should not log at as ERROR. > > One more situation is demonstrated by the following log: > [2022-05-16T16:43:51,301][ERROR][sys-#51%xxx-node%][TcpCommunicationSpi] > Failed to send message to remote node [node=TcpDiscoveryNode > [id=68e268f7-abf2-41a1-a4fa-520169d2dac5, > consistentId=68e268f7-abf2-41a1-a4fa-520169d2dac5, addrs=ArrayList > 2[0:0:0:0:0:0:0:1%lo0, 127.0.0.1, 127.94.0.1, 192.168.1.170], > sockAddrs=HashSet [/127.0.0.1:0, 0:0:0:0:0:0:0:1%lo0:0, /192.168.1.170:0, > /127.94.0.1:0], discPort=0, order=79, intOrder=44, > lastExchangeTime=1652719430974, loc=false, ver=8.8.14#202201 > 324-sha1:53de42db, isClient=true], msg=GridIoMessage [plc=0, > topic=TOPIC_COMM_USER, topicOrd=9, ordered=true, timeout=5000, > skipOnTimeout=true, msg=GridIoUserMessage [clsLdrId=null, depMode=null, > depClsName=null, userVer=null, ldrParties=null, dep 4=null]]] > org.apache.ignite.IgniteCheckedException: Failed to connect to node > 68e268f7-abf2-41a1-a4fa-520169d2dac5 because it is started in > 'forceClientToServerConnections' mode; inverse connection will be requested. > > Here, the exception is not a problem at all, it's just used for flow control, > and it should not be logged at ERROR as well. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17070) [TEST] Fix flaky IgniteCacheTopologyValidatorTest#testSplitWithBaseline test.
[ https://issues.apache.org/jira/browse/IGNITE-17070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-17070: - Fix Version/s: 2.14 > [TEST] Fix flaky IgniteCacheTopologyValidatorTest#testSplitWithBaseline test. > - > > Key: IGNITE-17070 > URL: https://issues.apache.org/jira/browse/IGNITE-17070 > Project: Ignite > Issue Type: Test > Components: extensions >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Fix For: 2.14 > > > IgniteCacheTopologyValidatorTest#testSplitWithBaseline is flaky we need to > fix it. > https://ci.ignite.apache.org/project.html?projectId=IgniteExtensions_Tests=-4574202048063239300=testDetails > The main problem here is that rebalance of test keys could take more then 30 > seconds to complete. 30 seconds is a timeout that is used by > awaitPartitionMapExchange method in which assertion is arised. > The proposed solution - to decrease the number of test keys. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17150) Add ENCRYPTED_OUT_OF_ORDER_UPDATE WAL record type placeholder
[
https://issues.apache.org/jira/browse/IGNITE-17150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554060#comment-17554060
]
Ignite TC Bot commented on IGNITE-17150:
{panel:title=Branch: [pull/10081/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10081/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6620846buildTypeId=IgniteTests24Java8_RunAll]
> Add ENCRYPTED_OUT_OF_ORDER_UPDATE WAL record type placeholder
> -
>
> Key: IGNITE-17150
> URL: https://issues.apache.org/jira/browse/IGNITE-17150
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Minor
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Reserve new WAL type for encrypted OUT_OF_ORDER_UPDATE record.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17122) Failed to release WAL segments even after reaching DataStorageConfiguration#maxWalArchiveSize
[ https://issues.apache.org/jira/browse/IGNITE-17122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554058#comment-17554058 ] Kirill Tkalenko commented on IGNITE-17122: -- [~marcus.lo] Please add: * Configuration *org.apache.ignite.configuration.DataStorageConfiguration* in xml format; * More logs, at least to include information about checkpoints. > Failed to release WAL segments even after reaching > DataStorageConfiguration#maxWalArchiveSize > - > > Key: IGNITE-17122 > URL: https://issues.apache.org/jira/browse/IGNITE-17122 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.13 >Reporter: Marcus Lo >Priority: Major > Attachments: 1654590690_34713_920D9DE6-1C3F-4E8B-8181-446CB340ACF3.txt > > > When maxWalArchiveSize is reached, Ignite is able to detect that and tries to > release WAL segments (and prints out "maximum size of the WAL archive > exceeded, the segments will be forcibly released"). However the WAL archive > deletion doesn't happens immediately, and sometimes it happens almost 1 hour > after the first detection, and the actual WAL archive size is much larger > than the maxWalArchiveSize. See the (trimmed) attached log for an example. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17152) Improve logging levels for situations when dealing with a client node
[ https://issues.apache.org/jira/browse/IGNITE-17152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554051#comment-17554051 ] Kirill Tkalenko commented on IGNITE-17152: -- [~rpuch] Looks good to me. > Improve logging levels for situations when dealing with a client node > - > > Key: IGNITE-17152 > URL: https://issues.apache.org/jira/browse/IGNITE-17152 > Project: Ignite > Issue Type: Improvement > Components: networking >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > An example follows: > [2022-04-27T23:01:17,872][ERROR][query-#17069%nebula-node%][TcpCommunicationSpi] > Failed to send message to remote node [node=TcpDiscoveryNode > [id=67cf0e5e-974c-463a-a1f2-915fe3cdd3e7, consistentId=67cf0e5e-974c- > 2463a-a1f2-915fe3cdd3e7, addrs=ArrayList [0:0:0:0:0:0:0:1%lo0, 127.0.0.1, > 127.94.0.1, 192.168.1.35], sockAddrs=HashSet [/127.0.0.1:0, > 0:0:0:0:0:0:0:1%lo0:0, /192.168.1.35:0, /127.94.0.1:0], discPort=0, order=25, > 3intOrder=15, lastExchangeTime=1651100317979, loc=false, > ver=8.8.14#20220124-sha1:53de42db, isClient=true], msg=GridIoMessage [plc=10, > topic=TOPIC_QUERY, topicOrd=19, ordered=false, timeout=0, skipOnTimeout=false > 4, msg=GridQueryFailResponse [qryReqId=1, errMsg=Failed to wait for > establishing inverse connection (node left topology): > 67cf0e5e-974c-463a-a1f2-915fe3cdd3e7, failCode=0, sqlErrCode=0]]] > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed to > wait for establishing inverse connection (node left topology): > 67cf0e5e-974c-463a-a1f2-915fe3cdd3e7 > Here, a client has left the topology, hence we were not able to send it some > message. The resulting problem is not the server internal problem, it is just > a consequence of a client leaving (which is normal). So in this case the > problem should not be logged as an ERROR to avoid too much noise in the log. > > Another similar log is > [2022-04-27T23:01:17,872][ERROR][query-#17069%xxx-node%][GridMapQueryExecutor] > Failed to send error message. > 2org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed > to wait for establishing inverse connection (node left topology): > 67cf0e5e-974c-463a-a1f2-915fe3cdd3e7 3 > > Here, an error message was tried to be sent to a client, but it has already > left. Similar reasoning implies that we should not log at as ERROR. > > One more situation is demonstrated by the following log: > [2022-05-16T16:43:51,301][ERROR][sys-#51%xxx-node%][TcpCommunicationSpi] > Failed to send message to remote node [node=TcpDiscoveryNode > [id=68e268f7-abf2-41a1-a4fa-520169d2dac5, > consistentId=68e268f7-abf2-41a1-a4fa-520169d2dac5, addrs=ArrayList > 2[0:0:0:0:0:0:0:1%lo0, 127.0.0.1, 127.94.0.1, 192.168.1.170], > sockAddrs=HashSet [/127.0.0.1:0, 0:0:0:0:0:0:0:1%lo0:0, /192.168.1.170:0, > /127.94.0.1:0], discPort=0, order=79, intOrder=44, > lastExchangeTime=1652719430974, loc=false, ver=8.8.14#202201 > 324-sha1:53de42db, isClient=true], msg=GridIoMessage [plc=0, > topic=TOPIC_COMM_USER, topicOrd=9, ordered=true, timeout=5000, > skipOnTimeout=true, msg=GridIoUserMessage [clsLdrId=null, depMode=null, > depClsName=null, userVer=null, ldrParties=null, dep 4=null]]] > org.apache.ignite.IgniteCheckedException: Failed to connect to node > 68e268f7-abf2-41a1-a4fa-520169d2dac5 because it is started in > 'forceClientToServerConnections' mode; inverse connection will be requested. > > Here, the exception is not a problem at all, it's just used for flow control, > and it should not be logged at ERROR as well. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17141) Use Maven to build .NET
[ https://issues.apache.org/jira/browse/IGNITE-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554041#comment-17554041 ] Maxim Muzafarov commented on IGNITE-17141: -- [~ptupitsyn] I've fixed all comments according to your suggestion. Please, take a look. I've also updated DEVNOTES. > Use Maven to build .NET > --- > > Key: IGNITE-17141 > URL: https://issues.apache.org/jira/browse/IGNITE-17141 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 0.5h > Remaining Estimate: 0h > > It seems we can build the .NET using maven + maven-ant-plugin. This will > simplify the Apache Ignite release build distribution and will add a single > build point for the whole release. > Discussion: > https://lists.apache.org/thread/9os553vhcryko1jlfzywmx977o6lyor5 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17159) Server node failed due to java.lang.AssertionError: Client already created
[
https://issues.apache.org/jira/browse/IGNITE-17159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semyon Danilov updated IGNITE-17159:
Description:
It seems like we release recovery descriptor prior to removing communication
client from the connection pool. So another thread successfully reserves
descriptor, creates a client and tries to put a newly created client into the
pool and fails because there is a stale client which we didn’t remove yet. I
think we should release descriptor AFTER we remove communication client and it
should fix the issue.
{noformat}
at
org.apache.ignite.spi.communication.tcp.internal.ConnectionClientPool.addNodeClient(ConnectionClientPool.java:638)
at
org.apache.ignite.spi.communication.tcp.internal.ConnectionClientPool.reserveClient(ConnectionClientPool.java:242)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1174)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1123)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1817)
at
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1944)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1265)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1304)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.sendDhtRequests(GridDhtAtomicAbstractUpdateFuture.java:489)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:445)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1921)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1685)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:319)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:496)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:454)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:267)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1164)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:627)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2073)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2048)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1311)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:817)
at
com.autozone.supplychain.csr.receiver.QuantityCacheTupleReceiver.processRecord(QuantityCacheTupleReceiver.java:123)
at
com.autozone.supplychain.csr.receiver.QuantityCacheTupleReceiver.receive(QuantityCacheTupleReceiver.java:47)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:401)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:306)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:59)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:89)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1727)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1334)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4800(GridIoManager.java:158)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.execute(GridIoManager.java:1218)
at
org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:54)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:567)
at
[jira] [Created] (IGNITE-17159) Server node failed due to java.lang.AssertionError: Client already created
Semyon Danilov created IGNITE-17159:
---
Summary: Server node failed due to java.lang.AssertionError:
Client already created
Key: IGNITE-17159
URL: https://issues.apache.org/jira/browse/IGNITE-17159
Project: Ignite
Issue Type: Bug
Components: networking
Reporter: Semyon Danilov
Assignee: Semyon Danilov
{noformat}
at
org.apache.ignite.spi.communication.tcp.internal.ConnectionClientPool.addNodeClient(ConnectionClientPool.java:638)
at
org.apache.ignite.spi.communication.tcp.internal.ConnectionClientPool.reserveClient(ConnectionClientPool.java:242)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1174)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1123)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1817)
at
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1944)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1265)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1304)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.sendDhtRequests(GridDhtAtomicAbstractUpdateFuture.java:489)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:445)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1921)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1685)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:319)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:496)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:454)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:267)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1164)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:627)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2073)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2048)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1311)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:817)
at
com.autozone.supplychain.csr.receiver.QuantityCacheTupleReceiver.processRecord(QuantityCacheTupleReceiver.java:123)
at
com.autozone.supplychain.csr.receiver.QuantityCacheTupleReceiver.receive(QuantityCacheTupleReceiver.java:47)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:401)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:306)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:59)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:89)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1727)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1334)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4800(GridIoManager.java:158)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.execute(GridIoManager.java:1218)
at
org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:54)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:567)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at java.lang.Thread.run(Thread.java:750)
{noformat}
--
This message was sent by Atlassian Jira
[jira] [Updated] (IGNITE-12404) .NET: Adopt nullable reference types
[ https://issues.apache.org/jira/browse/IGNITE-12404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-12404: Labels: .NET (was: .NET ignite-3) > .NET: Adopt nullable reference types > > > Key: IGNITE-12404 > URL: https://issues.apache.org/jira/browse/IGNITE-12404 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Critical > Labels: .NET > Original Estimate: 40h > Remaining Estimate: 40h > > .NET 5 is due on November 2020. Microsoft recommends adopting nullable > annotations on public APIs before that date to all library authors: > * https://devblogs.microsoft.com/dotnet/embracing-nullable-reference-types/ > * https://stu.dev/csharp8-doing-unsupported-things/ > * https://www.youtube.com/watch?v=TJiLhRPgyq4=youtu.be > The adoption can be performed on any language version by using special > attributes in the source code (no binary dependency required): > https://github.com/manuelroemer/Nullable -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17123) Fix wrong update counter assignment on backup nodes for noop invoke operation.
[ https://issues.apache.org/jira/browse/IGNITE-17123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554011#comment-17554011 ] Vyacheslav Koptilin commented on IGNITE-17123: -- Hello [~amashenkov], The fix looks good to me. Thank you for your efforts! > Fix wrong update counter assignment on backup nodes for noop invoke operation. > -- > > Key: IGNITE-17123 > URL: https://issues.apache.org/jira/browse/IGNITE-17123 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Minor > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Transaction reserves partition counters on primary. > On the backup side, TxEntries must be commited with counters from the > reserved range. > However, a range of update counters, which were reserved on primary, is NOT > validated on backup. Thus means NOOP invoke operation may cause partition > counter difference on the primary and backup nodes. > 1. Let's pass NOOP result of invoke operation to the backup and avoid > incorrect partition counter change on backup nodes (see DhtTxPrepareFuture). > 2. Update counter can be assigned to TxEntry instantly on tx commit on Remote > node (for the WAL purposes) instead of allocating+iterating over a new > collection (see GridDistributedTxRemoteAdapter.commitIfLocked). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-14529) Add offline utility for analyzing indexes
[ https://issues.apache.org/jira/browse/IGNITE-14529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554009#comment-17554009 ] Nikolay Izhikov commented on IGNITE-14529: -- [~Denis Chudov] Can you, please share your drafts? We have feature request from our support - they want to analyze total/free space in each index and some similar index parameters. Seems like index-reader is a great fit to add those number. So, I have some questions about initial utility design and planning usages. > Add offline utility for analyzing indexes > - > > Key: IGNITE-14529 > URL: https://issues.apache.org/jira/browse/IGNITE-14529 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Chudov >Assignee: Denis Chudov >Priority: Major > Labels: important > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > It would be useful to have the possibility for indexes offline validation. > The utility must check that every configured index (available in MetaTree > [1]) is reachable from corresponding root page, tree structure is valid and > no orphan(unreachable) index pages are present in the index.bin persistent > page store. > [1] > org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl#getIndexNames -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17158) Get SqlFieldQueryResults columns by name
[ https://issues.apache.org/jira/browse/IGNITE-17158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surinder updated IGNITE-17158: -- Description: In current ignite version(2.11.1), when we execute SQL query , result is a list of lists where inner list is values of selected columns in order of select clause and outer list of rows fetched. Now we can read column values with zero based indices. This works well but it would be nicer to fetch column values with name. was: In current ignite version(2.11.1), when we execute SQL query , result is list if list where inner list is values of selected columns in order and outer list if rows fetched. Now we can read column values with zero based indices. This works well but it would be nicer to fetch column values with name. > Get SqlFieldQueryResults columns by name > > > Key: IGNITE-17158 > URL: https://issues.apache.org/jira/browse/IGNITE-17158 > Project: Ignite > Issue Type: New Feature > Components: sql >Affects Versions: 2.11.1 >Reporter: Surinder >Priority: Minor > > In current ignite version(2.11.1), when we execute SQL query , result is a > list of lists where inner list is values of selected columns in order of > select clause and outer list of rows fetched. > Now we can read column values with zero based indices. This works well but it > would be nicer to fetch column values with name. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17158) Get SqlFieldQueryResults columns by name
[ https://issues.apache.org/jira/browse/IGNITE-17158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surinder updated IGNITE-17158: -- Component/s: sql > Get SqlFieldQueryResults columns by name > > > Key: IGNITE-17158 > URL: https://issues.apache.org/jira/browse/IGNITE-17158 > Project: Ignite > Issue Type: New Feature > Components: sql >Affects Versions: 2.11.1 >Reporter: Surinder >Priority: Minor > > In current ignite version(2.11.1), when we execute SQL query , result is list > if list where inner list is values of selected columns in order and outer > list if rows fetched. > Now we can read column values with zero based indices. This works well but it > would be nicer to fetch column values with name. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17158) Get SqlFieldQueryResults columns by name
[ https://issues.apache.org/jira/browse/IGNITE-17158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surinder updated IGNITE-17158: -- Affects Version/s: 2.11.1 > Get SqlFieldQueryResults columns by name > > > Key: IGNITE-17158 > URL: https://issues.apache.org/jira/browse/IGNITE-17158 > Project: Ignite > Issue Type: New Feature >Affects Versions: 2.11.1 >Reporter: Surinder >Priority: Minor > > In current ignite version(2.11.1), when we execute SQL query , result is list > if list where inner list is values of selected columns in order and outer > list if rows fetched. > Now we can read column values with zero based indices. This works well but it > would be nicer to fetch column values with name. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17158) Get SqlFieldQueryResults columns by name
Surinder created IGNITE-17158: - Summary: Get SqlFieldQueryResults columns by name Key: IGNITE-17158 URL: https://issues.apache.org/jira/browse/IGNITE-17158 Project: Ignite Issue Type: New Feature Reporter: Surinder In current ignite version(2.11.1), when we execute SQL query , result is list if list where inner list is values of selected columns in order and outer list if rows fetched. Now we can read column values with zero based indices. This works well but it would be nicer to fetch column values with name. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-17145) Fix handle BinaryObjectException at the thin JDBC
[
https://issues.apache.org/jira/browse/IGNITE-17145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov resolved IGNITE-17145.
---
Resolution: Fixed
Merged to
[master|https://github.com/apache/ignite/commit/f6c434ed8153ac4dc91bef58bd9b50a8521313e9]
> Fix handle BinaryObjectException at the thin JDBC
> -
>
> Key: IGNITE-17145
> URL: https://issues.apache.org/jira/browse/IGNITE-17145
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.13
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I am trying to get enum field using sqlline, but failed with error Statement
> is closed.
> {code}
> 0: jdbc:ignite:thin://127.0.0.1> select status from nebulaclusterinfo;
> Error: Statement is closed. (state=,code=0)
> java.sql.SQLException: Statement is closed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.ensureNotClosed(JdbcThinStatement.java:950)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.getWarnings(JdbcThinStatement.java:546)
> at sqlline.Commands.execute(Commands.java:849)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1> select count(status) from nebulaclusterinfo;
> ++
> | COUNT(STATUS) |
> ++
> | 310|
> ++
> 1 row selected (0.108 seconds)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17148) Support for abstract configuration
[
https://issues.apache.org/jira/browse/IGNITE-17148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-17148:
-
Description:
*NOTE*
Description may not be complete.
*Problem*
We need the ability to create a basic configuration schema so that we can
define a common configuration schema and inherit from it with additional
configuration added.
Let's look at an example:
We need to create two configuration schemes for the PageMemory based storage
engine, they should have a common property "page size in bytes" and then they
should be different, let's sketch an example scheme.
{code:java}
public class BasePageMemoryStorageEngineConfigurationSchema {
@Value(hasDefault = true)
public int pageSize = 16 * 1024;
}
@ConfigurationRoot(rootName = "in-memory-page-memory", type = DISTRIBUTED)
public class VolatilePageMemoryStorageEngineConfigurationSchema extends
BasePageMemoryStorageEngineConfigurationSchema{
@ConfigValue
public VolatilePageMemoryDataRegionConfigurationSchema defaultRegion;
@NamedConfigValue
public VolatilePageMemoryDataRegionConfigurationSchema regions;
}
@ConfigurationRoot(rootName = "persistent-page-memory", type = DISTRIBUTED)
public class PersistentPageMemoryStorageEngineConfigurationSchema extends
BasePageMemoryStorageEngineConfigurationSchema{
@ConfigValue
public PersistentPageMemoryDataRegionConfigurationSchema defaultRegion;
@NamedConfigValue
public PersistentPageMemoryDataRegionConfigurationSchema regions;
@ConfigValue
public PageMemoryCheckpointConfigurationSchema checkpoint;
}{code}
How can we implement this at the moment:
* internal extension of the configuration: then the user will not be able to
see and change it - not suitable;
* polymorphic configuration:
** by design, we cannot create root config schemas for polymorphic config or
instances;
** by design, we can change the type of polymorphic configuration to any
instance, we do not fix its type, which does not suit us;
** by design, we cannot expose a polymorphic instance as a configuration
schema property;
** hocon will display the type of polymorphic configuration, which is not
necessary in this case and will look a little strange.
The possible options do not suit us, so I propose to add another solution.
*Proposal*
Add an abstract configuration schema from which we can inherit, add properties,
but only its heirs could be used as properties of other configurations schemas
or configuration roots. Unlike a polymorphic configuration, it will not store
and display the type in hocon, and the type cannot be changed.
The abstract configuration schema from which will be inherited will contain the
annotation {*}@AbstractConfiguration{*}, and any successor must extend it and
contain *@Config* or {*}@ConfigurationRoot{*}, consider examples:
{code:java}
@AbstractConfiguration
public class BasePageMemoryStorageEngineConfigurationSchema {
@Value(hasDefault = true)
public int pageSize = 16 * 1024;
}
@ConfigurationRoot(rootName = "in-memory-page-memory", type = DISTRIBUTED)
public class VolatilePageMemoryStorageEngineConfigurationSchema extends
BasePageMemoryStorageEngineConfigurationSchema{
@ConfigValue
public VolatilePageMemoryDataRegionConfigurationSchema defaultRegion;
@NamedConfigValue
public VolatilePageMemoryDataRegionConfigurationSchema regions;
}
@Config
public class PersistentPageMemoryStorageEngineConfigurationSchema extends
BasePageMemoryStorageEngineConfigurationSchema{
@ConfigValue
public PersistentPageMemoryDataRegionConfigurationSchema defaultRegion;
@NamedConfigValue
public PersistentPageMemoryDataRegionConfigurationSchema regions;
@ConfigValue
public PageMemoryCheckpointConfigurationSchema checkpoint;
}{code}
*Implementation notes*
# Add annotation
*org.apache.ignite.configuration.annotation.AbstractConfiguration*;
# Add processing to
*org.apache.ignite.internal.configuration.processor.Processor*;
# Add processing to
*org.apache.ignite.internal.configuration.asm.ConfigurationAsmGenerator*;
# Cover with tests.
*Further development*
* Consider the possibility and necessity of crossing with the annotation
*InternalConfiguration* and *PolymorphicConfig* in a separate ticket, at the
moment they cannot be used together in the same class (for simplicity).
was:
*NOTE*
Description may not be complete.
*Problem*
We need the ability to create a basic configuration schema so that we can
define a common configuration schema and inherit from it with additional
configuration added.
Let's look at an example:
We need to create two configuration schemes for the PageMemory based storage
engine, they should have a common property "page size in bytes" and then they
should be different, let's sketch an example scheme.
{code:java}
public class BasePageMemoryStorageEngineConfigurationSchema {
[jira] [Updated] (IGNITE-17148) Support for abstract configuration
[
https://issues.apache.org/jira/browse/IGNITE-17148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-17148:
-
Description:
*NOTE*
Description may not be complete.
*Problem*
We need the ability to create a basic configuration schema so that we can
define a common configuration schema and inherit from it with additional
configuration added.
Let's look at an example:
We need to create two configuration schemes for the PageMemory based storage
engine, they should have a common property "page size in bytes" and then they
should be different, let's sketch an example scheme.
{code:java}
public class BasePageMemoryStorageEngineConfigurationSchema {
@Value(hasDefault = true)
public int pageSize = 16 * 1024;
}
@ConfigurationRoot(rootName = "in-memory-page-memory", type = DISTRIBUTED)
public class VolatilePageMemoryStorageEngineConfigurationSchema extends
BasePageMemoryStorageEngineConfigurationSchema{
@ConfigValue
public VolatilePageMemoryDataRegionConfigurationSchema defaultRegion;
@NamedConfigValue
public VolatilePageMemoryDataRegionConfigurationSchema regions;
}
@ConfigurationRoot(rootName = "persistent-page-memory", type = DISTRIBUTED)
public class PersistentPageMemoryStorageEngineConfigurationSchema extends
BasePageMemoryStorageEngineConfigurationSchema{
@ConfigValue
public PersistentPageMemoryDataRegionConfigurationSchema defaultRegion;
@NamedConfigValue
public PersistentPageMemoryDataRegionConfigurationSchema regions;
@ConfigValue
public PageMemoryCheckpointConfigurationSchema checkpoint;
}{code}
How can we implement this at the moment:
* internal extension of the configuration: then the user will not be able to
see and change it - not suitable;
* polymorphic configuration:
** by design, we cannot create root config schemas for polymorphic config or
instances;
** by design, we can change the type of polymorphic configuration to any
instance, we do not fix its type, which does not suit us;
** by design, we cannot expose a polymorphic instance as a configuration
schema property;
** hocon will display the type of polymorphic configuration, which is not
necessary in this case and will look a little strange.
The possible options do not suit us, so I propose to add another solution.
*Proposal*
Add an abstract configuration schema from which we can inherit, add properties,
but only its heirs could be used as properties of other configurations schemas
or configuration roots. Unlike a polymorphic configuration, it will not store
and display the type in hocon, and the type cannot be changed.
The abstract configuration schema from which will be inherited will contain the
annotation {*}@AbstractConfiguration{*}, and any successor must extend it and
contain *@Config* or {*}@ConfigurationRoot{*}, consider examples:
{code:java}
@AbstractConfiguration
public class BasePageMemoryStorageEngineConfigurationSchema {
@Value(hasDefault = true)
public int pageSize = 16 * 1024;
}
@ConfigurationRoot(rootName = "in-memory-page-memory", type = DISTRIBUTED)
public class VolatilePageMemoryStorageEngineConfigurationSchema extends
BasePageMemoryStorageEngineConfigurationSchema{
@ConfigValue
public VolatilePageMemoryDataRegionConfigurationSchema defaultRegion;
@NamedConfigValue
public VolatilePageMemoryDataRegionConfigurationSchema regions;
}
@Config
public class PersistentPageMemoryStorageEngineConfigurationSchema extends
BasePageMemoryStorageEngineConfigurationSchema{
@ConfigValue
public PersistentPageMemoryDataRegionConfigurationSchema defaultRegion;
@NamedConfigValue
public PersistentPageMemoryDataRegionConfigurationSchema regions;
@ConfigValue
public PageMemoryCheckpointConfigurationSchema checkpoint;
}{code}
*Implementation notes
# Add annotation
*org.apache.ignite.configuration.annotation.AbstractConfiguration*;
# Add processing to
*org.apache.ignite.internal.configuration.processor.Processor*;
# Add processing to
*org.apache.ignite.internal.configuration.asm.ConfigurationAsmGenerator*;
# Cover with tests.
*Further development*
* Consider the possibility and necessity of crossing with the annotation
*InternalConfiguration* and *PolymorphicConfig* in a separate ticket, at the
moment they cannot be used together in the same class (for simplicity).
was:
*NOTE*
Description may not be complete.
*Problem*
We need the ability to create a basic configuration schema so that we can
define a common configuration schema and inherit from it with additional
configuration added.
Let's look at an example:
We need to create two configuration schemes for the PageMemory based storage
engine, they should have a common property "page size in bytes" and then they
should be different, let's sketch an example scheme.
{code:java}
public class BasePageMemoryStorageEngineConfigurationSchema {
[jira] [Commented] (IGNITE-17145) Fix handle BinaryObjectException at the thin JDBC
[
https://issues.apache.org/jira/browse/IGNITE-17145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553994#comment-17553994
]
Ignite TC Bot commented on IGNITE-17145:
{panel:title=Branch: [pull/10084/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10084/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}JDBC Driver{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6622659]]
* {color:#013220}IgniteJdbcDriverTestSuite:
JdbcThinStatementSelfTest.testExceptionOnDeserializeResponse - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6622718buildTypeId=IgniteTests24Java8_RunAll]
> Fix handle BinaryObjectException at the thin JDBC
> -
>
> Key: IGNITE-17145
> URL: https://issues.apache.org/jira/browse/IGNITE-17145
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.13
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I am trying to get enum field using sqlline, but failed with error Statement
> is closed.
> {code}
> 0: jdbc:ignite:thin://127.0.0.1> select status from nebulaclusterinfo;
> Error: Statement is closed. (state=,code=0)
> java.sql.SQLException: Statement is closed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.ensureNotClosed(JdbcThinStatement.java:950)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.getWarnings(JdbcThinStatement.java:546)
> at sqlline.Commands.execute(Commands.java:849)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1> select count(status) from nebulaclusterinfo;
> ++
> | COUNT(STATUS) |
> ++
> | 310|
> ++
> 1 row selected (0.108 seconds)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17157) Documentation of the Ignite index reader
[ https://issues.apache.org/jira/browse/IGNITE-17157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov updated IGNITE-17157: -- Summary: Documentation of the Ignite index reader (was: Documentation of Ignite index reader) > Documentation of the Ignite index reader > > > Key: IGNITE-17157 > URL: https://issues.apache.org/jira/browse/IGNITE-17157 > Project: Ignite > Issue Type: Task >Reporter: Denis Chudov >Priority: Major > Labels: documentation > > It would be nice to have a documentation for the Ignite index reader utility > that was added in IGNITE-14529. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17136) Update Ignite dependency: Tomcat Servlet API
[ https://issues.apache.org/jira/browse/IGNITE-17136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17136: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Update Ignite dependency: Tomcat Servlet API > > > Key: IGNITE-17136 > URL: https://issues.apache.org/jira/browse/IGNITE-17136 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Minor > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Update Tomcat Servlet API dependency 9.0.10 to 9.0.63 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17157) Documentation of Ignite index reader
Denis Chudov created IGNITE-17157: - Summary: Documentation of Ignite index reader Key: IGNITE-17157 URL: https://issues.apache.org/jira/browse/IGNITE-17157 Project: Ignite Issue Type: Task Reporter: Denis Chudov It would be nice to have a documentation for the Ignite index reader utility that was added in IGNITE-14529. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16873) C++ thin client SqlFieldsQuery should allow setting a partition
[
https://issues.apache.org/jira/browse/IGNITE-16873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553990#comment-17553990
]
Ignite TC Bot commented on IGNITE-16873:
{panel:title=Branch: [pull/10088/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10088/head] Base: [master] : New Tests
(1060)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform C++ CMake (Win x64 / Debug){color} [[tests
1060|https://ci.ignite.apache.org/viewLog.html?buildId=6626731]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForDaemons -
PASSED{color}
... and 1049 new tests
{panel}
[TeamCity *- Run :: CPP*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6626734buildTypeId=IgniteTests24Java8_RunCpp]
> C++ thin client SqlFieldsQuery should allow setting a partition
> ---
>
> Key: IGNITE-16873
> URL: https://issues.apache.org/jira/browse/IGNITE-16873
> Project: Ignite
> Issue Type: New Feature
> Components: platforms, thin client
>Affects Versions: 2.12
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> C++ client node queries (ScanQuery and SqlFiedsQuery) allow setting a
> partition the query would be executed on. This can be used to improve initial
> data load performance significantly
> The C++ thin client SqlFieldsQuery API has no partition property and that
> makes the initial data load performance unacceptable.
> Need to add the partition property to SqlFieldsQuery.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-16873) C++ thin client SqlFieldsQuery should allow setting a partition
[ https://issues.apache.org/jira/browse/IGNITE-16873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553988#comment-17553988 ] Igor Sapego commented on IGNITE-16873: -- Merged to master. > C++ thin client SqlFieldsQuery should allow setting a partition > --- > > Key: IGNITE-16873 > URL: https://issues.apache.org/jira/browse/IGNITE-16873 > Project: Ignite > Issue Type: New Feature > Components: platforms, thin client >Affects Versions: 2.12 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > C++ client node queries (ScanQuery and SqlFiedsQuery) allow setting a > partition the query would be executed on. This can be used to improve initial > data load performance significantly > The C++ thin client SqlFieldsQuery API has no partition property and that > makes the initial data load performance unacceptable. > Need to add the partition property to SqlFieldsQuery. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-14529) Add offline utility for analyzing indexes
[ https://issues.apache.org/jira/browse/IGNITE-14529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553984#comment-17553984 ] Denis Chudov commented on IGNITE-14529: --- [~nizhikov] no docs yet, though I have some drafts. We possibly could get back to this work if there is a need. > Add offline utility for analyzing indexes > - > > Key: IGNITE-14529 > URL: https://issues.apache.org/jira/browse/IGNITE-14529 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Chudov >Assignee: Denis Chudov >Priority: Major > Labels: important > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > It would be useful to have the possibility for indexes offline validation. > The utility must check that every configured index (available in MetaTree > [1]) is reachable from corresponding root page, tree structure is valid and > no orphan(unreachable) index pages are present in the index.bin persistent > page store. > [1] > org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl#getIndexNames -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17156) Fix potential bug in org.apache.ignite.internal.configuration.storage.ItRebalanceDistributedTest#testThreeQueuedRebalances
Mirza Aliev created IGNITE-17156: Summary: Fix potential bug in org.apache.ignite.internal.configuration.storage.ItRebalanceDistributedTest#testThreeQueuedRebalances Key: IGNITE-17156 URL: https://issues.apache.org/jira/browse/IGNITE-17156 Project: Ignite Issue Type: Bug Reporter: Mirza Aliev Assignee: Mirza Aliev We have noticed that once this test hangs on TC, the root cause was the problem with stopping meta storage listeners, when meta storage node was stopped first. To fix test, stop meta storage node last. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17093) Map error codes for cli commands
[ https://issues.apache.org/jira/browse/IGNITE-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev updated IGNITE-17093: -- Description: Invoking Ignite CLI tool in non-REPL mode produces the following exit codes: 0. Successful completion. 1. An error occured during the execution. 2. An error occured during parsing command line arguments. was: There should be a mapping between the error and the exit code. * list types of errors that user can get during commands execution * return exit codes from all commands > Map error codes for cli commands > > > Key: IGNITE-17093 > URL: https://issues.apache.org/jira/browse/IGNITE-17093 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > Invoking Ignite CLI tool in non-REPL mode produces the following exit codes: > 0. Successful completion. > 1. An error occured during the execution. > 2. An error occured during parsing command line arguments. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17141) Use Maven to build .NET
[ https://issues.apache.org/jira/browse/IGNITE-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-17141: Summary: Use Maven to build .NET (was: Use maven to build .NET) > Use Maven to build .NET > --- > > Key: IGNITE-17141 > URL: https://issues.apache.org/jira/browse/IGNITE-17141 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > It seems we can build the .NET using maven + maven-ant-plugin. This will > simplify the Apache Ignite release build distribution and will add a single > build point for the whole release. > Discussion: > https://lists.apache.org/thread/9os553vhcryko1jlfzywmx977o6lyor5 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17136) Update Ignite dependency: Tomcat Servlet API
[
https://issues.apache.org/jira/browse/IGNITE-17136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553971#comment-17553971
]
Ignite TC Bot commented on IGNITE-17136:
{panel:title=Branch: [pull/10078/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Yarn{color} [[tests 0 Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=6480169]]
{panel}
{panel:title=Branch: [pull/10078/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=6473174buildTypeId=IgniteTests24Java8_RunAll]
> Update Ignite dependency: Tomcat Servlet API
>
>
> Key: IGNITE-17136
> URL: https://issues.apache.org/jira/browse/IGNITE-17136
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr
>Assignee: Aleksandr
>Priority: Minor
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Update Tomcat Servlet API dependency 9.0.10 to 9.0.63
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-2292) .NET: Add ability to build .NET platform from Maven
[
https://issues.apache.org/jira/browse/IGNITE-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553964#comment-17553964
]
Pavel Tupitsyn commented on IGNITE-2292:
Superceded by IGNITE-17141.
> .NET: Add ability to build .NET platform from Maven
> ---
>
> Key: IGNITE-2292
> URL: https://issues.apache.org/jira/browse/IGNITE-2292
> Project: Ignite
> Issue Type: Task
> Components: general, platforms
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Minor
> Labels: .net
>
> Currently build procedure looks as follows:
> 1) Java is built from Maven
> 2) .NET is built manually using modules/platforms/dotnet/mkbuild.cmd
> 3) Docs fo Java, .NET and CPP are built form Maven
> Looks like we should intergrate .NET buld into Maven process so that user can
> build the whole product with a single command. E.g.:
> {code}mvn clean package [java_build_args] -Dignite.net.docs=true
> -Dignite.net.build =true -Dignite.net.build.x86=true
> -Dignite.net.build.x86.javaHome=[path to x86 JDK]{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (IGNITE-2292) .NET: Add ability to build .NET platform from Maven
[
https://issues.apache.org/jira/browse/IGNITE-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-2292.
Resolution: Duplicate
> .NET: Add ability to build .NET platform from Maven
> ---
>
> Key: IGNITE-2292
> URL: https://issues.apache.org/jira/browse/IGNITE-2292
> Project: Ignite
> Issue Type: Task
> Components: general, platforms
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .net
>
> Currently build procedure looks as follows:
> 1) Java is built from Maven
> 2) .NET is built manually using modules/platforms/dotnet/mkbuild.cmd
> 3) Docs fo Java, .NET and CPP are built form Maven
> Looks like we should intergrate .NET buld into Maven process so that user can
> build the whole product with a single command. E.g.:
> {code}mvn clean package [java_build_args] -Dignite.net.docs=true
> -Dignite.net.build =true -Dignite.net.build.x86=true
> -Dignite.net.build.x86.javaHome=[path to x86 JDK]{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (IGNITE-2292) .NET: Add ability to build .NET platform from Maven
[
https://issues.apache.org/jira/browse/IGNITE-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-2292:
--
Assignee: Pavel Tupitsyn
> .NET: Add ability to build .NET platform from Maven
> ---
>
> Key: IGNITE-2292
> URL: https://issues.apache.org/jira/browse/IGNITE-2292
> Project: Ignite
> Issue Type: Task
> Components: general, platforms
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .net
>
> Currently build procedure looks as follows:
> 1) Java is built from Maven
> 2) .NET is built manually using modules/platforms/dotnet/mkbuild.cmd
> 3) Docs fo Java, .NET and CPP are built form Maven
> Looks like we should intergrate .NET buld into Maven process so that user can
> build the whole product with a single command. E.g.:
> {code}mvn clean package [java_build_args] -Dignite.net.docs=true
> -Dignite.net.build =true -Dignite.net.build.x86=true
> -Dignite.net.build.x86.javaHome=[path to x86 JDK]{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17141) Use maven to build .NET
[ https://issues.apache.org/jira/browse/IGNITE-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-17141: Summary: Use maven to build .NET (was: Use maven to build .NET thin client ) > Use maven to build .NET > --- > > Key: IGNITE-17141 > URL: https://issues.apache.org/jira/browse/IGNITE-17141 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > It seems we can build the .NET using maven + maven-ant-plugin. This will > simplify the Apache Ignite release build distribution and will add a single > build point for the whole release. > Discussion: > https://lists.apache.org/thread/9os553vhcryko1jlfzywmx977o6lyor5 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17141) Use maven to build .NET thin client
[ https://issues.apache.org/jira/browse/IGNITE-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553960#comment-17553960 ] Pavel Tupitsyn commented on IGNITE-17141: - [~vveider] would you like to have a look at those changes too? > Use maven to build .NET thin client > > > Key: IGNITE-17141 > URL: https://issues.apache.org/jira/browse/IGNITE-17141 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > It seems we can build the .NET using maven + maven-ant-plugin. This will > simplify the Apache Ignite release build distribution and will add a single > build point for the whole release. > Discussion: > https://lists.apache.org/thread/9os553vhcryko1jlfzywmx977o6lyor5 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17141) Use maven to build .NET thin client
[ https://issues.apache.org/jira/browse/IGNITE-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553958#comment-17553958 ] Pavel Tupitsyn commented on IGNITE-17141: - [~mmuzaf] the changes look good to me in general. Please see a comment on GitHub. Also, can you please update DEVNOTES.txt in repo root (explain how .NET can be built from Maven) and DEVNOTES.txt in modules/platforms/dotnet (add a note that .NET can be built from Maven)? > Use maven to build .NET thin client > > > Key: IGNITE-17141 > URL: https://issues.apache.org/jira/browse/IGNITE-17141 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > It seems we can build the .NET using maven + maven-ant-plugin. This will > simplify the Apache Ignite release build distribution and will add a single > build point for the whole release. > Discussion: > https://lists.apache.org/thread/9os553vhcryko1jlfzywmx977o6lyor5 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16873) C++ thin client SqlFieldsQuery should allow setting a partition
[ https://issues.apache.org/jira/browse/IGNITE-16873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553947#comment-17553947 ] Pavel Tupitsyn commented on IGNITE-16873: - [~isapego] Looks good to me. > C++ thin client SqlFieldsQuery should allow setting a partition > --- > > Key: IGNITE-16873 > URL: https://issues.apache.org/jira/browse/IGNITE-16873 > Project: Ignite > Issue Type: New Feature > Components: platforms, thin client >Affects Versions: 2.12 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > C++ client node queries (ScanQuery and SqlFiedsQuery) allow setting a > partition the query would be executed on. This can be used to improve initial > data load performance significantly > The C++ thin client SqlFieldsQuery API has no partition property and that > makes the initial data load performance unacceptable. > Need to add the partition property to SqlFieldsQuery. -- This message was sent by Atlassian Jira (v8.20.7#820007)
