[jira] [Commented] (IGNITE-11084) Change copyrights to 2019
[
https://issues.apache.org/jira/browse/IGNITE-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752565#comment-16752565
]
Dmitriy Pavlov commented on IGNITE-11084:
-
[~aealeksandrov]. I'm a little bit confused by checking of property value to be
!=0
If this property can be missed, then parseLong will fail.
If this property is always present then I think we don't need
Long.valueOf(IgniteProperties.get("ignite.build"))!=0
> Change copyrights to 2019
> -
>
> Key: IGNITE-11084
> URL: https://issues.apache.org/jira/browse/IGNITE-11084
> Project: Ignite
> Issue Type: Task
>Reporter: Andrey Aleksandrov
>Assignee: Andrey Aleksandrov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Every year copyright date should be changed. We can use the build date for it
> or local date for cases when Ignite built from the sources,
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples
[ https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752473#comment-16752473 ] Dmitriy Pavlov commented on IGNITE-6826: I feel this change is sensitive and we probably need to build up a consensus on the dev.list. > Change default DiscoverySpi ipFinder type for examples > -- > > Key: IGNITE-6826 > URL: https://issues.apache.org/jira/browse/IGNITE-6826 > Project: Ignite > Issue Type: Improvement > Components: examples >Affects Versions: 2.3 >Reporter: Alexey Popov >Assignee: Ryabov Dmitrii >Priority: Major > Labels: newbie > Fix For: 2.8 > > > It is better to change multicast ipFinder to static (vm) ipFinder for java > examples, .NET examples and C++ examples. > http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8227) Research possibility and implement JUnit test failure handler for TeamCity
[ https://issues.apache.org/jira/browse/IGNITE-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752391#comment-16752391 ] Dmitriy Pavlov commented on IGNITE-8227: [~SomeFire] can we somehow demonstrate that failure handler test failure process works properly? It may sound like nonsense, but can we create a test, which tests test failure? > Research possibility and implement JUnit test failure handler for TeamCity > -- > > Key: IGNITE-8227 > URL: https://issues.apache.org/jira/browse/IGNITE-8227 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Pavlov >Assignee: Ryabov Dmitrii >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > After IEP-14 > (https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling) > we found a lot of TC failures involving unexpected nodes stop. > To avoid suites exit codes, tests have NoOpFailureHandler as default. > But instead of this, better handler could be > stopNode + fail currenly running test with message. > This default allows to identify such failures without log-message fail > condition. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11084) Change copyrights to 2019
[ https://issues.apache.org/jira/browse/IGNITE-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11084: Ignite Flags: (was: Docs Required) > Change copyrights to 2019 > - > > Key: IGNITE-11084 > URL: https://issues.apache.org/jira/browse/IGNITE-11084 > Project: Ignite > Issue Type: Task >Reporter: Andrey Aleksandrov >Assignee: Andrey Aleksandrov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Change copyrights to 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10879) Create suite of Cassandra Cache Store tests, add to TC
[ https://issues.apache.org/jira/browse/IGNITE-10879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752365#comment-16752365 ] Dmitriy Pavlov commented on IGNITE-10879: - I've retriggered 3 suites > Create suite of Cassandra Cache Store tests, add to TC > -- > > Key: IGNITE-10879 > URL: https://issues.apache.org/jira/browse/IGNITE-10879 > Project: Ignite > Issue Type: Sub-task > Components: cassandra >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: test > Time Spent: 20m > Remaining Estimate: 0h > > Currently, they're not running in TC at all -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751593#comment-16751593
]
Dmitriy Pavlov commented on IGNITE-11030:
-
[~zstan], could you please review the fix in
https://github.com/apache/ignite/pull/5915 ?
Providing partId = 0 was affecting InitNewPage record and a page was erased in
the wrong partition.
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> -
>
> Key: IGNITE-11030
> URL: https://issues.apache.org/jira/browse/IGNITE-11030
> Project: Ignite
> Issue Type: Task
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> - TC Bot was stopped with kill command (default signal).
> - Shutdown hook calls ignite close
> But after updating to V190122 TC Bot DB was became unrecoverable for
> "teamcityTestRunHist" cache with exception
> {noformat}
> Failure periodic check failed: javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> com.google.common.util.concurrent.UncheckedExecutionException:
> javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2050)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3952)
> at
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4871)
> at
> org.apache.ignite.ci.di.cache.GuavaCachedInterceptor.invoke(GuavaCachedInterceptor.java:59)
> at
> org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.getTestRunHist(TeamcityIgnitedImpl.java:404)
> at
> org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.lambda$initFromContext$0(SuiteCurrentStatus.java:155)
> at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
> at
> java.util.Collections$ReverseComparator2.compare(Collections.java:5178)
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
> at java.util.TimSort.sort(TimSort.java:220)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1462)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.initFromContext(SuiteCurrentStatus.java:160)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.lambda$initFromContext$0(ChainAtServerCurrentStatus.java:171)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.initFromContext(ChainAtServerCurrentStatus.java:167)
> at
> org.apache.ignite.ci.tcbot.chain.TrackedBranchChainsProcessor.lambda$getTrackedBranchTestFailures$1(TrackedBranchChainsProcessor.java:121)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachO
[jira] [Commented] (IGNITE-10978) Remove unused tests marked with unclear todo
[
https://issues.apache.org/jira/browse/IGNITE-10978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751294#comment-16751294
]
Dmitriy Pavlov commented on IGNITE-10978:
-
[~agoncharuk] could you please confirm you are comfortable with the removal of
these ^ tests?
> Remove unused tests marked with unclear todo
>
>
> Key: IGNITE-10978
> URL: https://issues.apache.org/jira/browse/IGNITE-10978
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Dmitriy Pavlov
>Assignee: Konstantin Bolyandra
>Priority: Major
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> {noformat}
> IgniteCacheTestSuite3
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapValuesSelfTest.class,
> ignoredTests);
> IgniteCacheInterceptorSelfTestSuite
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagTxPartitionedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagReplicatedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagLocalSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagAtomicSelfTest.class,
> ignoredTests);
> {noformat}
> Test classes not used, so there is no reason to keep it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11030:
Fix Version/s: 2.8
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> -
>
> Key: IGNITE-11030
> URL: https://issues.apache.org/jira/browse/IGNITE-11030
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> - TC Bot was stopped with kill command (default signal).
> - Shutdown hook calls ignite close
> But after updating to V190122 TC Bot DB was became unrecoverable for
> "teamcityTestRunHist" cache with exception
> {noformat}
> Failure periodic check failed: javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> com.google.common.util.concurrent.UncheckedExecutionException:
> javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2050)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3952)
> at
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4871)
> at
> org.apache.ignite.ci.di.cache.GuavaCachedInterceptor.invoke(GuavaCachedInterceptor.java:59)
> at
> org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.getTestRunHist(TeamcityIgnitedImpl.java:404)
> at
> org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.lambda$initFromContext$0(SuiteCurrentStatus.java:155)
> at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
> at
> java.util.Collections$ReverseComparator2.compare(Collections.java:5178)
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
> at java.util.TimSort.sort(TimSort.java:220)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1462)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.initFromContext(SuiteCurrentStatus.java:160)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.lambda$initFromContext$0(ChainAtServerCurrentStatus.java:171)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.initFromContext(ChainAtServerCurrentStatus.java:167)
> at
> org.apache.ignite.ci.tcbot.chain.TrackedBranchChainsProcessor.lambda$getTrackedBranchTestFailures$1(TrackedBranchChainsProcessor.java:121)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePi
[jira] [Updated] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11030:
Component/s: persistence
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> -
>
> Key: IGNITE-11030
> URL: https://issues.apache.org/jira/browse/IGNITE-11030
> Project: Ignite
> Issue Type: Task
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> - TC Bot was stopped with kill command (default signal).
> - Shutdown hook calls ignite close
> But after updating to V190122 TC Bot DB was became unrecoverable for
> "teamcityTestRunHist" cache with exception
> {noformat}
> Failure periodic check failed: javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> com.google.common.util.concurrent.UncheckedExecutionException:
> javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2050)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3952)
> at
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4871)
> at
> org.apache.ignite.ci.di.cache.GuavaCachedInterceptor.invoke(GuavaCachedInterceptor.java:59)
> at
> org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.getTestRunHist(TeamcityIgnitedImpl.java:404)
> at
> org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.lambda$initFromContext$0(SuiteCurrentStatus.java:155)
> at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
> at
> java.util.Collections$ReverseComparator2.compare(Collections.java:5178)
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
> at java.util.TimSort.sort(TimSort.java:220)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1462)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.initFromContext(SuiteCurrentStatus.java:160)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.lambda$initFromContext$0(ChainAtServerCurrentStatus.java:171)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.initFromContext(ChainAtServerCurrentStatus.java:167)
> at
> org.apache.ignite.ci.tcbot.chain.TrackedBranchChainsProcessor.lambda$getTrackedBranchTestFailures$1(TrackedBranchChainsProcessor.java:121)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
>
[jira] [Updated] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11030:
Priority: Critical (was: Major)
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> -
>
> Key: IGNITE-11030
> URL: https://issues.apache.org/jira/browse/IGNITE-11030
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Time Spent: 10m
> Remaining Estimate: 0h
>
> - TC Bot was stopped with kill command (default signal).
> - Shutdown hook calls ignite close
> But after updating to V190122 TC Bot DB was became unrecoverable for
> "teamcityTestRunHist" cache with exception
> {noformat}
> Failure periodic check failed: javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> com.google.common.util.concurrent.UncheckedExecutionException:
> javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2050)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3952)
> at
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4871)
> at
> org.apache.ignite.ci.di.cache.GuavaCachedInterceptor.invoke(GuavaCachedInterceptor.java:59)
> at
> org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.getTestRunHist(TeamcityIgnitedImpl.java:404)
> at
> org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.lambda$initFromContext$0(SuiteCurrentStatus.java:155)
> at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
> at
> java.util.Collections$ReverseComparator2.compare(Collections.java:5178)
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
> at java.util.TimSort.sort(TimSort.java:220)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1462)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.initFromContext(SuiteCurrentStatus.java:160)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.lambda$initFromContext$0(ChainAtServerCurrentStatus.java:171)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.initFromContext(ChainAtServerCurrentStatus.java:167)
> at
> org.apache.ignite.ci.tcbot.chain.TrackedBranchChainsProcessor.lambda$getTrackedBranchTestFailures$1(TrackedBranchChainsProcessor.java:121)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.forEach(
[jira] [Commented] (IGNITE-11061) Сopyright still points out 2018
[ https://issues.apache.org/jira/browse/IGNITE-11061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751178#comment-16751178 ] Dmitriy Pavlov commented on IGNITE-11061: - Please fill ticket description, it is not clear where to find this copyright > Сopyright still points out 2018 > --- > > Key: IGNITE-11061 > URL: https://issues.apache.org/jira/browse/IGNITE-11061 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751177#comment-16751177
]
Dmitriy Pavlov commented on IGNITE-11030:
-
For -da option test is failed with the same trace as on TC Bot server:
{noformat}
more
Caused by: java.lang.IllegalStateException: Failed to get page IO instance
(page content is corrupted)
at
org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:85)
at
org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:97)
at
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.doInitFromLink(CacheDataRowAdapter.java:218)
at
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:138)
at
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:111)
at
org.apache.ignite.internal.processors.cache.tree.DataRow.(DataRow.java:55)
at
org.apache.ignite.internal.processors.cache.tree.CacheDataRowStore.dataRow(CacheDataRowStore.java:99)
at
org.apache.ignite.internal.processors.cache.tree.CacheDataTree.getRow(CacheDataTree.java:391)
at
org.apache.ignite.internal.processors.cache.tree.CacheDataTree.getRow(CacheDataTree.java:61)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetOne.found(BPlusTree.java:2902)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:300)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5643)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run(BPlusTree.java:273)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5629)
at
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:168)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.read(DataStructure.java:349)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.read(BPlusTree.java:5830)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findDown(BPlusTree.java:1314)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findDown(BPlusTree.java:1323)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findDown(BPlusTree.java:1323)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doFind(BPlusTree.java:1281)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findOne(BPlusTree.java:1249)
...
{noformat}
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> -
>
> Key: IGNITE-11030
> URL: https://issues.apache.org/jira/browse/IGNITE-11030
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> - TC Bot was stopped with kill command (default signal).
> - Shutdown hook calls ignite close
> But after updating to V190122 TC Bot DB was became unrecoverable for
> "teamcityTestRunHist" cache with exception
> {noformat}
> Failure periodic check failed: javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> com.google.common.util.concurrent.UncheckedExecutionException:
> javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2050)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3952)
> at
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4871)
> at
> org.apache.ignite.ci.di.cache.GuavaCachedInterceptor.invoke(GuavaCachedInterceptor.java:59)
> at
> org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.getTestRunHist(
[jira] [Resolved] (IGNITE-11049) [TC Bot] Reset Credentials is broken
[ https://issues.apache.org/jira/browse/IGNITE-11049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-11049. - Resolution: Fixed Fixed in 20190123, content type was set properly > [TC Bot] Reset Credentials is broken > > > Key: IGNITE-11049 > URL: https://issues.apache.org/jira/browse/IGNITE-11049 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > https://mtcga.gridgain.com/user.html > Reset credentials > gives > Internal Server Error [500]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11049) [TC Bot] Reset Credentials is broken
[ https://issues.apache.org/jira/browse/IGNITE-11049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov reassigned IGNITE-11049: --- Assignee: Dmitriy Pavlov > [TC Bot] Reset Credentials is broken > > > Key: IGNITE-11049 > URL: https://issues.apache.org/jira/browse/IGNITE-11049 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > https://mtcga.gridgain.com/user.html > Reset credentials > gives > Internal Server Error [500]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov reassigned IGNITE-11030:
---
Assignee: Dmitriy Pavlov
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> -
>
> Key: IGNITE-11030
> URL: https://issues.apache.org/jira/browse/IGNITE-11030
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> - TC Bot was stopped with kill command (default signal).
> - Shutdown hook calls ignite close
> But after updating to V190122 TC Bot DB was became unrecoverable for
> "teamcityTestRunHist" cache with exception
> {noformat}
> Failure periodic check failed: javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> com.google.common.util.concurrent.UncheckedExecutionException:
> javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2050)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3952)
> at
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4871)
> at
> org.apache.ignite.ci.di.cache.GuavaCachedInterceptor.invoke(GuavaCachedInterceptor.java:59)
> at
> org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.getTestRunHist(TeamcityIgnitedImpl.java:404)
> at
> org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.lambda$initFromContext$0(SuiteCurrentStatus.java:155)
> at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
> at
> java.util.Collections$ReverseComparator2.compare(Collections.java:5178)
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
> at java.util.TimSort.sort(TimSort.java:220)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1462)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.initFromContext(SuiteCurrentStatus.java:160)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.lambda$initFromContext$0(ChainAtServerCurrentStatus.java:171)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.initFromContext(ChainAtServerCurrentStatus.java:167)
> at
> org.apache.ignite.ci.tcbot.chain.TrackedBranchChainsProcessor.lambda$getTrackedBranchTestFailures$1(TrackedBranchChainsProcessor.java:121)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.forEach(Refe
[jira] [Commented] (IGNITE-10742) Replace java.io.Console to GridConsole
[ https://issues.apache.org/jira/browse/IGNITE-10742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750248#comment-16750248 ] Dmitriy Pavlov commented on IGNITE-10742: - Merged to master. [~antonovsergey93], [~ibessonov] thank you for the review. [~timerbaev] thank you for the contribution. > Replace java.io.Console to GridConsole > --- > > Key: IGNITE-10742 > URL: https://issues.apache.org/jira/browse/IGNITE-10742 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Antonov >Assignee: ramil >Priority: Minor > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > We should create and use GridConsole instead of java.io.Console because of > using Console in tests impossible. The API of GridConsole must be identical > Console API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750235#comment-16750235
]
Dmitriy Pavlov edited comment on IGNITE-11030 at 1/23/19 5:11 PM:
--
Scanning segment [248190], relIdx [0]
InitNewPageRecord:: pos=FileWALPointer [idx=248190, fileOff=7691736, len=45],
rec=InitNewPageRecord [newPageId=0001000145b4, super=PageDeltaRecord
[grpId=482599155, pageId=0101001a000145b4, super=WALRecord [size=45,
chainSize=0, pos=FileWALPointer [idx=248190, fileOff=7691736, len=45],
type=INIT_NEW_PAGE_RECORD]]], ioType=1, ioVersion=1[2019-01-23
19:31:04,287][ERROR][main][root] Test failed.
has different partitions:
pageId=101001a000145b4
newPageId= 1000145b4
was (Author: dpavlov):
pageId=101001a000145b4
newPageId= 1000145b4
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> -
>
> Key: IGNITE-11030
> URL: https://issues.apache.org/jira/browse/IGNITE-11030
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> - TC Bot was stopped with kill command (default signal).
> - Shutdown hook calls ignite close
> But after updating to V190122 TC Bot DB was became unrecoverable for
> "teamcityTestRunHist" cache with exception
> {noformat}
> Failure periodic check failed: javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> com.google.common.util.concurrent.UncheckedExecutionException:
> javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2050)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3952)
> at
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4871)
> at
> org.apache.ignite.ci.di.cache.GuavaCachedInterceptor.invoke(GuavaCachedInterceptor.java:59)
> at
> org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.getTestRunHist(TeamcityIgnitedImpl.java:404)
> at
> org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.lambda$initFromContext$0(SuiteCurrentStatus.java:155)
> at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
> at
> java.util.Collections$ReverseComparator2.compare(Collections.java:5178)
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
> at java.util.TimSort.sort(TimSort.java:220)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1462)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.initFromContext(SuiteCurrentStatus.java:160)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.lambda$initFromContext$0(ChainAtServerCurrentStatus.java:171)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.initFromContext(ChainAtServerCurrentStatus.java:167)
> at
> org.apache.ignite.ci.tcbot.chain.TrackedBranchChainsProcessor.lambda$getTrackedBranchTestFailures$1(TrackedBranchChainsProcessor.java:121)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at
> java.util.stream.ReferencePipeline$2$1
[jira] [Comment Edited] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750235#comment-16750235
]
Dmitriy Pavlov edited comment on IGNITE-11030 at 1/23/19 5:12 PM:
--
Scanning segment [248190], relIdx [0]
{noformat}
InitNewPageRecord:: pos=FileWALPointer [idx=248190, fileOff=7691736, len=45],
rec=InitNewPageRecord [newPageId=0001000145b4, super=PageDeltaRecord
[grpId=482599155, pageId=0101001a000145b4, super=WALRecord [size=45,
chainSize=0, pos=FileWALPointer [idx=248190, fileOff=7691736, len=45],
type=INIT_NEW_PAGE_RECORD]]], ioType=1, ioVersion=1[2019-01-23
19:31:04,287][ERROR][main][root] Test failed.
{noformat}
has different partitions:
{noformat}
pageId=101001a000145b4
newPageId= 1000145b4
{noformat}
was (Author: dpavlov):
Scanning segment [248190], relIdx [0]
InitNewPageRecord:: pos=FileWALPointer [idx=248190, fileOff=7691736, len=45],
rec=InitNewPageRecord [newPageId=0001000145b4, super=PageDeltaRecord
[grpId=482599155, pageId=0101001a000145b4, super=WALRecord [size=45,
chainSize=0, pos=FileWALPointer [idx=248190, fileOff=7691736, len=45],
type=INIT_NEW_PAGE_RECORD]]], ioType=1, ioVersion=1[2019-01-23
19:31:04,287][ERROR][main][root] Test failed.
has different partitions:
pageId=101001a000145b4
newPageId= 1000145b4
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> -
>
> Key: IGNITE-11030
> URL: https://issues.apache.org/jira/browse/IGNITE-11030
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> - TC Bot was stopped with kill command (default signal).
> - Shutdown hook calls ignite close
> But after updating to V190122 TC Bot DB was became unrecoverable for
> "teamcityTestRunHist" cache with exception
> {noformat}
> Failure periodic check failed: javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> com.google.common.util.concurrent.UncheckedExecutionException:
> javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2050)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3952)
> at
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4871)
> at
> org.apache.ignite.ci.di.cache.GuavaCachedInterceptor.invoke(GuavaCachedInterceptor.java:59)
> at
> org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.getTestRunHist(TeamcityIgnitedImpl.java:404)
> at
> org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.lambda$initFromContext$0(SuiteCurrentStatus.java:155)
> at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
> at
> java.util.Collections$ReverseComparator2.compare(Collections.java:5178)
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
> at java.util.TimSort.sort(TimSort.java:220)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1462)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.initFromContext(SuiteCurrentStatus.java:160)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.lambda$initFromContext$0(ChainAtServerCurrentStatus.java:171)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:
[jira] [Commented] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750235#comment-16750235
]
Dmitriy Pavlov commented on IGNITE-11030:
-
pageId=101001a000145b4
newPageId= 1000145b4
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> -
>
> Key: IGNITE-11030
> URL: https://issues.apache.org/jira/browse/IGNITE-11030
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> - TC Bot was stopped with kill command (default signal).
> - Shutdown hook calls ignite close
> But after updating to V190122 TC Bot DB was became unrecoverable for
> "teamcityTestRunHist" cache with exception
> {noformat}
> Failure periodic check failed: javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> com.google.common.util.concurrent.UncheckedExecutionException:
> javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2050)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3952)
> at
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4871)
> at
> org.apache.ignite.ci.di.cache.GuavaCachedInterceptor.invoke(GuavaCachedInterceptor.java:59)
> at
> org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.getTestRunHist(TeamcityIgnitedImpl.java:404)
> at
> org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.lambda$initFromContext$0(SuiteCurrentStatus.java:155)
> at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
> at
> java.util.Collections$ReverseComparator2.compare(Collections.java:5178)
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
> at java.util.TimSort.sort(TimSort.java:220)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1462)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.initFromContext(SuiteCurrentStatus.java:160)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.lambda$initFromContext$0(ChainAtServerCurrentStatus.java:171)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.initFromContext(ChainAtServerCurrentStatus.java:167)
> at
> org.apache.ignite.ci.tcbot.chain.TrackedBranchChainsProcessor.lambda$getTrackedBranchTestFailures$1(TrackedBranchChainsProcessor.java:121)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.s
[jira] [Updated] (IGNITE-11049) [TC Bot] Reset Credentials is broken
[ https://issues.apache.org/jira/browse/IGNITE-11049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11049: Ignite Flags: (was: Docs Required) > [TC Bot] Reset Credentials is broken > > > Key: IGNITE-11049 > URL: https://issues.apache.org/jira/browse/IGNITE-11049 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Priority: Major > > https://mtcga.gridgain.com/user.html > Reset credentials > gives > Internal Server Error [500]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11049) [TC Bot] Reset Credentials is broken
Dmitriy Pavlov created IGNITE-11049: --- Summary: [TC Bot] Reset Credentials is broken Key: IGNITE-11049 URL: https://issues.apache.org/jira/browse/IGNITE-11049 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov https://mtcga.gridgain.com/user.html Reset credentials gives Internal Server Error [500]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10742) Replace java.io.Console to GridConsole
[ https://issues.apache.org/jira/browse/IGNITE-10742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749837#comment-16749837 ] Dmitriy Pavlov commented on IGNITE-10742: - [~antonovsergey93] could you please review the solution? > Replace java.io.Console to GridConsole > --- > > Key: IGNITE-10742 > URL: https://issues.apache.org/jira/browse/IGNITE-10742 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Antonov >Assignee: ramil >Priority: Minor > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > We should create and use GridConsole instead of java.io.Console because of > using Console in tests impossible. The API of GridConsole must be identical > Console API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
Dmitriy Pavlov created IGNITE-11030:
---
Summary: Teamcity Bot cache is in unrecoverable state after bot
restart: need to check reasons
Key: IGNITE-11030
URL: https://issues.apache.org/jira/browse/IGNITE-11030
Project: Ignite
Issue Type: Task
Reporter: Dmitriy Pavlov
- TC Bot was stopped with kill command (default signal).
- Shutdown hook calls ignite close
But after updating to V190122 TC Bot DB was became unrecoverable for
"teamcityTestRunHist" cache with exception
{noformat}
Failure periodic check failed: javax.cache.CacheException: class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
Runtime failure on lookup row: SearchRow
[key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
[idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
branch=281], hash=1241170874, cacheId=0]
com.google.common.util.concurrent.UncheckedExecutionException:
javax.cache.CacheException: class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
Runtime failure on lookup row: SearchRow
[key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
[idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
branch=281], hash=1241170874, cacheId=0]
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2050)
at com.google.common.cache.LocalCache.get(LocalCache.java:3952)
at
com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4871)
at
org.apache.ignite.ci.di.cache.GuavaCachedInterceptor.invoke(GuavaCachedInterceptor.java:59)
at
org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.getTestRunHist(TeamcityIgnitedImpl.java:404)
at
org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
at
org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.lambda$initFromContext$0(SuiteCurrentStatus.java:155)
at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
at
java.util.Collections$ReverseComparator2.compare(Collections.java:5178)
at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
at java.util.TimSort.sort(TimSort.java:220)
at java.util.Arrays.sort(Arrays.java:1512)
at java.util.ArrayList.sort(ArrayList.java:1462)
at
org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.initFromContext(SuiteCurrentStatus.java:160)
at
org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.lambda$initFromContext$0(ChainAtServerCurrentStatus.java:171)
at
java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at
java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at
java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at
java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at
java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at
java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at
org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.initFromContext(ChainAtServerCurrentStatus.java:167)
at
org.apache.ignite.ci.tcbot.chain.TrackedBranchChainsProcessor.lambda$getTrackedBranchTestFailures$1(TrackedBranchChainsProcessor.java:121)
at
java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at
java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at
java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at
java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at
java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at
java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at
org.apache.ignite.ci.tcbot.chain.TrackedBranchChainsProcessor.getTrackedBranchTestFailures(TrackedBranchChainsProcessor.java:125)
at
org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
at
org.apache.ignite.ci.tcbot.issue.IssueDetector.checkFailuresEx(IssueDetector.java:445)
at
org.apache.ignite.ci.di.MonitoredTaskInterceptor.invoke(Monitore
[jira] [Commented] (IGNITE-10978) Remove unused tests marked with unclear todo
[
https://issues.apache.org/jira/browse/IGNITE-10978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747886#comment-16747886
]
Dmitriy Pavlov commented on IGNITE-10978:
-
[~ilyak], yes I agree. We should remove classes to avoid them to become lost
tests without correct explanation why the code is not running on CI server.
> Remove unused tests marked with unclear todo
>
>
> Key: IGNITE-10978
> URL: https://issues.apache.org/jira/browse/IGNITE-10978
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Dmitriy Pavlov
>Assignee: Konstantin Bolyandra
>Priority: Major
> Labels: newbie
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> IgniteCacheTestSuite3
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapValuesSelfTest.class,
> ignoredTests);
> IgniteCacheInterceptorSelfTestSuite
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagTxPartitionedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagReplicatedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagLocalSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagAtomicSelfTest.class,
> ignoredTests);
> {noformat}
> Test classes not used, so there is no reason to keep it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10978) Remove unused tests marked with unclear todo
[
https://issues.apache.org/jira/browse/IGNITE-10978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747858#comment-16747858
]
Dmitriy Pavlov commented on IGNITE-10978:
-
[~SomeFire] I absolutely agree with you in general, this approach is always
preferred.
But in this particular case, these tests were testing peer class loading for
cache entry (key/value). This case is not to be supported in the nearest
future, so we can remove tests for now. If later somebody will support this
case, VCS will have tests code in it.
> Remove unused tests marked with unclear todo
>
>
> Key: IGNITE-10978
> URL: https://issues.apache.org/jira/browse/IGNITE-10978
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Dmitriy Pavlov
>Assignee: Konstantin Bolyandra
>Priority: Major
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> IgniteCacheTestSuite3
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapValuesSelfTest.class,
> ignoredTests);
> IgniteCacheInterceptorSelfTestSuite
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagTxPartitionedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagReplicatedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagLocalSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagAtomicSelfTest.class,
> ignoredTests);
> {noformat}
> Test classes not used, so there is no reason to keep it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10989) [TC Bot] Finalize refactoring and remove REST data persistent caches
Dmitriy Pavlov created IGNITE-10989: --- Summary: [TC Bot] Finalize refactoring and remove REST data persistent caches Key: IGNITE-10989 URL: https://issues.apache.org/jira/browse/IGNITE-10989 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov TC Bot was migrated to compacted storage of builds, so now it is no reason to keep old-fashioned REST request caches for TeamCity data -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10863) Fix incorrect links to git repositories.
[ https://issues.apache.org/jira/browse/IGNITE-10863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-10863. - Resolution: Fixed Apache ignite site was updated > Fix incorrect links to git repositories. > > > Key: IGNITE-10863 > URL: https://issues.apache.org/jira/browse/IGNITE-10863 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Andrew Mashenkov >Assignee: Dmitriy Pavlov >Priority: Critical > Fix For: 2.8 > > > We have to refresh outdated links to project git repository. > [https://cwiki.apache.org/confluence/display/IGNITE/] [ > https://ignite.apache.org/community/resources.html#git] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10095) [TC Bot] Support Build Parameters storage in bot's DB and in run statistics
[ https://issues.apache.org/jira/browse/IGNITE-10095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10095: Ignite Flags: (was: Docs Required) > [TC Bot] Support Build Parameters storage in bot's DB and in run statistics > --- > > Key: IGNITE-10095 > URL: https://issues.apache.org/jira/browse/IGNITE-10095 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > [TC Bot] Support Build Parameters storage in bot's DB, and support > propagation of these parameters into run statistics > It is needed to have a future opportunity to separate Java 8,10,11 Runs and > also runs with short test set and full overnight run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10974) Node may hangs if an exception is throw from PageMemoryImpl.beforeReleaseWrite()
[
https://issues.apache.org/jira/browse/IGNITE-10974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746315#comment-16746315
]
Dmitriy Pavlov commented on IGNITE-10974:
-
LGTM for me provided that is it approved by the Bot.
> Node may hangs if an exception is throw from
> PageMemoryImpl.beforeReleaseWrite()
>
>
> Key: IGNITE-10974
> URL: https://issues.apache.org/jira/browse/IGNITE-10974
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> There are situations when a node may hang during stopping. Bug in the
> PageMemoryImpl.writeUnlockPage(), this method invokes
> PageMemoryImpl.beforeReleaseWrite() which may throw a exception and
> writeUnlockPage does not release page lock, after that checkpoint try to do
> final checkpoint (if stop was gracefully) and next access for this page hangs
> on obtain write lock.
> {code:java}
> [2019-01-17 14:35:15,953][WARN ][main][root] Thread dump at 2019/01/17
> 14:35:15 UTC
> [17:35:15]W: [org.apache.ignite:ignite-core] Thread
> [name="sys-#857%failure.IoomFailureHandlerTest0%", id=931,
> state=TIMED_WAITING, blockCnt=0, waitCnt=1]
> [17:35:15]W: [org.apache.ignite:ignite-core] Lock
> [object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@4339baec,
> ownerName=null, ownerId=-1]
> [17:35:15]W: [org.apache.ignite:ignite-core] at sun.misc.Unsafe.park(Native
> Method)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1073)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.lang.Thread.run(Thread.java:748)
> [17:35:15]W: [org.apache.ignite:ignite-core]
> [17:35:15]W: [org.apache.ignite:ignite-core] Thread
> [name="sys-#856%failure.IoomFailureHandlerTest0%", id=930,
> state=TIMED_WAITING, blockCnt=0, waitCnt=1]
> [17:35:15]W: [org.apache.ignite:ignite-core] Lock
> [object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@4339baec,
> ownerName=null, ownerId=-1]
> [17:35:15]W: [org.apache.ignite:ignite-core] at sun.misc.Unsafe.park(Native
> Method)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1073)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.lang.Thread.run(Thread.java:748)
> [17:35:15]W: [org.apache.ignite:ignite-core]
> [17:35:15]W: [org.apache.ignite:ignite-core] Thread
> [name="sys-#855%failure.IoomFailureHandlerTest0%", id=929,
> state=TIMED_WAITING, blockCnt=0, waitCnt=1]
> [17:35:15]W: [org.apache.ignite:ignite-core] Lock
> [object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@4339baec,
> ownerName=null, ownerId=-1]
> [17:35:15]W: [org.apache.ignite:ignite-core] at sun.misc.Unsafe.park(Native
> Method)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
> [17:35:15]W: [org.apache.
[jira] [Commented] (IGNITE-10974) Node may hangs if an exception is throw from PageMemoryImpl.beforeReleaseWrite()
[
https://issues.apache.org/jira/browse/IGNITE-10974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746284#comment-16746284
]
Dmitriy Pavlov commented on IGNITE-10974:
-
I left several comments and questions in the PR. Provided that TC bot issues a
green VISA, and comments will be addressed - I agree with the change.
> Node may hangs if an exception is throw from
> PageMemoryImpl.beforeReleaseWrite()
>
>
> Key: IGNITE-10974
> URL: https://issues.apache.org/jira/browse/IGNITE-10974
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> There are situations when a node may hang during stopping. Bug in the
> PageMemoryImpl.writeUnlockPage(), this method invokes
> PageMemoryImpl.beforeReleaseWrite() which may throw a exception and
> writeUnlockPage does not release page lock, after that checkpoint try to do
> final checkpoint (if stop was gracefully) and next access for this page hangs
> on obtain write lock.
> {code:java}
> [2019-01-17 14:35:15,953][WARN ][main][root] Thread dump at 2019/01/17
> 14:35:15 UTC
> [17:35:15]W: [org.apache.ignite:ignite-core] Thread
> [name="sys-#857%failure.IoomFailureHandlerTest0%", id=931,
> state=TIMED_WAITING, blockCnt=0, waitCnt=1]
> [17:35:15]W: [org.apache.ignite:ignite-core] Lock
> [object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@4339baec,
> ownerName=null, ownerId=-1]
> [17:35:15]W: [org.apache.ignite:ignite-core] at sun.misc.Unsafe.park(Native
> Method)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1073)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.lang.Thread.run(Thread.java:748)
> [17:35:15]W: [org.apache.ignite:ignite-core]
> [17:35:15]W: [org.apache.ignite:ignite-core] Thread
> [name="sys-#856%failure.IoomFailureHandlerTest0%", id=930,
> state=TIMED_WAITING, blockCnt=0, waitCnt=1]
> [17:35:15]W: [org.apache.ignite:ignite-core] Lock
> [object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@4339baec,
> ownerName=null, ownerId=-1]
> [17:35:15]W: [org.apache.ignite:ignite-core] at sun.misc.Unsafe.park(Native
> Method)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1073)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.lang.Thread.run(Thread.java:748)
> [17:35:15]W: [org.apache.ignite:ignite-core]
> [17:35:15]W: [org.apache.ignite:ignite-core] Thread
> [name="sys-#855%failure.IoomFailureHandlerTest0%", id=929,
> state=TIMED_WAITING, blockCnt=0, waitCnt=1]
> [17:35:15]W: [org.apache.ignite:ignite-core] Lock
> [object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@4339baec,
> ownerName=null, ownerId=-1]
> [17:35:15]W: [org.apache.ignite:ignite-core] at sun.misc.Unsafe.park(Native
> Method)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
> [17:35:15]W: [org.apache.ignite:ignite-core] at
> java.uti
[jira] [Assigned] (IGNITE-10978) Remove unused tests marked with unclear todo
[
https://issues.apache.org/jira/browse/IGNITE-10978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov reassigned IGNITE-10978:
---
Assignee: (was: Dmitriy Pavlov)
> Remove unused tests marked with unclear todo
>
>
> Key: IGNITE-10978
> URL: https://issues.apache.org/jira/browse/IGNITE-10978
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Priority: Major
> Labels: newbie
>
> {noformat}
> IgniteCacheTestSuite3
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapValuesSelfTest.class,
> ignoredTests);
> IgniteCacheInterceptorSelfTestSuite
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagTxPartitionedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagReplicatedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagLocalSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagAtomicSelfTest.class,
> ignoredTests);
> {noformat}
> Test classes not used, so there is no reason to keep it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10978) Remove unused tests marked with unclear todo
[
https://issues.apache.org/jira/browse/IGNITE-10978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10978:
Description:
{noformat}
IgniteCacheTestSuite3
// TODO GG-11141.
//
GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapValuesSelfTest.class,
ignoredTests);
IgniteCacheInterceptorSelfTestSuite
// TODO GG-11141.
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagTxPartitionedSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagReplicatedSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagLocalSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagAtomicSelfTest.class,
ignoredTests);
{noformat}
Test classes not used, so there is no reason to keep it
was:
{noformat}
// TODO GG-11141.
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagTxPartitionedSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagReplicatedSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagLocalSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagAtomicSelfTest.class,
ignoredTests);
{noformat}
Test classes not used, so there is no reason to keep it
> Remove unused tests marked with unclear todo
>
>
> Key: IGNITE-10978
> URL: https://issues.apache.org/jira/browse/IGNITE-10978
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Labels: newbie
>
> {noformat}
> IgniteCacheTestSuite3
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapValuesSelfTest.class,
> ignoredTests);
> IgniteCacheInterceptorSelfTestSuite
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagTxPartitionedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagReplicatedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagLocalSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagAtomicSelfTest.class,
> ignoredTests);
> {noformat}
> Test classes not used, so there is no reason to keep it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10978) Remove unused tests marked with unclear todo
[
https://issues.apache.org/jira/browse/IGNITE-10978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10978:
Labels: newbie (was: )
> Remove unused tests marked with unclear todo
>
>
> Key: IGNITE-10978
> URL: https://issues.apache.org/jira/browse/IGNITE-10978
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Labels: newbie
>
> {noformat}
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagTxPartitionedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagReplicatedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagLocalSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagAtomicSelfTest.class,
> ignoredTests);
> {noformat}
> Test classes not used, so there is no reason to keep it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10978) Remove unused tests marked with unclear todo
Dmitriy Pavlov created IGNITE-10978:
---
Summary: Remove unused tests marked with unclear todo
Key: IGNITE-10978
URL: https://issues.apache.org/jira/browse/IGNITE-10978
Project: Ignite
Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
{noformat}
// TODO GG-11141.
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagTxPartitionedSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagReplicatedSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagLocalSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagAtomicSelfTest.class,
ignoredTests);
{noformat}
Test classes not used, so there is no reason to keep it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-10942) [TC Bot] Optimize background JIRA tickets sync
[ https://issues.apache.org/jira/browse/IGNITE-10942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-10942. - Resolution: Fixed Done in V190118 > [TC Bot] Optimize background JIRA tickets sync > -- > > Key: IGNITE-10942 > URL: https://issues.apache.org/jira/browse/IGNITE-10942 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > JIRA sync is now performed in not an efficient manner. > All project data is reloaded every 15 minutes, and this may create additional > pressure for 3rd party services. > Introduce incremental updates (update is running only until the first > non-modified element found) and full updates. > Check ticket data modification before saving into Ignite DB (will safe WAL & > page store pressure). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10942) [TC Bot] Optimize background JIRA tickets sync
[ https://issues.apache.org/jira/browse/IGNITE-10942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10942: Summary: [TC Bot] Optimize background JIRA tickets sync (was: [TC Bot] Optimize backround JIRA tickets sync) > [TC Bot] Optimize background JIRA tickets sync > -- > > Key: IGNITE-10942 > URL: https://issues.apache.org/jira/browse/IGNITE-10942 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > JIRA sync is now performed in not an efficient manner. > All project data is reloaded every 15 minutes, and this may create additional > pressure for 3rd party services. > Introduce incremental updates (update is running only until the first > non-modified element found) and full updates. > Check ticket data modification before saving into Ignite DB (will safe WAL & > page store pressure). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10930) [TC Bot] Support PR-less contributions
[ https://issues.apache.org/jira/browse/IGNITE-10930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-10930. - Resolution: Fixed Supported in V190117 Now apache (origin) branches ignite- and its run-alls may be used for checking this code & obtaining TC Bot visa. > [TC Bot] Support PR-less contributions > -- > > Key: IGNITE-10930 > URL: https://issues.apache.org/jira/browse/IGNITE-10930 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > An Apache Ignite committer can prepare issue fix with origin/ignite-1 > branch. And this contributions testing does not require any PR creations, > because TC RunAll may be created without it. > Support contributions detection by provided TC run for branches matching > ignite-N, where N=0-9 > If such RunAll presented for any tracked branch and JIRA issue is in PA > state, we may display these branches as addition to PRs, show its report and > setup VISA into IGNITE-N ticket. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10942) [TC Bot] Optimize backround JIRA tickets sync
Dmitriy Pavlov created IGNITE-10942: --- Summary: [TC Bot] Optimize backround JIRA tickets sync Key: IGNITE-10942 URL: https://issues.apache.org/jira/browse/IGNITE-10942 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov JIRA sync is now performed in not an efficient manner. All project data is reloaded every 15 minutes, and this may create additional pressure for 3rd party services. Introduce incremental updates (update is running only until the first non-modified element found) and full updates. Check ticket data modification before saving into Ignite DB (will safe WAL & page store pressure). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10519) [TC Bot] Create project documentation
[ https://issues.apache.org/jira/browse/IGNITE-10519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-10519. - Resolution: Fixed [~PetrovMikhail] thank you for contributions. > [TC Bot] Create project documentation > - > > Key: IGNITE-10519 > URL: https://issues.apache.org/jira/browse/IGNITE-10519 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Minor > > Fill javadocs and package infos. > Create readme with multiclass interactions for developers with links to > package infos. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10519) [TC Bot] Create project documentation
[ https://issues.apache.org/jira/browse/IGNITE-10519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742048#comment-16742048 ] Dmitriy Pavlov edited comment on IGNITE-10519 at 1/14/19 1:15 PM: -- [~PetrovMikhail] thank you for contributions. Both PRs were merged to master. was (Author: dpavlov): [~PetrovMikhail] thank you for contributions. > [TC Bot] Create project documentation > - > > Key: IGNITE-10519 > URL: https://issues.apache.org/jira/browse/IGNITE-10519 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Minor > > Fill javadocs and package infos. > Create readme with multiclass interactions for developers with links to > package infos. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10930) [TC Bot] Support PR-less contributions
Dmitriy Pavlov created IGNITE-10930: --- Summary: [TC Bot] Support PR-less contributions Key: IGNITE-10930 URL: https://issues.apache.org/jira/browse/IGNITE-10930 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov An Apache Ignite committer can prepare issue fix with origin/ignite-1 branch. And this contributions testing does not require any PR creations, because TC RunAll may be created without it. Support contributions detection by provided TC run for branches matching ignite-N, where N=0-9 If such RunAll presented for any tracked branch and JIRA issue is in PA state, we may display these branches as addition to PRs, show its report and setup VISA into IGNITE-N ticket. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10677) [TC Bot] Include build failure on metric & exit code into critical failures
[ https://issues.apache.org/jira/browse/IGNITE-10677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-10677. - Resolution: Fixed Already supported in actual TC Bot version, V19 Compilation failure and inspections failure is considered as critical, 4 failures causes notification > [TC Bot] Include build failure on metric & exit code into critical failures > --- > > Key: IGNITE-10677 > URL: https://issues.apache.org/jira/browse/IGNITE-10677 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > It is necessary to setup dev.list notifications for _License&Headers_ failure > and for Inspections: Core failures notification -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9677) [TC Bot] Automatic build trigger should track all branches defined in configuration.
[
https://issues.apache.org/jira/browse/IGNITE-9677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov reassigned IGNITE-9677:
--
Assignee: Dmitriy Pavlov
> [TC Bot] Automatic build trigger should track all branches defined in
> configuration.
>
>
> Key: IGNITE-9677
> URL: https://issues.apache.org/jira/browse/IGNITE-9677
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Pereslegin
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> Automatic build trigger tracks only chains defined in branch with identifier
> "master", this should be changed to track all configured branches.
> Also before bot starts build it checks that there is no self-started builds
> in queue already, this check should be improved to be able start another
> branch build simultaneously (skip triggering only if build's {{branchName}}
> is equal to {{branchForRest}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9677) [TC Bot] Automatic build trigger should track all branches defined in configuration.
[
https://issues.apache.org/jira/browse/IGNITE-9677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9677:
---
Ignite Flags: (was: Docs Required)
> [TC Bot] Automatic build trigger should track all branches defined in
> configuration.
>
>
> Key: IGNITE-9677
> URL: https://issues.apache.org/jira/browse/IGNITE-9677
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Pereslegin
>Priority: Major
>
> Automatic build trigger tracks only chains defined in branch with identifier
> "master", this should be changed to track all configured branches.
> Also before bot starts build it checks that there is no self-started builds
> in queue already, this check should be improved to be able start another
> branch build simultaneously (skip triggering only if build's {{branchName}}
> is equal to {{branchForRest}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-7920) Research local crash recovery speed after stop in the middle of checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-7920. Resolution: Information Provided > Research local crash recovery speed after stop in the middle of checkpoint > -- > > Key: IGNITE-7920 > URL: https://issues.apache.org/jira/browse/IGNITE-7920 > Project: Ignite > Issue Type: Task > Components: persistence >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > When using Ignite as a database on one node, I observed that the recovery > time using the WAL exceeds the time between checkpoints. > Ignite logs message that it is restored after stopping in the middle of the > checkpoint > I use the frequency of CP - setCheckpointFrequency (60 * 1000), but at server > with HDD and heavy IO load. At least 16 minutes required to restore Ignite > after stop. > Server monitoring states that high rate of IOPS ocurred and it is constraint > (there is plenty of CPU/RAM) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9677) [TC Bot] Automatic build trigger should track all branches defined in configuration.
[
https://issues.apache.org/jira/browse/IGNITE-9677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov resolved IGNITE-9677.
Resolution: Fixed
Fixed in V19... TC bot.
Now code is able to trigger and monitor unlimited number of bracnhes
> [TC Bot] Automatic build trigger should track all branches defined in
> configuration.
>
>
> Key: IGNITE-9677
> URL: https://issues.apache.org/jira/browse/IGNITE-9677
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Pereslegin
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> Automatic build trigger tracks only chains defined in branch with identifier
> "master", this should be changed to track all configured branches.
> Also before bot starts build it checks that there is no self-started builds
> in queue already, this check should be improved to be able start another
> branch build simultaneously (skip triggering only if build's {{branchName}}
> is equal to {{branchForRest}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7153) Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for values > 8kb
[
https://issues.apache.org/jira/browse/IGNITE-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16741930#comment-16741930
]
Dmitriy Pavlov commented on IGNITE-7153:
I concerned about test failures
- IgniteClientTestSuite: RedisProtocolConnectSelfTest.testSetBigObject1
- IgniteClientTestSuite: RedisProtocolStringSelfTest.testGetSet - 0,0% fails in
last 571 master runs.
It may be related by the proposed change.
> Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for
> values > 8kb
> ---
>
> Key: IGNITE-7153
> URL: https://issues.apache.org/jira/browse/IGNITE-7153
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.3
> Environment: Win, PHP 7, php_redis-3.1.1-7.0
>Reporter: Alexey Popov
>Assignee: Michael Fong
>Priority: Major
> Labels: redis
>
> Exception:
> {noformat}
> [15:03:23,690][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol]
> Failed to process selector key [ses=GridSelectorNioSessionImpl
> [worker=ByteBufferNioClientWorker [readBuf=java.nio.HeapByteBuffer[pos=28
> lim=8192 cap=8192], super=AbstractNioClientWorker [idx=0, bytesRcvd=0,
> bytesSent=0, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker
> [name=grid-nio-worker-tcp-rest-0, igniteInstanceName=null, finished=false,
> hashCode=396395638, interrupted=false,
> runner=grid-nio-worker-tcp-rest-0-#36]]], writeBuf=null, readBuf=null,
> inRecovery=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/127.0.0.1:6380, rmtAddr=/127.0.0.1:51794, createTime=1512734602674,
> closeTime=0, bytesSent=0, bytesRcvd=8192, bytesSent0=0, bytesRcvd0=8192,
> sndSchedTime=1512734602674, lastSndTime=1512734602674,
> lastRcvTime=1512734602674, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioCodecFilter [parser=GridTcpRestParser
> [jdkMarshaller=JdkMarshaller [], routerClient=false], directMode=false]],
> accepted=true]]]
> java.nio.BufferUnderflowException
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:150)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:70)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3392)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1096)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2272)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> [15:03:23,691][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol]
> Closing NIO session because of unhandled exception.
> class org.apache.ignite.internal.util.nio.GridNioException: null
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2296)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.nio.BufferUnderflowException
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
> at
> org.apache.ignite.internal.processors.r
[jira] [Updated] (IGNITE-10775) Migrate from JUnit 3 to 4 test suites of simple dynamic lists that use addTestIfNeeded API
[
https://issues.apache.org/jira/browse/IGNITE-10775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10775:
Fix Version/s: 2.8
> Migrate from JUnit 3 to 4 test suites of simple dynamic lists that use
> addTestIfNeeded API
> --
>
> Key: IGNITE-10775
> URL: https://issues.apache.org/jira/browse/IGNITE-10775
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> This task is to migrate from JUnit 3 to 4 test suites of simple dynamic lists
> that use {{GridTestUtils.addTestIfNeeded}} API.
> If needed, refer parent task comments for more details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10863) Fix incorrect links to git repositories.
[ https://issues.apache.org/jira/browse/IGNITE-10863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov reassigned IGNITE-10863: --- Assignee: Dmitriy Pavlov > Fix incorrect links to git repositories. > > > Key: IGNITE-10863 > URL: https://issues.apache.org/jira/browse/IGNITE-10863 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Andrew Mashenkov >Assignee: Dmitriy Pavlov >Priority: Critical > Fix For: 2.8 > > > We have to refresh outdated links to project git repository. > [https://cwiki.apache.org/confluence/display/IGNITE/] [ > https://ignite.apache.org/community/resources.html#git] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10732) Incorrect file.encoding leads to inconsistent SqlFieldsQuery results between nodes
[
https://issues.apache.org/jira/browse/IGNITE-10732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738246#comment-16738246
]
Dmitriy Pavlov commented on IGNITE-10732:
-
[~ilyak], it is OK for me to keep warning, but I still think odd warning may
confuse users.
> Incorrect file.encoding leads to inconsistent SqlFieldsQuery results between
> nodes
> --
>
> Key: IGNITE-10732
> URL: https://issues.apache.org/jira/browse/IGNITE-10732
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.4
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Labels: windows
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When doing
> {code}
> cache.query(new SqlFieldsQuery("SELECT _key FROM Cache"))
> {code}
> resulting Unicode values may be different when coming from Windows or Linux
> node.
> Linux nodes will mostly use UTF-8 but Windows nodes will use local Cp
> encoding to encode query results, as bizzare as it may sound.
> Windows < - > Windows and Linux < - > Linux will get correct result but
> Windows < - > Linux will get broken strings.
> Note that if cluster has Windows and Linux nodes and cache is REPLICATED,
> results will be different for subsequent queries!
> There is a workaround for this: set -Dfile.encoding=UTF-8 JVM arg on Windows.
> There is probably an underlying problem in H2 but since non-UTF-8
> file.encoding is dangerous (it affects String.getBytes()) I think we should
> peg it to UTF-8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10863) Fix incorrect links to git repositories.
[ https://issues.apache.org/jira/browse/IGNITE-10863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10863: Ignite Flags: (was: Docs Required) > Fix incorrect links to git repositories. > > > Key: IGNITE-10863 > URL: https://issues.apache.org/jira/browse/IGNITE-10863 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Andrew Mashenkov >Priority: Critical > Fix For: 2.8 > > > We have to refresh outdated links to project git repository. > [https://cwiki.apache.org/confluence/display/IGNITE/] [ > https://ignite.apache.org/community/resources.html#git] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10863) Fix incorrect links to git repositories.
[ https://issues.apache.org/jira/browse/IGNITE-10863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738078#comment-16738078 ] Dmitriy Pavlov commented on IGNITE-10863: - Wiki was updated > Fix incorrect links to git repositories. > > > Key: IGNITE-10863 > URL: https://issues.apache.org/jira/browse/IGNITE-10863 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Andrew Mashenkov >Priority: Critical > Fix For: 2.8 > > > We have to refresh outdated links to project git repository. > [https://cwiki.apache.org/confluence/display/IGNITE/] [ > https://ignite.apache.org/community/resources.html#git] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9858) [Test Failed] SystemCacheNotConfiguredTest#test flaky fails on TC (timeout).
[
https://issues.apache.org/jira/browse/IGNITE-9858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733473#comment-16733473
]
Dmitriy Pavlov commented on IGNITE-9858:
[~xtern] [~DmitriyGovorukhin] I see there are no comments here since Dec 11,
but from issue description, it seems to be a test fix. Could you please find a
spare minute to finalize the review?
> [Test Failed] SystemCacheNotConfiguredTest#test flaky fails on TC (timeout).
>
>
> Key: IGNITE-9858
> URL: https://issues.apache.org/jira/browse/IGNITE-9858
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> SystemCacheNotConfiguredTest hangs sometimes on TeamCity (timeout).
> Example of such failures on master branch:
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&buildTypeId=&tab=testDetails&testNameId=-2762467041583095183&order=TEST_STATUS_DESC&itemsCount=50&branch_IgniteTests24Java8=%3Cdefault%3E]
> When we using ip finder in shared mode each node should register self address
> (except clients, obviously).
> Check that the node is a client uses installed (via DI
> @IgniteInstanceResource) Ignite instance (see
> {{TcpDiscoveryIpFinderAdapter#initializeLocalAddresses}}).
> So when client and server starts simultaneously, the following scenario is
> possible - Ignite server injected at first, then the Ignite client injected
> when the SPI is initialized ({{spiStart}}) both nodes assume that the local
> node is a client and don't register local address.
> {noformat}
> [2018-10-11 18:03:49,794][WARN
> ][tcp-client-disco-msg-worker-#57%client%][TcpDiscoverySpi] IP finder
> returned empty addresses list. Please check IP finder configuration. Will
> retry every 2000 ms. Change 'reconnectDelay' to configure the frequency of
> retries.{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10748) Remove dead code in TcpCommunicationSpi for the tcp client creation flow
[
https://issues.apache.org/jira/browse/IGNITE-10748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733479#comment-16733479
]
Dmitriy Pavlov commented on IGNITE-10748:
-
[~sergey-chugunov], maybe you can review. Would you have spare cycles to burn?
> Remove dead code in TcpCommunicationSpi for the tcp client creation flow
>
>
> Key: IGNITE-10748
> URL: https://issues.apache.org/jira/browse/IGNITE-10748
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
> Fix For: 2.8
>
>
> Currently, a batch of changes can be applied over {{TcpCommunicationSpi}}
> class implementation due to:
> # {{safeTcpHandshake(..)}}
> #* {{handshakeConnIdx}} - parameter is always not null
> #* {{recovery}} - parameter is always not null
> #* {{HandhakeMessage}} - is not used in current flow at all
> # {{HandshakeMessage2}}
> #* Message size must be defined in the message class as constant
> # {{createTcpClient(..)}}
> #* Instantiation of {{GridTcpNioCommunicationClient}} must be performed
> outside the while-loop
> # Code-style issues. Fix one-liner if statements.
> # Extract internal {{HandshakeException}}, {{HandshakeTimeoutException}} from
> class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9859) add debug logging on refreshPartitions cause
[ https://issues.apache.org/jira/browse/IGNITE-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov reassigned IGNITE-9859: -- Assignee: Max Shonichev > add debug logging on refreshPartitions cause > > > Key: IGNITE-9859 > URL: https://issues.apache.org/jira/browse/IGNITE-9859 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Max Shonichev >Assignee: Max Shonichev >Priority: Major > Fix For: 2.8 > > Attachments: > IGNITE_9859__add_debug_logging_on_resendPartitions_cause.patch > > > Need some additional log messages for debugging PME issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9859) add debug logging on refreshPartitions cause
[ https://issues.apache.org/jira/browse/IGNITE-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733476#comment-16733476 ] Dmitriy Pavlov commented on IGNITE-9859: [~mshonichev] I've assigned this issue to you by lazy consensus (approve via silence). I hope you don't mind > add debug logging on refreshPartitions cause > > > Key: IGNITE-9859 > URL: https://issues.apache.org/jira/browse/IGNITE-9859 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Max Shonichev >Assignee: Max Shonichev >Priority: Major > Fix For: 2.8 > > Attachments: > IGNITE_9859__add_debug_logging_on_resendPartitions_cause.patch > > > Need some additional log messages for debugging PME issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10856) cassandra-store seems to be broken by incorrect guava version
[ https://issues.apache.org/jira/browse/IGNITE-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733049#comment-16733049 ] Dmitriy Pavlov commented on IGNITE-10856: - I've set blocker priority. According to the user list there can be workaround, so it is not a reason to prepare emergency release, but I'm sure it should be blocker > cassandra-store seems to be broken by incorrect guava version > - > > Key: IGNITE-10856 > URL: https://issues.apache.org/jira/browse/IGNITE-10856 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Priority: Blocker > Fix For: 2.8 > > > IGNITE-9131 upgrade guava from 18 to 25. > However, cassandra-driver-core:3.0 dependency of the Ignite's cassandra-store > requires guava 16-19. > Need to fix the dependency conflict there. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10856) cassandra-store seems to be broken by incorrect guava version
[ https://issues.apache.org/jira/browse/IGNITE-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10856: Ignite Flags: (was: Docs Required) > cassandra-store seems to be broken by incorrect guava version > - > > Key: IGNITE-10856 > URL: https://issues.apache.org/jira/browse/IGNITE-10856 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Priority: Major > Fix For: 2.8 > > > IGNITE-9131 upgrade guava from 18 to 25. > However, cassandra-driver-core:3.0 dependency of the Ignite's cassandra-store > requires guava 16-19. > Need to fix the dependency conflict there. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10856) cassandra-store seems to be broken by incorrect guava version
[ https://issues.apache.org/jira/browse/IGNITE-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10856: Priority: Blocker (was: Major) > cassandra-store seems to be broken by incorrect guava version > - > > Key: IGNITE-10856 > URL: https://issues.apache.org/jira/browse/IGNITE-10856 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Priority: Blocker > Fix For: 2.8 > > > IGNITE-9131 upgrade guava from 18 to 25. > However, cassandra-driver-core:3.0 dependency of the Ignite's cassandra-store > requires guava 16-19. > Need to fix the dependency conflict there. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10732) Incorrect file.encoding leads to inconsistent SqlFieldsQuery results between nodes
[
https://issues.apache.org/jira/browse/IGNITE-10732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731323#comment-16731323
]
Dmitriy Pavlov commented on IGNITE-10732:
-
[~ilyak] I left only 1 comment in the PR and I'm concerned about a case when
user set non-UTF-8 encoding cluster-wide but set it for all nodes without
mistakes. Will user get a warning in this case? I believe user may potentially
want to have another encoding.
> Incorrect file.encoding leads to inconsistent SqlFieldsQuery results between
> nodes
> --
>
> Key: IGNITE-10732
> URL: https://issues.apache.org/jira/browse/IGNITE-10732
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.4
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Labels: windows
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When doing
> {code}
> cache.query(new SqlFieldsQuery("SELECT _key FROM Cache"))
> {code}
> resulting Unicode values may be different when coming from Windows or Linux
> node.
> Linux nodes will mostly use UTF-8 but Windows nodes will use local Cp
> encoding to encode query results, as bizzare as it may sound.
> Windows < - > Windows and Linux < - > Linux will get correct result but
> Windows < - > Linux will get broken strings.
> Note that if cluster has Windows and Linux nodes and cache is REPLICATED,
> results will be different for subsequent queries!
> There is a workaround for this: set -Dfile.encoding=UTF-8 JVM arg on Windows.
> There is probably an underlying problem in H2 but since non-UTF-8
> file.encoding is dangerous (it affects String.getBytes()) I think we should
> peg it to UTF-8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10854) Change git URL in apply-pull-request.sh to gitbox
[ https://issues.apache.org/jira/browse/IGNITE-10854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10854: Ignite Flags: (was: Docs Required) > Change git URL in apply-pull-request.sh to gitbox > - > > Key: IGNITE-10854 > URL: https://issues.apache.org/jira/browse/IGNITE-10854 > Project: Ignite > Issue Type: Task >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Minor > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10854) Change git URL in apply-pull-request.sh to gitbox
[ https://issues.apache.org/jira/browse/IGNITE-10854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10854: Description: Git remotes were changed due to migration from git-wip-us server to gitbox. > Change git URL in apply-pull-request.sh to gitbox > - > > Key: IGNITE-10854 > URL: https://issues.apache.org/jira/browse/IGNITE-10854 > Project: Ignite > Issue Type: Task >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Minor > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Git remotes were changed due to migration from git-wip-us server to gitbox. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10854) Change git URL in apply-pull-request.sh to gitbox
[ https://issues.apache.org/jira/browse/IGNITE-10854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10854: Fix Version/s: 2.8 > Change git URL in apply-pull-request.sh to gitbox > - > > Key: IGNITE-10854 > URL: https://issues.apache.org/jira/browse/IGNITE-10854 > Project: Ignite > Issue Type: Task >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Minor > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10854) Change git URL in apply-pull-request.sh to gitbox
[ https://issues.apache.org/jira/browse/IGNITE-10854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731251#comment-16731251 ] Dmitriy Pavlov commented on IGNITE-10854: - [~roman_s] LGTM, thank you. I've missed we need update this script. > Change git URL in apply-pull-request.sh to gitbox > - > > Key: IGNITE-10854 > URL: https://issues.apache.org/jira/browse/IGNITE-10854 > Project: Ignite > Issue Type: Task >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10835) Test failure in IgnitePdsReplacementNativeIoTest
[ https://issues.apache.org/jira/browse/IGNITE-10835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10835: Ignite Flags: (was: Docs Required) > Test failure in IgnitePdsReplacementNativeIoTest > > > Key: IGNITE-10835 > URL: https://issues.apache.org/jira/browse/IGNITE-10835 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6, 2.7 > Environment: Linux Ubuntu 16.04 big endian >Reporter: Namrata Bhave >Priority: Major > > Hi, > `IgnitePdsReplacementNativeIoTest.testPageReplacement` from `direct-io` fails > with below error on big endian platform: > _[ERROR] > IgnitePdsReplacementNativeIoTest>GridAbstractTest.access$000:143->GridAbstractTest.runTestInternal:2177->testPageReplacement:42->IgnitePdsPageReplacementTest.testPageReplacement:123->IgnitePdsPageReplacementTest.writeData:144 > Page buffer order LITTLE_ENDIAN should be same with BIG_ENDIAN_ > The error is thrown from > [FilePageStore.java|https://github.com/apache/ignite/blob/2.7.0/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/file/FilePageStore.java#L548 > ] during write function. This is happening since header order is set to > LITTLE_ENDIAN in code. > How to handle this functionality on Big endian? > Could someone please help in resolving this error? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10832) [TC Bot] Auto-trigger check win agents availability before triggering a build
[ https://issues.apache.org/jira/browse/IGNITE-10832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10832: Ignite Flags: (was: Docs Required) > [TC Bot] Auto-trigger check win agents availability before triggering a build > - > > Key: IGNITE-10832 > URL: https://issues.apache.org/jira/browse/IGNITE-10832 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > Currently, Win Agents may be a bottle-neck in TC throughput. > So it is reasonable to check constraint availability, but not only overall > pool of agents -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10832) [TC Bot] Auto-trigger check win agents availability before triggering a build
Dmitriy Pavlov created IGNITE-10832: --- Summary: [TC Bot] Auto-trigger check win agents availability before triggering a build Key: IGNITE-10832 URL: https://issues.apache.org/jira/browse/IGNITE-10832 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Currently, Win Agents may be a bottle-neck in TC throughput. So it is reasonable to check constraint availability, but not only overall pool of agents -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-995) Nodes on one host doesn't discover each other if IP finder doesn't explicitly provide port
[ https://issues.apache.org/jira/browse/IGNITE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729529#comment-16729529 ] Dmitriy Pavlov commented on IGNITE-995: --- Hi [~mlipkovich] could you please merge current master into your branch so we could validate TeamCity Results for related branch? > Nodes on one host doesn't discover each other if IP finder doesn't explicitly > provide port > -- > > Key: IGNITE-995 > URL: https://issues.apache.org/jira/browse/IGNITE-995 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: sprint-4 >Reporter: Valentin Kulichenko >Assignee: Mikhail Lipkovich >Priority: Major > Labels: Usability, newbie > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7054) S3 IP finder: support client side encryption
[
https://issues.apache.org/jira/browse/IGNITE-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729510#comment-16729510
]
Dmitriy Pavlov commented on IGNITE-7054:
[~vkulichenko] thank you for your efforts while reviewing this patch
> S3 IP finder: support client side encryption
>
>
> Key: IGNITE-7054
> URL: https://issues.apache.org/jira/browse/IGNITE-7054
> Project: Ignite
> Issue Type: Improvement
> Components: s3
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Uday Kale
>Priority: Major
> Fix For: 2.8
>
>
> In case client side encryption [1] is used, it may be required to use
> {{AmazonS3EncryptionClient}} instead of regular {{AmazonS3Client}}. We need
> to add this option to the S3 IP finder, along with any applicable
> configuration parameters.
> [1]
> http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10448) MVCC: NPE on data page eviction.
[
https://issues.apache.org/jira/browse/IGNITE-10448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729149#comment-16729149
]
Dmitriy Pavlov commented on IGNITE-10448:
-
Please unmute tests related to this issue
IgniteCacheMvccTestSuite7 testPageEviction7026IGNITE-10448
Resolved2018-12-04 12:03:06 Ignite Tests 2.4+ (Java 8/9/10/11)
IgniteCacheTestSuite7 testPageEvictionMvcc7044IGNITE-10448
Resolved2018-12-06 19:57:33 Ignite Tests 2.4+ (Java 8/9/10/11)
IgniteCacheTestSuite8 testEvictionWithRebalanceMvcc 7050IGNITE-10448
Resolved2018-12-06 20:00:06 Ignite Tests 2.4+ (Java 8/9/10/11)
IgniteCacheTestSuite8 testEvictionWithRebalanceMvcc 7050IGNITE-10448
Resolved2018-12-06 20:00:06 Ignite Tests 2.4+ (Java 8/9/10/11)
IgniteCacheTestSuite8 testPageEvictionMetricMvcc 7046IGNITE-10448
Resolved2018-12-06 19:58:23 Ignite Tests 2.4+ (Java 8/9/10/11)
IgniteCacheTestSuite8 testPageEvictionMvcc7046IGNITE-10448
Resolved2018-12-06 19:58:23 Ignite Tests 2.4+ (Java 8/9/10/11)
IgniteCacheTestSuite8 testPageEvictionMvcc7050IGNITE-10448
Resolved2018-12-06 20:00:06 Ignite Tests 2.4+ (Java 8/9/10/11)
IgniteCacheTestSuite8 testPageEvictionMvcc7050IGNITE-10448
Resolved2018-12-06 20:00:06 Ignite Tests 2.4+ (Java 8/9/10/11)
IgniteCacheTestSuite8 testPageEvictionMvcc7050IGNITE-10448
Resolved2018-12-06 20:00:06 Ignite Tests 2.4+ (Java 8/9/10/11)
IgniteCacheTestSuite8 testPageEvictionMvcc7050IGNITE-10448
Resolved2018-12-06 20:00:06 Ignite Tests 2.4+ (Java 8/9/10/11)
IgniteCacheTestSuite8 testPagesRecyclingAndReusingMvccTxPartitioned 7082
IGNITE-10448Resolved2018-12-09 17:45:31 Ignite Tests 2.4+ (Java
8/9/10/11)
IgniteCacheTestSuite8 testPagesRecyclingAndReusingMvccTxReplicated7050
IGNITE-10448Resolved2018-12-06 20:00:06 Ignite Tests 2.4+ (Java
8/9/10/11)
IgniteCacheTestSuite8 testTouchOrderWithFairFifoEvictionMvccTxPartitioned
7082IGNITE-10448Resolved2018-12-09 17:45:31 Ignite Tests
2.4+ (Java 8/9/10/11)
IgniteCacheTestSuite8 testTouchOrderWithFairFifoEvictionMvccTxReplicated
> MVCC: NPE on data page eviction.
>
>
> Key: IGNITE-10448
> URL: https://issues.apache.org/jira/browse/IGNITE-10448
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, pagememory
> Fix For: 2.8
>
>
> NPE occurred during page eviction process.
> Reproducer: {{PageEvictionMultinodeMixedRegionsTest}}.
> StackTrace:
>
> {noformat}
> javax.cache.CacheException: class
> org.apache.ignite.transactions.TransactionRollbackException: Transaction has
> been rolled back: 83e7f9a5761--093b-7d30--0005
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1108)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.cache.eviction.paged.PageEvictionMultinodeAbstractTest.createCacheAndTestEvcition(PageEvictionMultinodeAbstractTest.java:101)
> at
> org.apache.ignite.internal.processors.cache.eviction.paged.PageEvictionMultinodeAbstractTest.testPageEviction(PageEvictionMultinodeAbstractTest.java:81)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.transactions.TransactionRollbackException:
> Transaction has been rolled back:
> 83e7f9a5761--093b-7d30--0005
> at
> org.apache.ignite.in
[jira] [Updated] (IGNITE-10403) Yardstick does not work without Guava 20 in the classpath
[
https://issues.apache.org/jira/browse/IGNITE-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10403:
Ignite Flags: (was: Docs Required)
> Yardstick does not work without Guava 20 in the classpath
> -
>
> Key: IGNITE-10403
> URL: https://issues.apache.org/jira/browse/IGNITE-10403
> Project: Ignite
> Issue Type: Bug
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
>Priority: Major
> Fix For: 2.8
>
>
> {noformat}
> Exception in thread "main" java.lang.NoSuchMethodError:
> com.google.common.collect.Sets$SetView.iterator()Lcom/google/common/collect/UnmodifiableIterator;
> at org.reflections.Reflections.expandSuperTypes(Reflections.java:380) at
> org.reflections.Reflections.(Reflections.java:126) at
> org.reflections.Reflections.(Reflections.java:168) at
> org.yardstickframework.impl.BenchmarkLoader.initialize(BenchmarkLoader.java:99)
> at
> org.yardstickframework.BenchmarkServerStartUp.main(BenchmarkServerStartUp.java:40)
> {noformat}
>
> Explanation from this link:
> [https://github.com/confluentinc/kafka-connect-elasticsearch/issues/143]
> 'This error means that you are bringing an older version of guava earlier in
> your classpath. Connect worker requires guava >= 20 for org.reflections to
> work correctly.'
> Indeed adding guava 20 to Yardstick ./lib folder helps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10403) Yardstick does not work without Guava 20 in the classpath
[
https://issues.apache.org/jira/browse/IGNITE-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10403:
Fix Version/s: 2.8
> Yardstick does not work without Guava 20 in the classpath
> -
>
> Key: IGNITE-10403
> URL: https://issues.apache.org/jira/browse/IGNITE-10403
> Project: Ignite
> Issue Type: Bug
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
>Priority: Major
> Fix For: 2.8
>
>
> {noformat}
> Exception in thread "main" java.lang.NoSuchMethodError:
> com.google.common.collect.Sets$SetView.iterator()Lcom/google/common/collect/UnmodifiableIterator;
> at org.reflections.Reflections.expandSuperTypes(Reflections.java:380) at
> org.reflections.Reflections.(Reflections.java:126) at
> org.reflections.Reflections.(Reflections.java:168) at
> org.yardstickframework.impl.BenchmarkLoader.initialize(BenchmarkLoader.java:99)
> at
> org.yardstickframework.BenchmarkServerStartUp.main(BenchmarkServerStartUp.java:40)
> {noformat}
>
> Explanation from this link:
> [https://github.com/confluentinc/kafka-connect-elasticsearch/issues/143]
> 'This error means that you are bringing an older version of guava earlier in
> your classpath. Connect worker requires guava >= 20 for org.reflections to
> work correctly.'
> Indeed adding guava 20 to Yardstick ./lib folder helps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10813) Run CheckpointReadLockFailureTest with JUnit4 runner
[ https://issues.apache.org/jira/browse/IGNITE-10813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10813: Ignite Flags: (was: Docs Required) > Run CheckpointReadLockFailureTest with JUnit4 runner > > > Key: IGNITE-10813 > URL: https://issues.apache.org/jira/browse/IGNITE-10813 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Kuznetsov >Assignee: Andrey Kuznetsov >Priority: Trivial > Fix For: 2.8 > > > The test fails on TeamCity. Should be run in JUnit4 manner. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10813) Run CheckpointReadLockFailureTest with JUnit4 runner
[ https://issues.apache.org/jira/browse/IGNITE-10813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10813: Fix Version/s: 2.8 > Run CheckpointReadLockFailureTest with JUnit4 runner > > > Key: IGNITE-10813 > URL: https://issues.apache.org/jira/browse/IGNITE-10813 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Kuznetsov >Assignee: Andrey Kuznetsov >Priority: Trivial > Fix For: 2.8 > > > The test fails on TeamCity. Should be run in JUnit4 manner. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10779) PagesWriteThrottleSmokeTest.testThrottle is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729078#comment-16729078
]
Dmitriy Pavlov commented on IGNITE-10779:
-
Merged to master [~zzzadruga] thank you for finding out reason and fixing this
issue.
> PagesWriteThrottleSmokeTest.testThrottle is flaky
> -
>
> Key: IGNITE-10779
> URL: https://issues.apache.org/jira/browse/IGNITE-10779
> Project: Ignite
> Issue Type: Task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Sometimes, at poor checkpoint write speed, put rate degrated to zero for at
> least 10 seconds with write throttling enabled. Success rate on TC = 87%.
> [Test
> details|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=2808794487465215609&tab=testDetails]
> {code:java}
> junit.framework.AssertionFailedError: Put rate degraded to zero for at least
> 10 seconds
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PagesWriteThrottleSmokeTest.testThrottle(PagesWriteThrottleSmokeTest.java:217)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2209)
> 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:748)
> {code}
> Test became flaky after IGNITE-10028.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-1436) C++: Port to MAC OS.
[ https://issues.apache.org/jira/browse/IGNITE-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728755#comment-16728755 ] Dmitriy Pavlov commented on IGNITE-1436: [~isapego] how do you find this patch? Can we merge? Unfortunately, I'm not an expert in C/C++, so I guess only you can approve PR. > C++: Port to MAC OS. > > > Key: IGNITE-1436 > URL: https://issues.apache.org/jira/browse/IGNITE-1436 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Stephen Darlington >Priority: Major > Labels: cpp > Fix For: 2.8 > > > It will require minimal porting of "common" and "utils" stuff. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9149) Get rid of logging remaining supplier nodes rebalance time
[
https://issues.apache.org/jira/browse/IGNITE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9149:
---
Comment: was deleted
(was: GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/4483
IGNITE-9149 Add proper handling of UUID column in DDL statements.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9149
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4483.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 #4483
commit 06ab44c311a0084f75c44aacb1fc11142f67a922
Author: Ivan Daschinskiy
Date: 2018-08-03T13:30:51Z
IGNITE-9149 Add proper handling of UUID column in DDL statements.
)
> Get rid of logging remaining supplier nodes rebalance time
> --
>
> Key: IGNITE-9149
> URL: https://issues.apache.org/jira/browse/IGNITE-9149
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: rebalance
> Fix For: 2.8
>
>
> Logging rebalance execution time in section of each supplier node have no
> sence and provides no helpfull info for analyzing logs. It also
> overcomplicates {{GridDhtPartitionDemander}}.
> I'm suggesting remove it by simplifying {{Map IgniteDhtDemandedPartitionsMap>>}} to {{Map IgniteDhtDemandedPartitionsMap>}}.
> {code:java}
> /** Remaining. T2: startTime, partitions */
> private final Map> remaining =
> new HashMap<>();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9149) Get rid of logging remaining supplier nodes rebalance time
[
https://issues.apache.org/jira/browse/IGNITE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9149:
---
Fix Version/s: 2.8
> Get rid of logging remaining supplier nodes rebalance time
> --
>
> Key: IGNITE-9149
> URL: https://issues.apache.org/jira/browse/IGNITE-9149
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: rebalance
> Fix For: 2.8
>
>
> Logging rebalance execution time in section of each supplier node have no
> sence and provides no helpfull info for analyzing logs. It also
> overcomplicates {{GridDhtPartitionDemander}}.
> I'm suggesting remove it by simplifying {{Map IgniteDhtDemandedPartitionsMap>>}} to {{Map IgniteDhtDemandedPartitionsMap>}}.
> {code:java}
> /** Remaining. T2: startTime, partitions */
> private final Map> remaining =
> new HashMap<>();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9149) Get rid of logging remaining supplier nodes rebalance time
[
https://issues.apache.org/jira/browse/IGNITE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9149:
---
Ignite Flags: (was: Docs Required)
> Get rid of logging remaining supplier nodes rebalance time
> --
>
> Key: IGNITE-9149
> URL: https://issues.apache.org/jira/browse/IGNITE-9149
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: rebalance
> Fix For: 2.8
>
>
> Logging rebalance execution time in section of each supplier node have no
> sence and provides no helpfull info for analyzing logs. It also
> overcomplicates {{GridDhtPartitionDemander}}.
> I'm suggesting remove it by simplifying {{Map IgniteDhtDemandedPartitionsMap>>}} to {{Map IgniteDhtDemandedPartitionsMap>}}.
> {code:java}
> /** Remaining. T2: startTime, partitions */
> private final Map> remaining =
> new HashMap<>();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10594) Remove 'java 8' source in indexing module, add test to regular suite
[ https://issues.apache.org/jira/browse/IGNITE-10594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10594: Fix Version/s: 2.8 > Remove 'java 8' source in indexing module, add test to regular suite > > > Key: IGNITE-10594 > URL: https://issues.apache.org/jira/browse/IGNITE-10594 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: test > Fix For: 2.8 > > > CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest to be precise -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-1757) [Failed test] CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails on TC sometimes
[
https://issues.apache.org/jira/browse/IGNITE-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728285#comment-16728285
]
Dmitriy Pavlov commented on IGNITE-1757:
I've unmuted 2 tests related to this ticket
> [Failed test] CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails
> on TC sometimes
>
>
> Key: IGNITE-1757
> URL: https://issues.apache.org/jira/browse/IGNITE-1757
> Project: Ignite
> Issue Type: Test
>Reporter: Artem Shutak
>Priority: Critical
> Labels: Muted_test
> Fix For: 2.8
>
>
> CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails on TC
> sometimes.
> {noformat}
> java.lang.NullPointerException: null
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.DeferredFileOutputStream.thresholdReached(DeferredFileOutputStream.java:179)
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.checkThreshold(ThresholdingOutputStream.java:224)
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.write(ThresholdingOutputStream.java:128)
> at
> org.apache.maven.plugin.surefire.report.Utf8RecodingDeferredFileOutputStream.write(Utf8RecodingDeferredFileOutputStream.java:59)
> at
> org.apache.maven.plugin.surefire.report.TestSetRunListener.writeTestOutput(TestSetRunListener.java:98)
> at
> org.apache.maven.surefire.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:91)
> at
> org.hibernate.engine.jdbc.spi.SqlStatementLogger.logStatement(SqlStatementLogger.java:106)
> at
> org.hibernate.engine.jdbc.spi.SqlStatementLogger.logStatement(SqlStatementLogger.java:95)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl$StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:180)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl.prepareStatement(StatementPreparerImpl.java:85)
> at
> org.hibernate.persister.entity.AbstractEntityPersister.getDatabaseSnapshot(AbstractEntityPersister.java:1513)
> at
> org.hibernate.engine.internal.StatefulPersistenceContext.getDatabaseSnapshot(StatefulPersistenceContext.java:316)
> at
> org.hibernate.engine.internal.ForeignKeys.isTransient(ForeignKeys.java:217)
> at
> org.hibernate.event.internal.AbstractSaveEventListener.getEntityState(AbstractSaveEventListener.java:497)
> at
> org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:100)
> at
> org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:90)
> at
> org.hibernate.internal.SessionImpl.fireSaveOrUpdate(SessionImpl.java:735)
> at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:727)
> at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:723)
> at
> org.apache.ignite.cache.store.hibernate.CacheHibernateBlobStore.write(CacheHibernateBlobStore.java:190)
> at
> org.apache.ignite.testframework.junits.cache.GridAbstractCacheStoreSelfTest$1.call(GridAbstractCacheStoreSelfTest.java:396)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> --- Stderr: ---
> [21:04:18,410][WARN
> ][hibernate.CacheHibernateBlobStoreSelfTest-1][CacheHibernateBlobStore] No
> Hibernate configuration has been provided for store (will use default).
> [21:04:18,495][WARN
> ][hibernate.CacheHibernateBlobStoreSelfTest-1][DriverManagerConnectionProviderImpl]
> HHH000148: No JDBC Driver class was specified by property
> hibernate.connection.driver_class
> Failure in thread: Thread [id=711,
> name=hibernate.CacheHibernateBlobStoreSelfTest-5]
> java.lang.NullPointerException
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.DeferredFileOutputStream.thresholdReached(DeferredFileOutputStream.java:179)
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.checkThreshold(ThresholdingOutputStream.java:224)
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.write(ThresholdingOutputStream.java:128)
> at
> org.apache.maven.plugin.surefire.report.Utf8RecodingDeferredFileOutputStream.write(Utf8RecodingDeferredFileOutputStream.java:59)
> at
> org.apache.maven.plugin.surefire.report.TestSetRunListener.writeTestOutput(TestSetRunListener.java:98)
> at
> org.apache.maven.surefire.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:91)
> at
> org.hibernate.engine.jdbc.spi.SqlStatementLogger.logStatement(SqlStatementLogger.java:106)
> at
> org.h
[jira] [Commented] (IGNITE-10264) MVCC: Enlist request failure on backup can cause grid hanging.
[
https://issues.apache.org/jira/browse/IGNITE-10264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728284#comment-16728284
]
Dmitriy Pavlov commented on IGNITE-10264:
-
[~rkondakov] [~gvvinblade]
- please set fix version for the ticket if it was not set by a contributor.
Now current version is 2.8.
- please pay attention to this ticket has muted test on TC, I will unmute it
for now but better that contributor/committer unmute.
> MVCC: Enlist request failure on backup can cause grid hanging.
> --
>
> Key: IGNITE-10264
> URL: https://issues.apache.org/jira/browse/IGNITE-10264
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Roman Kondakov
>Priority: Critical
> Labels: Hanging
> Fix For: 2.8
>
>
> See stacktrace below, runtime ClusterTopologyException has not been catched
> and causes transaction hanging.
> Seems, we should throws some meaningful checked exception and thow it onto
> primary node.
> Reproducer is IgniteCacheIncrementTxTest running in Mvcc mode.
>
> {noformat}
> [2018-11-14
> 22:26:37,099][ERROR][sys-stripe-3-#10280%cache.IgniteCacheIncrementTxTest7%][GridCacheIoManager]
> Failed to process message [senderId=3774798b-3cbc-4ae1-95d1-745dd371,
> messageType=class
> o.a.i.i.processors.cache.distributed.dht.GridDhtTxQueryFirstEnlistRequest]
> class org.apache.ignite.cluster.ClusterTopologyException: Can not reserve
> partition. Please retry on stable topology.
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.mvccEnlistBatch(IgniteTxHandler.java:1865)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistRequest(GridDhtTransactionalCacheAdapter.java:2301)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1100(GridDhtTransactionalCacheAdapter.java:112)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$17.apply(GridDhtTransactionalCacheAdapter.java:250)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$17.apply(GridDhtTransactionalCacheAdapter.java:248)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:100)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1$2$1.run(GridCacheIoManager.java:274)
> 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){noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10264) MVCC: Enlist request failure on backup can cause grid hanging.
[
https://issues.apache.org/jira/browse/IGNITE-10264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10264:
Fix Version/s: 2.8
> MVCC: Enlist request failure on backup can cause grid hanging.
> --
>
> Key: IGNITE-10264
> URL: https://issues.apache.org/jira/browse/IGNITE-10264
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Roman Kondakov
>Priority: Critical
> Labels: Hanging
> Fix For: 2.8
>
>
> See stacktrace below, runtime ClusterTopologyException has not been catched
> and causes transaction hanging.
> Seems, we should throws some meaningful checked exception and thow it onto
> primary node.
> Reproducer is IgniteCacheIncrementTxTest running in Mvcc mode.
>
> {noformat}
> [2018-11-14
> 22:26:37,099][ERROR][sys-stripe-3-#10280%cache.IgniteCacheIncrementTxTest7%][GridCacheIoManager]
> Failed to process message [senderId=3774798b-3cbc-4ae1-95d1-745dd371,
> messageType=class
> o.a.i.i.processors.cache.distributed.dht.GridDhtTxQueryFirstEnlistRequest]
> class org.apache.ignite.cluster.ClusterTopologyException: Can not reserve
> partition. Please retry on stable topology.
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.mvccEnlistBatch(IgniteTxHandler.java:1865)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistRequest(GridDhtTransactionalCacheAdapter.java:2301)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1100(GridDhtTransactionalCacheAdapter.java:112)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$17.apply(GridDhtTransactionalCacheAdapter.java:250)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$17.apply(GridDhtTransactionalCacheAdapter.java:248)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:100)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1$2$1.run(GridCacheIoManager.java:274)
> 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){noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9774) CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan hangs
[
https://issues.apache.org/jira/browse/IGNITE-9774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728281#comment-16728281
]
Dmitriy Pavlov commented on IGNITE-9774:
Also, please remove docs required flag if this ticket does not need to be
documented.
> CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan
> hangs
> ---
>
> Key: IGNITE-9774
> URL: https://issues.apache.org/jira/browse/IGNITE-9774
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Assignee: Roman Kondakov
>Priority: Major
> Labels: Hanging
> Fix For: 2.8
>
>
> Test
> {{CacheMvccTransactionsTest#testPutAllGetAll_ClientServer_Backups1_Restart_Scan
> hangs}} and can freeze a whole suite. Investigation is needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9774) CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan hangs
[
https://issues.apache.org/jira/browse/IGNITE-9774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9774:
---
Ignite Flags: (was: Docs Required)
> CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan
> hangs
> ---
>
> Key: IGNITE-9774
> URL: https://issues.apache.org/jira/browse/IGNITE-9774
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Assignee: Roman Kondakov
>Priority: Major
> Labels: Hanging
> Fix For: 2.8
>
>
> Test
> {{CacheMvccTransactionsTest#testPutAllGetAll_ClientServer_Backups1_Restart_Scan
> hangs}} and can freeze a whole suite. Investigation is needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9774) CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan hangs
[
https://issues.apache.org/jira/browse/IGNITE-9774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728268#comment-16728268
]
Dmitriy Pavlov commented on IGNITE-9774:
[~gvvinblade] please set fix version for the ticket if it was not set by a
contributor. Now current version is 2.8.
[~gvvinblade] [~rkondakov], please pay attention to this ticket has muted test
on TC, I will unmute it for now but better that contributor/committer unmute.
> CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan
> hangs
> ---
>
> Key: IGNITE-9774
> URL: https://issues.apache.org/jira/browse/IGNITE-9774
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Assignee: Roman Kondakov
>Priority: Major
> Labels: Hanging
> Fix For: 2.8
>
>
> Test
> {{CacheMvccTransactionsTest#testPutAllGetAll_ClientServer_Backups1_Restart_Scan
> hangs}} and can freeze a whole suite. Investigation is needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9774) CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan hangs
[
https://issues.apache.org/jira/browse/IGNITE-9774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9774:
---
Fix Version/s: 2.8
> CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan
> hangs
> ---
>
> Key: IGNITE-9774
> URL: https://issues.apache.org/jira/browse/IGNITE-9774
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Assignee: Roman Kondakov
>Priority: Major
> Labels: Hanging
> Fix For: 2.8
>
>
> Test
> {{CacheMvccTransactionsTest#testPutAllGetAll_ClientServer_Backups1_Restart_Scan
> hangs}} and can freeze a whole suite. Investigation is needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10779) PagesWriteThrottleSmokeTest.testThrottle is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728258#comment-16728258
]
Dmitriy Pavlov commented on IGNITE-10779:
-
[~zzzadruga] could you also please explain how counter increment can affect
test pass?
> PagesWriteThrottleSmokeTest.testThrottle is flaky
> -
>
> Key: IGNITE-10779
> URL: https://issues.apache.org/jira/browse/IGNITE-10779
> Project: Ignite
> Issue Type: Task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Sometimes, at poor checkpoint write speed, put rate degrated to zero for at
> least 10 seconds with write throttling enabled. Success rate on TC = 87%.
> [Test
> details|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=2808794487465215609&tab=testDetails]
> {code:java}
> junit.framework.AssertionFailedError: Put rate degraded to zero for at least
> 10 seconds
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PagesWriteThrottleSmokeTest.testThrottle(PagesWriteThrottleSmokeTest.java:217)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2209)
> 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:748)
> {code}
> Test became flaky after IGNITE-10028.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10779) PagesWriteThrottleSmokeTest.testThrottle is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728255#comment-16728255
]
Dmitriy Pavlov commented on IGNITE-10779:
-
[~zzzadruga] please close unrelevant PR 5722
> PagesWriteThrottleSmokeTest.testThrottle is flaky
> -
>
> Key: IGNITE-10779
> URL: https://issues.apache.org/jira/browse/IGNITE-10779
> Project: Ignite
> Issue Type: Task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Sometimes, at poor checkpoint write speed, put rate degrated to zero for at
> least 10 seconds with write throttling enabled. Success rate on TC = 87%.
> [Test
> details|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=2808794487465215609&tab=testDetails]
> {code:java}
> junit.framework.AssertionFailedError: Put rate degraded to zero for at least
> 10 seconds
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PagesWriteThrottleSmokeTest.testThrottle(PagesWriteThrottleSmokeTest.java:217)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2209)
> 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:748)
> {code}
> Test became flaky after IGNITE-10028.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
https://issues.apache.org/jira/browse/IGNITE-10177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10177:
Fix Version/s: 2.8
> cleanup Junit 3 from the project
>
>
> Key: IGNITE-10177
> URL: https://issues.apache.org/jira/browse/IGNITE-10177
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.8
>
>
> If needed, refer parent task for more details.
> # remove Junit3-specific parts of API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven (if there are any)
> # migrate tests that were missed at prior steps for various reasons:
> ## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> ## find out why
> {{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
> start running slow / timing out after adding Junit 4 annotations (reproduced
> this on teamcity and locally as was discovered in IGNITE-10175)
> ## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
> starts failing after move to JUnit 4
> ## IgniteCachePartitionedQuerySelfTest,
> IgniteCacheReplicatedQueryP2PDisabledSelfTest, ComputeUtilsTest,
> CacheBasedDatasetBuilderTest, CacheBasedDatasetTest,
> GridPartitionedCacheJtaLookupClassNameSelfTest,
> GridReplicatedCacheJtaLookupClassNameSelfTest (there were problems migrating
> these at IGNITE-10176)
> ## find out why tests in logging suite failed on teamcity (not locally) when
> setup method was annotated {{@Before}}
> ## (!) note part of this work related to
> {{IgniteConfigVariationsAbstractTest}} is expected to be done separately per
> IGNITE-10739
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # find and update all Junit3-specific code that {{extends TestCase}}
> # execute junit related inspections of IDE and analyse results
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> (i) per discussion with [~EdShangGG] plan to to do this in a separate
> ticket for smoother merges - IGNITE-10758
> Side note if for some reason it turns out critically important to keep test
> suites names (by default Junit 4 will use suite class names instead),
> approach with custom description annotation [described
> here|https://stackoverflow.com/questions/34745080/is-it-possible-to-name-a-test-suite-in-junit-4/34745518]
> can be used to address that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10215) [Tc Bot] Mark Inspections:Core failures as critical
[ https://issues.apache.org/jira/browse/IGNITE-10215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10215: Description: Currently inspections failures are not considered as a blocker by TC bot. These failures does not produce any notification. (was: Currently inspections failures ) > [Tc Bot] Mark Inspections:Core failures as critical > --- > > Key: IGNITE-10215 > URL: https://issues.apache.org/jira/browse/IGNITE-10215 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Currently inspections failures are not considered as a blocker by TC bot. > These failures does not produce any notification. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10215) [Tc Bot] Mark Inspections:Core failures as critical
[ https://issues.apache.org/jira/browse/IGNITE-10215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10215: Description: Currently, inspections failures are not considered as a blocker by TC bot. These failures do not produce any notification. It is necessary to support notifications and blocker detection for case a build failure on a metric. (was: Currently inspections failures are not considered as a blocker by TC bot. These failures does not produce any notification.) > [Tc Bot] Mark Inspections:Core failures as critical > --- > > Key: IGNITE-10215 > URL: https://issues.apache.org/jira/browse/IGNITE-10215 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Currently, inspections failures are not considered as a blocker by TC bot. > These failures do not produce any notification. It is necessary to support > notifications and blocker detection for case a build failure on a metric. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10215) [Tc Bot] Mark Inspections:Core failures as critical
[ https://issues.apache.org/jira/browse/IGNITE-10215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10215: Description: Currently inspections failures > [Tc Bot] Mark Inspections:Core failures as critical > --- > > Key: IGNITE-10215 > URL: https://issues.apache.org/jira/browse/IGNITE-10215 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Currently inspections failures -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10594) Remove 'java 8' source in indexing module, add test to regular suite
[ https://issues.apache.org/jira/browse/IGNITE-10594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726860#comment-16726860 ] Dmitriy Pavlov commented on IGNITE-10594: - [~ilyak], LGTM could you please apply the pull request? I've got local problems with this PR & apply-pr script. > Remove 'java 8' source in indexing module, add test to regular suite > > > Key: IGNITE-10594 > URL: https://issues.apache.org/jira/browse/IGNITE-10594 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: test > > CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest to be precise -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10599) Add test for Scheduler Example to LGPL Examples suite
[ https://issues.apache.org/jira/browse/IGNITE-10599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10599: Fix Version/s: 2.8 > Add test for Scheduler Example to LGPL Examples suite > - > > Key: IGNITE-10599 > URL: https://issues.apache.org/jira/browse/IGNITE-10599 > Project: Ignite > Issue Type: Test >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: test > Fix For: 2.8 > > > Currently we in LGPL Examples suite we have Hibernate example test and > Geospatial example test but no Scheduler test. We need to add it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10353) Spring Add Update/Delete support for Spring Data
[ https://issues.apache.org/jira/browse/IGNITE-10353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726769#comment-16726769 ] Dmitriy Pavlov commented on IGNITE-10353: - Please keep it assigned to you. Committers filter tickets in Patch Available state to review. Also, you can drop an email to dev.list directly asking for a review. Some time ago I was involved in Spring Data changes, so if nobody picks up this ticket, eventually I'm going to review. > Spring Add Update/Delete support for Spring Data > > > Key: IGNITE-10353 > URL: https://issues.apache.org/jira/browse/IGNITE-10353 > Project: Ignite > Issue Type: New Feature > Components: spring >Affects Versions: 2.7 >Reporter: Jonathan Camargo >Assignee: Jonathan Camargo >Priority: Minor > Labels: spring > > In Spring Data 2.0 module, add the update/delete functionalities to work with > the cache, this should be possible even using the method name in the > IgniteRepository interface or by a @Query notation writing the SQL query > following the ignite docs for it. > The specification for the remaining methods for the Repository interface are > mentioned on the Spring documentation. > https://docs.spring.io/spring-data/jpa/docs/current/reference/html/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10353) Spring Add Update/Delete support for Spring Data
[ https://issues.apache.org/jira/browse/IGNITE-10353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726747#comment-16726747 ] Dmitriy Pavlov commented on IGNITE-10353: - [~JCamargoS] please do not move Patch Available ticket to unassigned. It may be more difficult for committers to find a ticket with a patch if is not assigned. > Spring Add Update/Delete support for Spring Data > > > Key: IGNITE-10353 > URL: https://issues.apache.org/jira/browse/IGNITE-10353 > Project: Ignite > Issue Type: New Feature > Components: spring >Affects Versions: 2.7 >Reporter: Jonathan Camargo >Priority: Minor > Labels: spring > > In Spring Data 2.0 module, add the update/delete functionalities to work with > the cache, this should be possible even using the method name in the > IgniteRepository interface or by a @Query notation writing the SQL query > following the ignite docs for it. > The specification for the remaining methods for the Repository interface are > mentioned on the Spring documentation. > https://docs.spring.io/spring-data/jpa/docs/current/reference/html/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10787) [TC Bot] Setup TC bot profiling on the server using SJK/stcap and prepare rules for Ignite thread groups
[ https://issues.apache.org/jira/browse/IGNITE-10787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10787: Ignite Flags: (was: Docs Required) > [TC Bot] Setup TC bot profiling on the server using SJK/stcap and prepare > rules for Ignite thread groups > > > Key: IGNITE-10787 > URL: https://issues.apache.org/jira/browse/IGNITE-10787 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Trivial > > https://github.com/aragozin/jvm-tools > Integrate tool into start scrips, prepare settings for capturing > Prepare traces analysis and include into server monitoring page > https://mtcga.gridgain.com/monitoring.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10787) [TC Bot] Setup TC bot profiling on the server using SJK/stcap and prepare rules for Ignite thread groups
Dmitriy Pavlov created IGNITE-10787: --- Summary: [TC Bot] Setup TC bot profiling on the server using SJK/stcap and prepare rules for Ignite thread groups Key: IGNITE-10787 URL: https://issues.apache.org/jira/browse/IGNITE-10787 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov https://github.com/aragozin/jvm-tools Integrate tool into start scrips, prepare settings for capturing Prepare traces analysis and include into server monitoring page https://mtcga.gridgain.com/monitoring.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6341) Use direct IO or libaio for file page store where applicable
[ https://issues.apache.org/jira/browse/IGNITE-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726609#comment-16726609 ] Dmitriy Pavlov commented on IGNITE-6341: https://github.com/apache/ignite/commit/9bba2d5203b0e67b206f153cac4a60a213ce9a15 > Use direct IO or libaio for file page store where applicable > > > Key: IGNITE-6341 > URL: https://issues.apache.org/jira/browse/IGNITE-6341 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Andrey Gura >Assignee: Dmitriy Pavlov >Priority: Major > Fix For: 2.4 > > > Need try to use direct IO or libaio for page store because once data buffer > is serialized, we can write it as disk pages (this will also make it easier > if we decide to open file as a block device). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
