[jira] [Created] (IGNITE-11508) Yarn Ignite deployment: Add support to over ride queue name through cluster properties
ARAVINDA REDDY N created IGNITE-11508:
-
Summary: Yarn Ignite deployment: Add support to over ride queue
name through cluster properties
Key: IGNITE-11508
URL: https://issues.apache.org/jira/browse/IGNITE-11508
Project: Ignite
Issue Type: Improvement
Components: yarn
Affects Versions: 2.7
Reporter: ARAVINDA REDDY N
Yarn ignite 2.7.0 doesn't have the facility to provide queue name through the
cluster.properties. When i checked the IgniteYarnClient source code by default
it is set to "default".
// Finally, set-up ApplicationSubmissionContext for the application
ApplicationSubmissionContext appContext =
app.getApplicationSubmissionContext();
appContext.setApplicationName("ignition"); // application name
appContext.setAMContainerSpec(amContainer);
appContext.setResource(capability);
appContext.setQueue("default"); // queue
It would be a great support if we can allow overriding it through cluster
properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11438) TTL manager may not clear entries from the underlying CacheDataStore
[
https://issues.apache.org/jira/browse/IGNITE-11438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787176#comment-16787176
]
Ignite TC Bot commented on IGNITE-11438:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3256822&buildTypeId=IgniteTests24Java8_RunAll]
> TTL manager may not clear entries from the underlying CacheDataStore
>
>
> Key: IGNITE-11438
> URL: https://issues.apache.org/jira/browse/IGNITE-11438
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
>
> Please see the attached test:
> {code:java}
> /*
> * 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.internal.processors.cache.persistence.db;
> import java.util.TreeMap;
> import java.util.concurrent.TimeUnit;
> import javax.cache.expiry.AccessedExpiryPolicy;
> import javax.cache.expiry.CreatedExpiryPolicy;
> import javax.cache.expiry.Duration;
> import javax.cache.expiry.ExpiryPolicy;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.IgniteCheckedException;
> import org.apache.ignite.cache.CachePeekMode;
> import org.apache.ignite.cache.CacheRebalanceMode;
> import org.apache.ignite.cache.CacheWriteSynchronizationMode;
> import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.DataRegionConfiguration;
> import org.apache.ignite.configuration.DataStorageConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.WALMode;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.internal.IgniteInterruptedCheckedException;
> import org.apache.ignite.internal.processors.cache.GridCacheContext;
> import org.apache.ignite.internal.processors.cache.GridCacheSharedContext;
> import org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager;
> import org.apache.ignite.internal.processors.cache.IgniteCacheProxy;
> import
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition;
> import org.apache.ignite.internal.util.lang.GridAbsPredicate;
> import org.apache.ignite.internal.util.lang.GridCursor;
> import org.apache.ignite.internal.util.typedef.PA;
> import org.apache.ignite.internal.util.typedef.internal.CU;
> import org.apache.ignite.testframework.GridTestUtils;
> import org.apache.ignite.testframework.MvccFeatureChecker;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.junit.Test;
> import static
> org.apache.ignite.IgniteSystemProperties.IGNITE_BASELINE_AUTO_ADJUST_ENABLED;
> /**
> * Test TTL worker with persistence enabled
> */
> public class IgnitePdsWithTtlTest extends GridCommonAbstractTest {
> /** */
> public static final String CACHE_NAME = "expirableCache";
> /** */
> public static final String GROUP_NAME = "group1";
> /** */
> public static final int PART_SIZE = 32;
> /** */
> private static final int EXPIRATION_TIMEOUT = 10;
> /** */
> public static final int ENTRIES = 100_000;
> /** {@inheritDoc} */
> @Override protected void beforeTestsStarted() throws Exception {
> System.setProperty(IGNITE_BASELINE_AUTO_ADJUST_ENABLED, "false");
> super.beforeTestsStarted();
> }
> /** {@inheritDoc} */
> @Override protected void afterTestsStopped() throws Exception {
> super.afterTestsStopped();
> System.clearProperty(IGNITE_BASELINE_AUTO_ADJUST_ENABLED);
> }
> /** {@inheritDoc} */
> @Override protected void beforeTest() throws Exception {
>
> MvccFeatureChecker.skipIfNotSupported(MvccFeatureChecker.Feature.EXPIRATION);
> super.b
[jira] [Updated] (IGNITE-11299) During SSL Handshake GridNioServer.processWrite is invoked constantly
[ https://issues.apache.org/jira/browse/IGNITE-11299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11299: Priority: Blocker (was: Major) > During SSL Handshake GridNioServer.processWrite is invoked constantly > - > > Key: IGNITE-11299 > URL: https://issues.apache.org/jira/browse/IGNITE-11299 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Blocker > Labels: ssl > Fix For: 2.8 > > Time Spent: 40m > Remaining Estimate: 0h > > Causes busy looping in processSelectionKeyOptimized() > This also causes problems on Windows/Java 11 since if key is always ready for > writing it will never be shown as ready for reading. > The reason for this behavior that during handshake we never un-listen OP_WRITE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11299) During SSL Handshake GridNioServer.processWrite is invoked constantly
[ https://issues.apache.org/jira/browse/IGNITE-11299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11299: Fix Version/s: 2.8 > During SSL Handshake GridNioServer.processWrite is invoked constantly > - > > Key: IGNITE-11299 > URL: https://issues.apache.org/jira/browse/IGNITE-11299 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: ssl > Fix For: 2.8 > > Time Spent: 40m > Remaining Estimate: 0h > > Causes busy looping in processSelectionKeyOptimized() > This also causes problems on Windows/Java 11 since if key is always ready for > writing it will never be shown as ready for reading. > The reason for this behavior that during handshake we never un-listen OP_WRITE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11507) SQL: Ensure that affinity topology version doesn't change during PartitionResult construction/application.
Alexander Lapin created IGNITE-11507: Summary: SQL: Ensure that affinity topology version doesn't change during PartitionResult construction/application. Key: IGNITE-11507 URL: https://issues.apache.org/jira/browse/IGNITE-11507 Project: Ignite Issue Type: Improvement Components: sql Reporter: Alexander Lapin Fix For: 2.8 Currently some actions might be performed (for example cache removal) during PartitionResult construction, so it might become invalid. Besides that it's not possible to associate PartitionResult with affinity topology version, so it is impossible to guarantee that the partition result is used on the same version on which it was built. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10261) MVCC: cache operation may hang during late affinity assignment.
[
https://issues.apache.org/jira/browse/IGNITE-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786953#comment-16786953
]
Ignite TC Bot commented on IGNITE-10261:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3194790&buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: cache operation may hang during late affinity assignment.
> ---
>
> Key: IGNITE-10261
> URL: https://issues.apache.org/jira/browse/IGNITE-10261
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Andrew Mashenkov
>Assignee: Roman Kondakov
>Priority: Critical
> Labels: failover, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> ForceKey response processing fails with ClassCastException with Mvcc mode
> that causes test hanging.
> Issue can be easily reproduced with backups > 0 and disabled rebalance. See
> GridCacheDhtPreloadPutGetSelfTest.testPutGetNone1().
> Also CacheLateAffinityAssignmentTest.testRandomOperations() hangs sometimes
> due to same reason.
>
> {noformat}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry
> cannot be cast to
> org.apache.ignite.internal.processors.cache.mvcc.MvccVersionAware
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture$MiniFuture.onResult(GridDhtForceKeysFuture.java:545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onResult(GridDhtForceKeysFuture.java:202)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processForceKeyResponse(GridDhtCacheAdapter.java:180)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$11.onMessage(GridDhtTransactionalCacheAdapter.java:208)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$11.onMessage(GridDhtTransactionalCacheAdapter.java:206)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$MessageHandler.apply(GridDhtCacheAdapter.java:1434)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$MessageHandler.apply(GridDhtCacheAdapter.java:1416)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10768) MVCC: CacheMvccBasicContinuousQueryTest.testUpdateCountersGapClosedSimplePartitioned may hang
[
https://issues.apache.org/jira/browse/IGNITE-10768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786952#comment-16786952
]
Roman Kondakov commented on IGNITE-10768:
-
[~amashenkov], please review the patch. Tests are ok.
The reason of the test blinking is the race when {{TestDiscoverySpi}} should
swallow prepare messages from the first transaction, but sometimes it swallows
several prepare messages from the first transaction and at least one prepare
message issued by the second transaction. In this case second transaction hangs
and tests fails. The fix is to wait for all prepare messages from the first tx
is arrived and then start the second one.
> MVCC:
> CacheMvccBasicContinuousQueryTest.testUpdateCountersGapClosedSimplePartitioned
> may hang
> -
>
> Key: IGNITE-10768
> URL: https://issues.apache.org/jira/browse/IGNITE-10768
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: CQ, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Test
> {{CacheMvccBasicContinuousQueryTest.testUpdateCountersGapClosedSimplePartitioned}}
> may hang sometimes.
>
> {noformat}
> Thread [name="test-runner-#209301%mvcc.CacheMvccBasicContinuousQueryTest%",
> id=228123, state=WAITING, blockCnt=5, waitCnt=89]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:179)
> at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:142)
> at
> o.a.i.i.processors.cache.mvcc.CacheMvccBasicContinuousQueryTest.checkUpdateCountersGapIsProcessedSimple(CacheMvccBasicContinuousQueryTest.java:346)
> at
> o.a.i.i.processors.cache.mvcc.CacheMvccBasicContinuousQueryTest.testUpdateCountersGapClosedSimplePartitioned(CacheMvccBasicContinuousQueryTest.java:257)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at
> o.a.i.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2121)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11079) MVCC: IgniteCacheContinuousQueryBackupQueueTest is flacky.
[
https://issues.apache.org/jira/browse/IGNITE-11079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786965#comment-16786965
]
Roman Kondakov commented on IGNITE-11079:
-
Dedicated TC run for this test:
[https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccQueries&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=pull%2F6249%2Fhead|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccQueries&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=pull%2F6249%2Fhead]
> MVCC: IgniteCacheContinuousQueryBackupQueueTest is flacky.
> --
>
> Key: IGNITE-11079
> URL: https://issues.apache.org/jira/browse/IGNITE-11079
> Project: Ignite
> Issue Type: Test
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: MakeTeamcityGreenAgain, mvcc_stabilization_stage_1
> Time Spent: 10m
> Remaining Estimate: 0h
>
> See Tc run
>
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=925274886589214180&tab=testDetails]
> Test fails after series of long JVM pauses with stacktrace:
> {code:java}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertTrue(Assert.java:31)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryBackupQueueTest.testManyQueryBackupQueue(IgniteCacheContinuousQueryBackupQueueTest.java:175)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
> at java.lang.Thread.run(Thread.java:748){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10261) MVCC: cache operation may hang during late affinity assignment.
[
https://issues.apache.org/jira/browse/IGNITE-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786956#comment-16786956
]
Roman Kondakov commented on IGNITE-10261:
-
[~amashenkov], I've fixed the issues we've discussed. Please, take a look.
Tests are fine.
> MVCC: cache operation may hang during late affinity assignment.
> ---
>
> Key: IGNITE-10261
> URL: https://issues.apache.org/jira/browse/IGNITE-10261
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Andrew Mashenkov
>Assignee: Roman Kondakov
>Priority: Critical
> Labels: failover, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> ForceKey response processing fails with ClassCastException with Mvcc mode
> that causes test hanging.
> Issue can be easily reproduced with backups > 0 and disabled rebalance. See
> GridCacheDhtPreloadPutGetSelfTest.testPutGetNone1().
> Also CacheLateAffinityAssignmentTest.testRandomOperations() hangs sometimes
> due to same reason.
>
> {noformat}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry
> cannot be cast to
> org.apache.ignite.internal.processors.cache.mvcc.MvccVersionAware
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture$MiniFuture.onResult(GridDhtForceKeysFuture.java:545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onResult(GridDhtForceKeysFuture.java:202)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processForceKeyResponse(GridDhtCacheAdapter.java:180)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$11.onMessage(GridDhtTransactionalCacheAdapter.java:208)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$11.onMessage(GridDhtTransactionalCacheAdapter.java:206)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$MessageHandler.apply(GridDhtCacheAdapter.java:1434)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$MessageHandler.apply(GridDhtCacheAdapter.java:1416)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10768) MVCC: CacheMvccBasicContinuousQueryTest.testUpdateCountersGapClosedSimplePartitioned may hang
[
https://issues.apache.org/jira/browse/IGNITE-10768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786940#comment-16786940
]
Ignite TC Bot commented on IGNITE-10768:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3256449&buildTypeId=IgniteTests24Java8_RunAll]
> MVCC:
> CacheMvccBasicContinuousQueryTest.testUpdateCountersGapClosedSimplePartitioned
> may hang
> -
>
> Key: IGNITE-10768
> URL: https://issues.apache.org/jira/browse/IGNITE-10768
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: CQ, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Test
> {{CacheMvccBasicContinuousQueryTest.testUpdateCountersGapClosedSimplePartitioned}}
> may hang sometimes.
>
> {noformat}
> Thread [name="test-runner-#209301%mvcc.CacheMvccBasicContinuousQueryTest%",
> id=228123, state=WAITING, blockCnt=5, waitCnt=89]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:179)
> at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:142)
> at
> o.a.i.i.processors.cache.mvcc.CacheMvccBasicContinuousQueryTest.checkUpdateCountersGapIsProcessedSimple(CacheMvccBasicContinuousQueryTest.java:346)
> at
> o.a.i.i.processors.cache.mvcc.CacheMvccBasicContinuousQueryTest.testUpdateCountersGapClosedSimplePartitioned(CacheMvccBasicContinuousQueryTest.java:257)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at
> o.a.i.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2121)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-11506) Web Console: Adjust CSS styles to correctly show "User name" in top menu.
[ https://issues.apache.org/jira/browse/IGNITE-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-11506. - > Web Console: Adjust CSS styles to correctly show "User name" in top menu. > - > > Key: IGNITE-11506 > URL: https://issues.apache.org/jira/browse/IGNITE-11506 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > If user will input large names UI will be broken. > We need to tweak CSS overflow properties -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11506) Web Console: Adjust CSS styles to correctly show "User name" in top menu.
[ https://issues.apache.org/jira/browse/IGNITE-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-11506: -- Component/s: wizards > Web Console: Adjust CSS styles to correctly show "User name" in top menu. > - > > Key: IGNITE-11506 > URL: https://issues.apache.org/jira/browse/IGNITE-11506 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > If user will input large names UI will be broken. > We need to tweak CSS overflow properties -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11506) Web Console: Adjust CSS styles to correctly show "User name" in top menu.
[ https://issues.apache.org/jira/browse/IGNITE-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-11506: -- Ignite Flags: (was: Docs Required) > Web Console: Adjust CSS styles to correctly show "User name" in top menu. > - > > Key: IGNITE-11506 > URL: https://issues.apache.org/jira/browse/IGNITE-11506 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > If user will input large names UI will be broken. > We need to tweak CSS overflow properties -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11506) Web Console: Adjust CSS styles to correctly show "User name" in top menu.
[ https://issues.apache.org/jira/browse/IGNITE-11506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-11506: -- Fix Version/s: 2.8 > Web Console: Adjust CSS styles to correctly show "User name" in top menu. > - > > Key: IGNITE-11506 > URL: https://issues.apache.org/jira/browse/IGNITE-11506 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > If user will input large names UI will be broken. > We need to tweak CSS overflow properties -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11506) Web Console: Adjust CSS styles to correctly show "User name" in top menu.
Alexey Kuznetsov created IGNITE-11506: - Summary: Web Console: Adjust CSS styles to correctly show "User name" in top menu. Key: IGNITE-11506 URL: https://issues.apache.org/jira/browse/IGNITE-11506 Project: Ignite Issue Type: Bug Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov If user will input large names UI will be broken. We need to tweak CSS overflow properties -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11497) Web console: index.html is cached
[ https://issues.apache.org/jira/browse/IGNITE-11497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-11497: -- Fix Version/s: 2.8 > Web console: index.html is cached > - > > Key: IGNITE-11497 > URL: https://issues.apache.org/jira/browse/IGNITE-11497 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > Time Spent: 41m > Remaining Estimate: 0h > > Some users, including [~pkonstantinov], reported cache-related issues for a > long while. According to [this > article|https://blog.cronobo.com/2018/03/17/how-to-configure-caching-with-single-page-apps.html], > it might have to do with index.html caching, so let's disabled caching for > this particular file. > What to do: > Disable index.html caching. > Acceptance criteria: > With "disable cache" option turned off in web inspector, index.html should > always be loaded from server. Here's a convoluted scenario: > 1. Build docker image of web console > 2. Open a tab (A), open web inspector on network tab, ensure caching is > enabled, go to web console. > 3. Build the image again. > 4. Open another tab (B), open web inspector on network tab, ensure caching is > not disabled, go to web console; index.html should not reported cache usage, > js/css assets should have file names different from same files in inspector > of browser tab A. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11447) Replacements for default values in System SQL views.
[ https://issues.apache.org/jira/browse/IGNITE-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11447: --- Labels: (was: iep-29) > Replacements for default values in System SQL views. > > > Key: IGNITE-11447 > URL: https://issues.apache.org/jira/browse/IGNITE-11447 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Priority: Major > Fix For: 2.8 > > > To avoid specific internal values need to change how we show values for some > fields. > Columns CACHES and CACHE_GROUPS: if there is no node filter > (IgniteAllNodesPredicate) we should print NULL > Columns CACHE_GROUPS.BACKUPS - show NULL for REPLICATED caches > (Integer.MAX_VALUE is shown at the moment) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11445) Usability improvements for TABLES system SQL view
[ https://issues.apache.org/jira/browse/IGNITE-11445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11445: --- Component/s: (was: sql) > Usability improvements for TABLES system SQL view > - > > Key: IGNITE-11445 > URL: https://issues.apache.org/jira/browse/IGNITE-11445 > Project: Ignite > Issue Type: Task >Reporter: Yury Gerzhedovich >Priority: Major > > Need to add CACHE_GROUP_NAME and CACHE_GROUP_ID attributes to TABLES system > SQL view -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11447) Replacements for default values in System SQL views.
[ https://issues.apache.org/jira/browse/IGNITE-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11447: --- Fix Version/s: (was: 2.8) > Replacements for default values in System SQL views. > > > Key: IGNITE-11447 > URL: https://issues.apache.org/jira/browse/IGNITE-11447 > Project: Ignite > Issue Type: Task >Reporter: Yury Gerzhedovich >Priority: Major > > To avoid specific internal values need to change how we show values for some > fields. > Columns CACHES and CACHE_GROUPS: if there is no node filter > (IgniteAllNodesPredicate) we should print NULL > Columns CACHE_GROUPS.BACKUPS - show NULL for REPLICATED caches > (Integer.MAX_VALUE is shown at the moment) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-11447) Replacements for default values in System SQL views.
[ https://issues.apache.org/jira/browse/IGNITE-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich resolved IGNITE-11447. Resolution: Duplicate > Replacements for default values in System SQL views. > > > Key: IGNITE-11447 > URL: https://issues.apache.org/jira/browse/IGNITE-11447 > Project: Ignite > Issue Type: Task >Reporter: Yury Gerzhedovich >Priority: Major > Fix For: 2.8 > > > To avoid specific internal values need to change how we show values for some > fields. > Columns CACHES and CACHE_GROUPS: if there is no node filter > (IgniteAllNodesPredicate) we should print NULL > Columns CACHE_GROUPS.BACKUPS - show NULL for REPLICATED caches > (Integer.MAX_VALUE is shown at the moment) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11447) Replacements for default values in System SQL views.
[ https://issues.apache.org/jira/browse/IGNITE-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11447: --- Component/s: (was: sql) > Replacements for default values in System SQL views. > > > Key: IGNITE-11447 > URL: https://issues.apache.org/jira/browse/IGNITE-11447 > Project: Ignite > Issue Type: Task >Reporter: Yury Gerzhedovich >Priority: Major > Fix For: 2.8 > > > To avoid specific internal values need to change how we show values for some > fields. > Columns CACHES and CACHE_GROUPS: if there is no node filter > (IgniteAllNodesPredicate) we should print NULL > Columns CACHE_GROUPS.BACKUPS - show NULL for REPLICATED caches > (Integer.MAX_VALUE is shown at the moment) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11445) Usability improvements for TABLES system SQL view
[ https://issues.apache.org/jira/browse/IGNITE-11445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11445: --- Labels: (was: iep-29) > Usability improvements for TABLES system SQL view > - > > Key: IGNITE-11445 > URL: https://issues.apache.org/jira/browse/IGNITE-11445 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Priority: Major > > Need to add CACHE_GROUP_NAME and CACHE_GROUP_ID attributes to TABLES system > SQL view -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-11445) Usability improvements for TABLES system SQL view
[ https://issues.apache.org/jira/browse/IGNITE-11445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich resolved IGNITE-11445. Resolution: Duplicate > Usability improvements for TABLES system SQL view > - > > Key: IGNITE-11445 > URL: https://issues.apache.org/jira/browse/IGNITE-11445 > Project: Ignite > Issue Type: Task >Reporter: Yury Gerzhedovich >Priority: Major > > Need to add CACHE_GROUP_NAME and CACHE_GROUP_ID attributes to TABLES system > SQL view -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11443) usability improvements system SQL view
[ https://issues.apache.org/jira/browse/IGNITE-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11443: --- Description: For all views need to: 1) move cache and cache group attributes to the beginning to form consistent hierarchy: cache group -> cache -> schema -> table -> index 2) columns GROUP_ID and GROUP_NAME should be renamed to CACHE_GROUP_ID and CACHE_GROUP_NAME respectively 3) TABLES view: add CACHE_GROUP_NAME and CACHE_GROUP_ID attributes 4) CACHES and CACHE_GROUPS: if there is no node filter (IgniteAllNodesPredicate) we should print NULL 5) CACHE_GROUPS.BACKUPS - show NULL for REPLICATED caches (Integer.MAX_VALUE is shown at the moment) 6) For all columns with name ID need to add prefix which reflect real meaning of the column was: For all views need to: 1) move cache and cache group attributes to the beginning to form consistent hierarchy: cache group -> cache -> table -> index 2) columns GROUP_ID and GROUP_NAME should be renamed to CACHE_GROUP_ID and CACHE_GROUP_NAME respectively > usability improvements system SQL view > -- > > Key: IGNITE-11443 > URL: https://issues.apache.org/jira/browse/IGNITE-11443 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > > For all views need to: > 1) move cache and cache group attributes to the beginning to form consistent > hierarchy: cache group -> cache -> schema -> table -> index > 2) columns GROUP_ID and GROUP_NAME should be renamed to CACHE_GROUP_ID and > CACHE_GROUP_NAME respectively > 3) TABLES view: add CACHE_GROUP_NAME and CACHE_GROUP_ID attributes > 4) CACHES and CACHE_GROUPS: if there is no node filter > (IgniteAllNodesPredicate) we should print NULL > 5) CACHE_GROUPS.BACKUPS - show NULL for REPLICATED caches (Integer.MAX_VALUE > is shown at the moment) > 6) For all columns with name ID need to add prefix which reflect real meaning > of the column -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11443) Usability improvements system SQL view
[ https://issues.apache.org/jira/browse/IGNITE-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11443: --- Summary: Usability improvements system SQL view (was: usability improvements system SQL view) > Usability improvements system SQL view > -- > > Key: IGNITE-11443 > URL: https://issues.apache.org/jira/browse/IGNITE-11443 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > > For all views need to: > 1) move cache and cache group attributes to the beginning to form consistent > hierarchy: cache group -> cache -> schema -> table -> index > 2) columns GROUP_ID and GROUP_NAME should be renamed to CACHE_GROUP_ID and > CACHE_GROUP_NAME respectively > 3) TABLES view: add CACHE_GROUP_NAME and CACHE_GROUP_ID attributes > 4) CACHES and CACHE_GROUPS: if there is no node filter > (IgniteAllNodesPredicate) we should print NULL > 5) CACHE_GROUPS.BACKUPS - show NULL for REPLICATED caches (Integer.MAX_VALUE > is shown at the moment) > 6) For all columns with name ID need to add prefix which reflect real meaning > of the column -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11443) usability improvements system SQL view
[ https://issues.apache.org/jira/browse/IGNITE-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11443: --- Summary: usability improvements system SQL view (was: usability improvements for INDEXES system SQL view) > usability improvements system SQL view > -- > > Key: IGNITE-11443 > URL: https://issues.apache.org/jira/browse/IGNITE-11443 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > > For all views need to: > 1) move cache and cache group attributes to the beginning to form consistent > hierarchy: cache group -> cache -> table -> index > 2) columns GROUP_ID and GROUP_NAME should be renamed to CACHE_GROUP_ID and > CACHE_GROUP_NAME respectively -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11465) Multiple client leave/join events may wipe affinity assignment history and cause transactions fail
[
https://issues.apache.org/jira/browse/IGNITE-11465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786783#comment-16786783
]
Sergey Antonov commented on IGNITE-11465:
-
[~ivan.glukos] looks good.
> Multiple client leave/join events may wipe affinity assignment history and
> cause transactions fail
> --
>
> Key: IGNITE-11465
> URL: https://issues.apache.org/jira/browse/IGNITE-11465
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We keep history of GridAffinityAssignmentCache#MAX_HIST_SIZE affinity
> assignments. However, flood of client joins/leaves may wipe it out entirely
> and cause fail/hang of transaction that was started before the flood due to
> the following exception:
> {code:java}
> if (cache == null || cache.topologyVersion().compareTo(topVer) >
> 0) {
> throw new IllegalStateException("Getting affinity for
> topology version earlier than affinity is " +
> "calculated [locNode=" + ctx.discovery().localNode() +
> ", grp=" + cacheOrGrpName +
> ", topVer=" + topVer +
> ", head=" + head.get().topologyVersion() +
> ", history=" + affCache.keySet() +
> ']');
> }
> {code}
> History is limited in order to prevent JVM heap overflow. At the same time,
> only "server event" affinity assignments are heavy: "client event"
> assignments are just shallow copies of "server event" assignments.
> I suggest to limit history by the number of "server event" assignments.
> Also, considering the provided fix, I don't see any need to keep 500 items in
> history. I propose to change history size to 50.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[
https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786773#comment-16786773
]
Ignite TC Bot commented on IGNITE-5962:
---
{panel:title=-> Run :: SQL: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3256952]]
* exe: CancellationTest.TestJavaTask - 0,0% fails in last 582 master runs.
{panel}
[TeamCity *-> Run :: SQL*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3256954&buildTypeId=IgniteTests24Java8_RunAllSql]
> Increase max length of index name
> -
>
> Key: IGNITE-5962
> URL: https://issues.apache.org/jira/browse/IGNITE-5962
> Project: Ignite
> Issue Type: Improvement
> Components: general, sql
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Pavel Kuznetsov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length
> was reduced from 768 to 256 bytes. If we need to support longer names, we
> need to change format of metastore data pages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-10644) CorruptedTreeException might occur after force node kill during transaction
[ https://issues.apache.org/jira/browse/IGNITE-10644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny resolved IGNITE-10644. - Resolution: Duplicate > CorruptedTreeException might occur after force node kill during transaction > --- > > Key: IGNITE-10644 > URL: https://issues.apache.org/jira/browse/IGNITE-10644 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > > Partition eviction process on the other hand: > > 2018-12-10 20:59:24.426 > [ERROR]sys-#204%_GRID%GridNodeName%[o.a.i.i.p.c.d.d.t.PartitionsEvictManager] > Partition eviction failed, this can cause grid hang. > org.h2.message.DbException: General error: "class > org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException: > Runtime failure on search row: Row@3580787f[ key: 4071535538120363041, val: > X.common.dpl.model.backstream.DBackStreamMessage_DPL_PROXY > [idHash=1961442513, hash=529139710, colocationKey=14465, entityType=I, > lastChangeDate=1544464745135, errorMessage=No api > [X.scripts.ucp.retail.propagate.publicapi.ClientPropagateService] services > available for route: [*][*][kbt] (zone-node-module).IP: [*]. > List of services violations: > NODE MODULE FILTER VIOLATIONS > No services or violations were found for routing, partition_X_id=5, > messageId=1211871172446406939, entityId=1211871174131851324, ownerId=ucp, > responseDate=null, entityVersion=1, isDeleted=false, requestDate=Mon Dec 10 > 20:59:05 MSK 2018, id=4071535538120363041], ver: GridCacheVersion > [topVer=155940834, order=1544596983071, nodeOrder=114] ][ I, null, > 1211871172446406939, 1211871174131851324, null, 1, 2018-12-10 20:59:05.115, > No api [X.scripts.ucp.retail.propagate.publicapi.ClientPropagateService] > services available for route: [*][*][kbt] (zone-node-module).IP: [*]. > List of services violations: > NODE MODULE FILTER VIOLATIONS > No services or violations were found for routing, 4071535538120363041, FALSE, > 5 ]" [5-195] > at org.h2.message.DbException.get(DbException.java:168) > at org.h2.message.DbException.convert(DbException.java:295) > at > org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.removex(H2TreeIndex.java:293) > at > org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.remove(GridH2Table.java:515) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.remove(IgniteH2Indexing.java:738) > at > org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:2487) > at > org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:433) > at > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishRemove(IgniteCacheOffheapManagerImpl.java:1465) > at > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1435) > at > org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.remove(GridCacheOffheapManager.java:1633) > at > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:383) > at > org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3706) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.clearInternal(GridDhtCacheEntry.java:652) > at > org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.clearAll(GridDhtLocalPartition.java:1079) > at > org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.tryClear(GridDhtLocalPartition.java:915) > at > org.apache.ignite.internal.processors.cache.distributed.dht.topology.PartitionsEvictManager$PartitionEvictionTask.run(PartitionsEvictManager.java:423) > at > org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6782) > at > org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827) > at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.h2.jdbc.JdbcSQLException: General error: "class > org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException: > Runtime failure on search row: Row@3580787f[ key: 4071535538120363041, val: > X.common.X.model.backstream.DBackStreamMessage_X_PROXY [idHash=1961442513, > hash=529139710, colocationKey=14465, e
[jira] [Commented] (IGNITE-11227) SQL: Streamline DML execution logic
[ https://issues.apache.org/jira/browse/IGNITE-11227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786739#comment-16786739 ] Vladimir Ozerov commented on IGNITE-11227: -- Implemented. Test run: https://ci.ignite.apache.org/viewQueued.html?itemId=3258802 > SQL: Streamline DML execution logic > --- > > Key: IGNITE-11227 > URL: https://issues.apache.org/jira/browse/IGNITE-11227 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently DML execution logic is overly complex with execution flow being > transferred between indexing and DML processor back and forth. Need to > simplify it as much as possible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11505) Validation of starting cache configuration wraps original exception into Suppressed section
[
https://issues.apache.org/jira/browse/IGNITE-11505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kuznetsov updated IGNITE-11505:
-
Labels: Usability (was: )
> Validation of starting cache configuration wraps original exception into
> Suppressed section
> ---
>
> Key: IGNITE-11505
> URL: https://issues.apache.org/jira/browse/IGNITE-11505
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Kuznetsov
>Priority: Major
> Labels: Usability
>
> {{org.apache.ignite.internal.processors.cache.GridCacheProcessor#validate}} :
> If user starts cache dynamically via {{getOrCreateCache}} on *server node*
> and {{validate}} method throws an
> exception, this exception will be shown to user in the as Suppressed. So user
> need to get the cause as:
> {code:java}
> String origMessage =
> catchedUserExc.getSuppressed()[0].getCause().getMessage();
> {code}
> To reproduce, it is important, that validation should be performed on the
> server node.
> take a look at stacktraces.
> cache started from server node:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Failed to complete exchange
> process.
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.createExchangeException(GridDhtPartitionsExchangeFuture.java:3209)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendExchangeFailureMessage(GridDhtPartitionsExchangeFuture.java:3237)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3323)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3304)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2906)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:145)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2713)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2701)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2701)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1812)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:148)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:385)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:343)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3368)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3347)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1126)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1561)
> at
> org.apache.ignite.internal.manag
[jira] [Commented] (IGNITE-11464) Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix queries and visor package conflicts
[
https://issues.apache.org/jira/browse/IGNITE-11464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786719#comment-16786719
]
Ignite TC Bot commented on IGNITE-11464:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3232869&buildTypeId=IgniteTests24Java8_RunAll]
> Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix
> queries and visor package conflicts
>
>
> Key: IGNITE-11464
> URL: https://issues.apache.org/jira/browse/IGNITE-11464
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> error: the unnamed module reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: the unnamed module reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: the unnamed module reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: the unnamed module reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: the unnamed module reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
>
> C:\projects\incubator-ignite\modules\dev-utils\ignite-modules-test\src\test\java\module-info.java:18:
> error: module ignite_modules_test reads package org.apache.lucene.search
> from both lucene.sandbox and lucene.core
> module ignite_modules_test
> {noformat}
>
> Some of these errors probably can be fixed by workarounds for dependencies:
> 2 errors coming from duplicate packages declared in code and indexing:
> - error: module ignite.core reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> - error: module ignite.core reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11505) Validation of starting cache configuration wraps original exception into Suppressed section
[
https://issues.apache.org/jira/browse/IGNITE-11505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kuznetsov updated IGNITE-11505:
-
Description:
{{org.apache.ignite.internal.processors.cache.GridCacheProcessor#validate}} :
If user starts cache dynamically via {{getOrCreateCache}} on *server node* and
{{validate}} method throws an
exception, this exception will be shown to user in the as Suppressed. So user
need to get the cause as {{String origMessage =
catchedUserExc.getSuppressed()[0].getCause().getMessage();}}.
To reproduce, it is important, that validation should be performed on the
server node.
take a look at stacktraces.
cache started from server node:
{noformat}
class org.apache.ignite.IgniteCheckedException: Failed to complete exchange
process.
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.createExchangeException(GridDhtPartitionsExchangeFuture.java:3209)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendExchangeFailureMessage(GridDhtPartitionsExchangeFuture.java:3237)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3323)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3304)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2906)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:145)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2713)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2701)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2701)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1812)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:148)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:385)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:343)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3368)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3347)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1126)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1561)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1189)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1086)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Suppressed: class org.apache.ignite.Igni
[jira] [Updated] (IGNITE-11505) Validation of starting cache configuration wraps original exception into Suppressed section
[
https://issues.apache.org/jira/browse/IGNITE-11505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kuznetsov updated IGNITE-11505:
-
Description:
{{org.apache.ignite.internal.processors.cache.GridCacheProcessor#validate}} :
If user starts cache dynamically via {{getOrCreateCache}} on *server node* and
{{validate}} method throws an
exception, this exception will be shown to user in the as Suppressed. So user
need to get the cause as:
{code:java}
String origMessage = catchedUserExc.getSuppressed()[0].getCause().getMessage();
{code}
To reproduce, it is important, that validation should be performed on the
server node.
take a look at stacktraces.
cache started from server node:
{noformat}
class org.apache.ignite.IgniteCheckedException: Failed to complete exchange
process.
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.createExchangeException(GridDhtPartitionsExchangeFuture.java:3209)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendExchangeFailureMessage(GridDhtPartitionsExchangeFuture.java:3237)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3323)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3304)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2906)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:145)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2713)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2701)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2701)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1812)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:148)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:385)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:343)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3368)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3347)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1126)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1561)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1189)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1086)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Suppressed: class org.apa
[jira] [Updated] (IGNITE-11505) Validation of starting cache configuration wraps original exception into Suppressed section
[
https://issues.apache.org/jira/browse/IGNITE-11505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kuznetsov updated IGNITE-11505:
-
Description:
{{org.apache.ignite.internal.processors.cache.GridCacheProcessor#validate}} :
If user starts cache dynamically via {{getOrCreateCache}} on *server node* and
{{validate}} method throws an
exception, this exception will be shown to user in the as Suppressed. So user
need to get the cause as
{code:java}
String origMessage = catchedUserExc.getSuppressed()[0].getCause().getMessage();
{code}
To reproduce, it is important, that validation should be performed on the
server node.
take a look at stacktraces.
cache started from server node:
{noformat}
class org.apache.ignite.IgniteCheckedException: Failed to complete exchange
process.
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.createExchangeException(GridDhtPartitionsExchangeFuture.java:3209)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendExchangeFailureMessage(GridDhtPartitionsExchangeFuture.java:3237)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3323)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3304)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2906)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:145)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2713)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2701)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2701)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1812)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:148)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:385)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:343)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3368)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3347)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1126)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1561)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1189)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1086)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Suppressed: class org.apa
[jira] [Updated] (IGNITE-11505) Validation of starting cache configuration wraps original exception into Suppressed section
[
https://issues.apache.org/jira/browse/IGNITE-11505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kuznetsov updated IGNITE-11505:
-
Description:
{{org.apache.ignite.internal.processors.cache.GridCacheProcessor#validate}} :
If user starts cache dynamically via {{getOrCreateCache}} on *server node* and
{{validate}} method throws an
exception, this exception will be shown to user in the as Suppressed. So user
need to get the cause as:
{code:java}
String origMessage = catchedUserExc.getSuppressed()[0].getCause().getMessage();
{code}
To reproduce, it is important, that validation should be performed on the
server node.
take a look at stacktraces.
cache started from server node:
{noformat}
class org.apache.ignite.IgniteCheckedException: Failed to complete exchange
process.
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.createExchangeException(GridDhtPartitionsExchangeFuture.java:3209)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendExchangeFailureMessage(GridDhtPartitionsExchangeFuture.java:3237)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3323)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3304)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2906)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:145)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2713)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2701)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2701)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1812)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:148)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:385)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:343)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3368)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3347)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1126)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1561)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1189)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1086)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Suppressed: class org.apac
[jira] [Created] (IGNITE-11505) Validation of starting cache configuration wraps original exception into Suppressed section
Pavel Kuznetsov created IGNITE-11505:
Summary: Validation of starting cache configuration wraps original
exception into Suppressed section
Key: IGNITE-11505
URL: https://issues.apache.org/jira/browse/IGNITE-11505
Project: Ignite
Issue Type: Improvement
Reporter: Pavel Kuznetsov
{{org.apache.ignite.internal.processors.cache.GridCacheProcessor#validate}} :
If user starts cache dynamically via {{getOrCreateCache}} on *server node* and
{{validate}} method throws an
exception, this exception will be shown to user in the as Suppressed. So user
need to get the cause as {{ String origMessage =
catchedUserExc.getSuppressed()[0].getCause().getMessage();}}.
To reproduce, it is important, that validation should be performed on the
server node.
take a look at stacktraces.
cache started from server node:
{noformat}
class org.apache.ignite.IgniteCheckedException: Failed to complete exchange
process.
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.createExchangeException(GridDhtPartitionsExchangeFuture.java:3209)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendExchangeFailureMessage(GridDhtPartitionsExchangeFuture.java:3237)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3323)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3304)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2906)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:145)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2713)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2701)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2701)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1812)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:148)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:385)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:343)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3368)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3347)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1126)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1561)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1189)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1086)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[jira] [Comment Edited] (IGNITE-10104) MVCC TX: client SFU doesn't work on replicated caches
[
https://issues.apache.org/jira/browse/IGNITE-10104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786601#comment-16786601
]
Andrew Mashenkov edited comment on IGNITE-10104 at 3/7/19 12:07 PM:
[~rkondakov],
# Let's replace map queries collection with single object as seems, we always
have a single map query for every reduce query.
# It is not clear why we have to save both query versions: with and without
"FOR UPDATE" clause. Please, add a bit more info to javadoc for added fields in
TwoStepQuery.
# Also, I'm not sure if "_key" column is added correctly in case of nested
Selects. Most likely it wasn't work before changes in PR and such changes look
ok for now.
was (Author: amashenkov):
[~rkondakov],
# Let's replace map queries collection with single object as seems, we always
have a single map query for every reduce query.
# It is not clear why we have to save both query versions: with and without
"FOR UPDATE" clause. Please, add a bit more info to javadoc for added fields in
TwoStepQuery.
> MVCC TX: client SFU doesn't work on replicated caches
> -
>
> Key: IGNITE-10104
> URL: https://issues.apache.org/jira/browse/IGNITE-10104
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When select for update executes from client node the execution is sent to
> random owning node. On that node dht enlist operation is started what causes
> an assertion error because dht enlist operation implies that the node is
> primary for all processed keys.
> see
> {{CacheMvccReplicatedBackupsTest.testBackupsCoherenceWithLargeOperations}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11504) [ML] Preprocessor trainers should support new feature-label extraction API
Alexey Platonov created IGNITE-11504: Summary: [ML] Preprocessor trainers should support new feature-label extraction API Key: IGNITE-11504 URL: https://issues.apache.org/jira/browse/IGNITE-11504 Project: Ignite Issue Type: Improvement Components: ml Reporter: Alexey Platonov Problem is same as feature extractors serialization bug. We should narrow our API. (see parent task) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[
https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786681#comment-16786681
]
Pavel Kuznetsov commented on IGNITE-5962:
-
Currently {{LongIndexNameTest}} is part of {{IgniteBinaryCacheQueryTestSuite}}
> Increase max length of index name
> -
>
> Key: IGNITE-5962
> URL: https://issues.apache.org/jira/browse/IGNITE-5962
> Project: Ignite
> Issue Type: Improvement
> Components: general, sql
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Pavel Kuznetsov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length
> was reduced from 768 to 256 bytes. If we need to support longer names, we
> need to change format of metastore data pages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11107) MVCC: IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodes hangs sometimes
[
https://issues.apache.org/jira/browse/IGNITE-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin reassigned IGNITE-11107:
---
Assignee: (was: Ivan Pavlukhin)
> MVCC:
> IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodes
> hangs sometimes
> ---
>
> Key: IGNITE-11107
> URL: https://issues.apache.org/jira/browse/IGNITE-11107
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: Hanging, mvcc_stabilization_stage_1
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Sometimes
> IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodes
> hangs on PME. Some partitions have not changed their state from {{RENTING}}
> to {{OWNING}}.
> {noformat}
> [2019-01-27 07:20:23,420][WARN
> ][test-runner-#32729%distributed.IgniteCachePartitionLossPolicySelfTest%][root]
> Finished waiting for topology map update
> [igniteInstanceName=distributed.IgniteCachePartitionLossPolicySelfTest4, p=0,
> duration=1415ms]
> [2019-01-27 07:20:23,421][WARN
> ][test-runner-#32729%distributed.IgniteCachePartitionLossPolicySelfTest%][root]
> Waiting for correct partition state part=2, should be OWNING
> [state=RENTING], node=distributed.IgniteCachePartitionLossPolicySelfTest4,
> cache=default
> [2019-01-27 07:20:25,023][WARN
> ][test-runner-#32729%distributed.IgniteCachePartitionLossPolicySelfTest%][root]
> Waiting for correct partition state part=13, should be OWNING
> [state=RENTING], node=distributed.IgniteCachePartitionLossPolicySelfTest4,
> cache=default
> Thread
> [name="test-runner-#32729%distributed.IgniteCachePartitionLossPolicySelfTest%",
> id=35714, state=RUNNABLE, blockCnt=93, waitCnt=1033]
> at sun.management.ThreadImpl.dumpThreads0(Native Method)
> at sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:454)
> at o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1370)
> at
> o.a.i.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:792)
> at
> o.a.i.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:569)
> at
> o.a.i.i.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.checkLostPartition(IgniteCachePartitionLossPolicySelfTest.java:560)
> at
> o.a.i.i.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodes(IgniteCachePartitionLossPolicySelfTest.java:258)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> o.a.i.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11215) MVCC: JVM crash in MVCC PDS 1 suite
[
https://issues.apache.org/jira/browse/IGNITE-11215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-11215:
--
Attachment: No_C2_opts_hs_err_pid957384.log
> MVCC: JVM crash in MVCC PDS 1 suite
> ---
>
> Key: IGNITE-11215
> URL: https://issues.apache.org/jira/browse/IGNITE-11215
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Critical
> Labels: mvcc_stabilization_stage_1
> Attachments: No_C2_opts_hs_err_pid957384.log, hs_err_pid429215.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Sometimes JVM crash
> [occurs|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeHistoryList&state=failed]
> in {{vacuum-cleaner}} thread in {{ExplicitWalDeltaConsistencyTest}}.
> See attached crash report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11152) IgniteTxManager.idMap possible memory leak
[
https://issues.apache.org/jira/browse/IGNITE-11152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786632#comment-16786632
]
Andrew Mashenkov commented on IGNITE-11152:
---
[~rkondakov],
Got it. PR looks ok.
Thanks for contribution!
> IgniteTxManager.idMap possible memory leak
> --
>
> Key: IGNITE-11152
> URL: https://issues.apache.org/jira/browse/IGNITE-11152
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Stepachev Maksim
>Assignee: Roman Kondakov
>Priority: Major
> Labels: memory-leak, mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> CacheContinuousQueryAsyncFailoverMvccTxSelfTest.testMultiThreadedFailover
> sometimes finished with OMM.
> Heapdump analyze showed that leak happened in IgniteTxManager.idMap, this map
> contains *2_097_152* instances of GridNearTxLocal with *ACTIVE state* and
> *without* finishFut *and prepFut.*
>
> {code:java}
> while (!updated) {
> try {
> prevVal = (Integer)qryClnCache.getAndPut(key, val);
> updated = true;
> }
> catch (CacheException e) {
> assertSame(atomicityMode(), CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT);
> }
> }
> {code}
>
>
> Possible the CacheException is common and may hide wrong cases. Change it at
> specific (ignite-10976).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11496) Long running SQL queries could be randomly canceled from WC
[
https://issues.apache.org/jira/browse/IGNITE-11496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-11496:
--
Assignee: Andrey Novikov (was: Sergey Kozlov)
> Long running SQL queries could be randomly canceled from WC
> ---
>
> Key: IGNITE-11496
> URL: https://issues.apache.org/jira/browse/IGNITE-11496
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.5
>Reporter: Evgenii Zhuravlev
>Assignee: Andrey Novikov
>Priority: Major
>
> I've tried to run some long-running queries from WC(more than a couple of
> minutes) and I've faced a behavior when the query was canceled without
> clicking on the cancel button.
> I've opened different browser tabs at this moment, maybe it could be the
> reason.
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:883)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$7.iterator(IgniteH2Indexing.java:1494)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
> at
> org.apache.ignite.internal.visor.query.VisorQueryHolder.getIterator(VisorQueryHolder.java:97)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:85)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:51)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6750)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1921)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.cache.query.QueryCancelledException: The
> query was cancelled while executing.
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1240)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1303)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1281)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:835)
> ... 20 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11496) Long running SQL queries could be randomly canceled from WC
[
https://issues.apache.org/jira/browse/IGNITE-11496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786618#comment-16786618
]
Vasiliy Sisko commented on IGNITE-11496:
Implemented notification of node when extraction of query results is long.
> Long running SQL queries could be randomly canceled from WC
> ---
>
> Key: IGNITE-11496
> URL: https://issues.apache.org/jira/browse/IGNITE-11496
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.5
>Reporter: Evgenii Zhuravlev
>Assignee: Vasiliy Sisko
>Priority: Major
>
> I've tried to run some long-running queries from WC(more than a couple of
> minutes) and I've faced a behavior when the query was canceled without
> clicking on the cancel button.
> I've opened different browser tabs at this moment, maybe it could be the
> reason.
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:883)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$7.iterator(IgniteH2Indexing.java:1494)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
> at
> org.apache.ignite.internal.visor.query.VisorQueryHolder.getIterator(VisorQueryHolder.java:97)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:85)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:51)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6750)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1921)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.cache.query.QueryCancelledException: The
> query was cancelled while executing.
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1240)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1303)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1281)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:835)
> ... 20 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11496) Long running SQL queries could be randomly canceled from WC
[
https://issues.apache.org/jira/browse/IGNITE-11496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-11496:
--
Assignee: Sergey Kozlov (was: Vasiliy Sisko)
> Long running SQL queries could be randomly canceled from WC
> ---
>
> Key: IGNITE-11496
> URL: https://issues.apache.org/jira/browse/IGNITE-11496
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.5
>Reporter: Evgenii Zhuravlev
>Assignee: Sergey Kozlov
>Priority: Major
>
> I've tried to run some long-running queries from WC(more than a couple of
> minutes) and I've faced a behavior when the query was canceled without
> clicking on the cancel button.
> I've opened different browser tabs at this moment, maybe it could be the
> reason.
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:883)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$7.iterator(IgniteH2Indexing.java:1494)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
> at
> org.apache.ignite.internal.visor.query.VisorQueryHolder.getIterator(VisorQueryHolder.java:97)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:85)
> at
> org.apache.ignite.internal.visor.query.VisorQueryFetchFirstPageTask$VisorQueryFetchFirstPageJob.run(VisorQueryFetchFirstPageTask.java:51)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6750)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1921)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.cache.query.QueryCancelledException: The
> query was cancelled while executing.
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1240)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1303)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1281)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:835)
> ... 20 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-8459) Searching checkpoint history for WAL rebalance is broken
[
https://issues.apache.org/jira/browse/IGNITE-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko resolved IGNITE-8459.
-
Resolution: Won't Fix
The problem is already fixed in IGNITE-10078
> Searching checkpoint history for WAL rebalance is broken
>
>
> Key: IGNITE-8459
> URL: https://issues.apache.org/jira/browse/IGNITE-8459
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Priority: Critical
> Fix For: 2.8
>
>
> Currently the mechanism to search available checkpoint records in WAL to have
> history for WAL rebalance is broken. It means that WAL (Historical) rebalance
> will never find history for rebalance and full rebalance will be always used.
> This mechanism was broken in
> https://github.com/apache/ignite/commit/ec04cd174ed5476fba83e8682214390736321b37
> by unclear reasons.
> If we swap the following two code blocks (database().beforeExchange() and
> exchCtx if block):
> {noformat}
> /* It is necessary to run database callback before all topology
> callbacks.
>In case of persistent store is enabled we first restore partitions
> presented on disk.
>We need to guarantee that there are no partition state changes
> logged to WAL before this callback
>to make sure that we correctly restored last actual states. */
> cctx.database().beforeExchange(this);
> if (!exchCtx.mergeExchanges()) {
> for (CacheGroupContext grp : cctx.cache().cacheGroups()) {
> if (grp.isLocal() || cacheGroupStopping(grp.groupId()))
> continue;
> // It is possible affinity is not initialized yet if node
> joins to cluster.
> if (grp.affinity().lastVersion().topologyVersion() > 0)
> grp.topology().beforeExchange(this, !centralizedAff &&
> !forceAffReassignment, false);
> }
> }
> {noformat}
> the searching mechanism will start to work correctly. Currently it's unclear
> why it's happened.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10104) MVCC TX: client SFU doesn't work on replicated caches
[
https://issues.apache.org/jira/browse/IGNITE-10104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786601#comment-16786601
]
Andrew Mashenkov commented on IGNITE-10104:
---
[~rkondakov],
# Let's replace map queries collection with single object as seems, we always
have a single map query for every reduce query.
# It is not clear why we have to save both query versions: with and without
"FOR UPDATE" clause. Please, add a bit more info to javadoc for added fields in
TwoStepQuery.
> MVCC TX: client SFU doesn't work on replicated caches
> -
>
> Key: IGNITE-10104
> URL: https://issues.apache.org/jira/browse/IGNITE-10104
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When select for update executes from client node the execution is sent to
> random owning node. On that node dht enlist operation is started what causes
> an assertion error because dht enlist operation implies that the node is
> primary for all processed keys.
> see
> {{CacheMvccReplicatedBackupsTest.testBackupsCoherenceWithLargeOperations}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11227) SQL: Streamline DML execution logic
[ https://issues.apache.org/jira/browse/IGNITE-11227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-11227: - Fix Version/s: 2.8 > SQL: Streamline DML execution logic > --- > > Key: IGNITE-11227 > URL: https://issues.apache.org/jira/browse/IGNITE-11227 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > > Currently DML execution logic is overly complex with execution flow being > transferred between indexing and DML processor back and forth. Need to > simplify it as much as possible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11227) SQL: Streamline DML execution logic
[ https://issues.apache.org/jira/browse/IGNITE-11227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-11227: - Ignite Flags: (was: Docs Required) > SQL: Streamline DML execution logic > --- > > Key: IGNITE-11227 > URL: https://issues.apache.org/jira/browse/IGNITE-11227 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > > Currently DML execution logic is overly complex with execution flow being > transferred between indexing and DML processor back and forth. Need to > simplify it as much as possible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11227) SQL: Streamline DML execution logic
[ https://issues.apache.org/jira/browse/IGNITE-11227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-11227: Assignee: Vladimir Ozerov > SQL: Streamline DML execution logic > --- > > Key: IGNITE-11227 > URL: https://issues.apache.org/jira/browse/IGNITE-11227 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > > Currently DML execution logic is overly complex with execution flow being > transferred between indexing and DML processor back and forth. Need to > simplify it as much as possible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11503) MVCC: Handle partition loss policies
Ivan Pavlukhin created IGNITE-11503: --- Summary: MVCC: Handle partition loss policies Key: IGNITE-11503 URL: https://issues.apache.org/jira/browse/IGNITE-11503 Project: Ignite Issue Type: Task Components: mvcc Reporter: Ivan Pavlukhin We need to be sure that partition loss policy is properly handled during interaction with MVCC caches. It should be covered by tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11441) ignite-sys-cache present in SQL schemas
[ https://issues.apache.org/jira/browse/IGNITE-11441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786575#comment-16786575 ] Yury Gerzhedovich commented on IGNITE-11441: Vladimir in case tickets IGNITE-11428/IGNITE-11431 will be merged earlier then this ticket, need to remerge with master and fix some test related to check set of available schemas. So please don't merge it if IGNITE-11428/IGNITE-11431 merged and don't have new BOT vise. > ignite-sys-cache present in SQL schemas > --- > > Key: IGNITE-11441 > URL: https://issues.apache.org/jira/browse/IGNITE-11441 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Time Spent: 10m > Remaining Estimate: 0h > > Investigate why ignite-sys-cache (and possible other caches without > configured QueryEntity) are displayed in schemas. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10161) Be able to cancel any query by query id
[
https://issues.apache.org/jira/browse/IGNITE-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786549#comment-16786549
]
Ignite TC Bot commented on IGNITE-10161:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3249334&buildTypeId=IgniteTests24Java8_RunAll]
> Be able to cancel any query by query id
> ---
>
> Key: IGNITE-10161
> URL: https://issues.apache.org/jira/browse/IGNITE-10161
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> User should be able to cancel any query by query id through SQL command.
> SQL syntax: *KILL QUERY \{ASYNC} '<_query_id>'_*
> _ASYNC_ is optional parameter which return control immediately without
> waiting real cancellation will be done.
> By default, without ASYNC parameter, the request is blocking untill
> cancellation is not done.
> Query should be canceled together with its parts on all nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11107) MVCC: IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodes hangs sometimes
[
https://issues.apache.org/jira/browse/IGNITE-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786561#comment-16786561
]
Andrew Mashenkov commented on IGNITE-11107:
---
Looks like we have no test for Transactional caches with loss policy configured
at all.
This means such case is not tested well and can be broken.
Let's fix loss policy for TX cache at first (or adapt tests for tx cache if
needed).
> MVCC:
> IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodes
> hangs sometimes
> ---
>
> Key: IGNITE-11107
> URL: https://issues.apache.org/jira/browse/IGNITE-11107
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: Hanging, mvcc_stabilization_stage_1
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Sometimes
> IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodes
> hangs on PME. Some partitions have not changed their state from {{RENTING}}
> to {{OWNING}}.
> {noformat}
> [2019-01-27 07:20:23,420][WARN
> ][test-runner-#32729%distributed.IgniteCachePartitionLossPolicySelfTest%][root]
> Finished waiting for topology map update
> [igniteInstanceName=distributed.IgniteCachePartitionLossPolicySelfTest4, p=0,
> duration=1415ms]
> [2019-01-27 07:20:23,421][WARN
> ][test-runner-#32729%distributed.IgniteCachePartitionLossPolicySelfTest%][root]
> Waiting for correct partition state part=2, should be OWNING
> [state=RENTING], node=distributed.IgniteCachePartitionLossPolicySelfTest4,
> cache=default
> [2019-01-27 07:20:25,023][WARN
> ][test-runner-#32729%distributed.IgniteCachePartitionLossPolicySelfTest%][root]
> Waiting for correct partition state part=13, should be OWNING
> [state=RENTING], node=distributed.IgniteCachePartitionLossPolicySelfTest4,
> cache=default
> Thread
> [name="test-runner-#32729%distributed.IgniteCachePartitionLossPolicySelfTest%",
> id=35714, state=RUNNABLE, blockCnt=93, waitCnt=1033]
> at sun.management.ThreadImpl.dumpThreads0(Native Method)
> at sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:454)
> at o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1370)
> at
> o.a.i.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:792)
> at
> o.a.i.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:569)
> at
> o.a.i.i.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.checkLostPartition(IgniteCachePartitionLossPolicySelfTest.java:560)
> at
> o.a.i.i.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodes(IgniteCachePartitionLossPolicySelfTest.java:258)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> o.a.i.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10900) Print a warning if native persistence is used without an explicit consistent ID
[ https://issues.apache.org/jira/browse/IGNITE-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10900: -- Fix Version/s: 2.8 > Print a warning if native persistence is used without an explicit consistent > ID > --- > > Key: IGNITE-10900 > URL: https://issues.apache.org/jira/browse/IGNITE-10900 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Experience shows that when Native Persistence is enabled, it is better to > explicitly set ConsistentIDs than use the autogenerated ones. > First, it simplifies managing the baseline topology. It is much easier to > manage it via control.sh when the nodes have stable and meaningful names. > Second, it helps to avoid certain shoot-yourself-in-the-foot issues. E.g. if > one loses all the data of a baseline node, when that node is restarted it > doesn't have its old autogenerated consistent ID - so it is not a part of the > baseline anymore. This may be unexpected and confusing. > Finally, having explicit consistent IDs improves the general stability of the > setup - one knows what the the set of nodes, where they run and what they're > called. > All in all, it seems beneficial to urge users to explicitly configure > consistent IDs. We can do this by introducing a warning that is printed every > time a new consistent ID is automatically generated. It should also be > printed when a node doesn't have an explicit consistent ID and picks up one > from an existing peristence folder. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10900) Print a warning if native persistence is used without an explicit consistent ID
[ https://issues.apache.org/jira/browse/IGNITE-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10900: -- Ignite Flags: (was: Docs Required) > Print a warning if native persistence is used without an explicit consistent > ID > --- > > Key: IGNITE-10900 > URL: https://issues.apache.org/jira/browse/IGNITE-10900 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Experience shows that when Native Persistence is enabled, it is better to > explicitly set ConsistentIDs than use the autogenerated ones. > First, it simplifies managing the baseline topology. It is much easier to > manage it via control.sh when the nodes have stable and meaningful names. > Second, it helps to avoid certain shoot-yourself-in-the-foot issues. E.g. if > one loses all the data of a baseline node, when that node is restarted it > doesn't have its old autogenerated consistent ID - so it is not a part of the > baseline anymore. This may be unexpected and confusing. > Finally, having explicit consistent IDs improves the general stability of the > setup - one knows what the the set of nodes, where they run and what they're > called. > All in all, it seems beneficial to urge users to explicitly configure > consistent IDs. We can do this by introducing a warning that is printed every > time a new consistent ID is automatically generated. It should also be > printed when a node doesn't have an explicit consistent ID and picks up one > from an existing peristence folder. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11431) SQL: Create a view with list of existing SCHEMAS
[
https://issues.apache.org/jira/browse/IGNITE-11431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786551#comment-16786551
]
Ignite TC Bot commented on IGNITE-11431:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3249946&buildTypeId=IgniteTests24Java8_RunAll]
> SQL: Create a view with list of existing SCHEMAS
>
>
> Key: IGNITE-11431
> URL: https://issues.apache.org/jira/browse/IGNITE-11431
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need to create a system view of currently available SQL schemas.
> Minimal required information is Schema name
> May be considered the follow info:
> 1) flag system or user schema
> 2) number of usages a schema.
> Starting point: {{SqlSystemView}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11434) SQL: Create a view with list of existing COLUMNS
[ https://issues.apache.org/jira/browse/IGNITE-11434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786548#comment-16786548 ] Taras Ledkov commented on IGNITE-11434: --- [~jooger], [~vozerov] make sense. e.g.: PostgreSQL & MS SQL provide no information about PK & indexes at the COLUMNS view, > SQL: Create a view with list of existing COLUMNS > > > Key: IGNITE-11434 > URL: https://issues.apache.org/jira/browse/IGNITE-11434 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Taras Ledkov >Priority: Major > Labels: iep-29 > Time Spent: 10m > Remaining Estimate: 0h > > Need to expose SQL system view with COLUMNS information. > Need to investigate more deeper which of information should be there. > > As start point we can take > [https://dev.mysql.com/doc/refman/8.0/en/columns-table.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11502) Django engine
Nikolai Svistov created IGNITE-11502: Summary: Django engine Key: IGNITE-11502 URL: https://issues.apache.org/jira/browse/IGNITE-11502 Project: Ignite Issue Type: New Feature Reporter: Nikolai Svistov Django supports a standard driver for working with DB. To work with cassandra, there is a driver - [Django Cassandra Engine|https://github.com/r4fek/django-cassandra-engine], but Apache Ignite doesn’t have a driver that allows users to work with Ignite from Django. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11417) Get rid of CacheRebalanceMode#NONE
[
https://issues.apache.org/jira/browse/IGNITE-11417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-11417:
Ignite Flags: Docs Required
> Get rid of CacheRebalanceMode#NONE
> --
>
> Key: IGNITE-11417
> URL: https://issues.apache.org/jira/browse/IGNITE-11417
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Roman Kondakov
>Priority: Major
> Fix For: 3.0
>
>
> We should get rid of erroneous and unusable rebalance mode {{NONE}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11428) Schemas don't show in Dbeaver
[
https://issues.apache.org/jira/browse/IGNITE-11428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786528#comment-16786528
]
Ignite TC Bot commented on IGNITE-11428:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3249592&buildTypeId=IgniteTests24Java8_RunAll]
> Schemas don't show in Dbeaver
> -
>
> Key: IGNITE-11428
> URL: https://issues.apache.org/jira/browse/IGNITE-11428
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> At Database navigator tab we can see just single schema PUBLIC. Need to add
> to jdbc driver support show all schemas except INFORMATIONAL, due to it H2
> schema and contains incorrect information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11500) Web Console: All emails to user should have template
[ https://issues.apache.org/jira/browse/IGNITE-11500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786515#comment-16786515 ] Alexey Kuznetsov commented on IGNITE-11500: --- Looks good to me. > Web Console: All emails to user should have template > > > Key: IGNITE-11500 > URL: https://issues.apache.org/jira/browse/IGNITE-11500 > Project: Ignite > Issue Type: Improvement > Components: wizards >Affects Versions: 2.7 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11500) Web Console: All emails to user should have template
[ https://issues.apache.org/jira/browse/IGNITE-11500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-11500: -- Ignite Flags: (was: Docs Required) > Web Console: All emails to user should have template > > > Key: IGNITE-11500 > URL: https://issues.apache.org/jira/browse/IGNITE-11500 > Project: Ignite > Issue Type: Improvement > Components: wizards >Affects Versions: 2.7 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11501) Build examples failed with Scala profile and Java11
[
https://issues.apache.org/jira/browse/IGNITE-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11501:
---
Description:
Import in IDEA {{examples/pom.xml}} with {{scala}} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.199 s
[INFO] Finished at: 2019-03-07T11:17:10+03:00
[INFO] Final Memory: 18M/67M
[INFO]
[ERROR] Failed to execute goal on project ignite-examples: Could not resolve
dependencies for project org.apache.ignite:ignite-examples:jar:2.7.0: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
C:\Java\open-jdk-11.0.1/../lib/tools.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
{noformat}
was:
Import in IDEA examples}/pom.xml with {{ scala }} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO]
[jira] [Assigned] (IGNITE-11500) Web Console: All emails to user should have template
[ https://issues.apache.org/jira/browse/IGNITE-11500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-11500: --- Assignee: Andrey Novikov > Web Console: All emails to user should have template > > > Key: IGNITE-11500 > URL: https://issues.apache.org/jira/browse/IGNITE-11500 > Project: Ignite > Issue Type: Improvement > Components: wizards >Affects Versions: 2.7 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11501) Build examples failed with Scala profile and Java11
[
https://issues.apache.org/jira/browse/IGNITE-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11501:
---
Description:
Import in IDEA examples}/pom.xml with {{ scala }} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.199 s
[INFO] Finished at: 2019-03-07T11:17:10+03:00
[INFO] Final Memory: 18M/67M
[INFO]
[ERROR] Failed to execute goal on project ignite-examples: Could not resolve
dependencies for project org.apache.ignite:ignite-examples:jar:2.7.0: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
C:\Java\open-jdk-11.0.1/../lib/tools.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
{noformat}
was:
Import in IDEA {{ examples}/pom.xml }} with {{ scala }} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[I
[jira] [Updated] (IGNITE-11501) Build examples failed with Scala profile and Java11
[
https://issues.apache.org/jira/browse/IGNITE-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11501:
---
Description:
Import in IDEA {{ examples}/pom.xml }} with {{ scala }} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.199 s
[INFO] Finished at: 2019-03-07T11:17:10+03:00
[INFO] Final Memory: 18M/67M
[INFO]
[ERROR] Failed to execute goal on project ignite-examples: Could not resolve
dependencies for project org.apache.ignite:ignite-examples:jar:2.7.0: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
C:\Java\open-jdk-11.0.1/../lib/tools.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
{noformat}
was:
Import in IDEA {{examples}/pom.xml}} with {{scala}} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[jira] [Updated] (IGNITE-11501) Build examples failed with Scala profile and Java11
[
https://issues.apache.org/jira/browse/IGNITE-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-11501:
---
Description:
Import in IDEA {{examples}/pom.xml}} with {{scala}} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.199 s
[INFO] Finished at: 2019-03-07T11:17:10+03:00
[INFO] Final Memory: 18M/67M
[INFO]
[ERROR] Failed to execute goal on project ignite-examples: Could not resolve
dependencies for project org.apache.ignite:ignite-examples:jar:2.7.0: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
C:\Java\open-jdk-11.0.1/../lib/tools.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
{noformat}
was:
Import in IDEA {{examples}/pom.xml} with {{scala}} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO
[jira] [Created] (IGNITE-11501) Build examples failed with Scala profile and Java11
Sergey Kozlov created IGNITE-11501:
--
Summary: Build examples failed with Scala profile and Java11
Key: IGNITE-11501
URL: https://issues.apache.org/jira/browse/IGNITE-11501
Project: Ignite
Issue Type: Bug
Components: examples
Affects Versions: 2.7
Environment: Open JDK 11.0.1, Windows 10 64bit
Reporter: Sergey Kozlov
Import in IDEA {{examples}/pom.xml} with {{scala}} profile.
The compilation failed:
{noformat}
C:\Java\open-jdk-11.0.1\bin\java.exe
-Dmaven.multiModuleProjectDirectory=C:\Work\apache-ignite-2.7.0-bin\examples
"-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\lib\idea_rt.jar=52182:C:\Program Files\JetBrains\IntelliJ IDEA
Community Edition 2018.3.5\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program
Files\JetBrains\IntelliJ IDEA Community Edition
2018.3.5\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar"
org.codehaus.classworlds.Launcher -Didea.version=2018.3.5 compile -P scala
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.ignite:ignite-examples:jar:2.7.0
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 204, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
[INFO] Building ignite-examples 2.7.0
[INFO]
Downloading:
http://h2database.com/m2-repo/commons-codec/commons-codec/maven-metadata.xml
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.199 s
[INFO] Finished at: 2019-03-07T11:17:10+03:00
[INFO] Final Memory: 18M/67M
[INFO]
[ERROR] Failed to execute goal on project ignite-examples: Could not resolve
dependencies for project org.apache.ignite:ignite-examples:jar:2.7.0: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
C:\Java\open-jdk-11.0.1/../lib/tools.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
