[jira] [Commented] (IGNITE-10577) ignite-kubernetes is missing jackson-annotations dependency
[
https://issues.apache.org/jira/browse/IGNITE-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713503#comment-16713503
]
Ignite TC Bot commented on IGNITE-10577:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hibernate 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2489439]]
{color:#d04437}Hibernate 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2489440]]
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2489463]]
* ZookeeperDiscoverySpiTestSuite2:
GridCachePartitionedNodeRestartTest.testRestartWithPutEightNodesTwoBackups -
0,0% fails in last 100 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2489523buildTypeId=IgniteTests24Java8_RunAll]
> ignite-kubernetes is missing jackson-annotations dependency
> ---
>
> Key: IGNITE-10577
> URL: https://issues.apache.org/jira/browse/IGNITE-10577
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 2.7
>Reporter: Stephen Darlington
>Assignee: Stephen Darlington
>Priority: Major
>
> When starting 2.7 with the ignite-kubernetes option I get the following
> exception on startup:
>
> {code}
> [13:44:34,605][SEVERE][main][IgniteKernal] Got exception while starting (will
> rollback startup routine).
> java.lang.NoClassDefFoundError: com/fasterxml/jackson/annotation/JsonView
> at
> com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector.(JacksonAnnotationIntrospector.java:37)
> at
> com.fasterxml.jackson.databind.ObjectMapper.(ObjectMapper.java:291)
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder.getRegisteredAddresses(TcpDiscoveryKubernetesIpFinder.java:151)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredAddresses(TcpDiscoverySpi.java:1900)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.resolvedAddresses(TcpDiscoverySpi.java:1848)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:1049)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:910)
> {code}
>
> It's clearly missing a dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10175) migrate core module tests from Junit 3 to 4
[
https://issues.apache.org/jira/browse/IGNITE-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713460#comment-16713460
]
Ignite TC Bot commented on IGNITE-10175:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hibernate 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2491162]]
* HibernateL2CacheTransactionalUseSyncSelfTest.testRegionClear (last started)
{color:#d04437}PDS 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2491164]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2488187buildTypeId=IgniteTests24Java8_RunAll]
> migrate core module tests from Junit 3 to 4
> ---
>
> Key: IGNITE-10175
> URL: https://issues.apache.org/jira/browse/IGNITE-10175
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> If needed, refer parent task for more details.
> Migrate using new API introduced at prior step.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10176) migrate non-core modules tests from Junit 3 to 4
[
https://issues.apache.org/jira/browse/IGNITE-10176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713459#comment-16713459
]
Ignite TC Bot commented on IGNITE-10176:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hibernate 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2490739]]
* HibernateL2CacheTransactionalUseSyncSelfTest.testRegionClear (last started)
{color:#d04437}Hibernate 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2490740]]
* HibernateL2CacheTransactionalUseSyncSelfTest.testRegionClear (last started)
{color:#d04437}Queries 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2490816]]
* IgniteBinaryCacheQueryTestSuite:
H2DynamicIndexingComplexClientTransactionalReplicatedTest.testOperations - 1,0%
fails in last 100 master runs.
{color:#d04437}Cache 5{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2490792]]
* IgniteCacheWithIndexingTestSuite:
CacheTtlTransactionalPartitionedSelfTest.testDefaultTimeToLiveLoadAll - 1,0%
fails in last 100 master runs.
* IgniteCacheTestSuite5:
IgniteCacheGroupsPartitionLossPolicySelfTest.testReadOnlyAll - 1,0% fails in
last 100 master runs.
{color:#d04437}Streamers{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2490753]]
* IgniteKafkaStreamerSelfTestSuite:
IgniteSinkConnectorTest.testSinkPutsWithoutTransformation - 1,0% fails in last
100 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2490823buildTypeId=IgniteTests24Java8_RunAll]
> migrate non-core modules tests from Junit 3 to 4
>
>
> Key: IGNITE-10176
> URL: https://issues.apache.org/jira/browse/IGNITE-10176
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
>
> If needed, refer parent task for more details.
> Migrate using new API introduced and tested at prior step.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8871) TDE - Phase-1. Documentation
[ https://issues.apache.org/jira/browse/IGNITE-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713428#comment-16713428 ] Denis Magda commented on IGNITE-8871: - Folks, looks good, did minor clarifications and moved the page to the Security sections which looks like a better place. > TDE - Phase-1. Documentation > > > Key: IGNITE-8871 > URL: https://issues.apache.org/jira/browse/IGNITE-8871 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 2.5 >Reporter: Nikolay Izhikov >Assignee: Denis Magda >Priority: Major > Labels: documentation > Fix For: 2.7 > > > TDE feature should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8871) TDE - Phase-1. Documentation
[ https://issues.apache.org/jira/browse/IGNITE-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-8871. --- > TDE - Phase-1. Documentation > > > Key: IGNITE-8871 > URL: https://issues.apache.org/jira/browse/IGNITE-8871 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 2.5 >Reporter: Nikolay Izhikov >Assignee: Denis Magda >Priority: Major > Labels: documentation > Fix For: 2.7 > > > TDE feature should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[
https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713267#comment-16713267
]
ASF GitHub Bot commented on IGNITE-10454:
-
dspavlov commented on a change in pull request #89: IGNITE-10454 Create page
with muted tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239939993
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/mute/MuteDao.java
##
@@ -0,0 +1,126 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.mute;
+
+import com.google.common.base.Preconditions;
+import java.util.Set;
+import javax.inject.Inject;
+import javax.inject.Provider;
+import org.apache.ignite.Ignite;
+import org.apache.ignite.IgniteCache;
+import org.apache.ignite.ci.db.TcHelperDb;
+import org.apache.ignite.ci.di.AutoProfiling;
+import org.apache.ignite.ci.teamcity.ignited.IStringCompactor;
+import org.apache.ignite.internal.util.typedef.F;
+
+/**
+ *
+ */
+public class MuteDao {
+/** Cache name. */
+public static final String TEAMCITY_MUTE_CACHE_NAME = "teamcityMute";
+
+/** Ignite provider. */
+@Inject private Provider igniteProvider;
+
+/** Builds cache. */
+private IgniteCache muteCache;
+
+/** Compactor. */
+@Inject private IStringCompactor compactor;
+
+/**
+ *
+ */
+public void init() {
+muteCache =
igniteProvider.get().getOrCreateCache(TcHelperDb.getCacheV2Config(TEAMCITY_MUTE_CACHE_NAME));
+}
+
+/**
+ * @param srvIdMaskHigh Server id mask high.
+ * @param projectId Build id.
+ */
+@AutoProfiling
+public Mutes getMutes(int srvIdMaskHigh, String projectId) {
+Preconditions.checkNotNull(muteCache, "init() was not called");
+
+MutesCompacted compacted =
muteCache.get(projectIdToCacheKey(srvIdMaskHigh, projectId));
+
+return compacted != null ? compacted.toMutes(compactor) : new Mutes();
+}
+
+/**
+ * Combine server and project into key for storage.
+ *
+ * @param srvIdMaskHigh Server id mask high.
+ * @param projectId Build type id.
+ * @return Key from server-project pair.
+ */
+public static long projectIdToCacheKey(long srvIdMaskHigh, String
projectId) {
+return (long)projectId.hashCode() | srvIdMaskHigh << 32;
+}
+
+/**
+ * Save small part of loaded mutes.
+ *
+ * @param srvId Server id.
+ * @param projectId Project id.
+ * @param chunk Chunk.
+ */
+public void saveChunk(int srvId, String projectId, Set chunk) {
Review comment:
To make this method thread-safe we should lock on updated entry before
read-update-modify. But please consider cache transformation instead.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Create page with muted tests
> -
>
> Key: IGNITE-10454
> URL: https://issues.apache.org/jira/browse/IGNITE-10454
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> We need a page with muted tests. On this page we should have possibility to
> filter tests by fail reason (fail with ticket link or not) and fail rate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[
https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713266#comment-16713266
]
ASF GitHub Bot commented on IGNITE-10454:
-
dspavlov commented on a change in pull request #89: IGNITE-10454 Create page
with muted tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239939993
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/mute/MuteDao.java
##
@@ -0,0 +1,126 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.mute;
+
+import com.google.common.base.Preconditions;
+import java.util.Set;
+import javax.inject.Inject;
+import javax.inject.Provider;
+import org.apache.ignite.Ignite;
+import org.apache.ignite.IgniteCache;
+import org.apache.ignite.ci.db.TcHelperDb;
+import org.apache.ignite.ci.di.AutoProfiling;
+import org.apache.ignite.ci.teamcity.ignited.IStringCompactor;
+import org.apache.ignite.internal.util.typedef.F;
+
+/**
+ *
+ */
+public class MuteDao {
+/** Cache name. */
+public static final String TEAMCITY_MUTE_CACHE_NAME = "teamcityMute";
+
+/** Ignite provider. */
+@Inject private Provider igniteProvider;
+
+/** Builds cache. */
+private IgniteCache muteCache;
+
+/** Compactor. */
+@Inject private IStringCompactor compactor;
+
+/**
+ *
+ */
+public void init() {
+muteCache =
igniteProvider.get().getOrCreateCache(TcHelperDb.getCacheV2Config(TEAMCITY_MUTE_CACHE_NAME));
+}
+
+/**
+ * @param srvIdMaskHigh Server id mask high.
+ * @param projectId Build id.
+ */
+@AutoProfiling
+public Mutes getMutes(int srvIdMaskHigh, String projectId) {
+Preconditions.checkNotNull(muteCache, "init() was not called");
+
+MutesCompacted compacted =
muteCache.get(projectIdToCacheKey(srvIdMaskHigh, projectId));
+
+return compacted != null ? compacted.toMutes(compactor) : new Mutes();
+}
+
+/**
+ * Combine server and project into key for storage.
+ *
+ * @param srvIdMaskHigh Server id mask high.
+ * @param projectId Build type id.
+ * @return Key from server-project pair.
+ */
+public static long projectIdToCacheKey(long srvIdMaskHigh, String
projectId) {
+return (long)projectId.hashCode() | srvIdMaskHigh << 32;
+}
+
+/**
+ * Save small part of loaded mutes.
+ *
+ * @param srvId Server id.
+ * @param projectId Project id.
+ * @param chunk Chunk.
+ */
+public void saveChunk(int srvId, String projectId, Set chunk) {
Review comment:
To make this method concurrent we should lock on updated entry. But please
consider cache transformation instead.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Create page with muted tests
> -
>
> Key: IGNITE-10454
> URL: https://issues.apache.org/jira/browse/IGNITE-10454
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> We need a page with muted tests. On this page we should have possibility to
> filter tests by fail reason (fail with ticket link or not) and fail rate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[
https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713263#comment-16713263
]
ASF GitHub Bot commented on IGNITE-10454:
-
dspavlov commented on a change in pull request #89: IGNITE-10454 Create page
with muted tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239939250
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/mute/MuteDao.java
##
@@ -0,0 +1,126 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.mute;
+
+import com.google.common.base.Preconditions;
+import java.util.Set;
+import javax.inject.Inject;
+import javax.inject.Provider;
+import org.apache.ignite.Ignite;
+import org.apache.ignite.IgniteCache;
+import org.apache.ignite.ci.db.TcHelperDb;
+import org.apache.ignite.ci.di.AutoProfiling;
+import org.apache.ignite.ci.teamcity.ignited.IStringCompactor;
+import org.apache.ignite.internal.util.typedef.F;
+
+/**
+ *
+ */
+public class MuteDao {
+/** Cache name. */
+public static final String TEAMCITY_MUTE_CACHE_NAME = "teamcityMute";
+
+/** Ignite provider. */
+@Inject private Provider igniteProvider;
+
+/** Builds cache. */
+private IgniteCache muteCache;
+
+/** Compactor. */
+@Inject private IStringCompactor compactor;
+
+/**
+ *
+ */
+public void init() {
+muteCache =
igniteProvider.get().getOrCreateCache(TcHelperDb.getCacheV2Config(TEAMCITY_MUTE_CACHE_NAME));
+}
+
+/**
+ * @param srvIdMaskHigh Server id mask high.
+ * @param projectId Build id.
+ */
+@AutoProfiling
+public Mutes getMutes(int srvIdMaskHigh, String projectId) {
+Preconditions.checkNotNull(muteCache, "init() was not called");
+
+MutesCompacted compacted =
muteCache.get(projectIdToCacheKey(srvIdMaskHigh, projectId));
+
+return compacted != null ? compacted.toMutes(compactor) : new Mutes();
+}
+
+/**
+ * Combine server and project into key for storage.
+ *
+ * @param srvIdMaskHigh Server id mask high.
+ * @param projectId Build type id.
+ * @return Key from server-project pair.
+ */
+public static long projectIdToCacheKey(long srvIdMaskHigh, String
projectId) {
+return (long)projectId.hashCode() | srvIdMaskHigh << 32;
+}
+
+/**
+ * Save small part of loaded mutes.
+ *
+ * @param srvId Server id.
+ * @param projectId Project id.
+ * @param chunk Chunk.
+ */
+public void saveChunk(int srvId, String projectId, Set chunk) {
+if (F.isEmpty(chunk))
+return;
+
+long key = projectIdToCacheKey(srvId, projectId);
+MutesCompacted compacted = muteCache.get(key);
Review comment:
What if we transform muteCache entries to be separated for each mute
occurrence? It will save disk IO and saveChunk will become concurrent. We can
use putAll for saving, and ScanQuery for extracting mutes related to a
particular project. Actually, I expect there will be just 1 project.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Create page with muted tests
> -
>
> Key: IGNITE-10454
> URL: https://issues.apache.org/jira/browse/IGNITE-10454
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> We need a page with muted tests. On this page we should have possibility to
> filter tests by fail reason (fail with ticket link or not) and fail rate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10176) migrate non-core modules tests from Junit 3 to 4
[ https://issues.apache.org/jira/browse/IGNITE-10176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713251#comment-16713251 ] ASF GitHub Bot commented on IGNITE-10176: - GitHub user oignatenko opened a pull request: https://github.com/apache/ignite/pull/5613 IGNITE-10176 migrate non-core modules tests from Junit 3 to 4 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10176 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5613.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 #5613 commit ff4699bebf2571cbd648cbf8bccf1e957c7547e5 Author: Oleg Ignatenko Date: 2018-12-02T23:35:51Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - added @Test -- verified with diffs overview commit a72e24ea010fd7333b7425c349e3de1373aed0fc Author: Oleg Ignatenko Date: 2018-12-03T00:24:34Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit eeeba1cc2f9d9dc02065c19c7c1079008bf73e00 Author: Oleg Ignatenko Date: 2018-12-03T00:26:13Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 9304b5f31ef712708be7d04b68a963d8bf4b050d Author: Oleg Ignatenko Date: 2018-12-03T00:29:51Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 7eaf7a0252fb347f19d192859c410c3c29f7c4b6 Author: Oleg Ignatenko Date: 2018-12-03T00:39:54Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit eaee42ebf611c1617993177d6466e81399c3ebdc Author: Oleg Ignatenko Date: 2018-12-03T00:48:56Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 62738a3820d4057a9c34ad8b2c6e85959ebfc67e Author: Oleg Ignatenko Date: 2018-12-03T00:57:00Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit afb495f9e97e6e15b0c4c29f6d57dd2bbd569f1c Author: Oleg Ignatenko Date: 2018-12-03T08:39:38Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 3b56b742b52a516a4244d2a07635a99d9abeba18 Author: Oleg Ignatenko Date: 2018-12-03T09:06:45Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 3835772a72a99882f9d6cd2557001c9db94ed416 Author: Oleg Ignatenko Date: 2018-12-03T09:31:45Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit ac6be2c4e07748f34da5d83ce3e9f20786ead2fc Author: Oleg Ignatenko Date: 2018-12-03T10:46:59Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 9f663a9c857f76fcb0e56c194cc2d6ec10f6888b Author: Oleg Ignatenko Date: 2018-12-03T11:13:26Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit e2eae3201a88c3d9800b9964ce9ca4096ed3d85f Author: Oleg Ignatenko Date: 2018-12-03T11:31:35Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit f9ccc80de28fb2fc64c96d695f5f906a8cd9a946 Author: Oleg Ignatenko Date: 2018-12-03T12:40:21Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 3eadd0abf6f58a0a3d8fe8464bb08879d412bca1 Author: Oleg Ignatenko Date: 2018-12-03T13:33:00Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 28d9f854993cb99867803cfe0126cf723e071cc5 Author: Oleg Ignatenko Date: 2018-12-03T13:54:52Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit ed54719377f694d0111740c0bbd92dcf5294e6c6 Author: Oleg Ignatenko Date: 2018-12-03T14:10:26Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit fb97a8c23881d1d1c50423dcea6ac519a36c195a Author: Oleg Ignatenko Date: 2018-12-03T14:26:19Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 063f7ae0164924a775b4235ebd0f704017bc2c73 Author: Oleg Ignatenko Date: 2018-12-03T14:45:00Z IGNITE-10175 migrate core module tests from Junit 3 to 4
[jira] [Commented] (IGNITE-10371) [ML] Add multiple metrics calculation fo Binary Classification Evaluation process
[ https://issues.apache.org/jira/browse/IGNITE-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713183#comment-16713183 ] ASF GitHub Bot commented on IGNITE-10371: - GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/5612 IGNITE-10371: [ML] Add multiple metrics calculation fo Binary Classification Evaluation process You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10371 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5612.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 #5612 commit 319f092a96afe1f05e08803acec422e81410e499 Author: Zinoviev Alexey Date: 2018-12-07T18:22:55Z IGNITE-10371: Added examples and multiple metrics commit 161937f0c197870aef8aa7cf50f4732bbef0d343 Author: Zinoviev Alexey Date: 2018-12-07T18:30:16Z IGNITE-10371: Fixed docs commit e9f17e6827a0e38548923a9f26388e2d29eb1400 Author: Zinoviev Alexey Date: 2018-12-07T18:39:08Z IGNITE-10371: Fixed files > [ML] Add multiple metrics calculation fo Binary Classification Evaluation > process > - > > Key: IGNITE-10371 > URL: https://issues.apache.org/jira/browse/IGNITE-10371 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Critical > Fix For: 2.8 > > > Add ability to get map of metrics to evaluate binary classification. > Try to implement: All implemented metrics should be calculated for one > iteration cycle along the data > Naive implementation: compose all passed metrics and calculate them separatly -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10606) [ML] Add new tests for Evaluator
[ https://issues.apache.org/jira/browse/IGNITE-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10606: -- Description: Cover the Evaluator static methods by tests. It should be simple tests smaller than Evaluator example Cover next items: 1) incorrect metrics 2) unexisting labels in a part of metrics 3) repeatable metrics 4) repeatable metrics with repeatable class labels (check count of final results) was: Cover the Evaluator static methods by tests. It should be simple tests smaller than Evaluator example > [ML] Add new tests for Evaluator > > > Key: IGNITE-10606 > URL: https://issues.apache.org/jira/browse/IGNITE-10606 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.8 > > > Cover the Evaluator static methods by tests. > It should be simple tests smaller than Evaluator example > Cover next items: > 1) incorrect metrics > 2) unexisting labels in a part of metrics > 3) repeatable metrics > 4) repeatable metrics with repeatable class labels (check count of final > results) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10606) [ML] Add tests for Evaluator
Aleksey Zinoviev created IGNITE-10606: - Summary: [ML] Add tests for Evaluator Key: IGNITE-10606 URL: https://issues.apache.org/jira/browse/IGNITE-10606 Project: Ignite Issue Type: Task Components: ml Affects Versions: 2.8 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.8 Cover the Evaluator static methods by tests. It should be simple tests smaller than Evaluator example -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10606) [ML] Add new tests for Evaluator
[ https://issues.apache.org/jira/browse/IGNITE-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10606: -- Summary: [ML] Add new tests for Evaluator (was: [ML] Add tests for Evaluator) > [ML] Add new tests for Evaluator > > > Key: IGNITE-10606 > URL: https://issues.apache.org/jira/browse/IGNITE-10606 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.8 > > > Cover the Evaluator static methods by tests. > It should be simple tests smaller than Evaluator example -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10605) [ML] Add multiple metrics calculations to Cross-Validation
Aleksey Zinoviev created IGNITE-10605: - Summary: [ML] Add multiple metrics calculations to Cross-Validation Key: IGNITE-10605 URL: https://issues.apache.org/jira/browse/IGNITE-10605 Project: Ignite Issue Type: Improvement Components: ml Affects Versions: 2.8 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.8 Extend and refactor CrossValidation class methods with scoreCalculator parameter. Refactor tests and examples and tutorial according new changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10604) MVCC: IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover fails
Andrew Mashenkov created IGNITE-10604:
-
Summary: MVCC:
IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover
fails
Key: IGNITE-10604
URL: https://issues.apache.org/jira/browse/IGNITE-10604
Project: Ignite
Issue Type: Bug
Components: data structures, mvcc
Reporter: Andrew Mashenkov
IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover
fails on closing IgniteAtomicLong datastructure.
DhtEnlist request with REMOVE operation with no history fails on MOVING
partition.
{noformat}
[2018-12-07
20:05:14,674][ERROR][sys-stripe-6-#10748%dht.IgniteAtomicLongChangingTopologySelfTest3%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=SingletonSet [SYSTEM_WORKER_BLOCKED]]],
failureCtx=FailureContext [type=CRITICAL_ERROR, err=java.lang.AssertionError]]
java.lang.AssertionError
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.addToBatch(GridDhtTxAbstractEnlistFuture.java:701)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.processEntry(GridDhtTxAbstractEnlistFuture.java:651)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:534)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:363)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearTxEnlistRequest(GridDhtTransactionalCacheAdapter.java:2065)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$900(GridDhtTransactionalCacheAdapter.java:112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$14.apply(GridDhtTransactionalCacheAdapter.java:229)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$14.apply(GridDhtTransactionalCacheAdapter.java:227)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10150) DisappearedCacheWasNotFoundMessageSelfTest fails with NPE
[
https://issues.apache.org/jira/browse/IGNITE-10150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713111#comment-16713111
]
Stanislav Lukyanov commented on IGNITE-10150:
-
[~vozerov], changing the message to "Cache not found on local node (was
concurrently destroyed?) [cacheId=%d]". Is it fine with you?
We can't pass a cache name there since the message is thrown when we don't have
the cache context (so don't have access to cache name).
> DisappearedCacheWasNotFoundMessageSelfTest fails with NPE
> -
>
> Key: IGNITE-10150
> URL: https://issues.apache.org/jira/browse/IGNITE-10150
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Stanislav Lukyanov
>Assignee: Stanislav Lukyanov
>Priority: Major
> Fix For: 2.8
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2226328=buildResultsDiv=IgniteTests24Java8_Queries2
> {code}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.nodesForPartitions(GridReduceQueryExecutor.java:1702)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:690)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$8.iterator(IgniteH2Indexing.java:1801)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$9.iterator(IgniteH2Indexing.java:1869)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:114)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.DisappearedCacheWasNotFoundMessageSelfTest.testDisappearedCacheWasNotFoundMessage(DisappearedCacheWasNotFoundMessageSelfTest.java:59)
> 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:2206)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2121)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9542) [TC bot] provide separated base/current branch history for PR page
[ https://issues.apache.org/jira/browse/IGNITE-9542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9542: --- Description: https://issues.apache.org/jira/browse/IGNITE-9376 works incorrectly without separation of test history for the base and for a shown branch. It is suggested to refactor provided data for the current and for the base branch. It will allow showing blockers based on statistics from any base branch without relation with the previous quering of data. was: https://issues.apache.org/jira/browse/IGNITE-9376 works incorrectly without separation of test history for the base and for a shown branch. It is suggested to refactor provided data for the current and for the base branch. It will allow showing blockers based on statistics from the base branch. > [TC bot] provide separated base/current branch history for PR page > -- > > Key: IGNITE-9542 > URL: https://issues.apache.org/jira/browse/IGNITE-9542 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > https://issues.apache.org/jira/browse/IGNITE-9376 > works incorrectly without separation of test history for the base and for a > shown branch. > It is suggested to refactor provided data for the current and for the base > branch. > It will allow showing blockers based on statistics from any base branch > without relation with the previous quering of data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9542) [TC bot] provide separated base/current branch history for PR page
[ https://issues.apache.org/jira/browse/IGNITE-9542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713109#comment-16713109 ] ASF GitHub Bot commented on IGNITE-9542: dspavlov opened a new pull request #95: IGNITE-9542: new run history stripe URL: https://github.com/apache/ignite-teamcity-bot/pull/95 - flakiness detection - new failures detection - switch to new mode This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [TC bot] provide separated base/current branch history for PR page > -- > > Key: IGNITE-9542 > URL: https://issues.apache.org/jira/browse/IGNITE-9542 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > https://issues.apache.org/jira/browse/IGNITE-9376 > works incorrectly without separation of test history for the base and for a > shown branch. > It is suggested to refactor provided data for the current and for the base > branch. > It will allow showing blockers based on statistics from the base branch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10603) MVCC: Inconsistent partition state after recovery.
Andrew Mashenkov created IGNITE-10603:
-
Summary: MVCC: Inconsistent partition state after recovery.
Key: IGNITE-10603
URL: https://issues.apache.org/jira/browse/IGNITE-10603
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Andrew Mashenkov
IgnitePdsPartitionsStateRecoveryTest.testPartitionsStateConsistencyAfterRecoveryNoCheckpoints()
fails in mvcc mode.
{noformat}
java.lang.AssertionError: Node restored moving partitions after join to
topology.
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertFalse(Assert.java:64)
at
org.apache.ignite.internal.processors.cache.persistence.IgnitePdsPartitionsStateRecoveryTest.testPartitionsStateConsistencyAfterRecoveryNoCheckpoints(IgnitePdsPartitionsStateRecoveryTest.java:165)
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:149)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2106)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2123)
at java.lang.Thread.run(Thread.java:748){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10471) SQL: ALTER TABLE ADD COLUMN doesn't support user types but drop column does
[ https://issues.apache.org/jira/browse/IGNITE-10471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Lukyanov updated IGNITE-10471: Summary: SQL: ALTER TABLE ADD COLUMN doesn't support user types but drop column does (was: SQL: Alter table to add column syntax doesn't support the user types but drop column can drop such fields) > SQL: ALTER TABLE ADD COLUMN doesn't support user types but drop column does > --- > > Key: IGNITE-10471 > URL: https://issues.apache.org/jira/browse/IGNITE-10471 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.6 >Reporter: Andrey Aleksandrov >Priority: Minor > Fix For: 2.8 > > > Looks like ALTER COLUMN commands could be used only on a subset of supported > types (that could be used in CREATE TABLE syntax): > [https://apacheignite-sql.readme.io/docs/data-types] > But using query entities we can provide to use a field that has user types. > This fields can be used in > ALTER TABLE CACHE_NAME DROP COLUMN COLUMN_NAME > But it can't be used as next: > ALTER TABLE CACHE_NAME ADD COLUMN COLUMN_NAME 'type' > Where type is a user's one. > Possible we should think about supporting POJO and enums. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10471) SQL: ADD COLUMN doesn't support user types but DROP COLUMN does
[ https://issues.apache.org/jira/browse/IGNITE-10471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Lukyanov updated IGNITE-10471: Summary: SQL: ADD COLUMN doesn't support user types but DROP COLUMN does (was: SQL: ALTER TABLE ADD COLUMN doesn't support user types but drop column does) > SQL: ADD COLUMN doesn't support user types but DROP COLUMN does > --- > > Key: IGNITE-10471 > URL: https://issues.apache.org/jira/browse/IGNITE-10471 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.6 >Reporter: Andrey Aleksandrov >Priority: Minor > Fix For: 2.8 > > > Looks like ALTER COLUMN commands could be used only on a subset of supported > types (that could be used in CREATE TABLE syntax): > [https://apacheignite-sql.readme.io/docs/data-types] > But using query entities we can provide to use a field that has user types. > This fields can be used in > ALTER TABLE CACHE_NAME DROP COLUMN COLUMN_NAME > But it can't be used as next: > ALTER TABLE CACHE_NAME ADD COLUMN COLUMN_NAME 'type' > Where type is a user's one. > Possible we should think about supporting POJO and enums. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10471) SQL: Alter table to add column syntax doesn't support the user types but drop column can drop such fields
[ https://issues.apache.org/jira/browse/IGNITE-10471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Lukyanov updated IGNITE-10471: Summary: SQL: Alter table to add column syntax doesn't support the user types but drop column can drop such fields (was: SQL: Alter table to add column sytax doesn't support the user types but drop column can drop such fields) > SQL: Alter table to add column syntax doesn't support the user types but drop > column can drop such fields > - > > Key: IGNITE-10471 > URL: https://issues.apache.org/jira/browse/IGNITE-10471 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.6 >Reporter: Andrey Aleksandrov >Priority: Minor > Fix For: 2.8 > > > Looks like ALTER COLUMN commands could be used only on a subset of supported > types (that could be used in CREATE TABLE syntax): > [https://apacheignite-sql.readme.io/docs/data-types] > But using query entities we can provide to use a field that has user types. > This fields can be used in > ALTER TABLE CACHE_NAME DROP COLUMN COLUMN_NAME > But it can't be used as next: > ALTER TABLE CACHE_NAME ADD COLUMN COLUMN_NAME 'type' > Where type is a user's one. > Possible we should think about supporting POJO and enums. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10602) Failure parsing INLINE_SIZE if CREATE INDEX is one of multiple statements
Ilya Kasnacheev created IGNITE-10602:
Summary: Failure parsing INLINE_SIZE if CREATE INDEX is one of
multiple statements
Key: IGNITE-10602
URL: https://issues.apache.org/jira/browse/IGNITE-10602
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.7
Reporter: Ilya Kasnacheev
On an empty cluster issue the following statements (shown using sqlline):
{code}
0: jdbc:ignite:thin://localhost> CREATE TABLE public.transactions (pk INT, id
INT, k
. . . . . . . . . . . . . . . .> VARCHAR, v VARCHAR, PRIMARY KEY (pk, id));
CREATE INDEX transactions_id_k_v ON public.transactions (id, k, v) INLINE_SIZE
150; CREATE INDEX transactions_k_v_id ON
. . . . . . . . . . . . . . . .> public.transactions (k, v, id) INLINE_SIZE
150; CREATE INDEX transactions_pk_id ON public.transactions
. . . . . . . . . . . . . . . .> (pk, id) INLINE_SIZE 20;
{code}
Expected: Table is created, three indexes are created.
Actual: table is created, indexes are NOT created, error is printed:
{{Error: Failed to parse query. Синтаксическая ошибка в выражении SQL "CREATE
INDEX TRANSACTIONS_ID_K_V ON PUBLIC.TRANSACTIONS (ID, K, V) INLINE_SIZE[*] 150;
CREATE INDEX TRANSACTIONS_K_V_ID ON}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10589) Multiple server node failure after a client node stopping
[
https://issues.apache.org/jira/browse/IGNITE-10589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-10589:
--
Fix Version/s: 2.8
> Multiple server node failure after a client node stopping
> -
>
> Key: IGNITE-10589
> URL: https://issues.apache.org/jira/browse/IGNITE-10589
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Kosarev
>Assignee: Ilya Lantukh
>Priority: Critical
> Fix For: 2.8
>
> Attachments: 16_02.tar
>
>
> after stopping a client
> we see topology change and pme finish on the coordinator,
> and at soon on another nodes we still don't see new topology, but have
> Critical error resulting nodes failure
> crd log
> {code}
> 2018-12-06 15:55:23.660 [WARN
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Node FAILED: ZookeeperClusterNode [id=979f03db-f858-44f6-8646-12034dfd5c93,
> addrs=[10.116.206.1], order=129, loc=false, client=true]
> 2018-12-06 15:55:23.660 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Topology snapshot [ver=162, servers=128, clients=0, CPUs=7168,
> offheap=14.0GB, heap=4000.0GB]
> 2018-12-06 15:55:23.660 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- Node [id=44D27930-80E5-4EB7-B377-8B07C02C2033, clusterState=ACTIVE]
> 2018-12-06 15:55:23.660 [INFO
> ][zk-DPL_GRID%DplGridNodeName-EventThread][o.a.i.s.d.z.i.ZookeeperDiscoveryImpl]
> Process alive nodes change [alives=128]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- Baseline [id=0, size=128, online=128, offline=0]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Data Regions Configured:
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- dpl_mem_plc [initSize=256.0 MiB, maxSize=556.6 GiB,
> persistenceEnabled=true]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- not-persisted [initSize=256.0 MiB, maxSize=556.6 GiB,
> persistenceEnabled=false]
> 2018-12-06 15:55:23.670
> [DEBUG][sys-#564%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
> Process node left 979f03db-f858-44f6-8646-12034dfd5c93
> 2018-12-06 15:55:23.670 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time]
> Started exchange init [topVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], crd=true, evt=NODE_FAILED,
> evtNode=979f03db-f858-44f6-8646-12034dfd5c93, customEvt=null, allowMerge=true]
> 2018-12-06 15:55:23.712 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time]
> Finished exchange init [topVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], crd=true]
> 2018-12-06 15:55:23.699 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Finish exchange future [startVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=162, minorTopVer=0],
> err=null]
> {code}
> on a node(1) we have critical error(1)
> {code}
> 2018-12-06 15:55:23.727
> [ERROR][utility-#432%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed processing message [senderId=1e17c56a-5213-4a1b-b94b-4575a95a2c81,
> msg=GridDhtTxPrepareRequest [nearNodeId=44d27930-80e5-4eb7-b377-8b07c02c2033,
> futId=1d225238761-05eea259-5c25-4a4b-8469-9dd8980e218c, miniId=105,
> topVer=AffinityTopologyVersion [topVer=162, minorTopVer=0],
> invalidateNearEntries={}, nearWrites=null, owned=null,
> nearXidVer=GridCacheVersion [topVer=155571374, order=1545423626166, nodeOrd
> er=1], subjId=44d27930-80e5-4eb7-b377-8b07c02c2033, taskNameHash=0,
> preloadKeys=null, skipCompletedVers=false,
> super=GridDistributedTxPrepareRequest [threadId=1281,
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, writeVer=GridCacheVersion
> [topVer=15557137
> 4, order=1545423626614, nodeOrder=96], timeout=0, reads=null,
> writes=ArrayList [IgniteTxEntry [key=KeyCacheObjectImpl [part=65,
> val=GridServiceAssignmentsKey [name=DPLThreadManager_service],
> hasValBytes=true], cacheId=-2100569601, txKey=IgniteTxKey [key=KeyCa
> cheObjectImpl [part=65, val=GridServiceAssignmentsKey
> [name=DPLThreadManager_service], hasValBytes=true], cacheId=-2100569601],
> val=CacheObjectImpl [val=GridServiceAssignments
> [nodeId=426a4a51-1af3-4019-9769-4a58d8ece426, topVer=162,
> cfg=LazyServiceConfigurat
> ion
[jira] [Updated] (IGNITE-10589) Multiple server node failure after a client node stopping
[
https://issues.apache.org/jira/browse/IGNITE-10589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-10589:
--
Ignite Flags: (was: Docs Required)
> Multiple server node failure after a client node stopping
> -
>
> Key: IGNITE-10589
> URL: https://issues.apache.org/jira/browse/IGNITE-10589
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Kosarev
>Assignee: Ilya Lantukh
>Priority: Critical
> Fix For: 2.8
>
> Attachments: 16_02.tar
>
>
> after stopping a client
> we see topology change and pme finish on the coordinator,
> and at soon on another nodes we still don't see new topology, but have
> Critical error resulting nodes failure
> crd log
> {code}
> 2018-12-06 15:55:23.660 [WARN
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Node FAILED: ZookeeperClusterNode [id=979f03db-f858-44f6-8646-12034dfd5c93,
> addrs=[10.116.206.1], order=129, loc=false, client=true]
> 2018-12-06 15:55:23.660 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Topology snapshot [ver=162, servers=128, clients=0, CPUs=7168,
> offheap=14.0GB, heap=4000.0GB]
> 2018-12-06 15:55:23.660 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- Node [id=44D27930-80E5-4EB7-B377-8B07C02C2033, clusterState=ACTIVE]
> 2018-12-06 15:55:23.660 [INFO
> ][zk-DPL_GRID%DplGridNodeName-EventThread][o.a.i.s.d.z.i.ZookeeperDiscoveryImpl]
> Process alive nodes change [alives=128]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- Baseline [id=0, size=128, online=128, offline=0]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Data Regions Configured:
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- dpl_mem_plc [initSize=256.0 MiB, maxSize=556.6 GiB,
> persistenceEnabled=true]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- not-persisted [initSize=256.0 MiB, maxSize=556.6 GiB,
> persistenceEnabled=false]
> 2018-12-06 15:55:23.670
> [DEBUG][sys-#564%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
> Process node left 979f03db-f858-44f6-8646-12034dfd5c93
> 2018-12-06 15:55:23.670 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time]
> Started exchange init [topVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], crd=true, evt=NODE_FAILED,
> evtNode=979f03db-f858-44f6-8646-12034dfd5c93, customEvt=null, allowMerge=true]
> 2018-12-06 15:55:23.712 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time]
> Finished exchange init [topVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], crd=true]
> 2018-12-06 15:55:23.699 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Finish exchange future [startVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=162, minorTopVer=0],
> err=null]
> {code}
> on a node(1) we have critical error(1)
> {code}
> 2018-12-06 15:55:23.727
> [ERROR][utility-#432%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed processing message [senderId=1e17c56a-5213-4a1b-b94b-4575a95a2c81,
> msg=GridDhtTxPrepareRequest [nearNodeId=44d27930-80e5-4eb7-b377-8b07c02c2033,
> futId=1d225238761-05eea259-5c25-4a4b-8469-9dd8980e218c, miniId=105,
> topVer=AffinityTopologyVersion [topVer=162, minorTopVer=0],
> invalidateNearEntries={}, nearWrites=null, owned=null,
> nearXidVer=GridCacheVersion [topVer=155571374, order=1545423626166, nodeOrd
> er=1], subjId=44d27930-80e5-4eb7-b377-8b07c02c2033, taskNameHash=0,
> preloadKeys=null, skipCompletedVers=false,
> super=GridDistributedTxPrepareRequest [threadId=1281,
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, writeVer=GridCacheVersion
> [topVer=15557137
> 4, order=1545423626614, nodeOrder=96], timeout=0, reads=null,
> writes=ArrayList [IgniteTxEntry [key=KeyCacheObjectImpl [part=65,
> val=GridServiceAssignmentsKey [name=DPLThreadManager_service],
> hasValBytes=true], cacheId=-2100569601, txKey=IgniteTxKey [key=KeyCa
> cheObjectImpl [part=65, val=GridServiceAssignmentsKey
> [name=DPLThreadManager_service], hasValBytes=true], cacheId=-2100569601],
> val=CacheObjectImpl [val=GridServiceAssignments
> [nodeId=426a4a51-1af3-4019-9769-4a58d8ece426, topVer=162,
> cfg=LazyServiceConfigurat
> ion
[jira] [Commented] (IGNITE-10589) Multiple server node failure after a client node stopping
[
https://issues.apache.org/jira/browse/IGNITE-10589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713015#comment-16713015
]
Alexey Goncharuk commented on IGNITE-10589:
---
[~ilantukh], changes look good to me, one note - please add a short description
of this scenario in the code.
Will merge once we confirm that TC tests are ok.
> Multiple server node failure after a client node stopping
> -
>
> Key: IGNITE-10589
> URL: https://issues.apache.org/jira/browse/IGNITE-10589
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Kosarev
>Assignee: Ilya Lantukh
>Priority: Critical
> Fix For: 2.8
>
> Attachments: 16_02.tar
>
>
> after stopping a client
> we see topology change and pme finish on the coordinator,
> and at soon on another nodes we still don't see new topology, but have
> Critical error resulting nodes failure
> crd log
> {code}
> 2018-12-06 15:55:23.660 [WARN
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Node FAILED: ZookeeperClusterNode [id=979f03db-f858-44f6-8646-12034dfd5c93,
> addrs=[10.116.206.1], order=129, loc=false, client=true]
> 2018-12-06 15:55:23.660 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Topology snapshot [ver=162, servers=128, clients=0, CPUs=7168,
> offheap=14.0GB, heap=4000.0GB]
> 2018-12-06 15:55:23.660 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- Node [id=44D27930-80E5-4EB7-B377-8B07C02C2033, clusterState=ACTIVE]
> 2018-12-06 15:55:23.660 [INFO
> ][zk-DPL_GRID%DplGridNodeName-EventThread][o.a.i.s.d.z.i.ZookeeperDiscoveryImpl]
> Process alive nodes change [alives=128]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- Baseline [id=0, size=128, online=128, offline=0]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Data Regions Configured:
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- dpl_mem_plc [initSize=256.0 MiB, maxSize=556.6 GiB,
> persistenceEnabled=true]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- not-persisted [initSize=256.0 MiB, maxSize=556.6 GiB,
> persistenceEnabled=false]
> 2018-12-06 15:55:23.670
> [DEBUG][sys-#564%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
> Process node left 979f03db-f858-44f6-8646-12034dfd5c93
> 2018-12-06 15:55:23.670 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time]
> Started exchange init [topVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], crd=true, evt=NODE_FAILED,
> evtNode=979f03db-f858-44f6-8646-12034dfd5c93, customEvt=null, allowMerge=true]
> 2018-12-06 15:55:23.712 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time]
> Finished exchange init [topVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], crd=true]
> 2018-12-06 15:55:23.699 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Finish exchange future [startVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=162, minorTopVer=0],
> err=null]
> {code}
> on a node(1) we have critical error(1)
> {code}
> 2018-12-06 15:55:23.727
> [ERROR][utility-#432%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed processing message [senderId=1e17c56a-5213-4a1b-b94b-4575a95a2c81,
> msg=GridDhtTxPrepareRequest [nearNodeId=44d27930-80e5-4eb7-b377-8b07c02c2033,
> futId=1d225238761-05eea259-5c25-4a4b-8469-9dd8980e218c, miniId=105,
> topVer=AffinityTopologyVersion [topVer=162, minorTopVer=0],
> invalidateNearEntries={}, nearWrites=null, owned=null,
> nearXidVer=GridCacheVersion [topVer=155571374, order=1545423626166, nodeOrd
> er=1], subjId=44d27930-80e5-4eb7-b377-8b07c02c2033, taskNameHash=0,
> preloadKeys=null, skipCompletedVers=false,
> super=GridDistributedTxPrepareRequest [threadId=1281,
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, writeVer=GridCacheVersion
> [topVer=15557137
> 4, order=1545423626614, nodeOrder=96], timeout=0, reads=null,
> writes=ArrayList [IgniteTxEntry [key=KeyCacheObjectImpl [part=65,
> val=GridServiceAssignmentsKey [name=DPLThreadManager_service],
> hasValBytes=true], cacheId=-2100569601, txKey=IgniteTxKey [key=KeyCa
> cheObjectImpl [part=65, val=GridServiceAssignmentsKey
> [name=DPLThreadManager_service], hasValBytes=true], cacheId=-2100569601],
>
[jira] [Commented] (IGNITE-10589) Multiple server node failure after a client node stopping
[
https://issues.apache.org/jira/browse/IGNITE-10589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712984#comment-16712984
]
ASF GitHub Bot commented on IGNITE-10589:
-
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/5609
IGNITE-10589
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10589
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5609.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 #5609
commit 3ed80f1c6709e0ee3f1d51dc5614a60e3f146c8f
Author: Ilya Lantukh
Date: 2018-12-07T14:05:03Z
IGNITE-10589 : Fixed lastAffTopVer check in DiscoCache for merged exchanges.
commit f7eb669e561db5653c801553bc7fc4788d03ba4a
Author: Ilya Lantukh
Date: 2018-12-07T14:55:00Z
IGNITE-10589 : Fixed lastAffTopVer calculation for merged exchanges.
commit 392a339e68b4543dc7dfdab8572d6e1ca21704de
Author: Ilya Lantukh
Date: 2018-12-07T15:39:09Z
IGNITE-10589 : Test.
> Multiple server node failure after a client node stopping
> -
>
> Key: IGNITE-10589
> URL: https://issues.apache.org/jira/browse/IGNITE-10589
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Kosarev
>Assignee: Ilya Lantukh
>Priority: Critical
> Attachments: 16_02.tar
>
>
> after stopping a client
> we see topology change and pme finish on the coordinator,
> and at soon on another nodes we still don't see new topology, but have
> Critical error resulting nodes failure
> crd log
> {code}
> 2018-12-06 15:55:23.660 [WARN
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Node FAILED: ZookeeperClusterNode [id=979f03db-f858-44f6-8646-12034dfd5c93,
> addrs=[10.116.206.1], order=129, loc=false, client=true]
> 2018-12-06 15:55:23.660 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Topology snapshot [ver=162, servers=128, clients=0, CPUs=7168,
> offheap=14.0GB, heap=4000.0GB]
> 2018-12-06 15:55:23.660 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- Node [id=44D27930-80E5-4EB7-B377-8B07C02C2033, clusterState=ACTIVE]
> 2018-12-06 15:55:23.660 [INFO
> ][zk-DPL_GRID%DplGridNodeName-EventThread][o.a.i.s.d.z.i.ZookeeperDiscoveryImpl]
> Process alive nodes change [alives=128]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- Baseline [id=0, size=128, online=128, offline=0]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Data Regions Configured:
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- dpl_mem_plc [initSize=256.0 MiB, maxSize=556.6 GiB,
> persistenceEnabled=true]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- not-persisted [initSize=256.0 MiB, maxSize=556.6 GiB,
> persistenceEnabled=false]
> 2018-12-06 15:55:23.670
> [DEBUG][sys-#564%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
> Process node left 979f03db-f858-44f6-8646-12034dfd5c93
> 2018-12-06 15:55:23.670 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time]
> Started exchange init [topVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], crd=true, evt=NODE_FAILED,
> evtNode=979f03db-f858-44f6-8646-12034dfd5c93, customEvt=null, allowMerge=true]
> 2018-12-06 15:55:23.712 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time]
> Finished exchange init [topVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], crd=true]
> 2018-12-06 15:55:23.699 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Finish exchange future [startVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=162, minorTopVer=0],
> err=null]
> {code}
> on a node(1) we have critical error(1)
> {code}
> 2018-12-06 15:55:23.727
> [ERROR][utility-#432%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed processing message [senderId=1e17c56a-5213-4a1b-b94b-4575a95a2c81,
> msg=GridDhtTxPrepareRequest [nearNodeId=44d27930-80e5-4eb7-b377-8b07c02c2033,
> futId=1d225238761-05eea259-5c25-4a4b-8469-9dd8980e218c, miniId=105,
> topVer=AffinityTopologyVersion [topVer=162,
[jira] [Resolved] (IGNITE-10562) [TC Bot] DB contains invalid values for build references ID maps to value with other ID
[
https://issues.apache.org/jira/browse/IGNITE-10562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov resolved IGNITE-10562.
-
Resolution: Fixed
Fixed with extended ID validation of builds.
Validation is enforced by FatBuildCompacted._ver = 5 -> 6
Old persistence calls not used anymore for fat builds.
V181206
> [TC Bot] DB contains invalid values for build references ID maps to value
> with other ID
> ---
>
> Key: IGNITE-10562
> URL: https://issues.apache.org/jira/browse/IGNITE-10562
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
>
> New Fat builds storage takes initial data from old cache "apache.builds":
> String->JavaObject.
> This cache contains a number of incorrect build ID->build mapping.
> Example:
> {noformat}
>
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="4532"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253798buildTypeId=IgniteTests24Java8_Cloud;
> href="/app/rest/latest/builds/id:2253798">
> projectId="IgniteTests24Java8" projectName="Ignite Tests 2.4+ (Java
> 8/9/10/11)" href="/app/rest/latest/buildTypes/id:IgniteTests24Java8_Cloud"/>
> 20181106T114741+0300
> 20181106T130017+0300
> 20181106T130156+0300
>
> buildTypeId="IgniteTests24Java8_BuildApacheIgnite"
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="8100"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253788buildTypeId=IgniteTests24Java8_BuildApacheIgnite;
> href="/app/rest/latest/builds/id:2253788"/>
>
> href="/app/rest/latest/testOccurrences?locator=build:(id:2253798)" count="2"
> passed="1" muted="1"/>
>
>
>
> version="6eda0197db2721620d0671c5f8a7e1712465dace" username="zzzadruga"
> date="20181106T114312+0300"
> webUrl="http://ci.ignite.apache.org/viewModification.html?modId=837621personal=false;
> href="/app/rest/latest/changes/id:837621"/>
>
>
>
> href="/app/rest/latest/users/id:281"/>
> branchName="pull/4478/head" status="FAILURE" state="finished" number="6369"
> composite="true"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253900buildTypeId=IgniteTests24Java8_RunAll;
> href="/app/rest/latest/builds/id:2253900"/>
>
>
> {noformat}
> It is required to
> - stop using deprecated persistent TC
> - remove incorrect Fat Build entries (migration procedure or background task).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10599) Add test for Scheduler Example test to LGPL Examples suite
[ https://issues.apache.org/jira/browse/IGNITE-10599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev reassigned IGNITE-10599: Assignee: Ilya Kasnacheev > Add test for Scheduler Example test 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 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10599) Add test for Scheduler Example test to LGPL Examples suite
[ https://issues.apache.org/jira/browse/IGNITE-10599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712993#comment-16712993 ] ASF GitHub Bot commented on IGNITE-10599: - GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/5610 IGNITE-10599 Add Compute Schedule example to LGPL suite. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10599 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5610.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 #5610 commit 0de0fc5b228a3ad9ae817e5d66b503684cf8efc5 Author: Ilya Kasnacheev Date: 2018-12-07T15:43:19Z IGNITE-10599 Add Compute Schedule example to LGPL suite. > Add test for Scheduler Example test to LGPL Examples suite > -- > > Key: IGNITE-10599 > URL: https://issues.apache.org/jira/browse/IGNITE-10599 > Project: Ignite > Issue Type: Test >Reporter: Ilya Kasnacheev >Priority: Major > Labels: test > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10601) USE INDEX ("index_name") does not work with DELETE query
Abhishek Kumar created IGNITE-10601:
---
Summary: USE INDEX ("index_name") does not work with DELETE query
Key: IGNITE-10601
URL: https://issues.apache.org/jira/browse/IGNITE-10601
Project: Ignite
Issue Type: Bug
Components: jdbc
Affects Versions: 2.6
Reporter: Abhishek Kumar
At my work we're using ignite for our data caching and we mostly request data
from ignite with range queries. I recently found out that H2 database does not
support range queries very well. Range query works if it is the only condition
in the "where" clause but i want to have range plus bounded query condition
together which does not work vary well. In this case, Ignite is not able to
resolve the best suited index. Although i found a nice solution that i can use
"USE INDEX" in my query and specify which index to use. Unfortunately this does
not work with "Delete" query.
Query :- DELETE FROM Person USE INDEX(index_age) WHERE name = 'Perter' AND age
< 35;
Exception :-
Caused by: org.h2.jdbc.JdbcSQLException: Syntax error in SQL statement "DELETE
FROM Person USE INDEX[*] (index_age) WHERE (name= CAST(? AS VARCHAR) AND age <
CAST(? AS BIGINT)) "; SQL statement:
delete from Person use index (index_age) where (name= cast(? as varchar) and
age < cast(? as bigint)) [42000-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.message.DbException.getSyntaxError(DbException.java:191)
at org.h2.command.Parser.getSyntaxError(Parser.java:533)
at org.h2.command.Parser.prepareCommand(Parser.java:260)
at org.h2.engine.Session.prepareLocal(Session.java:573)
at org.h2.engine.Session.prepareCommand(Session.java:514)
at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1204)
at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:288)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepare0(IgniteH2Indexing.java:484)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:452)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:419)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2008)
... 54 more
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10601) USE INDEX ("index_name") does not work with DELETE query
[
https://issues.apache.org/jira/browse/IGNITE-10601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated IGNITE-10601:
Description:
At my work we're using ignite for our data caching and we mostly request data
from ignite with range queries. I recently found out that H2 database does not
support range queries very well. Range query works if it is the only condition
in the "where" clause but i want to have range plus bounded query condition
together which does not work vary well and Ignite is not able to resolve the
best suited index. Although i found a nice
[solution|https://apacheignite.readme.io/v2.0/docs/sql-performance-and-debugging#section-index-hints]
that i can use "USE INDEX" in my query and specify which index to use.
Unfortunately this does not work with "Delete" query.
Query :- DELETE FROM Person USE INDEX(index_age) WHERE name = 'Perter' AND age
< 35;
Exception :-
Caused by: org.h2.jdbc.JdbcSQLException: Syntax error in SQL statement "DELETE
FROM Person USE INDEX[*] (index_age) WHERE (name= CAST(? AS VARCHAR) AND age <
CAST(? AS BIGINT)) "; SQL statement:
delete from Person use index (index_age) where (name= cast(? as varchar) and
age < cast(? as bigint)) [42000-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.message.DbException.getSyntaxError(DbException.java:191)
at org.h2.command.Parser.getSyntaxError(Parser.java:533)
at org.h2.command.Parser.prepareCommand(Parser.java:260)
at org.h2.engine.Session.prepareLocal(Session.java:573)
at org.h2.engine.Session.prepareCommand(Session.java:514)
at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1204)
at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:288)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepare0(IgniteH2Indexing.java:484)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:452)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:419)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2008)
... 54 more
was:
At my work we're using ignite for our data caching and we mostly request data
from ignite with range queries. I recently found out that H2 database does not
support range queries very well. Range query works if it is the only condition
in the "where" clause but i want to have range plus bounded query condition
together which does not work vary well and Ignite is not able to resolve the
best suited index. Although i found a nice solution that i can use "USE INDEX"
in my query and specify which index to use. Unfortunately this does not work
with "Delete" query.
Query :- DELETE FROM Person USE INDEX(index_age) WHERE name = 'Perter' AND age
< 35;
Exception :-
Caused by: org.h2.jdbc.JdbcSQLException: Syntax error in SQL statement "DELETE
FROM Person USE INDEX[*] (index_age) WHERE (name= CAST(? AS VARCHAR) AND age <
CAST(? AS BIGINT)) "; SQL statement:
delete from Person use index (index_age) where (name= cast(? as varchar) and
age < cast(? as bigint)) [42000-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.message.DbException.getSyntaxError(DbException.java:191)
at org.h2.command.Parser.getSyntaxError(Parser.java:533)
at org.h2.command.Parser.prepareCommand(Parser.java:260)
at org.h2.engine.Session.prepareLocal(Session.java:573)
at org.h2.engine.Session.prepareCommand(Session.java:514)
at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1204)
at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:288)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepare0(IgniteH2Indexing.java:484)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:452)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:419)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2008)
... 54 more
> USE INDEX ("index_name") does not work with DELETE query
>
>
> Key: IGNITE-10601
> URL: https://issues.apache.org/jira/browse/IGNITE-10601
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.6
>
[jira] [Updated] (IGNITE-10601) USE INDEX ("index_name") does not work with DELETE query
[
https://issues.apache.org/jira/browse/IGNITE-10601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated IGNITE-10601:
Description:
At my work we're using ignite for our data caching and we mostly request data
from ignite with range queries. I recently found out that H2 database does not
support range queries very well. Range query works if it is the only condition
in the "where" clause but i want to have range plus bounded query condition
together which does not work vary well and Ignite is not able to resolve the
best suited index. Although i found a nice solution that i can use "USE INDEX"
in my query and specify which index to use. Unfortunately this does not work
with "Delete" query.
Query :- DELETE FROM Person USE INDEX(index_age) WHERE name = 'Perter' AND age
< 35;
Exception :-
Caused by: org.h2.jdbc.JdbcSQLException: Syntax error in SQL statement "DELETE
FROM Person USE INDEX[*] (index_age) WHERE (name= CAST(? AS VARCHAR) AND age <
CAST(? AS BIGINT)) "; SQL statement:
delete from Person use index (index_age) where (name= cast(? as varchar) and
age < cast(? as bigint)) [42000-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.message.DbException.getSyntaxError(DbException.java:191)
at org.h2.command.Parser.getSyntaxError(Parser.java:533)
at org.h2.command.Parser.prepareCommand(Parser.java:260)
at org.h2.engine.Session.prepareLocal(Session.java:573)
at org.h2.engine.Session.prepareCommand(Session.java:514)
at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1204)
at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:288)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepare0(IgniteH2Indexing.java:484)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:452)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:419)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2008)
... 54 more
was:
At my work we're using ignite for our data caching and we mostly request data
from ignite with range queries. I recently found out that H2 database does not
support range queries very well. Range query works if it is the only condition
in the "where" clause but i want to have range plus bounded query condition
together which does not work vary well. In this case, Ignite is not able to
resolve the best suited index. Although i found a nice solution that i can use
"USE INDEX" in my query and specify which index to use. Unfortunately this does
not work with "Delete" query.
Query :- DELETE FROM Person USE INDEX(index_age) WHERE name = 'Perter' AND age
< 35;
Exception :-
Caused by: org.h2.jdbc.JdbcSQLException: Syntax error in SQL statement "DELETE
FROM Person USE INDEX[*] (index_age) WHERE (name= CAST(? AS VARCHAR) AND age <
CAST(? AS BIGINT)) "; SQL statement:
delete from Person use index (index_age) where (name= cast(? as varchar) and
age < cast(? as bigint)) [42000-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.message.DbException.getSyntaxError(DbException.java:191)
at org.h2.command.Parser.getSyntaxError(Parser.java:533)
at org.h2.command.Parser.prepareCommand(Parser.java:260)
at org.h2.engine.Session.prepareLocal(Session.java:573)
at org.h2.engine.Session.prepareCommand(Session.java:514)
at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1204)
at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:288)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepare0(IgniteH2Indexing.java:484)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:452)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:419)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2008)
... 54 more
> USE INDEX ("index_name") does not work with DELETE query
>
>
> Key: IGNITE-10601
> URL: https://issues.apache.org/jira/browse/IGNITE-10601
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.6
>Reporter: Abhishek Kumar
>Priority: Major
>
> At my work
[jira] [Updated] (IGNITE-10596) Introduce Docker images release build
[ https://issues.apache.org/jira/browse/IGNITE-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-10596: -- Issue Type: Sub-task (was: Improvement) Parent: IGNITE-10600 > Introduce Docker images release build > - > > Key: IGNITE-10596 > URL: https://issues.apache.org/jira/browse/IGNITE-10596 > Project: Ignite > Issue Type: Sub-task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.8 > > > Add > [new|https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteRelease_Run_ApacheIgnitePostRelease_BuildUploadDockerImages] > build in [Apache Ignite > Release|https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8=projectOverview] > project for building and uploading Docker images based on Release build > artifacts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10572) MVCC TX: Possible race on invokeAll operations
[
https://issues.apache.org/jira/browse/IGNITE-10572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712968#comment-16712968
]
ASF GitHub Bot commented on IGNITE-10572:
-
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5608
IGNITE-10572: Fix races in mvcc invokeAll().
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10572
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5608.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 #5608
commit 118c2d842d557f85f6aa98d878bad4fc809e500b
Author: Andrey V. Mashenkov
Date: 2018-12-07T14:32:16Z
IGNITE-10572: Fix races on invokeAll().
> MVCC TX: Possible race on invokeAll operations
> --
>
> Key: IGNITE-10572
> URL: https://issues.apache.org/jira/browse/IGNITE-10572
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Igor Seliverstov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.8
>
>
> see {{GridNearTxEnlistFuture#checkResponse}} method.
> 1) race on result creation - two threads may see {{this.res == null}} and
> just set their values, result is partially lost
> 2) race on success flag set - just set false flag may be overwritten by
> concurrent successful response checking operation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10595) Introduce RPM / DEB release build
[ https://issues.apache.org/jira/browse/IGNITE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-10595: -- Issue Type: Sub-task (was: Improvement) Parent: IGNITE-10600 > Introduce RPM / DEB release build > - > > Key: IGNITE-10595 > URL: https://issues.apache.org/jira/browse/IGNITE-10595 > Project: Ignite > Issue Type: Sub-task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.8 > > > Add > [new|https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteRelease_Run_ApacheIgnitePostRelease_BuildUploadRpmDebPackages] > build in [Apache Ignite > Release|https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8=projectOverview] > project for building and uploading RPM / DEB packages based on Release build > artifacts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10600) Revise Apache Ignite release build
Peter Ivanov created IGNITE-10600: - Summary: Revise Apache Ignite release build Key: IGNITE-10600 URL: https://issues.apache.org/jira/browse/IGNITE-10600 Project: Ignite Issue Type: Improvement Reporter: Peter Ivanov Assignee: Peter Ivanov Fix For: 2.8 Current set of Apache Ignite release builds on TC have to be revised and refactored to become more stable and understandable. Also, release documentation has to be modified to fit the changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10577) ignite-kubernetes is missing jackson-annotations dependency
[
https://issues.apache.org/jira/browse/IGNITE-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10577:
Ignite Flags: (was: Docs Required)
> ignite-kubernetes is missing jackson-annotations dependency
> ---
>
> Key: IGNITE-10577
> URL: https://issues.apache.org/jira/browse/IGNITE-10577
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 2.7
>Reporter: Stephen Darlington
>Assignee: Stephen Darlington
>Priority: Major
>
> When starting 2.7 with the ignite-kubernetes option I get the following
> exception on startup:
>
> {code}
> [13:44:34,605][SEVERE][main][IgniteKernal] Got exception while starting (will
> rollback startup routine).
> java.lang.NoClassDefFoundError: com/fasterxml/jackson/annotation/JsonView
> at
> com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector.(JacksonAnnotationIntrospector.java:37)
> at
> com.fasterxml.jackson.databind.ObjectMapper.(ObjectMapper.java:291)
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder.getRegisteredAddresses(TcpDiscoveryKubernetesIpFinder.java:151)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredAddresses(TcpDiscoverySpi.java:1900)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.resolvedAddresses(TcpDiscoverySpi.java:1848)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:1049)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:910)
> {code}
>
> It's clearly missing a dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10596) Introduce Docker images release build
[ https://issues.apache.org/jira/browse/IGNITE-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-10596: -- Description: Add [new|https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteRelease_Run_ApacheIgnitePostRelease_BuildUploadDockerImages] build in [Apache Ignite Release|https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8=projectOverview] project for building and uploading Docker images based on Release build artifacts. was: Add new build in [Apache Ignite Release|https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8=projectOverview] project for building and uploading Docker images based on Release build artifacts. > Introduce Docker images release build > - > > Key: IGNITE-10596 > URL: https://issues.apache.org/jira/browse/IGNITE-10596 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.8 > > > Add > [new|https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteRelease_Run_ApacheIgnitePostRelease_BuildUploadDockerImages] > build in [Apache Ignite > Release|https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8=projectOverview] > project for building and uploading Docker images based on Release build > artifacts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10461) MVCC: Create "PDS 1" test suite for MVCC mode.
[ https://issues.apache.org/jira/browse/IGNITE-10461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712941#comment-16712941 ] Roman Kondakov commented on IGNITE-10461: - [~amashenkov], [~gvvinblade], patch looks good for me and can be merged to master. > MVCC: Create "PDS 1" test suite for MVCC mode. > -- > > Key: IGNITE-10461 > URL: https://issues.apache.org/jira/browse/IGNITE-10461 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.8 > > > Create MVCC version of IgnitePdsTestSuite and add it to TC. > All non-relevant tests should be marked as ignored. > Failed tests should be muted and tickets should be created for unknown > failure reasons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10599) Add test for Scheduler Example test to LGPL Examples suite
[ https://issues.apache.org/jira/browse/IGNITE-10599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712936#comment-16712936 ] Dmitriy Pavlov commented on IGNITE-10599: - [~ilyak], could you please fill ticket description? well described issue has higher chance to find its contributor > Add test for Scheduler Example test to LGPL Examples suite > -- > > Key: IGNITE-10599 > URL: https://issues.apache.org/jira/browse/IGNITE-10599 > Project: Ignite > Issue Type: Test >Reporter: Ilya Kasnacheev >Priority: Major > Labels: test > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10461) MVCC: Create "PDS 1" test suite for MVCC mode.
[
https://issues.apache.org/jira/browse/IGNITE-10461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712932#comment-16712932
]
Ignite TC Bot commented on IGNITE-10461:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hibernate 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2480519]]
* HibernateL2CacheTransactionalSelfTest.testRegionClear (last started)
{color:#d04437}Hibernate 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2480520]]
* HibernateL2CacheTransactionalUseSyncSelfTest.testNaturalIdCache (last started)
{color:#d04437}Cache 6{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2481594]]
* IgniteCacheTestSuite6: TxStateChangeEventTest.testRemote - 0,0% fails in last
100 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2480602buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Create "PDS 1" test suite for MVCC mode.
> --
>
> Key: IGNITE-10461
> URL: https://issues.apache.org/jira/browse/IGNITE-10461
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.8
>
>
> Create MVCC version of IgnitePdsTestSuite and add it to TC.
> All non-relevant tests should be marked as ignored.
> Failed tests should be muted and tickets should be created for unknown
> failure reasons.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10599) Add test for Scheduler Example test to LGPL Examples suite
Ilya Kasnacheev created IGNITE-10599: Summary: Add test for Scheduler Example test to LGPL Examples suite Key: IGNITE-10599 URL: https://issues.apache.org/jira/browse/IGNITE-10599 Project: Ignite Issue Type: Test Reporter: Ilya Kasnacheev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10595) Introduce RPM / DEB release build
[ https://issues.apache.org/jira/browse/IGNITE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-10595: -- Description: Add [new|https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteRelease_Run_ApacheIgnitePostRelease_BuildUploadRpmDebPackages] build in [Apache Ignite Release|https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8=projectOverview] project for building and uploading RPM / DEB packages based on Release build artifacts. (was: Add new build in [Apache Ignite Release|https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8=projectOverview] project for building and uploading RPM / DEB packages based on Release build artifacts.) > Introduce RPM / DEB release build > - > > Key: IGNITE-10595 > URL: https://issues.apache.org/jira/browse/IGNITE-10595 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.8 > > > Add > [new|https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteRelease_Run_ApacheIgnitePostRelease_BuildUploadRpmDebPackages] > build in [Apache Ignite > Release|https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8=projectOverview] > project for building and uploading RPM / DEB packages based on Release build > artifacts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10462) MVCC: Create "PDS 2" test suite for MVCC mode.
[
https://issues.apache.org/jira/browse/IGNITE-10462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712920#comment-16712920
]
Roman Kondakov commented on IGNITE-10462:
-
[~amashenkov], there is a couple comments concerning this patch:
1. I guess a {{TRANSACTIONAL}} mode should be checked in this test by default:
{{IgniteWalReaderTest#testRemoveOperationPresentedForDataEntry}}
2. There is no MVCC cache is started during these tests. I think
{{setAtomicityMode(TRANSACTIONAL)}} should be set explicitly in the cache
configuration to check both MVCC and non-MVCC cases.
* {{IgnitePdsPartitionFilesDestroyTest}}
* {{IgniteNodeStoppedDuringDisableWALTest}}
* {{IgnitePdsPartitionsStateRecoveryTest}}
* {{IgnitePdsRebalancingOnNotStableTopologyTest}}
* {{IgnitePdsWholeClusterRestartTest}}
* {{IgniteRebalanceScheduleResendPartitionsTest}}
* {{LocalWacModeNoChangeDuringRebalanceOnNonNodeAssignTest}} - there is also a
misprint here. I guess it should be LocalWal... here.
* {{LocalWalModeChangeDuringRebalancingSelfTest}}
* {{SlowHistoricalRebalanceSmallHistoryTest}}
* {{WalDeletionArchiveFsyncTest}}
* {{WalDeletionArchiveLogOnlyTest}}
3. Empty lines before and after {{break}} statement in
{{IgniteWalReaderTest.java:1360}}
> MVCC: Create "PDS 2" test suite for MVCC mode.
> --
>
> Key: IGNITE-10462
> URL: https://issues.apache.org/jira/browse/IGNITE-10462
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.8
>
>
> Create MVCC version of IgnitePdsTestSuite2 and add it to TC.
> All non-relevant tests should be marked as ignored.
> Failed tests should be muted and tickets should be created for unknown
> failure reasons.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9211) Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite
[
https://issues.apache.org/jira/browse/IGNITE-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev reassigned IGNITE-9211:
---
Assignee: Ilya Kasnacheev
> Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite
> --
>
> Key: IGNITE-9211
> URL: https://issues.apache.org/jira/browse/IGNITE-9211
> Project: Ignite
> Issue Type: Sub-task
> Components: examples
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> {code}
> //suite.addTest(new TestSuite(ContinuationExamplesSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesSelfTest.class));
> //suite.addTest(new TestSuite(DeploymentExamplesSelfTest.class));
> //suite.addTest(new TestSuite(LifecycleExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MemcacheRestExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MonteCarloExamplesSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesSelfTest.class));
> //suite.addTest(new TestSuite(SpringBeanExamplesSelfTest.class));
> //suite.addTest(new TestSuite(IgfsExamplesSelfTest.class));
> //suite.addTest(new TestSuite(CheckpointExamplesSelfTest.class));
> //suite.addTest(new TestSuite(HibernateL2CacheExampleSelfTest.class));
> //suite.addTest(new TestSuite(ClusterGroupExampleSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuationExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(DeploymentExamplesMultiNodeSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MemcacheRestExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MonteCarloExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(HibernateL2CacheExampleMultiNodeSelfTest.class));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10225) Striped pool starvation check reports false-positive warnings if a job starts right before the check
[ https://issues.apache.org/jira/browse/IGNITE-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712910#comment-16712910 ] ASF GitHub Bot commented on IGNITE-10225: - GitHub user DirectXceriD opened a pull request: https://github.com/apache/ignite/pull/5606 IGNITE-10225 fix starvation check You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10225 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5606.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 #5606 commit ec869715a4d3521715ac08d1112ba5e61e325098 Author: Vladimir Pligin Date: 2018-12-07T14:07:45Z IGNITE-10225 add new system property > Striped pool starvation check reports false-positive warnings if a job starts > right before the check > > > Key: IGNITE-10225 > URL: https://issues.apache.org/jira/browse/IGNITE-10225 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Assignee: Vladimir Pligin >Priority: Major > Labels: newbie > Attachments: StripedExecutorTest.java > > > StripedExecutor::checkStarvation checks if two conditions are met: a stripe > is executing a job and the stripe's job counter hasn't changed since the last > check. > These conditions will be met if no jobs have been executed for a long time > and a job (even a very short one) has just started. > This check isn't supposed to be exact and allowed to produce false-positives. > However, the check is supposed to detect jobs running for more than > starvation check interval (IGNITE_STARVATION_CHECK_INTERVAL), but in this > case it may detect even very short ones. > To fix this we may require a stripe to have no progress in two consecutive > checks - then we will have much less chance for a false-positive, but still > detect hanging or very long jobs. -- 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=16712909#comment-16712909 ] ASF GitHub Bot commented on IGNITE-10594: - GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/5605 IGNITE-10594 Remove modules/indexing/src/java8, add test to regular suite. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10594 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5605.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 #5605 commit 2b83081eab6e01c376304ea30b14aaab0a817634 Author: Ilya Kasnacheev Date: 2018-12-07T14:16:40Z IGNITE-10594 Remove modules/indexing/src/java8, add test to regular suite. > 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] [Assigned] (IGNITE-9303) PageSnapshot can contain wrong pageId tag when not dirty page is recycling
[
https://issues.apache.org/jira/browse/IGNITE-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rakov reassigned IGNITE-9303:
--
Assignee: Ilya Lantukh (was: Ivan Rakov)
> PageSnapshot can contain wrong pageId tag when not dirty page is recycling
> --
>
> Key: IGNITE-9303
> URL: https://issues.apache.org/jira/browse/IGNITE-9303
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Aleksey Plekhanov
>Assignee: Ilya Lantukh
>Priority: Major
> Fix For: 2.8
>
>
> When page is recycling (for example in {{BPlusTree.Remove#freePage()}} ->
> {{DataStructure#recyclePage()}}) tag of {{pageId}} is modified, but original
> {{pageId}} is passed to {{writeUnlock()}} method and this passed {{pageId}}
> is stored to PageSnapshot WAL record.
> This bug may lead to errors in WAL applying during crash recovery.
> Reproducer (ignite-indexing module must be in classpath):
> {code:java}
> public class WalFailReproducer extends AbstractWalDeltaConsistencyTest {
> @Override protected boolean checkPagesOnCheckpoint() {
> return true;
> }
> public final void testPutRemoveCacheDestroy() throws Exception {
> CacheConfiguration ccfg = new
> CacheConfiguration<>("cache0");
> ccfg.setIndexedTypes(Integer.class, Integer.class);
> IgniteEx ignite = startGrid(0);
> ignite.cluster().active(true);
> IgniteCache cache0 = ignite.getOrCreateCache(ccfg);
> for (int i = 0; i < 5_000; i++)
> cache0.put(i, i);
> forceCheckpoint();
> for (int i = 1_000; i < 4_000; i++)
> cache0.remove(i);
> forceCheckpoint();
> stopAllGrids();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9303) PageSnapshot can contain wrong pageId tag when not dirty page is recycling
[
https://issues.apache.org/jira/browse/IGNITE-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rakov reassigned IGNITE-9303:
--
Assignee: Ivan Rakov (was: Ilya Lantukh)
> PageSnapshot can contain wrong pageId tag when not dirty page is recycling
> --
>
> Key: IGNITE-9303
> URL: https://issues.apache.org/jira/browse/IGNITE-9303
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Aleksey Plekhanov
>Assignee: Ivan Rakov
>Priority: Major
> Fix For: 2.8
>
>
> When page is recycling (for example in {{BPlusTree.Remove#freePage()}} ->
> {{DataStructure#recyclePage()}}) tag of {{pageId}} is modified, but original
> {{pageId}} is passed to {{writeUnlock()}} method and this passed {{pageId}}
> is stored to PageSnapshot WAL record.
> This bug may lead to errors in WAL applying during crash recovery.
> Reproducer (ignite-indexing module must be in classpath):
> {code:java}
> public class WalFailReproducer extends AbstractWalDeltaConsistencyTest {
> @Override protected boolean checkPagesOnCheckpoint() {
> return true;
> }
> public final void testPutRemoveCacheDestroy() throws Exception {
> CacheConfiguration ccfg = new
> CacheConfiguration<>("cache0");
> ccfg.setIndexedTypes(Integer.class, Integer.class);
> IgniteEx ignite = startGrid(0);
> ignite.cluster().active(true);
> IgniteCache cache0 = ignite.getOrCreateCache(ccfg);
> for (int i = 0; i < 5_000; i++)
> cache0.put(i, i);
> forceCheckpoint();
> for (int i = 1_000; i < 4_000; i++)
> cache0.remove(i);
> forceCheckpoint();
> stopAllGrids();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10598) H2 ConnectionManager drop ThreadLocal logic
Taras Ledkov created IGNITE-10598: - Summary: H2 ConnectionManager drop ThreadLocal logic Key: IGNITE-10598 URL: https://issues.apache.org/jira/browse/IGNITE-10598 Project: Ignite Issue Type: Task Components: sql Affects Versions: 2.7 Reporter: Taras Ledkov Assignee: Taras Ledkov Looks like we have to change H2 connection management after the patch IGNITE-9171 is applied. Caching H2 connection in ThreadLocal doesn't make sense because connections are shared between thread in fact. Drop ThreadLocal connection cache simplifies connection management. We haven't check thread state to close connection. The solution needs in good performance analysis & benchmark to be sure that contention on concurrent collection of H2 connections doesn't affect query performance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10459) MVCC: Create "Cache (Failover) 2" test suite for MVCC mode.
[ https://issues.apache.org/jira/browse/IGNITE-10459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712888#comment-16712888 ] ASF GitHub Bot commented on IGNITE-10459: - GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/5604 IGNITE-10459: Created Mvcc Failover TestSuite 2. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10459 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5604.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 #5604 commit 9885f6034df09b8d692d0ddd37ca5f95f4158312 Author: Andrey V. Mashenkov Date: 2018-12-07T13:56:55Z IGNITE-10459: Created Mvcc Failover TestSuite 2. > MVCC: Create "Cache (Failover) 2" test suite for MVCC mode. > --- > > Key: IGNITE-10459 > URL: https://issues.apache.org/jira/browse/IGNITE-10459 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.8 > > > Create MVCC version of IgniteCacheFailoverTestSuite2 and add it to TC. > All non-relevant tests should be marked as ignored. > Failed tests should be muted and tickets should be created for unknown > failure reasons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10597) MVCC TX: Organize used thread pools
Igor Seliverstov created IGNITE-10597: - Summary: MVCC TX: Organize used thread pools Key: IGNITE-10597 URL: https://issues.apache.org/jira/browse/IGNITE-10597 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Igor Seliverstov Fix For: 2.8 All mvcc operations use cache pool, this means striped pool is used under hood that may lead performance issues in case of long operations (like query update). we need: 1) use query pool for query updates 2) use random stripe for batched updates 3) use appropriate stripe for single updates. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8527) Show actual rebalance starting in logs
[
https://issues.apache.org/jira/browse/IGNITE-8527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko resolved IGNITE-8527.
-
Resolution: Won't Fix
Fixed by https://issues.apache.org/jira/browse/IGNITE-9649
> Show actual rebalance starting in logs
> --
>
> Key: IGNITE-8527
> URL: https://issues.apache.org/jira/browse/IGNITE-8527
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Trivial
> Fix For: 2.8
>
>
> We should increase level of logging from DEBUG to INFO for message:
> {noformat}
> if (log.isDebugEnabled())
> log.debug("Requested rebalancing [from node="
> + node.id() + ", listener index=" + topicId + " " + demandMsg.rebalanceId() +
> ", partitions count=" + stripePartitions.get(topicId).size() + " (" +
> stripePartitions.get(topicId).partitionsList() + ")]");
> {noformat}
> to have actual rebalancing start time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-8782) Wrong message may be printed during simultaneous deactivation and rebalance
[ https://issues.apache.org/jira/browse/IGNITE-8782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko resolved IGNITE-8782. - Resolution: Won't Fix Fixed by https://issues.apache.org/jira/browse/IGNITE-10242 > Wrong message may be printed during simultaneous deactivation and rebalance > --- > > Key: IGNITE-8782 > URL: https://issues.apache.org/jira/browse/IGNITE-8782 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Kovalenko >Priority: Minor > Fix For: 2.8 > > > A message located at: GridCachePartitionExchangeManager.java:394 may be > printed out if cache group doesn't exist while rebalance process is still > finishing. This may happen after deactivation during rebalance. > We should put this logging under if (grp != null) block and print other > message if cache group was actually stopped. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10596) Introduce Docker images release build
Peter Ivanov created IGNITE-10596: - Summary: Introduce Docker images release build Key: IGNITE-10596 URL: https://issues.apache.org/jira/browse/IGNITE-10596 Project: Ignite Issue Type: Improvement Reporter: Peter Ivanov Assignee: Peter Ivanov Fix For: 2.8 Add new build in [Apache Ignite Release|https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8=projectOverview] project for building and uploading Docker images based on Release build artifacts. -- 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
]
Oleg Ignatenko updated IGNITE-10177:
Description:
If needed, refer parent task for more details.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
# review and if possible upgade all occurrences of {{import org.junit}} in the
project
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.
was:
If needed, refer parent task for more details.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
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.
> 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
>Priority: Major
>
> If needed, refer parent task for more details.
> # remove deprecated API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven
> # migrate tests that were missed at prior steps, if there are any
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}}
> to add the class via Junit4 adapter
> # find and update all Junit3-specific code that {{extends TestCase}}
> # untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> # review and if possible upgade all occurrences of {{import org.junit}} in
> the project
> 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] [Created] (IGNITE-10595) Introduce RPM / DEB Release build
Peter Ivanov created IGNITE-10595: - Summary: Introduce RPM / DEB Release build Key: IGNITE-10595 URL: https://issues.apache.org/jira/browse/IGNITE-10595 Project: Ignite Issue Type: Improvement Reporter: Peter Ivanov Assignee: Peter Ivanov Fix For: 2.8 Add new build in [Apache Ignite Release|https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8=projectOverview] project for building and uploading RPM / DEB packages based on Release build artifacts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10589) Multiple server node failure after a client node stopping
[
https://issues.apache.org/jira/browse/IGNITE-10589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Lantukh reassigned IGNITE-10589:
-
Assignee: Ilya Lantukh
> Multiple server node failure after a client node stopping
> -
>
> Key: IGNITE-10589
> URL: https://issues.apache.org/jira/browse/IGNITE-10589
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Kosarev
>Assignee: Ilya Lantukh
>Priority: Critical
> Attachments: 16_02.tar
>
>
> after stopping a client
> we see topology change and pme finish on the coordinator,
> and at soon on another nodes we still don't see new topology, but have
> Critical error resulting nodes failure
> crd log
> {code}
> 2018-12-06 15:55:23.660 [WARN
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Node FAILED: ZookeeperClusterNode [id=979f03db-f858-44f6-8646-12034dfd5c93,
> addrs=[10.116.206.1], order=129, loc=false, client=true]
> 2018-12-06 15:55:23.660 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Topology snapshot [ver=162, servers=128, clients=0, CPUs=7168,
> offheap=14.0GB, heap=4000.0GB]
> 2018-12-06 15:55:23.660 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- Node [id=44D27930-80E5-4EB7-B377-8B07C02C2033, clusterState=ACTIVE]
> 2018-12-06 15:55:23.660 [INFO
> ][zk-DPL_GRID%DplGridNodeName-EventThread][o.a.i.s.d.z.i.ZookeeperDiscoveryImpl]
> Process alive nodes change [alives=128]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- Baseline [id=0, size=128, online=128, offline=0]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
> Data Regions Configured:
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- dpl_mem_plc [initSize=256.0 MiB, maxSize=556.6 GiB,
> persistenceEnabled=true]
> 2018-12-06 15:55:23.661 [INFO
> ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager]
>^-- not-persisted [initSize=256.0 MiB, maxSize=556.6 GiB,
> persistenceEnabled=false]
> 2018-12-06 15:55:23.670
> [DEBUG][sys-#564%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.l.ExchangeLatchManager]
> Process node left 979f03db-f858-44f6-8646-12034dfd5c93
> 2018-12-06 15:55:23.670 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time]
> Started exchange init [topVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], crd=true, evt=NODE_FAILED,
> evtNode=979f03db-f858-44f6-8646-12034dfd5c93, customEvt=null, allowMerge=true]
> 2018-12-06 15:55:23.712 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time]
> Finished exchange init [topVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], crd=true]
> 2018-12-06 15:55:23.699 [INFO
> ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture]
> Finish exchange future [startVer=AffinityTopologyVersion [topVer=162,
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=162, minorTopVer=0],
> err=null]
> {code}
> on a node(1) we have critical error(1)
> {code}
> 2018-12-06 15:55:23.727
> [ERROR][utility-#432%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed processing message [senderId=1e17c56a-5213-4a1b-b94b-4575a95a2c81,
> msg=GridDhtTxPrepareRequest [nearNodeId=44d27930-80e5-4eb7-b377-8b07c02c2033,
> futId=1d225238761-05eea259-5c25-4a4b-8469-9dd8980e218c, miniId=105,
> topVer=AffinityTopologyVersion [topVer=162, minorTopVer=0],
> invalidateNearEntries={}, nearWrites=null, owned=null,
> nearXidVer=GridCacheVersion [topVer=155571374, order=1545423626166, nodeOrd
> er=1], subjId=44d27930-80e5-4eb7-b377-8b07c02c2033, taskNameHash=0,
> preloadKeys=null, skipCompletedVers=false,
> super=GridDistributedTxPrepareRequest [threadId=1281,
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, writeVer=GridCacheVersion
> [topVer=15557137
> 4, order=1545423626614, nodeOrder=96], timeout=0, reads=null,
> writes=ArrayList [IgniteTxEntry [key=KeyCacheObjectImpl [part=65,
> val=GridServiceAssignmentsKey [name=DPLThreadManager_service],
> hasValBytes=true], cacheId=-2100569601, txKey=IgniteTxKey [key=KeyCa
> cheObjectImpl [part=65, val=GridServiceAssignmentsKey
> [name=DPLThreadManager_service], hasValBytes=true], cacheId=-2100569601],
> val=CacheObjectImpl [val=GridServiceAssignments
> [nodeId=426a4a51-1af3-4019-9769-4a58d8ece426, topVer=162,
> cfg=LazyServiceConfigurat
> ion [srvcClsName=com.sbt.dpl.gridgain.thread.DPLThreadManager, svcCls=,
>
[jira] [Created] (IGNITE-10594) Remove 'java 8' source in indexing module, add test to regular suite
Ilya Kasnacheev created IGNITE-10594: Summary: 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 CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest to be precise -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9184) Cluster hangs during concurrent node restart and continues query registration
[
https://issues.apache.org/jira/browse/IGNITE-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712867#comment-16712867
]
Stanilovsky Evgeny commented on IGNITE-9184:
Guys, i suppose problem is here:
{code:java}
for (CacheEntryEvent e : evts) {
for (CacheEntryEvent event : evts) {
{code}
i run this code (with commented first *for* line) 10 mins and have no problems
here.
[~mcherkasov] check it ones more plz?
> Cluster hangs during concurrent node restart and continues query registration
> -
>
> Key: IGNITE-9184
> URL: https://issues.apache.org/jira/browse/IGNITE-9184
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.6
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>Priority: Blocker
> Fix For: 2.8
>
> Attachments: StressTest.java, logs, stacktrace
>
>
> Please check the attached test case and stack trace.
> I can see: "Failed to wait for initial partition map exchange" message.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9303) PageSnapshot can contain wrong pageId tag when not dirty page is recycling
[
https://issues.apache.org/jira/browse/IGNITE-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712865#comment-16712865
]
Aleksey Plekhanov commented on IGNITE-9303:
---
[~ilantukh], if we don't check WAL record pageId tag in tracker anymore, we
also can do some cleanup and delete code, which was written to check this tag:
{code:java}
// Set new fullPageId after recycle or after new page init, because pageId tag
is changed.
if (record instanceof RecycleRecord)
page.fullPageId(new FullPageId(((RecycleRecord)record).newPageId(), grpId));
else if (record instanceof InitNewPageRecord)
page.fullPageId(new FullPageId(((InitNewPageRecord)record).newPageId(),
grpId));
{code}
and:
{code:java}
page.fullPageId(fullPageId);
{code}
In {{applyWalRecord}} method.
> PageSnapshot can contain wrong pageId tag when not dirty page is recycling
> --
>
> Key: IGNITE-9303
> URL: https://issues.apache.org/jira/browse/IGNITE-9303
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Aleksey Plekhanov
>Assignee: Ilya Lantukh
>Priority: Major
> Fix For: 2.8
>
>
> When page is recycling (for example in {{BPlusTree.Remove#freePage()}} ->
> {{DataStructure#recyclePage()}}) tag of {{pageId}} is modified, but original
> {{pageId}} is passed to {{writeUnlock()}} method and this passed {{pageId}}
> is stored to PageSnapshot WAL record.
> This bug may lead to errors in WAL applying during crash recovery.
> Reproducer (ignite-indexing module must be in classpath):
> {code:java}
> public class WalFailReproducer extends AbstractWalDeltaConsistencyTest {
> @Override protected boolean checkPagesOnCheckpoint() {
> return true;
> }
> public final void testPutRemoveCacheDestroy() throws Exception {
> CacheConfiguration ccfg = new
> CacheConfiguration<>("cache0");
> ccfg.setIndexedTypes(Integer.class, Integer.class);
> IgniteEx ignite = startGrid(0);
> ignite.cluster().active(true);
> IgniteCache cache0 = ignite.getOrCreateCache(ccfg);
> for (int i = 0; i < 5_000; i++)
> cache0.put(i, i);
> forceCheckpoint();
> for (int i = 1_000; i < 4_000; i++)
> cache0.remove(i);
> forceCheckpoint();
> stopAllGrids();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9211) Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite
[
https://issues.apache.org/jira/browse/IGNITE-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712861#comment-16712861
]
Ilya Kasnacheev edited comment on IGNITE-9211 at 12/7/18 1:32 PM:
--
Looks like we're removing this suite entirely since we're always on Java 8 and
later.
All of the tests are already included in other suites.
was (Author: ilyak):
Looks like we're removing this suite entirely since we're always on Java 8 and
later.
> Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite
> --
>
> Key: IGNITE-9211
> URL: https://issues.apache.org/jira/browse/IGNITE-9211
> Project: Ignite
> Issue Type: Sub-task
> Components: examples
>Reporter: Ilya Kasnacheev
>Priority: Major
>
> {code}
> //suite.addTest(new TestSuite(ContinuationExamplesSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesSelfTest.class));
> //suite.addTest(new TestSuite(DeploymentExamplesSelfTest.class));
> //suite.addTest(new TestSuite(LifecycleExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MemcacheRestExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MonteCarloExamplesSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesSelfTest.class));
> //suite.addTest(new TestSuite(SpringBeanExamplesSelfTest.class));
> //suite.addTest(new TestSuite(IgfsExamplesSelfTest.class));
> //suite.addTest(new TestSuite(CheckpointExamplesSelfTest.class));
> //suite.addTest(new TestSuite(HibernateL2CacheExampleSelfTest.class));
> //suite.addTest(new TestSuite(ClusterGroupExampleSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuationExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(DeploymentExamplesMultiNodeSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MemcacheRestExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MonteCarloExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(HibernateL2CacheExampleMultiNodeSelfTest.class));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9211) Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite
[
https://issues.apache.org/jira/browse/IGNITE-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712861#comment-16712861
]
Ilya Kasnacheev commented on IGNITE-9211:
-
Looks like we're removing this suite entirely since we're always on Java 8 and
later.
> Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite
> --
>
> Key: IGNITE-9211
> URL: https://issues.apache.org/jira/browse/IGNITE-9211
> Project: Ignite
> Issue Type: Sub-task
> Components: examples
>Reporter: Ilya Kasnacheev
>Priority: Major
>
> {code}
> //suite.addTest(new TestSuite(ContinuationExamplesSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesSelfTest.class));
> //suite.addTest(new TestSuite(DeploymentExamplesSelfTest.class));
> //suite.addTest(new TestSuite(LifecycleExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MemcacheRestExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MonteCarloExamplesSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesSelfTest.class));
> //suite.addTest(new TestSuite(SpringBeanExamplesSelfTest.class));
> //suite.addTest(new TestSuite(IgfsExamplesSelfTest.class));
> //suite.addTest(new TestSuite(CheckpointExamplesSelfTest.class));
> //suite.addTest(new TestSuite(HibernateL2CacheExampleSelfTest.class));
> //suite.addTest(new TestSuite(ClusterGroupExampleSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuationExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(DeploymentExamplesMultiNodeSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MemcacheRestExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MonteCarloExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(HibernateL2CacheExampleMultiNodeSelfTest.class));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9211) Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite
[
https://issues.apache.org/jira/browse/IGNITE-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-9211:
Ignite Flags: (was: Docs Required)
> Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite
> --
>
> Key: IGNITE-9211
> URL: https://issues.apache.org/jira/browse/IGNITE-9211
> Project: Ignite
> Issue Type: Sub-task
> Components: examples
>Reporter: Ilya Kasnacheev
>Priority: Major
>
> {code}
> //suite.addTest(new TestSuite(ContinuationExamplesSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesSelfTest.class));
> //suite.addTest(new TestSuite(DeploymentExamplesSelfTest.class));
> //suite.addTest(new TestSuite(LifecycleExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MemcacheRestExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MonteCarloExamplesSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesSelfTest.class));
> //suite.addTest(new TestSuite(SpringBeanExamplesSelfTest.class));
> //suite.addTest(new TestSuite(IgfsExamplesSelfTest.class));
> //suite.addTest(new TestSuite(CheckpointExamplesSelfTest.class));
> //suite.addTest(new TestSuite(HibernateL2CacheExampleSelfTest.class));
> //suite.addTest(new TestSuite(ClusterGroupExampleSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuationExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(DeploymentExamplesMultiNodeSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MemcacheRestExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MonteCarloExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(HibernateL2CacheExampleMultiNodeSelfTest.class));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10459) MVCC: Create "Cache (Failover) 2" test suite for MVCC mode.
[ https://issues.apache.org/jira/browse/IGNITE-10459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov reassigned IGNITE-10459: - Assignee: Andrew Mashenkov > MVCC: Create "Cache (Failover) 2" test suite for MVCC mode. > --- > > Key: IGNITE-10459 > URL: https://issues.apache.org/jira/browse/IGNITE-10459 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.8 > > > Create MVCC version of IgniteCacheFailoverTestSuite2 and add it to TC. > All non-relevant tests should be marked as ignored. > Failed tests should be muted and tickets should be created for unknown > failure reasons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10300) control.sh: incorrect error message after three tries on unsuccessful authorization.
[
https://issues.apache.org/jira/browse/IGNITE-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712856#comment-16712856
]
Sergey Chugunov commented on IGNITE-10300:
--
[~voropava],
I left some comments in PR, could you please take a look?
> control.sh: incorrect error message after three tries on unsuccessful
> authorization.
>
>
> Key: IGNITE-10300
> URL: https://issues.apache.org/jira/browse/IGNITE-10300
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Voronkin
>Assignee: Pavel Voronkin
>Priority: Major
>
> 1. start grid with securirty enabled
> 2. try to issue control.sh --cache
> authentication credentials asked
> 3. enter incorrect credentials three times
> expected: Authentication error printed and logged
> actual: Latest topology update failed error printed
> {noformat}
> IGNITE_HOME=`pwd` bin/control.sh --cache list .
> Control utility [ver. 2.5.1-p160#20181113-sha1:5f845ca7]
> 2018 Copyright(C) Apache Software Foundation
> User: mshonichev
>
> Authentication error, try connection again.
> user:
> password:
> Authentication error, try connection again.
> user:
> password:
> Authentication error, try connection again.
> user:
> password:
> Authentication error.
> Error: Latest topology update failed.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9211) Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite
[
https://issues.apache.org/jira/browse/IGNITE-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712851#comment-16712851
]
ASF GitHub Bot commented on IGNITE-9211:
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/5603
IGNITE-9211 Remove Java 8 examples suite since we always run on Java 8+.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9211
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5603.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 #5603
commit c449d19acb9d022a32d1d6da384134d5c24138be
Author: Ilya Kasnacheev
Date: 2018-12-07T13:21:40Z
IGNITE-9211 Remove Java 8 examples suite since we always run on Java 8+.
> Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite
> --
>
> Key: IGNITE-9211
> URL: https://issues.apache.org/jira/browse/IGNITE-9211
> Project: Ignite
> Issue Type: Sub-task
> Components: examples
>Reporter: Ilya Kasnacheev
>Priority: Major
>
> {code}
> //suite.addTest(new TestSuite(ContinuationExamplesSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesSelfTest.class));
> //suite.addTest(new TestSuite(DeploymentExamplesSelfTest.class));
> //suite.addTest(new TestSuite(LifecycleExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MemcacheRestExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MonteCarloExamplesSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesSelfTest.class));
> //suite.addTest(new TestSuite(SpringBeanExamplesSelfTest.class));
> //suite.addTest(new TestSuite(IgfsExamplesSelfTest.class));
> //suite.addTest(new TestSuite(CheckpointExamplesSelfTest.class));
> //suite.addTest(new TestSuite(HibernateL2CacheExampleSelfTest.class));
> //suite.addTest(new TestSuite(ClusterGroupExampleSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuationExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(DeploymentExamplesMultiNodeSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MemcacheRestExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MonteCarloExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(HibernateL2CacheExampleMultiNodeSelfTest.class));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10593) Proper NoOpHandler injection
Ryabov Dmitrii created IGNITE-10593: --- Summary: Proper NoOpHandler injection Key: IGNITE-10593 URL: https://issues.apache.org/jira/browse/IGNITE-10593 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Fix For: 2.8 Improve no-op failure handler usage by replacing copy-pasted code by extending from class with changed default handler as recommended in [discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Default-failure-handler-was-changed-for-tests-tp38900p39010.html]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10459) MVCC: Create "Cache (Failover) 2" test suite for MVCC mode.
[ https://issues.apache.org/jira/browse/IGNITE-10459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-10459: -- Fix Version/s: 2.8 > MVCC: Create "Cache (Failover) 2" test suite for MVCC mode. > --- > > Key: IGNITE-10459 > URL: https://issues.apache.org/jira/browse/IGNITE-10459 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.8 > > > Create MVCC version of IgniteCacheFailoverTestSuite2 and add it to TC. > All non-relevant tests should be marked as ignored. > Failed tests should be muted and tickets should be created for unknown > failure reasons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10458) MVCC: Create "Cache (Failover) 1" test suite for MVCC mode.
[ https://issues.apache.org/jira/browse/IGNITE-10458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712842#comment-16712842 ] ASF GitHub Bot commented on IGNITE-10458: - GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/5602 IGNITE-10458: Created Mvcc Failover TestSuite 1. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10458 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5602.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 #5602 commit cf3b1214d7d3a6bc9bef644c1ae960febeed1b4e Author: Andrey V. Mashenkov Date: 2018-12-07T13:16:26Z IGNITE-10458: Created Mvcc Failover TestSuite 1. > MVCC: Create "Cache (Failover) 1" test suite for MVCC mode. > --- > > Key: IGNITE-10458 > URL: https://issues.apache.org/jira/browse/IGNITE-10458 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.8 > > > Create MVCC version of IgniteCacheFailoverTestSuite and add it to TC. > All non-relevant tests should be marked as ignored. > Failed tests should be muted and tickets should be created for unknown > failure reasons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10203) [TC Bot] Support for alternative configurations for PR testing
[ https://issues.apache.org/jira/browse/IGNITE-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-10203. - Resolution: Fixed Merged to master, and V181207 contains an additional fix for links in JIRA comments. [~zzzadruga] thank you for contribution > [TC Bot] Support for alternative configurations for PR testing > -- > > Key: IGNITE-10203 > URL: https://issues.apache.org/jira/browse/IGNITE-10203 > Project: Ignite > Issue Type: Task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Major > > Support for alternative configurations for PR testing (for example, > IgniteTests24Java8_RunMl) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[
https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712828#comment-16712828
]
ASF GitHub Bot commented on IGNITE-10454:
-
dspavlov commented on a change in pull request #89: IGNITE-10454 Create page
with muted tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239799469
##
File path:
ignite-tc-helper-web/src/test/java/org/apache/ignite/ci/di/scheduler/DirectExecNoWaitScheduler.java
##
@@ -21,7 +21,7 @@
/**
* Sheduler which never waits
*/
-public class DirectExecNoWaitSheduler implements IScheduler {
+public class DirectExecNoWaitScheduler implements IScheduler {
Review comment:
Always feel free to create a separate small PRs for such changes (srvNme,
misprints, etc). It is easier to accept such small changes without relation to
a big feature. Big feature change can be rejected, but small and needed changes
will wait. With a separate PRs is it easy to accept separately
A)refactoring/improving/misprints corrections and B) big feature.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Create page with muted tests
> -
>
> Key: IGNITE-10454
> URL: https://issues.apache.org/jira/browse/IGNITE-10454
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> We need a page with muted tests. On this page we should have possibility to
> filter tests by fail reason (fail with ticket link or not) and fail rate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10366) MVCC: Create "Cache 1" test suite for MVCC mode.
[ https://issues.apache.org/jira/browse/IGNITE-10366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712832#comment-16712832 ] Roman Kondakov commented on IGNITE-10366: - [~amashenkov], [~gvvinblade], patch looks good for me. Can be merged to master. > MVCC: Create "Cache 1" test suite for MVCC mode. > > > Key: IGNITE-10366 > URL: https://issues.apache.org/jira/browse/IGNITE-10366 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.8 > > > Create MVCC version of IgniteCacheTestSuite and add it to TC. > All non-relevant tests should be marked as ignored. > Failed tests should be muted and tickets should be created for unknown > failure reasons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10203) [TC Bot] Support for alternative configurations for PR testing
[ https://issues.apache.org/jira/browse/IGNITE-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10203: Ignite Flags: (was: Docs Required) > [TC Bot] Support for alternative configurations for PR testing > -- > > Key: IGNITE-10203 > URL: https://issues.apache.org/jira/browse/IGNITE-10203 > Project: Ignite > Issue Type: Task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Major > > Support for alternative configurations for PR testing (for example, > IgniteTests24Java8_RunMl) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[ https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712825#comment-16712825 ] ASF GitHub Bot commented on IGNITE-10454: - dspavlov commented on a change in pull request #89: IGNITE-10454 Create page with muted tests URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239798869 ## File path: ignite-tc-helper-web/src/main/webapp/mutes.html ## @@ -0,0 +1,224 @@ + + + + +Apache Ignite Teamcity Bot - Muted tests + +https://code.jquery.com/jquery-1.12.4.js";> +https://code.jquery.com/ui/1.12.1/jquery-ui.js";> + +https://code.jquery.com/ui/1.12.1/themes/base/jquery-ui.css;> + +https://cdn.datatables.net/1.10.16/js/jquery.dataTables.js";> +https://cdn.datatables.net/1.10.16/js/dataTables.jqueryui.js";> +https://code.jquery.com/ui/1.12.1/themes/base/jquery-ui.css;> +https://cdn.datatables.net/1.10.16/css/jquery.dataTables.min.css;> +
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[
https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712807#comment-16712807
]
ASF GitHub Bot commented on IGNITE-10454:
-
dspavlov commented on a change in pull request #89: IGNITE-10454 Create page
with muted tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239795515
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/mute/MuteScope.java
##
@@ -0,0 +1,65 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.mute;
+
+import java.util.List;
+import javax.xml.bind.annotation.XmlAccessType;
+import javax.xml.bind.annotation.XmlAccessorType;
+import javax.xml.bind.annotation.XmlElement;
+import javax.xml.bind.annotation.XmlElementWrapper;
+import org.apache.ignite.ci.tcmodel.conf.BuildType;
+import org.apache.ignite.ci.tcmodel.conf.Project;
+
+/**
+ *
+ */
+@XmlAccessorType(XmlAccessType.FIELD)
+public class MuteScope {
+/** Project. */
+@XmlElement public Project project;
+
+/** Build types. */
+@XmlElementWrapper(name = "buildTypes")
+@XmlElement(name = "buildType")
+public List buildTypes;
+
+/** {@inheritDoc} */
+@Override public boolean equals(Object o) {
Review comment:
Do we really need to compare XML models? If so I suggest to use Objects &
generated code
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Create page with muted tests
> -
>
> Key: IGNITE-10454
> URL: https://issues.apache.org/jira/browse/IGNITE-10454
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> We need a page with muted tests. On this page we should have possibility to
> filter tests by fail reason (fail with ticket link or not) and fail rate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10458) MVCC: Create "Cache (Failover) 1" test suite for MVCC mode.
[ https://issues.apache.org/jira/browse/IGNITE-10458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-10458: -- Fix Version/s: 2.8 > MVCC: Create "Cache (Failover) 1" test suite for MVCC mode. > --- > > Key: IGNITE-10458 > URL: https://issues.apache.org/jira/browse/IGNITE-10458 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.8 > > > Create MVCC version of IgniteCacheFailoverTestSuite and add it to TC. > All non-relevant tests should be marked as ignored. > Failed tests should be muted and tickets should be created for unknown > failure reasons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[
https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712824#comment-16712824
]
ASF GitHub Bot commented on IGNITE-10454:
-
dspavlov commented on a change in pull request #89: IGNITE-10454 Create page
with muted tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239798519
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/tracked/GetTrackedBranchTestResults.java
##
@@ -140,4 +145,31 @@ public TestFailuresSummary
getAllTestFailsNoCache(@Nullable @QueryParam("branch"
return tbProc.getTrackedBranchTestFailures(branchOpt, checkAllLogs,
cntLimit, creds);
}
+
+/**
+ * @param srvId Server id.
+ * @param projectId Project id.
+ * @return Mutes for given server-project pair.
+ */
+@GET
+@Path("mutes")
+public Set mutes(
+@Nullable @QueryParam("serverId") String srvId,
+@Nullable @QueryParam("projectId") String projectId
+) {
+ICredentialsProv creds = ICredentialsProv.get(req);
+
+if (F.isEmpty(srvId))
+srvId = "apache";
+
+if (F.isEmpty(projectId))
+projectId = "IgniteTests24Java8";
Review comment:
Probably we can create method returning default suite for a server.
Something similar to recently merged #90 and getContributionStatus() - contains
iteration on tracked branches. We can extract it as a separate method. This
change we can do in a standalone PR, but anyway, please consider it as well.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Create page with muted tests
> -
>
> Key: IGNITE-10454
> URL: https://issues.apache.org/jira/browse/IGNITE-10454
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> We need a page with muted tests. On this page we should have possibility to
> filter tests by fail reason (fail with ticket link or not) and fail rate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[
https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712821#comment-16712821
]
ASF GitHub Bot commented on IGNITE-10454:
-
dspavlov commented on a change in pull request #89: IGNITE-10454 Create page
with muted tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239798051
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/tracked/GetTrackedBranchTestResults.java
##
@@ -140,4 +145,31 @@ public TestFailuresSummary
getAllTestFailsNoCache(@Nullable @QueryParam("branch"
return tbProc.getTrackedBranchTestFailures(branchOpt, checkAllLogs,
cntLimit, creds);
}
+
+/**
+ * @param srvId Server id.
+ * @param projectId Project id.
+ * @return Mutes for given server-project pair.
+ */
+@GET
+@Path("mutes")
+public Set mutes(
+@Nullable @QueryParam("serverId") String srvId,
+@Nullable @QueryParam("projectId") String projectId
+) {
+ICredentialsProv creds = ICredentialsProv.get(req);
+
+if (F.isEmpty(srvId))
+srvId = "apache";
Review comment:
Avoid hardcoding. At least use constants - we have method retuning default
server ID.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Create page with muted tests
> -
>
> Key: IGNITE-10454
> URL: https://issues.apache.org/jira/browse/IGNITE-10454
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> We need a page with muted tests. On this page we should have possibility to
> filter tests by fail reason (fail with ticket link or not) and fail rate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[ https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712816#comment-16712816 ] ASF GitHub Bot commented on IGNITE-10454: - dspavlov commented on a change in pull request #89: IGNITE-10454 Create page with muted tests URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239796897 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/mute/MuteInfoCompacted.java ## @@ -0,0 +1,154 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +package org.apache.ignite.ci.tcmodel.mute; Review comment: Please place compacted objects related to Ignite storage to package org.apache.ignite.ci.teamcity.ignited.mute but not in package with TC XML models This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [TC Bot] Create page with muted tests > - > > Key: IGNITE-10454 > URL: https://issues.apache.org/jira/browse/IGNITE-10454 > Project: Ignite > Issue Type: Task >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Major > > We need a page with muted tests. On this page we should have possibility to > filter tests by fail reason (fail with ticket link or not) and fail rate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[
https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712814#comment-16712814
]
ASF GitHub Bot commented on IGNITE-10454:
-
dspavlov commented on a change in pull request #89: IGNITE-10454 Create page
with muted tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239796518
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/TeamcityIgnitedImpl.java
##
@@ -550,8 +581,51 @@ private void sheduleResyncBuildRefs() {
*
*/
void fullReindex() {
-buildRefSync.runActualizeBuildRefs(srvNme, true, null, conn);
+buildRefSync.runActualizeBuildRefs(srvName, true, null, conn);
}
+/**
+ * Refresh mutes for given project.
+ *
+ * @param projectId Project id.
+ * @return Message with loading result.
+ */
+protected String actualizeMuteRefs(String projectId) {
Review comment:
I suggest moving this actualization outside of TC Ignited class to avoid
creating a god object in future. We can name it MuteSync or something like that.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Create page with muted tests
> -
>
> Key: IGNITE-10454
> URL: https://issues.apache.org/jira/browse/IGNITE-10454
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> We need a page with muted tests. On this page we should have possibility to
> filter tests by fail reason (fail with ticket link or not) and fail rate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[
https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712805#comment-16712805
]
ASF GitHub Bot commented on IGNITE-10454:
-
dspavlov commented on a change in pull request #89: IGNITE-10454 Create page
with muted tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239795307
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/mute/MuteInfoCompacted.java
##
@@ -0,0 +1,154 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.mute;
+
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.List;
+import org.apache.ignite.ci.tcmodel.result.tests.TestRef;
+import org.apache.ignite.ci.teamcity.ignited.IStringCompactor;
+import org.apache.ignite.internal.util.typedef.F;
+
+/**
+ * @see MuteInfo
+ */
+public class MuteInfoCompacted {
+/** Mute id. */
+int id;
+
+/** Assignment. Mute date. */
+int muteDate;
+
+/** Assignment. Text. */
+int text;
+
+/** Scope. */
+MuteScopeCompacted scope;
+
+/** Target. Test ids. */
+long[] testIds;
+
+/** Target. Test names. */
+int[] testNames;
+
+/** Target. Test hrefs. */
+int[] testHrefs;
+
+/**
+ * @param mute Mute to compact.
+ * @param comp Compactor.
+ */
+MuteInfoCompacted(MuteInfo mute, IStringCompactor comp) {
+id = mute.id;
+
+muteDate = comp.getStringId(mute.assignment.muteDate);
+text = comp.getStringId(mute.assignment.text);
+
+scope = new MuteScopeCompacted(mute.scope, comp);
+
+List tests = mute.target.tests;
+
+if (F.isEmpty(tests))
+return;
+
+testIds = new long[tests.size()];
+testNames = new int[tests.size()];
+testHrefs = new int[tests.size()];
+
+for (int i = 0; i < tests.size(); i++) {
+TestRef test = tests.get(i);
+
+testIds[i] = Long.valueOf(test.id);
+testNames[i] = comp.getStringId(test.name);
+testHrefs[i] = comp.getStringId(test.href);
Review comment:
Can we generate href during uncompression of entity? Probably concatenating
ITeamcityConn.host()+"tests" +testId
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Create page with muted tests
> -
>
> Key: IGNITE-10454
> URL: https://issues.apache.org/jira/browse/IGNITE-10454
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> We need a page with muted tests. On this page we should have possibility to
> filter tests by fail reason (fail with ticket link or not) and fail rate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10592) [ML] DatasetTrainer#update should be thought over.
Artem Malykh created IGNITE-10592: - Summary: [ML] DatasetTrainer#update should be thought over. Key: IGNITE-10592 URL: https://issues.apache.org/jira/browse/IGNITE-10592 Project: Ignite Issue Type: Improvement Components: ml Reporter: Artem Malykh DatasetTrainer#update was designed to contain skeleton for updating models, whereas concrete behaviour of update is implemented in subclasses by overriding this skeletons protected components, namely DatasetTrainer#checkState and DatasetTrainer#updateModel. We have a problem here: if we retain skeleton method, then it should be final. But making it final will cut the possibility to write wrappers around some given DatasetTrainer, because in that case we will not be able to implement Wrapper#checkState and Wrapper#updateModel by delegation to wrapped object (this methods have protected access). We need wrappers for stacking and for bagging for example. Now in wrappers we have ability to 1. Override skeleton method, but (maybe) it seems not very clean solution, since it is no more skeleton method and we loose guarantees that checkState and updateModel will be used at all; 2. place wrapper in the same package as DatasetTrainer, but this forces not-so-good classes structure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[
https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712800#comment-16712800
]
ASF GitHub Bot commented on IGNITE-10454:
-
dspavlov commented on a change in pull request #89: IGNITE-10454 Create page
with muted tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239794609
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/mute/MuteInfoCompacted.java
##
@@ -0,0 +1,154 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.mute;
+
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.List;
+import org.apache.ignite.ci.tcmodel.result.tests.TestRef;
+import org.apache.ignite.ci.teamcity.ignited.IStringCompactor;
+import org.apache.ignite.internal.util.typedef.F;
+
+/**
+ * @see MuteInfo
+ */
+public class MuteInfoCompacted {
+/** Mute id. */
+int id;
+
+/** Assignment. Mute date. */
+int muteDate;
+
+/** Assignment. Text. */
+int text;
+
+/** Scope. */
+MuteScopeCompacted scope;
+
+/** Target. Test ids. */
+long[] testIds;
+
+/** Target. Test names. */
+int[] testNames;
+
+/** Target. Test hrefs. */
+int[] testHrefs;
+
+/**
+ * @param mute Mute to compact.
+ * @param comp Compactor.
+ */
+MuteInfoCompacted(MuteInfo mute, IStringCompactor comp) {
+id = mute.id;
+
+muteDate = comp.getStringId(mute.assignment.muteDate);
Review comment:
leak of strings ID allocation is possible with each mute
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Create page with muted tests
> -
>
> Key: IGNITE-10454
> URL: https://issues.apache.org/jira/browse/IGNITE-10454
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> We need a page with muted tests. On this page we should have possibility to
> filter tests by fail reason (fail with ticket link or not) and fail rate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[
https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712797#comment-16712797
]
ASF GitHub Bot commented on IGNITE-10454:
-
dspavlov commented on a change in pull request #89: IGNITE-10454 Create page
with muted tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239794453
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/mute/MuteInfo.java
##
@@ -0,0 +1,74 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.mute;
+
+import javax.xml.bind.annotation.XmlAccessType;
+import javax.xml.bind.annotation.XmlAccessorType;
+import javax.xml.bind.annotation.XmlAttribute;
+import javax.xml.bind.annotation.XmlElement;
+import javax.xml.bind.annotation.XmlRootElement;
+
+/**
+ *
+ */
+@XmlRootElement(name = "mute")
+@XmlAccessorType(XmlAccessType.FIELD)
+public class MuteInfo {
+/** Id. */
+@XmlAttribute public int id;
+
+/** Assignment. */
+@XmlElement public MuteAssignment assignment;
+
+/** Scope. */
+@XmlElement public MuteScope scope;
+
+/** Target. */
+@XmlElement public MuteTarget target;
+
+/** {@inheritDoc} */
+@Override public boolean equals(Object o) {
+if (this == o)
+return true;
+
+if (o == null || getClass() != o.getClass())
+return false;
+
+MuteInfo info = (MuteInfo)o;
+
+if (id != info.id)
+return false;
+
+if (assignment != null ? !assignment.equals(info.assignment) :
info.assignment != null)
+return false;
+
+if (scope != null ? !scope.equals(info.scope) : info.scope != null)
+return false;
+
+return target != null ? target.equals(info.target) : info.target ==
null;
+}
+
+/** {@inheritDoc} */
+@Override public int hashCode() {
Review comment:
I suggest using autogen hashcode:
@Override public int hashCode() {
return Objects.hashCode(login, avatarUrl);
}
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Create page with muted tests
> -
>
> Key: IGNITE-10454
> URL: https://issues.apache.org/jira/browse/IGNITE-10454
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> We need a page with muted tests. On this page we should have possibility to
> filter tests by fail reason (fail with ticket link or not) and fail rate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10454) [TC Bot] Create page with muted tests
[
https://issues.apache.org/jira/browse/IGNITE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712793#comment-16712793
]
ASF GitHub Bot commented on IGNITE-10454:
-
dspavlov commented on a change in pull request #89: IGNITE-10454 Create page
with muted tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/89#discussion_r239794124
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/mute/MuteInfoCompacted.java
##
@@ -0,0 +1,154 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.mute;
+
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.List;
+import org.apache.ignite.ci.tcmodel.result.tests.TestRef;
+import org.apache.ignite.ci.teamcity.ignited.IStringCompactor;
+import org.apache.ignite.internal.util.typedef.F;
+
+/**
+ * @see MuteInfo
+ */
+public class MuteInfoCompacted {
+/** Mute id. */
+int id;
+
+/** Assignment. Mute date. */
+int muteDate;
Review comment:
I suggest to use long with parsed timestamp
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC Bot] Create page with muted tests
> -
>
> Key: IGNITE-10454
> URL: https://issues.apache.org/jira/browse/IGNITE-10454
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> We need a page with muted tests. On this page we should have possibility to
> filter tests by fail reason (fail with ticket link or not) and fail rate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10434) MVCC: Transaction asynchronous rollback bug.
[
https://issues.apache.org/jira/browse/IGNITE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712787#comment-16712787
]
Igor Seliverstov commented on IGNITE-10434:
---
[~vozerov], please look at. Inspections are fixed;
MarshallerContextLockingSelfTest is very rare flaky.
> MVCC: Transaction asynchronous rollback bug.
>
>
> Key: IGNITE-10434
> URL: https://issues.apache.org/jira/browse/IGNITE-10434
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
>
> There is some bug in mvcc tx asynchronous rollback flow. Sometimes
> transaction is not rolled back completely: Remote transactions remain alive
> while Near and Dht transactions are terminated locally and on MVCC
> coordinator.
> Reproducer: {{MvccTxRollbackAsyncTest#testMixedAsyncRollbackTypes}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10458) MVCC: Create "Cache (Failover) 1" test suite for MVCC mode.
[ https://issues.apache.org/jira/browse/IGNITE-10458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov reassigned IGNITE-10458: - Assignee: Andrew Mashenkov > MVCC: Create "Cache (Failover) 1" test suite for MVCC mode. > --- > > Key: IGNITE-10458 > URL: https://issues.apache.org/jira/browse/IGNITE-10458 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.8 > > > Create MVCC version of IgniteCacheFailoverTestSuite and add it to TC. > All non-relevant tests should be marked as ignored. > Failed tests should be muted and tickets should be created for unknown > failure reasons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712781#comment-16712781
]
PetrovMikhail commented on IGNITE-10243:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2262947]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 31
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 31 master runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 31
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 31 master runs.
{color:#d04437}SPI{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2262949]]
* IgniteSpiTestSuite: TcpDiscoverySslTrustedSelfTest.testFailedNodes3 - 3,1%
fails in last 32 master runs.
{color:#d04437}Hadoop{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2255238]]
* IgniteHadoopTestSuite: HadoopSplitWrapperSelfTest.testSerialization - 0,0%
fails in last 28 master runs.
* IgniteHadoopTestSuite: HadoopTasksV1Test.testReduceTask - 0,0% fails in last
28 master runs.
* IgniteHadoopTestSuite: HadoopTaskExecutionSelfTest.testJobKill - 0,0% fails
in last 28 master runs.
* IgniteHadoopTestSuite: HadoopV2JobSelfTest.testCustomSerializationApplying -
0,0% fails in last 28 master runs.
* IgniteHadoopTestSuite:
HadoopSerializationWrapperSelfTest.testIntJavaSerialization - 0,0% fails in
last 28 master runs.
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2253721]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoverySpiTest.testReconnectDisabled_ConnectionLost - 3,0% fails in
last 33 master runs.
{color:#d04437}Platform .NET (Core Linux){color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2262951]]
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 31
master runs.
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 31
master runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in
last 31 master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 31 master runs.
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2253771]]
* IgnitePdsTestSuite:
BPlusTreeReuseListPageMemoryImplTest.testMassiveRemove2_false - 0,0% fails in
last 31 master runs.
{color:#d04437}Java Client{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2253701]]
* IgniteClientTestSuite:
ClientTcpConnectivitySelfTest.testRefreshTopologyOnNodeLeft - 0,0% fails in
last 30 master runs.
{color:#d04437}PDS 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2253772]]
* IgnitePdsTestSuite2:
WalCompactionTest.testCompressorToleratesEmptyWalSegmentsLogOnly - 0,0% fails
in last 29 master runs.
{color:#d04437}Platform C++ (Linux Clang){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2253730]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2
{color:#d04437}Platform C++ (Windows x64){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2253724]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2
{color:#d04437}Platform C++ (Linux){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2253723]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2
{color:#d04437}Inspections: Core{color} [[tests 0 BuildFailureOnMetric
|https://ci.ignite.apache.org/viewLog.html?buildId=2262952]]
{color:#d04437}Thin client: Python{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2262954]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2253787buildTypeId=IgniteTests24Java8_RunAll]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
[jira] [Commented] (IGNITE-9455) Total allocated size memory metric is always zero for metastore data region.
[ https://issues.apache.org/jira/browse/IGNITE-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712779#comment-16712779 ] Pavel Pereslegin commented on IGNITE-9455: -- [~alex_pl] thank you for the review. > Total allocated size memory metric is always zero for metastore data region. > > > Key: IGNITE-9455 > URL: https://issues.apache.org/jira/browse/IGNITE-9455 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Fix For: 2.8 > > Attachments: Reproducer.java > > > Persistence enabled and metrics for all regions enabled, but total allocated > size is always zero for metastore data region > Even if we change NO_OP allocated page tracker to a real page tracker in > CacheStoreHolder this metric counts incorrectly, because this region is > recreated, > Reproducer attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7993) Striped pool can't be disabled
[
https://issues.apache.org/jira/browse/IGNITE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712774#comment-16712774
]
Ilya Kasnacheev commented on IGNITE-7993:
-
[~guseinov] thank you for the contribution!
> Striped pool can't be disabled
> --
>
> Key: IGNITE-7993
> URL: https://issues.apache.org/jira/browse/IGNITE-7993
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.8
>
>
> Javadoc for {{IgniteConfiguration#setStripedPoolSize}} states that striped
> pool can be disabled by providing value less or equal than zero:
> {noformat}
> If set to non-positive value then requests get processed in system pool.
> {noformat}
> However, doing that prevents node from startup, it fails with the following
> exception:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid
> stripedPool thread pool size (must be greater than 0), actual value: 0
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.validateThreadPoolSize(IgnitionEx.java:2061)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:664)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9455) Total allocated size memory metric is always zero for metastore data region.
[ https://issues.apache.org/jira/browse/IGNITE-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712773#comment-16712773 ] ASF GitHub Bot commented on IGNITE-9455: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5195 > Total allocated size memory metric is always zero for metastore data region. > > > Key: IGNITE-9455 > URL: https://issues.apache.org/jira/browse/IGNITE-9455 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Fix For: 2.8 > > Attachments: Reproducer.java > > > Persistence enabled and metrics for all regions enabled, but total allocated > size is always zero for metastore data region > Even if we change NO_OP allocated page tracker to a real page tracker in > CacheStoreHolder this metric counts incorrectly, because this region is > recreated, > Reproducer attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10463) MVCC: Create "PDS 3" test suite for MVCC mode.
[ https://issues.apache.org/jira/browse/IGNITE-10463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712772#comment-16712772 ] Andrew Mashenkov commented on IGNITE-10463: --- [~rkondakov], There are 2 trivial styles issues, I've left comments to the PR. Please, fix them and merge the PR. > MVCC: Create "PDS 3" test suite for MVCC mode. > -- > > Key: IGNITE-10463 > URL: https://issues.apache.org/jira/browse/IGNITE-10463 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Roman Kondakov >Priority: Major > > Create MVCC version of IgnitePdsTestSuite3 and add it to TC. > All non-relevant tests should be marked as ignored. > Failed tests should be muted and tickets should be created for unknown > failure reasons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10591) MVCC: Incorrect data region metrics.
Andrew Mashenkov created IGNITE-10591:
-
Summary: MVCC: Incorrect data region metrics.
Key: IGNITE-10591
URL: https://issues.apache.org/jira/browse/IGNITE-10591
Project: Ignite
Issue Type: Bug
Components: mvcc, persistence
Reporter: Andrew Mashenkov
IgnitePdsDataRegionMetricsTest.testMemoryUsageSingleNode failed.
{noformat}
junit.framework.AssertionFailedError: Number of allocated pages is different
than in metrics for [node=db.IgnitePdsDataRegionMetricsTest0, cache=default]
expected:<13542> but was:<13881>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:159)
at junit.framework.TestCase.assertEquals(TestCase.java:316)
at
org.apache.ignite.internal.processors.cache.persistence.db.IgnitePdsDataRegionMetricsTest.checkMetricsConsistency(IgnitePdsDataRegionMetricsTest.java:337)
at
org.apache.ignite.internal.processors.cache.persistence.db.IgnitePdsDataRegionMetricsTest.testMemoryUsageSingleNode(IgnitePdsDataRegionMetricsTest.java:155){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10203) [TC Bot] Support for alternative configurations for PR testing
[
https://issues.apache.org/jira/browse/IGNITE-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712771#comment-16712771
]
ASF GitHub Bot commented on IGNITE-10203:
-
asfgit closed pull request #90: IGNITE-10203 Fix TC Bot visa on Jira
URL: https://github.com/apache/ignite-teamcity-bot/pull/90
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java
index eb66f302..3ec28401 100644
--- a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java
+++ b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java
@@ -208,7 +208,8 @@ private BranchesTracked getTrackedBranches() {
* @param webUrl Build URL.
* @return Comment, which should be sent to the JIRA ticket.
*/
-private String generateJiraComment(List suites, String
webUrl, String buildTypeId, ITeamcityIgnited tcIgnited) {
+private String generateJiraComment(List suites, String
webUrl, String buildTypeId,
+ITeamcityIgnited tcIgnited) {
BuildTypeRefCompacted bt = tcIgnited.getBuildTypeRef(buildTypeId);
String suiteName = (bt != null ? bt.name(compactor) : buildTypeId);
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildObserver.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildObserver.java
index 98287d2e..bee40967 100644
---
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildObserver.java
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildObserver.java
@@ -85,8 +85,9 @@ public boolean stopObservation(ContributionKey key) {
* @param branchForTc Branch for TC.
* @param ticket JIRA ticket name.
*/
-public void observe(String srvId, ICredentialsProv prov, String ticket,
String branchForTc, Build... builds) {
-BuildsInfo buildsInfo = new BuildsInfo(srvId, prov, ticket,
branchForTc, builds);
+public void observe(String srvId, ICredentialsProv prov, String ticket,
String branchForTc, String parentSuiteId,
+Build... builds) {
+BuildsInfo buildsInfo = new BuildsInfo(srvId, prov, ticket,
branchForTc, parentSuiteId, builds);
observerTask.addInfo(buildsInfo);
}
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
index 40e33011..bfb70e76 100644
---
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
@@ -17,6 +17,7 @@
package org.apache.ignite.ci.observer;
+import com.google.common.base.Strings;
import java.util.ArrayList;
import java.util.Calendar;
import java.util.Collections;
@@ -81,13 +82,15 @@ public BuildsInfo(CompactBuildsInfo compactBuildsInfo,
IStringCompactor strCompa
* @param ticket Ticket.
* @param builds Builds.
*/
-public BuildsInfo(String srvId, ICredentialsProv prov, String ticket,
String branchForTc, Build... builds) {
+public BuildsInfo(String srvId, ICredentialsProv prov, String ticket,
String branchForTc, String parentSuiteId,
+Build... builds) {
this.userName = prov.getUser(srvId);
this.date = Calendar.getInstance().getTime();
this.srvId = srvId;
this.ticket = ticket;
this.branchForTc = branchForTc;
-this.buildTypeId = builds.length == 1 ? builds[0].buildTypeId :
"IgniteTests24Java8_RunAll";
+this.buildTypeId = Strings.isNullOrEmpty(parentSuiteId) ?
+(builds.length == 1 ? builds[0].buildTypeId :
"IgniteTests24Java8_RunAll") : parentSuiteId;
for (Build build : builds)
this.builds.add(build.getId());
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/visa/TcBotTriggerAndSignOffService.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/visa/TcBotTriggerAndSignOffService.java
index bbec0a30..910079f9 100644
---
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/visa/TcBotTriggerAndSignOffService.java
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/visa/TcBotTriggerAndSignOffService.java
@@ -32,8 +32,10 @@
import javax.annotation.Nonnull;
import javax.inject.Inject;
import javax.ws.rs.QueryParam;
+import org.apache.ignite.ci.HelperConfig;
import org.apache.ignite.ci.ITcHelper;
import org.apache.ignite.ci.IAnalyticsEnabledTeamcity;
+import org.apache.ignite.ci.ITeamcity;
import
[jira] [Commented] (IGNITE-9455) Total allocated size memory metric is always zero for metastore data region.
[ https://issues.apache.org/jira/browse/IGNITE-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712769#comment-16712769 ] Aleksey Plekhanov commented on IGNITE-9455: --- [~xtern], merged to master, thank you for the contribution. > Total allocated size memory metric is always zero for metastore data region. > > > Key: IGNITE-9455 > URL: https://issues.apache.org/jira/browse/IGNITE-9455 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Fix For: 2.8 > > Attachments: Reproducer.java > > > Persistence enabled and metrics for all regions enabled, but total allocated > size is always zero for metastore data region > Even if we change NO_OP allocated page tracker to a real page tracker in > CacheStoreHolder this metric counts incorrectly, because this region is > recreated, > Reproducer attached. -- 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
]
Oleg Ignatenko updated IGNITE-10177:
Description:
If needed, refer parent task for more details.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
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.
was:
If needed, refer parent task for more details.
1) remove deprecated API of GridAbstractTest and its subclasses 2) remove
dependencies from Junit 3 in Maven 3) migrate tests that were missed at prior
steps, if there are any 4) remove redundant references to {{JUnit4.class}} if
there are any (like in {{@RunWith(JUnit4.class)}}) 5) in tests suite classes,
change {{extends TestSuite}} to either {{@RunWith(AllTests.class)}} or
{{@Suite.SuiteClasses}} 6) check and adjust if needed methods like
{{GridTestUtils.addTestIfNeeded}} to add the class via Junit4 adapter 7) find
and update all Junit3-specific code that {{extends TestCase}}
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.
> 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
>Priority: Major
>
> If needed, refer parent task for more details.
> # remove deprecated API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven
> # migrate tests that were missed at prior steps, if there are any
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}}
> to add the class via Junit4 adapter
> # find and update all Junit3-specific code that {{extends TestCase}}
> # untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> 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-4380) Cache invoke calls can be lost
[
https://issues.apache.org/jira/browse/IGNITE-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-4380:
Fix Version/s: 2.8
> Cache invoke calls can be lost
> --
>
> Key: IGNITE-4380
> URL: https://issues.apache.org/jira/browse/IGNITE-4380
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Semen Boikov
>Assignee: Amelchev Nikita
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> * Recently added test
> GridCacheAbstractFullApiSelfTest.testInvokeAllMultithreaded fails on TC in
> various configurations with transactional cache.
> Example of failure
> GridCacheReplicatedOffHeapTieredMultiNodeFullApiSelfTest.testInvokeAllMultithreaded:
> {noformat}
> junit.framework.AssertionFailedError: expected:<2> but was:<10868>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testInvokeAllMultithreaded(GridCacheAbstractFullApiSelfTest.java:342)
> at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1803)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1718)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-79) Illegal state exception in affinity assignment cache
[
https://issues.apache.org/jira/browse/IGNITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanilovsky Evgeny resolved IGNITE-79.
--
Resolution: Not A Problem
> Illegal state exception in affinity assignment cache
>
>
> Key: IGNITE-79
> URL: https://issues.apache.org/jira/browse/IGNITE-79
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Yakov Zhdanov
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
> Attachments: GridServiceProcessorMultiNodeConfigSelfTest#testAll.log
>
>
> {noformat}
> java.lang.IllegalStateException: Getting affinity for topology version
> earlier than affinity is calculated
> [locNodeId=41caf5c2-3827-4566-9e52-22dabf51f864, topVer=179, head=180]
> at
> org.gridgain.grid.kernal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:328)
> ~[gridgain-core-6.2.1-p1.jar:na]
> at
> org.gridgain.grid.kernal.processors.affinity.GridAffinityAssignmentCache.primaryPartitions(GridAffinityAssignmentCache.java:294)
> ~[gridgain-core-6.2.1-p1.jar:na]
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheAffinityManager.primaryPartitions(GridCacheAffinityManager.java:349)
> ~[gridgain-core-6.2.1-p1.jar:na]
> at
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:478)
> ~[gridgain-core-6.2.1-p1.jar:na]
> at
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandPool$ExchangeWorker.body(GridDhtPartitionDemandPool.java:1285)
> ~[gridgain-core-6.2.1-p1.jar:na]
> at org.gridgain.grid.util.worker.GridWorker.run(GridWorker.java:151)
> ~[gridgain-core-6.2.1-p1.jar:na]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_55]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
