[jira] [Comment Edited] (IGNITE-6123) First performance measurement of implemented ml algorithms
[ https://issues.apache.org/jira/browse/IGNITE-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214446#comment-16214446 ] Oleg Ignatenko edited comment on IGNITE-6123 at 10/23/17 6:52 AM: -- Sent detailed description of changes and request for feedback to dev list: http://apache-ignite-developers.2346864.n4.nabble.com/yardstick-module-adding-ML-benchmarks-PR-2780-IGNITE-6123-td23511.html [~oleg-ostanin], [~avinogradov] - could you please take a look? Pull request: https://github.com/apache/ignite/pull/2780 and branch is [ignite-6123|https://github.com/gridgain/apache-ignite/tree/ignite-6123] was (Author: oignatenko): Sent detailed description of changes and request for feedback to dev list: http://apache-ignite-developers.2346864.n4.nabble.com/yardstick-module-adding-ML-benchmarks-PR-2780-IGNITE-6123-td23511.html [~oleg-ostanin], [~avinogradov] - could you please take a look? Pull request: https://github.com/apache/ignite/pull/2780 > First performance measurement of implemented ml algorithms > -- > > Key: IGNITE-6123 > URL: https://issues.apache.org/jira/browse/IGNITE-6123 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Assignee: Oleg Ignatenko > Fix For: 2.4 > > > We want to start tracking our performance to avoid performance degradation. > Also we need some performance comparison with other ml libs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-6671) [Web Console] Wrong java type used in generated config from DB schema
[
https://issues.apache.org/jira/browse/IGNITE-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-6671:
-
Assignee: Vasiliy Sisko (was: Alexey Kuznetsov)
> [Web Console] Wrong java type used in generated config from DB schema
> -
>
> Key: IGNITE-6671
> URL: https://issues.apache.org/jira/browse/IGNITE-6671
> Project: Ignite
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
>Affects Versions: 2.2
>Reporter: Dmitry Karachentsev
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>
> We should be confident that java types in generated config are able to fit in
> values from DB. For example, WC generates short for Oracle's NUMBER(5), when
> short could be max 32767, but NUMBER(5) - 9.
> That may produce errors like below during DB import:
> {noformat}
> Exception in thread "main" javax.cache.integration.CacheLoaderException:
> Failed to load cache: test
>at
> org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.loadCache(CacheAbstractJdbcStore.java:798)
>at
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadCache(GridCacheStoreManagerAdapter.java:502)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.localLoadCache(GridDhtCacheAdapter.java:486)
>at
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.localLoadCache(GridCacheProxyImpl.java:217)
>at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheJob.localExecute(GridCacheAdapter.java:5439)
>at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheJobV2.localExecute(GridCacheAdapter.java:5488)
>at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$TopologyVersionAwareJob.execute(GridCacheAdapter.java:6103)
>at
> org.apache.ignite.compute.ComputeJobAdapter.call(ComputeJobAdapter.java:132)
>at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1842)
>at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
>at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6621)
>at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
>at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
>at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1114)
>at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1907)
>at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1257)
>at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:885)
>at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:114)
>at
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:802)
>at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.cache.CacheException: Failed to read binary object:
> org.apache.TestModel
>at
> org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStore.buildBinaryObject(CacheJdbcPojoStore.java:255)
>at
> org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStore.buildObject(CacheJdbcPojoStore.java:136)
>at
> org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore$1.call(CacheAbstractJdbcStore.java:463)
>at
> org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore$1.call(CacheAbstractJdbcStore.java:430)
>at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>... 3 more
> Caused by: java.sql.SQLException: Numeric Overflow
>at
> oracle.jdbc.driver.NumberCommonAccessor.throwOverflow(NumberCommonAccessor.java:4170)
>at
> oracle.jdbc.driver.NumberCommonAccessor.getShort(NumberCommonAccessor.java:311)
>at
> oracle.jdbc.driver.GeneratedStatement.getShort(GeneratedStatement.java:305)
>at
> oracle.jdbc.driver.GeneratedScrollableResultSet.getShort(GeneratedScrollableResultSet.java:879)
>at
> org.apache.ignite.cache.store.jdbc.JdbcTypesDefaultTransformer.getColumnValue(JdbcTypesDefaultTransformer.java:84)
>at
> org.apache.ignite.cac
[jira] [Updated] (IGNITE-5745) Web console: Admin panel - add registration date and ability to filter by it
[ https://issues.apache.org/jira/browse/IGNITE-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-5745: - Fix Version/s: (was: 2.3) 2.4 > Web console: Admin panel - add registration date and ability to filter by it > > > Key: IGNITE-5745 > URL: https://issues.apache.org/jira/browse/IGNITE-5745 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Vasiliy Sisko > Fix For: 2.4 > > > Will be nice to track user registration date in order to see how many users > registered each month. > Also period filtration should be configurable: use last activity date or > registration date to see numbers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6490) Optimize log search speed
[ https://issues.apache.org/jira/browse/IGNITE-6490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-6490: - Fix Version/s: (was: 2.3) 2.4 > Optimize log search speed > - > > Key: IGNITE-6490 > URL: https://issues.apache.org/jira/browse/IGNITE-6490 > Project: Ignite > Issue Type: Improvement > Components: wizards >Affects Versions: 2.1 >Reporter: Alexey Kuznetsov >Assignee: Vasiliy Sisko > Fix For: 2.4 > > > I see in VisorLogSearchJob code like this: `if > (s.toLowerCase().contains(searchStr))` and this is very non effective. This > can be reworked to `regionMatches` and this job should be profiled and may be > some other optimizations can be implemented. > See similar issue on SO: > https://codereview.stackexchange.com/questions/44021/fast-way-of-searching-for-a-string-in-a-text-file -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6123) First performance measurement of implemented ml algorithms
[ https://issues.apache.org/jira/browse/IGNITE-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214446#comment-16214446 ] Oleg Ignatenko commented on IGNITE-6123: Sent detailed description of changes and request for feedback to dev list: http://apache-ignite-developers.2346864.n4.nabble.com/yardstick-module-adding-ML-benchmarks-PR-2780-IGNITE-6123-td23511.html [~oleg-ostanin], [~avinogradov] - could you please take a look? Pull request: https://github.com/apache/ignite/pull/2780 > First performance measurement of implemented ml algorithms > -- > > Key: IGNITE-6123 > URL: https://issues.apache.org/jira/browse/IGNITE-6123 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Assignee: Oleg Ignatenko > Fix For: 2.4 > > > We want to start tracking our performance to avoid performance degradation. > Also we need some performance comparison with other ml libs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5739) JVM crash on node deactivation
[ https://issues.apache.org/jira/browse/IGNITE-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5739: Issue Type: Bug (was: Task) > JVM crash on node deactivation > -- > > Key: IGNITE-5739 > URL: https://issues.apache.org/jira/browse/IGNITE-5739 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Alexey Kuznetsov >Assignee: Alexey Goncharuk > Fix For: 2.3 > > Attachments: hs_err_pid16076.log, ignite-c43368bb.log > > > Start one node (with persistence). > Activate > Deactivate - node crashed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6660) Python Redis example fails for python 3 run
[
https://issues.apache.org/jira/browse/IGNITE-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214234#comment-16214234
]
Oleg Ostanin commented on IGNITE-6660:
--
Added new configuration file for Redis examples.
[~ntikho...@apache.org] please review.
> Python Redis example fails for python 3 run
> ---
>
> Key: IGNITE-6660
> URL: https://issues.apache.org/jira/browse/IGNITE-6660
> Project: Ignite
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: examples
>Affects Versions: 1.8, 1.9, 2.0, 2.1, 2.2
>Reporter: Sergey Kozlov
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> Looks like python redis example fails due to design python 2. But for python
> 3 run raised the following error:
> {noformat}
> File
> "/var/lib/teamcity/data/work/17028f058b6ef75f/i2test/var/suite-examples/gg-pro-fab/examples/redis/redis-example.py",
> line 32
> print 'Value for "k1": %s' % r.get('k1')
> ^
> SyntaxError: invalid syntax
> {noformat}
> The suggested fix is to put brackets for print calls:
> -{{print 'Value for "k1": %s' % r.get('k1')}}-
> {{print('Value for "k1": %s' % r.get('k1'))}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
