[jira] [Created] (IGNITE-7903) Explain how to tune performance by using WAL modes
Denis Magda created IGNITE-7903: --- Summary: Explain how to tune performance by using WAL modes Key: IGNITE-7903 URL: https://issues.apache.org/jira/browse/IGNITE-7903 Project: Ignite Issue Type: New Feature Components: documentation Reporter: Denis Magda Fix For: 2.5 Explain how to improve performance by switching between the WAL modes: https://apacheignite.readme.io/docs/durable-memory-tuning Basically, LOG_ONLY and BACKGROUND mode can be considered as an alternative for FULL_SYNC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6252) Cassandra Cache Store Session does not retry if prepare statement failed
[ https://issues.apache.org/jira/browse/IGNITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Man updated IGNITE-6252: -- Fix Version/s: (was: 2.4) 2.5 > Cassandra Cache Store Session does not retry if prepare statement failed > > > Key: IGNITE-6252 > URL: https://issues.apache.org/jira/browse/IGNITE-6252 > Project: Ignite > Issue Type: Bug > Components: cassandra >Affects Versions: 2.0, 2.1 >Reporter: Sunny Chan >Assignee: Igor Rudyak >Priority: Major > Fix For: 2.5 > > > During our testing, we have found that certain warning about prepared > statement: > 2017-08-31 11:27:19.479 > org.apache.ignite.cache.store.cassandra.CassandraCacheStore > flusher-0-#265%% WARN CassandraCacheStore - Prepared statement cluster > error detected, refreshing Cassandra session > com.datastax.driver.core.exceptions.InvalidQueryException: Tried to execute > unknown prepared query : 0xc7647611fd755386ef63478ee7de577b. You may have > used a PreparedStatement that was created with another Cluster instance. > We notice that after this warning occurs some of the data didn't persist > properly in cassandra cache. After further examining the Ignite's > CassandraSessionImpl code in method > execute(BatchExecutionAssistance,Iterable), we found that at around [line > 283|https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L283], > if the prepare statement fails in the asnyc call, it will not retry the > operation as the error is stored in [line > 269|https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L269] > and cleared in [line > 277|https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L277] > but it was not checked again after going through the [ResultSetFuture > |https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L307]. > I believe in line 307 you should check for error != null such that any > failure will be retry. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6853) Cassandra cache store does not clean prepared statements cache when remove old cassandra session
[ https://issues.apache.org/jira/browse/IGNITE-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Man updated IGNITE-6853: -- Fix Version/s: (was: 2.4) 2.5 > Cassandra cache store does not clean prepared statements cache when remove > old cassandra session > > > Key: IGNITE-6853 > URL: https://issues.apache.org/jira/browse/IGNITE-6853 > Project: Ignite > Issue Type: Bug > Components: cassandra >Affects Versions: 2.3 >Reporter: Mikhail Cherkasov >Assignee: Jason Man >Priority: Major > Labels: important > Fix For: 2.5 > > Attachments: CassandraSessionImplTest.java > > > Cassandra cache store does not clean prepared statements cache when remove > old cassandra session which can lead to: > Prepared > statement cluster error detected, refreshing Cassandra session > com.datastax.driver.core.exceptions.InvalidQueryException: Tried to execute > unknown prepared query : 0xcad5832309a512feeb602eec67408130. You may have > used a PreparedStatement that was created with another Cluster instance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7900) Write Zookeeper Discovery documentation in readme.io
[ https://issues.apache.org/jira/browse/IGNITE-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7900: Component/s: documentation > Write Zookeeper Discovery documentation in readme.io > > > Key: IGNITE-7900 > URL: https://issues.apache.org/jira/browse/IGNITE-7900 > Project: Ignite > Issue Type: Task > Components: documentation, zookeeper >Affects Versions: 2.5 >Reporter: Dmitry Sherstobitov >Priority: Major > Fix For: 2.5 > > > Describe Zookeeper Discovery in readme.io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7902) Enable either swap space or persistence but not both
Prachi Garg created IGNITE-7902: --- Summary: Enable either swap space or persistence but not both Key: IGNITE-7902 URL: https://issues.apache.org/jira/browse/IGNITE-7902 Project: Ignite Issue Type: Task Reporter: Prachi Garg Assignee: Ivan Rakov Fix For: 2.5 Enabling both swap and persistence at the same time for a data region does not make sense. An exception should be thrown in this case. See discussion - http://apache-ignite-developers.2346864.n4.nabble.com/Enabling-swap-space-and-Ignite-Persistence-td27595.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-4773) Web Console: Create New Design Concept
[ https://issues.apache.org/jira/browse/IGNITE-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-4773. -- Resolution: Fixed Multi cluster supported. New UI designed. > Web Console: Create New Design Concept > -- > > Key: IGNITE-4773 > URL: https://issues.apache.org/jira/browse/IGNITE-4773 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > > Don't forget to support multi-clustering. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-4773) Web Console: Create New Design Concept
[ https://issues.apache.org/jira/browse/IGNITE-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-4773. > Web Console: Create New Design Concept > -- > > Key: IGNITE-4773 > URL: https://issues.apache.org/jira/browse/IGNITE-4773 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > > Don't forget to support multi-clustering. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4773) Web Console: Create New Design Concept
[ https://issues.apache.org/jira/browse/IGNITE-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-4773: Assignee: Alexey Kuznetsov (was: Vica Abramova) > Web Console: Create New Design Concept > -- > > Key: IGNITE-4773 > URL: https://issues.apache.org/jira/browse/IGNITE-4773 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > > Don't forget to support multi-clustering. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-4773) Web Console: Create New Design Concept
[ https://issues.apache.org/jira/browse/IGNITE-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-4773: - Fix Version/s: (was: 2.5) > Web Console: Create New Design Concept > -- > > Key: IGNITE-4773 > URL: https://issues.apache.org/jira/browse/IGNITE-4773 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Vica Abramova >Priority: Major > > Don't forget to support multi-clustering. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5916) Web console: incorrect default value for Cache-Queries & Indexing-SQL index max inline size = -1
[ https://issues.apache.org/jira/browse/IGNITE-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-5916: - Fix Version/s: 2.5 > Web console: incorrect default value for Cache-Queries & Indexing-SQL index > max inline size = -1 > > > Key: IGNITE-5916 > URL: https://issues.apache.org/jira/browse/IGNITE-5916 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.5 > > > If I set -1 as real value then field become incorrect (red border) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-5916) Web console: incorrect default value for Cache-Queries & Indexing-SQL index max inline size = -1
[ https://issues.apache.org/jira/browse/IGNITE-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-5916: Resolution: Fixed Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) Merged to master. > Web console: incorrect default value for Cache-Queries & Indexing-SQL index > max inline size = -1 > > > Key: IGNITE-5916 > URL: https://issues.apache.org/jira/browse/IGNITE-5916 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.5 > > > If I set -1 as real value then field become incorrect (red border) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7154) .NET: Thin client: Async queries
[
https://issues.apache.org/jira/browse/IGNITE-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Stronchinskiy reassigned IGNITE-7154:
Assignee: Sergey Stronchinskiy (was: Pavel Tupitsyn)
> .NET: Thin client: Async queries
>
>
> Key: IGNITE-7154
> URL: https://issues.apache.org/jira/browse/IGNITE-7154
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Sergey Stronchinskiy
>Priority: Major
> Labels: .NET
>
> IGNITE-7109 adds async cache operations, but query methods remain
> synchronous.
> We should look for ideas at Entity Framework {{ToListAsync}} and
> {{ToArrayAsync}} .
> 1. Create {{IAsyncQueryCursor}} and {{IAsyncFieldsQueryCursor}} interfaces:
> {code}
> public interface IAsyncQueryCursor : IQueryCursor
> {
> Task> GetAllAsync();
> }
> {code}
> 2. Provide async counterparts for queries: {{Task
> ICacheClient.QueryAsync(...)}}
> This way both initial query and data retrieval can be made asynchronous.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7791) Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
[
https://issues.apache.org/jira/browse/IGNITE-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389804#comment-16389804
]
ASF GitHub Bot commented on IGNITE-7791:
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/3618
IGNITE-7791: add test case for delayed partition exchange
…nect
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-7791
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3618.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3618
commit 73c02562a485ad013d7a80cc358a56f47e7b1432
Author: Maxim Muzafarov
Date: 2018-03-07T17:02:02Z
IGNITE-7791: add test case for delayed partition exchange after reconnect
> Ignite Client Nodes: failed test
> IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
> ---
>
> Key: IGNITE-7791
> URL: https://issues.apache.org/jira/browse/IGNITE-7791
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Test is flaky, success rate: 32.4%, test history is
> [here|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-9174769196124217030&tab=testDetails]
> Reproducible locally.
> Test fails on waiting for disco cache content:
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertTrue(Assert.java:31)
> at junit.framework.TestCase.assertTrue(TestCase.java:201)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.checkCacheDiscoveryData(IgniteClientReconnectCacheTest.java:1414)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated(IgniteClientReconnectCacheTest.java:897)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This fail may be caused by another exception earlier in the log:
> {noformat}
> [2018-02-22
> 14:32:57,972][ERROR][exchange-worker-#3025%internal.IgniteClientReconnectCacheTest3%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=6,
> minorTopVer=1], discoEvt=DiscoveryCustomEvent
> [customMsg=CacheAffinityChangeMessage
> [id=3cea94db161-760b7b18-b776-4ee7-ae5a-64f9494eaa36,
> topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], exchId=null,
> partsMsg=null, exchangeNeeded=true], affTopVer=AffinityTopologyVersion
> [topVer=6, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=1b7f7330-69d8-4bd0-b2e9-71773610, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1519299177395, loc=false, ver=2.5.0#19700101-sha1:,
> isClient=false], topVer=6, nodeId8=658aeb36, msg=null,
> type=DISCOVERY_CUSTOM_EVT, tstamp=1519299177971]], nodeId=1b7f7330,
> evt=DISCOVERY_CUSTOM_EVT]
> java.lang.AssertionError: 236160867
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$CachesInfo.group(CacheAffinitySharedManager.java:2636)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:989)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:983)
> at
> org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllCacheGroups(CacheAffinitySharedManager.java:1118)
> at
[jira] [Commented] (IGNITE-7791) Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
[
https://issues.apache.org/jira/browse/IGNITE-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389791#comment-16389791
]
ASF GitHub Bot commented on IGNITE-7791:
Github user Mmuzaf closed the pull request at:
https://github.com/apache/ignite/pull/3598
> Ignite Client Nodes: failed test
> IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
> ---
>
> Key: IGNITE-7791
> URL: https://issues.apache.org/jira/browse/IGNITE-7791
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Test is flaky, success rate: 32.4%, test history is
> [here|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-9174769196124217030&tab=testDetails]
> Reproducible locally.
> Test fails on waiting for disco cache content:
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertTrue(Assert.java:31)
> at junit.framework.TestCase.assertTrue(TestCase.java:201)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.checkCacheDiscoveryData(IgniteClientReconnectCacheTest.java:1414)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated(IgniteClientReconnectCacheTest.java:897)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This fail may be caused by another exception earlier in the log:
> {noformat}
> [2018-02-22
> 14:32:57,972][ERROR][exchange-worker-#3025%internal.IgniteClientReconnectCacheTest3%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=6,
> minorTopVer=1], discoEvt=DiscoveryCustomEvent
> [customMsg=CacheAffinityChangeMessage
> [id=3cea94db161-760b7b18-b776-4ee7-ae5a-64f9494eaa36,
> topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], exchId=null,
> partsMsg=null, exchangeNeeded=true], affTopVer=AffinityTopologyVersion
> [topVer=6, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=1b7f7330-69d8-4bd0-b2e9-71773610, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1519299177395, loc=false, ver=2.5.0#19700101-sha1:,
> isClient=false], topVer=6, nodeId8=658aeb36, msg=null,
> type=DISCOVERY_CUSTOM_EVT, tstamp=1519299177971]], nodeId=1b7f7330,
> evt=DISCOVERY_CUSTOM_EVT]
> java.lang.AssertionError: 236160867
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$CachesInfo.group(CacheAffinitySharedManager.java:2636)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:989)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:983)
> at
> org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllCacheGroups(CacheAffinitySharedManager.java:1118)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onChangeAffinityMessage(CacheAffinitySharedManager.java:983)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAffinityChangeRequest(GridDhtPartitionsExchangeFuture.java:992)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:648)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
> at
> org.apache.ign
[jira] [Commented] (IGNITE-7791) Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
[
https://issues.apache.org/jira/browse/IGNITE-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389788#comment-16389788
]
ASF GitHub Bot commented on IGNITE-7791:
Github user Mmuzaf closed the pull request at:
https://github.com/apache/ignite/pull/3598
> Ignite Client Nodes: failed test
> IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
> ---
>
> Key: IGNITE-7791
> URL: https://issues.apache.org/jira/browse/IGNITE-7791
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Test is flaky, success rate: 32.4%, test history is
> [here|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-9174769196124217030&tab=testDetails]
> Reproducible locally.
> Test fails on waiting for disco cache content:
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertTrue(Assert.java:31)
> at junit.framework.TestCase.assertTrue(TestCase.java:201)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.checkCacheDiscoveryData(IgniteClientReconnectCacheTest.java:1414)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated(IgniteClientReconnectCacheTest.java:897)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This fail may be caused by another exception earlier in the log:
> {noformat}
> [2018-02-22
> 14:32:57,972][ERROR][exchange-worker-#3025%internal.IgniteClientReconnectCacheTest3%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=6,
> minorTopVer=1], discoEvt=DiscoveryCustomEvent
> [customMsg=CacheAffinityChangeMessage
> [id=3cea94db161-760b7b18-b776-4ee7-ae5a-64f9494eaa36,
> topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], exchId=null,
> partsMsg=null, exchangeNeeded=true], affTopVer=AffinityTopologyVersion
> [topVer=6, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=1b7f7330-69d8-4bd0-b2e9-71773610, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1519299177395, loc=false, ver=2.5.0#19700101-sha1:,
> isClient=false], topVer=6, nodeId8=658aeb36, msg=null,
> type=DISCOVERY_CUSTOM_EVT, tstamp=1519299177971]], nodeId=1b7f7330,
> evt=DISCOVERY_CUSTOM_EVT]
> java.lang.AssertionError: 236160867
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$CachesInfo.group(CacheAffinitySharedManager.java:2636)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:989)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:983)
> at
> org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllCacheGroups(CacheAffinitySharedManager.java:1118)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onChangeAffinityMessage(CacheAffinitySharedManager.java:983)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAffinityChangeRequest(GridDhtPartitionsExchangeFuture.java:992)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:648)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
> at
> org.apache.ign
[jira] [Commented] (IGNITE-7791) Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
[
https://issues.apache.org/jira/browse/IGNITE-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389789#comment-16389789
]
ASF GitHub Bot commented on IGNITE-7791:
GitHub user Mmuzaf reopened a pull request:
https://github.com/apache/ignite/pull/3598
IGNITE-7791: add additional logging
Logging for reproducing bug
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-7791
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3598.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3598
commit 9e06b5f6c253af65373164d462efba4ef509a925
Author: Maxim Muzafarov
Date: 2018-03-04T14:57:55Z
IGNITE-7791: add additional logging
commit c05110468124dbc21fe2ef148b4dc800be719dad
Author: Maxim Muzafarov
Date: 2018-03-04T17:07:32Z
IGNITE-7791: add additional logging details for cache groups
commit 13e7d8a82e32e5c6a6437ad4816331ada30b4f95
Author: Maxim Muzafarov
Date: 2018-03-05T16:51:55Z
IGNITE-7791: more logging
commit cc149ec8223dd501f7dbaf8011f2575864544971
Author: Maxim Muzafarov
Date: 2018-03-06T10:56:48Z
IGNITE-7791: more logging 2
commit aed7ea90d029fd15f3d8b6474652e4250ca67de4
Author: Maxim Muzafarov
Date: 2018-03-06T11:38:55Z
IGNITE-7791: more logging 3
commit 2b8a7ab433b9811a0a0df94b42300f19894c7332
Author: Maxim Muzafarov
Date: 2018-03-06T15:16:14Z
IGNITE-7791: more logging 4
commit f75bcb954b22f81f1e341926b2fe86c20a08cf21
Author: Maxim Muzafarov
Date: 2018-03-06T17:13:06Z
IGNITE-7791: more logging 5
commit 8691f5a67dd4c4b8d279661296241f1a77b28059
Author: Maxim Muzafarov
Date: 2018-03-06T18:45:28Z
IGNITE-7791: more logging 6
> Ignite Client Nodes: failed test
> IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
> ---
>
> Key: IGNITE-7791
> URL: https://issues.apache.org/jira/browse/IGNITE-7791
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Test is flaky, success rate: 32.4%, test history is
> [here|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-9174769196124217030&tab=testDetails]
> Reproducible locally.
> Test fails on waiting for disco cache content:
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertTrue(Assert.java:31)
> at junit.framework.TestCase.assertTrue(TestCase.java:201)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.checkCacheDiscoveryData(IgniteClientReconnectCacheTest.java:1414)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated(IgniteClientReconnectCacheTest.java:897)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This fail may be caused by another exception earlier in the log:
> {noformat}
> [2018-02-22
> 14:32:57,972][ERROR][exchange-worker-#3025%internal.IgniteClientReconnectCacheTest3%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=6,
> minorTopVer=1], discoEvt=DiscoveryCustomEvent
> [customMsg=CacheAffinityChangeMessage
> [id=3cea94db161-760b7b18-b776-4ee7-ae5a-64f9494eaa36,
> topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], exchId=null,
> partsMsg=null, exchangeNeeded=true], affTopVer=AffinityTopologyVersion
> [topVer=6, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=1b7f7330-69d8-4bd0-b2e9-71773610, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47500], discPort=47500, ord
[jira] [Commented] (IGNITE-7319) Memory leak during creating/destroying local cache
[
https://issues.apache.org/jira/browse/IGNITE-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389681#comment-16389681
]
Zbyszek B commented on IGNITE-7319:
---
{noformat}
C:\Dev>"C:\Program Files\Java\jdk1.8.0_111\bin\java" -Xmx3G
"-javaagent:C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
2017.2.5\lib\idea_rt.jar=4917
1:C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2017.2.5\bin"
-Dfile.encoding=UTF-8 -classpath "C:\Program
Files\Java\jdk1.8.0_111\jre\lib\charsets
.jar;C:\Program Files\Java\jdk1.8.0_111\jre\lib\deploy.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\ext\access-bridge-64.jar;C:\Program
Files\Java\jdk1.8.0_11
1\jre\lib\ext\cldrdata.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\ext\dnsns.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\ext\jaccess.jar;C:\Program Files\
Java\jdk1.8.0_111\jre\lib\ext\jfxrt.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\ext\localedata.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\ext\nashorn.jar
;C:\Program Files\Java\jdk1.8.0_111\jre\lib\ext\sunec.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\ext\sunjce_provider.jar;C:\Program
Files\Java\jdk1.8.0_111\
jre\lib\ext\sunmscapi.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\ext\sunpkcs11.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\ext\zipfs.jar;C:\Program Files
\Java\jdk1.8.0_111\jre\lib\javaws.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\jce.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\jfr.jar;C:\Program Files\Jav
a\jdk1.8.0_111\jre\lib\jfxswt.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\jsse.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\management-agent.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\plugin.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\resources.jar;C:\Program
Files\Java\jdk1.8.0_111\jre\lib\rt.jar;C:\Dev\Ig
niteMemLeak2\out\production\IgniteDemo;C:\Dev\IgniteMemLeak2\lib\2.3\cache-api-1.0.0.jar;C:\Dev\IgniteMemLeak2\lib\2.3\commons-codec-1.6.jar;C:\Dev\IgniteMemLea
k2\lib\2.3\h2-1.4.195.jar;C:\Dev\IgniteMemLeak2\lib\2.3\ignite-core-2.3.0.jar;C:\Dev\IgniteMemLeak2\lib\2.3\ignite-indexing-2.3.0.jar;C:\Dev\IgniteMemLeak2\lib\
2.3\lucene-analyzers-common-5.5.2.jar;C:\Dev\IgniteMemLeak2\lib\2.3\lucene-core-5.5.2.jar;C:\Dev\IgniteMemLeak2\lib\2.3\lucene-queryparser-5.5.2.jar"
p1.Demo
>>> Starting Ignite on MyLeakingNode; work directory C:\Users\testuser\ignite
>>> ...
Mar 06, 2018 6:12:16 PM java.util.logging.LogManager$RootLogger log
SEVERE: Failed to resolve default logging config file:
config/java.util.logging.properties
[18:12:16] __
[18:12:16] / _/ ___/ |/ / _/_ __/ __/
[18:12:16] _/ // (7 7 // / / / / _/
[18:12:16] /___/\___/_/|_/___/ /_/ /___/
[18:12:16]
[18:12:16] ver. 2.3.0#20171028-sha1:8add7fd5
[18:12:16] 2017 Copyright(C) Apache Software Foundation
[18:12:16]
[18:12:16] Ignite documentation: http://ignite.apache.org
[18:12:16]
[18:12:16] Quiet mode.
[18:12:16] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
"-v" to ignite.{sh|bat}
[18:12:16]
[18:12:16] OS: Windows 7 6.1 amd64
[18:12:16] VM information: Java(TM) SE Runtime Environment 1.8.0_111-b14 Oracle
Corporation Java HotSpot(TM) 64-Bit Server VM 25.111-b14
[18:12:16] Initial heap size is 256MB (should be no less than 512MB, use
-Xms512m -Xmx512m).
[18:12:16] Configured plugins:
[18:12:16] ^-- None
[18:12:16]
[18:12:16] 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 qu
eues growth on sender and receiver sides.
[18:12:16] Security status [authentication=off, tls/ssl=off]
[18:12:18] Performance suggestions for grid (fix if possible)
[18:12:18] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[18:12:18] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM options)
[18:12:18] ^-- Set max direct memory size if getting 'OOME: Direct buffer
memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
[18:12:18] ^-- Disable processing of calls to System.gc() (add
'-XX:+DisableExplicitGC' to JVM options)
[18:12:18] Refer to this page for more performance suggestions:
https://apacheignite.readme.io/docs/jvm-and-system-tuning
[18:12:18]
[18:12:18] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[18:12:18]
[18:12:18] Ignite node started OK (id=8219875e)
[18:12:18] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8, heap=2.7GB]
>>> Ignite started on MyLeakingNode (8219875e-97d5-4e0e-852a-15eb83759b7d)
>>> successfully!
s
Queue size: 1
Caches created: 387307
Caches destroyed: 387303
Mar 07, 2018 4:20:56 AM org.apache.ignite.logger.java.JavaLogger error
SEVERE: Error when executing timeout callback: CancelableTask
[id=c4ad4810261-a07dab65-3c81-4349-af11-68b9d200e3b3, endTime=1520392859178,
period=5000, cancel=f
alse,
task=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryManager$BackupCleane
[jira] [Comment Edited] (IGNITE-7319) Memory leak during creating/destroying local cache
[
https://issues.apache.org/jira/browse/IGNITE-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389676#comment-16389676
]
Zbyszek B edited comment on IGNITE-7319 at 3/7/18 3:17 PM:
---
on 3 GHz machine with 4 cores one gets OOM after 10 hours. The max heap is set
to 3G:
was (Author: zbyszek):
on 3 GHz machine with 4 cores one gets OOM after 10 hours:
> Memory leak during creating/destroying local cache
> --
>
> Key: IGNITE-7319
> URL: https://issues.apache.org/jira/browse/IGNITE-7319
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> The following code creates local caches:
> {code}
> private IgniteCache createLocalCache(String name) {
> CacheConfiguration cCfg = new
> CacheConfiguration<>();
> cCfg.setName(name);
> cCfg.setGroupName("localCaches"); // without group leak is much
> bigger!
> cCfg.setStoreKeepBinary(true);
> cCfg.setCacheMode(CacheMode.LOCAL);
> cCfg.setOnheapCacheEnabled(false);
> cCfg.setCopyOnRead(false);
> cCfg.setBackups(0);
> cCfg.setWriteBehindEnabled(false);
> cCfg.setReadThrough(false);
> cCfg.setReadFromBackup(false);
> cCfg.setQueryEntities();
> return ignite.createCache(cCfg).withKeepBinary();
> }
> {code}
> The caches are placed in the queue and are picked up by the worker thread
> which just destroys them after removing from the queue.
> This setup seems to generate a memory leak of about 1GB per day.
> When looking at heap dump, I see all space is occupied by instances of
> java.util.concurrent.ConcurrentSkipListMap$Node.
> User list:
> http://apache-ignite-users.70518.x6.nabble.com/Memory-leak-in-GridCachePartitionExchangeManager-tt18995.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7319) Memory leak during creating/destroying local cache
[
https://issues.apache.org/jira/browse/IGNITE-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389676#comment-16389676
]
Zbyszek B commented on IGNITE-7319:
---
on 3 GHz machine with 4 cores one gets OOM after 10 hours:
> Memory leak during creating/destroying local cache
> --
>
> Key: IGNITE-7319
> URL: https://issues.apache.org/jira/browse/IGNITE-7319
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> The following code creates local caches:
> {code}
> private IgniteCache createLocalCache(String name) {
> CacheConfiguration cCfg = new
> CacheConfiguration<>();
> cCfg.setName(name);
> cCfg.setGroupName("localCaches"); // without group leak is much
> bigger!
> cCfg.setStoreKeepBinary(true);
> cCfg.setCacheMode(CacheMode.LOCAL);
> cCfg.setOnheapCacheEnabled(false);
> cCfg.setCopyOnRead(false);
> cCfg.setBackups(0);
> cCfg.setWriteBehindEnabled(false);
> cCfg.setReadThrough(false);
> cCfg.setReadFromBackup(false);
> cCfg.setQueryEntities();
> return ignite.createCache(cCfg).withKeepBinary();
> }
> {code}
> The caches are placed in the queue and are picked up by the worker thread
> which just destroys them after removing from the queue.
> This setup seems to generate a memory leak of about 1GB per day.
> When looking at heap dump, I see all space is occupied by instances of
> java.util.concurrent.ConcurrentSkipListMap$Node.
> User list:
> http://apache-ignite-users.70518.x6.nabble.com/Memory-leak-in-GridCachePartitionExchangeManager-tt18995.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7421) Thin client Java API - data grid API
[
https://issues.apache.org/jira/browse/IGNITE-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389669#comment-16389669
]
Vladimir Ozerov commented on IGNITE-7421:
-
[~kukushal], my comments:
1) By convention we always set {{serialVersionUID}} to {{0L}}.
2) I do not recommend to use {{Objects.hash(...)}} method because it is vararg
and creates byte array underneath every time. It is better to calculate hash
code by hand using standard {{31 * x + y}} algorithm. We should discourage
ourselves from using helpers with hidden effects for simple code parts.
3) {{SslProtocol and SslMode}} - as these things are specific to thin client,
let's move them to thin client package.
4) {{SslProtocol}} - if we have only TLS mode (i.e. SSL is considered totally
deprecated), why would we need this enum at all? Let's remove it along with
relevant properties altogether for the sake of simplicity.
5) {{ClientCacheConfiguration}} is not top-level thing, and hence should be
located inside {{client}} package, not inside
{{org.apache.ignite.configuration}}
6) {{ClientCacheConfiguration}} - collection-based getter/setters should be
symmetircal. I.e. they either accept array (vararg) and return array, or accept
collection and return collection. Arrays is considered better practice at the
moment.
7) {{IgniteClientConfiguration.addrs}} - we should not resolve addresses here,
neither we should expose resolved address with public methods. Instead,
resolution should happen in runtime when connection attempt is performed.
Otherwise your code is not responsive to runtime changes to network
configuration.
8) Taking in count p.7, {{TcpAddressConfigLines}} appears to me a dangerous
abstraction. I would rather convert it to a static stateless method inside
{{IgniteUtils}} which is called in runtime in during connection attempt.
9) {{TcpDiscoveryVmIpFinder}} - I would recommend to revert the changes. It is
considered bad practice to change classes which is unrelated to the ticket. If
refactoring is needed, it should be performed in separate ticket. This approach
minimizes impact of certain changes and simplified review and testing. In this
particular case - {{TcpDiscoveryVmIpFinder}} is central class, very sensitive
to any changes. Any change introduced here may affect the whole project.
Definitely not the right move provided that current ticket is focused on thin
client and should not affect core logic in general.
10) Let's rename {{org.apache.ignite.thinclient}} package to
{{org.apache.ignite.client}}. Word {{thin}} doesn't add much value, because our
non-thin client is already considered deprecated and will be removed soon.
11) {{IgniteUnavailableException}} - I would rename it to
{{ClientConnectionException}}
12) {{IgniteConfigurationException}} - not clear why we need it, provided p.7,
p.8 and p.10. Appears to be a wrong abstraction to me.
13) {{IgniteBinaryMarshaller}} - there should be no static. In principle user
may have different clients connected to different grids. In general, any static
state is discouraged in Ignite. Instead, it is better to have a singleton
marshaller *per-client*.
> Thin client Java API - data grid API
>
>
> Key: IGNITE-7421
> URL: https://issues.apache.org/jira/browse/IGNITE-7421
> Project: Ignite
> Issue Type: New Feature
> Components: thin client
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
>Priority: Major
> Labels: data, java, thin
>
> Implement below Java bindings for the thin client protocol. The client
> configuration must support failover and encryption.
> Cache
> JCache (limited)
> getName(): String
> put(key, val)
> get(key): V
> getAll(keys: Set): Map
> containsKey(key): boolean
> getAndPut(key, val): V
> getAndReplace(key, val): V
> getAndRemove(key): V
> putIfAbsent
> replace(key, val)
> replace(key, oldVal, newVal)
> putAll
> clear
> remove(key)
> remove(key, val)
> removeAll()
> removeAll(keys: Set)
> getConfiguration(clazz): Configuration
> close()
> size(modes: CachePeekMode...)
> query(qry: Query): QueryCursor
> query(qry: SqlFieldsQuery): FieldsQueryCursor
> withKeepBinary(): IgniteCache
> Ignite
> cache(name: String)
> cacheNames(): Collection
> binary(): IgniteBinary
> createCache(name): Cache
> getOrCreateCache(name): Cache
> destroyCache(name)
> Ignition
> startClient(:ClientConfiguration): Ignite
> ClientConfiguration(port, host, binaryConfiguration, sslConfiguration,
> etc...)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7319) Memory leak during creating/destroying local cache
[
https://issues.apache.org/jira/browse/IGNITE-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389663#comment-16389663
]
Zbyszek B commented on IGNITE-7319:
---
{code:java}
// code placeholder
package p1;
import org.apache.ignite.*;
import org.apache.ignite.binary.BinaryObject;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.QueryEntity;
import org.apache.ignite.cluster.ClusterNode;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import java.io.BufferedReader;
import java.io.File;
import java.io.InputStreamReader;
import java.util.Collections;
import java.util.concurrent.*;
import java.util.concurrent.atomic.AtomicLong;
public class Demo {
private final static Ignite ignite = createIgnite();
private final static AtomicLong localCacheCreateCount = new AtomicLong();
private final static AtomicLong localCacheDestroyCount = new AtomicLong();
private final static BlockingQueue> queue =
new LinkedBlockingQueue<>(100);
public static void main(String[] args) throws Exception {
CompletableFuture.runAsync(Demo::runProducer);
CompletableFuture.runAsync(Demo::runProducer);
CompletableFuture.runAsync(Demo::runConsumer);
CompletableFuture.runAsync(Demo::runConsumer);
BufferedReader br = new BufferedReader(new InputStreamReader(System.in));
do {
String input = br.readLine();
if ("q".equals(input)) {
System.out.println("Exit!");
System.exit(0);
} else {
System.out.println("Queue size: " + queue.size());
System.out.println("Caches created: " + localCacheCreateCount.longValue());
System.out.println("Caches destroyed: " + localCacheDestroyCount.longValue());
}
} while (true);
}
private static void runProducer() {
do {
try {
IgniteCache cache = createLocalCache();
queue.put(cache);
} catch (Exception e) {
throw new RuntimeException(e);
}
} while (true);
}
private static void runConsumer() {
do {
try {
IgniteCache cache = queue.take();
cache.close();
cache.destroy();
localCacheDestroyCount.incrementAndGet();
} catch (Exception e) {
throw new RuntimeException(e);
}
} while (true);
}
private static Ignite createIgnite() {
IgniteConfiguration iCfg = new IgniteConfiguration();
String workDirectory = System.getProperty("user.home") + File.separator +
"ignite";
iCfg.setWorkDirectory(workDirectory);
System.out.println();
System.out.println(String.format(">>> Starting Ignite on %s; work directory %s
...", "MyLeakingNode", workDirectory));
System.out.println();
final Ignite ignite = Ignition.start(iCfg);
ClusterNode localNode = ignite.cluster().localNode();
System.out.println();
System.out.println(String.format(">>> Ignite started on %s (%s) successfully!",
"MyLeakingNode", localNode.id()));
System.out.println();
return ignite;
}
private static IgniteCache createLocalCache() {
final String cacheName = "localCache" + localCacheCreateCount.incrementAndGet();
final CacheConfiguration cCfg = new
CacheConfiguration<>();
cCfg.setName(cacheName);
cCfg.setStoreKeepBinary(true);
cCfg.setCacheMode(CacheMode.LOCAL);
cCfg.setOnheapCacheEnabled(false);
cCfg.setCopyOnRead(false);
cCfg.setBackups(0);
cCfg.setWriteBehindEnabled(false);
cCfg.setReadThrough(false);
cCfg.setReadFromBackup(false);
cCfg.setQueryEntities(Collections.singletonList( new
QueryEntity(String.class.getTypeName(), "LocalEntity")));
ignite.destroyCache(cacheName); // local cache is not really local - reference
can be kept by other nodes if restart during the load happens
return ignite.createCache(cCfg).withKeepBinary();
}
}
{code}
> Memory leak during creating/destroying local cache
> --
>
> Key: IGNITE-7319
> URL: https://issues.apache.org/jira/browse/IGNITE-7319
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> The following code creates local caches:
> {code}
> private IgniteCache createLocalCache(String name) {
> CacheConfiguration cCfg = new
> CacheConfiguration<>();
> cCfg.setName(name);
> cCfg.setGroupName("localCaches"); // without group leak is much
> bigger!
> cCfg.setStoreKeepBinary(true);
> cCfg.setCacheMode(CacheMode.LOCAL);
> cCfg.setOnheapCacheEnabled(false);
> cCfg.setCopyOnRead(false);
> cCfg.setBackups(0);
> cCfg.setWriteBehindEnabled(false);
> cCfg.setReadThrough(false);
> cCfg.setReadFromBackup(false);
> cCfg.setQueryEntities();
> return ignite.createCache(cCfg).withKeepBinary();
> }
> {code}
> The caches are placed in the queue and are picked up by the worker thread
> which just destroys them after removing from the queue.
> This setup seems to gener
[jira] [Issue Comment Deleted] (IGNITE-7319) Memory leak during creating/destroying local cache
[
https://issues.apache.org/jira/browse/IGNITE-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zbyszek B updated IGNITE-7319:
--
Comment: was deleted
(was: {code:java}
// code placeholder
{code}
package pack1; import org.apache.ignite.*; import
org.apache.ignite.binary.BinaryObject; import
org.apache.ignite.cache.CacheMode; import org.apache.ignite.cache.QueryEntity;
import org.apache.ignite.cluster.ClusterNode; import
org.apache.ignite.configuration.CacheConfiguration; import
org.apache.ignite.configuration.IgniteConfiguration; import
java.io.BufferedReader; import java.io.File; import java.io.InputStreamReader;
import java.util.Collections; import java.util.concurrent.*; import
java.util.concurrent.atomic.AtomicLong; public class Demo \{ private final
static Ignite ignite = createIgnite(); private final static AtomicLong
localCacheCreateCount = new AtomicLong(); private final static AtomicLong
localCacheDestroyCount = new AtomicLong(); private final static
BlockingQueue> queue = new
LinkedBlockingQueue<>(100); public static void main(String[] args) throws
Exception { CompletableFuture.runAsync(Demo::runProducer);
CompletableFuture.runAsync(Demo::runProducer);
CompletableFuture.runAsync(Demo::runConsumer);
CompletableFuture.runAsync(Demo::runConsumer); BufferedReader br = new
BufferedReader(new InputStreamReader(System.in)); do { String input =
br.readLine(); if ("q".equals(input)) { System.out.println("Exit!");
System.exit(0); } else \{ System.out.println("Queue size: " + queue.size());
System.out.println("Caches created: " + localCacheCreateCount.longValue());
System.out.println("Caches destroyed: " + localCacheDestroyCount.longValue());
} } while (true); } private static void runProducer() \{ do { try {
IgniteCache cache = createLocalCache(); queue.put(cache);
} catch (Exception e) \{ throw new RuntimeException(e); } } while (true); }
private static void runConsumer() \{ do { try { IgniteCache cache = queue.take(); cache.close(); cache.destroy();
localCacheDestroyCount.incrementAndGet(); } catch (Exception e) \{ throw new
RuntimeException(e); } } while (true); } private static Ignite createIgnite()
\{ IgniteConfiguration iCfg = new IgniteConfiguration(); String workDirectory =
System.getProperty("user.home") + File.separator + "ignite";
iCfg.setWorkDirectory(workDirectory); System.out.println();
System.out.println(String.format(">>> Starting Ignite on %s; work directory %s
...", "MyLeakingNode", workDirectory)); System.out.println(); final Ignite
ignite = Ignition.start(iCfg); ClusterNode localNode =
ignite.cluster().localNode(); System.out.println();
System.out.println(String.format(">>> Ignite started on %s (%s) successfully!",
"MyLeakingNode", localNode.id())); System.out.println(); return ignite; }
private static IgniteCache createLocalCache() \{ final
String cacheName = "localCache" + localCacheCreateCount.incrementAndGet();
final CacheConfiguration cCfg = new
CacheConfiguration<>(); cCfg.setName(cacheName); cCfg.setStoreKeepBinary(true);
cCfg.setCacheMode(CacheMode.LOCAL); cCfg.setOnheapCacheEnabled(false);
cCfg.setCopyOnRead(false); cCfg.setBackups(0);
cCfg.setWriteBehindEnabled(false); cCfg.setReadThrough(false);
cCfg.setReadFromBackup(false); cCfg.setQueryEntities(Collections.singletonList(
new QueryEntity(String.class.getTypeName(), "LocalEntity")));
ignite.destroyCache(cacheName); // local cache is not really local - reference
can be kept by other nodes if restart during the load happens return
ignite.createCache(cCfg).withKeepBinary(); } })
> Memory leak during creating/destroying local cache
> --
>
> Key: IGNITE-7319
> URL: https://issues.apache.org/jira/browse/IGNITE-7319
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> The following code creates local caches:
> {code}
> private IgniteCache createLocalCache(String name) {
> CacheConfiguration cCfg = new
> CacheConfiguration<>();
> cCfg.setName(name);
> cCfg.setGroupName("localCaches"); // without group leak is much
> bigger!
> cCfg.setStoreKeepBinary(true);
> cCfg.setCacheMode(CacheMode.LOCAL);
> cCfg.setOnheapCacheEnabled(false);
> cCfg.setCopyOnRead(false);
> cCfg.setBackups(0);
> cCfg.setWriteBehindEnabled(false);
> cCfg.setReadThrough(false);
> cCfg.setReadFromBackup(false);
> cCfg.setQueryEntities();
> return ignite.createCache(cCfg).withKeepBinary();
> }
> {code}
> The caches are placed in the queue and are picked up by the worker thread
> which just destroys them after removing from the queue.
> This setup seem
[jira] [Commented] (IGNITE-7319) Memory leak during creating/destroying local cache
[
https://issues.apache.org/jira/browse/IGNITE-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389662#comment-16389662
]
Zbyszek B commented on IGNITE-7319:
---
{code:java}
// code placeholder
{code}
package pack1; import org.apache.ignite.*; import
org.apache.ignite.binary.BinaryObject; import
org.apache.ignite.cache.CacheMode; import org.apache.ignite.cache.QueryEntity;
import org.apache.ignite.cluster.ClusterNode; import
org.apache.ignite.configuration.CacheConfiguration; import
org.apache.ignite.configuration.IgniteConfiguration; import
java.io.BufferedReader; import java.io.File; import java.io.InputStreamReader;
import java.util.Collections; import java.util.concurrent.*; import
java.util.concurrent.atomic.AtomicLong; public class Demo \{ private final
static Ignite ignite = createIgnite(); private final static AtomicLong
localCacheCreateCount = new AtomicLong(); private final static AtomicLong
localCacheDestroyCount = new AtomicLong(); private final static
BlockingQueue> queue = new
LinkedBlockingQueue<>(100); public static void main(String[] args) throws
Exception { CompletableFuture.runAsync(Demo::runProducer);
CompletableFuture.runAsync(Demo::runProducer);
CompletableFuture.runAsync(Demo::runConsumer);
CompletableFuture.runAsync(Demo::runConsumer); BufferedReader br = new
BufferedReader(new InputStreamReader(System.in)); do { String input =
br.readLine(); if ("q".equals(input)) { System.out.println("Exit!");
System.exit(0); } else \{ System.out.println("Queue size: " + queue.size());
System.out.println("Caches created: " + localCacheCreateCount.longValue());
System.out.println("Caches destroyed: " + localCacheDestroyCount.longValue());
} } while (true); } private static void runProducer() \{ do { try {
IgniteCache cache = createLocalCache(); queue.put(cache);
} catch (Exception e) \{ throw new RuntimeException(e); } } while (true); }
private static void runConsumer() \{ do { try { IgniteCache cache = queue.take(); cache.close(); cache.destroy();
localCacheDestroyCount.incrementAndGet(); } catch (Exception e) \{ throw new
RuntimeException(e); } } while (true); } private static Ignite createIgnite()
\{ IgniteConfiguration iCfg = new IgniteConfiguration(); String workDirectory =
System.getProperty("user.home") + File.separator + "ignite";
iCfg.setWorkDirectory(workDirectory); System.out.println();
System.out.println(String.format(">>> Starting Ignite on %s; work directory %s
...", "MyLeakingNode", workDirectory)); System.out.println(); final Ignite
ignite = Ignition.start(iCfg); ClusterNode localNode =
ignite.cluster().localNode(); System.out.println();
System.out.println(String.format(">>> Ignite started on %s (%s) successfully!",
"MyLeakingNode", localNode.id())); System.out.println(); return ignite; }
private static IgniteCache createLocalCache() \{ final
String cacheName = "localCache" + localCacheCreateCount.incrementAndGet();
final CacheConfiguration cCfg = new
CacheConfiguration<>(); cCfg.setName(cacheName); cCfg.setStoreKeepBinary(true);
cCfg.setCacheMode(CacheMode.LOCAL); cCfg.setOnheapCacheEnabled(false);
cCfg.setCopyOnRead(false); cCfg.setBackups(0);
cCfg.setWriteBehindEnabled(false); cCfg.setReadThrough(false);
cCfg.setReadFromBackup(false); cCfg.setQueryEntities(Collections.singletonList(
new QueryEntity(String.class.getTypeName(), "LocalEntity")));
ignite.destroyCache(cacheName); // local cache is not really local - reference
can be kept by other nodes if restart during the load happens return
ignite.createCache(cCfg).withKeepBinary(); } }
> Memory leak during creating/destroying local cache
> --
>
> Key: IGNITE-7319
> URL: https://issues.apache.org/jira/browse/IGNITE-7319
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> The following code creates local caches:
> {code}
> private IgniteCache createLocalCache(String name) {
> CacheConfiguration cCfg = new
> CacheConfiguration<>();
> cCfg.setName(name);
> cCfg.setGroupName("localCaches"); // without group leak is much
> bigger!
> cCfg.setStoreKeepBinary(true);
> cCfg.setCacheMode(CacheMode.LOCAL);
> cCfg.setOnheapCacheEnabled(false);
> cCfg.setCopyOnRead(false);
> cCfg.setBackups(0);
> cCfg.setWriteBehindEnabled(false);
> cCfg.setReadThrough(false);
> cCfg.setReadFromBackup(false);
> cCfg.setQueryEntities();
> return ignite.createCache(cCfg).withKeepBinary();
> }
> {code}
> The caches are placed in the queue and are picked up by the worker thread
> which just destroys them after removing from the
[jira] [Comment Edited] (IGNITE-7319) Memory leak during creating/destroying local cache
[
https://issues.apache.org/jira/browse/IGNITE-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389660#comment-16389660
]
Zbyszek B edited comment on IGNITE-7319 at 3/7/18 3:01 PM:
---
Here is a code to reproduce:
was (Author: zbyszek):
Gere is a code to reproduce:
> Memory leak during creating/destroying local cache
> --
>
> Key: IGNITE-7319
> URL: https://issues.apache.org/jira/browse/IGNITE-7319
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> The following code creates local caches:
> {code}
> private IgniteCache createLocalCache(String name) {
> CacheConfiguration cCfg = new
> CacheConfiguration<>();
> cCfg.setName(name);
> cCfg.setGroupName("localCaches"); // without group leak is much
> bigger!
> cCfg.setStoreKeepBinary(true);
> cCfg.setCacheMode(CacheMode.LOCAL);
> cCfg.setOnheapCacheEnabled(false);
> cCfg.setCopyOnRead(false);
> cCfg.setBackups(0);
> cCfg.setWriteBehindEnabled(false);
> cCfg.setReadThrough(false);
> cCfg.setReadFromBackup(false);
> cCfg.setQueryEntities();
> return ignite.createCache(cCfg).withKeepBinary();
> }
> {code}
> The caches are placed in the queue and are picked up by the worker thread
> which just destroys them after removing from the queue.
> This setup seems to generate a memory leak of about 1GB per day.
> When looking at heap dump, I see all space is occupied by instances of
> java.util.concurrent.ConcurrentSkipListMap$Node.
> User list:
> http://apache-ignite-users.70518.x6.nabble.com/Memory-leak-in-GridCachePartitionExchangeManager-tt18995.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7319) Memory leak during creating/destroying local cache
[
https://issues.apache.org/jira/browse/IGNITE-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389660#comment-16389660
]
Zbyszek B commented on IGNITE-7319:
---
Gere is a code to reproduce:
> Memory leak during creating/destroying local cache
> --
>
> Key: IGNITE-7319
> URL: https://issues.apache.org/jira/browse/IGNITE-7319
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> The following code creates local caches:
> {code}
> private IgniteCache createLocalCache(String name) {
> CacheConfiguration cCfg = new
> CacheConfiguration<>();
> cCfg.setName(name);
> cCfg.setGroupName("localCaches"); // without group leak is much
> bigger!
> cCfg.setStoreKeepBinary(true);
> cCfg.setCacheMode(CacheMode.LOCAL);
> cCfg.setOnheapCacheEnabled(false);
> cCfg.setCopyOnRead(false);
> cCfg.setBackups(0);
> cCfg.setWriteBehindEnabled(false);
> cCfg.setReadThrough(false);
> cCfg.setReadFromBackup(false);
> cCfg.setQueryEntities();
> return ignite.createCache(cCfg).withKeepBinary();
> }
> {code}
> The caches are placed in the queue and are picked up by the worker thread
> which just destroys them after removing from the queue.
> This setup seems to generate a memory leak of about 1GB per day.
> When looking at heap dump, I see all space is occupied by instances of
> java.util.concurrent.ConcurrentSkipListMap$Node.
> User list:
> http://apache-ignite-users.70518.x6.nabble.com/Memory-leak-in-GridCachePartitionExchangeManager-tt18995.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7708) Ignite Compute has flaky failures
[
https://issues.apache.org/jira/browse/IGNITE-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389639#comment-16389639
]
Dmitriy Pavlov edited comment on IGNITE-7708 at 3/7/18 2:41 PM:
I've moved
org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite
to Basic2 to avoid odd notifications on flaky failures.
(
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgniteBasic2&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
)
was (Author: dpavlov):
I've moved
org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite
to Basic2 to avoid odd notifications on flaky failures.
> Ignite Compute has flaky failures
> --
>
> Key: IGNITE-7708
> URL: https://issues.apache.org/jira/browse/IGNITE-7708
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1093187&buildTypeId=IgniteTests24Java8_IgniteComputeGrid
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1092214&buildTypeId=IgniteTests24Java8_IgniteComputeGrid
> IgniteBinaryObjectsComputeGridTestSuite
> IgniteComputeBasicConfigVariationsFullApiTestSuite
> it is required to fix flaky failure or remove tests from suite because of
> default notifications were enabled recently.
> Flaky failures generates a lot of unecessary spam.
> {noformat}
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCallCollection
> (fail rate 9%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApplyForCollectionAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApplyForCollection
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApply
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCall
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testExecuteTask
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApplyForCollectionWithReducerAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testAffinityCall
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testBroadcastCallableAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testBroadcastCallable
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCallCollectionAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCallCollectionWithReducer
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testExecuteTaskClassAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testBroadcastClosure
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.intern
[jira] [Commented] (IGNITE-7708) Ignite Compute has flaky failures
[
https://issues.apache.org/jira/browse/IGNITE-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389639#comment-16389639
]
Dmitriy Pavlov commented on IGNITE-7708:
I've moved
org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite
to Basic2 to avoid odd notifications on flaky failures.
> Ignite Compute has flaky failures
> --
>
> Key: IGNITE-7708
> URL: https://issues.apache.org/jira/browse/IGNITE-7708
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1093187&buildTypeId=IgniteTests24Java8_IgniteComputeGrid
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1092214&buildTypeId=IgniteTests24Java8_IgniteComputeGrid
> IgniteBinaryObjectsComputeGridTestSuite
> IgniteComputeBasicConfigVariationsFullApiTestSuite
> it is required to fix flaky failure or remove tests from suite because of
> default notifications were enabled recently.
> Flaky failures generates a lot of unecessary spam.
> {noformat}
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCallCollection
> (fail rate 9%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApplyForCollectionAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApplyForCollection
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApply
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCall
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testExecuteTask
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApplyForCollectionWithReducerAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testAffinityCall
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testBroadcastCallableAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testBroadcastCallable
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCallCollectionAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCallCollectionWithReducer
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testExecuteTaskClassAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testBroadcastClosure
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApplyAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCallAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVa
[jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
[
https://issues.apache.org/jira/browse/IGNITE-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389621#comment-16389621
]
Vladimir Ozerov commented on IGNITE-7029:
-
[~tledkov-gridgain], my comments:
1) {{ConnectionPropertiesImpl}} - I think it is not good idea to resolve
address on startup. For example, what if user had no connection when
application was started, but then recovered it? Or what if DNS settings were
changed in runtime, so invalid address became valid? We should not force use to
restart his app in this case. My proposal is to call
{{InetAddress.getAllByName}} at *connection time* and then try to connect to
every returned address iteratively.
2) {{JdbcThinSSLUtil.createSSLSocket}} - consequence of p.1, should be fixed as
well
> Add an ability to provide multiple connection addresses for thin JDBC driver
>
>
> Key: IGNITE-7029
> URL: https://issues.apache.org/jira/browse/IGNITE-7029
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc, sql
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Taras Ledkov
>Priority: Major
>
> Currently we allow only to provide one address when connecting via thin JDBC
> driver. This has to issues:
> * If node driver is connected to goes down, the driver stops working.
> * Driver has to always go though the same node - this is a bottleneck.
> As a simple solution we can allow to provide multiple addresses, like MySQL
> does for example:
> https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-usagenotes-j2ee-concepts-managing-load-balanced-connections.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7756) Streamer fails if IgniteUuid is indexed
[
https://issues.apache.org/jira/browse/IGNITE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389600#comment-16389600
]
Dmitriy Pavlov commented on IGNITE-7756:
Hi [~vozerov],
I've done some additional plugin tests, it seems change is OK.
Could you please review?
> Streamer fails if IgniteUuid is indexed
> ---
>
> Key: IGNITE-7756
> URL: https://issues.apache.org/jira/browse/IGNITE-7756
> Project: Ignite
> Issue Type: Bug
> Components: streaming
>Affects Versions: 2.3
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> IgniteDataStreamer are failed to put data to the cache if IgniteUuid is
> IndexedType.
> Spark tests in IGNITE-7227 are failed because of this issue.
> Reproducer:
> {code:java}
> public void testStreamer() throws Exception {
> Ignite client = grid("client");
> CacheConfiguration ccfg = new CacheConfiguration("UUID_CACHE");
> ccfg.setIndexedTypes(IgniteUuid.class, String.class);
> client.createCache(ccfg);
> try(IgniteDataStreamer cache =
> client.dataStreamer("UUID_CACHE")) {
> for(Integer i=0; i<2; i++)
> cache.addData(IgniteUuid.randomUuid(), i.toString());
> }
> }
> {code}
> Exception stack trace:
> {noformat}
> [23:43:35] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=[true, true]][23:43:35] (err) Failed to
> execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1,
> lsnrCalls=0, done=false, cancelled=false, err=null, futs=[true, true]]class
> org.apache.ignite.IgniteCheckedException: DataStreamer request failed
> [node=57961924-82ec-4d56-81eb-1a4109a0]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1900)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:344)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1089)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:499)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteException: Failed to set initial
> value for cache entry
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2135)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:397)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:302)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:59)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:89)
> ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
> index, incorrect key class [expCls=org.apache.ignite.lang.IgniteUuid,
> actualCls=org.apache.ignite.internal.binary.BinaryObjectImpl]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.typeByValue(GridQueryProcessor.java:1954)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1877)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:403)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1343)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1207)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:345)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3527)
> at
> org.apache.ignite.internal.
[jira] [Commented] (IGNITE-6860) Lack of context information upon serializing and marshalling (writeObject and writeFields)
[
https://issues.apache.org/jira/browse/IGNITE-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389565#comment-16389565
]
ASF GitHub Bot commented on IGNITE-6860:
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/3617
IGNITE-6860 Add logging and additional info while BinaryMarshaller fa…
…ils to serialize object.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ivandasch/ignite ignite-6860
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3617.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3617
commit 81071bec84d2cbb146acfb40d294e93cc44e7ffc
Author: Ivan Daschinskiy
Date: 2018-03-07T13:43:59Z
IGNITE-6860 Add logging and additional info while BinaryMarshaller fails to
serialize object.
> Lack of context information upon serializing and marshalling (writeObject and
> writeFields)
> --
>
> Key: IGNITE-6860
> URL: https://issues.apache.org/jira/browse/IGNITE-6860
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.3
>Reporter: Alexandr Kuramshin
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.5
>
>
> Having the stack trace
> {noformat}
> Caused by: org.apache.ignite.binary.BinaryObjectException: Failed to marshal
> object with optimized marshaller:
> [org.apache.logging.log4j.core.config.AppenderControl@302e61a8]
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:186)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
> at
> org.apache.ignite.interna
[jira] [Commented] (IGNITE-6860) Lack of context information upon serializing and marshalling (writeObject and writeFields)
[
https://issues.apache.org/jira/browse/IGNITE-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389567#comment-16389567
]
Ivan Daschinskiy commented on IGNITE-6860:
--
Please, review my pull-request
https://github.com/apache/ignite/pull/3617
> Lack of context information upon serializing and marshalling (writeObject and
> writeFields)
> --
>
> Key: IGNITE-6860
> URL: https://issues.apache.org/jira/browse/IGNITE-6860
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.3
>Reporter: Alexandr Kuramshin
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.5
>
>
> Having the stack trace
> {noformat}
> Caused by: org.apache.ignite.binary.BinaryObjectException: Failed to marshal
> object with optimized marshaller:
> [org.apache.logging.log4j.core.config.AppenderControl@302e61a8]
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:186)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>
[jira] [Updated] (IGNITE-7901) Refactor Pages Write Throttle: introduce exponential throttle as separate class
[ https://issues.apache.org/jira/browse/IGNITE-7901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rakov updated IGNITE-7901: --- Summary: Refactor Pages Write Throttle: introduce exponential throttle as separate class (was: Refactor Pages Write Throttling: introduce exponential throttle as separate class) > Refactor Pages Write Throttle: introduce exponential throttle as separate > class > --- > > Key: IGNITE-7901 > URL: https://issues.apache.org/jira/browse/IGNITE-7901 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Ivan Rakov >Assignee: Dmitriy Pavlov >Priority: Major > > After IGNITE-7751 fix, we have three incarnations of Pages Write Throttle: > 1) Only checkpoint buffer throttling - always on > 2) Ratio based throttling - legacy > 3) Speed based throttling - default when throttling is enabled > However, all three options use exponential throttling for preventing > checkpoint buffer overflow (see > PagesWriteSpeedBasedThrottle.ThrottleMode#EXPONENTIAL usages and > isPageInCheckpoint branch of PagesWriteThrottle). > For the sake of getting rid of copypaste, it would be better to refactor this > and introduce exponential throttling to separate class. Two callbacks now > will be called instead of one, but code will become nicer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7879) SQL query with group by and distinct in subquery produces JdbcSQLException
[ https://issues.apache.org/jira/browse/IGNITE-7879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-7879: Assignee: Taras Ledkov > SQL query with group by and distinct in subquery produces JdbcSQLException > -- > > Key: IGNITE-7879 > URL: https://issues.apache.org/jira/browse/IGNITE-7879 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.1, 2.3 >Reporter: Pavel Vinokurov >Assignee: Taras Ledkov >Priority: Major > > SQL initial script: > CREATE TABLE Person(id INTEGER PRIMARY KEY, company_id INTEGER); > CREATE TABLE Company(id INTEGER PRIMARY KEY, name VARCHAR); > INSERT INTO Person(id,company_id) VALUES (1, 1), (2, 2), (3, 3); > INSERT INTO Company(id,name) VALUES (1,'n1'), (2,'n2'), (3,'n3'); > SQL query: > SELECT p.id,sum(p.id) FROM person p > LEFT JOIN (select DISTINCT id from company) as c on c.id=p.company_id > group by p.id > Result: > Caused by: org.h2.jdbc.JdbcSQLException: Column "P__Z0.ID" must be in the > GROUP BY list; SQL statement: > SELECT > P__Z0.ID __C0_0, > P__Z0.COMPANY_ID __C0_1, > SUM(P__Z0.ID) __C0_2 > FROM PUBLIC.PERSON P__Z0 [90016-195] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7901) Refactor Pages Write Throttling: introduce exponential throttle as separate class
Ivan Rakov created IGNITE-7901: -- Summary: Refactor Pages Write Throttling: introduce exponential throttle as separate class Key: IGNITE-7901 URL: https://issues.apache.org/jira/browse/IGNITE-7901 Project: Ignite Issue Type: Improvement Affects Versions: 2.5 Reporter: Ivan Rakov Assignee: Dmitriy Pavlov After IGNITE-7751 fix, we have three incarnations of Pages Write Throttle: 1) Only checkpoint buffer throttling - always on 2) Ratio based throttling - legacy 3) Speed based throttling - default when throttling is enabled However, all three options use exponential throttling for preventing checkpoint buffer overflow (see PagesWriteSpeedBasedThrottle.ThrottleMode#EXPONENTIAL usages and isPageInCheckpoint branch of PagesWriteThrottle). For the sake of getting rid of copypaste, it would be better to refactor this and introduce exponential throttling to separate class. Two callbacks now will be called instead of one, but code will become nicer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception
[
https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Popov updated IGNITE-7851:
-
Fix Version/s: 2.5
> .NET: linq query throws "Hexadecimal string with odd number of characters"
> exception
>
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
> Issue Type: Bug
> Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Fix For: 2.5
>
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195] --->
> Apache.Ignite.Core.Common.JavaException: class
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195]
> at
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string
> with odd number of characters: "TST-1/1" [90003-195]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> ... 6 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 19 more
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void*
> target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte*
> errMsgChars, Int32 errMsgCharsLen, SByte* stackTraceChars, Int32
> stackTraceCharsLen, Void* errData, Int32 errDataLen)
>at
> Apache.Ignite.Core.Impl.Unman
[jira] [Commented] (IGNITE-7253) JDBC thin driver: introduce streaming mode
[
https://issues.apache.org/jira/browse/IGNITE-7253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389528#comment-16389528
]
Vladimir Ozerov commented on IGNITE-7253:
-
[~al.psc], my comments:
1) {{SqlParserSetStreamingSelfTest}} doesn't pass
2) {{SqlSetStreamingCommand#parse}} - we should thrown an exception if
parameters are found after {{OFF}} keyword. The easiest way to do this is
simply return as soon as {{OFF}} is found without further parsing. Our parser
should handle this gracefully. Additional tests are needed for this case.
3) {{DdlStatementsProcessor#zeroCursor}} - as this is common method it is
better to put it into {{H2Utils}} instead of DDL processor.
4) {{GridQueryProcessor#cliCtxs}} - unused
5) {{SqlClientContext#enableStreaming/disableStreaming}} - why don't we throw
an exception if user wants to re-enable already enabled streaming? We cannot
simply ignore the second command silently because it may contain different
parameters. I see two possible solutions here - either throw an exception, or
force "OFF" and then re-enable with passed arguments. The latter approach looks
more friendly to me. Additional tests are needed.
6) Please confirm that it is impossible to execute DDL commands when streaming
is on.
7) {{IgniteH2Indexing.doRunPrepared}} - unused {{cliCtx}} argument
8) {{JdbcConnectionContext}} - looks like we should advance the version to 2.5.0
9) {{JdbcRequestHandler}} - it is strange that {{replicatedOnly}} flag was not
moved to {{SqlClientContext}} along with other query parameters
10) {{JdbcBatchExecuteRequest.isLastStreamBatch}} - taking in count p.5 looks
like this flag is not the right way to go should we decide to implement more
user-friendly approach (what is {{STREAMING ON}} is executed when streaming is
enabled already?). Or may be we can for "last stream batch" request in this
case, and then enable streaming again with separate command.
11) {{JdbcThinConnection.executeNative}} - same as p.5, possible change to
streamer config is ignored.
12) {{JdbcthinStatement.checkStatementBatchEmpty}} - error message sounds
unclear to me. Can we rephrase it so something like "Statement has non-empty
batch (call executeBatch() or clearBatch() before enabling streaming)."
13) {{JdbcThinPreparedStatement.addBatch}} - it looks like it is allowed to add
{{SET STREAMING}} to batch here, while exception is thrown in similar case for
{{JdbcThinStatement.addBatch}}.
> JDBC thin driver: introduce streaming mode
> --
>
> Key: IGNITE-7253
> URL: https://issues.apache.org/jira/browse/IGNITE-7253
> Project: Ignite
> Issue Type: Task
> Components: jdbc, sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Major
> Fix For: 2.5
>
> Attachments: IGNITE_7253.patch
>
>
> Should be done after IGNITE-6022. We should allow optional streaming mode for
> JDBC driver. In this mode only INSERTs without SELECT should be possible. All
> other DML operations should throw an exception.
> Design considerations:
> 1) Add command {{SET STREAMING=1|ON|0|OFF}} which will enable or disable
> streaming for connection.
> 2) Add command {{STREAMER FLUSH}} which will force data flush.
> 3) Only INSERT without SELECT works, all other DML statements should throw an
> exception
> 4) It should be possible to stream into several tables simultaneously (i.e.
> several streamers could be opened)
> 5) Any DDL statement should force flush of all currently opened streamers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7900) Write Zookeeper Discovery documentation in readme.io
Dmitry Sherstobitov created IGNITE-7900: --- Summary: Write Zookeeper Discovery documentation in readme.io Key: IGNITE-7900 URL: https://issues.apache.org/jira/browse/IGNITE-7900 Project: Ignite Issue Type: Task Components: zookeeper Affects Versions: 2.5 Reporter: Dmitry Sherstobitov Fix For: 2.5 Describe Zookeeper Discovery in readme.io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7899) Write Zookeeper Discovery documentation in java docs
Dmitry Sherstobitov created IGNITE-7899: --- Summary: Write Zookeeper Discovery documentation in java docs Key: IGNITE-7899 URL: https://issues.apache.org/jira/browse/IGNITE-7899 Project: Ignite Issue Type: Task Components: zookeeper Affects Versions: 2.5 Reporter: Dmitry Sherstobitov Fix For: 2.5 Describe Zookeeper Discovery in java docs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7897) Add example of using LSQR with data normalization
[ https://issues.apache.org/jira/browse/IGNITE-7897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389473#comment-16389473 ] ASF GitHub Bot commented on IGNITE-7897: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3614 > Add example of using LSQR with data normalization > - > > Key: IGNITE-7897 > URL: https://issues.apache.org/jira/browse/IGNITE-7897 > Project: Ignite > Issue Type: Improvement >Reporter: Anton Dmitriev >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.5 > > > Currently we have an LSQR linear regression example (see > [here|https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/ml/regression/linear/DistributedLinearRegressionWithLSQRTrainerExample.java]) > and a normalization procedure example (see > [here|https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/ml/preprocessing/NormalizationExample.java]). > For better understanding we'd like to add an example that includes data > normalization and LSQR linear regression in the same time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7898) IgniteCachePartitionLossPolicySelfTest is flaky on TC
[
https://issues.apache.org/jira/browse/IGNITE-7898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389454#comment-16389454
]
Dmitriy Pavlov commented on IGNITE-7898:
Hi [~Jokser], thank you for continuing to improve Ignite.
please consider closing IGNITE-5148 if your new change will help to solve the
problem
> IgniteCachePartitionLossPolicySelfTest is flaky on TC
> -
>
> Key: IGNITE-7898
> URL: https://issues.apache.org/jira/browse/IGNITE-7898
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.4
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> Affected tests:
> testReadOnlyAll
> testReadWriteSafe
> Exception:
> {code:java}
> junit.framework.AssertionFailedError: Failed to find expected lost partition
> [exp=0, lost=[]]
> at
> org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.verifyCacheOps(IgniteCachePartitionLossPolicySelfTest.java:219)
> at
> org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.checkLostPartition(IgniteCachePartitionLossPolicySelfTest.java:166)
> at
> org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.testReadWriteSafe(IgniteCachePartitionLossPolicySelfTest.java:114)
> {code}
> The problem of failure:
> After we prepare topology and shutdown the node containing lost partition we
> start to check it immediately on all nodes (cache.lostPartitions() method).
> Sometimes we invoke this method on client node where last PME is not even
> started and getting empty list of lost partitions because we haven't received
> it yet on PME.
> Possible solution:
> Wait for PME finishing on all nodes (including client) before start to check
> for lost partitions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7898) IgniteCachePartitionLossPolicySelfTest is flaky on TC
Pavel Kovalenko created IGNITE-7898:
---
Summary: IgniteCachePartitionLossPolicySelfTest is flaky on TC
Key: IGNITE-7898
URL: https://issues.apache.org/jira/browse/IGNITE-7898
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.4
Reporter: Pavel Kovalenko
Assignee: Pavel Kovalenko
Affected tests:
testReadOnlyAll
testReadWriteSafe
Exception:
{code:java}
junit.framework.AssertionFailedError: Failed to find expected lost partition
[exp=0, lost=[]]
at
org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.verifyCacheOps(IgniteCachePartitionLossPolicySelfTest.java:219)
at
org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.checkLostPartition(IgniteCachePartitionLossPolicySelfTest.java:166)
at
org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.testReadWriteSafe(IgniteCachePartitionLossPolicySelfTest.java:114)
{code}
The problem of failure:
After we prepare topology and shutdown the node containing lost partition we
start to check it immediately on all nodes (cache.lostPartitions() method).
Sometimes we invoke this method on client node where last PME is not even
started and getting empty list of lost partitions because we haven't received
it yet on PME.
Possible solution:
Wait for PME finishing on all nodes (including client) before start to check
for lost partitions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7773) .NET: Add getRebalanceClearingPartitionsLeft JMX metric
[ https://issues.apache.org/jira/browse/IGNITE-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko reassigned IGNITE-7773: --- Assignee: Alexey Goncharuk Metric has been fixed. TC: https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&branch_IgniteTests24Java8=pull%2F3613%2Fhead PR: https://github.com/apache/ignite/pull/3613 > .NET: Add getRebalanceClearingPartitionsLeft JMX metric > --- > > Key: IGNITE-7773 > URL: https://issues.apache.org/jira/browse/IGNITE-7773 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Pavel Kovalenko >Assignee: Alexey Goncharuk >Priority: Major > Labels: .NET, MakeTeamcityGreenAgain > Fix For: 2.5 > > > New metric is introduced in IGNITE-6113 . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7880) Enum values not shown correctly in Webconsole
[
https://issues.apache.org/jira/browse/IGNITE-7880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov closed IGNITE-7880.
> Enum values not shown correctly in Webconsole
> -
>
> Key: IGNITE-7880
> URL: https://issues.apache.org/jira/browse/IGNITE-7880
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
> Attachments: image-2018-03-05-13-34-48-992.png
>
>
> Enum values not shown correctly in Webconsole:
>
> {code:java}
> public enum SomeEnum { ONE, TWO; }{code}
>
> !image-2018-03-05-13-34-48-992.png!
>
> expecting value:
> enum value as String like: ONE
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7880) Enum values not shown correctly in Webconsole
[
https://issues.apache.org/jira/browse/IGNITE-7880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-7880:
-
Component/s: (was: visor)
wizards
> Enum values not shown correctly in Webconsole
> -
>
> Key: IGNITE-7880
> URL: https://issues.apache.org/jira/browse/IGNITE-7880
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
> Attachments: image-2018-03-05-13-34-48-992.png
>
>
> Enum values not shown correctly in Webconsole:
>
> {code:java}
> public enum SomeEnum { ONE, TWO; }{code}
>
> !image-2018-03-05-13-34-48-992.png!
>
> expecting value:
> enum value as String like: ONE
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7897) Add example of using LSQR with data normalization
[ https://issues.apache.org/jira/browse/IGNITE-7897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389412#comment-16389412 ] ASF GitHub Bot commented on IGNITE-7897: GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/3614 IGNITE-7897 Add example for LSQR with data normalization. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7897 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3614.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3614 commit 77890d9b1880cc94954b23973c2aee0bcb8847a5 Author: Anton Dmitriev Date: 2018-03-07T11:17:47Z IGNITE-7897 Add example for LSQR with data normalization. > Add example of using LSQR with data normalization > - > > Key: IGNITE-7897 > URL: https://issues.apache.org/jira/browse/IGNITE-7897 > Project: Ignite > Issue Type: Improvement >Reporter: Anton Dmitriev >Assignee: Anton Dmitriev >Priority: Major > > Currently we have an LSQR linear regression example (see > [here|https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/ml/regression/linear/DistributedLinearRegressionWithLSQRTrainerExample.java]) > and a normalization procedure example (see > [here|https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/ml/preprocessing/NormalizationExample.java]). > For better understanding we'd like to add an example that includes data > normalization and LSQR linear regression in the same time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception
[
https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389344#comment-16389344
]
ASF GitHub Bot commented on IGNITE-7851:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3595
> .NET: linq query throws "Hexadecimal string with odd number of characters"
> exception
>
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
> Issue Type: Bug
> Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195] --->
> Apache.Ignite.Core.Common.JavaException: class
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195]
> at
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string
> with odd number of characters: "TST-1/1" [90003-195]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> ... 6 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 19 more
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void*
> target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte*
> errMsgChars, Int32 errMsgCharsLen, SByte* stackTraceCha
[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception
[
https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389333#comment-16389333
]
Sergey Kalashnikov commented on IGNITE-7851:
[~alexey.tank2], looks good to me.
> .NET: linq query throws "Hexadecimal string with odd number of characters"
> exception
>
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
> Issue Type: Bug
> Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195] --->
> Apache.Ignite.Core.Common.JavaException: class
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195]
> at
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string
> with odd number of characters: "TST-1/1" [90003-195]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> ... 6 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 19 more
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void*
> target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte*
> errMsgChars, Int32 errMsgCharsLen, SByte* stackTraceChars, Int32
> stackTraceCharsLen, Void* errData, Int32
[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception
[
https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389330#comment-16389330
]
Alexey Popov commented on IGNITE-7851:
--
TC results are green.
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&branch_IgniteTests24Java8=pull%2F3595%2Fhead
> .NET: linq query throws "Hexadecimal string with odd number of characters"
> exception
>
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
> Issue Type: Bug
> Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195] --->
> Apache.Ignite.Core.Common.JavaException: class
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195]
> at
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string
> with odd number of characters: "TST-1/1" [90003-195]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> ... 6 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number
> of characters: "TST-1/1" [90003-195]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 19 more
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void*
> target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte*
> errMsgChars, In
[jira] [Created] (IGNITE-7897) Add example of using LSQR with data normalization
Anton Dmitriev created IGNITE-7897: -- Summary: Add example of using LSQR with data normalization Key: IGNITE-7897 URL: https://issues.apache.org/jira/browse/IGNITE-7897 Project: Ignite Issue Type: Improvement Reporter: Anton Dmitriev Assignee: Anton Dmitriev Currently we have an LSQR linear regression example (see [here|https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/ml/regression/linear/DistributedLinearRegressionWithLSQRTrainerExample.java]) and a normalization procedure example (see [here|https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/ml/preprocessing/NormalizationExample.java]). For better understanding we'd like to add an example that includes data normalization and LSQR linear regression in the same time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7773) .NET: Add getRebalanceClearingPartitionsLeft JMX metric
[ https://issues.apache.org/jira/browse/IGNITE-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389293#comment-16389293 ] ASF GitHub Bot commented on IGNITE-7773: GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3613 IGNITE-7773 Add 'rebalanceClearingPartitionsLeft' metric to .NET You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7773 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3613.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3613 commit 0d839c8ecfbd521825ab13be799073207c4bbf71 Author: Pavel Kovalenko Date: 2018-03-07T09:17:13Z IGNITE-7773 Add 'rebalanceClearingPartitionsLeft' metric to .NET > .NET: Add getRebalanceClearingPartitionsLeft JMX metric > --- > > Key: IGNITE-7773 > URL: https://issues.apache.org/jira/browse/IGNITE-7773 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Pavel Kovalenko >Priority: Major > Labels: .NET, MakeTeamcityGreenAgain > Fix For: 2.5 > > > New metric is introduced in IGNITE-6113 . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7773) .NET: Add getRebalanceClearingPartitionsLeft JMX metric
[ https://issues.apache.org/jira/browse/IGNITE-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7773: --- Labels: .NET MakeTeamcityGreenAgain (was: .NET) > .NET: Add getRebalanceClearingPartitionsLeft JMX metric > --- > > Key: IGNITE-7773 > URL: https://issues.apache.org/jira/browse/IGNITE-7773 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Pavel Kovalenko >Priority: Major > Labels: .NET, MakeTeamcityGreenAgain > Fix For: 2.5 > > > New metric is introduced in IGNITE-6113 . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7894) Web console: extract new design collapsible panels into component
[ https://issues.apache.org/jira/browse/IGNITE-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-7894: Assignee: Andrey Novikov (was: Ilya Borisov) [~anovikov] please review. > Web console: extract new design collapsible panels into component > - > > Key: IGNITE-7894 > URL: https://issues.apache.org/jira/browse/IGNITE-7894 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Andrey Novikov >Priority: Minor > Attachments: image-2018-03-07-10-39-32-857.png, > image-2018-03-07-10-42-01-013.png, image-2018-03-07-10-42-44-368.png > > > Collapsible panels in new design still don't have a reusable component that > encapsulates it's behavior and styles. > Where such panels are/will be used: > 1. Redesigned cluster configuration forms. > !image-2018-03-07-10-42-44-368.png! > 2. Current user profile. > !image-2018-03-07-10-42-01-013.png! > 3. Upcoming queries screen redesign. > !image-2018-03-07-10-39-32-857.png! > New component should: > 1. Have bindings for opened state and opened/closed events. > 2. Have a way to insert buttons to the right of header. > Make sure that there are no leftover unused styles/code left. > What to test when the issue's done: > 1. Panels on user profile page. > 2. Panels on configuration screens should still have lazy panel content > loading. > 3. Legacy validation in clutser configuration / advanced / domain model form. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5298) .NET: DML update via LINQ
[
https://issues.apache.org/jira/browse/IGNITE-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389260#comment-16389260
]
ASF GitHub Bot commented on IGNITE-5298:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3599
> .NET: DML update via LINQ
> -
>
> Key: IGNITE-5298
> URL: https://issues.apache.org/jira/browse/IGNITE-5298
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, LINQ, important
> Fix For: 2.5
>
>
> Bulk update with LINQ:
> {code}
> var persons = ignite.GetCache("persons").AsCacheQueryable();
> int affectedRows = persons.Where(x => x.Key > 10).UpdateAll(x =>
> x.Value.OrgId = 7);
> {code}
> See bulk delete with {{RemoveAll}}, IGNITE-4904.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7896) Files of evicted partitions do not remove from disk storage
[ https://issues.apache.org/jira/browse/IGNITE-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Vinokurov reassigned IGNITE-7896: --- Assignee: Pavel Vinokurov > Files of evicted partitions do not remove from disk storage > --- > > Key: IGNITE-7896 > URL: https://issues.apache.org/jira/browse/IGNITE-7896 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Pavel Vinokurov >Priority: Major > Attachments: IgnitePdsRebalanceCompletionAndPartitionFilesTest.java > > > Look at test reproduction: > [^IgnitePdsRebalanceCompletionAndPartitionFilesTest.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5300) .NET: LINQ RemoveAll and UpdateAll examples
[
https://issues.apache.org/jira/browse/IGNITE-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-5300:
---
Fix Version/s: 2.5
> .NET: LINQ RemoveAll and UpdateAll examples
> ---
>
> Key: IGNITE-5300
> URL: https://issues.apache.org/jira/browse/IGNITE-5300
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, LINQ
> Fix For: 2.5
>
>
> Update examples (normal and LinqPad) to demonstrate {{RemoveAll}} and
> {{UpdateAll}} LINQ bulk operations (IGNITE-4904, IGNITE-5298).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-5300) .NET: LINQ RemoveAll and UpdateAll examples
[
https://issues.apache.org/jira/browse/IGNITE-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-5300:
---
Description: Update examples (normal and LinqPad) to demonstrate
{{RemoveAll}} and {{UpdateAll}} LINQ bulk operations (IGNITE-4904,
IGNITE-5298). (was: Update examples (normal and LinqPad) to demonstrate
{{RemoveAll}} LINQ bulk delete (IGNITE-4904).)
> .NET: LINQ RemoveAll and UpdateAll examples
> ---
>
> Key: IGNITE-5300
> URL: https://issues.apache.org/jira/browse/IGNITE-5300
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, LINQ
> Fix For: 2.5
>
>
> Update examples (normal and LinqPad) to demonstrate {{RemoveAll}} and
> {{UpdateAll}} LINQ bulk operations (IGNITE-4904, IGNITE-5298).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-5300) .NET: LINQ RemoveAll and UpdateAll examples
[
https://issues.apache.org/jira/browse/IGNITE-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-5300:
---
Summary: .NET: LINQ RemoveAll and UpdateAll examples (was: .NET: LINQ
RemoveAll examples)
> .NET: LINQ RemoveAll and UpdateAll examples
> ---
>
> Key: IGNITE-5300
> URL: https://issues.apache.org/jira/browse/IGNITE-5300
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, LINQ
> Fix For: 2.5
>
>
> Update examples (normal and LinqPad) to demonstrate {{RemoveAll}} LINQ bulk
> delete (IGNITE-4904).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5298) .NET: DML update via LINQ
[
https://issues.apache.org/jira/browse/IGNITE-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389257#comment-16389257
]
Pavel Tupitsyn commented on IGNITE-5298:
Merged to master: {{ed76af245e7947b0e701907bde76849971a6a75c}}.
Thanks again [~GuruStron]!
> .NET: DML update via LINQ
> -
>
> Key: IGNITE-5298
> URL: https://issues.apache.org/jira/browse/IGNITE-5298
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, LINQ, important
> Fix For: 2.5
>
>
> Bulk update with LINQ:
> {code}
> var persons = ignite.GetCache("persons").AsCacheQueryable();
> int affectedRows = persons.Where(x => x.Key > 10).UpdateAll(x =>
> x.Value.OrgId = 7);
> {code}
> See bulk delete with {{RemoveAll}}, IGNITE-4904.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-5298) .NET: DML update via LINQ
[
https://issues.apache.org/jira/browse/IGNITE-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-5298:
---
Fix Version/s: 2.5
> .NET: DML update via LINQ
> -
>
> Key: IGNITE-5298
> URL: https://issues.apache.org/jira/browse/IGNITE-5298
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, LINQ, important
> Fix For: 2.5
>
>
> Bulk update with LINQ:
> {code}
> var persons = ignite.GetCache("persons").AsCacheQueryable();
> int affectedRows = persons.Where(x => x.Key > 10).UpdateAll(x =>
> x.Value.OrgId = 7);
> {code}
> See bulk delete with {{RemoveAll}}, IGNITE-4904.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-7566) .NET: Build scripts: stop build when one of the steps fails
[
https://issues.apache.org/jira/browse/IGNITE-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-7566.
Resolution: Fixed
> .NET: Build scripts: stop build when one of the steps fails
> ---
>
> Key: IGNITE-7566
> URL: https://issues.apache.org/jira/browse/IGNITE-7566
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.5
>
>
> We have multiple build scripts for various platforms:
> * {{build.bat}} / {{build.ps1}} (Windows)
> * {{build.sh}} (.NET Core Linux / macOS)
> * {{build-mono.sh}} (Mono Linux / macOS)
> Make sure that we stop build scripts execution when one of the steps fails.
> For example, if Java build fails, we should show an error and stop instead of
> continuing to build .NET.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7566) .NET: Build scripts: stop build when one of the steps fails
[
https://issues.apache.org/jira/browse/IGNITE-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389221#comment-16389221
]
Pavel Tupitsyn commented on IGNITE-7566:
Fixed in master: {{0936f162b84d0ff701ac020405e7e44f55fae52e}}.
> .NET: Build scripts: stop build when one of the steps fails
> ---
>
> Key: IGNITE-7566
> URL: https://issues.apache.org/jira/browse/IGNITE-7566
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.5
>
>
> We have multiple build scripts for various platforms:
> * {{build.bat}} / {{build.ps1}} (Windows)
> * {{build.sh}} (.NET Core Linux / macOS)
> * {{build-mono.sh}} (Mono Linux / macOS)
> Make sure that we stop build scripts execution when one of the steps fails.
> For example, if Java build fails, we should show an error and stop instead of
> continuing to build .NET.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
