[jira] [Updated] (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 updated IGNITE-12067: Description: Lets add: - Counter of success executed user queries. - Counter of failed executed user queries. - Counter of cancelled user queries. was: 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. > 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 > Labels: IEP-35 > > Lets add: > - Counter of success executed user queries. > - Counter of failed executed user queries. > - Counter of cancelled user queries. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12615) Add warning that cluster deactivation purges data from memory
[ https://issues.apache.org/jira/browse/IGNITE-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-12615. - Resolution: Fixed > Add warning that cluster deactivation purges data from memory > - > > Key: IGNITE-12615 > URL: https://issues.apache.org/jira/browse/IGNITE-12615 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7.6 >Reporter: Denis A. Magda >Assignee: Artem Budnikov >Priority: Blocker > Fix For: 2.8 > > > Baseline topology [1] and control script's [2] documentation needs to have a > warning callout saying that a cluster deactivation procedure will purge data > from memory requiring users to reload data back after the activation. For > caches that persist data in the native persistence, this will happen > automatically, for all the other cases the user has to reload data manually. > [1] https://apacheignite.readme.io/docs/baseline-topology > [2] > https://apacheignite-tools.readme.io/docs/control-script#section-activation-deactivation-and-topology-management -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12615) Add warning that cluster deactivation purges data from memory
[ https://issues.apache.org/jira/browse/IGNITE-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035106#comment-17035106 ] Artem Budnikov commented on IGNITE-12615: - I added a warning to each section. > Add warning that cluster deactivation purges data from memory > - > > Key: IGNITE-12615 > URL: https://issues.apache.org/jira/browse/IGNITE-12615 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7.6 >Reporter: Denis A. Magda >Assignee: Artem Budnikov >Priority: Blocker > Fix For: 2.8 > > > Baseline topology [1] and control script's [2] documentation needs to have a > warning callout saying that a cluster deactivation procedure will purge data > from memory requiring users to reload data back after the activation. For > caches that persist data in the native persistence, this will happen > automatically, for all the other cases the user has to reload data manually. > [1] https://apacheignite.readme.io/docs/baseline-topology > [2] > https://apacheignite-tools.readme.io/docs/control-script#section-activation-deactivation-and-topology-management -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12582) It is needed to set used cache for Spring Data dynamically
[ https://issues.apache.org/jira/browse/IGNITE-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035086#comment-17035086 ] Sergey Chernolyas commented on IGNITE-12582: [~Pavlukhin] the visa has been gotten. the process is followed. > It is needed to set used cache for Spring Data dynamically > -- > > 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 >Priority: Major > Fix For: 2.8.1 > > > 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)
[jira] [Commented] (IGNITE-12582) It is needed to set used cache for Spring Data dynamically
[
https://issues.apache.org/jira/browse/IGNITE-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035083#comment-17035083
]
Ignite TC Bot commented on IGNITE-12582:
{panel:title=Branch: [pull/7411/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=5043398buildTypeId=IgniteTests24Java8_RunAll]
> It is needed to set used cache for Spring Data dynamically
> --
>
> 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
>Priority: Major
> Fix For: 2.8.1
>
>
> 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)
[jira] [Commented] (IGNITE-12582) It is needed to set used cache for Spring Data dynamically
[
https://issues.apache.org/jira/browse/IGNITE-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035022#comment-17035022
]
Ignite TC Bot commented on IGNITE-12582:
{panel:title=Branch: [pull/7411/head] Base: [master] : Possible Blockers
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Cache 7{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5042435]]
{color:#d04437}Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5042398]]
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsAfterKillCrdWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5042421]]
* IgniteBinaryCacheQueryTestSuite:
IndexingCachePartitionLossPolicySelfTest.testReadWriteSafeWithPersistence[ATOMIC]
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5042397]]
* IgniteCacheTestSuite4: IgniteCacheAtomicLoadAllTest.testLoadAll - Test has
low fail rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5042445buildTypeId=IgniteTests24Java8_RunAll]
> It is needed to set used cache for Spring Data dynamically
> --
>
> 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
>Priority: Major
> Fix For: 2.8.1
>
>
> 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)
[jira] [Commented] (IGNITE-12582) It is needed to set used cache for Spring Data dynamically
[ https://issues.apache.org/jira/browse/IGNITE-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034718#comment-17034718 ] Sergey Chernolyas commented on IGNITE-12582: New PR is created. See [https://github.com/apache/ignite/pull/7411] > It is needed to set used cache for Spring Data dynamically > -- > > 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 >Priority: Major > Fix For: 2.8.1 > > > 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)
[jira] [Commented] (IGNITE-10698) Get rid of @MXBeanParametersNames and @MXBeanParametersDescriptions
[
https://issues.apache.org/jira/browse/IGNITE-10698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034681#comment-17034681
]
Andrey N. Gura commented on IGNITE-10698:
-
[~l4ndsc4pe] Could you please fix checkstyle issues:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:3.0.0:check (style) on project
ignite-core: Failed during checkstyle execution: There are 21 errors reported
by Checkstyle 8.19 with ../checkstyle/checkstyle.xml ruleset. -> [Help 1]
{noformat}
For example you can run build locally with the following command:
{noformat}
mvn clean install -DskipTests -Dmaven.javadoc.skip=true -P checkstyle,lgpl
{noformat}
Also please look at Apache Ignite code style guidelines:
https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines
Do not ignore this guidelines and javadocs.
> Get rid of @MXBeanParametersNames and @MXBeanParametersDescriptions
> ---
>
> Key: IGNITE-10698
> URL: https://issues.apache.org/jira/browse/IGNITE-10698
> Project: Ignite
> Issue Type: Task
>Reporter: Yakov Zhdanov
>Assignee: Lev Kiselev
>Priority: Major
> Labels: newbie, pull-request-available, usability
> Fix For: 3.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> @MXBeanDescription("Returns or kills transactions matching the filter
> conditions.")
> @MXBeanParametersNames(
> {
> "minDuration",
> "minSize",
> "prj",
> "consistentIds",
> "xid",
> "lbRegex",
> "limit",
> "order",
> "detailed",
> "kill"
> }
> )
> @MXBeanParametersDescriptions(
> {
> "Minimum duration (seconds).",
> "Minimum size.",
> "Projection (servers|clients).",
> "Consistent ids (separated by comma).",
> "Transaction XID.",
> "Label regexp.",
> "Limit a number of transactions collected on each node.",
> "Order by DURATION|SIZE.",
> "Show detailed description, otherwise only count.",
> "Kill matching transactions (be careful)."
> }
> )
> {noformat}
> Above looks pretty ugly and is very error prone due to messing names and
> descr order or number of strings.
> I would suggest to introduce individual parameters annotations and get them
> via mtd.getParamterAnnotations() at runtime.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12344) Remote listener of IgniteMessaging has to run with appropriate SecurityContext.
[
https://issues.apache.org/jira/browse/IGNITE-12344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034651#comment-17034651
]
Ignite TC Bot commented on IGNITE-12344:
{panel:title=Branch: [pull/7338/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=5040895buildTypeId=IgniteTests24Java8_RunAll]
> Remote listener of IgniteMessaging has to run with appropriate
> SecurityContext.
> ---
>
> Key: IGNITE-12344
> URL: https://issues.apache.org/jira/browse/IGNITE-12344
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Garus
>Assignee: Denis Garus
>Priority: Major
> Labels: iep-38
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Remote listener of IgniteMessaging has to run on a remote node with the
> SecurityContext of the initiator node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12659) [ML] Remove broken sub-modules in ML
[
https://issues.apache.org/jira/browse/IGNITE-12659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034556#comment-17034556
]
Ignite TC Bot commented on IGNITE-12659:
{panel:title=Branch: [pull/7407/head] Base: [master] : Possible Blockers
(23)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests
20|https://ci.ignite.apache.org/viewLog.html?buildId=5041368]]
* IgniteCacheTestSuite2: IgniteCacheClientNodeChangingTopologyTest.testLock -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxNearEnabledNoRemap -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxPutAllMultinode -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testAtomicPrimaryPutAllMultinode -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxMessageClientFirstFlag
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testLockAllMultinode - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testAtomicPutAllPrimaryMode - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testAtomicNoRemapPrimaryMode - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testPessimisticTx - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testOptimisticTxMessageClientFirstFlag
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testAtomicGetAndPutPrimaryMode - Test
has low fail rate in base branch 0,0% and is not flaky
... and 9 tests blockers
{color:#d04437}Queries 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5041394]]
* IgniteBinaryCacheQueryTestSuite:
IndexingCachePartitionLossPolicySelfTest.testReadWriteSafeWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Continuous Query 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5041313]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryFailoverAtomicNearEnabledSelfSelfTest.testMultiThreadedFailover
- New test duration 63s is more that 1 minute
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryFailoverAtomicNearEnabledSelfSelfTest.testFailoverStartStopBackup
- New test duration 66s is more that 1 minute
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5041418buildTypeId=IgniteTests24Java8_RunAll]
> [ML] Remove broken sub-modules in ML
>
>
> Key: IGNITE-12659
> URL: https://issues.apache.org/jira/browse/IGNITE-12659
> Project: Ignite
> Issue Type: Bug
> Components: ml
>Reporter: Alexey Zinoviev
>Assignee: Alexey Zinoviev
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> After testing phase we investigated that the next sub-modules are broken and
> should be removed from the release branch 2.8
> * tensorflow (it uses deprecated IGFS and current solution in tf.contrib
> could n't connect to Ignite now)
> * tensorflow-ml-parser (it has a lot of bugs and doesn't work with tf 2.0)
> * mleap-ml-parser (CVE, Ignite ML couldn't work with metadata)
> * outdated genetic algorithms what are not supported now and are not
> formatted and refactored for the years (it's not a part of ML historically)
> also due to connect with Hadoop, Spark and another libraries it has a few CVE
> related to the old dependencies in Hadoop libraries
>
> P.S. I suppose all these solutions should be moved to the separate project
> ignite-ml-extensions for the independent developement
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-9216) Uncomment 28 test classes in IgniteCacheTestSuite (Cache 1)
[
https://issues.apache.org/jira/browse/IGNITE-9216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034555#comment-17034555
]
Ilya Kasnacheev commented on IGNITE-9216:
-
[~aealeksandrov] thank you for review
> Uncomment 28 test classes in IgniteCacheTestSuite (Cache 1)
> ---
>
> Key: IGNITE-9216
> URL: https://issues.apache.org/jira/browse/IGNITE-9216
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {code}
> //GridTestUtils.addTestIfNeeded(suite,
> CacheEntryProcessorCopySelfTest.class, ignoredTests);
> // suite.addTestSuite(GridCacheP2PUndeploySelfTest.class);
> //suite.addTestSuite(GridCacheTtlManagerEvictionSelfTest.class);
> //suite.addTestSuite(GridIoManagerSelfTest.class);
> //suite.addTestSuite(CacheAtomicSingleMessageCountSelfTest.class);
>
> //suite.addTestSuite(GridCacheAtomicUsersAffinityMapperSelfTest.class);
> //suite.addTestSuite(GridCacheClearLocallySelfTest.class);
> //suite.addTestSuite(GridCacheConcurrentGetCacheOnClientTest.class);
>
> //suite.addTestSuite(GridCacheFullTextQueryMultithreadedSelfTest.class);
> //suite.addTestSuite(GridCacheKeyCheckNearEnabledSelfTest.class);
> //suite.addTestSuite(GridCacheKeyCheckSelfTest.class);
> //suite.addTestSuite(GridCacheLeakTest.class);
> //suite.addTestSuite(GridCacheMultiUpdateLockSelfTest.class);
> //suite.addTestSuite(GridCacheMvccFlagsTest.class);
>
> //suite.addTestSuite(GridCacheReplicatedUsersAffinityMapperSelfTest.class);
> //suite.addTestSuite(GridCacheReturnValueTransferSelfTest.class);
> //suite.addTestSuite(GridCacheSlowTxWarnTest.class);
> //suite.addTestSuite(GridCacheTtlManagerLoadTest.class);
> //suite.addTestSuite(GridCacheTxUsersAffinityMapperSelfTest.class);
> //suite.addTestSuite(IgniteInternalCacheRemoveTest.class);
> //suite.addTestSuite(IgniteCacheBinaryEntryProcessorSelfTest.class);
> //suite.addTestSuite(IgniteCacheObjectPutSelfTest.class);
> //suite.addTestSuite(IgniteCacheSerializationSelfTest.class);
> //suite.addTestSuite(IgniteCacheStartStopLoadTest.class);
> //suite.addTestSuite(IgniteCachingProviderSelfTest.class);
> //suite.addTestSuite(IgniteOnePhaseCommitNearSelfTest.class);
> //suite.addTestSuite(IgniteStaticCacheStartSelfTest.class);
> //suite.addTestSuite(InterceptorWithKeepBinaryCacheFullApiTest.class);
>//suite.addTest(new TestSuite(IgfsSizeSelfTest.class));
>//suite.addTestSuite(IgfsPathSelfTest.class);
>//suite.addTestSuite(IgfsBackupFailoverSelfTest.class);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-12658) [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1 node
[
https://issues.apache.org/jira/browse/IGNITE-12658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Zinoviev resolved IGNITE-12658.
--
Resolution: Fixed
> [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1
> node
>
>
> Key: IGNITE-12658
> URL: https://issues.apache.org/jira/browse/IGNITE-12658
> Project: Ignite
> Issue Type: Bug
> Components: examples, ml
>Affects Versions: 2.8
> Environment: Ubuntu/Win
> Java 8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Zinoviev
>Priority: Critical
> Fix For: 2.8
>
>
> Steps to reproduce:
> 1. Run Ignite node with org.apache.ignite.examples.ExampleNodeStartup (1
> node will be enough)
> 2. Run org.apache.ignite.examples.ml.tutorial.TutorialStepByStepExample
> Actual:
> On Step_8_CV_with_Param_Grid_and_metrics starting to throw a lot of
> exceptions
> {code:java}
> Train with p: 2 and maxDeep: 1
> >>> Trained model: if (x1 > 0.4368) then return 1. else return 0.
> >>> Accuracy 0.7679083094555874
> >>> Test Error 0.2320916905444126
> >>> Tutorial step 8 (cross-validation) example completed.
> [13:25:40] Ignite node stopped OK [uptime=00:00:17.453]
> >>> Tutorial step 8 (cross-validation with param grid) example started.
> [13:25:40]__
> [13:25:40] / _/ ___/ |/ / _/_ __/ __/
> [13:25:40] _/ // (7 7// / / / / _/
> [13:25:40] /___/\___/_/|_/___/ /_/ /___/
> [13:25:40]
> [13:25:40] ver. 2.8.0#20200130-sha1:f478aa56
> [13:25:40] 2020 Copyright(C) Apache Software Foundation
> [13:25:40]
> [13:25:40] Ignite documentation: http://ignite.apache.org
> [13:25:40]
> [13:25:40] Quiet mode.
> [13:25:40] ^-- Logging to file
> '/opt/buildagent/work/d501ae8146bd8253/i2test/var/suite-examples/app-ignite/work/log/ignite-e156b2f2.log'
> [13:25:40] ^-- Logging by 'Log4JLogger [quiet=true, config=null]'
> [13:25:40] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [13:25:40]
> [13:25:40] OS: Linux 4.15.0-65-generic amd64
> [13:25:40] VM information: Java(TM) SE Runtime Environment 1.8.0_221-b11
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.221-b11
> [13:25:40] Please set system property '-Djava.net.preferIPv4Stack=true' to
> avoid possible problems in mixed environments.
> [13:25:40] Configured plugins:
> [13:25:40] ^-- ml-inference-plugin 1.0.0
> [13:25:40] ^-- null
> [13:25:40]
> [13:25:40] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
> [tryStop=false, timeout=0, super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT
> [13:25:40] Message queue limit is set to 0 which may lead to potential OOMEs
> when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
> message queues growth on sender and receiver sides.
> [13:25:40] Security status [authentication=off, tls/ssl=off]
> [13:25:41] Performance suggestions for grid (fix if possible)
> [13:25:41] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [13:25:41] ^-- Disable grid events (remove 'includeEventTypes' from
> configuration)
> [13:25:41] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM
> options)
> [13:25:41] ^-- Set max direct memory size if getting 'OOME: Direct buffer
> memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
> [13:25:41] ^-- Disable processing of calls to System.gc() (add
> '-XX:+DisableExplicitGC' to JVM options)
> [13:25:41] Refer to this page for more performance suggestions:
> https://apacheignite.readme.io/docs/jvm-and-system-tuning
> [13:25:41]
> [13:25:41] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [13:25:41] Data Regions Configured:
> [13:25:41] ^-- Default_Region [initSize=500.0 MiB, maxSize=18.9 GiB,
> persistence=false, lazyMemoryAllocation=true]
> [13:25:41]
> [13:25:41] Ignite node started OK (id=e156b2f2)
> [13:25:41] Topology snapshot [ver=20, locNode=e156b2f2, servers=2, clients=0,
> state=ACTIVE, CPUs=5, offheap=38.0GB, heap=3.0GB]
> [13:25:41] ^-- Baseline [id=0, size=2, online=2, offline=0]
> [2020-02-11 13:25:42,428][ERROR][sys-#593][GridTaskWorker] Failed to obtain
> remote job result policy for result from ComputeTask.result(..) method (will
> fail the whole task): GridJobResultImpl [job=C2
> [c=o.a.i.ml.dataset.impl.cache.util.ComputeUtils$DeployableCallable@30e27659],
> sib=GridJobSiblingImpl
> [sesId=f9aced33071-e156b2f2-d116-4389-bd43-8536dc59,
> jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59,
> nodeId=f1135598-73c8-4324-92af-45c110a6a637, isJobDone=false],
> jobCtx=GridJobContextImpl
>
[jira] [Commented] (IGNITE-12657) ML examples EvaluatorExample and MultipleMetricsExample looks the same
[ https://issues.apache.org/jira/browse/IGNITE-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034549#comment-17034549 ] Alexey Zinoviev commented on IGNITE-12657: -- Fixed in https://github.com/apache/ignite/pull/7408 > ML examples EvaluatorExample and MultipleMetricsExample looks the same > -- > > Key: IGNITE-12657 > URL: https://issues.apache.org/jira/browse/IGNITE-12657 > Project: Ignite > Issue Type: Bug > Components: examples, ml >Affects Versions: 2.8 >Reporter: Stepan Pilschikov >Assignee: Alexey Zinoviev >Priority: Blocker > Fix For: 2.8 > > > Examples > org.apache.ignite.examples.ml.selection.scoring.EvaluatorExample > and > org.apache.ignite.examples.ml.selection.scoring.MultipleMetricsExample > Looks exactly the same > I think MultipleMetricsExample is wrong because description told about using > KNNClassificationTrainer but actually used SVMLinearClassificationTrainer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12661) Fix GridIoManagerSelfTest
Ilya Kasnacheev created IGNITE-12661: Summary: Fix GridIoManagerSelfTest Key: IGNITE-12661 URL: https://issues.apache.org/jira/browse/IGNITE-12661 Project: Ignite Issue Type: Test Components: cache Reporter: Ilya Kasnacheev It is an old test which tries to create some Processors and stich them together, which just does no longer work. We need to rewrite this test, I think. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9216) Uncomment 28 test classes in IgniteCacheTestSuite (Cache 1)
[
https://issues.apache.org/jira/browse/IGNITE-9216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034521#comment-17034521
]
Andrey Aleksandrov commented on IGNITE-9216:
[~ilyak] Looks good for me.
> Uncomment 28 test classes in IgniteCacheTestSuite (Cache 1)
> ---
>
> Key: IGNITE-9216
> URL: https://issues.apache.org/jira/browse/IGNITE-9216
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code}
> //GridTestUtils.addTestIfNeeded(suite,
> CacheEntryProcessorCopySelfTest.class, ignoredTests);
> // suite.addTestSuite(GridCacheP2PUndeploySelfTest.class);
> //suite.addTestSuite(GridCacheTtlManagerEvictionSelfTest.class);
> //suite.addTestSuite(GridIoManagerSelfTest.class);
> //suite.addTestSuite(CacheAtomicSingleMessageCountSelfTest.class);
>
> //suite.addTestSuite(GridCacheAtomicUsersAffinityMapperSelfTest.class);
> //suite.addTestSuite(GridCacheClearLocallySelfTest.class);
> //suite.addTestSuite(GridCacheConcurrentGetCacheOnClientTest.class);
>
> //suite.addTestSuite(GridCacheFullTextQueryMultithreadedSelfTest.class);
> //suite.addTestSuite(GridCacheKeyCheckNearEnabledSelfTest.class);
> //suite.addTestSuite(GridCacheKeyCheckSelfTest.class);
> //suite.addTestSuite(GridCacheLeakTest.class);
> //suite.addTestSuite(GridCacheMultiUpdateLockSelfTest.class);
> //suite.addTestSuite(GridCacheMvccFlagsTest.class);
>
> //suite.addTestSuite(GridCacheReplicatedUsersAffinityMapperSelfTest.class);
> //suite.addTestSuite(GridCacheReturnValueTransferSelfTest.class);
> //suite.addTestSuite(GridCacheSlowTxWarnTest.class);
> //suite.addTestSuite(GridCacheTtlManagerLoadTest.class);
> //suite.addTestSuite(GridCacheTxUsersAffinityMapperSelfTest.class);
> //suite.addTestSuite(IgniteInternalCacheRemoveTest.class);
> //suite.addTestSuite(IgniteCacheBinaryEntryProcessorSelfTest.class);
> //suite.addTestSuite(IgniteCacheObjectPutSelfTest.class);
> //suite.addTestSuite(IgniteCacheSerializationSelfTest.class);
> //suite.addTestSuite(IgniteCacheStartStopLoadTest.class);
> //suite.addTestSuite(IgniteCachingProviderSelfTest.class);
> //suite.addTestSuite(IgniteOnePhaseCommitNearSelfTest.class);
> //suite.addTestSuite(IgniteStaticCacheStartSelfTest.class);
> //suite.addTestSuite(InterceptorWithKeepBinaryCacheFullApiTest.class);
>//suite.addTest(new TestSuite(IgfsSizeSelfTest.class));
>//suite.addTestSuite(IgfsPathSelfTest.class);
>//suite.addTestSuite(IgfsBackupFailoverSelfTest.class);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12642) Fix a typo in the log message about the topology version context when check if rebalance should be started
[
https://issues.apache.org/jira/browse/IGNITE-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034522#comment-17034522
]
Ivan Pavlukhin commented on IGNITE-12642:
-
[~mikecaat], usually we do not set CLOSED status to tickets which were merged
to master but use RESOLVED status for them. Let's keep it RESOLVED so far.
> Fix a typo in the log message about the topology version context when check
> if rebalance should be started
> --
>
> Key: IGNITE-12642
> URL: https://issues.apache.org/jira/browse/IGNITE-12642
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: masahiro ikeda
>Assignee: masahiro ikeda
>Priority: Trivial
> Fix For: 2.9
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When check if rebalance should be started, there is a assertion to check the
> context of the local and rebalance topology version.
> The assertion message contains a typo("hisroty").
> {code:java}
> "Empty hisroty allowed only for newly started cache group [rebTopVer=" +
> rebTopVer +
> ", localStartTopVer=" + grp.localStartVersion() + ']';
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-12642) Fix a typo in the log message about the topology version context when check if rebalance should be started
[
https://issues.apache.org/jira/browse/IGNITE-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin resolved IGNITE-12642.
-
Fix Version/s: 2.9
> Fix a typo in the log message about the topology version context when check
> if rebalance should be started
> --
>
> Key: IGNITE-12642
> URL: https://issues.apache.org/jira/browse/IGNITE-12642
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: masahiro ikeda
>Assignee: masahiro ikeda
>Priority: Trivial
> Fix For: 2.9
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When check if rebalance should be started, there is a assertion to check the
> context of the local and rebalance topology version.
> The assertion message contains a typo("hisroty").
> {code:java}
> "Empty hisroty allowed only for newly started cache group [rebTopVer=" +
> rebTopVer +
> ", localStartTopVer=" + grp.localStartVersion() + ']';
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-2855) Apache Calcite as an SQL query parser and optimizer
[ https://issues.apache.org/jira/browse/IGNITE-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin resolved IGNITE-2855. Resolution: Duplicate This activity was continued in IGNITE-12248 > Apache Calcite as an SQL query parser and optimizer > --- > > Key: IGNITE-2855 > URL: https://issues.apache.org/jira/browse/IGNITE-2855 > Project: Ignite > Issue Type: New Feature >Reporter: Roman Shtykh >Priority: Minor > > Apache Calcite (https://calcite.apache.org/) can be used as an SQL query > parser, validator and optimizer with Ignite at the back end. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IGNITE-12659) [ML] Remove broken sub-modules in ML
[ https://issues.apache.org/jira/browse/IGNITE-12659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev reopened IGNITE-12659: -- > [ML] Remove broken sub-modules in ML > > > Key: IGNITE-12659 > URL: https://issues.apache.org/jira/browse/IGNITE-12659 > Project: Ignite > Issue Type: Bug > Components: ml >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > After testing phase we investigated that the next sub-modules are broken and > should be removed from the release branch 2.8 > * tensorflow (it uses deprecated IGFS and current solution in tf.contrib > could n't connect to Ignite now) > * tensorflow-ml-parser (it has a lot of bugs and doesn't work with tf 2.0) > * mleap-ml-parser (CVE, Ignite ML couldn't work with metadata) > * outdated genetic algorithms what are not supported now and are not > formatted and refactored for the years (it's not a part of ML historically) > also due to connect with Hadoop, Spark and another libraries it has a few CVE > related to the old dependencies in Hadoop libraries > > P.S. I suppose all these solutions should be moved to the separate project > ignite-ml-extensions for the independent developement -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12638) Classes persisted by DistributedMetaStorage are not IgniteDTO
[ https://issues.apache.org/jira/browse/IGNITE-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034498#comment-17034498 ] Ivan Bessonov commented on IGNITE-12638: [~mmuzaf] I'm all for merging it to master but I can't do it by myself. What flaky failures do you mean? Are you afraid that this change will add some? > Classes persisted by DistributedMetaStorage are not IgniteDTO > - > > Key: IGNITE-12638 > URL: https://issues.apache.org/jira/browse/IGNITE-12638 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > This has to be fixed to simplify future modification of component. > DistributedMetaStorageHistoryItem and DistributedMetaStorageVersion will be > persisted on disc so we need to have a reliable way to read them even when > classes will be updated in the future. IgniteDataTransferObject is the > standard option for such cases - it allows versioning of serialization format. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12658) [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1 node
[
https://issues.apache.org/jira/browse/IGNITE-12658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Zinoviev updated IGNITE-12658:
-
Fix Version/s: 2.8
> [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1
> node
>
>
> Key: IGNITE-12658
> URL: https://issues.apache.org/jira/browse/IGNITE-12658
> Project: Ignite
> Issue Type: Bug
> Components: examples, ml
>Affects Versions: 2.8
> Environment: Ubuntu/Win
> Java 8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Zinoviev
>Priority: Critical
> Fix For: 2.8
>
>
> Steps to reproduce:
> 1. Run Ignite node with org.apache.ignite.examples.ExampleNodeStartup (1
> node will be enough)
> 2. Run org.apache.ignite.examples.ml.tutorial.TutorialStepByStepExample
> Actual:
> On Step_8_CV_with_Param_Grid_and_metrics starting to throw a lot of
> exceptions
> {code:java}
> Train with p: 2 and maxDeep: 1
> >>> Trained model: if (x1 > 0.4368) then return 1. else return 0.
> >>> Accuracy 0.7679083094555874
> >>> Test Error 0.2320916905444126
> >>> Tutorial step 8 (cross-validation) example completed.
> [13:25:40] Ignite node stopped OK [uptime=00:00:17.453]
> >>> Tutorial step 8 (cross-validation with param grid) example started.
> [13:25:40]__
> [13:25:40] / _/ ___/ |/ / _/_ __/ __/
> [13:25:40] _/ // (7 7// / / / / _/
> [13:25:40] /___/\___/_/|_/___/ /_/ /___/
> [13:25:40]
> [13:25:40] ver. 2.8.0#20200130-sha1:f478aa56
> [13:25:40] 2020 Copyright(C) Apache Software Foundation
> [13:25:40]
> [13:25:40] Ignite documentation: http://ignite.apache.org
> [13:25:40]
> [13:25:40] Quiet mode.
> [13:25:40] ^-- Logging to file
> '/opt/buildagent/work/d501ae8146bd8253/i2test/var/suite-examples/app-ignite/work/log/ignite-e156b2f2.log'
> [13:25:40] ^-- Logging by 'Log4JLogger [quiet=true, config=null]'
> [13:25:40] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [13:25:40]
> [13:25:40] OS: Linux 4.15.0-65-generic amd64
> [13:25:40] VM information: Java(TM) SE Runtime Environment 1.8.0_221-b11
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.221-b11
> [13:25:40] Please set system property '-Djava.net.preferIPv4Stack=true' to
> avoid possible problems in mixed environments.
> [13:25:40] Configured plugins:
> [13:25:40] ^-- ml-inference-plugin 1.0.0
> [13:25:40] ^-- null
> [13:25:40]
> [13:25:40] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
> [tryStop=false, timeout=0, super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT
> [13:25:40] Message queue limit is set to 0 which may lead to potential OOMEs
> when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
> message queues growth on sender and receiver sides.
> [13:25:40] Security status [authentication=off, tls/ssl=off]
> [13:25:41] Performance suggestions for grid (fix if possible)
> [13:25:41] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [13:25:41] ^-- Disable grid events (remove 'includeEventTypes' from
> configuration)
> [13:25:41] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM
> options)
> [13:25:41] ^-- Set max direct memory size if getting 'OOME: Direct buffer
> memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
> [13:25:41] ^-- Disable processing of calls to System.gc() (add
> '-XX:+DisableExplicitGC' to JVM options)
> [13:25:41] Refer to this page for more performance suggestions:
> https://apacheignite.readme.io/docs/jvm-and-system-tuning
> [13:25:41]
> [13:25:41] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [13:25:41] Data Regions Configured:
> [13:25:41] ^-- Default_Region [initSize=500.0 MiB, maxSize=18.9 GiB,
> persistence=false, lazyMemoryAllocation=true]
> [13:25:41]
> [13:25:41] Ignite node started OK (id=e156b2f2)
> [13:25:41] Topology snapshot [ver=20, locNode=e156b2f2, servers=2, clients=0,
> state=ACTIVE, CPUs=5, offheap=38.0GB, heap=3.0GB]
> [13:25:41] ^-- Baseline [id=0, size=2, online=2, offline=0]
> [2020-02-11 13:25:42,428][ERROR][sys-#593][GridTaskWorker] Failed to obtain
> remote job result policy for result from ComputeTask.result(..) method (will
> fail the whole task): GridJobResultImpl [job=C2
> [c=o.a.i.ml.dataset.impl.cache.util.ComputeUtils$DeployableCallable@30e27659],
> sib=GridJobSiblingImpl
> [sesId=f9aced33071-e156b2f2-d116-4389-bd43-8536dc59,
> jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59,
> nodeId=f1135598-73c8-4324-92af-45c110a6a637, isJobDone=false],
> jobCtx=GridJobContextImpl
>
[jira] [Updated] (IGNITE-12660) [ML] The ParamGrid uses unserialized lambdas in interface to get an access to the trainer fields
[ https://issues.apache.org/jira/browse/IGNITE-12660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-12660: - Priority: Blocker (was: Major) > [ML] The ParamGrid uses unserialized lambdas in interface to get an access to > the trainer fields > > > Key: IGNITE-12660 > URL: https://issues.apache.org/jira/browse/IGNITE-12660 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.8 >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Blocker > Fix For: 2.8 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12657) ML examples EvaluatorExample and MultipleMetricsExample looks the same
[ https://issues.apache.org/jira/browse/IGNITE-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12657: - Priority: Blocker (was: Major) > ML examples EvaluatorExample and MultipleMetricsExample looks the same > -- > > Key: IGNITE-12657 > URL: https://issues.apache.org/jira/browse/IGNITE-12657 > Project: Ignite > Issue Type: Bug > Components: examples, ml >Affects Versions: 2.8 >Reporter: Stepan Pilschikov >Assignee: Alexey Zinoviev >Priority: Blocker > Fix For: 2.8 > > > Examples > org.apache.ignite.examples.ml.selection.scoring.EvaluatorExample > and > org.apache.ignite.examples.ml.selection.scoring.MultipleMetricsExample > Looks exactly the same > I think MultipleMetricsExample is wrong because description told about using > KNNClassificationTrainer but actually used SVMLinearClassificationTrainer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12660) [ML] The ParamGrid uses unserialized lambdas in interface to get an access to the trainer fields
[ https://issues.apache.org/jira/browse/IGNITE-12660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-12660: - Affects Version/s: 2.8 > [ML] The ParamGrid uses unserialized lambdas in interface to get an access to > the trainer fields > > > Key: IGNITE-12660 > URL: https://issues.apache.org/jira/browse/IGNITE-12660 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Major > Fix For: 2.8 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12657) ML examples EvaluatorExample and MultipleMetricsExample looks the same
[ https://issues.apache.org/jira/browse/IGNITE-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12657: - Fix Version/s: 2.8 > ML examples EvaluatorExample and MultipleMetricsExample looks the same > -- > > Key: IGNITE-12657 > URL: https://issues.apache.org/jira/browse/IGNITE-12657 > Project: Ignite > Issue Type: Bug > Components: examples, ml >Affects Versions: 2.8 >Reporter: Stepan Pilschikov >Assignee: Alexey Zinoviev >Priority: Major > Fix For: 2.8 > > > Examples > org.apache.ignite.examples.ml.selection.scoring.EvaluatorExample > and > org.apache.ignite.examples.ml.selection.scoring.MultipleMetricsExample > Looks exactly the same > I think MultipleMetricsExample is wrong because description told about using > KNNClassificationTrainer but actually used SVMLinearClassificationTrainer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12660) [ML] The ParamGrid uses unserialized lambdas in interface to get an access to the trainer fields
[ https://issues.apache.org/jira/browse/IGNITE-12660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-12660: - Component/s: ml > [ML] The ParamGrid uses unserialized lambdas in interface to get an access to > the trainer fields > > > Key: IGNITE-12660 > URL: https://issues.apache.org/jira/browse/IGNITE-12660 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.8 >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Major > Fix For: 2.8 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12660) [ML] The ParamGrid uses unserialized lambdas in interface to get an access to the trainer fields
Alexey Zinoviev created IGNITE-12660: Summary: [ML] The ParamGrid uses unserialized lambdas in interface to get an access to the trainer fields Key: IGNITE-12660 URL: https://issues.apache.org/jira/browse/IGNITE-12660 Project: Ignite Issue Type: Bug Reporter: Alexey Zinoviev Assignee: Alexey Zinoviev Fix For: 2.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12658) [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1 node
[
https://issues.apache.org/jira/browse/IGNITE-12658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Zinoviev updated IGNITE-12658:
-
Priority: Critical (was: Blocker)
> [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1
> node
>
>
> Key: IGNITE-12658
> URL: https://issues.apache.org/jira/browse/IGNITE-12658
> Project: Ignite
> Issue Type: Bug
> Components: examples, ml
>Affects Versions: 2.8
> Environment: Ubuntu/Win
> Java 8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Zinoviev
>Priority: Critical
>
> Steps to reproduce:
> 1. Run Ignite node with org.apache.ignite.examples.ExampleNodeStartup (1
> node will be enough)
> 2. Run org.apache.ignite.examples.ml.tutorial.TutorialStepByStepExample
> Actual:
> On Step_8_CV_with_Param_Grid_and_metrics starting to throw a lot of
> exceptions
> {code:java}
> Train with p: 2 and maxDeep: 1
> >>> Trained model: if (x1 > 0.4368) then return 1. else return 0.
> >>> Accuracy 0.7679083094555874
> >>> Test Error 0.2320916905444126
> >>> Tutorial step 8 (cross-validation) example completed.
> [13:25:40] Ignite node stopped OK [uptime=00:00:17.453]
> >>> Tutorial step 8 (cross-validation with param grid) example started.
> [13:25:40]__
> [13:25:40] / _/ ___/ |/ / _/_ __/ __/
> [13:25:40] _/ // (7 7// / / / / _/
> [13:25:40] /___/\___/_/|_/___/ /_/ /___/
> [13:25:40]
> [13:25:40] ver. 2.8.0#20200130-sha1:f478aa56
> [13:25:40] 2020 Copyright(C) Apache Software Foundation
> [13:25:40]
> [13:25:40] Ignite documentation: http://ignite.apache.org
> [13:25:40]
> [13:25:40] Quiet mode.
> [13:25:40] ^-- Logging to file
> '/opt/buildagent/work/d501ae8146bd8253/i2test/var/suite-examples/app-ignite/work/log/ignite-e156b2f2.log'
> [13:25:40] ^-- Logging by 'Log4JLogger [quiet=true, config=null]'
> [13:25:40] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [13:25:40]
> [13:25:40] OS: Linux 4.15.0-65-generic amd64
> [13:25:40] VM information: Java(TM) SE Runtime Environment 1.8.0_221-b11
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.221-b11
> [13:25:40] Please set system property '-Djava.net.preferIPv4Stack=true' to
> avoid possible problems in mixed environments.
> [13:25:40] Configured plugins:
> [13:25:40] ^-- ml-inference-plugin 1.0.0
> [13:25:40] ^-- null
> [13:25:40]
> [13:25:40] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
> [tryStop=false, timeout=0, super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT
> [13:25:40] Message queue limit is set to 0 which may lead to potential OOMEs
> when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
> message queues growth on sender and receiver sides.
> [13:25:40] Security status [authentication=off, tls/ssl=off]
> [13:25:41] Performance suggestions for grid (fix if possible)
> [13:25:41] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [13:25:41] ^-- Disable grid events (remove 'includeEventTypes' from
> configuration)
> [13:25:41] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM
> options)
> [13:25:41] ^-- Set max direct memory size if getting 'OOME: Direct buffer
> memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
> [13:25:41] ^-- Disable processing of calls to System.gc() (add
> '-XX:+DisableExplicitGC' to JVM options)
> [13:25:41] Refer to this page for more performance suggestions:
> https://apacheignite.readme.io/docs/jvm-and-system-tuning
> [13:25:41]
> [13:25:41] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [13:25:41] Data Regions Configured:
> [13:25:41] ^-- Default_Region [initSize=500.0 MiB, maxSize=18.9 GiB,
> persistence=false, lazyMemoryAllocation=true]
> [13:25:41]
> [13:25:41] Ignite node started OK (id=e156b2f2)
> [13:25:41] Topology snapshot [ver=20, locNode=e156b2f2, servers=2, clients=0,
> state=ACTIVE, CPUs=5, offheap=38.0GB, heap=3.0GB]
> [13:25:41] ^-- Baseline [id=0, size=2, online=2, offline=0]
> [2020-02-11 13:25:42,428][ERROR][sys-#593][GridTaskWorker] Failed to obtain
> remote job result policy for result from ComputeTask.result(..) method (will
> fail the whole task): GridJobResultImpl [job=C2
> [c=o.a.i.ml.dataset.impl.cache.util.ComputeUtils$DeployableCallable@30e27659],
> sib=GridJobSiblingImpl
> [sesId=f9aced33071-e156b2f2-d116-4389-bd43-8536dc59,
> jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59,
> nodeId=f1135598-73c8-4324-92af-45c110a6a637, isJobDone=false],
> jobCtx=GridJobContextImpl
> [jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59,
[jira] [Updated] (IGNITE-12658) [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1 node
[
https://issues.apache.org/jira/browse/IGNITE-12658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Zinoviev updated IGNITE-12658:
-
Priority: Blocker (was: Critical)
> [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1
> node
>
>
> Key: IGNITE-12658
> URL: https://issues.apache.org/jira/browse/IGNITE-12658
> Project: Ignite
> Issue Type: Bug
> Components: examples, ml
>Affects Versions: 2.8
> Environment: Ubuntu/Win
> Java 8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Zinoviev
>Priority: Blocker
>
> Steps to reproduce:
> 1. Run Ignite node with org.apache.ignite.examples.ExampleNodeStartup (1
> node will be enough)
> 2. Run org.apache.ignite.examples.ml.tutorial.TutorialStepByStepExample
> Actual:
> On Step_8_CV_with_Param_Grid_and_metrics starting to throw a lot of
> exceptions
> {code:java}
> Train with p: 2 and maxDeep: 1
> >>> Trained model: if (x1 > 0.4368) then return 1. else return 0.
> >>> Accuracy 0.7679083094555874
> >>> Test Error 0.2320916905444126
> >>> Tutorial step 8 (cross-validation) example completed.
> [13:25:40] Ignite node stopped OK [uptime=00:00:17.453]
> >>> Tutorial step 8 (cross-validation with param grid) example started.
> [13:25:40]__
> [13:25:40] / _/ ___/ |/ / _/_ __/ __/
> [13:25:40] _/ // (7 7// / / / / _/
> [13:25:40] /___/\___/_/|_/___/ /_/ /___/
> [13:25:40]
> [13:25:40] ver. 2.8.0#20200130-sha1:f478aa56
> [13:25:40] 2020 Copyright(C) Apache Software Foundation
> [13:25:40]
> [13:25:40] Ignite documentation: http://ignite.apache.org
> [13:25:40]
> [13:25:40] Quiet mode.
> [13:25:40] ^-- Logging to file
> '/opt/buildagent/work/d501ae8146bd8253/i2test/var/suite-examples/app-ignite/work/log/ignite-e156b2f2.log'
> [13:25:40] ^-- Logging by 'Log4JLogger [quiet=true, config=null]'
> [13:25:40] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [13:25:40]
> [13:25:40] OS: Linux 4.15.0-65-generic amd64
> [13:25:40] VM information: Java(TM) SE Runtime Environment 1.8.0_221-b11
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.221-b11
> [13:25:40] Please set system property '-Djava.net.preferIPv4Stack=true' to
> avoid possible problems in mixed environments.
> [13:25:40] Configured plugins:
> [13:25:40] ^-- ml-inference-plugin 1.0.0
> [13:25:40] ^-- null
> [13:25:40]
> [13:25:40] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
> [tryStop=false, timeout=0, super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT
> [13:25:40] Message queue limit is set to 0 which may lead to potential OOMEs
> when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
> message queues growth on sender and receiver sides.
> [13:25:40] Security status [authentication=off, tls/ssl=off]
> [13:25:41] Performance suggestions for grid (fix if possible)
> [13:25:41] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [13:25:41] ^-- Disable grid events (remove 'includeEventTypes' from
> configuration)
> [13:25:41] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM
> options)
> [13:25:41] ^-- Set max direct memory size if getting 'OOME: Direct buffer
> memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
> [13:25:41] ^-- Disable processing of calls to System.gc() (add
> '-XX:+DisableExplicitGC' to JVM options)
> [13:25:41] Refer to this page for more performance suggestions:
> https://apacheignite.readme.io/docs/jvm-and-system-tuning
> [13:25:41]
> [13:25:41] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [13:25:41] Data Regions Configured:
> [13:25:41] ^-- Default_Region [initSize=500.0 MiB, maxSize=18.9 GiB,
> persistence=false, lazyMemoryAllocation=true]
> [13:25:41]
> [13:25:41] Ignite node started OK (id=e156b2f2)
> [13:25:41] Topology snapshot [ver=20, locNode=e156b2f2, servers=2, clients=0,
> state=ACTIVE, CPUs=5, offheap=38.0GB, heap=3.0GB]
> [13:25:41] ^-- Baseline [id=0, size=2, online=2, offline=0]
> [2020-02-11 13:25:42,428][ERROR][sys-#593][GridTaskWorker] Failed to obtain
> remote job result policy for result from ComputeTask.result(..) method (will
> fail the whole task): GridJobResultImpl [job=C2
> [c=o.a.i.ml.dataset.impl.cache.util.ComputeUtils$DeployableCallable@30e27659],
> sib=GridJobSiblingImpl
> [sesId=f9aced33071-e156b2f2-d116-4389-bd43-8536dc59,
> jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59,
> nodeId=f1135598-73c8-4324-92af-45c110a6a637, isJobDone=false],
> jobCtx=GridJobContextImpl
> [jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59,
[jira] [Commented] (IGNITE-12638) Classes persisted by DistributedMetaStorage are not IgniteDTO
[ https://issues.apache.org/jira/browse/IGNITE-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034471#comment-17034471 ] Maxim Muzafarov commented on IGNITE-12638: -- Let's merge to the master branch first and wait for flaky failures (if any) > Classes persisted by DistributedMetaStorage are not IgniteDTO > - > > Key: IGNITE-12638 > URL: https://issues.apache.org/jira/browse/IGNITE-12638 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > This has to be fixed to simplify future modification of component. > DistributedMetaStorageHistoryItem and DistributedMetaStorageVersion will be > persisted on disc so we need to have a reliable way to read them even when > classes will be updated in the future. IgniteDataTransferObject is the > standard option for such cases - it allows versioning of serialization format. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12654) Some of rentingFutures in GridDhtPartitionTopologyImpl may accumulate a huge number of eviction callbacks
[
https://issues.apache.org/jira/browse/IGNITE-12654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034470#comment-17034470
]
Ignite TC Bot commented on IGNITE-12654:
{panel:title=Branch: [pull/7399/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=5040481buildTypeId=IgniteTests24Java8_RunAll]
> Some of rentingFutures in GridDhtPartitionTopologyImpl may accumulate a huge
> number of eviction callbacks
> -
>
> Key: IGNITE-12654
> URL: https://issues.apache.org/jira/browse/IGNITE-12654
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Example of heap dump:
> ||Class Name||Shallow Heap||Retained Heap||
> |top
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl
> @ 0x809f03d0|88|1 381 118 968|
> |grp org.apache.ignite.internal.processors.cache.CacheGroupContext @
> 0x809f04c8|96|1 381 121 912|
> |locParts java.util.concurrent.atomic.AtomicReferenceArray @ 0x81656c30|16|1
> 380 925 496|
> |array java.lang.Object[1024] @ 0x81656c40|4 112|1 380 925 480|
> |org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition
> @ 0xb5f2bcd8|24|318 622 384|
> |org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition
> @ 0xb5f28d90|96|318 618 624|
> |org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition
> @ 0xb5ed4ac8|24|318 618 576|
> |org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition
> @ 0xb5f2e7f8|24|318 618 528|
> |grp org.apache.ignite.internal.processors.cache.CacheGroupContext @
> 0x809f04c8|96|1 381 121 912|
> |state org.apache.ignite.internal.util.future.GridFutureAdapter$Node @
> 0xe8ed4cd0|24|318 618 624|
> |val
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl$$Lambda$58
> @ 0xe8ed4cb8|24|24|
> |arg$1
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl
> @ 0x809f03d0|88|1 381 118 968|
> The number of {{GridFutureAdapter$Node}}'s and
> {{GridDhtPartitionTopologyImpl$$Lambda$58}}'s looks weird. It seems that the
> following code is the root cause:
> {code:java|title=GridDhtPartitionTopologyImpl.java}
> /**
> * Finds local partitions which don't belong to affinity and runs
> eviction process for such partitions.
> *
> * @param updateSeq Update sequence.
> * @param aff Affinity assignments.
> * @return {@code True} if there are local partitions need to be evicted.
> */
> private boolean checkEvictions(long updateSeq, AffinityAssignment aff) {
>...
> // After all rents are finished resend partitions.
> if (!rentingFutures.isEmpty()) {
> final AtomicInteger rentingPartitions = new
> AtomicInteger(rentingFutures.size());
> for (IgniteInternalFuture rentingFuture : rentingFutures) {
> rentingFuture.listen(f -> {
> int remaining = rentingPartitions.decrementAndGet();
> if (remaining == 0) {
> lock.writeLock().lock();
> try {
> this.updateSeq.incrementAndGet();
> if (log.isDebugEnabled())
> log.debug("Partitions have been scheduled to
> resend [reason=" +
> "Evictions are done [grp=" +
> grp.cacheOrGroupName() + "]");
> ctx.exchange().scheduleResendPartitions();
> }
> finally {
> lock.writeLock().unlock();
> }
> }
> });
> }
> }
> return hasEvictedPartitions;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12658) [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1 node
[
https://issues.apache.org/jira/browse/IGNITE-12658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Zinoviev updated IGNITE-12658:
-
Priority: Critical (was: Major)
> [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1
> node
>
>
> Key: IGNITE-12658
> URL: https://issues.apache.org/jira/browse/IGNITE-12658
> Project: Ignite
> Issue Type: Bug
> Components: examples, ml
>Affects Versions: 2.8
> Environment: Ubuntu/Win
> Java 8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Zinoviev
>Priority: Critical
>
> Steps to reproduce:
> 1. Run Ignite node with org.apache.ignite.examples.ExampleNodeStartup (1
> node will be enough)
> 2. Run org.apache.ignite.examples.ml.tutorial.TutorialStepByStepExample
> Actual:
> On Step_8_CV_with_Param_Grid_and_metrics starting to throw a lot of
> exceptions
> {code:java}
> Train with p: 2 and maxDeep: 1
> >>> Trained model: if (x1 > 0.4368) then return 1. else return 0.
> >>> Accuracy 0.7679083094555874
> >>> Test Error 0.2320916905444126
> >>> Tutorial step 8 (cross-validation) example completed.
> [13:25:40] Ignite node stopped OK [uptime=00:00:17.453]
> >>> Tutorial step 8 (cross-validation with param grid) example started.
> [13:25:40]__
> [13:25:40] / _/ ___/ |/ / _/_ __/ __/
> [13:25:40] _/ // (7 7// / / / / _/
> [13:25:40] /___/\___/_/|_/___/ /_/ /___/
> [13:25:40]
> [13:25:40] ver. 2.8.0#20200130-sha1:f478aa56
> [13:25:40] 2020 Copyright(C) Apache Software Foundation
> [13:25:40]
> [13:25:40] Ignite documentation: http://ignite.apache.org
> [13:25:40]
> [13:25:40] Quiet mode.
> [13:25:40] ^-- Logging to file
> '/opt/buildagent/work/d501ae8146bd8253/i2test/var/suite-examples/app-ignite/work/log/ignite-e156b2f2.log'
> [13:25:40] ^-- Logging by 'Log4JLogger [quiet=true, config=null]'
> [13:25:40] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [13:25:40]
> [13:25:40] OS: Linux 4.15.0-65-generic amd64
> [13:25:40] VM information: Java(TM) SE Runtime Environment 1.8.0_221-b11
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.221-b11
> [13:25:40] Please set system property '-Djava.net.preferIPv4Stack=true' to
> avoid possible problems in mixed environments.
> [13:25:40] Configured plugins:
> [13:25:40] ^-- ml-inference-plugin 1.0.0
> [13:25:40] ^-- null
> [13:25:40]
> [13:25:40] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
> [tryStop=false, timeout=0, super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT
> [13:25:40] Message queue limit is set to 0 which may lead to potential OOMEs
> when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
> message queues growth on sender and receiver sides.
> [13:25:40] Security status [authentication=off, tls/ssl=off]
> [13:25:41] Performance suggestions for grid (fix if possible)
> [13:25:41] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [13:25:41] ^-- Disable grid events (remove 'includeEventTypes' from
> configuration)
> [13:25:41] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM
> options)
> [13:25:41] ^-- Set max direct memory size if getting 'OOME: Direct buffer
> memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
> [13:25:41] ^-- Disable processing of calls to System.gc() (add
> '-XX:+DisableExplicitGC' to JVM options)
> [13:25:41] Refer to this page for more performance suggestions:
> https://apacheignite.readme.io/docs/jvm-and-system-tuning
> [13:25:41]
> [13:25:41] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [13:25:41] Data Regions Configured:
> [13:25:41] ^-- Default_Region [initSize=500.0 MiB, maxSize=18.9 GiB,
> persistence=false, lazyMemoryAllocation=true]
> [13:25:41]
> [13:25:41] Ignite node started OK (id=e156b2f2)
> [13:25:41] Topology snapshot [ver=20, locNode=e156b2f2, servers=2, clients=0,
> state=ACTIVE, CPUs=5, offheap=38.0GB, heap=3.0GB]
> [13:25:41] ^-- Baseline [id=0, size=2, online=2, offline=0]
> [2020-02-11 13:25:42,428][ERROR][sys-#593][GridTaskWorker] Failed to obtain
> remote job result policy for result from ComputeTask.result(..) method (will
> fail the whole task): GridJobResultImpl [job=C2
> [c=o.a.i.ml.dataset.impl.cache.util.ComputeUtils$DeployableCallable@30e27659],
> sib=GridJobSiblingImpl
> [sesId=f9aced33071-e156b2f2-d116-4389-bd43-8536dc59,
> jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59,
> nodeId=f1135598-73c8-4324-92af-45c110a6a637, isJobDone=false],
> jobCtx=GridJobContextImpl
> [jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59,
[jira] [Commented] (IGNITE-11939) IgnitePdsTxHistoricalRebalancingTest.testTopologyChangesWithConstantLoad test failure
[
https://issues.apache.org/jira/browse/IGNITE-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034455#comment-17034455
]
Ignite TC Bot commented on IGNITE-11939:
{panel:title=Branch: [pull/7400/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=5037998buildTypeId=IgniteTests24Java8_RunAll]
> IgnitePdsTxHistoricalRebalancingTest.testTopologyChangesWithConstantLoad
> test failure
> --
>
> Key: IGNITE-11939
> URL: https://issues.apache.org/jira/browse/IGNITE-11939
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Scherbakov
>Assignee: Mirza Aliev
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Caused by exception on releasing reserved segments:
> {noformat}
> [12:51:23]W: [org.apache.ignite:ignite-indexing] [2019-06-21
> 12:51:23,967][ERROR][exchange-worker-#33825%persistence.IgnitePdsTxHistoricalRebalancingTest1%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (rebalancing will be stopped)
> : GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=7,
> minorTopVer=1], discoEvt=DiscoveryCustomEvent
> [customMsg=CacheAffinityChangeMessage
> [id=08de0ff7b61-276ac575-e4dc-4525-b24b-d0a5d1d7633d,
> topVer=AffinityTopologyVersion [topVer=7, minorTopVer=0], exc
> hId=null, partsMsg=null, exchangeNeeded=true],
> affTopVer=AffinityTopologyVersion [topVer=7, minorTopVer=1],
> super=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=97e46568-6aa0-4a4b-864c-f05415c0,
> consistentId=persistence.IgnitePdsTxHistoricalRebalancingTest0, addrs=Arra
> yList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500,
> order=1, intOrder=1, lastExchangeTime=1561110643882, loc=false,
> ver=2.8.0#20190621-sha1:, isClient=false], topVer=7,
> nodeId8=0ff3354e, msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=15611106839
> 58]], nodeId=97e46568, evt=DISCOVERY_CUSTOM_EVT]
> [12:51:23]W: [org.apache.ignite:ignite-indexing]
> java.lang.AssertionError: cur=null, absIdx=0
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentReservationStorage.release(SegmentReservationStorage.java:55)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentAware.release(SegmentAware.java:207)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.release(FileWriteAheadLogManager.java:983)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.releaseHistoryForPreloading(GridCacheDatabaseSharedManager.java:1844)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1431)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:862)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3079)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2928)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> java.lang.Thread.run(Thread.java:748)
> [12:51:23]W: [org.apache.ignite:ignite-indexing] [12:51:23] (err)
> Failed to notify listener:
> o.a.i.i.processors.timeout.GridTimeoutProcessor$2...@79ba1907java.lang.AssertionError:
> cur=null, absIdx=0
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentReservationStorage.release(SegmentReservationStorage.java:55)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentAware.release(SegmentAware.java:207)
> [12:51:23]W:
[jira] [Commented] (IGNITE-12099) Don't write metadata to disk in discovery thread
[
https://issues.apache.org/jira/browse/IGNITE-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034439#comment-17034439
]
Ignite TC Bot commented on IGNITE-12099:
{panel:title=Branch: [pull/7396/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=5036477buildTypeId=IgniteTests24Java8_RunAll]
> Don't write metadata to disk in discovery thread
>
>
> Key: IGNITE-12099
> URL: https://issues.apache.org/jira/browse/IGNITE-12099
> Project: Ignite
> Issue Type: Improvement
> Components: binary
>Reporter: Denis Mekhanikov
>Assignee: Sergey Chugunov
>Priority: Major
>
> When persistence is enabled, binary metadata is written to disk upon
> registration. Currently it happens in the discovery thread, which makes
> processing of related messages very slow.
> A different thread should be used to write metadata to disk. Binary type
> registration will be considered finished before information about it is
> written to disks on all nodes.
> The implementation should guarantee consistency in cases of cluster restarts.
> Dev list discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/Asynchronous-registration-of-binary-metadata-td43021.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12659) [ML] Remove broken sub-modules in ML
[ https://issues.apache.org/jira/browse/IGNITE-12659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-12659: - Description: After testing phase we investigated that the next sub-modules are broken and should be removed from the release branch 2.8 * tensorflow (it uses deprecated IGFS and current solution in tf.contrib could n't connect to Ignite now) * tensorflow-ml-parser (it has a lot of bugs and doesn't work with tf 2.0) * mleap-ml-parser (CVE, Ignite ML couldn't work with metadata) * outdated genetic algorithms what are not supported now and are not formatted and refactored for the years (it's not a part of ML historically) also due to connect with Hadoop, Spark and another libraries it has a few CVE related to the old dependencies in Hadoop libraries P.S. I suppose all these solutions should be moved to the separate project ignite-ml-extensions for the independent developement was: After testing phase we investigated that the next sub-modules are broken and should be removed from the release branch 2.8 * tensorflow (it uses deprecated IGFS and current solution in tf.contrib could n't connect to Ignite now) * tensorflow-ml-parser (it has a lot of bugs and doesn't work with tf 2.0) * mleap-ml-parser (CVE, Ignite ML couldn't work with metadata) also due to connect with Hadoop, Spark and another libraries it has a few CVE related to the old dependencies in Hadoop libraries P.S. I suppose all these solutions should be moved to the separate project ignite-ml-extensions for the independent developement > [ML] Remove broken sub-modules in ML > > > Key: IGNITE-12659 > URL: https://issues.apache.org/jira/browse/IGNITE-12659 > Project: Ignite > Issue Type: Bug > Components: ml >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Major > Fix For: 2.8 > > > After testing phase we investigated that the next sub-modules are broken and > should be removed from the release branch 2.8 > * tensorflow (it uses deprecated IGFS and current solution in tf.contrib > could n't connect to Ignite now) > * tensorflow-ml-parser (it has a lot of bugs and doesn't work with tf 2.0) > * mleap-ml-parser (CVE, Ignite ML couldn't work with metadata) > * outdated genetic algorithms what are not supported now and are not > formatted and refactored for the years (it's not a part of ML historically) > also due to connect with Hadoop, Spark and another libraries it has a few CVE > related to the old dependencies in Hadoop libraries > > P.S. I suppose all these solutions should be moved to the separate project > ignite-ml-extensions for the independent developement -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12659) [ML] Remove broken sub-modules in ML
Alexey Zinoviev created IGNITE-12659: Summary: [ML] Remove broken sub-modules in ML Key: IGNITE-12659 URL: https://issues.apache.org/jira/browse/IGNITE-12659 Project: Ignite Issue Type: Bug Components: ml Reporter: Alexey Zinoviev Assignee: Alexey Zinoviev Fix For: 2.8 After testing phase we investigated that the next sub-modules are broken and should be removed from the release branch 2.8 * tensorflow (it uses deprecated IGFS and current solution in tf.contrib could n't connect to Ignite now) * tensorflow-ml-parser (it has a lot of bugs and doesn't work with tf 2.0) * mleap-ml-parser (CVE, Ignite ML couldn't work with metadata) also due to connect with Hadoop, Spark and another libraries it has a few CVE related to the old dependencies in Hadoop libraries P.S. I suppose all these solutions should be moved to the separate project ignite-ml-extensions for the independent developement -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12658) [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1 node
[
https://issues.apache.org/jira/browse/IGNITE-12658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Zinoviev reassigned IGNITE-12658:
Assignee: Alexey Zinoviev
> [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1
> node
>
>
> Key: IGNITE-12658
> URL: https://issues.apache.org/jira/browse/IGNITE-12658
> Project: Ignite
> Issue Type: Bug
> Components: examples, ml
>Affects Versions: 2.8
> Environment: Ubuntu/Win
> Java 8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Zinoviev
>Priority: Major
>
> Steps to reproduce:
> 1. Run Ignite node with org.apache.ignite.examples.ExampleNodeStartup (1
> node will be enough)
> 2. Run org.apache.ignite.examples.ml.tutorial.TutorialStepByStepExample
> Actual:
> On Step_8_CV_with_Param_Grid_and_metrics starting to throw a lot of
> exceptions
> {code:java}
> Train with p: 2 and maxDeep: 1
> >>> Trained model: if (x1 > 0.4368) then return 1. else return 0.
> >>> Accuracy 0.7679083094555874
> >>> Test Error 0.2320916905444126
> >>> Tutorial step 8 (cross-validation) example completed.
> [13:25:40] Ignite node stopped OK [uptime=00:00:17.453]
> >>> Tutorial step 8 (cross-validation with param grid) example started.
> [13:25:40]__
> [13:25:40] / _/ ___/ |/ / _/_ __/ __/
> [13:25:40] _/ // (7 7// / / / / _/
> [13:25:40] /___/\___/_/|_/___/ /_/ /___/
> [13:25:40]
> [13:25:40] ver. 2.8.0#20200130-sha1:f478aa56
> [13:25:40] 2020 Copyright(C) Apache Software Foundation
> [13:25:40]
> [13:25:40] Ignite documentation: http://ignite.apache.org
> [13:25:40]
> [13:25:40] Quiet mode.
> [13:25:40] ^-- Logging to file
> '/opt/buildagent/work/d501ae8146bd8253/i2test/var/suite-examples/app-ignite/work/log/ignite-e156b2f2.log'
> [13:25:40] ^-- Logging by 'Log4JLogger [quiet=true, config=null]'
> [13:25:40] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [13:25:40]
> [13:25:40] OS: Linux 4.15.0-65-generic amd64
> [13:25:40] VM information: Java(TM) SE Runtime Environment 1.8.0_221-b11
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.221-b11
> [13:25:40] Please set system property '-Djava.net.preferIPv4Stack=true' to
> avoid possible problems in mixed environments.
> [13:25:40] Configured plugins:
> [13:25:40] ^-- ml-inference-plugin 1.0.0
> [13:25:40] ^-- null
> [13:25:40]
> [13:25:40] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
> [tryStop=false, timeout=0, super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT
> [13:25:40] Message queue limit is set to 0 which may lead to potential OOMEs
> when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
> message queues growth on sender and receiver sides.
> [13:25:40] Security status [authentication=off, tls/ssl=off]
> [13:25:41] Performance suggestions for grid (fix if possible)
> [13:25:41] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [13:25:41] ^-- Disable grid events (remove 'includeEventTypes' from
> configuration)
> [13:25:41] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM
> options)
> [13:25:41] ^-- Set max direct memory size if getting 'OOME: Direct buffer
> memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
> [13:25:41] ^-- Disable processing of calls to System.gc() (add
> '-XX:+DisableExplicitGC' to JVM options)
> [13:25:41] Refer to this page for more performance suggestions:
> https://apacheignite.readme.io/docs/jvm-and-system-tuning
> [13:25:41]
> [13:25:41] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [13:25:41] Data Regions Configured:
> [13:25:41] ^-- Default_Region [initSize=500.0 MiB, maxSize=18.9 GiB,
> persistence=false, lazyMemoryAllocation=true]
> [13:25:41]
> [13:25:41] Ignite node started OK (id=e156b2f2)
> [13:25:41] Topology snapshot [ver=20, locNode=e156b2f2, servers=2, clients=0,
> state=ACTIVE, CPUs=5, offheap=38.0GB, heap=3.0GB]
> [13:25:41] ^-- Baseline [id=0, size=2, online=2, offline=0]
> [2020-02-11 13:25:42,428][ERROR][sys-#593][GridTaskWorker] Failed to obtain
> remote job result policy for result from ComputeTask.result(..) method (will
> fail the whole task): GridJobResultImpl [job=C2
> [c=o.a.i.ml.dataset.impl.cache.util.ComputeUtils$DeployableCallable@30e27659],
> sib=GridJobSiblingImpl
> [sesId=f9aced33071-e156b2f2-d116-4389-bd43-8536dc59,
> jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59,
> nodeId=f1135598-73c8-4324-92af-45c110a6a637, isJobDone=false],
> jobCtx=GridJobContextImpl
> [jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59,
[jira] [Assigned] (IGNITE-12657) ML examples EvaluatorExample and MultipleMetricsExample looks the same
[ https://issues.apache.org/jira/browse/IGNITE-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev reassigned IGNITE-12657: Assignee: Alexey Zinoviev > ML examples EvaluatorExample and MultipleMetricsExample looks the same > -- > > Key: IGNITE-12657 > URL: https://issues.apache.org/jira/browse/IGNITE-12657 > Project: Ignite > Issue Type: Bug > Components: examples, ml >Affects Versions: 2.8 >Reporter: Stepan Pilschikov >Assignee: Alexey Zinoviev >Priority: Major > > Examples > org.apache.ignite.examples.ml.selection.scoring.EvaluatorExample > and > org.apache.ignite.examples.ml.selection.scoring.MultipleMetricsExample > Looks exactly the same > I think MultipleMetricsExample is wrong because description told about using > KNNClassificationTrainer but actually used SVMLinearClassificationTrainer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12642) Fix a typo in the log message about the topology version context when check if rebalance should be started
[
https://issues.apache.org/jira/browse/IGNITE-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
masahiro ikeda closed IGNITE-12642.
---
> Fix a typo in the log message about the topology version context when check
> if rebalance should be started
> --
>
> Key: IGNITE-12642
> URL: https://issues.apache.org/jira/browse/IGNITE-12642
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: masahiro ikeda
>Assignee: masahiro ikeda
>Priority: Trivial
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When check if rebalance should be started, there is a assertion to check the
> context of the local and rebalance topology version.
> The assertion message contains a typo("hisroty").
> {code:java}
> "Empty hisroty allowed only for newly started cache group [rebTopVer=" +
> rebTopVer +
> ", localStartTopVer=" + grp.localStartVersion() + ']';
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12642) Fix a typo in the log message about the topology version context when check if rebalance should be started
[
https://issues.apache.org/jira/browse/IGNITE-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
masahiro ikeda reassigned IGNITE-12642:
---
Assignee: masahiro ikeda
> Fix a typo in the log message about the topology version context when check
> if rebalance should be started
> --
>
> Key: IGNITE-12642
> URL: https://issues.apache.org/jira/browse/IGNITE-12642
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: masahiro ikeda
>Assignee: masahiro ikeda
>Priority: Trivial
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When check if rebalance should be started, there is a assertion to check the
> context of the local and rebalance topology version.
> The assertion message contains a typo("hisroty").
> {code:java}
> "Empty hisroty allowed only for newly started cache group [rebTopVer=" +
> rebTopVer +
> ", localStartTopVer=" + grp.localStartVersion() + ']';
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12642) Fix a typo in the log message about the topology version context when check if rebalance should be started
[
https://issues.apache.org/jira/browse/IGNITE-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034429#comment-17034429
]
masahiro ikeda commented on IGNITE-12642:
-
[~Pavlukhin], thanks.
> Fix a typo in the log message about the topology version context when check
> if rebalance should be started
> --
>
> Key: IGNITE-12642
> URL: https://issues.apache.org/jira/browse/IGNITE-12642
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: masahiro ikeda
>Priority: Trivial
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When check if rebalance should be started, there is a assertion to check the
> context of the local and rebalance topology version.
> The assertion message contains a typo("hisroty").
> {code:java}
> "Empty hisroty allowed only for newly started cache group [rebTopVer=" +
> rebTopVer +
> ", localStartTopVer=" + grp.localStartVersion() + ']';
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11922) [IEP-35] Migrate ClusterMetricsMxBean
[ https://issues.apache.org/jira/browse/IGNITE-11922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11922: - Release Note: ClusterMetricsMxBean migrated to the new framework > [IEP-35] Migrate ClusterMetricsMxBean > - > > Key: IGNITE-11922 > URL: https://issues.apache.org/jira/browse/IGNITE-11922 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Ivan Fedotov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 4h > Remaining Estimate: 0h > > After merging of IGNITE-11848 we should migrate `ClusterMetricsMxBean` to the > new metric framework. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11921) [IEP-35] Migrate CacheGroupMetrics
[ https://issues.apache.org/jira/browse/IGNITE-11921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11921: - Release Note: CacheGroupMetrics migrated to the new framework > [IEP-35] Migrate CacheGroupMetrics > -- > > Key: IGNITE-11921 > URL: https://issues.apache.org/jira/browse/IGNITE-11921 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > After merging of IGNITE-11848 we should migrate `CacheGroupMetricsMXBean` to > the new metric framework. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11923) [IEP-35] Migrate IgniteMXBean
[ https://issues.apache.org/jira/browse/IGNITE-11923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11923: - Release Note: IgniteMXBean migrated to the new framework > [IEP-35] Migrate IgniteMXBean > - > > Key: IGNITE-11923 > URL: https://issues.apache.org/jira/browse/IGNITE-11923 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Sergey Kalashnikov >Priority: Major > Labels: IEP-35, await > Fix For: 2.8 > > Time Spent: 3h > Remaining Estimate: 0h > > After merging of IGNITE-11848 we should migrate `IgniteMXBean` to the new > metric framework. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11925) [IEP-35] Migrage QueryMetrics
[ https://issues.apache.org/jira/browse/IGNITE-11925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11925: - Release Note: QueryMetrics migrated to the new framework > [IEP-35] Migrage QueryMetrics > - > > Key: IGNITE-11925 > URL: https://issues.apache.org/jira/browse/IGNITE-11925 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > After merging of IGNITE-11848 we should migrate `QueryMetrics` to the new > metric framework. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11924) [IEP-35] Migrate TransactionMetricsMxBean
[ https://issues.apache.org/jira/browse/IGNITE-11924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11924: - Release Note: TransactionMetricsMxBean migrated to the new framework > [IEP-35] Migrate TransactionMetricsMxBean > - > > Key: IGNITE-11924 > URL: https://issues.apache.org/jira/browse/IGNITE-11924 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > After merging of IGNITE-11848 we should migrate `TransactionMetricsMxBean` to > the new metric framework. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11941) [IEP-35] Rewrite GridLocalMetrics using new framework
[ https://issues.apache.org/jira/browse/IGNITE-11941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11941: - Release Note: GridLocalMetrics migrated to the new framework > [IEP-35] Rewrite GridLocalMetrics using new framework > - > > Key: IGNITE-11941 > URL: https://issues.apache.org/jira/browse/IGNITE-11941 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 50m > Remaining Estimate: 0h > > 1. GridLocalMetrics should be moved to GridMetricManager > 2. Standard JVM JMX beans should be registered as metrics on startup. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11926) [IEP-35] Migrage GridJobMetricsProcessor
[ https://issues.apache.org/jira/browse/IGNITE-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11926: - Release Note: GridJobMetricsProcessor migrated to the new framework > [IEP-35] Migrage GridJobMetricsProcessor > > > Key: IGNITE-11926 > URL: https://issues.apache.org/jira/browse/IGNITE-11926 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > After merging of IGNITE-11848 we should migrate `GridJobMetricsProcessor` to > the new metric framework. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11987) [IEP-35] Add ability to configure metrics
[ https://issues.apache.org/jira/browse/IGNITE-11987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11987: - Release Note: Metrics configuration via JMX added. > [IEP-35] Add ability to configure metrics > - > > Key: IGNITE-11987 > URL: https://issues.apache.org/jira/browse/IGNITE-11987 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 10h 50m > Remaining Estimate: 0h > > Ignite should be able to: > * Configure Histogram metrics > * Configure HitRate metrics. > We should provide 2 ways to configure metric: > 1. -Configuration file.- Discussed on dev-list. Agreed to go with the > simplest solution - JMX method. > 2. JMX method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11961) Provide JMX metrics for PME timings
[ https://issues.apache.org/jira/browse/IGNITE-11961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11961: - Release Note: Metrics for PME timings added. > Provide JMX metrics for PME timings > --- > > Key: IGNITE-11961 > URL: https://issues.apache.org/jira/browse/IGNITE-11961 > Project: Ignite > Issue Type: Improvement >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 7h 50m > Remaining Estimate: 0h > > Currently, partition map exchange timings printed to log(IGNITE-10493). It > will be useful if we allow external tools to collect and aggregate partition > map exchange metrics. > UPD: Need to implement next metrics: > - `CurrentPMEDuration` - existing metric, shows current PME duration. > - `CurrentPMECacheOperationsBlockedDuration` - new long metric. show > blocking duration of PME. > - `PMEDuration` - histogram of full PME durations. > - `PMECacheOperationsBlockedDuration` - histogram of blocking PME durations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12108) [IEP-35] Migrate Communication Metrics.
[ https://issues.apache.org/jira/browse/IGNITE-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12108: - Release Note: Communication metrics migrated to the new framework. > [IEP-35] Migrate Communication Metrics. > --- > > Key: IGNITE-12108 > URL: https://issues.apache.org/jira/browse/IGNITE-12108 > Project: Ignite > Issue Type: New Feature >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: IEP-35, await > Fix For: 2.8 > > Time Spent: 9h 10m > Remaining Estimate: 0h > > ||*Name*||*Description*|| > |communication.tcp.outboundMessagesQueueSize|Number of messages waiting to be > sent| > |communication.tcp.sentBytes|Total number of bytes received by current node| > |communication.tcp.receivedBytes|Total number of bytes sent by current node| > |communication.tcp.sentMessagesCount|Total number of messages sent by current > node| > |communication.tcp.receivedMessagesCount|Total number of messages received by > current node| > |communication.tcp.sentMessagesByType.|Total number of messages > with given type sent by current node| > |communication.tcp.receivedMessagesByType.|Total number of > messages with given type received by current node| > |communication.tcp..sentMessagesToNode|Total number of messages sent > by current node to the given node| > |communication.tcp..receivedMessagesFromNode|Total number of messages > received by current node from the given node| > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12145) [IEP-35] Monitoring list engine
[ https://issues.apache.org/jira/browse/IGNITE-12145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12145: - Release Note: An internal framework to expose objects as system views added. SQL, JMX exporters supported "out of the box" > [IEP-35] Monitoring list engine > --- > > Key: IGNITE-12145 > URL: https://issues.apache.org/jira/browse/IGNITE-12145 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.5 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 20h 40m > Remaining Estimate: 0h > > The base engine for the monitoring list. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12185) [IEP-35] Add metrics - how many indexes are left to rebuild
[ https://issues.apache.org/jira/browse/IGNITE-12185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12185: - Release Note: Metrics to show if index building in progress added. > [IEP-35] Add metrics - how many indexes are left to rebuild > --- > > Key: IGNITE-12185 > URL: https://issues.apache.org/jira/browse/IGNITE-12185 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr Brazhnikov >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-35, await > Fix For: 2.8 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > We want to know how many indexes are left to rebuild at the moment. The > result must be an integer. The information must be in JMX, with no statistics > enabled on the caches. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12209) Transaction system view
[ https://issues.apache.org/jira/browse/IGNITE-12209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12209: - Release Note: Transaction system view added. > Transaction system view > --- > > Key: IGNITE-12209 > URL: https://issues.apache.org/jira/browse/IGNITE-12209 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 2h > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add transactions to the system views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12211) Client connections system view
[ https://issues.apache.org/jira/browse/IGNITE-12211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12211: - Release Note: Client connections(JDBC, ODBC, Thin) system view added. > Client connections system view > -- > > Key: IGNITE-12211 > URL: https://issues.apache.org/jira/browse/IGNITE-12211 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add client connections to the system views. > System view should track JDBC, ODBC and thin connections. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12212) Nodes system view
[ https://issues.apache.org/jira/browse/IGNITE-12212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12212: - Release Note: Cluster nodes system view added. > Nodes system view > - > > Key: IGNITE-12212 > URL: https://issues.apache.org/jira/browse/IGNITE-12212 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35, await > Fix For: 2.8 > > Time Spent: 1h > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add nodes system views. > System view should track current topology nodes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12213) Sql objects system views
[ https://issues.apache.org/jira/browse/IGNITE-12213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12213: - Release Note: System views for schema, tables, views, indexes, columns added. > Sql objects system views > > > Key: IGNITE-12213 > URL: https://issues.apache.org/jira/browse/IGNITE-12213 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35, await > Fix For: 2.8 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add SQL objects system views. > * Schemas > * Tables > * Indexes > * SQL queries -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12214) Continuous query system view
[ https://issues.apache.org/jira/browse/IGNITE-12214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12214: - Release Note: Continuous query system view added. > Continuous query system view > > > Key: IGNITE-12214 > URL: https://issues.apache.org/jira/browse/IGNITE-12214 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35, await > Fix For: 2.8 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add continuous query system views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12219) Cache operations performance metrics
[ https://issues.apache.org/jira/browse/IGNITE-12219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12219: - Release Note: Metrics to measure cache API performance added. > Cache operations performance metrics > > > Key: IGNITE-12219 > URL: https://issues.apache.org/jira/browse/IGNITE-12219 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-35, await > Fix For: 2.8 > > Time Spent: 5h 20m > Remaining Estimate: 0h > > We need to provide cache operations histogram metrics > Next API and its variants should be covered: > * get > * put > * remove -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12223) Scan query system view
[ https://issues.apache.org/jira/browse/IGNITE-12223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12223: - Release Note: Scan query system view added. > Scan query system view > -- > > Key: IGNITE-12223 > URL: https://issues.apache.org/jira/browse/IGNITE-12223 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35, await > Fix For: 2.8 > > Time Spent: 1.5h > Remaining Estimate: 0h > > We need to add a system views for Scan queries -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12642) Fix a typo in the log message about the topology version context when check if rebalance should be started
[
https://issues.apache.org/jira/browse/IGNITE-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034412#comment-17034412
]
Ivan Pavlukhin commented on IGNITE-12642:
-
[~mikecaat], I added you to the contributors list.
> Fix a typo in the log message about the topology version context when check
> if rebalance should be started
> --
>
> Key: IGNITE-12642
> URL: https://issues.apache.org/jira/browse/IGNITE-12642
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: masahiro ikeda
>Priority: Trivial
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When check if rebalance should be started, there is a assertion to check the
> context of the local and rebalance topology version.
> The assertion message contains a typo("hisroty").
> {code:java}
> "Empty hisroty allowed only for newly started cache group [rebTopVer=" +
> rebTopVer +
> ", localStartTopVer=" + grp.localStartVersion() + ']';
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12224) SQL query system view
[ https://issues.apache.org/jira/browse/IGNITE-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12224: - Release Note: SQL query system view added. > SQL query system view > - > > Key: IGNITE-12224 > URL: https://issues.apache.org/jira/browse/IGNITE-12224 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35, await > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We need to add system view for a SQL queries -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12301) Free-lists system view
[ https://issues.apache.org/jira/browse/IGNITE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12301: - Release Note: Free-lists system view added. > Free-lists system view > -- > > Key: IGNITE-12301 > URL: https://issues.apache.org/jira/browse/IGNITE-12301 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: IEP-35 > Fix For: 2.9 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Implement a system view for free-lists monitoring. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12393) Striped thread pool queue system view
[
https://issues.apache.org/jira/browse/IGNITE-12393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-12393:
-
Release Note: Striped thread pool queue system view added.
> Striped thread pool queue system view
> -
>
> Key: IGNITE-12393
> URL: https://issues.apache.org/jira/browse/IGNITE-12393
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When in the production environment exist some cluster performance issues
> usually it leads to the large striped executor queue size.
> The number of tasks in the queue can observe by
> {StripedExecutorMXBean#getTotalQueueSize} metric. In the case queue size
> becomes large it's useful to have the ability to know what tasks are waiting
> for execution in the thread pool.
> Especially, for dealing with failover scenarios.
> We should create a system views to expose information about striped executor
> services queue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12450) Transaction operations metrics
[ https://issues.apache.org/jira/browse/IGNITE-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12450: - Release Note: Metrics for transaction duration added. > Transaction operations metrics > -- > > Key: IGNITE-12450 > URL: https://issues.apache.org/jira/browse/IGNITE-12450 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > We should add histogram metrics that measure tx.commit and tx.rollback time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12553) [IEP-35] public Java metric API
[ https://issues.apache.org/jira/browse/IGNITE-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12553: - Release Note: An internal framework to store and update metrics implemented. JMX, SQL, Log, OpenCensus exporters supported "out of the box". > [IEP-35] public Java metric API > --- > > Key: IGNITE-12553 > URL: https://issues.apache.org/jira/browse/IGNITE-12553 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.9 > > Time Spent: 20m > Remaining Estimate: 0h > > Right now, there is no simple way to get metrics values from the java code. > We need to create a java API to access metric values. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12642) Fix a typo in the log message about the topology version context when check if rebalance should be started
[
https://issues.apache.org/jira/browse/IGNITE-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034407#comment-17034407
]
masahiro ikeda commented on IGNITE-12642:
-
[~Pavlukhin], thanks for reviewing the patch and teaching me the good workflow
to contribute! Please attach a _contributor_ role to my account. I subscribed
the mailing lists for user and developers, by the way.
> Fix a typo in the log message about the topology version context when check
> if rebalance should be started
> --
>
> Key: IGNITE-12642
> URL: https://issues.apache.org/jira/browse/IGNITE-12642
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: masahiro ikeda
>Priority: Trivial
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When check if rebalance should be started, there is a assertion to check the
> context of the local and rebalance topology version.
> The assertion message contains a typo("hisroty").
> {code:java}
> "Empty hisroty allowed only for newly started cache group [rebTopVer=" +
> rebTopVer +
> ", localStartTopVer=" + grp.localStartVersion() + ']';
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-6804) Print a warning if HashMap is passed into bulk update operations
[
https://issues.apache.org/jira/browse/IGNITE-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034404#comment-17034404
]
Andrey N. Gura commented on IGNITE-6804:
[~ilyak] It us unimportant after removal of deadlock detection related logic.
One cosmetic comment: {{Map}} and {{Collection}} parameters in
{{warnIfUnordered}} should be declared as {{Map}} and {{Collection}}
respectively.
LGTM. Please proceed with merge.
> Print a warning if HashMap is passed into bulk update operations
>
>
> Key: IGNITE-6804
> URL: https://issues.apache.org/jira/browse/IGNITE-6804
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Denis A. Magda
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Labels: usability
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> Ignite newcomers tend to stumble on deadlocks simply because the keys are
> passed in an unordered HashMap. Propose to do the following:
> * update bulk operations Java docs.
> * print out a warning if not SortedMap (e.g. HashMap,
> Weak/Identity/Concurrent/Linked HashMap etc) is passed into
> a bulk method (instead of SortedMap) and contains more than 1 element.
> However, we should make sure that we only print that warning once and not
> every time the API is called.
> * do not produce warning for explicit optimistic transactions
> More details are here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-Ignite-2-0-0-GridUnsafe-unmonitor-td23706.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12638) Classes persisted by DistributedMetaStorage are not IgniteDTO
[ https://issues.apache.org/jira/browse/IGNITE-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034395#comment-17034395 ] Dmitriy Govorukhin edited comment on IGNITE-12638 at 2/11/20 12:17 PM: --- [~ibessonov] Looks good to me! Thanks! was (Author: dmitriygovorukhin): [~ibessonov]Looks good to me! Thanks! > Classes persisted by DistributedMetaStorage are not IgniteDTO > - > > Key: IGNITE-12638 > URL: https://issues.apache.org/jira/browse/IGNITE-12638 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > This has to be fixed to simplify future modification of component. > DistributedMetaStorageHistoryItem and DistributedMetaStorageVersion will be > persisted on disc so we need to have a reliable way to read them even when > classes will be updated in the future. IgniteDataTransferObject is the > standard option for such cases - it allows versioning of serialization format. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12638) Classes persisted by DistributedMetaStorage are not IgniteDTO
[ https://issues.apache.org/jira/browse/IGNITE-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034395#comment-17034395 ] Dmitriy Govorukhin commented on IGNITE-12638: - [~ibessonov]Looks good to me! Thanks! > Classes persisted by DistributedMetaStorage are not IgniteDTO > - > > Key: IGNITE-12638 > URL: https://issues.apache.org/jira/browse/IGNITE-12638 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > This has to be fixed to simplify future modification of component. > DistributedMetaStorageHistoryItem and DistributedMetaStorageVersion will be > persisted on disc so we need to have a reliable way to read them even when > classes will be updated in the future. IgniteDataTransferObject is the > standard option for such cases - it allows versioning of serialization format. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12638) Classes persisted by DistributedMetaStorage are not IgniteDTO
[ https://issues.apache.org/jira/browse/IGNITE-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-12638: --- Description: This has to be fixed to simplify future modification of component. DistributedMetaStorageHistoryItem and DistributedMetaStorageVersion will be persisted on disc so we need to have a reliable way to read them even when classes will be updated in the future. IgniteDataTransferObject is the standard option for such cases - it allows versioning of serialization format. was: This has to be fixed to simplify future modification of component. > Classes persisted by DistributedMetaStorage are not IgniteDTO > - > > Key: IGNITE-12638 > URL: https://issues.apache.org/jira/browse/IGNITE-12638 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > This has to be fixed to simplify future modification of component. > DistributedMetaStorageHistoryItem and DistributedMetaStorageVersion will be > persisted on disc so we need to have a reliable way to read them even when > classes will be updated in the future. IgniteDataTransferObject is the > standard option for such cases - it allows versioning of serialization format. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11402) SQL: Add ability to specify inline size of PK and affinity key indexes from CREATE TABLE and QueryEntity
[ https://issues.apache.org/jira/browse/IGNITE-11402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11402: --- Description: Currently it is not possible to set inline size for automatically created indexes easily. We need to make sure that user has a convenient way to set them both programmatically and from DDL. Start point for automatically created indexes is org.apache.ignite.internal.processors.query.h2.H2TableDescriptor#createSystemIndexes where passed parameter inlineSize as -1 for org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing#createSortedIndex was:Currently it is not possible to set inline size for automatically created indexes easily. We need to make sure that user has a convenient way to set them both programmatically and from DDL. > SQL: Add ability to specify inline size of PK and affinity key indexes from > CREATE TABLE and QueryEntity > > > Key: IGNITE-11402 > URL: https://issues.apache.org/jira/browse/IGNITE-11402 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Priority: Major > Labels: newbie > Fix For: 2.9 > > > Currently it is not possible to set inline size for automatically created > indexes easily. We need to make sure that user has a convenient way to set > them both programmatically and from DDL. > Start point for automatically created indexes is > org.apache.ignite.internal.processors.query.h2.H2TableDescriptor#createSystemIndexes > where passed parameter inlineSize as -1 for > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing#createSortedIndex -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12638) Classes persisted by DistributedMetaStorage are not IgniteDTO
[ https://issues.apache.org/jira/browse/IGNITE-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-12638: --- Description: This has to be fixed to simplify future modification of component. was:This has to be fixed to simplify future modification of component. > Classes persisted by DistributedMetaStorage are not IgniteDTO > - > > Key: IGNITE-12638 > URL: https://issues.apache.org/jira/browse/IGNITE-12638 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > This has to be fixed to simplify future modification of component. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12609) SQL: GridReduceQueryExecutor refactoring.
[ https://issues.apache.org/jira/browse/IGNITE-12609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034380#comment-17034380 ] Taras Ledkov commented on IGNITE-12609: --- [~amashenkov], the patch is OK with me. > SQL: GridReduceQueryExecutor refactoring. > - > > Key: IGNITE-12609 > URL: https://issues.apache.org/jira/browse/IGNITE-12609 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: refactoring > Time Spent: 10m > Remaining Estimate: 0h > > For now we have few issues that can be resolved. > 1. We create fake H2 tables\indices for reduce stage even if there is no need > to do so (skipMergeTable=true. > Let's decouple reduce logic from H2Index adapter code. > 2. Partition mapping code look to complicated and non-optimal. > Let's use cached affinity mapping and avoid collections copying when possible. > 3. Also there is no sense to pass RequestID to mapping code just for logging. > We'll never be able to match any request as no query really exists at a time > when error with RequestID is logged. > 4. Replicated only flag value semantic (calculation and usage) is not clear. > 5. GridReduceQueryExecutor.reduce() method is too long (over 400 lines). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12590) MERGE INTO query is failing on Ignite client node
[
https://issues.apache.org/jira/browse/IGNITE-12590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034372#comment-17034372
]
Taras Ledkov commented on IGNITE-12590:
---
[~amashenkov], [~Pavlukhin] please review the patch.
> MERGE INTO query is failing on Ignite client node
> -
>
> Key: IGNITE-12590
> URL: https://issues.apache.org/jira/browse/IGNITE-12590
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Precondition: server nodes (any amount), webconsole is running.
> 1. Create the table as following:
> CREATE TABLE USERPUBSTATICDATA (BOOK VARCHAR, DESK VARCHAR, TRADERS VARCHAR,
> REGION VARCHAR, LOB VARCHAR, EXCLUDE VARCHAR, TRANSIT VARCHAR,
> MAPBOOKTOTHISBOOK VARCHAR, CONSTRAINT USERPUBSTATICDATA_PK PRIMARY KEY
> (BOOK,DESK)) WITH "template=replicated"
> 2. Execute merge into query:
> MERGE INTO USERPUBSTATICDATA(BOOK, DESK, TRADERS, REGION, LOB, EXCLUDE,
> TRANSIT, MAPBOOKTOTHISBOOK) VALUES('CADOIS', 'FRT TOR', 'Robin Das/Dave
> Carlson', 'Toronto', 'FRT', null, null, 'CADOIS');
> Step 2 is successfull on Web Console and called on IgniteCache from the
> server node, but fails when called from the Ignite client node with exception:
> {code}
> javax.cache.CacheException: Invalid column name in KEYS clause of MERGE - it
> may include only key and/or affinity columns: BOOK
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12651) Non-comparable keys for eviction policy cause failure handle and node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-12651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034354#comment-17034354
]
Ignite TC Bot commented on IGNITE-12651:
{panel:title=Branch: [pull/7397/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=5037062buildTypeId=IgniteTests24Java8_RunAll]
> Non-comparable keys for eviction policy cause failure handle and node shutdown
> --
>
> Key: IGNITE-12651
> URL: https://issues.apache.org/jira/browse/IGNITE-12651
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Non-comparable keys in the same cache (for instance, Integer and Double) and
> eviction policy enabled results in node failure with the following exception:
> {code:java}
> java.lang.ClassCastException: java.lang.Integer cannot be cast to
> java.lang.Doublejava.lang.ClassCastException: java.lang.Integer cannot be
> cast to java.lang.Double at java.lang.Double.compareTo(Double.java:49) at
> org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicy$DefaultHolderComparator.compare(SortedEvictionPolicy.java:360)
> at
> org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicy$DefaultHolderComparator.compare(SortedEvictionPolicy.java:348)
> at
> java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
> at
> java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:835)
> at
> java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1962)
> at
> org.apache.ignite.internal.util.GridConcurrentSkipListSet.add(GridConcurrentSkipListSet.java:143)
> at
> org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicy$GridConcurrentSkipListSetEx.add(SortedEvictionPolicy.java:398)
> at
> org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicy.touch(SortedEvictionPolicy.java:176)
> at
> org.apache.ignite.cache.eviction.AbstractEvictionPolicy.onEntryAccessed(AbstractEvictionPolicy.java:88)
> at
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.notifyPolicy(GridCacheEvictionManager.java:321)
> at
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(GridCacheEvictionManager.java:199)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12658) [ML][Examples] TutorialStepByStepExample failed on cluster with more then 1 node
Stepan Pilschikov created IGNITE-12658:
--
Summary: [ML][Examples] TutorialStepByStepExample failed on
cluster with more then 1 node
Key: IGNITE-12658
URL: https://issues.apache.org/jira/browse/IGNITE-12658
Project: Ignite
Issue Type: Bug
Components: examples, ml
Affects Versions: 2.8
Environment: Ubuntu/Win
Java 8
Reporter: Stepan Pilschikov
Steps to reproduce:
1. Run Ignite node with org.apache.ignite.examples.ExampleNodeStartup (1 node
will be enough)
2. Run org.apache.ignite.examples.ml.tutorial.TutorialStepByStepExample
Actual:
On Step_8_CV_with_Param_Grid_and_metrics starting to throw a lot of exceptions
{code:java}
Train with p: 2 and maxDeep: 1
>>> Trained model: if (x1 > 0.4368) then return 1. else return 0.
>>> Accuracy 0.7679083094555874
>>> Test Error 0.2320916905444126
>>> Tutorial step 8 (cross-validation) example completed.
[13:25:40] Ignite node stopped OK [uptime=00:00:17.453]
>>> Tutorial step 8 (cross-validation with param grid) example started.
[13:25:40]__
[13:25:40] / _/ ___/ |/ / _/_ __/ __/
[13:25:40] _/ // (7 7// / / / / _/
[13:25:40] /___/\___/_/|_/___/ /_/ /___/
[13:25:40]
[13:25:40] ver. 2.8.0#20200130-sha1:f478aa56
[13:25:40] 2020 Copyright(C) Apache Software Foundation
[13:25:40]
[13:25:40] Ignite documentation: http://ignite.apache.org
[13:25:40]
[13:25:40] Quiet mode.
[13:25:40] ^-- Logging to file
'/opt/buildagent/work/d501ae8146bd8253/i2test/var/suite-examples/app-ignite/work/log/ignite-e156b2f2.log'
[13:25:40] ^-- Logging by 'Log4JLogger [quiet=true, config=null]'
[13:25:40] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
"-v" to ignite.{sh|bat}
[13:25:40]
[13:25:40] OS: Linux 4.15.0-65-generic amd64
[13:25:40] VM information: Java(TM) SE Runtime Environment 1.8.0_221-b11 Oracle
Corporation Java HotSpot(TM) 64-Bit Server VM 25.221-b11
[13:25:40] Please set system property '-Djava.net.preferIPv4Stack=true' to
avoid possible problems in mixed environments.
[13:25:40] Configured plugins:
[13:25:40] ^-- ml-inference-plugin 1.0.0
[13:25:40] ^-- null
[13:25:40]
[13:25:40] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
[tryStop=false, timeout=0, super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT
[13:25:40] Message queue limit is set to 0 which may lead to potential OOMEs
when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
message queues growth on sender and receiver sides.
[13:25:40] Security status [authentication=off, tls/ssl=off]
[13:25:41] Performance suggestions for grid (fix if possible)
[13:25:41] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[13:25:41] ^-- Disable grid events (remove 'includeEventTypes' from
configuration)
[13:25:41] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM options)
[13:25:41] ^-- Set max direct memory size if getting 'OOME: Direct buffer
memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
[13:25:41] ^-- Disable processing of calls to System.gc() (add
'-XX:+DisableExplicitGC' to JVM options)
[13:25:41] Refer to this page for more performance suggestions:
https://apacheignite.readme.io/docs/jvm-and-system-tuning
[13:25:41]
[13:25:41] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[13:25:41] Data Regions Configured:
[13:25:41] ^-- Default_Region [initSize=500.0 MiB, maxSize=18.9 GiB,
persistence=false, lazyMemoryAllocation=true]
[13:25:41]
[13:25:41] Ignite node started OK (id=e156b2f2)
[13:25:41] Topology snapshot [ver=20, locNode=e156b2f2, servers=2, clients=0,
state=ACTIVE, CPUs=5, offheap=38.0GB, heap=3.0GB]
[13:25:41] ^-- Baseline [id=0, size=2, online=2, offline=0]
[2020-02-11 13:25:42,428][ERROR][sys-#593][GridTaskWorker] Failed to obtain
remote job result policy for result from ComputeTask.result(..) method (will
fail the whole task): GridJobResultImpl [job=C2
[c=o.a.i.ml.dataset.impl.cache.util.ComputeUtils$DeployableCallable@30e27659],
sib=GridJobSiblingImpl [sesId=f9aced33071-e156b2f2-d116-4389-bd43-8536dc59,
jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59,
nodeId=f1135598-73c8-4324-92af-45c110a6a637, isJobDone=false],
jobCtx=GridJobContextImpl
[jobId=1aaced33071-e156b2f2-d116-4389-bd43-8536dc59, timeoutObj=null,
attrs=HashMap {}], node=TcpDiscoveryNode
[id=f1135598-73c8-4324-92af-45c110a6a637,
consistentId=127.0.0.1,192.168.112.2:47500, addrs=ArrayList [127.0.0.1,
192.168.112.2], sockAddrs=HashSet [/127.0.0.1:47500,
87bf29244900/192.168.112.2:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1581416741501, loc=false, ver=2.8.0#20200130-sha1:f478aa56,
isClient=false], ex=class o.a.i.IgniteException: Failed to deserialize object
[jira] [Commented] (IGNITE-12646) When DEBUG mode is enabled GridToStringBuilder may throw java.util.ConcurrentModificationException
[
https://issues.apache.org/jira/browse/IGNITE-12646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034345#comment-17034345
]
Ignite TC Bot commented on IGNITE-12646:
{panel:title=Branch: [pull/7389/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=5036593buildTypeId=IgniteTests24Java8_RunAll]
> When DEBUG mode is enabled GridToStringBuilder may throw
> java.util.ConcurrentModificationException
> --
>
> Key: IGNITE-12646
> URL: https://issues.apache.org/jira/browse/IGNITE-12646
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.9
>
>
> With DEBUG enabled many components like CommunicationSPI start to log much
> larger chunks of information e.g. communication messages are logged as is.
> When big enough message with non-thread safe collection inside is logged by
> communication thread it is possible that some other thread started processing
> the same message. If processing involves modifying of the collection
> communication thread will get ConcurrentModificationException when in the
> middle of iterating over it.
> GridToStringBuilder should be safe from throwing this exception and
> (optionally) any type of RuntimeException.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12522) Extend test coverage [IGNITE-12104] Check deployment from cache before to load it from local or version storage
[ https://issues.apache.org/jira/browse/IGNITE-12522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-12522: -- Fix Version/s: 2.9 > Extend test coverage [IGNITE-12104] Check deployment from cache before to > load it from local or version storage > --- > > Key: IGNITE-12522 > URL: https://issues.apache.org/jira/browse/IGNITE-12522 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12616) At start grid need twice enter psswords for keystore and truststore.
[ https://issues.apache.org/jira/browse/IGNITE-12616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034288#comment-17034288 ] Alexey Goncharuk commented on IGNITE-12616: --- [~ktkale...@gridgain.com] should we add a test for this scenario? > At start grid need twice enter psswords for keystore and truststore. > > > Key: IGNITE-12616 > URL: https://issues.apache.org/jira/browse/IGNITE-12616 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > At start grid with keystore and truststore parameters but without password, > need twice enter psswords for keystore and truststore (before and after enter > password for user accaunt). > sequencing: > 1.Start grid: bin/control.sh --deactivate --host test_host --user test_user > --keystore /usr/key_store/keystore.jks --truststore > /usr/key_store/truststore.jks > 2. Enter password for keystore > 3. Enter password for truststore > 4. Enter password for user accaunt > 5. Second time enter password for keystore > 6. Second time enter password for trustore > 7. Doing start... > Expected result : all without 5-6. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12522) Extend test coverage [IGNITE-12104] Check deployment from cache before to load it from local or version storage
[ https://issues.apache.org/jira/browse/IGNITE-12522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-12522: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Extend test coverage [IGNITE-12104] Check deployment from cache before to > load it from local or version storage > --- > > Key: IGNITE-12522 > URL: https://issues.apache.org/jira/browse/IGNITE-12522 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12438) Extend communication protocol to establish client-server connection
[ https://issues.apache.org/jira/browse/IGNITE-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov reassigned IGNITE-12438: -- Assignee: Ivan Bessonov > Extend communication protocol to establish client-server connection > --- > > Key: IGNITE-12438 > URL: https://issues.apache.org/jira/browse/IGNITE-12438 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Ivan Bessonov >Priority: Major > > Recently there was quite a lot of questions related to thick clients > connectivity issues when the clients are deployed in a k8s pod [1]. The > general issue here is clients reporting network address which are not > reachable from server nodes. At the same time, the clients can connect to > server nodes. > An idea of how to fix this is as follows: > * Make sure that think clients discovery SPI always maintains a connection > to a server node (this should be already implemented) > * (Optionally) detect when a client has only one-way connectivity with the > server nodes. This part should be investigated. We need this to avoid server > nodes attempt to connect to a client and send communication request to the > client node faster > * When a server attempts to establish a connection with a client, check if > client is unreachable or the previous connection attempt failed. If so, send > a discovery message to the client to force a client-server connection. In > this case, server will be able to send the original message via the newly > established connection. > [1] > https://stackoverflow.com/questions/59192075/ignite-communicationspi-questions-in-paas-environment/59232504 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-9490) Connection.getMetaData.getIndexInfo method doesn't return PK indexes
[
https://issues.apache.org/jira/browse/IGNITE-9490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich resolved IGNITE-9490.
---
Resolution: Duplicate
The issue should be fixed during implementation IGNITE-11368
> Connection.getMetaData.getIndexInfo method doesn't return PK indexes
>
>
> Key: IGNITE-9490
> URL: https://issues.apache.org/jira/browse/IGNITE-9490
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.6
>Reporter: Yury Gerzhedovich
>Priority: Major
> Labels: newbie
>
> Connection.getMetaData.getIndexInfo method doesn't return PK indexes.
> Apache Ignite should return all exists indexes include PK one.
> Also order of result should be correspond Javadoc ('ordered by NON_UNIQUE,
> TYPE, INDEX_NAME, and ORDINAL_POSITION') - at present it is not so.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11368) use the same information about indexes for JDBC drivers as for system view INDEXES
[
https://issues.apache.org/jira/browse/IGNITE-11368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-11368:
---
Description:
As of now indexes information for JDBC drivers get by another way then system
SQL view INDEXES. Need to use single source of the information to have
consistent picture.
So, JDBC drivers should use the same source as SQL view INDEXES
(org.apache.ignite.internal.processors.query.h2.sys.view.SqlSystemViewIndexes)
Start point for JDBC index metadata is
org.apache.ignite.internal.jdbc2.JdbcDatabaseMetadata#getIndexInfo
Also order of result should be correspond Javadoc ('ordered by NON_UNIQUE,
TYPE, INDEX_NAME, and ORDINAL_POSITION') - at present it is not so.
was:
As of now indexes information for JDBC drivers get by another way then system
SQL view INDEXES. Need to use single source of the information to have
consistent picture.
So, JDBC drivers should use the same source as SQL view INDEXES
(org.apache.ignite.internal.processors.query.h2.sys.view.SqlSystemViewIndexes)
Start point for JDBC index metadata is
org.apache.ignite.internal.processors.odbc.jdbc.JdbcMetadataInfo#getIndexesMeta
> use the same information about indexes for JDBC drivers as for system view
> INDEXES
> --
>
> Key: IGNITE-11368
> URL: https://issues.apache.org/jira/browse/IGNITE-11368
> Project: Ignite
> Issue Type: Task
> Components: jdbc, odbc, sql
>Reporter: Yury Gerzhedovich
>Priority: Major
> Labels: newbie
> Fix For: 2.9
>
>
> As of now indexes information for JDBC drivers get by another way then system
> SQL view INDEXES. Need to use single source of the information to have
> consistent picture.
> So, JDBC drivers should use the same source as SQL view INDEXES
> (org.apache.ignite.internal.processors.query.h2.sys.view.SqlSystemViewIndexes)
> Start point for JDBC index metadata is
> org.apache.ignite.internal.jdbc2.JdbcDatabaseMetadata#getIndexInfo
> Also order of result should be correspond Javadoc ('ordered by NON_UNIQUE,
> TYPE, INDEX_NAME, and ORDINAL_POSITION') - at present it is not so.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12642) Fix a typo in the log message about the topology version context when check if rebalance should be started
[
https://issues.apache.org/jira/browse/IGNITE-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034269#comment-17034269
]
Ivan Pavlukhin commented on IGNITE-12642:
-
[~mikecaat], I applied your patch to the mater branch. Thank you for
contribution!
Generally, it is good to assign an issue to yourself and move it to _patch
available_ status as long as a pull request is ready. This way people actively
doing a code review will see the ticket on a review board. A _contributor_ role
in JIRA is needed to assign issues and change statuses. Would you like to be
added to a contributors list?
Usual contribution process is described in
https://ignite.apache.org/community/contribute.html
> Fix a typo in the log message about the topology version context when check
> if rebalance should be started
> --
>
> Key: IGNITE-12642
> URL: https://issues.apache.org/jira/browse/IGNITE-12642
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: masahiro ikeda
>Priority: Trivial
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When check if rebalance should be started, there is a assertion to check the
> context of the local and rebalance topology version.
> The assertion message contains a typo("hisroty").
> {code:java}
> "Empty hisroty allowed only for newly started cache group [rebTopVer=" +
> rebTopVer +
> ", localStartTopVer=" + grp.localStartVersion() + ']';
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-12642) Fix a typo in the log message about the topology version context when check if rebalance should be started
[
https://issues.apache.org/jira/browse/IGNITE-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin resolved IGNITE-12642.
-
Resolution: Fixed
> Fix a typo in the log message about the topology version context when check
> if rebalance should be started
> --
>
> Key: IGNITE-12642
> URL: https://issues.apache.org/jira/browse/IGNITE-12642
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: masahiro ikeda
>Priority: Trivial
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When check if rebalance should be started, there is a assertion to check the
> context of the local and rebalance topology version.
> The assertion message contains a typo("hisroty").
> {code:java}
> "Empty hisroty allowed only for newly started cache group [rebTopVer=" +
> rebTopVer +
> ", localStartTopVer=" + grp.localStartVersion() + ']';
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12582) It is needed to set used cache for Spring Data dynamically
[ https://issues.apache.org/jira/browse/IGNITE-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034252#comment-17034252 ] Ivan Pavlukhin commented on IGNITE-12582: - [~schernolyas], according to the development process a ticket can be moved to _patch available_ status as long as a PR is ready from standpoint of an author and there is a TC bot visa. But here I suppose we should rerun test suites where tests were added as a visa added previously does not have new tests executed. > It is needed to set used cache for Spring Data dynamically > -- > > 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 >Priority: Major > Fix For: 2.8.1 > > > 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)
[jira] [Created] (IGNITE-12657) ML examples EvaluatorExample and MultipleMetricsExample looks the same
Stepan Pilschikov created IGNITE-12657: -- Summary: ML examples EvaluatorExample and MultipleMetricsExample looks the same Key: IGNITE-12657 URL: https://issues.apache.org/jira/browse/IGNITE-12657 Project: Ignite Issue Type: Bug Components: examples, ml Affects Versions: 2.8 Reporter: Stepan Pilschikov Examples org.apache.ignite.examples.ml.selection.scoring.EvaluatorExample and org.apache.ignite.examples.ml.selection.scoring.MultipleMetricsExample Looks exactly the same I think MultipleMetricsExample is wrong because description told about using KNNClassificationTrainer but actually used SVMLinearClassificationTrainer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12582) It is needed to set used cache for Spring Data dynamically
[ https://issues.apache.org/jira/browse/IGNITE-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepachev Maksim updated IGNITE-12582: -- Labels: spring-plugin (was: ) > It is needed to set used cache for Spring Data dynamically > -- > > 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 >Priority: Major > Labels: spring-plugin > Fix For: 2.8 > > > 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)
[jira] [Updated] (IGNITE-12582) It is needed to set used cache for Spring Data dynamically
[ https://issues.apache.org/jira/browse/IGNITE-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepachev Maksim updated IGNITE-12582: -- Fix Version/s: 2.8 > It is needed to set used cache for Spring Data dynamically > -- > > 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 >Priority: Major > Fix For: 2.8 > > > 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)
[jira] [Comment Edited] (IGNITE-8617) Node Discovery Using AWS Application ELB
[
https://issues.apache.org/jira/browse/IGNITE-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034212#comment-17034212
]
Emmanouil Gkatziouras edited comment on IGNITE-8617 at 2/11/20 8:13 AM:
Hi all!
Added the commend
{code:java}
Note that this finder can only be used on AWS EC2 instances that belong on a
Load Balancer based auto scaling group.
{code}
was (Author: gkatzioura):
Hi all!
Added the commend
{code:java}
Note that this finder can only be used on AWS EC2 instances that belong on a
Load Balanced auto scaling group.
{code}
> Node Discovery Using AWS Application ELB
>
>
> Key: IGNITE-8617
> URL: https://issues.apache.org/jira/browse/IGNITE-8617
> Project: Ignite
> Issue Type: New Feature
> Components: aws
>Reporter: Uday Kale
>Assignee: Emmanouil Gkatziouras
>Priority: Critical
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Support for Node discovery using AWS Application ELB.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12582) It is needed to set used cache for Spring Data dynamically
[ https://issues.apache.org/jira/browse/IGNITE-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034213#comment-17034213 ] Sergey Chernolyas commented on IGNITE-12582: Hi [~Pavlukhin]! The tests have been appended to corresponding test suits. Can I change status of the issue ? > It is needed to set used cache for Spring Data dynamically > -- > > 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 >Priority: Major > > 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)
[jira] [Comment Edited] (IGNITE-8617) Node Discovery Using AWS Application ELB
[
https://issues.apache.org/jira/browse/IGNITE-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034212#comment-17034212
]
Emmanouil Gkatziouras edited comment on IGNITE-8617 at 2/11/20 8:08 AM:
Hi all!
Added the commend
{code:java}
Note that this finder can only be used on AWS EC2 instances that belong on a
Load Balanced auto scaling group.
{code}
was (Author: gkatzioura):
Hi all!
Added the commend
{code:java}
Note that this finder can only be used on AWS EC2 instances that belong on a
Load Balanced autoscalling group.
{code}
> Node Discovery Using AWS Application ELB
>
>
> Key: IGNITE-8617
> URL: https://issues.apache.org/jira/browse/IGNITE-8617
> Project: Ignite
> Issue Type: New Feature
> Components: aws
>Reporter: Uday Kale
>Assignee: Emmanouil Gkatziouras
>Priority: Critical
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Support for Node discovery using AWS Application ELB.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-8617) Node Discovery Using AWS Application ELB
[
https://issues.apache.org/jira/browse/IGNITE-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034212#comment-17034212
]
Emmanouil Gkatziouras commented on IGNITE-8617:
---
Hi all!
Added the commend
{code:java}
Note that this finder can only be used on AWS EC2 instances that belong on a
Load Balanced autoscalling group.
{code}
> Node Discovery Using AWS Application ELB
>
>
> Key: IGNITE-8617
> URL: https://issues.apache.org/jira/browse/IGNITE-8617
> Project: Ignite
> Issue Type: New Feature
> Components: aws
>Reporter: Uday Kale
>Assignee: Emmanouil Gkatziouras
>Priority: Critical
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Support for Node discovery using AWS Application ELB.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
