[jira] [Updated] (IGNITE-10301) GridToStringBuilder is broken for classes with inheritance
[
https://issues.apache.org/jira/browse/IGNITE-10301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-10301:
-
Fix Version/s: (was: 2.7)
2.8
> GridToStringBuilder is broken for classes with inheritance
> --
>
> Key: IGNITE-10301
> URL: https://issues.apache.org/jira/browse/IGNITE-10301
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Alexey Goncharuk
>Assignee: Ryabov Dmitrii
>Priority: Blocker
> Fix For: 2.8
>
>
> Given the following class hierarchy
> {code}
> /** */
> private static class Parent {
> /** */
> private int a;
> /** {@inheritDoc} */
> @Override public String toString() {
> return S.toString(Parent.class, this);
> }
> }
> /** */
> private static class Child extends Parent {
> /** */
> private int b;
> /** {@inheritDoc} */
> @Override public String toString() {
> return S.toString(Child.class, this, super.toString());
> }
> }
> private static class Wrapper {
> /** */
> @GridToStringInclude
> Parent p = new Child();
> /** {@inheritDoc} */
> @Override public String toString() {
> return S.toString(Wrapper.class, this);
> }
> }
> {code}
> the next test fails:
> {code}
> /**
> */
> public void testHierarchy() {
> Wrapper w = new Wrapper();
> Parent p = w.p;
> String wS = w.toString();
> String pS = p.toString();
> // Expect wS to be "Wrapper [p=" + pS + ']'.
> assertEquals("Wrapper [p=" + pS + ']', wS);
> }
> {code}
> {code}
> Expected :Wrapper [p=Child [b=0, super=Parent [a=0]]]
> Actual :Wrapper [p=Parent [a=0]Child [b=0, super=]]
> {code}
> This is a regression from IGNITE-602. We need to fix this in 2.7 or revert
> IGNITE-602.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8493) GridToStringBuilder fails with NPE deals with primitive arrays operations.
[ https://issues.apache.org/jira/browse/IGNITE-8493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697674#comment-16697674 ] ASF GitHub Bot commented on IGNITE-8493: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5492 > GridToStringBuilder fails with NPE deals with primitive arrays operations. > -- > > Key: IGNITE-8493 > URL: https://issues.apache.org/jira/browse/IGNITE-8493 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.4 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Fix For: 2.7 > > > GridToStringBuilder#arrayToString fails with NPE, if input is a primitive > array. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10002) MVCC: Create "Cache 2" test suite for MVCC mode.
[
https://issues.apache.org/jira/browse/IGNITE-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697593#comment-16697593
]
Ignite TC Bot commented on IGNITE-10002:
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Inspections] Core{color} [[tests 0 BuildFailureOnMetric
|https://ci.ignite.apache.org/viewLog.html?buildId=2387948]]
{color:#d04437}Queries 2{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2387877]]
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentAtomicReplicatedSelfTest.testAddColumnCoordinatorChange
- 1,0% fails in last 100 master runs.
{color:#d04437}Platform .NET (Integrations){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2387943]]
* dll: EntityFrameworkCacheTest.TestIncrementMultithreaded - 0,0% fails in last
100 master runs.
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2387952buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Create "Cache 2" test suite for MVCC mode.
>
>
> Key: IGNITE-10002
> URL: https://issues.apache.org/jira/browse/IGNITE-10002
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.8
>
>
> Create MVCC version of IgniteCacheTestSuite2 and add it to TC.
> All non-relevant tests should be marked as ignored.
> Failed tests should be muted and tickets should be created for unknown
> failure reasons.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10158) Some tests in IgniteCacheAbstractQuerySelfTest are incorrectly muted
[
https://issues.apache.org/jira/browse/IGNITE-10158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697562#comment-16697562
]
Oleg Ignatenko commented on IGNITE-10158:
-
[~Jokser] as you suggested I resolved conflicts and re-run tests, see TC bot
visa above
> Some tests in IgniteCacheAbstractQuerySelfTest are incorrectly muted
>
>
> Key: IGNITE-10158
> URL: https://issues.apache.org/jira/browse/IGNITE-10158
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Some tests in
> [IgniteCacheAbstractQuerySelfTest|https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/IgniteCacheAbstractQuerySelfTest.java]
> are muted by renaming (prefixing with underscore, {{_test...}} and refer
> invalid JIRA URL in fail parameter
> ("http://atlassian.gridgain.com/jira/browse/GG-11216;).
> - _testDifferentKeyTypes
> this test should change expectation to opposite and after that recovered
> - _testObjectQueryWithSwap and _testTwoObjectsTextSearch
> Need to be properly muted and further investigated, per separate tickets.
> Per my preliminary checks tests fail because
> of wrong cache configuration, although there is also a chance that test
> design is wrong and these should be deleted.
> There is also a dead code there, a private class {{EmptyObject}} - it needs
> to be deleted. Code that was using this class was removed per
> [IGNITE-1232|https://issues.apache.org/jira/browse/IGNITE-1232] ([commit
> 79b8b08|https://github.com/gridgain/apache-ignite/commit/68891e89dd0e0f19321d6a4d45ae7372279b8b08#diff-a2f35b3aa70a70b98ce0cd6a1381d1f7])
> but this private class was forgotten.
> I also searched project code for other occurrences of mentioned troublesome
> fail parameter "GG-11216" and found yet another incorrectly muted test:
> {{IgniteCacheQueryMultiThreadedSelfTest#_testMultiThreadedSwapUnswapLongString}}
> This test should be recovered. It passed on my machine and per my comparison
> with similar test cases {{testMultiThreadedSwapUnswapLong}} and
> {{testMultiThreadedSwapUnswapString}} its design looks fairly reasonable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10158) Some tests in IgniteCacheAbstractQuerySelfTest are incorrectly muted
[
https://issues.apache.org/jira/browse/IGNITE-10158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697561#comment-16697561
]
Ignite TC Bot commented on IGNITE-10158:
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2388945buildTypeId=IgniteTests24Java8_RunAll]
> Some tests in IgniteCacheAbstractQuerySelfTest are incorrectly muted
>
>
> Key: IGNITE-10158
> URL: https://issues.apache.org/jira/browse/IGNITE-10158
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Some tests in
> [IgniteCacheAbstractQuerySelfTest|https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/IgniteCacheAbstractQuerySelfTest.java]
> are muted by renaming (prefixing with underscore, {{_test...}} and refer
> invalid JIRA URL in fail parameter
> ("http://atlassian.gridgain.com/jira/browse/GG-11216;).
> - _testDifferentKeyTypes
> this test should change expectation to opposite and after that recovered
> - _testObjectQueryWithSwap and _testTwoObjectsTextSearch
> Need to be properly muted and further investigated, per separate tickets.
> Per my preliminary checks tests fail because
> of wrong cache configuration, although there is also a chance that test
> design is wrong and these should be deleted.
> There is also a dead code there, a private class {{EmptyObject}} - it needs
> to be deleted. Code that was using this class was removed per
> [IGNITE-1232|https://issues.apache.org/jira/browse/IGNITE-1232] ([commit
> 79b8b08|https://github.com/gridgain/apache-ignite/commit/68891e89dd0e0f19321d6a4d45ae7372279b8b08#diff-a2f35b3aa70a70b98ce0cd6a1381d1f7])
> but this private class was forgotten.
> I also searched project code for other occurrences of mentioned troublesome
> fail parameter "GG-11216" and found yet another incorrectly muted test:
> {{IgniteCacheQueryMultiThreadedSelfTest#_testMultiThreadedSwapUnswapLongString}}
> This test should be recovered. It passed on my machine and per my comparison
> with similar test cases {{testMultiThreadedSwapUnswapLong}} and
> {{testMultiThreadedSwapUnswapString}} its design looks fairly reasonable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10158) Some tests in IgniteCacheAbstractQuerySelfTest are incorrectly muted
[
https://issues.apache.org/jira/browse/IGNITE-10158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697560#comment-16697560
]
Ignite TC Bot commented on IGNITE-10158:
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2388945buildTypeId=IgniteTests24Java8_RunAll]
> Some tests in IgniteCacheAbstractQuerySelfTest are incorrectly muted
>
>
> Key: IGNITE-10158
> URL: https://issues.apache.org/jira/browse/IGNITE-10158
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Some tests in
> [IgniteCacheAbstractQuerySelfTest|https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/IgniteCacheAbstractQuerySelfTest.java]
> are muted by renaming (prefixing with underscore, {{_test...}} and refer
> invalid JIRA URL in fail parameter
> ("http://atlassian.gridgain.com/jira/browse/GG-11216;).
> - _testDifferentKeyTypes
> this test should change expectation to opposite and after that recovered
> - _testObjectQueryWithSwap and _testTwoObjectsTextSearch
> Need to be properly muted and further investigated, per separate tickets.
> Per my preliminary checks tests fail because
> of wrong cache configuration, although there is also a chance that test
> design is wrong and these should be deleted.
> There is also a dead code there, a private class {{EmptyObject}} - it needs
> to be deleted. Code that was using this class was removed per
> [IGNITE-1232|https://issues.apache.org/jira/browse/IGNITE-1232] ([commit
> 79b8b08|https://github.com/gridgain/apache-ignite/commit/68891e89dd0e0f19321d6a4d45ae7372279b8b08#diff-a2f35b3aa70a70b98ce0cd6a1381d1f7])
> but this private class was forgotten.
> I also searched project code for other occurrences of mentioned troublesome
> fail parameter "GG-11216" and found yet another incorrectly muted test:
> {{IgniteCacheQueryMultiThreadedSelfTest#_testMultiThreadedSwapUnswapLongString}}
> This test should be recovered. It passed on my machine and per my comparison
> with similar test cases {{testMultiThreadedSwapUnswapLong}} and
> {{testMultiThreadedSwapUnswapString}} its design looks fairly reasonable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10398) CacheMetrics always return 0 for local cache
Evgenii Zhuravlev created IGNITE-10398:
--
Summary: CacheMetrics always return 0 for local cache
Key: IGNITE-10398
URL: https://issues.apache.org/jira/browse/IGNITE-10398
Project: Ignite
Issue Type: Bug
Reporter: Evgenii Zhuravlev
However, it shows the right offHeapEntriesCnt.
Short code snippet:
{code:java}
IgniteConfiguration igniteConfig = new IgniteConfiguration();
CacheConfiguration cacheConfig = new CacheConfiguration("testCache");
cacheConfig.setStatisticsEnabled(true);
igniteConfig.setCacheConfiguration(cacheConfig);
cacheConfig.setCacheMode(CacheMode.LOCAL);
try (Ignite ignite = Ignition.start(igniteConfig)) {
IgniteCache cache = ignite.getOrCreateCache(cacheConfig.getName());
cache.put("key", "val");
cache.put("key2", "val2");
cache.remove("key2");
System.out.println(cache.localMetrics());
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10216) Disable annotations order according in inspection profile
[
https://issues.apache.org/jira/browse/IGNITE-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697497#comment-16697497
]
ASF GitHub Bot commented on IGNITE-10216:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5471
> Disable annotations order according in inspection profile
> -
>
> Key: IGNITE-10216
> URL: https://issues.apache.org/jira/browse/IGNITE-10216
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> The {{requireAnnotationFirst}} option of {{Missorted modifiers}} Intellij
> inspection must be set to {{false}}.
> Example,
> {code:title=false}
> @Nullable @Override public Long reduce(List results)
> {code}
> {code:title=true}
> @Override public @Nullable Long reduce(List results)
> {code}
> The {{ingnite_inspections.xml}} configuration need to be updated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10290) Map.Entry interface for key cache may lead to incorrect hash code calculation
[
https://issues.apache.org/jira/browse/IGNITE-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697493#comment-16697493
]
Ignite TC Bot commented on IGNITE-10290:
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2341728]]
* IgniteBinarySimpleNameMapperBasicTestSuite:
MarshallerContextLockingSelfTest.testMultithreadedUpdate - 0,0% fails in last
100 master runs.
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2341837buildTypeId=IgniteTests24Java8_RunAll]
> Map.Entry interface for key cache may lead to incorrect hash code calculation
> -
>
> Key: IGNITE-10290
> URL: https://issues.apache.org/jira/browse/IGNITE-10290
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
> Attachments: Reproducer.java
>
>
> If use Map.Entry interface for a key, we can try to find (key, value) in
> store with incorrect calculated hash code for binary representation, it lead
> to result null.
> The problem is in the
> GridPartitionedSingleGetFuture#localGet() and
> GridPartitionedGetFuture#localGet() does not execute prepareForCache before
> reading cacheDataRow from row store.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8493) GridToStringBuilder fails with NPE deals with primitive arrays operations.
[ https://issues.apache.org/jira/browse/IGNITE-8493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697482#comment-16697482 ] ASF GitHub Bot commented on IGNITE-8493: GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/5492 ignite-2.7 revert GridToStringBuilder changes Revert of - IGNITE-8493 - IGNITE-9209 - IGNITE-602 You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite ignite-2.7-revert-toString Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5492.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5492 commit e6b42abb81c22bd119a9233023be6be66b2aad09 Author: Nikolay Izhikov Date: 2018-11-23T19:51:08Z Revert "IGNITE-8493 GridToStringBuilder arrayToString refactoring. - Fixes #4501." This reverts commit dd8c933fd44e4ad9b315daccce8e2327606867b0. commit 5f968d2413c0c914da0ebcb5c051023429b3e518 Author: Nikolay Izhikov Date: 2018-11-23T19:51:45Z Revert "IGNITE-9209 fix for GridDistributedTxMapping.toString() returns broken string. - Fixes #4519." This reverts commit 9bb9c043513c3cc6c6b70c6c3395e5bb76fad75e. commit 307ac58d1aa1f0145c16affe6de96314b1c8ecef Author: Nikolay Izhikov Date: 2018-11-23T19:52:12Z Revert "IGNITE-602 Fixed possible StackOverflowError in GridToStringBuilder when circular references are present - Fixes #1558." This reverts commit d67c5bf4c22338695a116e0fbf0a58a4d581af5d. > GridToStringBuilder fails with NPE deals with primitive arrays operations. > -- > > Key: IGNITE-8493 > URL: https://issues.apache.org/jira/browse/IGNITE-8493 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.4 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Fix For: 2.7 > > > GridToStringBuilder#arrayToString fails with NPE, if input is a primitive > array. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10193) IgniteBaselineAffinityTopologyActivationTest#testBaselineTopologyHistoryIsDeletedOnBaselineDelete fails asserting bltHist.history().size()
[
https://issues.apache.org/jira/browse/IGNITE-10193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697476#comment-16697476
]
Ignite TC Bot commented on IGNITE-10193:
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS 2{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2385294]]
* IgnitePdsTestSuite2:
IgniteWalIteratorSwitchSegmentTest.testSwitchReadingSegmentFromWorkToArchive -
0,0% fails in last 100 master runs.
* IgnitePdsTestSuite2:
IgniteWalIteratorSwitchSegmentTest.testInvariantSwitchSegment - 0,0% fails in
last 100 master runs.
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2361671buildTypeId=IgniteTests24Java8_RunAll]
> IgniteBaselineAffinityTopologyActivationTest#testBaselineTopologyHistoryIsDeletedOnBaselineDelete
> fails asserting bltHist.history().size()
> --
>
> Key: IGNITE-10193
> URL: https://issues.apache.org/jira/browse/IGNITE-10193
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Assignee: Alexey Platonov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> IgniteBaselineAffinityTopologyActivationTest#testBaselineTopologyHistoryIsDeletedOnBaselineDelete
> (in current codebase muted by renaming to
> {{_testBaselineTopologyHistoryIsDeletedOnBaselineDelete}}) fails. Test
> javadoc says: "Restore this test when requirements for BaselineTopology
> deletion are clarified and this feature is covered with more tests."
> (javadoc appears to be giving proper reason)
> Failure message: {noformat}
> junit.framework.AssertionFailedError:
> Expected :0
> Actual :2
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgniteBaselineAffinityTopologyActivationTest$17.verify(IgniteBaselineAffinityTopologyActivationTest.java:1041)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgniteBaselineAffinityTopologyActivationTest.verifyBaselineTopologyHistoryOnNodes(IgniteBaselineAffinityTopologyActivationTest.java:693)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgniteBaselineAffinityTopologyActivationTest.testBaselineTopologyHistoryIsDeletedOnBaselineDelete(IgniteBaselineAffinityTopologyActivationTest.java:1082)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2208)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2124)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Snippet of code referred to from above message: {code}assertEquals(0,
> bltHist.history().size());{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9996) Investigate possible performance drop in FSYNC mode for ignite-2.7 compared to ignite-2.6
[ https://issues.apache.org/jira/browse/IGNITE-9996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697430#comment-16697430 ] Nikolay Izhikov edited comment on IGNITE-9996 at 11/23/18 6:39 PM: --- final fix merged to master and 2.7 https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=c670b012c915f244f508340cbbaef47709b0c4c4 https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=475a0a71500dc4f638100f3ec0c7f8029db42f4a was (Author: nizhikov): https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=c670b012c915f244f508340cbbaef47709b0c4c4 https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=475a0a71500dc4f638100f3ec0c7f8029db42f4a > Investigate possible performance drop in FSYNC mode for ignite-2.7 compared > to ignite-2.6 > - > > Key: IGNITE-9996 > URL: https://issues.apache.org/jira/browse/IGNITE-9996 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Alexey Goncharuk >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-29 at 3.30.51 PM.png, Screen Shot > 2018-10-31 at 10.30.26 AM.png, Screen Shot 2018-11-08 at 2.38.06 PM.png > > > As per the latest reports we probably have a performance drop around 5-8% on > write benchmarks in FSYNC mode. The cause needs to be investigated and fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10392) Client broken cluster where try to connect. Server nodes drop by handler
[
https://issues.apache.org/jira/browse/IGNITE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697407#comment-16697407
]
ASF GitHub Bot commented on IGNITE-10392:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5488
> Client broken cluster where try to connect. Server nodes drop by handler
>
>
> Key: IGNITE-10392
> URL: https://issues.apache.org/jira/browse/IGNITE-10392
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Blocker
> Fix For: 2.8
>
>
> {noformat}
> org.apache.ignite.IgniteException: Failed to resolve nodes topology
> [cacheGrp=N/A, topVer=AffinityTopologyVersion [topVer=133, minorTopVer=0],
> history=[AffinityTopologyVersion [topVer=35, minorTopVer=0],
> AffinityTopologyVersion [topVer=36, minorTopVer=0], AffinityTopologyVersion
> [topVer=37, minorTopVer=0], AffinityTopologyVersion [topVer=38,
> minorTopVer=0], AffinityTopologyVersion [topVer=39, minorTopVer=0],
> AffinityTopologyVersion [topVer=40, minorTopVer=0], AffinityTopologyVersion
> [topVer=41, minorTopVer=0], AffinityTopologyVersion [topVer=42,
> minorTopVer=0], AffinityTopologyVersion [topVer=43, minorTopVer=0],
> AffinityTopologyVersion [topVer=44, minorTopVer=0], AffinityTopologyVersion
> [topVer=45, minorTopVer=0], AffinityTopologyVersion [topVer=46,
> minorTopVer=0], AffinityTopologyVersion [topVer=47, minorTopVer=0],
> AffinityTopologyVersion [topVer=48, minorTopVer=0], AffinityTopologyVersion
> [topVer=49, minorTopVer=0], AffinityTopologyVersion [topVer=50,
> minorTopVer=0], AffinityTopologyVersion [topVer=51, minorTopVer=0],
> AffinityTopologyVersion [topVer=52, minorTopVer=0], AffinityTopologyVersion
> [topVer=53, minorTopVer=0], AffinityTopologyVersion [topVer=54,
> minorTopVer=0], AffinityTopologyVersion [topVer=55, minorTopVer=0],
> AffinityTopologyVersion [topVer=56, minorTopVer=0], AffinityTopologyVersion
> [topVer=57, minorTopVer=0], AffinityTopologyVersion [topVer=58,
> minorTopVer=0], AffinityTopologyVersion [topVer=59, minorTopVer=0],
> AffinityTopologyVersion [topVer=60, minorTopVer=0], AffinityTopologyVersion
> [topVer=61, minorTopVer=0], AffinityTopologyVersion [topVer=62,
> minorTopVer=0], AffinityTopologyVersion [topVer=63, minorTopVer=0],
> AffinityTopologyVersion [topVer=64, minorTopVer=0], AffinityTopologyVersion
> [topVer=65, minorTopVer=0], AffinityTopologyVersion [topVer=66,
> minorTopVer=0], AffinityTopologyVersion [topVer=67, minorTopVer=0],
> AffinityTopologyVersion [topVer=68, minorTopVer=0], AffinityTopologyVersion
> [topVer=69, minorTopVer=0], AffinityTopologyVersion [topVer=70,
> minorTopVer=0], AffinityTopologyVersion [topVer=71, minorTopVer=0],
> AffinityTopologyVersion [topVer=72, minorTopVer=0], AffinityTopologyVersion
> [topVer=73, minorTopVer=0], AffinityTopologyVersion [topVer=74,
> minorTopVer=0], AffinityTopologyVersion [topVer=75, minorTopVer=0],
> AffinityTopologyVersion [topVer=76, minorTopVer=0], AffinityTopologyVersion
> [topVer=77, minorTopVer=0], AffinityTopologyVersion [topVer=78,
> minorTopVer=0], AffinityTopologyVersion [topVer=79, minorTopVer=0],
> AffinityTopologyVersion [topVer=80, minorTopVer=0], AffinityTopologyVersion
> [topVer=81, minorTopVer=0], AffinityTopologyVersion [topVer=82,
> minorTopVer=0], AffinityTopologyVersion [topVer=83, minorTopVer=0],
> AffinityTopologyVersion [topVer=84, minorTopVer=0], AffinityTopologyVersion
> [topVer=85, minorTopVer=0], AffinityTopologyVersion [topVer=86,
> minorTopVer=0], AffinityTopologyVersion [topVer=87, minorTopVer=0],
> AffinityTopologyVersion [topVer=88, minorTopVer=0], AffinityTopologyVersion
> [topVer=89, minorTopVer=0], AffinityTopologyVersion [topVer=90,
> minorTopVer=0], AffinityTopologyVersion [topVer=91, minorTopVer=0],
> AffinityTopologyVersion [topVer=92, minorTopVer=0], AffinityTopologyVersion
> [topVer=93, minorTopVer=0], AffinityTopologyVersion [topVer=94,
> minorTopVer=0], AffinityTopologyVersion [topVer=95, minorTopVer=0],
> AffinityTopologyVersion [topVer=96, minorTopVer=0], AffinityTopologyVersion
> [topVer=97, minorTopVer=0], AffinityTopologyVersion [topVer=98,
> minorTopVer=0], AffinityTopologyVersion [topVer=99, minorTopVer=0],
> AffinityTopologyVersion [topVer=100, minorTopVer=0], AffinityTopologyVersion
> [topVer=101, minorTopVer=0], AffinityTopologyVersion [topVer=102,
> minorTopVer=0], AffinityTopologyVersion [topVer=103, minorTopVer=0],
> AffinityTopologyVersion [topVer=104, minorTopVer=0], AffinityTopologyVersion
> [topVer=105, minorTopVer=0], AffinityTopologyVersion [topVer=106,
> minorTopVer=0], AffinityTopologyVersion [topVer=107, minorTopVer=0],
> AffinityTopologyVersion [topVer=108, minorTopVer=0],
[jira] [Updated] (IGNITE-10397) SQL Schema may be lost after cluster activation and simple query run
[
https://issues.apache.org/jira/browse/IGNITE-10397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Antonov updated IGNITE-10397:
Ignite Flags: (was: Docs Required)
> SQL Schema may be lost after cluster activation and simple query run
>
>
> Key: IGNITE-10397
> URL: https://issues.apache.org/jira/browse/IGNITE-10397
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.8
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Critical
> Fix For: 2.8
>
>
> Scenario:
> 1) Start 3 grids in a multithread mode with auto-activation.
> 2) Start the client.
> 3) Run a simple query like this
> {noformat}
> cache(DEFAULT_CACHE_NAME + 0).query(new SqlQuery<>(Integer.class,
> "1=1")).getAll();
> {noformat}
> Exception with the message that schema not found will be thrown:
> {noformat}
> [2018-11-23
> 19:56:57,284][ERROR][query-#223%distributed.CacheMessageStatsIndexingTest2%][GridMapQueryExecutor]
> Failed to execute local query.
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to set schema for DB connection for thread [schema=default0]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:549)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:392)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:767)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:637)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:224)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor$2.onMessage(GridMapQueryExecutor.java:184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2333)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.h2.jdbc.JdbcSQLException: Schema "default0" not found; SQL
> statement:
> SET SCHEMA "default0" [90079-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.engine.Database.getSchema(Database.java:1755)
> at org.h2.command.dml.Set.update(Set.java:408)
> at org.h2.command.CommandContainer.update(CommandContainer.java:101)
> at org.h2.command.Command.executeUpdate(Command.java:260)
> at org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:137)
> at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:122)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:541)
> ... 13 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10352) Cache get request can be mapped to node while partition in MOVING state
[
https://issues.apache.org/jira/browse/IGNITE-10352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697388#comment-16697388
]
Ignite TC Bot commented on IGNITE-10352:
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Inspections] Core{color} [[tests 0 BuildFailureOnMetric
|https://ci.ignite.apache.org/viewLog.html?buildId=2387516]]
{color:#d04437}Basic 1{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2386463]]
* IgniteBasicTestSuite:
BPlusTreeSelfTest.testSizeForRandomPutRmvMultithreadedAsync_3 - 0,0% fails in
last 100 master runs.
{color:#d04437}PDS 2{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2387522]]
* IgnitePdsTestSuite2:
ClientAffinityAssignmentWithBaselineTest.testClientJoinCacheLongTransactionNodeStart
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2386488]]
* IgniteCacheTestSuite5:
CacheLateAffinityAssignmentTest.testCreateCloseClientCacheOnCoordinator2 - 0,0%
fails in last 100 master runs.
{color:#d04437}Cache 3{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2386486]]
* IgniteBinaryObjectsCacheTestSuite3:
IgniteCacheGroupsTest.testRestartsAndCacheCreateDestroy - 0,0% fails in last
100 master runs.
{color:#d04437}Cache 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2387534]]
* IgniteCacheTestSuite4:
IgniteDynamicCacheWithConfigStartSelfTest.testStartCacheOnClient - 0,0% fails
in last 100 master runs.
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2386520buildTypeId=IgniteTests24Java8_RunAll]
> Cache get request can be mapped to node while partition in MOVING state
> ---
>
> Key: IGNITE-10352
> URL: https://issues.apache.org/jira/browse/IGNITE-10352
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>
> Cache get request can be mapped to node while partition in MOVING state.
> It leads to assertions like quoted below and eventually to failure handler
> action.
> {noformat}
> java.lang.AssertionError: Wrong ready topology version for invalid partitions
> response [topVer=AffinityTopologyVersion [topVer=19, minorTopVer=0],
> req=GridNearSingleGetRequest [futId=1542371256329, key=KeyCacheObjectImpl
> [part=4595,
> val=com.sbt.cdm.api.model.published.ae.PublishedOperationCondition,
> hasValBytes=true], flags=1, topVer=AffinityTopologyVersion [topVer=19,
> minorTopVer=0], subjId=ea523c3a-4d22-4a3c-b1b0-3137da762021, taskNameHash=0,
> createTtl=-1, accessTtl=-1, mvccSnapshot=null]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$6.apply(GridDhtCacheAdapter.java:975)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$6.apply(GridDhtCacheAdapter.java:938)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetRequest(GridDhtCacheAdapter.java:938)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$2.apply(GridDhtTransactionalCacheAdapter.java:152)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$2.apply(GridDhtTransactionalCacheAdapter.java:150)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:295)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2349)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
>
[jira] [Commented] (IGNITE-9996) Investigate possible performance drop in FSYNC mode for ignite-2.7 compared to ignite-2.6
[ https://issues.apache.org/jira/browse/IGNITE-9996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697385#comment-16697385 ] ASF GitHub Bot commented on IGNITE-9996: Github user nizhikov closed the pull request at: https://github.com/apache/ignite/pull/5426 > Investigate possible performance drop in FSYNC mode for ignite-2.7 compared > to ignite-2.6 > - > > Key: IGNITE-9996 > URL: https://issues.apache.org/jira/browse/IGNITE-9996 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Alexey Goncharuk >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-29 at 3.30.51 PM.png, Screen Shot > 2018-10-31 at 10.30.26 AM.png, Screen Shot 2018-11-08 at 2.38.06 PM.png > > > As per the latest reports we probably have a performance drop around 5-8% on > write benchmarks in FSYNC mode. The cause needs to be investigated and fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10397) SQL Schema may be lost after cluster activation and simple query run
[
https://issues.apache.org/jira/browse/IGNITE-10397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko updated IGNITE-10397:
-
Component/s: cache
> SQL Schema may be lost after cluster activation and simple query run
>
>
> Key: IGNITE-10397
> URL: https://issues.apache.org/jira/browse/IGNITE-10397
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.8
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Critical
> Fix For: 2.8
>
>
> Scenario:
> 1) Start 3 grids in a multithread mode with auto-activation.
> 2) Start the client.
> 3) Run a simple query like this
> {noformat}
> cache(DEFAULT_CACHE_NAME + 0).query(new SqlQuery<>(Integer.class,
> "1=1")).getAll();
> {noformat}
> Exception with the message that schema not found will be thrown:
> {noformat}
> [2018-11-23
> 19:56:57,284][ERROR][query-#223%distributed.CacheMessageStatsIndexingTest2%][GridMapQueryExecutor]
> Failed to execute local query.
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to set schema for DB connection for thread [schema=default0]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:549)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:392)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:767)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:637)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:224)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor$2.onMessage(GridMapQueryExecutor.java:184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2333)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.h2.jdbc.JdbcSQLException: Schema "default0" not found; SQL
> statement:
> SET SCHEMA "default0" [90079-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.engine.Database.getSchema(Database.java:1755)
> at org.h2.command.dml.Set.update(Set.java:408)
> at org.h2.command.CommandContainer.update(CommandContainer.java:101)
> at org.h2.command.Command.executeUpdate(Command.java:260)
> at org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:137)
> at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:122)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:541)
> ... 13 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10397) SQL Schema may be lost after cluster activation and simple query run
[ https://issues.apache.org/jira/browse/IGNITE-10397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697384#comment-16697384 ] ASF GitHub Bot commented on IGNITE-10397: - GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/5491 IGNITE-10397 Fix for 2.5 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10397-2.5 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5491.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5491 commit 702c31859251738b187e8db2a8155264f39b8b52 Author: Ivan Daschinskiy Date: 2018-07-23T12:29:08Z IGNITE-8820 Fix rollback logic when tx is initiated from client. - Fixes #4399. Signed-off-by: Alexey Goncharuk (cherry picked from commit 5794eb0) commit 32777e77797f4cf3260d42d4ca408336247d4e55 Author: Dmitriy Govorukhin Date: 2018-07-23T15:01:37Z IGNITE-9049 Fixed write of SWITCH_SEGMENT_RECORD at the end of a segment file - Fixes #4401. Signed-off-by: Alexey Goncharuk (cherry picked from commit 713a428) commit bbf8f83afe3b07e807912d9bab78873edf698d4d Author: Andrey V. Mashenkov Date: 2018-07-24T14:38:34Z IGNITE-8892 Fixed CacheQueryFuture usage in DataStructures processor - Fixes #4415. Signed-off-by: Alexey Goncharuk (cherry picked from commit 281a400) commit e0404913088b5cd97cd79de1b62e6aaa4c00b5d2 Author: Andrey V. Mashenkov Date: 2018-07-24T15:24:57Z Merge remote-tracking branch 'origin/ignite-2.5.1-master' into ignite-2.5.1-master commit 86c52700a007368a351ac3595a8e38bb02923080 Author: Sergey Chugunov Date: 2018-07-25T13:26:12Z IGNITE-9040 StopNodeFailureHandler is not able to stop node correctly on node segmentation Signed-off-by: Andrey Gura (cherry-picked from commit#469aaba59c0539507972f4725642b2f2f81c08a0) commit e1c3cc9d30baeaff4e653751775ab39a347b753b Author: Pavel Kovalenko Date: 2018-07-24T14:48:57Z IGNITE-8791 Fixed missed update counter in WAL data record for backup transaction - Fixes #4264. Signed-off-by: Alexey Goncharuk (cherry picked from commit 13e2a31) commit 2ea5b376d895fe41cc882c4383b5d3d2793ba684 Author: devozerov Date: 2018-07-31T09:53:51Z IGNITE-9114: SQL: fail query after some timeout if it cannot be mapped to topology. This closes #4453. commit 5b230b7015148e483136c229c9e6081bb9c68023 Author: Denis Mekhanikov Date: 2018-04-20T15:41:06Z IGNITE-8134 Subscribe to system cache events on nodes outside BLT Signed-off-by: Andrey Gura (cherry picked from commit c82277e) commit 2528435ec946c479f6bf4eb7eaeabf092a0536a3 Author: devozerov Date: 2018-07-31T14:15:49Z IGNITE-9114: SQL: use query time in retry timeout calculation. This closes #4460. commit 98d0ccc729e647a4ad8876e2d29423904e6fa6ca Author: devozerov Date: 2018-07-31T14:18:49Z Merge remote-tracking branch 'upstream/ignite-2.5.1-master' into ignite-2.5.1-master commit c78a7f215699f65983edfcc0c9014d9e3108f381 Author: Anton Kalashnikov Date: 2018-08-01T09:23:03Z IGNITE-8757 idle_verify utility doesn't show both update counter and hash conflicts (cherry picked from commit 9131e4d) commit 66369583096b04d71c3f82e1ebfd1922ae6b0b6a Author: Anton Kalashnikov Date: 2018-07-31T13:13:27Z IGNITE-8973 Calculate partition hash and print into standard output Signed-off-by: Andrey Gura (cherry picked from commit 8309cef) commit e92788d392d4c60f76c4fd0f38c52669f4e3e772 Author: Evgeny Stanilovskiy Date: 2018-08-01T11:05:58Z IGNITE-8939 Catch and proper propagate transaction string reprsentation - Fixes #4454. Signed-off-by: Dmitriy Pavlov (cherry picked from commit 458480c5b0520aa8e28935361a37ab49e1e65ff6) commit 60155cb55ca35790da7f80ae167dd7fb3f3793fd Author: Andrey V. Mashenkov Date: 2018-08-01T10:23:32Z IGNITE-9154: Fixed conflict version passed to events for ATOMIC cache. This closes #4463. (cherry picked from commit 3ea3a56) commit 15d72fc022f64939fee336438256460024ca59c0 Author: Andrey V. Mashenkov Date: 2018-08-01T12:58:22Z Merge remote-tracking branch 'origin/ignite-2.5.1-master' into ignite-2.5.1-master commit 158f36de551e860176ac7f3bcf92e9751039a35c Author: ilantukh Date: 2018-08-01T13:31:15Z IGNITE-8900 SqlFieldsQuery provides incorrect result when item size exceeds page size. (cherry picked from commit f1ecbbc) commit ef331f3ba58da49746f34546f1972cf65c083b3d Author: Maxim Muzafarov Date: 2018-08-01T15:39:54Z IGNITE-7165 Re-balancing is cancelled if client node joins Signed-off-by: Anton Vinogradov (cherry
[jira] [Created] (IGNITE-10397) SQL Schema may be lost after cluster activation and simple query run
Pavel Kovalenko created IGNITE-10397:
Summary: SQL Schema may be lost after cluster activation and
simple query run
Key: IGNITE-10397
URL: https://issues.apache.org/jira/browse/IGNITE-10397
Project: Ignite
Issue Type: Bug
Affects Versions: 2.8
Reporter: Pavel Kovalenko
Assignee: Pavel Kovalenko
Fix For: 2.8
Scenario:
1) Start 3 grids in a multithread mode with auto-activation.
2) Start the client.
3) Run a simple query like this
{noformat}
cache(DEFAULT_CACHE_NAME + 0).query(new SqlQuery<>(Integer.class,
"1=1")).getAll();
{noformat}
Exception with the message that schema not found will be thrown:
{noformat}
[2018-11-23
19:56:57,284][ERROR][query-#223%distributed.CacheMessageStatsIndexingTest2%][GridMapQueryExecutor]
Failed to execute local query.
class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
set schema for DB connection for thread [schema=default0]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:549)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:392)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:767)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:637)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:224)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor$2.onMessage(GridMapQueryExecutor.java:184)
at
org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2333)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.h2.jdbc.JdbcSQLException: Schema "default0" not found; SQL
statement:
SET SCHEMA "default0" [90079-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.engine.Database.getSchema(Database.java:1755)
at org.h2.command.dml.Set.update(Set.java:408)
at org.h2.command.CommandContainer.update(CommandContainer.java:101)
at org.h2.command.Command.executeUpdate(Command.java:260)
at org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:137)
at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:122)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:541)
... 13 more
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10339) Connection to cluster failed in control.sh while using --cache
[ https://issues.apache.org/jira/browse/IGNITE-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697351#comment-16697351 ] ASF GitHub Bot commented on IGNITE-10339: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5475 > Connection to cluster failed in control.sh while using --cache > -- > > Key: IGNITE-10339 > URL: https://issues.apache.org/jira/browse/IGNITE-10339 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.8 > > > This issue is related to https://issues.apache.org/jira/browse/IGNITE-8423 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10381) U.doInParallel can terminate early due to an error in batch processing
[
https://issues.apache.org/jira/browse/IGNITE-10381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697329#comment-16697329
]
ASF GitHub Bot commented on IGNITE-10381:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5483
> U.doInParallel can terminate early due to an error in batch processing
> --
>
> Key: IGNITE-10381
> URL: https://issues.apache.org/jira/browse/IGNITE-10381
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8
>
>
> Originally the issue was spotted due to intermittent Cache 7 suite hang with
> the following critical failure:
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:695)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$beforeExchange$ec1c537d$1(GridCacheDatabaseSharedManager.java:1281)
> at
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10840)
> at
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10763)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1268)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1405)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:805)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2864)
> ... 3 more
> {code}
> Further debugging revealed that the NPE is caused due to a race appeared
> because {{U.doInParallel}} may terminate early due to an exception thrown
> inside of one of the closures, but other threads still working.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10339) Connection to cluster failed in control.sh while using --cache
[ https://issues.apache.org/jira/browse/IGNITE-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697341#comment-16697341 ] Alexey Goncharuk commented on IGNITE-10339: --- Merged the second PR. > Connection to cluster failed in control.sh while using --cache > -- > > Key: IGNITE-10339 > URL: https://issues.apache.org/jira/browse/IGNITE-10339 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.8 > > > This issue is related to https://issues.apache.org/jira/browse/IGNITE-8423 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10396) IgniteCache Key class with HashMap field doesn't recognized in some cases
PetrovMikhail created IGNITE-10396: -- Summary: IgniteCache Key class with HashMap field doesn't recognized in some cases Key: IGNITE-10396 URL: https://issues.apache.org/jira/browse/IGNITE-10396 Project: Ignite Issue Type: Bug Environment: [^IgniteCacheRemoveTest.java] Reporter: PetrovMikhail Attachments: IgniteCacheRemoveTest.java IgniteCache#containsKey or IgniteCache#remove methods return false when in their parameters passed instance of key class produced via cache iterator. Even in so situation when IgniteCache.Entry with such key is existing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10392) Client broken cluster where try to connect. Server nodes drop by handler
[
https://issues.apache.org/jira/browse/IGNITE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697322#comment-16697322
]
Ilya Lantukh commented on IGNITE-10392:
---
The aforementioned test failures are known issues.
> Client broken cluster where try to connect. Server nodes drop by handler
>
>
> Key: IGNITE-10392
> URL: https://issues.apache.org/jira/browse/IGNITE-10392
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Blocker
> Fix For: 2.8
>
>
> {noformat}
> org.apache.ignite.IgniteException: Failed to resolve nodes topology
> [cacheGrp=N/A, topVer=AffinityTopologyVersion [topVer=133, minorTopVer=0],
> history=[AffinityTopologyVersion [topVer=35, minorTopVer=0],
> AffinityTopologyVersion [topVer=36, minorTopVer=0], AffinityTopologyVersion
> [topVer=37, minorTopVer=0], AffinityTopologyVersion [topVer=38,
> minorTopVer=0], AffinityTopologyVersion [topVer=39, minorTopVer=0],
> AffinityTopologyVersion [topVer=40, minorTopVer=0], AffinityTopologyVersion
> [topVer=41, minorTopVer=0], AffinityTopologyVersion [topVer=42,
> minorTopVer=0], AffinityTopologyVersion [topVer=43, minorTopVer=0],
> AffinityTopologyVersion [topVer=44, minorTopVer=0], AffinityTopologyVersion
> [topVer=45, minorTopVer=0], AffinityTopologyVersion [topVer=46,
> minorTopVer=0], AffinityTopologyVersion [topVer=47, minorTopVer=0],
> AffinityTopologyVersion [topVer=48, minorTopVer=0], AffinityTopologyVersion
> [topVer=49, minorTopVer=0], AffinityTopologyVersion [topVer=50,
> minorTopVer=0], AffinityTopologyVersion [topVer=51, minorTopVer=0],
> AffinityTopologyVersion [topVer=52, minorTopVer=0], AffinityTopologyVersion
> [topVer=53, minorTopVer=0], AffinityTopologyVersion [topVer=54,
> minorTopVer=0], AffinityTopologyVersion [topVer=55, minorTopVer=0],
> AffinityTopologyVersion [topVer=56, minorTopVer=0], AffinityTopologyVersion
> [topVer=57, minorTopVer=0], AffinityTopologyVersion [topVer=58,
> minorTopVer=0], AffinityTopologyVersion [topVer=59, minorTopVer=0],
> AffinityTopologyVersion [topVer=60, minorTopVer=0], AffinityTopologyVersion
> [topVer=61, minorTopVer=0], AffinityTopologyVersion [topVer=62,
> minorTopVer=0], AffinityTopologyVersion [topVer=63, minorTopVer=0],
> AffinityTopologyVersion [topVer=64, minorTopVer=0], AffinityTopologyVersion
> [topVer=65, minorTopVer=0], AffinityTopologyVersion [topVer=66,
> minorTopVer=0], AffinityTopologyVersion [topVer=67, minorTopVer=0],
> AffinityTopologyVersion [topVer=68, minorTopVer=0], AffinityTopologyVersion
> [topVer=69, minorTopVer=0], AffinityTopologyVersion [topVer=70,
> minorTopVer=0], AffinityTopologyVersion [topVer=71, minorTopVer=0],
> AffinityTopologyVersion [topVer=72, minorTopVer=0], AffinityTopologyVersion
> [topVer=73, minorTopVer=0], AffinityTopologyVersion [topVer=74,
> minorTopVer=0], AffinityTopologyVersion [topVer=75, minorTopVer=0],
> AffinityTopologyVersion [topVer=76, minorTopVer=0], AffinityTopologyVersion
> [topVer=77, minorTopVer=0], AffinityTopologyVersion [topVer=78,
> minorTopVer=0], AffinityTopologyVersion [topVer=79, minorTopVer=0],
> AffinityTopologyVersion [topVer=80, minorTopVer=0], AffinityTopologyVersion
> [topVer=81, minorTopVer=0], AffinityTopologyVersion [topVer=82,
> minorTopVer=0], AffinityTopologyVersion [topVer=83, minorTopVer=0],
> AffinityTopologyVersion [topVer=84, minorTopVer=0], AffinityTopologyVersion
> [topVer=85, minorTopVer=0], AffinityTopologyVersion [topVer=86,
> minorTopVer=0], AffinityTopologyVersion [topVer=87, minorTopVer=0],
> AffinityTopologyVersion [topVer=88, minorTopVer=0], AffinityTopologyVersion
> [topVer=89, minorTopVer=0], AffinityTopologyVersion [topVer=90,
> minorTopVer=0], AffinityTopologyVersion [topVer=91, minorTopVer=0],
> AffinityTopologyVersion [topVer=92, minorTopVer=0], AffinityTopologyVersion
> [topVer=93, minorTopVer=0], AffinityTopologyVersion [topVer=94,
> minorTopVer=0], AffinityTopologyVersion [topVer=95, minorTopVer=0],
> AffinityTopologyVersion [topVer=96, minorTopVer=0], AffinityTopologyVersion
> [topVer=97, minorTopVer=0], AffinityTopologyVersion [topVer=98,
> minorTopVer=0], AffinityTopologyVersion [topVer=99, minorTopVer=0],
> AffinityTopologyVersion [topVer=100, minorTopVer=0], AffinityTopologyVersion
> [topVer=101, minorTopVer=0], AffinityTopologyVersion [topVer=102,
> minorTopVer=0], AffinityTopologyVersion [topVer=103, minorTopVer=0],
> AffinityTopologyVersion [topVer=104, minorTopVer=0], AffinityTopologyVersion
> [topVer=105, minorTopVer=0], AffinityTopologyVersion [topVer=106,
> minorTopVer=0], AffinityTopologyVersion [topVer=107, minorTopVer=0],
> AffinityTopologyVersion [topVer=108, minorTopVer=0], AffinityTopologyVersion
> [topVer=109, minorTopVer=0],
[jira] [Commented] (IGNITE-10392) Client broken cluster where try to connect. Server nodes drop by handler
[
https://issues.apache.org/jira/browse/IGNITE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697312#comment-16697312
]
Ignite TC Bot commented on IGNITE-10392:
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Queries{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2388223]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testAccountsTxSql_SingleNode_CoordinatorFails_Persistence
- 0,0% fails in last 100 master runs.
{color:#d04437}PDS (Indexing){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2388256]]
* IgnitePdsWithIndexingCoreTestSuite:
IgnitePdsThreadInterruptionTest.testInterruptsOnLFSRead - 0,0% fails in last
100 master runs.
{color:#d04437}Continuous Query 2{color} [[tests 0 CANCELLED, Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2388184]]
* CacheContinuousQueryFailoverMvccTxSelfTest.testFailoverStartStopBackup (last
started)
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2388274buildTypeId=IgniteTests24Java8_RunAll]
> Client broken cluster where try to connect. Server nodes drop by handler
>
>
> Key: IGNITE-10392
> URL: https://issues.apache.org/jira/browse/IGNITE-10392
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Blocker
> Fix For: 2.8
>
>
> {noformat}
> org.apache.ignite.IgniteException: Failed to resolve nodes topology
> [cacheGrp=N/A, topVer=AffinityTopologyVersion [topVer=133, minorTopVer=0],
> history=[AffinityTopologyVersion [topVer=35, minorTopVer=0],
> AffinityTopologyVersion [topVer=36, minorTopVer=0], AffinityTopologyVersion
> [topVer=37, minorTopVer=0], AffinityTopologyVersion [topVer=38,
> minorTopVer=0], AffinityTopologyVersion [topVer=39, minorTopVer=0],
> AffinityTopologyVersion [topVer=40, minorTopVer=0], AffinityTopologyVersion
> [topVer=41, minorTopVer=0], AffinityTopologyVersion [topVer=42,
> minorTopVer=0], AffinityTopologyVersion [topVer=43, minorTopVer=0],
> AffinityTopologyVersion [topVer=44, minorTopVer=0], AffinityTopologyVersion
> [topVer=45, minorTopVer=0], AffinityTopologyVersion [topVer=46,
> minorTopVer=0], AffinityTopologyVersion [topVer=47, minorTopVer=0],
> AffinityTopologyVersion [topVer=48, minorTopVer=0], AffinityTopologyVersion
> [topVer=49, minorTopVer=0], AffinityTopologyVersion [topVer=50,
> minorTopVer=0], AffinityTopologyVersion [topVer=51, minorTopVer=0],
> AffinityTopologyVersion [topVer=52, minorTopVer=0], AffinityTopologyVersion
> [topVer=53, minorTopVer=0], AffinityTopologyVersion [topVer=54,
> minorTopVer=0], AffinityTopologyVersion [topVer=55, minorTopVer=0],
> AffinityTopologyVersion [topVer=56, minorTopVer=0], AffinityTopologyVersion
> [topVer=57, minorTopVer=0], AffinityTopologyVersion [topVer=58,
> minorTopVer=0], AffinityTopologyVersion [topVer=59, minorTopVer=0],
> AffinityTopologyVersion [topVer=60, minorTopVer=0], AffinityTopologyVersion
> [topVer=61, minorTopVer=0], AffinityTopologyVersion [topVer=62,
> minorTopVer=0], AffinityTopologyVersion [topVer=63, minorTopVer=0],
> AffinityTopologyVersion [topVer=64, minorTopVer=0], AffinityTopologyVersion
> [topVer=65, minorTopVer=0], AffinityTopologyVersion [topVer=66,
> minorTopVer=0], AffinityTopologyVersion [topVer=67, minorTopVer=0],
> AffinityTopologyVersion [topVer=68, minorTopVer=0], AffinityTopologyVersion
> [topVer=69, minorTopVer=0], AffinityTopologyVersion [topVer=70,
> minorTopVer=0], AffinityTopologyVersion [topVer=71, minorTopVer=0],
> AffinityTopologyVersion [topVer=72, minorTopVer=0], AffinityTopologyVersion
> [topVer=73, minorTopVer=0], AffinityTopologyVersion [topVer=74,
> minorTopVer=0], AffinityTopologyVersion [topVer=75, minorTopVer=0],
> AffinityTopologyVersion [topVer=76, minorTopVer=0], AffinityTopologyVersion
> [topVer=77, minorTopVer=0], AffinityTopologyVersion [topVer=78,
> minorTopVer=0], AffinityTopologyVersion [topVer=79, minorTopVer=0],
> AffinityTopologyVersion [topVer=80, minorTopVer=0], AffinityTopologyVersion
> [topVer=81, minorTopVer=0], AffinityTopologyVersion [topVer=82,
> minorTopVer=0], AffinityTopologyVersion [topVer=83, minorTopVer=0],
> AffinityTopologyVersion [topVer=84, minorTopVer=0], AffinityTopologyVersion
> [topVer=85, minorTopVer=0], AffinityTopologyVersion [topVer=86,
> minorTopVer=0], AffinityTopologyVersion [topVer=87, minorTopVer=0],
> AffinityTopologyVersion [topVer=88, minorTopVer=0], AffinityTopologyVersion
> [topVer=89, minorTopVer=0], AffinityTopologyVersion [topVer=90,
> minorTopVer=0], AffinityTopologyVersion [topVer=91, minorTopVer=0],
> AffinityTopologyVersion [topVer=92, minorTopVer=0],
[jira] [Commented] (IGNITE-10381) U.doInParallel can terminate early due to an error in batch processing
[
https://issues.apache.org/jira/browse/IGNITE-10381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697314#comment-16697314
]
Ignite TC Bot commented on IGNITE-10381:
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2380691buildTypeId=IgniteTests24Java8_RunAll]
> U.doInParallel can terminate early due to an error in batch processing
> --
>
> Key: IGNITE-10381
> URL: https://issues.apache.org/jira/browse/IGNITE-10381
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8
>
>
> Originally the issue was spotted due to intermittent Cache 7 suite hang with
> the following critical failure:
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:695)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$beforeExchange$ec1c537d$1(GridCacheDatabaseSharedManager.java:1281)
> at
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10840)
> at
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10763)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1268)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1405)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:805)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2864)
> ... 3 more
> {code}
> Further debugging revealed that the NPE is caused due to a race appeared
> because {{U.doInParallel}} may terminate early due to an exception thrown
> inside of one of the closures, but other threads still working.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9489) CorruptedTreeException on index create.
[
https://issues.apache.org/jira/browse/IGNITE-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9489:
Priority: Blocker (was: Major)
> CorruptedTreeException on index create.
> ---
>
> Key: IGNITE-9489
> URL: https://issues.apache.org/jira/browse/IGNITE-9489
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Affects Versions: 2.4, 2.5, 2.6
>Reporter: Igor Seliverstov
>Priority: Blocker
> Fix For: 2.8
>
> Attachments: Test.java
>
>
> Currently on dynamic index drop with enabled persistence H2TreeIndex
> instances aren't destroyed. That means that their root pages aren't removed
> from meta tree (see
> {{org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl#getOrAllocateForTree}})
> and reused on subsequent dynamic index create that leads
> CorruptedTreeException on initial index rebuild because there are some items
> with broken links on the root page.
> Reproducer attached.
> Error log:
> {noformat}
> Error during parallel index create/rebuild.
> org.h2.message.DbException: Внутренняя ошибка: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> General error: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> [5-195]
> at org.h2.message.DbException.get(DbException.java:168)
> at org.h2.message.DbException.convert(DbException.java:295)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:251)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.apply(IgniteH2Indexing.java:890)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.updateIndex(GridCacheMapEntry.java:4320)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processKey(SchemaIndexCacheVisitorImpl.java:244)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartition(SchemaIndexCacheVisitorImpl.java:207)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartitions(SchemaIndexCacheVisitorImpl.java:166)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.access$100(SchemaIndexCacheVisitorImpl.java:50)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl$AsyncWorker.body(SchemaIndexCacheVisitorImpl.java:317)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.h2.jdbc.JdbcSQLException: Внутренняя ошибка: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> General error: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> [5-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 12 more
> Caused by: class
>
[jira] [Comment Edited] (IGNITE-10358) thin python: put collections have no data type specification
[ https://issues.apache.org/jira/browse/IGNITE-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697285#comment-16697285 ] Stepan Pilschikov edited comment on IGNITE-10358 at 11/23/18 3:38 PM: -- [~Melnichuk] Great Problem with collections is solved All types in all But in this branch i find out that python working bad with Decimal's Example with output: https://gist.github.com/pilshchikov/335db29e6e748c6ce334e0cb6251179e This behavior same for NodeJS, PHP, Java and affecting all special types (Collections, Arrays, Maps) Master branch does not have this issue Or im doing something wrong? For same problem with data type "Map" i should create another ticket? was (Author: spilschikov): [~Melnichuk] Great Problem with collections is solved All types in all But in this branch i find out that python working bad with Decimal's Example with output: https://gist.github.com/pilshchikov/335db29e6e748c6ce334e0cb6251179e This behavior same for NodeJS, PHP, Java and affecting all special types (Collections, Arrays, Maps) Master branch does not have this issue For same problem with data type "Map" i should create another ticket? > thin python: put collections have no data type specification > > > Key: IGNITE-10358 > URL: https://issues.apache.org/jira/browse/IGNITE-10358 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: Dmitry Melnichuk >Priority: Major > Labels: python > Fix For: 2.8 > > > Trying to put collection with Integers through python thin client and get > through others clients > Value type in others clients specified as "collection with Integers" > > During GET operation clients throwing exceptions that "type wrong, expected > Integer type but getting Long type" (because python collection data types are > not specified) > Python put and php and js get code/output: > https://gist.github.com/pilshchikov/7ba7a7a2568c758b7b8680ba9a4215f5 > Also same behavior right for Map data type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10358) thin python: put collections have no data type specification
[ https://issues.apache.org/jira/browse/IGNITE-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697285#comment-16697285 ] Stepan Pilschikov commented on IGNITE-10358: [~Melnichuk] Great Problem with collections is solved All types in all But in this branch i find out that python working bad with Decimal's Example with output: https://gist.github.com/pilshchikov/335db29e6e748c6ce334e0cb6251179e This behavior same for NodeJS, PHP, Java and affecting all special types (Collections, Arrays, Maps) Master branch does not have this issue For same problem with data type "Map" i should create another ticket? > thin python: put collections have no data type specification > > > Key: IGNITE-10358 > URL: https://issues.apache.org/jira/browse/IGNITE-10358 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: Dmitry Melnichuk >Priority: Major > Labels: python > Fix For: 2.8 > > > Trying to put collection with Integers through python thin client and get > through others clients > Value type in others clients specified as "collection with Integers" > > During GET operation clients throwing exceptions that "type wrong, expected > Integer type but getting Long type" (because python collection data types are > not specified) > Python put and php and js get code/output: > https://gist.github.com/pilshchikov/7ba7a7a2568c758b7b8680ba9a4215f5 > Also same behavior right for Map data type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4618) CPP: Do not start JVM if it is already started
[ https://issues.apache.org/jira/browse/IGNITE-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-4618: --- Assignee: (was: Igor Sapego) > CPP: Do not start JVM if it is already started > -- > > Key: IGNITE-4618 > URL: https://issues.apache.org/jira/browse/IGNITE-4618 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.8 >Reporter: Vladimir Ozerov >Priority: Major > Labels: cpp > > *Problem* > Consider the following scenario: > 1) User's app started JVM in the process somehow. > 2) User tries to start the node. > 3) Result: exception. > *Solution* > We need to check if JVM is already started. If yes - then try re-using. Note > that we are likely to fail at this point because user might forgot to pass > proper Ignite classpath. In this case we must throw extremely sensible > exception, so that user understand how to fix the problem right away. > E.g.: "Failed to start Ignite node with already started JVM due to invalid > classpath; please add the following JARs to the classpath: [PATH TO > IGNITE_HOME JARS]". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4618) CPP: Do not start JVM if it is already started
[ https://issues.apache.org/jira/browse/IGNITE-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-4618: --- Assignee: Igor Sapego > CPP: Do not start JVM if it is already started > -- > > Key: IGNITE-4618 > URL: https://issues.apache.org/jira/browse/IGNITE-4618 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.8 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Major > Labels: cpp > > *Problem* > Consider the following scenario: > 1) User's app started JVM in the process somehow. > 2) User tries to start the node. > 3) Result: exception. > *Solution* > We need to check if JVM is already started. If yes - then try re-using. Note > that we are likely to fail at this point because user might forgot to pass > proper Ignite classpath. In this case we must throw extremely sensible > exception, so that user understand how to fix the problem right away. > E.g.: "Failed to start Ignite node with already started JVM due to invalid > classpath; please add the following JARs to the classpath: [PATH TO > IGNITE_HOME JARS]". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7441) Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property
[ https://issues.apache.org/jira/browse/IGNITE-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697280#comment-16697280 ] Vyacheslav Daradur commented on IGNITE-7441: [~dmekhanikov], thanks! [~NIzhikov], could you help with the merge, please? > Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property > --- > > Key: IGNITE-7441 > URL: https://issues.apache.org/jira/browse/IGNITE-7441 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Denis Mekhanikov >Assignee: Vyacheslav Daradur >Priority: Minor > Fix For: 2.8 > > > IGNITE_SERVICES_COMPATIBILITY_MODE system property was introduced to > configure backward compatibility mode for service configuration classes. But > since it was done in 1.9 and current version is completely incompatible with > it, there is no point in keeping this property. > Moreover, it is ignored after IGNITE-5145. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7441) Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property
[ https://issues.apache.org/jira/browse/IGNITE-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697266#comment-16697266 ] Denis Mekhanikov commented on IGNITE-7441: -- Changes look good to me. > Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property > --- > > Key: IGNITE-7441 > URL: https://issues.apache.org/jira/browse/IGNITE-7441 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Denis Mekhanikov >Assignee: Vyacheslav Daradur >Priority: Minor > Fix For: 2.8 > > > IGNITE_SERVICES_COMPATIBILITY_MODE system property was introduced to > configure backward compatibility mode for service configuration classes. But > since it was done in 1.9 and current version is completely incompatible with > it, there is no point in keeping this property. > Moreover, it is ignored after IGNITE-5145. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10339) Connection to cluster failed in control.sh while using --cache
[ https://issues.apache.org/jira/browse/IGNITE-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697264#comment-16697264 ] Sergey Antonov commented on IGNITE-10339: - [~ivandasch] looks good for me. > Connection to cluster failed in control.sh while using --cache > -- > > Key: IGNITE-10339 > URL: https://issues.apache.org/jira/browse/IGNITE-10339 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.8 > > > This issue is related to https://issues.apache.org/jira/browse/IGNITE-8423 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10392) Client broken cluster where try to connect. Server nodes drop by handler
[
https://issues.apache.org/jira/browse/IGNITE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-10392:
--
Ignite Flags: (was: Docs Required)
> Client broken cluster where try to connect. Server nodes drop by handler
>
>
> Key: IGNITE-10392
> URL: https://issues.apache.org/jira/browse/IGNITE-10392
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Blocker
> Fix For: 2.8
>
>
> {noformat}
> org.apache.ignite.IgniteException: Failed to resolve nodes topology
> [cacheGrp=N/A, topVer=AffinityTopologyVersion [topVer=133, minorTopVer=0],
> history=[AffinityTopologyVersion [topVer=35, minorTopVer=0],
> AffinityTopologyVersion [topVer=36, minorTopVer=0], AffinityTopologyVersion
> [topVer=37, minorTopVer=0], AffinityTopologyVersion [topVer=38,
> minorTopVer=0], AffinityTopologyVersion [topVer=39, minorTopVer=0],
> AffinityTopologyVersion [topVer=40, minorTopVer=0], AffinityTopologyVersion
> [topVer=41, minorTopVer=0], AffinityTopologyVersion [topVer=42,
> minorTopVer=0], AffinityTopologyVersion [topVer=43, minorTopVer=0],
> AffinityTopologyVersion [topVer=44, minorTopVer=0], AffinityTopologyVersion
> [topVer=45, minorTopVer=0], AffinityTopologyVersion [topVer=46,
> minorTopVer=0], AffinityTopologyVersion [topVer=47, minorTopVer=0],
> AffinityTopologyVersion [topVer=48, minorTopVer=0], AffinityTopologyVersion
> [topVer=49, minorTopVer=0], AffinityTopologyVersion [topVer=50,
> minorTopVer=0], AffinityTopologyVersion [topVer=51, minorTopVer=0],
> AffinityTopologyVersion [topVer=52, minorTopVer=0], AffinityTopologyVersion
> [topVer=53, minorTopVer=0], AffinityTopologyVersion [topVer=54,
> minorTopVer=0], AffinityTopologyVersion [topVer=55, minorTopVer=0],
> AffinityTopologyVersion [topVer=56, minorTopVer=0], AffinityTopologyVersion
> [topVer=57, minorTopVer=0], AffinityTopologyVersion [topVer=58,
> minorTopVer=0], AffinityTopologyVersion [topVer=59, minorTopVer=0],
> AffinityTopologyVersion [topVer=60, minorTopVer=0], AffinityTopologyVersion
> [topVer=61, minorTopVer=0], AffinityTopologyVersion [topVer=62,
> minorTopVer=0], AffinityTopologyVersion [topVer=63, minorTopVer=0],
> AffinityTopologyVersion [topVer=64, minorTopVer=0], AffinityTopologyVersion
> [topVer=65, minorTopVer=0], AffinityTopologyVersion [topVer=66,
> minorTopVer=0], AffinityTopologyVersion [topVer=67, minorTopVer=0],
> AffinityTopologyVersion [topVer=68, minorTopVer=0], AffinityTopologyVersion
> [topVer=69, minorTopVer=0], AffinityTopologyVersion [topVer=70,
> minorTopVer=0], AffinityTopologyVersion [topVer=71, minorTopVer=0],
> AffinityTopologyVersion [topVer=72, minorTopVer=0], AffinityTopologyVersion
> [topVer=73, minorTopVer=0], AffinityTopologyVersion [topVer=74,
> minorTopVer=0], AffinityTopologyVersion [topVer=75, minorTopVer=0],
> AffinityTopologyVersion [topVer=76, minorTopVer=0], AffinityTopologyVersion
> [topVer=77, minorTopVer=0], AffinityTopologyVersion [topVer=78,
> minorTopVer=0], AffinityTopologyVersion [topVer=79, minorTopVer=0],
> AffinityTopologyVersion [topVer=80, minorTopVer=0], AffinityTopologyVersion
> [topVer=81, minorTopVer=0], AffinityTopologyVersion [topVer=82,
> minorTopVer=0], AffinityTopologyVersion [topVer=83, minorTopVer=0],
> AffinityTopologyVersion [topVer=84, minorTopVer=0], AffinityTopologyVersion
> [topVer=85, minorTopVer=0], AffinityTopologyVersion [topVer=86,
> minorTopVer=0], AffinityTopologyVersion [topVer=87, minorTopVer=0],
> AffinityTopologyVersion [topVer=88, minorTopVer=0], AffinityTopologyVersion
> [topVer=89, minorTopVer=0], AffinityTopologyVersion [topVer=90,
> minorTopVer=0], AffinityTopologyVersion [topVer=91, minorTopVer=0],
> AffinityTopologyVersion [topVer=92, minorTopVer=0], AffinityTopologyVersion
> [topVer=93, minorTopVer=0], AffinityTopologyVersion [topVer=94,
> minorTopVer=0], AffinityTopologyVersion [topVer=95, minorTopVer=0],
> AffinityTopologyVersion [topVer=96, minorTopVer=0], AffinityTopologyVersion
> [topVer=97, minorTopVer=0], AffinityTopologyVersion [topVer=98,
> minorTopVer=0], AffinityTopologyVersion [topVer=99, minorTopVer=0],
> AffinityTopologyVersion [topVer=100, minorTopVer=0], AffinityTopologyVersion
> [topVer=101, minorTopVer=0], AffinityTopologyVersion [topVer=102,
> minorTopVer=0], AffinityTopologyVersion [topVer=103, minorTopVer=0],
> AffinityTopologyVersion [topVer=104, minorTopVer=0], AffinityTopologyVersion
> [topVer=105, minorTopVer=0], AffinityTopologyVersion [topVer=106,
> minorTopVer=0], AffinityTopologyVersion [topVer=107, minorTopVer=0],
> AffinityTopologyVersion [topVer=108, minorTopVer=0], AffinityTopologyVersion
> [topVer=109, minorTopVer=0], AffinityTopologyVersion [topVer=110,
>
[jira] [Commented] (IGNITE-8718) Documentation about using of the C++ BinaryWriter/BinaryReader should be updated
[
https://issues.apache.org/jira/browse/IGNITE-8718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697259#comment-16697259
]
ASF GitHub Bot commented on IGNITE-8718:
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/5490
IGNITE-8718: Updated C++ doxygen comments about BinaryWriter/BinaryReader
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8718
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5490.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5490
commit a8d8637bb342a6e4e254d755fbcd11d90a02ba97
Author: Igor Sapego
Date: 2018-11-23T14:31:13Z
IGNITE-8718: Fixed comments for BinaryWriter
commit 79729136d648bd7c65a68cf67e9017c20bb32b7f
Author: Igor Sapego
Date: 2018-11-23T15:02:26Z
IGNITE-8718: Added comments for BinaryReader and BinaryRawReader
> Documentation about using of the C++ BinaryWriter/BinaryReader should be
> updated
>
>
> Key: IGNITE-8718
> URL: https://issues.apache.org/jira/browse/IGNITE-8718
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.5
>Reporter: Andrey Aleksandrov
>Assignee: Igor Sapego
>Priority: Major
> Labels: c++
> Fix For: 2.7
>
>
> The usage that should be documented:
> 1)In case if you get some writer from BinaryWriter then you started writing
> session. Until method close will not be called for this writer you can't get
> another writer.
>
> For example, next code isn't correct:
> {code:java}
> BinaryMapWriter field1Writer = writer.WriteMap int64_t>("field1", MapType::HASH_MAP); //here you start writing session
> BinaryMapWriter field2Writer = writer.WriteMap int64_t>("field2", MapType::HASH_MAP); //here you start another writing
> session - error
> {code}
> Should be:
>
> {code:java}
> BinaryMapWriter field1Writer = writer.WriteMap int64_t>("field1", MapType::HASH_MAP); //here you start writing session
> //do something
> field1Writer.Close() //here you end writing session
> BinaryMapWriter field2Writer = writer.WriteMap int64_t>("field2", MapType::HASH_MAP); //here you start another writing
> session
> //do something
> field2Writer.Close() //here you end another writing session
> {code}
>
> 2) In case if you get some reader from BinaryWriter then you started reading
> session. Until something will not be read from this reader you can't get
> another reader.
>
> For example, next code isn't correct:
>
> {code:java}
> BinaryMapReader field1Reader = reader.ReadMap int64_t>("field1"); //start reading session
> BinaryMapReader field2Reader = reader.ReadMap int64_t>("field2"); //start another read session - error
> {code}
> Should be for example:
> {code:java}
> BinaryMapReader field1Reader = reader.ReadMap int64_t>("field1"); //start reading session
> ...
> field1Reader.GetNext(key, val); //reading done
> ...
> BinaryMapReader field2Reader = reader.ReadMap int64_t>("field2"); //start another read session
> ...
> field2Reader.GetNext(key, val); //reading done
> ...{code}
>
>
>
> In the case of the writer, it looks like expected. In case of the reader, it
> looks a little bit confusing.
>
> These two behaviors should be described in the documentation as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10392) Client broken cluster where try to connect. Server nodes drop by handler
[
https://issues.apache.org/jira/browse/IGNITE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697252#comment-16697252
]
Alexey Goncharuk commented on IGNITE-10392:
---
[~ilantukh] looks good.
> Client broken cluster where try to connect. Server nodes drop by handler
>
>
> Key: IGNITE-10392
> URL: https://issues.apache.org/jira/browse/IGNITE-10392
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Blocker
> Fix For: 2.8
>
>
> {noformat}
> org.apache.ignite.IgniteException: Failed to resolve nodes topology
> [cacheGrp=N/A, topVer=AffinityTopologyVersion [topVer=133, minorTopVer=0],
> history=[AffinityTopologyVersion [topVer=35, minorTopVer=0],
> AffinityTopologyVersion [topVer=36, minorTopVer=0], AffinityTopologyVersion
> [topVer=37, minorTopVer=0], AffinityTopologyVersion [topVer=38,
> minorTopVer=0], AffinityTopologyVersion [topVer=39, minorTopVer=0],
> AffinityTopologyVersion [topVer=40, minorTopVer=0], AffinityTopologyVersion
> [topVer=41, minorTopVer=0], AffinityTopologyVersion [topVer=42,
> minorTopVer=0], AffinityTopologyVersion [topVer=43, minorTopVer=0],
> AffinityTopologyVersion [topVer=44, minorTopVer=0], AffinityTopologyVersion
> [topVer=45, minorTopVer=0], AffinityTopologyVersion [topVer=46,
> minorTopVer=0], AffinityTopologyVersion [topVer=47, minorTopVer=0],
> AffinityTopologyVersion [topVer=48, minorTopVer=0], AffinityTopologyVersion
> [topVer=49, minorTopVer=0], AffinityTopologyVersion [topVer=50,
> minorTopVer=0], AffinityTopologyVersion [topVer=51, minorTopVer=0],
> AffinityTopologyVersion [topVer=52, minorTopVer=0], AffinityTopologyVersion
> [topVer=53, minorTopVer=0], AffinityTopologyVersion [topVer=54,
> minorTopVer=0], AffinityTopologyVersion [topVer=55, minorTopVer=0],
> AffinityTopologyVersion [topVer=56, minorTopVer=0], AffinityTopologyVersion
> [topVer=57, minorTopVer=0], AffinityTopologyVersion [topVer=58,
> minorTopVer=0], AffinityTopologyVersion [topVer=59, minorTopVer=0],
> AffinityTopologyVersion [topVer=60, minorTopVer=0], AffinityTopologyVersion
> [topVer=61, minorTopVer=0], AffinityTopologyVersion [topVer=62,
> minorTopVer=0], AffinityTopologyVersion [topVer=63, minorTopVer=0],
> AffinityTopologyVersion [topVer=64, minorTopVer=0], AffinityTopologyVersion
> [topVer=65, minorTopVer=0], AffinityTopologyVersion [topVer=66,
> minorTopVer=0], AffinityTopologyVersion [topVer=67, minorTopVer=0],
> AffinityTopologyVersion [topVer=68, minorTopVer=0], AffinityTopologyVersion
> [topVer=69, minorTopVer=0], AffinityTopologyVersion [topVer=70,
> minorTopVer=0], AffinityTopologyVersion [topVer=71, minorTopVer=0],
> AffinityTopologyVersion [topVer=72, minorTopVer=0], AffinityTopologyVersion
> [topVer=73, minorTopVer=0], AffinityTopologyVersion [topVer=74,
> minorTopVer=0], AffinityTopologyVersion [topVer=75, minorTopVer=0],
> AffinityTopologyVersion [topVer=76, minorTopVer=0], AffinityTopologyVersion
> [topVer=77, minorTopVer=0], AffinityTopologyVersion [topVer=78,
> minorTopVer=0], AffinityTopologyVersion [topVer=79, minorTopVer=0],
> AffinityTopologyVersion [topVer=80, minorTopVer=0], AffinityTopologyVersion
> [topVer=81, minorTopVer=0], AffinityTopologyVersion [topVer=82,
> minorTopVer=0], AffinityTopologyVersion [topVer=83, minorTopVer=0],
> AffinityTopologyVersion [topVer=84, minorTopVer=0], AffinityTopologyVersion
> [topVer=85, minorTopVer=0], AffinityTopologyVersion [topVer=86,
> minorTopVer=0], AffinityTopologyVersion [topVer=87, minorTopVer=0],
> AffinityTopologyVersion [topVer=88, minorTopVer=0], AffinityTopologyVersion
> [topVer=89, minorTopVer=0], AffinityTopologyVersion [topVer=90,
> minorTopVer=0], AffinityTopologyVersion [topVer=91, minorTopVer=0],
> AffinityTopologyVersion [topVer=92, minorTopVer=0], AffinityTopologyVersion
> [topVer=93, minorTopVer=0], AffinityTopologyVersion [topVer=94,
> minorTopVer=0], AffinityTopologyVersion [topVer=95, minorTopVer=0],
> AffinityTopologyVersion [topVer=96, minorTopVer=0], AffinityTopologyVersion
> [topVer=97, minorTopVer=0], AffinityTopologyVersion [topVer=98,
> minorTopVer=0], AffinityTopologyVersion [topVer=99, minorTopVer=0],
> AffinityTopologyVersion [topVer=100, minorTopVer=0], AffinityTopologyVersion
> [topVer=101, minorTopVer=0], AffinityTopologyVersion [topVer=102,
> minorTopVer=0], AffinityTopologyVersion [topVer=103, minorTopVer=0],
> AffinityTopologyVersion [topVer=104, minorTopVer=0], AffinityTopologyVersion
> [topVer=105, minorTopVer=0], AffinityTopologyVersion [topVer=106,
> minorTopVer=0], AffinityTopologyVersion [topVer=107, minorTopVer=0],
> AffinityTopologyVersion [topVer=108, minorTopVer=0], AffinityTopologyVersion
> [topVer=109, minorTopVer=0],
[jira] [Commented] (IGNITE-9406) Improve SQL "Performance and Debugging" page
[ https://issues.apache.org/jira/browse/IGNITE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697244#comment-16697244 ] Artem Budnikov commented on IGNITE-9406: [~vozerov] If I could clarify, I wouldn't have asked you. > Improve SQL "Performance and Debugging" page > > > Key: IGNITE-9406 > URL: https://issues.apache.org/jira/browse/IGNITE-9406 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > Attachments: ignite_sql_perf.txt > > > I prepared a document for one of Ignite clients with some advanced > information about how various performance optimizations work in Ignite SQL. > Let's compare this document with our "Performance and Debugging" page [1], > and enhance the latter with missing info (if any). > P.S.: Document is attached. Russian language. > [1] > https://apacheignite-sql.readme.io/docs/performance-and-debugging#query-execution-flow-optimizations -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9550) Get operation returns null for a lost partition with READ_SAFE policy
[ https://issues.apache.org/jira/browse/IGNITE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697236#comment-16697236 ] ASF GitHub Bot commented on IGNITE-9550: Github user ibessonov closed the pull request at: https://github.com/apache/ignite/pull/4785 > Get operation returns null for a lost partition with READ_SAFE policy > - > > Key: IGNITE-9550 > URL: https://issues.apache.org/jira/browse/IGNITE-9550 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.6 >Reporter: Pavel Vinokurov >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.7 > > Attachments: PartitionLostReproducer.java > > > See reproduced attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10376) NPE during invocation on cache
[ https://issues.apache.org/jira/browse/IGNITE-10376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Fedotov updated IGNITE-10376: -- Summary: NPE during invocation on cache (was: NPE during invocation from cache) > NPE during invocation on cache > -- > > Key: IGNITE-10376 > URL: https://issues.apache.org/jira/browse/IGNITE-10376 > Project: Ignite > Issue Type: Test >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > Labels: MakeTeamcityGreenAgain, stability, test-fail > > Null pointer exception sometimes appears in > [testAtomicOnheapTwoBackupAsyncFullSync|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3300126853696550025=testDetails] > at the > [moment|https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/query/continuous/CacheContinuousQueryOrderingEventTest.java#L371] > of CacheEntryProcessor invocation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10395) Add to control.sh --cache --tx overall info: count of transaction and count of transaction in each state (Rollback, Commiting and etc)
[ https://issues.apache.org/jira/browse/IGNITE-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ARomantsov updated IGNITE-10395: Summary: Add to control.sh --cache --tx overall info: count of transaction and count of transaction in each state (Rollback, Commiting and etc) (was: Add to control.sh --cache --tx overall info:) > Add to control.sh --cache --tx overall info: count of transaction and count > of transaction in each state (Rollback, Commiting and etc) > -- > > Key: IGNITE-10395 > URL: https://issues.apache.org/jira/browse/IGNITE-10395 > Project: Ignite > Issue Type: Improvement >Reporter: ARomantsov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10395) Add to control.sh --cache --tx overall info:
[ https://issues.apache.org/jira/browse/IGNITE-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ARomantsov updated IGNITE-10395: Issue Type: Improvement (was: Bug) > Add to control.sh --cache --tx overall info: > > > Key: IGNITE-10395 > URL: https://issues.apache.org/jira/browse/IGNITE-10395 > Project: Ignite > Issue Type: Improvement >Reporter: ARomantsov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10395) Add to control.sh --cache --tx overall info:
ARomantsov created IGNITE-10395: --- Summary: Add to control.sh --cache --tx overall info: Key: IGNITE-10395 URL: https://issues.apache.org/jira/browse/IGNITE-10395 Project: Ignite Issue Type: Bug Reporter: ARomantsov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10394) Try to activate cluster after deactivate. All node exit by handler
ARomantsov created IGNITE-10394: --- Summary: Try to activate cluster after deactivate. All node exit by handler Key: IGNITE-10394 URL: https://issues.apache.org/jira/browse/IGNITE-10394 Project: Ignite Issue Type: Bug Components: data structures Affects Versions: 2.7 Reporter: ARomantsov AE: ignite-sys-cache ..processors.cache.CacheRegistry.update(CacheRegistry.java:188) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10290) Map.Entry interface for key cache may lead to incorrect hash code calculation
[ https://issues.apache.org/jira/browse/IGNITE-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-10290: Description: If use Map.Entry interface for a key, we can try to find (key, value) in store with incorrect calculated hash code for binary representation, it lead to result null. The problem is in the GridPartitionedSingleGetFuture#localGet() and GridPartitionedGetFuture#localGet() does not execute prepareForCache before reading cacheDataRow from row store. was: In case if use Map.Entry interface for a key, we can try to find (key, value) in store with incorrect calculated hash code for binary representation, it lead to result null. The problem is in the GridPartitionedSingleGetFuture#localGet() and GridPartitionedGetFuture#localGet() does not execute prepareForCache before reading cacheDataRow from row store. > Map.Entry interface for key cache may lead to incorrect hash code calculation > - > > Key: IGNITE-10290 > URL: https://issues.apache.org/jira/browse/IGNITE-10290 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Major > Fix For: 2.8 > > Attachments: Reproducer.java > > > If use Map.Entry interface for a key, we can try to find (key, value) in > store with incorrect calculated hash code for binary representation, it lead > to result null. > The problem is in the > GridPartitionedSingleGetFuture#localGet() and > GridPartitionedGetFuture#localGet() does not execute prepareForCache before > reading cacheDataRow from row store. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10393) DataStreamer failed with NPE for MVCC caches
[
https://issues.apache.org/jira/browse/IGNITE-10393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-10393:
-
Component/s: mvcc
> DataStreamer failed with NPE for MVCC caches
>
>
> Key: IGNITE-10393
> URL: https://issues.apache.org/jira/browse/IGNITE-10393
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Blocker
> Fix For: 2.7
>
>
> 1. Start node with configured MVCC cache and PDS
> 2. Try to load data into cache by data streamer running on client node
> {noformat}
> OUT >>> datastreamer into cache 'cache_121', key=java.lang.Long,
> value=org.apache.ignite.testtools.model.AllTypes, range=21..51
> [14:55:16] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true, false, false,
> true]][14:55:16] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true, true, false,
> true]][14:55:16] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true, false, false,
> true]]class org.apache.ignite.IgniteCheckedException: DataStreamer request
> failed [node=5fae5c99-716e-441a-99d5-194de6ba61a6]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:2055)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:356)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: Failed to write record:
> MvccDataRecord [super=DataRecord [writeEntries=SingletonList [MvccDataEntry
> [mvccVer=null]], super=TimeStampRecord [timestamp=1542974116042]]]
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.fillBuffer(FileWriteAheadLogManager.java:2634)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.addRecord(FileWriteAheadLogManager.java:2563)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.access$1600(FileWriteAheadLogManager.java:2451)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:823)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3414)
> at
> org.apache.ignite.internal.processors.cache.GridCacheEntryEx.initialValue(GridCacheEntryEx.java:766)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2265)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:400)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:305)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:60)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:90)
> ... 7 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.TxRecordSerializer.putMvccVersion(TxRecordSerializer.java:66)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV2Serializer.putMvccDataEntry(RecordDataV2Serializer.java:298)
> at
>
[jira] [Commented] (IGNITE-10375) Fix inspection failures
[
https://issues.apache.org/jira/browse/IGNITE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697178#comment-16697178
]
Nikolai Kulagin commented on IGNITE-10375:
--
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity IgniteTests24Java8_RunIntelliJIdeaInspections
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2377131buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> Fix inspection failures
> ---
>
> Key: IGNITE-10375
> URL: https://issues.apache.org/jira/browse/IGNITE-10375
> Project: Ignite
> Issue Type: Bug
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> 4 failures in the master
> https://ci.ignite.apache.org/viewLog.html?buildId=2376109=IgniteTests24Java8_InspectionsCore=Inspection
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10203) [TC Bot] Support for alternative configurations for PR testing
[
https://issues.apache.org/jira/browse/IGNITE-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697165#comment-16697165
]
ASF GitHub Bot commented on IGNITE-10203:
-
SomeFire commented on a change in pull request #78: IGNITE-10203 Support for
alternative configurations for PR testing
URL: https://github.com/apache/ignite-teamcity-bot/pull/78#discussion_r235949008
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/buildtype/ParametersCompacted.java
##
@@ -0,0 +1,134 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.teamcity.ignited.buildtype;
+
+import com.google.common.base.MoreObjects;
+import com.google.common.base.Strings;
+import java.util.ArrayList;
+import java.util.List;
+import java.util.Objects;
+import org.apache.ignite.ci.tcmodel.conf.bt.Parameters;
+import org.apache.ignite.ci.tcmodel.conf.bt.Property;
+import org.apache.ignite.ci.teamcity.ignited.IStringCompactor;
+import org.apache.ignite.internal.util.GridIntList;
+
+public class ParametersCompacted {
+private GridIntList keys;
+private GridIntList values;
+
+/**
+ * Default constructor.
+ */
+public ParametersCompacted() {
+}
+
+/**
+ * @param compactor Compactor.
+ * @param ref Reference.
+ */
+public ParametersCompacted(IStringCompactor compactor, List ref)
{
+final int size = ref.size();
+keys = new GridIntList(size);
+values = new GridIntList(size);
+for (Property next : ref) {
+final String name = next.name();
+if (Strings.isNullOrEmpty(name))
+continue;
+
+final String value = next.getValue();
+if (Strings.isNullOrEmpty(value))
+continue;
+final int val = compactor.getStringId(value);
+final int stringId = compactor.getStringId(name);
+
+keys.add(stringId);
+values.add(val);
+}
+}
+
+public Parameters toParameters(IStringCompactor compactor) {
+List properties = null;
+
+if (keys.size() > 0) {
+properties = new ArrayList<>();
+
+final int size = keys.size();
+for (int i = 0; i < size; i++) {
+if (i >= values.size())
Review comment:
Move check inside `for` statement.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Support for alternative configurations for PR testing
> --
>
> Key: IGNITE-10203
> URL: https://issues.apache.org/jira/browse/IGNITE-10203
> Project: Ignite
> Issue Type: Task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Support for alternative configurations for PR testing (for example,
> IgniteTests24Java8_RunMl)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10393) DataStreamer failed with NPE for MVCC caches
[
https://issues.apache.org/jira/browse/IGNITE-10393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10393:
---
Ignite Flags: (was: Docs Required)
> DataStreamer failed with NPE for MVCC caches
>
>
> Key: IGNITE-10393
> URL: https://issues.apache.org/jira/browse/IGNITE-10393
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Blocker
> Fix For: 2.7
>
>
> 1. Start node with configured MVCC cache and PDS
> 2. Try to load data into cache by data streamer running on client node
> {noformat}
> OUT >>> datastreamer into cache 'cache_121', key=java.lang.Long,
> value=org.apache.ignite.testtools.model.AllTypes, range=21..51
> [14:55:16] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true, false, false,
> true]][14:55:16] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true, true, false,
> true]][14:55:16] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true, false, false,
> true]]class org.apache.ignite.IgniteCheckedException: DataStreamer request
> failed [node=5fae5c99-716e-441a-99d5-194de6ba61a6]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:2055)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:356)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: Failed to write record:
> MvccDataRecord [super=DataRecord [writeEntries=SingletonList [MvccDataEntry
> [mvccVer=null]], super=TimeStampRecord [timestamp=1542974116042]]]
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.fillBuffer(FileWriteAheadLogManager.java:2634)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.addRecord(FileWriteAheadLogManager.java:2563)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.access$1600(FileWriteAheadLogManager.java:2451)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:823)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3414)
> at
> org.apache.ignite.internal.processors.cache.GridCacheEntryEx.initialValue(GridCacheEntryEx.java:766)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2265)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:400)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:305)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:60)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:90)
> ... 7 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.TxRecordSerializer.putMvccVersion(TxRecordSerializer.java:66)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV2Serializer.putMvccDataEntry(RecordDataV2Serializer.java:298)
> at
>
[jira] [Created] (IGNITE-10393) DataStreamer failed with NPE for MVCC caches
Sergey Kozlov created IGNITE-10393:
--
Summary: DataStreamer failed with NPE for MVCC caches
Key: IGNITE-10393
URL: https://issues.apache.org/jira/browse/IGNITE-10393
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Sergey Kozlov
Fix For: 2.7
1. Start node with configured MVCC cache and PDS
2. Try to load data into cache by data streamer running on client node
{noformat}
OUT >>> datastreamer into cache 'cache_121', key=java.lang.Long,
value=org.apache.ignite.testtools.model.AllTypes, range=21..51
[14:55:16] (err) Failed to execute compound future reducer: GridCompoundFuture
[rdc=null, initFlag=1, lsnrCalls=0, done=false, cancelled=false, err=null,
futs=TransformCollectionView [true, false, false, true]][14:55:16] (err) Failed
to execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1,
lsnrCalls=0, done=false, cancelled=false, err=null,
futs=TransformCollectionView [true, true, false, true]][14:55:16] (err) Failed
to execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1,
lsnrCalls=0, done=false, cancelled=false, err=null,
futs=TransformCollectionView [true, false, false, true]]class
org.apache.ignite.IgniteCheckedException: DataStreamer request failed
[node=5fae5c99-716e-441a-99d5-194de6ba61a6]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:2055)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:356)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: Failed to write record:
MvccDataRecord [super=DataRecord [writeEntries=SingletonList [MvccDataEntry
[mvccVer=null]], super=TimeStampRecord [timestamp=1542974116042]]]
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.fillBuffer(FileWriteAheadLogManager.java:2634)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.addRecord(FileWriteAheadLogManager.java:2563)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.access$1600(FileWriteAheadLogManager.java:2451)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:823)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3414)
at
org.apache.ignite.internal.processors.cache.GridCacheEntryEx.initialValue(GridCacheEntryEx.java:766)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2265)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:400)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:305)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:60)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:90)
... 7 more
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.TxRecordSerializer.putMvccVersion(TxRecordSerializer.java:66)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV2Serializer.putMvccDataEntry(RecordDataV2Serializer.java:298)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV2Serializer.putPlainDataEntry(RecordDataV2Serializer.java:286)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV2Serializer.writePlainRecord(RecordDataV2Serializer.java:246)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV1Serializer.writeRecord(RecordDataV1Serializer.java:222)
[jira] [Commented] (IGNITE-7441) Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property
[ https://issues.apache.org/jira/browse/IGNITE-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697170#comment-16697170 ] Vyacheslav Daradur commented on IGNITE-7441: The tests marked as possible blockers fail in the master branch too, so look like the tests have not been affected by changes. > Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property > --- > > Key: IGNITE-7441 > URL: https://issues.apache.org/jira/browse/IGNITE-7441 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Denis Mekhanikov >Assignee: Vyacheslav Daradur >Priority: Minor > Fix For: 2.8 > > > IGNITE_SERVICES_COMPATIBILITY_MODE system property was introduced to > configure backward compatibility mode for service configuration classes. But > since it was done in 1.9 and current version is completely incompatible with > it, there is no point in keeping this property. > Moreover, it is ignored after IGNITE-5145. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10203) [TC Bot] Support for alternative configurations for PR testing
[
https://issues.apache.org/jira/browse/IGNITE-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697166#comment-16697166
]
ASF GitHub Bot commented on IGNITE-10203:
-
SomeFire commented on a change in pull request #78: IGNITE-10203 Support for
alternative configurations for PR testing
URL: https://github.com/apache/ignite-teamcity-bot/pull/78#discussion_r235948717
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/TeamcityIgnitedImpl.java
##
@@ -308,6 +330,120 @@ else if (midValStartDate.before(key))
return chains;
}
+/**
+ * Actualize saved list of composite suites for project.
+ *
+ * @param projectId Project id.
+ */
+private void actualizeSavedCompositeBuildTypesIds(String projectId) {
+if (projectId.equals(DEFAULT_PROJECT_ID)) {
+compositeBuildTypesIdsForDefaultProject =
+
fatBuildTypeDao.compositeBuildTypesIdsSortedByBuildNumberCounter(srvIdMaskHigh,
projectId);
+}
+}
+
+/** {@inheritDoc} */
+@Override public List
getCompositeBuildTypesIdsSortedByBuildNumberCounter(String projectId) {
+ensureActualizeBuildTypeRefsRequested();
+ensureActualizeBuildTypesRequested();
+
+return projectId.equals(DEFAULT_PROJECT_ID) ?
compositeBuildTypesIdsForDefaultProject :
+
fatBuildTypeDao.compositeBuildTypesIdsSortedByBuildNumberCounter(srvIdMaskHigh,
projectId);
+}
+
+/** {@inheritDoc} */
+@Override public List
getAllBuildTypesCompacted(String projectId) {
+ensureActualizeBuildTypeRefsRequested();
+
+return buildTypeRefDao.buildTypesCompacted(srvIdMaskHigh, projectId);
+}
+
+/**
+ * Ensure actualize BuildTypeRefs requested. Add this task to scheduler.
+ */
+private void ensureActualizeBuildTypeRefsRequested() {
+scheduler.sheduleNamed(taskName("actualizeAllBuildTypeRefs"),
+this::reindexBuildTypeRefs, 4, TimeUnit.HOURS);
+}
+
+/**
+ *Ensure actualize BuildTypes requested. Add this task to scheduler.
+ */
+private void ensureActualizeBuildTypesRequested() {
+scheduler.sheduleNamed(taskName("actualizeAllBuildTypes"),
+this::reindexBuildTypes, 24, TimeUnit.HOURS);
+}
+
+/**
+ * Re-index all references to "IgniteTests24Java8" suites.
+ */
+private void reindexBuildTypeRefs() {
+runActualizeBuildTypeRefs(DEFAULT_PROJECT_ID);
+}
+
+/**
+ * Re-index all "IgniteTests24Java8" suites.
+ */
+private void reindexBuildTypes() {
+runActualizeBuildTypes(DEFAULT_PROJECT_ID);
+}
+
+/**
+ * Re-index all project suites.
+ *
+ * @param projectId Project id.
+ * @return Statistics with the number of updated and requested buildTypes.
+ */
+@SuppressWarnings({"WeakerAccess", "UnusedReturnValue"})
+@MonitoredTask(name = "Reindex BuildTypes (projectId)", nameExtArgsIndexes
= {0})
+@AutoProfiling
+protected String runActualizeBuildTypes(String projectId) {
+List buildTypeIds =
buildTypeRefDao.buildTypeIds(srvIdMaskHigh, projectId);
+
+int updated = 0;
+
+for (String buildTypeId : buildTypeIds) {
+
+BuildType buildType = conn.getBuildType(buildTypeId);
+
+FatBuildTypeCompacted existingBuildType =
fatBuildTypeDao.getFatBuildType(srvIdMaskHigh, buildTypeId);
+
+if (fatBuildTypeDao.saveBuildType(srvIdMaskHigh, buildType,
existingBuildType) != null)
+updated++;
+}
+
+if (updated != 0)
+actualizeSavedCompositeBuildTypesIds(projectId);
+
+return "BuildTypes updated " + updated + " from " +
buildTypeIds.size() + " requested";
+}
+
+/**
+ * Re-index all references to project suites.
+ *
+ * @param projectId Project id.
+ * @return Statistics with the number of updated and requested
buildTypeRefs.
+ */
+@SuppressWarnings({"WeakerAccess", "UnusedReturnValue"})
+@MonitoredTask(name = "Reindex BuildTypeRefs (projectId)",
nameExtArgsIndexes = {0})
+@AutoProfiling
+protected String runActualizeBuildTypeRefs(String projectId) {
+List tcData = conn.getBuildTypes(projectId);
+
+Set buildsUpdated = buildTypeRefDao.saveChunk(srvIdMaskHigh,
tcData);
+
+Set removedBuildTypes =
buildTypeRefDao.markMissingBuildsAsRemoved(srvIdMaskHigh,
+
tcData.stream().map(BuildTypeRef::getId).collect(Collectors.toList()),
projectId);
+
+if (!(buildsUpdated.isEmpty() && removedBuildTypes.isEmpty())) {
Review comment:
Remove braces.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service,
[jira] [Commented] (IGNITE-10203) [TC Bot] Support for alternative configurations for PR testing
[
https://issues.apache.org/jira/browse/IGNITE-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697167#comment-16697167
]
ASF GitHub Bot commented on IGNITE-10203:
-
SomeFire commented on a change in pull request #78: IGNITE-10203 Support for
alternative configurations for PR testing
URL: https://github.com/apache/ignite-teamcity-bot/pull/78#discussion_r235915862
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
##
@@ -57,7 +54,12 @@
@Deprecated
long DEFAULT_BUILDS_COUNT = 1000;
-CompletableFuture> getProjectSuites(String projectId);
+/** {@inheritDoc} */
+@Override default List getBuildTypes(String projectId) {
+return FutureUtil.getResult(getProjectSuites(projectId));
+}
+
+CompletableFuture> getProjectSuites(String projectId);
Review comment:
Missed javadocs.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Support for alternative configurations for PR testing
> --
>
> Key: IGNITE-10203
> URL: https://issues.apache.org/jira/browse/IGNITE-10203
> Project: Ignite
> Issue Type: Task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Support for alternative configurations for PR testing (for example,
> IgniteTests24Java8_RunMl)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10203) [TC Bot] Support for alternative configurations for PR testing
[
https://issues.apache.org/jira/browse/IGNITE-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697169#comment-16697169
]
ASF GitHub Bot commented on IGNITE-10203:
-
SomeFire commented on a change in pull request #78: IGNITE-10203 Support for
alternative configurations for PR testing
URL: https://github.com/apache/ignite-teamcity-bot/pull/78#discussion_r235949213
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/buildtype/ParametersCompacted.java
##
@@ -0,0 +1,134 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.teamcity.ignited.buildtype;
+
+import com.google.common.base.MoreObjects;
+import com.google.common.base.Strings;
+import java.util.ArrayList;
+import java.util.List;
+import java.util.Objects;
+import org.apache.ignite.ci.tcmodel.conf.bt.Parameters;
+import org.apache.ignite.ci.tcmodel.conf.bt.Property;
+import org.apache.ignite.ci.teamcity.ignited.IStringCompactor;
+import org.apache.ignite.internal.util.GridIntList;
+
+public class ParametersCompacted {
+private GridIntList keys;
+private GridIntList values;
+
+/**
+ * Default constructor.
+ */
+public ParametersCompacted() {
+}
+
+/**
+ * @param compactor Compactor.
+ * @param ref Reference.
+ */
+public ParametersCompacted(IStringCompactor compactor, List ref)
{
+final int size = ref.size();
+keys = new GridIntList(size);
+values = new GridIntList(size);
+for (Property next : ref) {
+final String name = next.name();
+if (Strings.isNullOrEmpty(name))
+continue;
+
+final String value = next.getValue();
+if (Strings.isNullOrEmpty(value))
+continue;
+final int val = compactor.getStringId(value);
+final int stringId = compactor.getStringId(name);
+
+keys.add(stringId);
+values.add(val);
+}
+}
+
+public Parameters toParameters(IStringCompactor compactor) {
+List properties = null;
+
+if (keys.size() > 0) {
+properties = new ArrayList<>();
+
+final int size = keys.size();
+for (int i = 0; i < size; i++) {
+if (i >= values.size())
Review comment:
And empty line before `for`.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Support for alternative configurations for PR testing
> --
>
> Key: IGNITE-10203
> URL: https://issues.apache.org/jira/browse/IGNITE-10203
> Project: Ignite
> Issue Type: Task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Support for alternative configurations for PR testing (for example,
> IgniteTests24Java8_RunMl)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10330) Implement disk page compression
[ https://issues.apache.org/jira/browse/IGNITE-10330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697164#comment-16697164 ] Sergi Vladykin edited comment on IGNITE-10330 at 11/23/18 2:00 PM: --- Already created IGNITE-10332 was (Author: sergi.vladykin): Already create IGNITE-10332 > Implement disk page compression > --- > > Key: IGNITE-10330 > URL: https://issues.apache.org/jira/browse/IGNITE-10330 > Project: Ignite > Issue Type: New Feature > Components: cache >Reporter: Sergi Vladykin >Assignee: Sergi Vladykin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10330) Implement disk page compression
[ https://issues.apache.org/jira/browse/IGNITE-10330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697164#comment-16697164 ] Sergi Vladykin commented on IGNITE-10330: - Already create IGNITE-10332 > Implement disk page compression > --- > > Key: IGNITE-10330 > URL: https://issues.apache.org/jira/browse/IGNITE-10330 > Project: Ignite > Issue Type: New Feature > Components: cache >Reporter: Sergi Vladykin >Assignee: Sergi Vladykin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10335) move ML examples datasets files to resources
[
https://issues.apache.org/jira/browse/IGNITE-10335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697160#comment-16697160
]
ASF GitHub Bot commented on IGNITE-10335:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5434
> move ML examples datasets files to resources
>
>
> Key: IGNITE-10335
> URL: https://issues.apache.org/jira/browse/IGNITE-10335
> Project: Ignite
> Issue Type: Improvement
> Components: ml
>Affects Versions: 2.7
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.8
>
>
> ML examples datasets files were moved from resources to some folder under
> src/main/java in the course of IGNITE-10209.
> This was done as a quick workaround to unblock another change. However,
> resources is a more appropriate location for this kind of content and in the
> course of IGNITE-10234 we discovered that there is a way to make things work
> with dataset files in this folder.
> Solution appears to be to rework {{SandboxMLCache}} to use
> {{IgniteUtils.resolveIgnitePath}} API like it is done in
> [SqlJdbcCopyExample|https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/sql/SqlJdbcCopyExample.java].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7441) Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property
[
https://issues.apache.org/jira/browse/IGNITE-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697159#comment-16697159
]
Ignite TC Bot commented on IGNITE-7441:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Inspections] Core{color} [[tests 0 BuildFailureOnMetric
|https://ci.ignite.apache.org/viewLog.html?buildId=2384857]]
{color:#d04437}Cache 7{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2384831]]
* IgniteDynamicCacheStartFailWithPersistenceTest.testBrokenCacheStoreOnAllNodes
(last started)
{color:#d04437}Continuous Query 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2384771]]
* CacheContinuousQueryAsyncFailoverMvccTxSelfTest.testFailoverStartStopBackup
(last started)
{color:#d04437}Basic 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2384804]]
* IgniteBasicTestSuite: BPlusTreeFakeReuseSelfTest.testMassiveRemove2_true -
0,0% fails in last 100 master runs.
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2384861buildTypeId=IgniteTests24Java8_RunAll]
> Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property
> ---
>
> Key: IGNITE-7441
> URL: https://issues.apache.org/jira/browse/IGNITE-7441
> Project: Ignite
> Issue Type: Task
> Components: managed services
>Reporter: Denis Mekhanikov
>Assignee: Vyacheslav Daradur
>Priority: Minor
> Fix For: 2.8
>
>
> IGNITE_SERVICES_COMPATIBILITY_MODE system property was introduced to
> configure backward compatibility mode for service configuration classes. But
> since it was done in 1.9 and current version is completely incompatible with
> it, there is no point in keeping this property.
> Moreover, it is ignored after IGNITE-5145.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10391) MVCC: Invoke request fails on backup while rebalance is in progress.
[ https://issues.apache.org/jira/browse/IGNITE-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-10391: -- Ignite Flags: (was: Docs Required) > MVCC: Invoke request fails on backup while rebalance is in progress. > > > Key: IGNITE-10391 > URL: https://issues.apache.org/jira/browse/IGNITE-10391 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Critical > Fix For: 2.8 > > > Invoke request fails with Assertion on backup while rebalance is in progress. > Enlist request handler expects entry processor instead of value in case of > Invoke operation, > but when rebalance is in progress we pass entry history to backup side. This > causes assertion triggering. > We have to handle correctly this case and apply history and then entry > processor. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10385) NPE in CachePartitionPartialCountersMap.toString
[
https://issues.apache.org/jira/browse/IGNITE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697141#comment-16697141
]
ASF GitHub Bot commented on IGNITE-10385:
-
GitHub user antkr opened a pull request:
https://github.com/apache/ignite/pull/5487
IGNITE-10385 replace empty fields with zero-length arrays.
TC run.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10385
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5487.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5487
commit 949dc3daf9e980b357ccb6e1ebc8cf7eb0f5e391
Author: antkr
Date: 2018-11-23T13:34:21Z
IGNITE-10385 replace empty fields with zero-length arrays.
> NPE in CachePartitionPartialCountersMap.toString
>
>
> Key: IGNITE-10385
> URL: https://issues.apache.org/jira/browse/IGNITE-10385
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Anton Kurbanov
>Priority: Blocker
>
> {noformat}
> Failed to reinitialize local partitions (preloading will be stopped)
> org.apache.ignite.IgniteException: null
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:868)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.toString(GridIoMessage.java:358)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at java.lang.StringBuilder.append(StringBuilder.java:131) ~[?:1.8.0_171]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2653)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2586)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1642)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1714)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1160)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:1399)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:1506)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1139)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:703)
> [ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2379)
> [ignite-core-2.4.10.jar:2.4.10]
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-2.4.10.jar:2.4.10]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
> Caused by: org.apache.ignite.IgniteException
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:830)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:787)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:889)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.toString(GridDhtPartitionsSingleMessage.java:551)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
>
[jira] [Updated] (IGNITE-10392) Client broken cluster where try to connect. Server nodes drop by handler
[
https://issues.apache.org/jira/browse/IGNITE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Antonov updated IGNITE-10392:
Fix Version/s: 2.8
> Client broken cluster where try to connect. Server nodes drop by handler
>
>
> Key: IGNITE-10392
> URL: https://issues.apache.org/jira/browse/IGNITE-10392
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Blocker
> Fix For: 2.8
>
>
> {noformat}
> org.apache.ignite.IgniteException: Failed to resolve nodes topology
> [cacheGrp=N/A, topVer=AffinityTopologyVersion [topVer=133, minorTopVer=0],
> history=[AffinityTopologyVersion [topVer=35, minorTopVer=0],
> AffinityTopologyVersion [topVer=36, minorTopVer=0], AffinityTopologyVersion
> [topVer=37, minorTopVer=0], AffinityTopologyVersion [topVer=38,
> minorTopVer=0], AffinityTopologyVersion [topVer=39, minorTopVer=0],
> AffinityTopologyVersion [topVer=40, minorTopVer=0], AffinityTopologyVersion
> [topVer=41, minorTopVer=0], AffinityTopologyVersion [topVer=42,
> minorTopVer=0], AffinityTopologyVersion [topVer=43, minorTopVer=0],
> AffinityTopologyVersion [topVer=44, minorTopVer=0], AffinityTopologyVersion
> [topVer=45, minorTopVer=0], AffinityTopologyVersion [topVer=46,
> minorTopVer=0], AffinityTopologyVersion [topVer=47, minorTopVer=0],
> AffinityTopologyVersion [topVer=48, minorTopVer=0], AffinityTopologyVersion
> [topVer=49, minorTopVer=0], AffinityTopologyVersion [topVer=50,
> minorTopVer=0], AffinityTopologyVersion [topVer=51, minorTopVer=0],
> AffinityTopologyVersion [topVer=52, minorTopVer=0], AffinityTopologyVersion
> [topVer=53, minorTopVer=0], AffinityTopologyVersion [topVer=54,
> minorTopVer=0], AffinityTopologyVersion [topVer=55, minorTopVer=0],
> AffinityTopologyVersion [topVer=56, minorTopVer=0], AffinityTopologyVersion
> [topVer=57, minorTopVer=0], AffinityTopologyVersion [topVer=58,
> minorTopVer=0], AffinityTopologyVersion [topVer=59, minorTopVer=0],
> AffinityTopologyVersion [topVer=60, minorTopVer=0], AffinityTopologyVersion
> [topVer=61, minorTopVer=0], AffinityTopologyVersion [topVer=62,
> minorTopVer=0], AffinityTopologyVersion [topVer=63, minorTopVer=0],
> AffinityTopologyVersion [topVer=64, minorTopVer=0], AffinityTopologyVersion
> [topVer=65, minorTopVer=0], AffinityTopologyVersion [topVer=66,
> minorTopVer=0], AffinityTopologyVersion [topVer=67, minorTopVer=0],
> AffinityTopologyVersion [topVer=68, minorTopVer=0], AffinityTopologyVersion
> [topVer=69, minorTopVer=0], AffinityTopologyVersion [topVer=70,
> minorTopVer=0], AffinityTopologyVersion [topVer=71, minorTopVer=0],
> AffinityTopologyVersion [topVer=72, minorTopVer=0], AffinityTopologyVersion
> [topVer=73, minorTopVer=0], AffinityTopologyVersion [topVer=74,
> minorTopVer=0], AffinityTopologyVersion [topVer=75, minorTopVer=0],
> AffinityTopologyVersion [topVer=76, minorTopVer=0], AffinityTopologyVersion
> [topVer=77, minorTopVer=0], AffinityTopologyVersion [topVer=78,
> minorTopVer=0], AffinityTopologyVersion [topVer=79, minorTopVer=0],
> AffinityTopologyVersion [topVer=80, minorTopVer=0], AffinityTopologyVersion
> [topVer=81, minorTopVer=0], AffinityTopologyVersion [topVer=82,
> minorTopVer=0], AffinityTopologyVersion [topVer=83, minorTopVer=0],
> AffinityTopologyVersion [topVer=84, minorTopVer=0], AffinityTopologyVersion
> [topVer=85, minorTopVer=0], AffinityTopologyVersion [topVer=86,
> minorTopVer=0], AffinityTopologyVersion [topVer=87, minorTopVer=0],
> AffinityTopologyVersion [topVer=88, minorTopVer=0], AffinityTopologyVersion
> [topVer=89, minorTopVer=0], AffinityTopologyVersion [topVer=90,
> minorTopVer=0], AffinityTopologyVersion [topVer=91, minorTopVer=0],
> AffinityTopologyVersion [topVer=92, minorTopVer=0], AffinityTopologyVersion
> [topVer=93, minorTopVer=0], AffinityTopologyVersion [topVer=94,
> minorTopVer=0], AffinityTopologyVersion [topVer=95, minorTopVer=0],
> AffinityTopologyVersion [topVer=96, minorTopVer=0], AffinityTopologyVersion
> [topVer=97, minorTopVer=0], AffinityTopologyVersion [topVer=98,
> minorTopVer=0], AffinityTopologyVersion [topVer=99, minorTopVer=0],
> AffinityTopologyVersion [topVer=100, minorTopVer=0], AffinityTopologyVersion
> [topVer=101, minorTopVer=0], AffinityTopologyVersion [topVer=102,
> minorTopVer=0], AffinityTopologyVersion [topVer=103, minorTopVer=0],
> AffinityTopologyVersion [topVer=104, minorTopVer=0], AffinityTopologyVersion
> [topVer=105, minorTopVer=0], AffinityTopologyVersion [topVer=106,
> minorTopVer=0], AffinityTopologyVersion [topVer=107, minorTopVer=0],
> AffinityTopologyVersion [topVer=108, minorTopVer=0], AffinityTopologyVersion
> [topVer=109, minorTopVer=0], AffinityTopologyVersion [topVer=110,
> minorTopVer=0],
[jira] [Commented] (IGNITE-10172) Enabling cache statistics on a large cluster with a large number of caches can affect performance
[
https://issues.apache.org/jira/browse/IGNITE-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697146#comment-16697146
]
Anton Vinogradov commented on IGNITE-10172:
---
[~alex_pl]
The code looks good to me.
Please discuss idea & design (property) on devlist.
> Enabling cache statistics on a large cluster with a large number of caches
> can affect performance
> -
>
> Key: IGNITE-10172
> URL: https://issues.apache.org/jira/browse/IGNITE-10172
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.8
>
>
> In current implementation cache metrics are collected on each node and sent
> across whole cluster with discovery message
> ({{TcpDiscoveryMetricsUpdateMessage}}) with configured frequency
> ({{MetricsUpdateFrequency}}, 2 seconds by default).
> If there are a lot of caches and a lot of nodes in the cluster, metrics
> update message (which contain metrics for each cache on each node) can reach
> a critical size.
> Also frequently collecting all cache metrics have a negative performance
> impact.
> The only way now to disable cache metrics collecting and sending with
> discovery metrics update message is to disable statistics for each cache. But
> this also makes impossible to request some of cache metrics locally (for the
> current node only). Requesting a limited set of cache metrics on the current
> node doesn't have such performance impact as the frequent collecting of all
> cache metrics, but sometimes it's enough for diagnostic purposes.
> To solve this introduce new system property which will disable cache metrics
> sending with {{TcpDiscoveryMetricsUpdateMessage}} even if
> {{statisticsEnabled}} flag is true.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10329) Create JDBC "query" and "query join" benchmarks and compare them with Postgres and MySQL
[
https://issues.apache.org/jira/browse/IGNITE-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696699#comment-16696699
]
Pavel Kuznetsov edited comment on IGNITE-10329 at 11/23/18 1:40 PM:
What is in scope:
1) Ignite inmemory
2) Ignite persistence on, data region fits all the data
3) Postgresql out of the box
4) Postgresql with increased {{shared_buffers}} to 10 GiB
5) Mysql out of the box
6) Mysql with {{innodb_buffer_pool_size = 10 GiB}} and
{{innodb_buffer_pool_instances = 8}}
was (Author: pkouznet):
What is in scope:
1) Ignite inmemory
2) Ignite persistence on, data region fits all the data
3) Postgresql out of the box
4) Postgresql with increased {{shared_buffers}} to 10 GiB
5) Mysql out of the box
6) Mysql with increased caches
> Create JDBC "query" and "query join" benchmarks and compare them with
> Postgres and MySQL
>
>
> Key: IGNITE-10329
> URL: https://issues.apache.org/jira/browse/IGNITE-10329
> Project: Ignite
> Issue Type: Task
> Components: sql, yardstick
>Reporter: Vladimir Ozerov
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> Currently we have {{IgniteSqlQueryBenchmark}} and
> {{IgniteSqlQueryJoinBenchmark}} benchmarks which query data over salary range
> and optionally joins it with second table. Let's create a set of similar
> benchmarks which will use JDBC to load and query data, and execute them
> against one-node Ignite cluster, MySQL and Postgres.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10392) Client broken cluster where try to connect. Server nodes drop by handler
[
https://issues.apache.org/jira/browse/IGNITE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697145#comment-16697145
]
ASF GitHub Bot commented on IGNITE-10392:
-
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/5488
IGNITE-10392 : Use lasdAffChangedTopVer if DiscoCache for the requested
topVer isn't ready.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10392
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5488.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5488
commit 22b39db36b820b4410be0e3b4f21d1b29ce760af
Author: Ilya Lantukh
Date: 2018-11-23T13:36:44Z
IGNITE-10392 : Use lasdAffChangedTopVer if DiscoCache for the requested
topVer isn't ready.
> Client broken cluster where try to connect. Server nodes drop by handler
>
>
> Key: IGNITE-10392
> URL: https://issues.apache.org/jira/browse/IGNITE-10392
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Blocker
>
> {noformat}
> org.apache.ignite.IgniteException: Failed to resolve nodes topology
> [cacheGrp=N/A, topVer=AffinityTopologyVersion [topVer=133, minorTopVer=0],
> history=[AffinityTopologyVersion [topVer=35, minorTopVer=0],
> AffinityTopologyVersion [topVer=36, minorTopVer=0], AffinityTopologyVersion
> [topVer=37, minorTopVer=0], AffinityTopologyVersion [topVer=38,
> minorTopVer=0], AffinityTopologyVersion [topVer=39, minorTopVer=0],
> AffinityTopologyVersion [topVer=40, minorTopVer=0], AffinityTopologyVersion
> [topVer=41, minorTopVer=0], AffinityTopologyVersion [topVer=42,
> minorTopVer=0], AffinityTopologyVersion [topVer=43, minorTopVer=0],
> AffinityTopologyVersion [topVer=44, minorTopVer=0], AffinityTopologyVersion
> [topVer=45, minorTopVer=0], AffinityTopologyVersion [topVer=46,
> minorTopVer=0], AffinityTopologyVersion [topVer=47, minorTopVer=0],
> AffinityTopologyVersion [topVer=48, minorTopVer=0], AffinityTopologyVersion
> [topVer=49, minorTopVer=0], AffinityTopologyVersion [topVer=50,
> minorTopVer=0], AffinityTopologyVersion [topVer=51, minorTopVer=0],
> AffinityTopologyVersion [topVer=52, minorTopVer=0], AffinityTopologyVersion
> [topVer=53, minorTopVer=0], AffinityTopologyVersion [topVer=54,
> minorTopVer=0], AffinityTopologyVersion [topVer=55, minorTopVer=0],
> AffinityTopologyVersion [topVer=56, minorTopVer=0], AffinityTopologyVersion
> [topVer=57, minorTopVer=0], AffinityTopologyVersion [topVer=58,
> minorTopVer=0], AffinityTopologyVersion [topVer=59, minorTopVer=0],
> AffinityTopologyVersion [topVer=60, minorTopVer=0], AffinityTopologyVersion
> [topVer=61, minorTopVer=0], AffinityTopologyVersion [topVer=62,
> minorTopVer=0], AffinityTopologyVersion [topVer=63, minorTopVer=0],
> AffinityTopologyVersion [topVer=64, minorTopVer=0], AffinityTopologyVersion
> [topVer=65, minorTopVer=0], AffinityTopologyVersion [topVer=66,
> minorTopVer=0], AffinityTopologyVersion [topVer=67, minorTopVer=0],
> AffinityTopologyVersion [topVer=68, minorTopVer=0], AffinityTopologyVersion
> [topVer=69, minorTopVer=0], AffinityTopologyVersion [topVer=70,
> minorTopVer=0], AffinityTopologyVersion [topVer=71, minorTopVer=0],
> AffinityTopologyVersion [topVer=72, minorTopVer=0], AffinityTopologyVersion
> [topVer=73, minorTopVer=0], AffinityTopologyVersion [topVer=74,
> minorTopVer=0], AffinityTopologyVersion [topVer=75, minorTopVer=0],
> AffinityTopologyVersion [topVer=76, minorTopVer=0], AffinityTopologyVersion
> [topVer=77, minorTopVer=0], AffinityTopologyVersion [topVer=78,
> minorTopVer=0], AffinityTopologyVersion [topVer=79, minorTopVer=0],
> AffinityTopologyVersion [topVer=80, minorTopVer=0], AffinityTopologyVersion
> [topVer=81, minorTopVer=0], AffinityTopologyVersion [topVer=82,
> minorTopVer=0], AffinityTopologyVersion [topVer=83, minorTopVer=0],
> AffinityTopologyVersion [topVer=84, minorTopVer=0], AffinityTopologyVersion
> [topVer=85, minorTopVer=0], AffinityTopologyVersion [topVer=86,
> minorTopVer=0], AffinityTopologyVersion [topVer=87, minorTopVer=0],
> AffinityTopologyVersion [topVer=88, minorTopVer=0], AffinityTopologyVersion
> [topVer=89, minorTopVer=0], AffinityTopologyVersion [topVer=90,
> minorTopVer=0], AffinityTopologyVersion [topVer=91, minorTopVer=0],
> AffinityTopologyVersion [topVer=92, minorTopVer=0], AffinityTopologyVersion
> [topVer=93, minorTopVer=0], AffinityTopologyVersion [topVer=94,
> minorTopVer=0], AffinityTopologyVersion [topVer=95, minorTopVer=0],
> AffinityTopologyVersion
[jira] [Created] (IGNITE-10392) Client broken cluster where try to connect. Server nodes drop by handler
Ilya Lantukh created IGNITE-10392:
-
Summary: Client broken cluster where try to connect. Server nodes
drop by handler
Key: IGNITE-10392
URL: https://issues.apache.org/jira/browse/IGNITE-10392
Project: Ignite
Issue Type: Bug
Reporter: Ilya Lantukh
Assignee: Ilya Lantukh
{noformat}
org.apache.ignite.IgniteException: Failed to resolve nodes topology
[cacheGrp=N/A, topVer=AffinityTopologyVersion [topVer=133, minorTopVer=0],
history=[AffinityTopologyVersion [topVer=35, minorTopVer=0],
AffinityTopologyVersion [topVer=36, minorTopVer=0], AffinityTopologyVersion
[topVer=37, minorTopVer=0], AffinityTopologyVersion [topVer=38, minorTopVer=0],
AffinityTopologyVersion [topVer=39, minorTopVer=0], AffinityTopologyVersion
[topVer=40, minorTopVer=0], AffinityTopologyVersion [topVer=41, minorTopVer=0],
AffinityTopologyVersion [topVer=42, minorTopVer=0], AffinityTopologyVersion
[topVer=43, minorTopVer=0], AffinityTopologyVersion [topVer=44, minorTopVer=0],
AffinityTopologyVersion [topVer=45, minorTopVer=0], AffinityTopologyVersion
[topVer=46, minorTopVer=0], AffinityTopologyVersion [topVer=47, minorTopVer=0],
AffinityTopologyVersion [topVer=48, minorTopVer=0], AffinityTopologyVersion
[topVer=49, minorTopVer=0], AffinityTopologyVersion [topVer=50, minorTopVer=0],
AffinityTopologyVersion [topVer=51, minorTopVer=0], AffinityTopologyVersion
[topVer=52, minorTopVer=0], AffinityTopologyVersion [topVer=53, minorTopVer=0],
AffinityTopologyVersion [topVer=54, minorTopVer=0], AffinityTopologyVersion
[topVer=55, minorTopVer=0], AffinityTopologyVersion [topVer=56, minorTopVer=0],
AffinityTopologyVersion [topVer=57, minorTopVer=0], AffinityTopologyVersion
[topVer=58, minorTopVer=0], AffinityTopologyVersion [topVer=59, minorTopVer=0],
AffinityTopologyVersion [topVer=60, minorTopVer=0], AffinityTopologyVersion
[topVer=61, minorTopVer=0], AffinityTopologyVersion [topVer=62, minorTopVer=0],
AffinityTopologyVersion [topVer=63, minorTopVer=0], AffinityTopologyVersion
[topVer=64, minorTopVer=0], AffinityTopologyVersion [topVer=65, minorTopVer=0],
AffinityTopologyVersion [topVer=66, minorTopVer=0], AffinityTopologyVersion
[topVer=67, minorTopVer=0], AffinityTopologyVersion [topVer=68, minorTopVer=0],
AffinityTopologyVersion [topVer=69, minorTopVer=0], AffinityTopologyVersion
[topVer=70, minorTopVer=0], AffinityTopologyVersion [topVer=71, minorTopVer=0],
AffinityTopologyVersion [topVer=72, minorTopVer=0], AffinityTopologyVersion
[topVer=73, minorTopVer=0], AffinityTopologyVersion [topVer=74, minorTopVer=0],
AffinityTopologyVersion [topVer=75, minorTopVer=0], AffinityTopologyVersion
[topVer=76, minorTopVer=0], AffinityTopologyVersion [topVer=77, minorTopVer=0],
AffinityTopologyVersion [topVer=78, minorTopVer=0], AffinityTopologyVersion
[topVer=79, minorTopVer=0], AffinityTopologyVersion [topVer=80, minorTopVer=0],
AffinityTopologyVersion [topVer=81, minorTopVer=0], AffinityTopologyVersion
[topVer=82, minorTopVer=0], AffinityTopologyVersion [topVer=83, minorTopVer=0],
AffinityTopologyVersion [topVer=84, minorTopVer=0], AffinityTopologyVersion
[topVer=85, minorTopVer=0], AffinityTopologyVersion [topVer=86, minorTopVer=0],
AffinityTopologyVersion [topVer=87, minorTopVer=0], AffinityTopologyVersion
[topVer=88, minorTopVer=0], AffinityTopologyVersion [topVer=89, minorTopVer=0],
AffinityTopologyVersion [topVer=90, minorTopVer=0], AffinityTopologyVersion
[topVer=91, minorTopVer=0], AffinityTopologyVersion [topVer=92, minorTopVer=0],
AffinityTopologyVersion [topVer=93, minorTopVer=0], AffinityTopologyVersion
[topVer=94, minorTopVer=0], AffinityTopologyVersion [topVer=95, minorTopVer=0],
AffinityTopologyVersion [topVer=96, minorTopVer=0], AffinityTopologyVersion
[topVer=97, minorTopVer=0], AffinityTopologyVersion [topVer=98, minorTopVer=0],
AffinityTopologyVersion [topVer=99, minorTopVer=0], AffinityTopologyVersion
[topVer=100, minorTopVer=0], AffinityTopologyVersion [topVer=101,
minorTopVer=0], AffinityTopologyVersion [topVer=102, minorTopVer=0],
AffinityTopologyVersion [topVer=103, minorTopVer=0], AffinityTopologyVersion
[topVer=104, minorTopVer=0], AffinityTopologyVersion [topVer=105,
minorTopVer=0], AffinityTopologyVersion [topVer=106, minorTopVer=0],
AffinityTopologyVersion [topVer=107, minorTopVer=0], AffinityTopologyVersion
[topVer=108, minorTopVer=0], AffinityTopologyVersion [topVer=109,
minorTopVer=0], AffinityTopologyVersion [topVer=110, minorTopVer=0],
AffinityTopologyVersion [topVer=111, minorTopVer=0], AffinityTopologyVersion
[topVer=112, minorTopVer=0], AffinityTopologyVersion [topVer=113,
minorTopVer=0], AffinityTopologyVersion [topVer=114, minorTopVer=0],
AffinityTopologyVersion [topVer=115, minorTopVer=0], AffinityTopologyVersion
[topVer=116, minorTopVer=0], AffinityTopologyVersion [topVer=117,
minorTopVer=0], AffinityTopologyVersion [topVer=118,
[jira] [Comment Edited] (IGNITE-10329) Create JDBC "query" and "query join" benchmarks and compare them with Postgres and MySQL
[
https://issues.apache.org/jira/browse/IGNITE-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695965#comment-16695965
]
Pavel Kuznetsov edited comment on IGNITE-10329 at 11/23/18 1:04 PM:
[~vozerov] see mysql .properties file commited
(https://github.com/apache/ignite/pull/5479/files#diff-fca692296dbed27188a9e1653590784d).
See my sanity results (on my laptop).
Uploaded 1M (Person)+ 100K (Org) rows.
*Simple select 1K rows:*
||Vendor || Queries/sec, Avg||
| Ignite | 5.75 |
| MySQL (mariadb)| 15.47 |
| PostgreSQL | 32.02 |
*Select 1K rows + join :*
||Vendor || Queries/sec, Avg||
| Ignite | 5.76 |
| MySQL (mariadb) | 12.23 |
| PostgreSQL | 29.82 |
Ignite cluster : 1 srv + 1 client (thin driver) on the same host, syn mode
FULL_SYNC, no backups. (todo : remove confusing option "-b" from script).
was (Author: pkouznet):
[~vozerov] see mysql .properties file commited
(https://github.com/apache/ignite/pull/5479/files#diff-fca692296dbed27188a9e1653590784d).
See my sanity results (on my laptop).
Uploaded 1M (Person)+ 100K (Org) rows.
*Simple select 1K rows:*
||Vendor || Queries/sec, Avg||
| Ignite | 5.75 |
| MySQL | 15.47 |
| PostgreSQL | 32.02 |
*Select 1K rows + join :*
||Vendor || Queries/sec, Avg||
| Ignite | 5.76 |
| MySQL | 12.23 |
| PostgreSQL | 29.82 |
Ignite cluster : 1 srv + 1 client (thin driver) on the same host, syn mode
FULL_SYNC, no backups. (todo : remove confusing option "-b" from script).
> Create JDBC "query" and "query join" benchmarks and compare them with
> Postgres and MySQL
>
>
> Key: IGNITE-10329
> URL: https://issues.apache.org/jira/browse/IGNITE-10329
> Project: Ignite
> Issue Type: Task
> Components: sql, yardstick
>Reporter: Vladimir Ozerov
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> Currently we have {{IgniteSqlQueryBenchmark}} and
> {{IgniteSqlQueryJoinBenchmark}} benchmarks which query data over salary range
> and optionally joins it with second table. Let's create a set of similar
> benchmarks which will use JDBC to load and query data, and execute them
> against one-node Ignite cluster, MySQL and Postgres.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10130) Add option for disable triggering cache interceptor in case of conflicts.
[ https://issues.apache.org/jira/browse/IGNITE-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-10130: Summary: Add option for disable triggering cache interceptor in case of conflicts. (was: Add option for disable triggering cache interceptor on cross datacenter replication changes.) > Add option for disable triggering cache interceptor in case of conflicts. > - > > Key: IGNITE-10130 > URL: https://issues.apache.org/jira/browse/IGNITE-10130 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > > It's needed for our proprietary plugin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9957) Optimize execution time of BinaryMetadataUpdatesFlowTest
[ https://issues.apache.org/jira/browse/IGNITE-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697090#comment-16697090 ] Sergey Chugunov edited comment on IGNITE-9957 at 11/23/18 12:48 PM: Test class was refactored in IGNITE-9976 task, proposed optimization was implemented as part of the task. Closing the ticket. [~ibessonov], [~Jokser], thanks guys for bringing this up! It is better to keep our tasks list clean. was (Author: sergey-chugunov): Test class was refactored in IGNITE-9976 task, proposed optimization was implemented as part of the task. Closing the ticket. > Optimize execution time of BinaryMetadataUpdatesFlowTest > > > Key: IGNITE-9957 > URL: https://issues.apache.org/jira/browse/IGNITE-9957 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > As TC statistics shows ([example run on master > branch|https://ci.ignite.apache.org/viewLog.html?currentGroup=test=org.apache.ignite.testsuites.IgniteBinaryObjectsTestSuite%23teamcity%23org.apache.ignite.internal.processors.cache.binary%23teamcity%23BinaryMetadataUpdatesFlowTest=1=DURATION_DESC=20===IgniteTests24Java8_RunAll=2136245=testsInfo]), > three tests within this class require about 6 minutes of running time which > is a lot. > It is worth investigating tests and speed them up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9957) Optimize execution time of BinaryMetadataUpdatesFlowTest
[ https://issues.apache.org/jira/browse/IGNITE-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov closed IGNITE-9957. --- > Optimize execution time of BinaryMetadataUpdatesFlowTest > > > Key: IGNITE-9957 > URL: https://issues.apache.org/jira/browse/IGNITE-9957 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > As TC statistics shows ([example run on master > branch|https://ci.ignite.apache.org/viewLog.html?currentGroup=test=org.apache.ignite.testsuites.IgniteBinaryObjectsTestSuite%23teamcity%23org.apache.ignite.internal.processors.cache.binary%23teamcity%23BinaryMetadataUpdatesFlowTest=1=DURATION_DESC=20===IgniteTests24Java8_RunAll=2136245=testsInfo]), > three tests within this class require about 6 minutes of running time which > is a lot. > It is worth investigating tests and speed them up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9957) Optimize execution time of BinaryMetadataUpdatesFlowTest
[ https://issues.apache.org/jira/browse/IGNITE-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov resolved IGNITE-9957. - Resolution: Won't Fix Test class was refactored in IGNITE-9976 task, proposed optimization was implemented as part of the task. Closing the ticket. > Optimize execution time of BinaryMetadataUpdatesFlowTest > > > Key: IGNITE-9957 > URL: https://issues.apache.org/jira/browse/IGNITE-9957 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > As TC statistics shows ([example run on master > branch|https://ci.ignite.apache.org/viewLog.html?currentGroup=test=org.apache.ignite.testsuites.IgniteBinaryObjectsTestSuite%23teamcity%23org.apache.ignite.internal.processors.cache.binary%23teamcity%23BinaryMetadataUpdatesFlowTest=1=DURATION_DESC=20===IgniteTests24Java8_RunAll=2136245=testsInfo]), > three tests within this class require about 6 minutes of running time which > is a lot. > It is worth investigating tests and speed them up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10356) JDBC thin driver returns wrong data type for Date and Decimal SQL type
[ https://issues.apache.org/jira/browse/IGNITE-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-10356: -- Ignite Flags: (was: Docs Required) > JDBC thin driver returns wrong data type for Date and Decimal SQL type > -- > > Key: IGNITE-10356 > URL: https://issues.apache.org/jira/browse/IGNITE-10356 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.6, 2.7 >Reporter: Ray >Assignee: Ray >Priority: Critical > Fix For: 2.8 > > > JDBC thin driver will return wrong metadata for column type when user creates > a table with Date and Decimal type. > > Steps to reproduce. > 1. Start one node and create table using this command > create table a(a varchar, b decimal,c date, primary key(a)); > 2. Run "!desc a" to show the metadata of table a > This results is as follows: > TABLE_CAT > TABLE_SCHEM PUBLIC > TABLE_NAME A > COLUMN_NAME A > DATA_TYPE 12 > TYPE_NAME VARCHAR > COLUMN_SIZE null > BUFFER_LENGTH null > DECIMAL_DIGITS null > NUM_PREC_RADIX 10 > NULLABLE 1 > REMARKS > COLUMN_DEF > SQL_DATA_TYPE 12 > SQL_DATETIME_SUB null > CHAR_OCTET_LENGTH 2147483647 > ORDINAL_POSITION 1 > IS_NULLABLE YES > SCOPE_CATLOG > SCOPE_SCHEMA > SCOPE_TABLE > SOURCE_DATA_TYPE null > IS_AUTOINCREMENT NO > IS_GENERATEDCOLUMN NO > TABLE_CAT > TABLE_SCHEM PUBLIC > TABLE_NAME A > COLUMN_NAME B > DATA_TYPE > TYPE_NAME OTHER > COLUMN_SIZE null > BUFFER_LENGTH null > DECIMAL_DIGITS null > NUM_PREC_RADIX 10 > NULLABLE 1 > REMARKS > COLUMN_DEF > SQL_DATA_TYPE > SQL_DATETIME_SUB null > CHAR_OCTET_LENGTH 2147483647 > ORDINAL_POSITION 2 > IS_NULLABLE YES > SCOPE_CATLOG > SCOPE_SCHEMA > SCOPE_TABLE > SOURCE_DATA_TYPE null > IS_AUTOINCREMENT NO > IS_GENERATEDCOLUMN NO > TABLE_CAT > TABLE_SCHEM PUBLIC > TABLE_NAME A > COLUMN_NAME C > DATA_TYPE > TYPE_NAME OTHER > COLUMN_SIZE null > BUFFER_LENGTH null > DECIMAL_DIGITS null > NUM_PREC_RADIX 10 > NULLABLE 1 > REMARKS > COLUMN_DEF > SQL_DATA_TYPE > SQL_DATETIME_SUB null > CHAR_OCTET_LENGTH 2147483647 > ORDINAL_POSITION 3 > IS_NULLABLE YES > SCOPE_CATLOG > SCOPE_SCHEMA > SCOPE_TABLE > SOURCE_DATA_TYPE null > IS_AUTOINCREMENT NO > IS_GENERATEDCOLUMN NO > > Column b and c has the wrong DATA_TYPE and TYPE_NAME. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10390) BPlusTree#isEmpty() does not release root page
[
https://issues.apache.org/jira/browse/IGNITE-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697075#comment-16697075
]
Igor Seliverstov commented on IGNITE-10390:
---
[~agoncharuk], looks OK
> BPlusTree#isEmpty() does not release root page
> --
>
> Key: IGNITE-10390
> URL: https://issues.apache.org/jira/browse/IGNITE-10390
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8
>
>
> {code}
> long rootId, rootPage = acquirePage(rootId = treeMeta.rootId);
> {code}
> The acquired page is never released. Corresponding tests should be added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10372) [TC Bot] Optimize master trends page
[ https://issues.apache.org/jira/browse/IGNITE-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697066#comment-16697066 ] Nikolai Kulagin commented on IGNITE-10372: -- [~dpavlov], looks good to me > [TC Bot] Optimize master trends page > > > Key: IGNITE-10372 > URL: https://issues.apache.org/jira/browse/IGNITE-10372 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > Now loading of the page may take up to several minutes. > It may be optimized > - by avoiding tests list obtaining from composites (instead we may load chain > of sub-builds) > - by creating a cache of loaded builds in memory (e.g. guava soft values for > the main method) > - by excluding of usage of deprecated REST caching API approach -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-6173) SQL: do not start caches on client nodes
[
https://issues.apache.org/jira/browse/IGNITE-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697058#comment-16697058
]
Yury Gerzhedovich edited comment on IGNITE-6173 at 11/23/18 12:18 PM:
--
[~vozerov],
Thanks for your priceless comments.
Could you please check a new patch as preliminary path. Just to check a main
idea of start H2 structures on non affinity nodes.
was (Author: jooger):
[~vozerov],
Thanks for your priceless comments.
Could you please check the patch again as preliminary path. Just to check a
main idea of start H2 structures on non affinity nodes.
> SQL: do not start caches on client nodes
>
>
> Key: IGNITE-6173
> URL: https://issues.apache.org/jira/browse/IGNITE-6173
> Project: Ignite
> Issue Type: Task
> Components: cache, sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: sql-stability
> Fix For: 2.8
>
>
> When cache is started, this even is distributed through custom discovery
> message. Server nodes start the cache, client nodes do nothing until cache is
> requested explicitly. At the same time H2 database objects are created only
> when cache is really started.
> For this reason query parsing could lead to {{TABLE NOT FOUND}}, {{INDEX NOT
> FOUND}}, etc. errors. If such exception is observed, we force start of all
> known cache on a client and then retry. See
> {{GridCacheProcessor#createMissingQueryCaches}} method.
> First, client node cache start leads to another custom discovery message. So
> query performance may suffer. Second, this is not needed! We already have all
> necessary cache info in discovery.
> Let's try to find a way to use available discovery data and do not start
> cache on a client for SQL query execution.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10339) Connection to cluster failed in control.sh while using --cache
[
https://issues.apache.org/jira/browse/IGNITE-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697060#comment-16697060
]
Ignite TC Bot commented on IGNITE-10339:
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Inspections] Core{color} [[tests 0 BuildFailureOnMetric
|https://ci.ignite.apache.org/viewLog.html?buildId=2385408]]
{color:#d04437}Continuous Query 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2380740]]
* CacheContinuousQueryFailoverMvccTxSelfTest.testFailoverStartStopBackup (last
started)
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2380830buildTypeId=IgniteTests24Java8_RunAll]
> Connection to cluster failed in control.sh while using --cache
> --
>
> Key: IGNITE-10339
> URL: https://issues.apache.org/jira/browse/IGNITE-10339
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.8
>
>
> This issue is related to https://issues.apache.org/jira/browse/IGNITE-8423
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-1478) Service cannot be used on remote node immediately after deployment.
[ https://issues.apache.org/jira/browse/IGNITE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-1478: --- Component/s: managed services > Service cannot be used on remote node immediately after deployment. > --- > > Key: IGNITE-1478 > URL: https://issues.apache.org/jira/browse/IGNITE-1478 > Project: Ignite > Issue Type: Task > Components: cache, managed services >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vyacheslav Daradur >Priority: Minor > Fix For: 2.8 > > > Consider the following scenario: > 1) Two nodes: A and B. > 2) Node A deploys cluster-wide service through IgniteServices.deploy(); > 3) Once we exited deploy() method we are trying to get the service on the > node B in any way (invoke it, get proxy, get descriptor, whatever). > Step 3 might fail. This happens because > GridServiceProcessor.AssignmentListener is not notified synchronously when > service cache is update in transaction. > As a result, transacion ends, node A informs us about successful service > deployment, but it is still not usable on remote nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-1478) Service cannot be used on remote node immediately after deployment.
[ https://issues.apache.org/jira/browse/IGNITE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-1478: --- Labels: iep-17 (was: ) > Service cannot be used on remote node immediately after deployment. > --- > > Key: IGNITE-1478 > URL: https://issues.apache.org/jira/browse/IGNITE-1478 > Project: Ignite > Issue Type: Task > Components: cache, managed services >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vyacheslav Daradur >Priority: Minor > Labels: iep-17 > Fix For: 2.8 > > > Consider the following scenario: > 1) Two nodes: A and B. > 2) Node A deploys cluster-wide service through IgniteServices.deploy(); > 3) Once we exited deploy() method we are trying to get the service on the > node B in any way (invoke it, get proxy, get descriptor, whatever). > Step 3 might fail. This happens because > GridServiceProcessor.AssignmentListener is not notified synchronously when > service cache is update in transaction. > As a result, transacion ends, node A informs us about successful service > deployment, but it is still not usable on remote nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-1478) Service cannot be used on remote node immediately after deployment.
[ https://issues.apache.org/jira/browse/IGNITE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-1478: --- Fix Version/s: 2.8 > Service cannot be used on remote node immediately after deployment. > --- > > Key: IGNITE-1478 > URL: https://issues.apache.org/jira/browse/IGNITE-1478 > Project: Ignite > Issue Type: Task > Components: cache >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vyacheslav Daradur >Priority: Minor > Fix For: 2.8 > > > Consider the following scenario: > 1) Two nodes: A and B. > 2) Node A deploys cluster-wide service through IgniteServices.deploy(); > 3) Once we exited deploy() method we are trying to get the service on the > node B in any way (invoke it, get proxy, get descriptor, whatever). > Step 3 might fail. This happens because > GridServiceProcessor.AssignmentListener is not notified synchronously when > service cache is update in transaction. > As a result, transacion ends, node A informs us about successful service > deployment, but it is still not usable on remote nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-1478) Service cannot be used on remote node immediately after deployment.
[ https://issues.apache.org/jira/browse/IGNITE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur reassigned IGNITE-1478: -- Assignee: Vyacheslav Daradur > Service cannot be used on remote node immediately after deployment. > --- > > Key: IGNITE-1478 > URL: https://issues.apache.org/jira/browse/IGNITE-1478 > Project: Ignite > Issue Type: Task > Components: cache >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vyacheslav Daradur >Priority: Minor > > Consider the following scenario: > 1) Two nodes: A and B. > 2) Node A deploys cluster-wide service through IgniteServices.deploy(); > 3) Once we exited deploy() method we are trying to get the service on the > node B in any way (invoke it, get proxy, get descriptor, whatever). > Step 3 might fail. This happens because > GridServiceProcessor.AssignmentListener is not notified synchronously when > service cache is update in transaction. > As a result, transacion ends, node A informs us about successful service > deployment, but it is still not usable on remote nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10329) Create JDBC "query" and "query join" benchmarks and compare them with Postgres and MySQL
[
https://issues.apache.org/jira/browse/IGNITE-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696699#comment-16696699
]
Pavel Kuznetsov commented on IGNITE-10329:
--
What is in scope:
1) Ignite inmemory
2) Ignite persistence on, data region fits all the data
3) Postgresql out of the box
4) Postgresql with increased {{shared_buffers}} to 10 GiB
5) Mysql out of the box
6) Mysql with increased caches
> Create JDBC "query" and "query join" benchmarks and compare them with
> Postgres and MySQL
>
>
> Key: IGNITE-10329
> URL: https://issues.apache.org/jira/browse/IGNITE-10329
> Project: Ignite
> Issue Type: Task
> Components: sql, yardstick
>Reporter: Vladimir Ozerov
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> Currently we have {{IgniteSqlQueryBenchmark}} and
> {{IgniteSqlQueryJoinBenchmark}} benchmarks which query data over salary range
> and optionally joins it with second table. Let's create a set of similar
> benchmarks which will use JDBC to load and query data, and execute them
> against one-node Ignite cluster, MySQL and Postgres.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9406) Improve SQL "Performance and Debugging" page
[ https://issues.apache.org/jira/browse/IGNITE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696694#comment-16696694 ] Vladimir Ozerov commented on IGNITE-9406: - [~Artem Budnikov], I do not understand what optimization this example should demonstrate. Could you please clarify? > Improve SQL "Performance and Debugging" page > > > Key: IGNITE-9406 > URL: https://issues.apache.org/jira/browse/IGNITE-9406 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > Attachments: ignite_sql_perf.txt > > > I prepared a document for one of Ignite clients with some advanced > information about how various performance optimizations work in Ignite SQL. > Let's compare this document with our "Performance and Debugging" page [1], > and enhance the latter with missing info (if any). > P.S.: Document is attached. Russian language. > [1] > https://apacheignite-sql.readme.io/docs/performance-and-debugging#query-execution-flow-optimizations -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10372) [TC Bot] Optimize master trends page
[ https://issues.apache.org/jira/browse/IGNITE-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696687#comment-16696687 ] ASF GitHub Bot commented on IGNITE-10372: - asfgit closed pull request #81: IGNITE-10372 Optimize master trends page step 3: Tests migrated to new concept URL: https://github.com/apache/ignite-teamcity-bot/pull/81 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [TC Bot] Optimize master trends page > > > Key: IGNITE-10372 > URL: https://issues.apache.org/jira/browse/IGNITE-10372 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > Now loading of the page may take up to several minutes. > It may be optimized > - by avoiding tests list obtaining from composites (instead we may load chain > of sub-builds) > - by creating a cache of loaded builds in memory (e.g. guava soft values for > the main method) > - by excluding of usage of deprecated REST caching API approach -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10356) JDBC thin driver returns wrong data type for Date and Decimal SQL type
[ https://issues.apache.org/jira/browse/IGNITE-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696684#comment-16696684 ] Vladimir Ozerov commented on IGNITE-10356: -- [~tledkov-gridgain], could you please take a look? > JDBC thin driver returns wrong data type for Date and Decimal SQL type > -- > > Key: IGNITE-10356 > URL: https://issues.apache.org/jira/browse/IGNITE-10356 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.6, 2.7 >Reporter: Ray >Assignee: Ray >Priority: Critical > Fix For: 2.8 > > > JDBC thin driver will return wrong metadata for column type when user creates > a table with Date and Decimal type. > > Steps to reproduce. > 1. Start one node and create table using this command > create table a(a varchar, b decimal,c date, primary key(a)); > 2. Run "!desc a" to show the metadata of table a > This results is as follows: > TABLE_CAT > TABLE_SCHEM PUBLIC > TABLE_NAME A > COLUMN_NAME A > DATA_TYPE 12 > TYPE_NAME VARCHAR > COLUMN_SIZE null > BUFFER_LENGTH null > DECIMAL_DIGITS null > NUM_PREC_RADIX 10 > NULLABLE 1 > REMARKS > COLUMN_DEF > SQL_DATA_TYPE 12 > SQL_DATETIME_SUB null > CHAR_OCTET_LENGTH 2147483647 > ORDINAL_POSITION 1 > IS_NULLABLE YES > SCOPE_CATLOG > SCOPE_SCHEMA > SCOPE_TABLE > SOURCE_DATA_TYPE null > IS_AUTOINCREMENT NO > IS_GENERATEDCOLUMN NO > TABLE_CAT > TABLE_SCHEM PUBLIC > TABLE_NAME A > COLUMN_NAME B > DATA_TYPE > TYPE_NAME OTHER > COLUMN_SIZE null > BUFFER_LENGTH null > DECIMAL_DIGITS null > NUM_PREC_RADIX 10 > NULLABLE 1 > REMARKS > COLUMN_DEF > SQL_DATA_TYPE > SQL_DATETIME_SUB null > CHAR_OCTET_LENGTH 2147483647 > ORDINAL_POSITION 2 > IS_NULLABLE YES > SCOPE_CATLOG > SCOPE_SCHEMA > SCOPE_TABLE > SOURCE_DATA_TYPE null > IS_AUTOINCREMENT NO > IS_GENERATEDCOLUMN NO > TABLE_CAT > TABLE_SCHEM PUBLIC > TABLE_NAME A > COLUMN_NAME C > DATA_TYPE > TYPE_NAME OTHER > COLUMN_SIZE null > BUFFER_LENGTH null > DECIMAL_DIGITS null > NUM_PREC_RADIX 10 > NULLABLE 1 > REMARKS > COLUMN_DEF > SQL_DATA_TYPE > SQL_DATETIME_SUB null > CHAR_OCTET_LENGTH 2147483647 > ORDINAL_POSITION 3 > IS_NULLABLE YES > SCOPE_CATLOG > SCOPE_SCHEMA > SCOPE_TABLE > SOURCE_DATA_TYPE null > IS_AUTOINCREMENT NO > IS_GENERATEDCOLUMN NO > > Column b and c has the wrong DATA_TYPE and TYPE_NAME. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10356) JDBC thin driver returns wrong data type for Date and Decimal SQL type
[ https://issues.apache.org/jira/browse/IGNITE-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10356: - Component/s: jdbc > JDBC thin driver returns wrong data type for Date and Decimal SQL type > -- > > Key: IGNITE-10356 > URL: https://issues.apache.org/jira/browse/IGNITE-10356 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.6, 2.7 >Reporter: Ray >Assignee: Ray >Priority: Critical > Fix For: 2.8 > > > JDBC thin driver will return wrong metadata for column type when user creates > a table with Date and Decimal type. > > Steps to reproduce. > 1. Start one node and create table using this command > create table a(a varchar, b decimal,c date, primary key(a)); > 2. Run "!desc a" to show the metadata of table a > This results is as follows: > TABLE_CAT > TABLE_SCHEM PUBLIC > TABLE_NAME A > COLUMN_NAME A > DATA_TYPE 12 > TYPE_NAME VARCHAR > COLUMN_SIZE null > BUFFER_LENGTH null > DECIMAL_DIGITS null > NUM_PREC_RADIX 10 > NULLABLE 1 > REMARKS > COLUMN_DEF > SQL_DATA_TYPE 12 > SQL_DATETIME_SUB null > CHAR_OCTET_LENGTH 2147483647 > ORDINAL_POSITION 1 > IS_NULLABLE YES > SCOPE_CATLOG > SCOPE_SCHEMA > SCOPE_TABLE > SOURCE_DATA_TYPE null > IS_AUTOINCREMENT NO > IS_GENERATEDCOLUMN NO > TABLE_CAT > TABLE_SCHEM PUBLIC > TABLE_NAME A > COLUMN_NAME B > DATA_TYPE > TYPE_NAME OTHER > COLUMN_SIZE null > BUFFER_LENGTH null > DECIMAL_DIGITS null > NUM_PREC_RADIX 10 > NULLABLE 1 > REMARKS > COLUMN_DEF > SQL_DATA_TYPE > SQL_DATETIME_SUB null > CHAR_OCTET_LENGTH 2147483647 > ORDINAL_POSITION 2 > IS_NULLABLE YES > SCOPE_CATLOG > SCOPE_SCHEMA > SCOPE_TABLE > SOURCE_DATA_TYPE null > IS_AUTOINCREMENT NO > IS_GENERATEDCOLUMN NO > TABLE_CAT > TABLE_SCHEM PUBLIC > TABLE_NAME A > COLUMN_NAME C > DATA_TYPE > TYPE_NAME OTHER > COLUMN_SIZE null > BUFFER_LENGTH null > DECIMAL_DIGITS null > NUM_PREC_RADIX 10 > NULLABLE 1 > REMARKS > COLUMN_DEF > SQL_DATA_TYPE > SQL_DATETIME_SUB null > CHAR_OCTET_LENGTH 2147483647 > ORDINAL_POSITION 3 > IS_NULLABLE YES > SCOPE_CATLOG > SCOPE_SCHEMA > SCOPE_TABLE > SOURCE_DATA_TYPE null > IS_AUTOINCREMENT NO > IS_GENERATEDCOLUMN NO > > Column b and c has the wrong DATA_TYPE and TYPE_NAME. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9777) Gathering local node IO statistics with cache and index dimensions
[ https://issues.apache.org/jira/browse/IGNITE-9777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696683#comment-16696683 ] Vladimir Ozerov commented on IGNITE-9777: - [~jooger], I would say yes, we need all of these. Normally we do not run so many benchmarks for a single ticket. But over the last month we missed a number of performance problems (TDE, WAL history) because we skipped some of these benchmarks. PR contains pretty sensitive change in terms of performance, so we'd better be on the safe side. > Gathering local node IO statistics with cache and index dimensions > -- > > Key: IGNITE-9777 > URL: https://issues.apache.org/jira/browse/IGNITE-9777 > Project: Ignite > Issue Type: Task > Components: persistence, sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-27 > Fix For: 2.8 > > > Should be gathered and exposed IO statistics on cache/index level. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10323) Contol utility --deactivate on non-activate cluster produse NPE and handler stop nodes
[
https://issues.apache.org/jira/browse/IGNITE-10323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696670#comment-16696670
]
ASF GitHub Bot commented on IGNITE-10323:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5476
> Contol utility --deactivate on non-activate cluster produse NPE and handler
> stop nodes
> --
>
> Key: IGNITE-10323
> URL: https://issues.apache.org/jira/browse/IGNITE-10323
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.7
>Reporter: ARomantsov
>Assignee: Vladislav Pyatkov
>Priority: Critical
> Fix For: 2.8
>
>
> Scenario:
> 1) Start cluster
> 2) Call control.sh --deactivate
> {noformat}
> org.apache.ignite.IgniteCheckedException: null
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7443)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:261)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:209)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2819)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2662)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1380)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:830)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2791)
> ... 3 common frames omitted
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10323) Contol utility --deactivate on non-activate cluster produse NPE and handler stop nodes
[
https://issues.apache.org/jira/browse/IGNITE-10323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696669#comment-16696669
]
Pavel Kovalenko commented on IGNITE-10323:
--
Failures are not related to changes. Inspections are already fixed, CQ2 test
fails on master branch also.
[~v.pyatkov] Thank you for contribution. Merged to master.
> Contol utility --deactivate on non-activate cluster produse NPE and handler
> stop nodes
> --
>
> Key: IGNITE-10323
> URL: https://issues.apache.org/jira/browse/IGNITE-10323
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.7
>Reporter: ARomantsov
>Assignee: Vladislav Pyatkov
>Priority: Critical
> Fix For: 2.8
>
>
> Scenario:
> 1) Start cluster
> 2) Call control.sh --deactivate
> {noformat}
> org.apache.ignite.IgniteCheckedException: null
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7443)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:261)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:209)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2819)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2662)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1380)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:830)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2791)
> ... 3 common frames omitted
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10108) Non-static class is passed between cluster nodes
[
https://issues.apache.org/jira/browse/IGNITE-10108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shtykh updated IGNITE-10108:
--
Fix Version/s: 2.8
> Non-static class is passed between cluster nodes
>
>
> Key: IGNITE-10108
> URL: https://issues.apache.org/jira/browse/IGNITE-10108
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Roman Shtykh
>Priority: Major
> Fix For: 2.8
>
>
> Need to avoid passing anonymous classes on compute, because this lead to
> serialize whole test-class context.
> By the reason need to refactor that place
> {code}
> ignite.compute().withTimeout(5_000).broadcastAsync(new IgniteRunnable() {
> ...
> });
> {code}
> in method \{{GridCommonAbstractTest#manualCacheRebalancing}} into private
> static nested class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10384) Stop cache groups in parallel on PME
[ https://issues.apache.org/jira/browse/IGNITE-10384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov reassigned IGNITE-10384: --- Assignee: (was: Sergey Antonov) > Stop cache groups in parallel on PME > > > Key: IGNITE-10384 > URL: https://issues.apache.org/jira/browse/IGNITE-10384 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Antonov >Priority: Major > Fix For: 2.8 > > > Stopping 6000+ caches sequentially go on more 80 seconds. We must parallel > this process. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7072) IgniteCache.replace(k, v, nv) does not work in binary mode without classes
[
https://issues.apache.org/jira/browse/IGNITE-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696665#comment-16696665
]
Ignite TC Bot commented on IGNITE-7072:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2362099buildTypeId=IgniteTests24Java8_RunAll]
> IgniteCache.replace(k, v, nv) does not work in binary mode without classes
> --
>
> Key: IGNITE-7072
> URL: https://issues.apache.org/jira/browse/IGNITE-7072
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Pavel Tupitsyn
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.8
>
>
> {{IgniteCache.replace(K key, V oldVal, V newVal)}} method deserializes cache
> values in order to compare them, which causes exception when classes are not
> present on server:
> {code}
> class org.apache.ignite.IgniteCheckedException: Unknown pair [platformId=0,
> typeId=-1690383137]
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7260)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.isAll(GridCacheContext.java:1242)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onEntriesLocked(GridDhtTxPrepareFuture.java:464)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1223)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:666)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1040)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareAsyncLocal(GridNearTxLocal.java:3452)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareColocatedTx(IgniteTxHandler.java:257)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.proceedPrepare(GridNearOptimisticTxPrepareFuture.java:574)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepareSingle(GridNearOptimisticTxPrepareFuture.java:401)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare0(GridNearOptimisticTxPrepareFuture.java:344)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFutureAdapter.prepareOnTopology(GridNearOptimisticTxPrepareFutureAdapter.java:137)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFutureAdapter.prepare(GridNearOptimisticTxPrepareFutureAdapter.java:74)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareNearTxLocal(GridNearTxLocal.java:3161)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitNearTxLocalAsync(GridNearTxLocal.java:3221)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.optimisticPutFuture(GridNearTxLocal.java:2391)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:622)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:385)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$34.op(GridCacheAdapter.java:2707)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$AsyncOp.op(GridCacheAdapter.java:5120)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4260)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$AsyncOpRetryFuture.execute(GridCacheAdapter.java:4841)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4173)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAsync0(GridCacheAdapter.java:2705)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAsync(GridCacheAdapter.java:2689)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.replaceAsync(GridCacheAdapter.java:2776)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.replaceAsync(IgniteCacheProxyImpl.java:1182)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.replaceAsync(GatewayProtectedCacheProxy.java:1082)
> at
>
[jira] [Commented] (IGNITE-9435) Document MVCC
[ https://issues.apache.org/jira/browse/IGNITE-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696658#comment-16696658 ] Artem Budnikov commented on IGNITE-9435: The feedback addressed in https://issues.apache.org/jira/browse/IGNITE-9880. > Document MVCC > - > > Key: IGNITE-9435 > URL: https://issues.apache.org/jira/browse/IGNITE-9435 > Project: Ignite > Issue Type: Task > Components: documentation, mvcc >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9943) Update documentation for default WAL archive size (added auto-adjust)
[ https://issues.apache.org/jira/browse/IGNITE-9943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696657#comment-16696657 ] Artem Budnikov commented on IGNITE-9943: [~agoncharuk] I updated the WAL archive section: [https://apacheignite.readme.io/v2.6/docs/write-ahead-log-1#section-wal-archive] Please review. > Update documentation for default WAL archive size (added auto-adjust) > - > > Key: IGNITE-9943 > URL: https://issues.apache.org/jira/browse/IGNITE-9943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10342) TC: Create "Run :: MVCC" suite.
[ https://issues.apache.org/jira/browse/IGNITE-10342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-10342: -- Description: Create "Run :: MVCC" that will be run "Mvcc Cache suites" with additional system property IGNITE_FORCE_MVCC_MODE_IN_TESTS=true. *Mvcc Cache 2* can be used as an example. All existed "Mvcc Cache X" suites should be recreated as they may use wrong template (JVM params and etc.). For now, "Run :: MVCC" should be run nightly, but we won't include it into "Run :: All" to save TC resources. The ideal solution would be to make "Run :: MVCC" to run all cache suites with given system property, but AFAIK it will make TC statistics broken as TC will mix Mvcc and non-mvcc runs. was: Create "Run :: MVCC" that will be run "Mvcc Cache suites" with additional system property IGNITE_FORCE_MVCC_MODE_IN_TESTS=true. *~[Excluded] Mvcc Cache 2* can be used as an example. For now, "Run :: MVCC" should be run nightly, but we won't include it into "Run :: All" to save TC resources. The ideal solution would be to make "Run :: MVCC" to run all cache suites with given system property, but AFAIK it will make TC statistics broken as TC will mix Mvcc and non-mvcc runs. > TC: Create "Run :: MVCC" suite. > --- > > Key: IGNITE-10342 > URL: https://issues.apache.org/jira/browse/IGNITE-10342 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Major > Labels: teamcity > Fix For: 2.8 > > > Create "Run :: MVCC" that will be run "Mvcc Cache suites" with additional > system property IGNITE_FORCE_MVCC_MODE_IN_TESTS=true. > *Mvcc Cache 2* can be used as an example. > All existed "Mvcc Cache X" suites should be recreated as they may use wrong > template (JVM params and etc.). > For now, "Run :: MVCC" should be run nightly, but we won't include it into > "Run :: All" to save TC resources. > > The ideal solution would be to make "Run :: MVCC" to run all cache suites > with given system property, but AFAIK it will make TC statistics broken as TC > will mix Mvcc and non-mvcc runs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9943) Update documentation for default WAL archive size (added auto-adjust)
[ https://issues.apache.org/jira/browse/IGNITE-9943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-9943: -- Assignee: Alexey Goncharuk (was: Artem Budnikov) > Update documentation for default WAL archive size (added auto-adjust) > - > > Key: IGNITE-9943 > URL: https://issues.apache.org/jira/browse/IGNITE-9943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10391) MVCC: Invoke request fails on backup while rebalance is in progress.
Andrew Mashenkov created IGNITE-10391: - Summary: MVCC: Invoke request fails on backup while rebalance is in progress. Key: IGNITE-10391 URL: https://issues.apache.org/jira/browse/IGNITE-10391 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Andrew Mashenkov Fix For: 2.8 Invoke request fails with Assertion on backup while rebalance is in progress. Enlist request handler expects entry processor instead of value in case of Invoke operation, but when rebalance is in progress we pass entry history to backup side. This causes assertion triggering. We have to handle correctly this case and apply history and then entry processor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9777) Gathering local node IO statistics with cache and index dimensions
[ https://issues.apache.org/jira/browse/IGNITE-9777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696633#comment-16696633 ] Yury Gerzhedovich commented on IGNITE-9777: --- [~vozerov], 1) Proposed interfaces has been implemented. 2) I have result of run Yardstick for FULL_SYNC, in-memory + all 4 WAL persistence modes, 4 servers, 8 clients. Is it enough? Or it need additional test runs for 1 client and Primary_SYNC mode? > Gathering local node IO statistics with cache and index dimensions > -- > > Key: IGNITE-9777 > URL: https://issues.apache.org/jira/browse/IGNITE-9777 > Project: Ignite > Issue Type: Task > Components: persistence, sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-27 > Fix For: 2.8 > > > Should be gathered and exposed IO statistics on cache/index level. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10390) BPlusTree#isEmpty() does not release root page
[
https://issues.apache.org/jira/browse/IGNITE-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696619#comment-16696619
]
ASF GitHub Bot commented on IGNITE-10390:
-
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/5486
IGNITE-10390 Fixed BPlusTree#isEmpty
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10390
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5486.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5486
commit fc8ee6b42785d4da11d19df26d2314b43ea53845
Author: Alexey Goncharuk
Date: 2018-11-23T10:07:42Z
IGNITE-10390 Fixed BPlusTree#isEmpty
> BPlusTree#isEmpty() does not release root page
> --
>
> Key: IGNITE-10390
> URL: https://issues.apache.org/jira/browse/IGNITE-10390
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8
>
>
> {code}
> long rootId, rootPage = acquirePage(rootId = treeMeta.rootId);
> {code}
> The acquired page is never released. Corresponding tests should be added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10390) BPlusTree#isEmpty() does not release root page
[
https://issues.apache.org/jira/browse/IGNITE-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-10390:
--
Ignite Flags: (was: Docs Required)
> BPlusTree#isEmpty() does not release root page
> --
>
> Key: IGNITE-10390
> URL: https://issues.apache.org/jira/browse/IGNITE-10390
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8
>
>
> {code}
> long rootId, rootPage = acquirePage(rootId = treeMeta.rootId);
> {code}
> The acquired page is never released. Corresponding tests should be added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10390) BPlusTree#isEmpty() does not release root page
[
https://issues.apache.org/jira/browse/IGNITE-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-10390:
--
Fix Version/s: 2.8
> BPlusTree#isEmpty() does not release root page
> --
>
> Key: IGNITE-10390
> URL: https://issues.apache.org/jira/browse/IGNITE-10390
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8
>
>
> {code}
> long rootId, rootPage = acquirePage(rootId = treeMeta.rootId);
> {code}
> The acquired page is never released. Corresponding tests should be added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10390) BPlusTree#isEmpty() does not release root page
[
https://issues.apache.org/jira/browse/IGNITE-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk reassigned IGNITE-10390:
-
Assignee: Alexey Goncharuk
> BPlusTree#isEmpty() does not release root page
> --
>
> Key: IGNITE-10390
> URL: https://issues.apache.org/jira/browse/IGNITE-10390
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
>
> {code}
> long rootId, rootPage = acquirePage(rootId = treeMeta.rootId);
> {code}
> The acquired page is never released. Corresponding tests should be added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
