[jira] [Resolved] (IGNITE-12470) Pme-free switch feature should be deactivatable
[ https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-12470. --- Resolution: Fixed > Pme-free switch feature should be deactivatable > --- > > Key: IGNITE-12470 > URL: https://issues.apache.org/jira/browse/IGNITE-12470 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Blocker > Labels: newbie > Fix For: 2.8, 2.9 > > Time Spent: 5.5h > Remaining Estimate: 0h > > We should be able to disable this feature by some env/jvm property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12470) Pme-free switch feature should be deactivatable
[ https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024878#comment-17024878 ] Anton Vinogradov commented on IGNITE-12470: --- Merged to ignite-2.8 branch. > Pme-free switch feature should be deactivatable > --- > > Key: IGNITE-12470 > URL: https://issues.apache.org/jira/browse/IGNITE-12470 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Blocker > Labels: newbie > Fix For: 2.8, 2.9 > > Time Spent: 5.5h > Remaining Estimate: 0h > > We should be able to disable this feature by some env/jvm property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12470) Pme-free switch feature should be deactivatable
[
https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024875#comment-17024875
]
Ignite TC Bot commented on IGNITE-12470:
{panel:title=Branch: [pull/7314/head] Base: [pull/7102/head] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4963776&buildTypeId=IgniteTests24Java8_RunAll]
> Pme-free switch feature should be deactivatable
> ---
>
> Key: IGNITE-12470
> URL: https://issues.apache.org/jira/browse/IGNITE-12470
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Blocker
> Labels: newbie
> Fix For: 2.8, 2.9
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> We should be able to disable this feature by some env/jvm property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12554) Ignite instance couldn't be restarted if it's parent thread group has been called destroy once
[
https://issues.apache.org/jira/browse/IGNITE-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024832#comment-17024832
]
ha faculty commented on IGNITE-12554:
-
[~Pavlukhin] Thanks
> Ignite instance couldn't be restarted if it's parent thread group has been
> called destroy once
> --
>
> Key: IGNITE-12554
> URL: https://issues.apache.org/jira/browse/IGNITE-12554
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7.6
>Reporter: ha faculty
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.9
>
> Attachments: NodeRestartTesting.java
>
>
> I am using an inhouse platform which manage the life cycle of ignite instance
> by calling ignition.start() and ignition.stop() from a web application.
> it could be started without issue for the first time. however, if it stop the
> ignite by calling ignition.stop() and followed by destroying the parent
> thread group which starting it.
> Calling ignition.start() in the 2nd time will throw the following exception
> Exception in thread "kickOff" java.lang.IllegalThreadStateExceptionException
> in thread "kickOff" java.lang.IllegalThreadStateException at
> java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:867) at
> java.lang.Thread.init(Thread.java:405) at
> java.lang.Thread.init(Thread.java:349) at
> java.lang.Thread.(Thread.java:599) at
> org.apache.ignite.thread.IgniteThread.(IgniteThread.java:96) at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.start(StripedExecutor.java:474)
> at
> org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:121)
> at
> org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:80)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1842)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:565) at
> org.apache.ignite.Ignition.start(Ignition.java:305) at
> com.faculty.poc.ignite.app.NodeRestartTesting.run(NodeRestartTesting.java:60)
> at java.lang.Thread.run(Thread.java:748)
> Please find my demo code for this issue.
> Walk through into Ignite code, it should be caused by a static thread group
> created in IgniteThread class. (private static final ThreadGroup DFLT_GRP =
> new ThreadGroup("ignite")
> Destroyed the parent thread group which start the ignite instance will result
> in causing the DFLT_GRP go into destroyed state. Therefore, when Ignite was
> start ifor the 2nd time, this static thread group has been destroyed and no
> longer able to run the ignite.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12580) NPE in GridMetricManager
[
https://issues.apache.org/jira/browse/IGNITE-12580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12580:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> NPE in GridMetricManager
>
>
> Key: IGNITE-12580
> URL: https://issues.apache.org/jira/browse/IGNITE-12580
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Scherbakov
>Assignee: Nikolay Izhikov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> NPE is thrown during cache recovery:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7534)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:234)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:152)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStart(GridCachePartitionExchangeManager.java:816)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:675)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1375)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:615)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:1017)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:958)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:946)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:895)
> at
> org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.doTestSimple(LocalWalModeChangeDuringRebalancingSelfTest.java:263)
> at
> org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.testWalDisabledDuringRebalancing(LocalWalModeChangeDuringRebalancingSelfTest.java:234)
> 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$7.run(GridAbstractTest.java:2124)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.remove(GridMetricManager.java:396)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.stop(GridCacheAdapter.java:669)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1024)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:998)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:754)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onBaselineChange(GridCacheProcessor.java:5460)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:982)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:849)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3236)
> at
> org.apache.ignite.internal.processors.cac
[jira] [Created] (IGNITE-12586) Calcite integration. NodesMapping simplification.
Igor Seliverstov created IGNITE-12586:
-
Summary: Calcite integration. NodesMapping simplification.
Key: IGNITE-12586
URL: https://issues.apache.org/jira/browse/IGNITE-12586
Project: Ignite
Issue Type: Improvement
Reporter: Igor Seliverstov
Seems turning {{List assignments}} to {{Map
assignments}} may significantly reduce occupied memory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12585) Calcite integration. Splitter improvements.
Igor Seliverstov created IGNITE-12585: - Summary: Calcite integration. Splitter improvements. Key: IGNITE-12585 URL: https://issues.apache.org/jira/browse/IGNITE-12585 Project: Ignite Issue Type: Improvement Reporter: Igor Seliverstov Currently in case a head fragment of a query plan have broadcast distribution it causes OptimisticPlanningException and additional fragment split each time it's mapped on topology on a client node. Seems it's quite usual case, so, we should cover it properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12554) Ignite instance couldn't be restarted if it's parent thread group has been called destroy once
[
https://issues.apache.org/jira/browse/IGNITE-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024543#comment-17024543
]
Ignite TC Bot commented on IGNITE-12554:
{panel:title=Branch: [pull/7297/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4963617&buildTypeId=IgniteTests24Java8_RunAll]
> Ignite instance couldn't be restarted if it's parent thread group has been
> called destroy once
> --
>
> Key: IGNITE-12554
> URL: https://issues.apache.org/jira/browse/IGNITE-12554
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7.6
>Reporter: ha faculty
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.9
>
> Attachments: NodeRestartTesting.java
>
>
> I am using an inhouse platform which manage the life cycle of ignite instance
> by calling ignition.start() and ignition.stop() from a web application.
> it could be started without issue for the first time. however, if it stop the
> ignite by calling ignition.stop() and followed by destroying the parent
> thread group which starting it.
> Calling ignition.start() in the 2nd time will throw the following exception
> Exception in thread "kickOff" java.lang.IllegalThreadStateExceptionException
> in thread "kickOff" java.lang.IllegalThreadStateException at
> java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:867) at
> java.lang.Thread.init(Thread.java:405) at
> java.lang.Thread.init(Thread.java:349) at
> java.lang.Thread.(Thread.java:599) at
> org.apache.ignite.thread.IgniteThread.(IgniteThread.java:96) at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.start(StripedExecutor.java:474)
> at
> org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:121)
> at
> org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:80)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1842)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:565) at
> org.apache.ignite.Ignition.start(Ignition.java:305) at
> com.faculty.poc.ignite.app.NodeRestartTesting.run(NodeRestartTesting.java:60)
> at java.lang.Thread.run(Thread.java:748)
> Please find my demo code for this issue.
> Walk through into Ignite code, it should be caused by a static thread group
> created in IgniteThread class. (private static final ThreadGroup DFLT_GRP =
> new ThreadGroup("ignite")
> Destroyed the parent thread group which start the ignite instance will result
> in causing the DFLT_GRP go into destroyed state. Therefore, when Ignite was
> start ifor the 2nd time, this static thread group has been destroyed and no
> longer able to run the ignite.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12534) [Spark] The spark 2.4 is not found in optional folder
[ https://issues.apache.org/jira/browse/IGNITE-12534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024524#comment-17024524 ] Pavel Tupitsyn commented on IGNITE-12534: - .NET NuGet build fails sporadically on TC because of the new profile. Trying to disable Scala & Spark related profiles: https://github.com/apache/ignite/pull/7318 > [Spark] The spark 2.4 is not found in optional folder > - > > Key: IGNITE-12534 > URL: https://issues.apache.org/jira/browse/IGNITE-12534 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.8 >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Major > Fix For: 2.8 > > Time Spent: 50m > Remaining Estimate: 0h > > The bug from dev-list: > [http://apache-ignite-developers.2346864.n4.nabble.com/Re-How-to-use-spark-2-4-module-in-Ignite-2-8-td44773.html#a45020] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12493) Test refactoring. Explicit method for starting client nodes
[
https://issues.apache.org/jira/browse/IGNITE-12493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024482#comment-17024482
]
PetrovMikhail commented on IGNITE-12493:
LGTM
> Test refactoring. Explicit method for starting client nodes
> ---
>
> Key: IGNITE-12493
> URL: https://issues.apache.org/jira/browse/IGNITE-12493
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: newbie
> Time Spent: 5h 50m
> Remaining Estimate: 0h
>
> Right now there is almost 500 explicit usage of {{setClientMode}} in tests.
> Seems we should support the starting of client nodes in test framework.
> We should refactor tests to use {{startClientNode(String name)}}.
> This will simplify tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12580) NPE in GridMetricManager
[
https://issues.apache.org/jira/browse/IGNITE-12580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-12580:
-
Fix Version/s: (was: 2.9)
2.8
> NPE in GridMetricManager
>
>
> Key: IGNITE-12580
> URL: https://issues.apache.org/jira/browse/IGNITE-12580
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Scherbakov
>Assignee: Nikolay Izhikov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> NPE is thrown during cache recovery:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7534)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:234)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:152)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStart(GridCachePartitionExchangeManager.java:816)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:675)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1375)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:615)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:1017)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:958)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:946)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:895)
> at
> org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.doTestSimple(LocalWalModeChangeDuringRebalancingSelfTest.java:263)
> at
> org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.testWalDisabledDuringRebalancing(LocalWalModeChangeDuringRebalancingSelfTest.java:234)
> 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$7.run(GridAbstractTest.java:2124)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.remove(GridMetricManager.java:396)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.stop(GridCacheAdapter.java:669)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1024)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:998)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:754)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onBaselineChange(GridCacheProcessor.java:5460)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:982)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:849)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3236)
> at
> org.apache.ignite.internal.processors.cache.Gri
[jira] [Updated] (IGNITE-12580) NPE in GridMetricManager
[
https://issues.apache.org/jira/browse/IGNITE-12580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-12580:
-
Priority: Blocker (was: Critical)
> NPE in GridMetricManager
>
>
> Key: IGNITE-12580
> URL: https://issues.apache.org/jira/browse/IGNITE-12580
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Scherbakov
>Assignee: Nikolay Izhikov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> NPE is thrown during cache recovery:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7534)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:234)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:152)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStart(GridCachePartitionExchangeManager.java:816)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:675)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1375)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:615)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:1017)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:958)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:946)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:895)
> at
> org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.doTestSimple(LocalWalModeChangeDuringRebalancingSelfTest.java:263)
> at
> org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.testWalDisabledDuringRebalancing(LocalWalModeChangeDuringRebalancingSelfTest.java:234)
> 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$7.run(GridAbstractTest.java:2124)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.remove(GridMetricManager.java:396)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.stop(GridCacheAdapter.java:669)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1024)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:998)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:754)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onBaselineChange(GridCacheProcessor.java:5460)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:982)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:849)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3236)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExch
[jira] [Commented] (IGNITE-12580) NPE in GridMetricManager
[
https://issues.apache.org/jira/browse/IGNITE-12580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024446#comment-17024446
]
Nikolay Izhikov commented on IGNITE-12580:
--
Hello, [~ascherbakov]
Can you, please, take a look at the fix [1]
[1] https://github.com/apache/ignite/pull/7317/files
> NPE in GridMetricManager
>
>
> Key: IGNITE-12580
> URL: https://issues.apache.org/jira/browse/IGNITE-12580
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Scherbakov
>Assignee: Nikolay Izhikov
>Priority: Critical
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> NPE is thrown during cache recovery:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7534)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:234)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:152)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStart(GridCachePartitionExchangeManager.java:816)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:675)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1375)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:615)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:1017)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:958)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:946)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:895)
> at
> org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.doTestSimple(LocalWalModeChangeDuringRebalancingSelfTest.java:263)
> at
> org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.testWalDisabledDuringRebalancing(LocalWalModeChangeDuringRebalancingSelfTest.java:234)
> 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$7.run(GridAbstractTest.java:2124)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.remove(GridMetricManager.java:396)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.stop(GridCacheAdapter.java:669)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1024)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:998)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:754)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onBaselineChange(GridCacheProcessor.java:5460)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:982)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:849)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$Exch
[jira] [Comment Edited] (IGNITE-7913) Current implementation of Internal Diagnostics may cause OOM on server nodes.
[
https://issues.apache.org/jira/browse/IGNITE-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024440#comment-17024440
]
Igor Kamyshnikov edited comment on IGNITE-7913 at 1/27/20 3:43 PM:
---
The same on Ignite 2.7.6. At least the way to disable the execution of the
logic of
org.apache.ignite.internal.IgniteDiagnosticPrepareContext.CompoundInfoClosure#apply
is required (or some throttling)
It does not seem that the configuration property 'IGNITE_DIAGNOSTIC_ENABLED'
disables all the diag tasks (e.g. TX problems)
The test case leading to the sys-# pool thread starvation:
1) take a cluster of several ignite server nodes (3 or 5) and backups=1
2) load it with a lot of concurrent put requests
3) kill one node and immediately restart it
There are chances that the *Latch release* message coming from the client will
be processed on the server *in several minutes* because the sys-# pool is busy
with diagnostic messages. Not receiving the *latch release* message in time
leads to failed SQL queries.
was (Author: kamyshnikov):
The same on Ignite 2.7.6. At least the way to disable the execution of the
logic of
org.apache.ignite.internal.IgniteDiagnosticPrepareContext.CompoundInfoClosure#apply
is required.
It does not seem that the configuration property 'IGNITE_DIAGNOSTIC_ENABLED'
disables all the diag tasks (e.g. TX problems)
The test case leading to the sys-# pool thread starvation:
1) take a cluster of several ignite server nodes (3 or 5) and backups=1
2) load it with a lot of concurrent put requests
3) kill one node and immediately restart it
There are chances that the *Latch release* message coming from the client will
be processed on the server *in several minutes* because the sys-# pool is busy
with diagnostic messages. Not receiving the *latch release* message in time
leads to failed SQL queries.
> Current implementation of Internal Diagnostics may cause OOM on server nodes.
> -
>
> Key: IGNITE-7913
> URL: https://issues.apache.org/jira/browse/IGNITE-7913
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.3
>Reporter: Alexey Scherbakov
>Priority: Major
> Fix For: 2.9
>
>
> If many transactions are active in grid, Internal Diagnostics can cause OOM
> on server nodes serving IgniteDiagnosticMessage because of heap buffering.
> See the stack trace demonstrating the issue:
> {noformat}
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1012)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:762)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:710)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.toString(GridDhtCacheEntry.java:818)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:939)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1005)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxEntry.toString(IgniteTxEntry.java:1267)
> at java.lang.String.valueOf(String.java:2994)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at java.util.AbstractMap.toString(AbstractMap.java:559)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:939)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1005)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:864)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxRemoteStateImpl.toString(IgniteTxRemoteStateImpl.java:180)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.in
[jira] [Commented] (IGNITE-7913) Current implementation of Internal Diagnostics may cause OOM on server nodes.
[
https://issues.apache.org/jira/browse/IGNITE-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024440#comment-17024440
]
Igor Kamyshnikov commented on IGNITE-7913:
--
The same on Ignite 2.7.6. At least the way to disable the execution of the
logic of
org.apache.ignite.internal.IgniteDiagnosticPrepareContext.CompoundInfoClosure#apply
is required.
It does not seem that the configuration property 'IGNITE_DIAGNOSTIC_ENABLED'
disables all the diag tasks (e.g. TX problems)
The test case leading to the sys-# pool thread starvation:
1) take a cluster of several ignite server nodes (3 or 5) and backups=1
2) load it with a lot of concurrent put requests
3) kill one node and immediately restart it
There are chances that the *Latch release* message coming from the client will
be processed on the server *in several minutes* because the sys-# pool is busy
with diagnostic messages. Not receiving the *latch release* message in time
leads to failed SQL queries.
> Current implementation of Internal Diagnostics may cause OOM on server nodes.
> -
>
> Key: IGNITE-7913
> URL: https://issues.apache.org/jira/browse/IGNITE-7913
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.3
>Reporter: Alexey Scherbakov
>Priority: Major
> Fix For: 2.9
>
>
> If many transactions are active in grid, Internal Diagnostics can cause OOM
> on server nodes serving IgniteDiagnosticMessage because of heap buffering.
> See the stack trace demonstrating the issue:
> {noformat}
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1012)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:762)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:710)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.toString(GridDhtCacheEntry.java:818)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:939)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1005)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxEntry.toString(IgniteTxEntry.java:1267)
> at java.lang.String.valueOf(String.java:2994)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at java.util.AbstractMap.toString(AbstractMap.java:559)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:939)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1005)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:864)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxRemoteStateImpl.toString(IgniteTxRemoteStateImpl.java:180)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:939)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1005)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.toString(GridDistributedTxRemoteAdapter.java:926)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxRemote.toString(GridDhtTxRemote.j
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024407#comment-17024407 ] Ryabov Dmitrii commented on IGNITE-12049: - [~ascherbakov], I restricted attributes by `String` class as suggested on discussion. > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 2h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12577) High persistence load can trigger erroneous assert: "Page was pin when we resolve abs pointer, it can not be evicted".
[ https://issues.apache.org/jira/browse/IGNITE-12577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024301#comment-17024301 ] Stanilovsky Evgeny commented on IGNITE-12577: - I really don`t know what additional tests need here, this reproduces rarely on persistent storage high load. [~akalashnikov] may be you have some comments here? > High persistence load can trigger erroneous assert: "Page was pin when we > resolve abs pointer, it can not be evicted". > -- > > Key: IGNITE-12577 > URL: https://issues.apache.org/jira/browse/IGNITE-12577 > Project: Ignite > Issue Type: Bug > Components: data structures >Affects Versions: 2.7.6 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > For now It seems erroneous assertion in checkpointer code : "Page was pin > when we resolve abs pointer, it can not be evicted", need to be removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12571) Statistics of query cache statements
[
https://issues.apache.org/jira/browse/IGNITE-12571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024290#comment-17024290
]
Konstantin Orlov commented on IGNITE-12571:
---
This is pretty unobvious for me :(. Ok, I'll move it to
{{IgniteBinaryCacheQueryTestSuite}}.
> Statistics of query cache statements
>
>
> Key: IGNITE-12571
> URL: https://issues.apache.org/jira/browse/IGNITE-12571
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need to collect hit/miss statistics for the query cache.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
[
https://issues.apache.org/jira/browse/IGNITE-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12573:
--
Fix Version/s: 2.8
> Copy ML dependencies to other standalone pom files in examples
> ---
>
> Key: IGNITE-12573
> URL: https://issues.apache.org/jira/browse/IGNITE-12573
> Project: Ignite
> Issue Type: Task
> Components: examples
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.8
>
>
> 2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
> {code}
>
> org.apache.ignite
> ignite-ml-tensorflow-model-parser
> ${project.version}
>
>
> org.apache.ignite
> ignite-ml-h2o-model-parser
> ${project.version}
>
> {code}
> Need to copy this libraries from original pom.xml because examples in
> released build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
[
https://issues.apache.org/jira/browse/IGNITE-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12573:
--
Fix Version/s: (was: 2.8)
> Copy ML dependencies to other standalone pom files in examples
> ---
>
> Key: IGNITE-12573
> URL: https://issues.apache.org/jira/browse/IGNITE-12573
> Project: Ignite
> Issue Type: Task
> Components: examples
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Goncharuk
>Priority: Critical
>
> 2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
> {code}
>
> org.apache.ignite
> ignite-ml-tensorflow-model-parser
> ${project.version}
>
>
> org.apache.ignite
> ignite-ml-h2o-model-parser
> ${project.version}
>
> {code}
> Need to copy this libraries from original pom.xml because examples in
> released build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12576) [IEP-35] TCP communication metrics use node ID instead of consistent ID
[
https://issues.apache.org/jira/browse/IGNITE-12576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024272#comment-17024272
]
Ignite TC Bot commented on IGNITE-12576:
{panel:title=Branch: [pull/7310/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4957763&buildTypeId=IgniteTests24Java8_RunAll]
> [IEP-35] TCP communication metrics use node ID instead of consistent ID
> ---
>
> Key: IGNITE-12576
> URL: https://issues.apache.org/jira/browse/IGNITE-12576
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: IEP-35
> Time Spent: 10m
> Remaining Estimate: 0h
>
> TcpCommunicationMetricsListener uses nodeId for metrics name. consistentId
> should be used instead.
> Also all metrics for registry should be created at once before registry added
> to GridMetricManager. There is no need in separate initialization for sent
> and received counters.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12584) Query execution is too long issue!
[
https://issues.apache.org/jira/browse/IGNITE-12584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024265#comment-17024265
]
Aditya commented on IGNITE-12584:
-
The Igntie metric when the warning is thrown is as follows:
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=a7924eda, uptime=04:15:01.531]
^-- H/N/C [hosts=3, nodes=3, CPUs=16]
^-- CPU [cur=78.93%, avg=68.4%, GC=0.1%]
^-- PageMemory [pages=429194]
^-- Heap [used=754MB, free=78.68%, comm=2183MB]
^-- Off-heap [used=1696MB, free=51.32%, comm=3384MB]
^-- sysMemPlc region [used=0MB, free=99.99%, comm=100MB]
^-- default region [used=1696MB, free=46.73%, comm=3184MB]
^-- metastoreMemPlc region [used=0MB, free=99.96%, comm=0MB]
^-- TxLog region [used=0MB, free=100%, comm=100MB]
^-- Ignite persistence [used=1732MB]
^-- sysMemPlc region [used=0MB]
^-- default region [used=1732MB]
^-- metastoreMemPlc region [used=0MB]
^-- TxLog region [used=0MB]
^-- Outbound messages queue [size=0]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=0, idle=6, qSize=0]
> Query execution is too long issue!
> --
>
> Key: IGNITE-12584
> URL: https://issues.apache.org/jira/browse/IGNITE-12584
> Project: Ignite
> Issue Type: Bug
>Reporter: Aditya
>Priority: Major
> Attachments: uploadthis.txt
>
>
> When querying via some java application and if the topology is in such a way
> that two clients connect to one server node, then some times we are getting
> an exception saying query execution is too long.
>
> This is the SQL schema for table
>
> stmt.executeUpdate("CREATE TABLE DOCIDS (" +
> " id LONG PRIMARY KEY, url VARCHAR, score LONG, appname VARCHAR) " +
> " WITH \"template=replicated\"");
>
> stmt.executeUpdate("CREATE INDEX idx_doc_name_url ON DOCIDS (appname, url)");
>
> Query ->
> SqlFieldsQuery query = new SqlFieldsQuery("SELECT count(id) FROM DOCIDS");
> FieldsQueryCursor> cursor = cache.query(query);
> For warning prints, please check the attachment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12584) Query execution is too long issue!
Aditya created IGNITE-12584:
---
Summary: Query execution is too long issue!
Key: IGNITE-12584
URL: https://issues.apache.org/jira/browse/IGNITE-12584
Project: Ignite
Issue Type: Bug
Reporter: Aditya
Attachments: uploadthis.txt
When querying via some java application and if the topology is in such a way
that two clients connect to one server node, then some times we are getting an
exception saying query execution is too long.
This is the SQL schema for table
stmt.executeUpdate("CREATE TABLE DOCIDS (" +
" id LONG PRIMARY KEY, url VARCHAR, score LONG, appname VARCHAR) " +
" WITH \"template=replicated\"");
stmt.executeUpdate("CREATE INDEX idx_doc_name_url ON DOCIDS (appname, url)");
Query ->
SqlFieldsQuery query = new SqlFieldsQuery("SELECT count(id) FROM DOCIDS");
FieldsQueryCursor> cursor = cache.query(query);
For warning prints, please check the attachment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12583) Parametrization of JdbcThinBulkLoadAbstractSelfTest
Vladimir Steshin created IGNITE-12583:
-
Summary: Parametrization of JdbcThinBulkLoadAbstractSelfTest
Key: IGNITE-12583
URL: https://issues.apache.org/jira/browse/IGNITE-12583
Project: Ignite
Issue Type: Sub-task
Reporter: Vladimir Steshin
Assignee: Vladimir Steshin
org.apache.ignite.jdbc.thin.JdbcThinBulkLoadAbstractSelfTest is extended
several times using just parameter-assigning-getters like
{code:java}
protected CacheMode cacheMode() { return CacheMode.REPLICATED; }
protected CacheAtomicityMode atomicityMode() { return
CacheAtomicityMode.TRANSACTIONAL;}
protected boolean nearCache() { return false; }
{code}
Should go with params instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12571) Statistics of query cache statements
[
https://issues.apache.org/jira/browse/IGNITE-12571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024234#comment-17024234
]
Ivan Pavlukhin commented on IGNITE-12571:
-
[~korlov], {{IgniteCacheQuerySelfTestSuite6}} on TC is Continuous Query 4.
There is already a couple of misplaced tests. It is better to place SQL tests
into {{IgniteBinaryCacheQueryTestSuite}} or
{{IgniteBinaryCacheQueryTestSuite2}}. Check if one of them has already
statistics/metrics tests.
> Statistics of query cache statements
>
>
> Key: IGNITE-12571
> URL: https://issues.apache.org/jira/browse/IGNITE-12571
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need to collect hit/miss statistics for the query cache.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12470) Pme-free switch feature should be deactivatable
[ https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024232#comment-17024232 ] Anton Vinogradov commented on IGNITE-12470: --- [~mmuzaf] Sure, PR check is in progress. > Pme-free switch feature should be deactivatable > --- > > Key: IGNITE-12470 > URL: https://issues.apache.org/jira/browse/IGNITE-12470 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Blocker > Labels: newbie > Fix For: 2.8, 2.9 > > Time Spent: 5h 20m > Remaining Estimate: 0h > > We should be able to disable this feature by some env/jvm property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12571) Statistics of query cache statements
[ https://issues.apache.org/jira/browse/IGNITE-12571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024230#comment-17024230 ] Konstantin Orlov commented on IGNITE-12571: --- [~Pavlukhin], I've added the test to the suite. Please look again. > Statistics of query cache statements > > > Key: IGNITE-12571 > URL: https://issues.apache.org/jira/browse/IGNITE-12571 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > We need to collect hit/miss statistics for the query cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12571) Statistics of query cache statements
[
https://issues.apache.org/jira/browse/IGNITE-12571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024226#comment-17024226
]
Ignite TC Bot commented on IGNITE-12571:
{panel:title=Branch: [pull/7299/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4954467&buildTypeId=IgniteTests24Java8_RunAll]
> Statistics of query cache statements
>
>
> Key: IGNITE-12571
> URL: https://issues.apache.org/jira/browse/IGNITE-12571
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need to collect hit/miss statistics for the query cache.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12557) Destroy of big cache which is not only cache in cache group causes IgniteOOME
[
https://issues.apache.org/jira/browse/IGNITE-12557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024224#comment-17024224
]
Ivan Rakov commented on IGNITE-12557:
-
The fix looks good to me as a workaround.
I'm ok with merging this patch (it isn't complete, but doesn't make the
situation worse) and continuation of work on async destroy and crash recovery
guarantees under aforementioned separate tickets.
[~alex_pl] Do you agree?
> Destroy of big cache which is not only cache in cache group causes IgniteOOME
> -
>
> Key: IGNITE-12557
> URL: https://issues.apache.org/jira/browse/IGNITE-12557
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Aleksey Plekhanov
>Assignee: Alexey Scherbakov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When {{destroyCache()}} is invoked {{checkpointReadLock}} is held by exchange
> thread during all time cache entries are cleaning. Meanwhile,
> {{db-checkpoint-thread}} can't acquire checkpoint write lock and can't start
> checkpoint. After some time all page-memory has filled with dirty pages and
> attempt to acquire a new page causes IgniteOOM exception:
> {noformat}
> class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to
> find a page for eviction [segmentCapacity=40485, loaded=15881,
> maxDirtyPages=11910, dirtyPages=15881, cpPages=0, pinnedInSegment=0,
> failedToPrepare=15881]
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:2420)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.removePageForReplacement(PageMemoryImpl.java:2314)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:743)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:679)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:158)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.acquirePage(BPlusTree.java:5872)
> at
> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.compareKeys(CacheDataTree.java:435)
> at
> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.compare(CacheDataTree.java:384)
> at
> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.compare(CacheDataTree.java:63)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.compare(BPlusTree.java:5214)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findInsertionPoint(BPlusTree.java:5134)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:298)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5723)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run(BPlusTree.java:278)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5709)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:169)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.read(DataStructure.java:364)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.read(BPlusTree.java:5910)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.removeDown(BPlusTree.java:2077)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doRemove(BPlusTree.java:2007)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.removex(BPlusTree.java:1838)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.clear(IgniteCacheOffheapManagerImpl.java:2963)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.clear(GridCacheOffheapManager.java:2611)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.removeCacheData(IgniteCacheOffheapManagerImpl.java:296)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.stopCache(IgniteCacheOffheapManagerImpl.java:258)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupContext.stopCache(CacheGroupContext.java:825)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1070)
> at
> o
[jira] [Assigned] (IGNITE-12581) [REFACTORING] Tests parametrization
[ https://issues.apache.org/jira/browse/IGNITE-12581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin reassigned IGNITE-12581: - Assignee: Vladimir Steshin > [REFACTORING] Tests parametrization > --- > > Key: IGNITE-12581 > URL: https://issues.apache.org/jira/browse/IGNITE-12581 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Vladimir Steshin >Priority: Minor > > Right now many Ignite tests parametrization implemented via inheritance. > For example: > parent - JdbcThinBulkLoadAbstractSelfTest > extensions - JdbcThinBulkLoadAtomicPartitionedNearSelfTest, > JdbcThinBulkLoadAtomicPartitionedSelfTest, > JdbcThinBulkLoadAtomicReplicatedSelfTest, > JdbcThinBulkLoadTransactionalPartitionedNearSelfTest, > JdbcThinBulkLoadTransactionalPartitionedSelfTest, > JdbcThinBulkLoadTransactionalReplicatedSelfTest. > > Look like we can significantly reduce tests code base, therefore, improve > readability and maintainability without losing any test-cases if we use the > JUnit parameterized approach. > > A contributor can use this ticket as an umbrella one and create a sub-ticket > for each refactored test-classes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12470) Pme-free switch feature should be deactivatable
[ https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024223#comment-17024223 ] Maxim Muzafarov commented on IGNITE-12470: -- [~avinogradov] Should we cherry-pick it to 2.8? > Pme-free switch feature should be deactivatable > --- > > Key: IGNITE-12470 > URL: https://issues.apache.org/jira/browse/IGNITE-12470 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Blocker > Labels: newbie > Fix For: 2.8, 2.9 > > Time Spent: 5h 20m > Remaining Estimate: 0h > > We should be able to disable this feature by some env/jvm property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12067) SQL: metrics of executions of user queries
[ https://issues.apache.org/jira/browse/IGNITE-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin reassigned IGNITE-12067: --- Assignee: Ivan Pavlukhin (was: Pavel Kuznetsov) > SQL: metrics of executions of user queries > -- > > Key: IGNITE-12067 > URL: https://issues.apache.org/jira/browse/IGNITE-12067 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Pavel Kuznetsov >Assignee: Ivan Pavlukhin >Priority: Major > > Lets add: > - Counter of success executed user queries. > - Counter of failed executed user queries. > - Counter of failed by OOM executed user queries. > - Counter of cancelled user queries. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12574) Fix failing IoStatisticsBasicIndexSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-12574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024201#comment-17024201 ] Konstantin Orlov commented on IGNITE-12574: --- [~Pavlukhin], the patch looks good to me. Please proceed with merging. > Fix failing IoStatisticsBasicIndexSelfTest > -- > > Key: IGNITE-12574 > URL: https://issues.apache.org/jira/browse/IGNITE-12574 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Need to move > org.apache.ignite.internal.processors.cache.index.IoStatisticsBasicIndexSelfTest > into a test suite with enabled persistence. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
[
https://issues.apache.org/jira/browse/IGNITE-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12573:
--
Fix Version/s: 2.8
> Copy ML dependencies to other standalone pom files in examples
> ---
>
> Key: IGNITE-12573
> URL: https://issues.apache.org/jira/browse/IGNITE-12573
> Project: Ignite
> Issue Type: Task
> Components: examples
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.8
>
>
> 2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
> {code}
>
> org.apache.ignite
> ignite-ml-tensorflow-model-parser
> ${project.version}
>
>
> org.apache.ignite
> ignite-ml-h2o-model-parser
> ${project.version}
>
> {code}
> Need to copy this libraries from original pom.xml because examples in
> released build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
[
https://issues.apache.org/jira/browse/IGNITE-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12573:
--
Fix Version/s: (was: 2.8)
> Copy ML dependencies to other standalone pom files in examples
> ---
>
> Key: IGNITE-12573
> URL: https://issues.apache.org/jira/browse/IGNITE-12573
> Project: Ignite
> Issue Type: Task
> Components: examples
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Goncharuk
>Priority: Critical
>
> 2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
> {code}
>
> org.apache.ignite
> ignite-ml-tensorflow-model-parser
> ${project.version}
>
>
> org.apache.ignite
> ignite-ml-h2o-model-parser
> ${project.version}
>
> {code}
> Need to copy this libraries from original pom.xml because examples in
> released build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
[
https://issues.apache.org/jira/browse/IGNITE-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12573:
--
Fix Version/s: 2.8
> Copy ML dependencies to other standalone pom files in examples
> ---
>
> Key: IGNITE-12573
> URL: https://issues.apache.org/jira/browse/IGNITE-12573
> Project: Ignite
> Issue Type: Task
> Components: examples
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.8
>
>
> 2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
> {code}
>
> org.apache.ignite
> ignite-ml-tensorflow-model-parser
> ${project.version}
>
>
> org.apache.ignite
> ignite-ml-h2o-model-parser
> ${project.version}
>
> {code}
> Need to copy this libraries from original pom.xml because examples in
> released build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
[
https://issues.apache.org/jira/browse/IGNITE-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12573:
--
Fix Version/s: (was: 2.8)
> Copy ML dependencies to other standalone pom files in examples
> ---
>
> Key: IGNITE-12573
> URL: https://issues.apache.org/jira/browse/IGNITE-12573
> Project: Ignite
> Issue Type: Task
> Components: examples
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Goncharuk
>Priority: Critical
>
> 2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
> {code}
>
> org.apache.ignite
> ignite-ml-tensorflow-model-parser
> ${project.version}
>
>
> org.apache.ignite
> ignite-ml-h2o-model-parser
> ${project.version}
>
> {code}
> Need to copy this libraries from original pom.xml because examples in
> released build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12582) It is needed to set used cache for Spring Data by property
Sergey Chernolyas created IGNITE-12582: -- Summary: It is needed to set used cache for Spring Data by property Key: IGNITE-12582 URL: https://issues.apache.org/jira/browse/IGNITE-12582 Project: Ignite Issue Type: Improvement Components: spring Affects Versions: 2.7.6 Reporter: Sergey Chernolyas Assignee: Sergey Chernolyas Hi! My project needs to configure used cache by property, like ""[spring.data|http://spring.data/].mongodb.uri: mongodb://:@:/" from Spring Data for MongoDB. Now, I can set cache for particular repository by annotation "RepositoryConfig" only. -- This message was sent by Atlassian Jira (v8.3.4#803005)
