[jira] [Assigned] (IGNITE-1770) Portables: implement constant-time field lookup.

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel  Tupitsyn reassigned IGNITE-1770:
---

Assignee: Pavel  Tupitsyn  (was: Vladimir Ozerov)

> Portables: implement constant-time field lookup.
> 
>
> Key: IGNITE-1770
> URL: https://issues.apache.org/jira/browse/IGNITE-1770
> Project: Ignite
>  Issue Type: Task
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Blocker
> Fix For: 1.5
>
>
> See 
> https://cwiki.apache.org/confluence/display/IGNITE/Portable+object+constant-time+field+lookup



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1770) Portables: implement constant-time field lookup.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980358#comment-14980358
 ] 

ASF GitHub Bot commented on IGNITE-1770:


GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/182

IGNITE-1770 Portables: implement constant-time field lookup

Adopt protocol in .NET

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-1770-dotnet

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/182.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 #182


commit 4121b549462fd14272b341843935c4f1dbad343d
Author: vozerov-gridgain 
Date:   2015-10-23T08:16:37Z

IGNITE-1665: Avoid field ID re-calculation during reads.

commit f15d66c2203c46c8951b051690e1b7b662fde8c2
Author: vozerov-gridgain 
Date:   2015-10-23T12:02:42Z

IGNITE-1770: WIP.

commit b9422dfa16cf3674d4d0c7587330bd309cbb21f6
Author: vozerov-gridgain 
Date:   2015-10-23T12:03:00Z

Merge branch 'ignite-1282' into ignite-1770

commit d218714087d64369bbe0f8c855d7c9cd3f2b8ef2
Author: vozerov-gridgain 
Date:   2015-10-23T12:36:49Z

IGNITE-1770: Added 1 byte to flags.

commit 1e62f46721edcf59671337df7a7df2180e470aa7
Author: vozerov-gridgain 
Date:   2015-10-23T13:35:29Z

IGNITE-1770: Simplifications on writer side.

commit 844ff1e829b0071d129b332d3a6748960dec66b4
Author: vozerov-gridgain 
Date:   2015-10-23T14:19:30Z

IGNITE-1770: Better raw mode handling.

commit cd931d3e2d67d527e8f493c86eaa8248b0356327
Author: vozerov-gridgain 
Date:   2015-10-23T14:20:16Z

IGNITE-1770: Better raw mode handling.

commit 03e1f8d25eb257e7cfcc3fd2c8d7f427b3a470c8
Author: vozerov-gridgain 
Date:   2015-10-23T14:21:42Z

IGNITE-1770: Better raw mode handling.

commit 2a8b75a269f71f2487bd9eb24457df2e1c53d3c1
Author: vozerov-gridgain 
Date:   2015-10-23T14:26:03Z

IGNITE-1770: Better raw mode handling.

commit 7cf21365f124c16560eba05d14507e7e124a838b
Author: vozerov-gridgain 
Date:   2015-10-23T14:27:10Z

IGNITE-1770: Better raw mode handling.

commit d5327836941fd4805ca441de51a81e427484bfb6
Author: vozerov-gridgain 
Date:   2015-10-23T14:28:53Z

IGNITE-1770: Better raw mode handling.

commit 80bbc7def3c32ce3daac7901731ef35c2d5bfde7
Author: vozerov-gridgain 
Date:   2015-10-23T14:31:04Z

IGNITE-1770: Better raw mode handling.

commit 46e1734d26a33342870246c034090119e1aa7be9
Author: vozerov-gridgain 
Date:   2015-10-23T14:37:11Z

IGNITE-1770: Better tests.

commit 90cb58842627855eac14621398e4a1619c704878
Author: vozerov-gridgain 
Date:   2015-10-23T14:41:13Z

IGNITE-1770: Better tests.

commit 0a024013f0b23fc1108b610a1ccb955163ee4d31
Author: vozerov-gridgain 
Date:   2015-10-23T14:53:39Z

IGNITE-1770: Added space for schema offset.

commit c4ce99736e054f52696be8387aa91e8ec9ca0e23
Author: vozerov-gridgain 
Date:   2015-10-23T14:58:13Z

IGNITE-1770: Field info is written to the tail.

commit 7bd743c3697e4e3886e7b3e12a5836907f877fec
Author: vozerov-gridgain 
Date:   2015-10-26T07:42:36Z

IGNITE-1770: Offset then ID in the tail.

commit 96d08a5312f1c6270abb755ed65784b60ac660b4
Author: vozerov-gridgain 
Date:   2015-10-26T07:51:50Z

IGNITE-1770: Do not write offset for the first field.

commit d6ba7185dca7f0f160d63a67486995e80ef5792a
Author: vozerov-gridgain 
Date:   2015-10-26T07:56:14Z

IGNITE-1770: Write raw offset if needed.

commit 8c039fb1d25ca1c1e874c813e2877945cd4c63e6
Author: vozerov-gridgain 
Date:   2015-10-26T08:26:59Z

IGNITE-1770: Reader refactoring.

commit 47e54b2db4415aa3cd52ad09edcad54089f96ea0
Author: vozerov-gridgain 
Date:   2015-10-26T08:53:02Z

IGNITE-1770: Reader refactoring.

commit 1fc0757b73b81d1a56fd6bf14632418872e4b88a
Author: vozerov-gridgain 
Date:   2015-10-26T08:59:49Z

IGNITE-1770: Reader refactoring (2).

commit 5bfb9a052ddec80de52e1db639862f58ad967cd3
Author: vozerov-gridgain 
Date:   2015-10-26T09:10:22Z

IGNITE-1770: Reader refactoring (3).

commit 31945688407a87d9041b0ab90e62399feaac799d
Author: vozerov-gridgain 
Date:   2015-10-26T09:16:33Z

IGNITE-1770: Reader refactoring (3).

commit 0489b145a20cfca85e30561b783272101ad1dc68
Author: vozerov-gridgain 

[jira] [Created] (IGNITE-1810) Upgrade ignite-aws dependencies (HttpClient and AWS SDK)

[JIRA]

Raúl Kripalani created IGNITE-1810:
--

 Summary: Upgrade ignite-aws dependencies (HttpClient and AWS SDK)
 Key: IGNITE-1810
 URL: https://issues.apache.org/jira/browse/IGNITE-1810
 Project: Ignite
  Issue Type: Improvement
  Components: aws
Reporter: Raúl Kripalani
Assignee: Raúl Kripalani
 Fix For: 1.5


We need to upgrade the HttpClient and AWS SDK dependencies in ignite-aws. They 
are very old:

* AWS SDK 1.3.21.1 => 1.10.29
* HttpClient 4.2.3 => 4.5.1
* HttpCore 4.2.3 => 4.4.3

These upgrades are needed by the OSGi integration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1607) Implement deadlock-free optimistic serializable mode

[Semen Boikov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980498#comment-14980498
 ] 

Semen Boikov commented on IGNITE-1607:
--

CacheSerializableTransactionsTest.testIncrementTxRestartfailed on TC, 
need investigate:
http://94.72.60.102/viewLog.html?buildId=559325=buildResultsDiv=Ignite_IgniteCache5

> Implement deadlock-free optimistic serializable mode
> 
>
> Key: IGNITE-1607
> URL: https://issues.apache.org/jira/browse/IGNITE-1607
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Semen Boikov
> Fix For: 1.5
>
>
> There is an idea of optimistic serializable mode which will provide better 
> scalability on relatively large transactions and large topologies when no 
> heavy contention is experienced.
>  * When transactional read is performed, we need to store the version of read 
> entry.
>  * When transaction prepare is performed, we can send prepare requests 
> simultaneously on all nodes. There is no need to preserve the order of locks 
> and create a queue of tx mappings for this mode.
>  * When we add local MVCC candidates on a primary node, two checks are 
> performed: that the current entry version matches the one transaction read 
> (if read was performed), and that currently there are no other local MVCC 
> candidates. If any of these checks fails, prepare step fails and transaction 
> is failed with optimistic conflict exception.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-1607) Implement deadlock-free optimistic serializable mode

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov reassigned IGNITE-1607:


Assignee: Semen Boikov

> Implement deadlock-free optimistic serializable mode
> 
>
> Key: IGNITE-1607
> URL: https://issues.apache.org/jira/browse/IGNITE-1607
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Semen Boikov
> Fix For: 1.5
>
>
> There is an idea of optimistic serializable mode which will provide better 
> scalability on relatively large transactions and large topologies when no 
> heavy contention is experienced.
>  * When transactional read is performed, we need to store the version of read 
> entry.
>  * When transaction prepare is performed, we can send prepare requests 
> simultaneously on all nodes. There is no need to preserve the order of locks 
> and create a queue of tx mappings for this mode.
>  * When we add local MVCC candidates on a primary node, two checks are 
> performed: that the current entry version matches the one transaction read 
> (if read was performed), and that currently there are no other local MVCC 
> candidates. If any of these checks fails, prepare step fails and transaction 
> is failed with optimistic conflict exception.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1809) GridCacheAtomicMultiNodeP2PDisabledFullApiSelfTest.testWithSkipStore fails on TC sometimes

[Artem Shutak (JIRA)]

Artem Shutak created IGNITE-1809:


 Summary: 
GridCacheAtomicMultiNodeP2PDisabledFullApiSelfTest.testWithSkipStore  fails 
on TC sometimes
 Key: IGNITE-1809
 URL: https://issues.apache.org/jira/browse/IGNITE-1809
 Project: Ignite
  Issue Type: Test
Reporter: Artem Shutak
Priority: Blocker
 Fix For: 1.5


GridCacheAtomicMultiNodeP2PDisabledFullApiSelfTest.testWithSkipStorefails 
on TC sometimes.

Logs
{noformat}
junit.framework.AssertionFailedError: Expected:  but was: 230
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertNull(Assert.java:277)
at junit.framework.Assert.assertNull(Assert.java:268)
at junit.framework.TestCase.assertNull(TestCase.java:438)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4550)
at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1658)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:112)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1596)
--- Stdout: ---
[21:00:58,689][INFO ][main][root] >>> Starting test: testWithSkipStore <<<
[21:00:59,506][INFO ][main][root] >>> Stopping test: testWithSkipStore in 816 
ms <<<
[21:00:59,506][INFO ][main][root] Checking grid: 0
[21:00:59,512][INFO ][main][root] Size after [idx=0, size=0, keySize=0, 
primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries []]
[21:00:59,513][INFO ][main][root] Checking grid: 1
[21:00:59,518][INFO ][main][root] Size after [idx=1, size=0, keySize=0, 
primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries []]
[21:00:59,519][INFO ][main][root] Checking grid: 2
[21:00:59,524][INFO ][main][root] Size after [idx=2, size=0, keySize=0, 
primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries []]
[21:00:59,525][INFO ][main][root] Checking grid: 3
[21:00:59,530][INFO ][main][root] Size after [idx=3, size=0, keySize=0, 
primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries []]
--- Stderr: ---
[21:00:59,505][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: Expected:  but was: 230
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertNull(Assert.java:277)
at junit.framework.Assert.assertNull(Assert.java:268)
at junit.framework.TestCase.assertNull(TestCase.java:438)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4550)
at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1658)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:112)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1596)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-1717) NPE during running ScalarCreditRiskExample with portableMarshaller

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda reassigned IGNITE-1717:
---

Assignee: Vasilisa  Sidorova  (was: Denis Magda)

> NPE during running ScalarCreditRiskExample with portableMarshaller
> --
>
> Key: IGNITE-1717
> URL: https://issues.apache.org/jira/browse/IGNITE-1717
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: Ubuntu 14.04, community 1.5.0 build #319
>Reporter: Vasilisa  Sidorova
>Assignee: Vasilisa  Sidorova
> Fix For: 1.5
>
>
> -
> DESCRIPTION
> -
> When default optimizedMarshaller is changed into portableMarshaller in 
> example-ignite.xml then ScalarCreditRiskExample  is failed with NPE
> -
> STEPS FOR REPRODUCE
> -
> 1. Build examples project in IDE
> 2.In the example-ignite.xml change property from:
> {noformat}
> 
>  class="org.apache.ignite.marshaller.optimized.OptimizedMarshaller"> -->
> 
>  ACTUAL RESULT
> -
> Example is failed with exception:
> {noformat}
> [13:57:40,936][ERROR][ignite-#18%sys-null%][GridTaskWorker] Failed to obtain 
> remote job result policy for result from ComputeTask.result(..) method (will 
> fail the whole task): GridJobResultImpl [job=C2 [], sib=GridJobSiblingImpl 
> [sesId=5274c407051-955a7d7a-3558-446d-842f-ca760c8e8b02, 
> jobId=8274c407051-a6a70d16-43e2-4c1a-b741-19c83132a1c8, 
> nodeId=a6a70d16-43e2-4c1a-b741-19c83132a1c8, isJobDone=false], 
> jobCtx=GridJobContextImpl 
> [jobId=8274c407051-a6a70d16-43e2-4c1a-b741-19c83132a1c8, timeoutObj=null, 
> attrs={}], node=TcpDiscoveryNode [id=a6a70d16-43e2-4c1a-b741-19c83132a1c8, 
> addrs=[0:0:0:0:0:0:0:1%1, 10.0.0.7, 127.0.0.1, 192.168.1.179], 
> sockAddrs=[/10.0.0.7:47500, /0:0:0:0:0:0:0:1%1:47500, /192.168.1.179:47500, 
> /10.0.0.7:47500, /127.0.0.1:47500, /192.168.1.179:47500], discPort=47500, 
> order=1, intOrder=1, lastExchangeTime=1444993059563, loc=false, 
> ver=1.5.0#20151012-sha1:6844370d, isClient=false], ex=class 
> o.a.i.IgniteException: null, hasRes=true, isCancelled=false, isOccupied=true]
> class org.apache.ignite.IgniteException: Remote job threw user exception 
> (override or implement ComputeTask.result(..) method if you would like to 
> have automatic failover for this exception).
>   at 
> org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$T3.result(GridClosureProcessor.java:1246)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:903)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:896)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6403)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:896)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:792)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:995)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1219)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
>   at java.lang.Thread.run(Thread.java:809)
> Caused by: class org.apache.ignite.IgniteException: null
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1792)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6371)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:456)
>   at 
> 

[jira] [Commented] (IGNITE-1756) [Test Failed] GridCacheAtomicOffHeapTieredMultiNodeFullApiSelfTest.testIgniteCacheIterator fails sometimes

[Artem Shutak (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980295#comment-14980295
 ] 

Artem Shutak commented on IGNITE-1756:
--

GridCacheAtomicNearEnabledMultiNodeFullApiSelfTest.testIgniteCacheIterator  
fails with the same exception (in portable case).

> [Test Failed] 
> GridCacheAtomicOffHeapTieredMultiNodeFullApiSelfTest.testIgniteCacheIterator 
> fails sometimes
> --
>
> Key: IGNITE-1756
> URL: https://issues.apache.org/jira/browse/IGNITE-1756
> Project: Ignite
>  Issue Type: Test
>Reporter: Artem Shutak
>Priority: Blocker
>  Labels: Muted_test
> Fix For: 1.5
>
>
> GridCacheAtomicOffHeapTieredMultiNodeFullApiSelfTest.testIgniteCacheIterator 
> fails on TC sometimes.
> {noformat}
> junit.framework.AssertionFailedError: Iterators not removed for grid 2 
> expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.TestCase.assertEquals(TestCase.java:401)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest$CheckIteratorTask.call(GridCacheAbstractFullApiSelfTest.java:5240)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest$CheckIteratorTask.call(GridCacheAbstractFullApiSelfTest.java:5229)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.executeOnLocalOrRemoteJvm(GridAbstractTest.java:1477)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.checkIteratorsCleared(GridCacheAbstractFullApiSelfTest.java:4144)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.checkIteratorEmpty(GridCacheAbstractFullApiSelfTest.java:4170)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testIgniteCacheIterator(GridCacheAbstractFullApiSelfTest.java:4036)
> at sun.reflect.GeneratedMethodAccessor95.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1658)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:112)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1596)
> --- Stdout: ---
> [17:58:58,214][INFO ][main][root] >>> Starting test: testIgniteCacheIterator 
> <<<
> [17:58:58,237][INFO ][test-runner][root] Puts finished: 500
> [17:58:58,244][INFO ][test-runner][root] Puts finished: 1000
> [17:58:58,248][INFO ][test-runner][root] Puts finished: 1500
> [17:58:58,256][INFO ][test-runner][root] Puts finished: 2000
> [17:58:58,263][INFO ][test-runner][root] Puts finished: 2500
> [17:58:58,270][INFO ][test-runner][root] Puts finished: 3000
> [17:58:58,275][INFO ][test-runner][root] Puts finished: 3500
> [17:58:58,281][INFO ][test-runner][root] Puts finished: 4000
> [17:58:58,286][INFO ][test-runner][root] Puts finished: 4500
> [17:58:58,290][INFO ][test-runner][root] Puts finished: 5000
> [17:58:58,294][INFO ][test-runner][root] Puts finished: 5500
> [17:58:58,298][INFO ][test-runner][root] Puts finished: 6000
> [17:58:58,303][INFO ][test-runner][root] Puts finished: 6500
> [17:58:58,307][INFO ][test-runner][root] Puts finished: 7000
> [17:58:58,313][INFO ][test-runner][root] Puts finished: 7500
> [17:58:58,318][INFO ][test-runner][root] Puts finished: 8000
> [17:58:58,323][INFO ][test-runner][root] Puts finished: 8500
> [17:58:58,327][INFO ][test-runner][root] Puts finished: 9000
> [17:58:58,334][INFO ][test-runner][root] Puts finished: 9500
> [17:58:58,340][INFO ][test-runner][root] Puts finished: 1
> [17:58:58,523][INFO ][test-runner][root] Caught expected exception: null
> [17:58:58,785][INFO ][test-runner][root] Set iterators not cleared, will wait
> [17:58:59,286][INFO ][test-runner][root] Set iterators not cleared, will wait
> [17:58:59,787][INFO ][test-runner][root] Set iterators not cleared, will wait
> [17:59:00,287][INFO ][test-runner][root] Set iterators not cleared, will wait
> [17:59:00,788][INFO ][test-runner][root] Set iterators not cleared, will wait
> [17:59:01,289][INFO ][test-runner][root] Set iterators not cleared, will wait
> [17:59:01,790][INFO ][test-runner][root] Set iterators not cleared, will wait
> [17:59:02,291][INFO ][test-runner][root] Set iterators not 

[jira] [Commented] (IGNITE-1717) NPE during running ScalarCreditRiskExample with portableMarshaller

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980380#comment-14980380
 ] 

Denis Magda commented on IGNITE-1717:
-

Thanks Andrey, the changes look good for me. Will merge the changes to the 
master shortly.

> NPE during running ScalarCreditRiskExample with portableMarshaller
> --
>
> Key: IGNITE-1717
> URL: https://issues.apache.org/jira/browse/IGNITE-1717
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: Ubuntu 14.04, community 1.5.0 build #319
>Reporter: Vasilisa  Sidorova
>Assignee: Denis Magda
> Fix For: 1.5
>
>
> -
> DESCRIPTION
> -
> When default optimizedMarshaller is changed into portableMarshaller in 
> example-ignite.xml then ScalarCreditRiskExample  is failed with NPE
> -
> STEPS FOR REPRODUCE
> -
> 1. Build examples project in IDE
> 2.In the example-ignite.xml change property from:
> {noformat}
> 
>  class="org.apache.ignite.marshaller.optimized.OptimizedMarshaller"> -->
> 
>  ACTUAL RESULT
> -
> Example is failed with exception:
> {noformat}
> [13:57:40,936][ERROR][ignite-#18%sys-null%][GridTaskWorker] Failed to obtain 
> remote job result policy for result from ComputeTask.result(..) method (will 
> fail the whole task): GridJobResultImpl [job=C2 [], sib=GridJobSiblingImpl 
> [sesId=5274c407051-955a7d7a-3558-446d-842f-ca760c8e8b02, 
> jobId=8274c407051-a6a70d16-43e2-4c1a-b741-19c83132a1c8, 
> nodeId=a6a70d16-43e2-4c1a-b741-19c83132a1c8, isJobDone=false], 
> jobCtx=GridJobContextImpl 
> [jobId=8274c407051-a6a70d16-43e2-4c1a-b741-19c83132a1c8, timeoutObj=null, 
> attrs={}], node=TcpDiscoveryNode [id=a6a70d16-43e2-4c1a-b741-19c83132a1c8, 
> addrs=[0:0:0:0:0:0:0:1%1, 10.0.0.7, 127.0.0.1, 192.168.1.179], 
> sockAddrs=[/10.0.0.7:47500, /0:0:0:0:0:0:0:1%1:47500, /192.168.1.179:47500, 
> /10.0.0.7:47500, /127.0.0.1:47500, /192.168.1.179:47500], discPort=47500, 
> order=1, intOrder=1, lastExchangeTime=1444993059563, loc=false, 
> ver=1.5.0#20151012-sha1:6844370d, isClient=false], ex=class 
> o.a.i.IgniteException: null, hasRes=true, isCancelled=false, isOccupied=true]
> class org.apache.ignite.IgniteException: Remote job threw user exception 
> (override or implement ComputeTask.result(..) method if you would like to 
> have automatic failover for this exception).
>   at 
> org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$T3.result(GridClosureProcessor.java:1246)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:903)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:896)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6403)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:896)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:792)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:995)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1219)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
>   at java.lang.Thread.run(Thread.java:809)
> Caused by: class org.apache.ignite.IgniteException: null
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1792)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6371)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:456)
>   at 
> 

[jira] [Updated] (IGNITE-1811) Get from backup in Dht cache can be optimized

[Yakov Zhdanov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yakov Zhdanov updated IGNITE-1811:
--
Attachment: Screenshot 2015-10-29 18.04.07.png

> Get from backup in Dht cache can be optimized
> -
>
> Key: IGNITE-1811
> URL: https://issues.apache.org/jira/browse/IGNITE-1811
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Yakov Zhdanov
>Assignee: Yakov Zhdanov
> Attachments: Screenshot 2015-10-29 18.04.07.png
>
>
> Reproducible example: https://gist.github.com/aboudnik/3419fdc3872cc3051a1d
> See attached screenshot for sampling info.
> Issues found:
> # entry is created with putIfObsoleteOrAbsent() even if store and swap are 
> disabled
> # no need to create DhtGetFuture on primary when there is no ongoing 
> rebalancing 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1770) Portables: implement constant-time field lookup.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980643#comment-14980643
 ] 

ASF GitHub Bot commented on IGNITE-1770:


GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/183

IGNITE-1770 Portables: implement constant-time field lookup.

.NET part

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-1770-dotnet

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/183.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 #183


commit 43be01e2b81320cd4532f0f5ad9e33e7be02c083
Author: Pavel Tupitsyn 
Date:   2015-10-28T09:57:53Z

Ignite-1770 wip

commit b861086c37179ec02693a00129cb38740f5d864f
Author: Pavel Tupitsyn 
Date:   2015-10-28T10:11:09Z

Renaming

commit 4b6dc0ced524249e2bd3fceb642cc78fee082c6a
Author: Pavel Tupitsyn 
Date:   2015-10-28T10:52:40Z

Wip header reading

commit 8f00b91ae2f5dc0aaf2f5f82ddd13b0971c2665c
Author: Pavel Tupitsyn 
Date:   2015-10-28T12:03:23Z

wip

commit ed924914acef7bc154a39259ebe4313dd1c2e112
Author: Pavel Tupitsyn 
Date:   2015-10-28T12:07:53Z

wip

commit 905841892d6a2da6d09067da74675629af275455
Author: Pavel Tupitsyn 
Date:   2015-10-28T12:10:33Z

wip

commit 080578226d39b10e2a5355f0f039b52246b834e6
Author: Pavel Tupitsyn 
Date:   2015-10-28T12:58:50Z

wip writer

commit c07eae8fa8ce5bef363c93daf8aa205af59f6444
Author: Pavel Tupitsyn 
Date:   2015-10-28T13:17:29Z

wip writer

commit 4ecbbeead8eaa4b964aa6988d4c192bc5c8c4154
Author: Pavel Tupitsyn 
Date:   2015-10-28T13:37:37Z

writer done?

commit 10ae3cef15070038328f8b05e4d6508ed8214340
Author: Pavel Tupitsyn 
Date:   2015-10-28T13:42:24Z

wip

commit ecd3163efc136ca6440bdb832de5cf3b0994e69e
Author: Pavel Tupitsyn 
Date:   2015-10-28T13:48:45Z

fixing raw offset

commit cc0c81a25b95c567bc70b8acb4abfd0c7c5c5482
Author: Pavel Tupitsyn 
Date:   2015-10-28T13:53:57Z

fixing raw offset

commit 6b9d4cbd530e99d49eaf2244bc2398d79bc17263
Author: Pavel Tupitsyn 
Date:   2015-10-28T14:00:01Z

wip

commit 224aeda51c8a259b894145c374355390bff65c46
Author: Pavel Tupitsyn 
Date:   2015-10-28T14:04:15Z

reader done

commit 6191baabf9095f64d28b26bf16a931b85e5ecbc2
Author: Pavel Tupitsyn 
Date:   2015-10-28T14:11:36Z

wip

commit 76a26064ed1d457f9655641c0b3e5d24037936ba
Author: Pavel Tupitsyn 
Date:   2015-10-28T14:18:10Z

wip

commit 45c76b4c902d62638eb1f72a3a177f20fba4cf10
Author: Pavel Tupitsyn 
Date:   2015-10-28T14:22:30Z

fixing

commit d362ec0bdc02bf3e79b52dd92bc607e3c7f75a63
Author: Pavel Tupitsyn 
Date:   2015-10-28T14:27:22Z

wip

commit 2eb98b377ecbc22a5f41ee702793f1b9d559696f
Author: Pavel Tupitsyn 
Date:   2015-10-28T14:37:04Z

wip

commit b3669d3f715e03d95ad0f0fe99822cf228d4e04c
Author: Pavel Tupitsyn 
Date:   2015-10-28T14:40:39Z

wip

commit 302d94659cc1671531a22270c36b4735ef94d5d8
Author: Pavel Tupitsyn 
Date:   2015-10-28T14:50:50Z

Merge remote-tracking branch 'remotes/upstream/ignite-1770' into 
ignite-1770-dotnet

commit 1cf37391089760546d3d9f9c256f8a35a016f1dc
Author: Pavel Tupitsyn 
Date:   2015-10-28T14:52:16Z

wip

commit ec5f5f0f957bea9d577ddaab979054e9009cd063
Author: Pavel Tupitsyn 
Date:   2015-10-28T14:53:41Z

wip

commit 15473c4529de8279231901cac61d09199c860595
Author: Pavel Tupitsyn 
Date:   2015-10-28T15:29:14Z

fixing portable objects

commit d6b08850d14ba7b1854c532e7b1f3dac7a765fce
Author: Pavel Tupitsyn 
Date:   2015-10-28T15:30:41Z

Merge remote-tracking branch 'remotes/upstream/ignite-1770' into 
ignite-1770-dotnet

commit f6c91c8cfdbf5fe0888d6a9af0444d12c803f65f
Author: Pavel Tupitsyn 
Date:   2015-10-28T16:17:08Z

wip

commit 543a67ce2f8540dabf4877a09b8a9effa9a63193
Author: Pavel Tupitsyn 
Date:   2015-10-28T16:34:26Z

wip

commit ec7caecaace4bd1222abb4b1791b85fc9bda339e
Author: Pavel Tupitsyn 
Date:   2015-10-28T16:34:51Z

wip

commit c46399e14e6cb39175a3d07451fed20c01ee93b8
Author: Pavel Tupitsyn 
Date:   

[jira] [Commented] (IGNITE-1770) Portables: implement constant-time field lookup.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980642#comment-14980642
 ] 

ASF GitHub Bot commented on IGNITE-1770:


Github user ptupitsyn closed the pull request at:

https://github.com/apache/ignite/pull/182


> Portables: implement constant-time field lookup.
> 
>
> Key: IGNITE-1770
> URL: https://issues.apache.org/jira/browse/IGNITE-1770
> Project: Ignite
>  Issue Type: Task
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Blocker
> Fix For: 1.5
>
>
> See 
> https://cwiki.apache.org/confluence/display/IGNITE/Portable+object+constant-time+field+lookup



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1770) Portables: implement constant-time field lookup.

[Vladimir Ozerov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980678#comment-14980678
 ] 

Vladimir Ozerov commented on IGNITE-1770:
-

Java and .Net are ready.

> Portables: implement constant-time field lookup.
> 
>
> Key: IGNITE-1770
> URL: https://issues.apache.org/jira/browse/IGNITE-1770
> Project: Ignite
>  Issue Type: Task
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Blocker
> Fix For: 1.5
>
>
> See 
> https://cwiki.apache.org/confluence/display/IGNITE/Portable+object+constant-time+field+lookup



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1812) Create a Maven BOM for Apache Ignite

[JIRA]

Raúl Kripalani created IGNITE-1812:
--

 Summary: Create a Maven BOM for Apache Ignite
 Key: IGNITE-1812
 URL: https://issues.apache.org/jira/browse/IGNITE-1812
 Project: Ignite
  Issue Type: New Feature
Reporter: Raúl Kripalani
Assignee: Raúl Kripalani
Priority: Minor


In Maven, a 
[BOM|https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies]
 == "Bill of Materials". 

BOMs provide an improved, short and safe way for users to import modules 
without having to reference the Ignite version over and over again.

It allows the user to add all of Ignite's modules into their 
{{}} section within a single dependency import. They 
are consequently able to reference modules without specifying the Ignite 
version:

{code}

org.apache.ignite
ignite-indexing

{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-1697) IGFS: implement reliable Igfs failover logic

[Ivan Veselovsky (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980936#comment-14980936
 ] 

Ivan Veselovsky edited comment on IGNITE-1697 at 10/29/15 6:17 PM:
---

All pending changes are in prq 
https://github.com/apache/ignite/pull/184


was (Author: iveselovskiy):
All changes the changes in prq 
https://github.com/apache/ignite/pull/184

> IGFS: implement reliable Igfs failover logic 
> -
>
> Key: IGNITE-1697
> URL: https://issues.apache.org/jira/browse/IGNITE-1697
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ivan Veselovsky
>Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> Problems to solve:
> 1) currently a write lock for a file may stay taken forever if a node have 
> taken the lock and then crashed.
> 2) Currently the blocks of file content are written not just as 
> dataCache.put() operations , but sent using ad-hoc async messages. This was 
> done earlier to improve performance. But in order to implement reliable 
> failover we need to get rid of that and use simple put() or asyncPut() cache 
> operations.
> Solution plan:
> 1) use async put to write file data blocks.
> 2) do writing using scheme "lock" -> "reserve space" -> "write" -> "commit" 
> -> "release lock".
> 3) The id of the node that locked a file should be readable from the lock id.
> 4) Upon taking a file lock the following procedure should be performed: 
> if file is locked, take the node Id of the node that locked the file. After 
> that ask DiscoveryProcessor if this node is alive. If it is not (node has 
> left topology), perform cleanup procedure: delete all the data blocks of the 
> reserved data range, then delete the lock.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1380) Random eviction policy for near cache works incorrectly

[Andrey Gura (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980935#comment-14980935
 ] 

Andrey Gura commented on IGNITE-1380:
-

There ar two problems in case of near cache:

# {{GridNearCacheAdapter.randomEntry()}} method returns 
{{GridDhtAtomicCacheEntry}} instance instead of {{GridNearCacheEntry}}.
# {{RandomEvictionPolicy}} always use 
{{IgniteCache.localSize(CachePeekMode.ONHEAP)}} call for size calculation.

PR cretaed: https://github.com/apache/ignite/pull/185

Waiting for TC.

> Random eviction policy for near cache works incorrectly
> ---
>
> Key: IGNITE-1380
> URL: https://issues.apache.org/jira/browse/IGNITE-1380
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Andrey Gura
> Fix For: 1.5
>
>
> Start two server nodes with cache with near cache with configuration below 
> (node with load generation and one more data node).
> Put 2000 keys (from 1 to 2000), read 200 key (from 1 to 200) using first 
> node. 
> {code}
> 
> 
> 
> 
> 
>  class="org.apache.ignite.configuration.NearCacheConfiguration">
> 
>  class="org.apache.ignite.cache.eviction.random.RandomEvictionPolicy">
> 
> 
> 
> 
> 
> 
> {code}
> Near cache contains more keys then I set in configuration (maxSize=100).
> Others eviction policies are  works correctly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1813) Need to add metrics for data structures

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-1813:
---

 Summary: Need to add metrics for data structures
 Key: IGNITE-1813
 URL: https://issues.apache.org/jira/browse/IGNITE-1813
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Valentin Kulichenko


All data structures (queues, sets, atomics, etc.) are based on internal caches, 
therefore there is no way to get metrics for this caches.

We should create an interface that will contain metrics suitable for data 
structures and add {{metrics()}} method to all data structures that will return 
the instance of this interface for a particular data structure.

Here is the corresponding user@ thread: 
http://apache-ignite-users.70518.x6.nabble.com/Queue-stats-td1727.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1758) Clients don't survive during massive servers shutdown

[Semen Boikov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979980#comment-14979980
 ] 

Semen Boikov commented on IGNITE-1758:
--

So far found several issue in logic handling client reconnect to cluster:
- some messages were not added to EnsuredMessageHistory (i.e. NodeAddedMessage 
created during processJoinRequestMessage)
- on client side BufferedInputStream was created two times for the same socket 
(in Reconnector and then in SocketReader), I suspect some messages could be not 
read in this case
- TcpDiscoveryNodeAddedMessage sent to joinning client node should contain 
'topology' collection with all nodes joined before, but 'topology' was 
initialized at the moment when this message was sent using nodes at current 
moment, so topology could contain not all needed nodes if it was sent during 
client reconnect

> Clients don't survive during massive servers shutdown
> -
>
> Key: IGNITE-1758
> URL: https://issues.apache.org/jira/browse/IGNITE-1758
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: 1.5
>
> Attachments: ignite-1758-test.patch
>
>
> There is a real world use case.
> Start sensible amount of servers and clients.
> Perform cache operations under a transaction.
> Stop a half of the servers. Clients must survive and keep execution their 
> transactions.
> Did the following test:
> - Started 14 servers and 14 clients;
> - Clients execute transactional put operations;
> - Stopped 7 servers.
> Getting different assertions on clients side.
> {noformat}
> [15:47:33,401][ERROR][tcp-client-disco-msg-worker-#521%internal.IgniteClientReconnectCacheMultiThreadedTest18][TcpDiscoverySpi]
>  Runtime error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-client-disco-msg-worker-#521%internal.IgniteClientReconnectCacheMultiThreadedTest18]
> java.lang.AssertionError: lastVer=29, newVer=32, locNode=TcpDiscoveryNode 
> [id=80f14def-9d49-43a0-96bc-6b83aedb3008, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:0], discPort=0, order=26, intOrder=0, 
> lastExchangeTime=1445428036418, loc=true, ver=1.4.1#19700101-sha1:, 
> isClient=true], msg=TcpDiscoveryNodeFailedMessage 
> [failedNodeId=3020dc65-ed3e-426f-8784-5bb766961003, order=4, warning=null, 
> super=TcpDiscoveryAbstractMessage 
> [sndNodeId=10c5cfe9-df07-4dfe-a5c0-460087aa9001, 
> id=eed3e3a8051-008a978d-28cc-4f0c-8728-4a815f858000, 
> verifierNodeId=800cf998-828e-4f56-af6a-c2760c5ed008, topVer=32, pendingIdx=0, 
> isClient=false]]
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl.updateTopologyHistory(ClientImpl.java:720)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl.access$2700(ClientImpl.java:118)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeFailedMessage(ClientImpl.java:1812)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1543)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1467)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat}
> {noformat}
> java.lang.AssertionError: Missed message future [rcvCnt=141, acked=0, 
> desc=GridNioRecoveryDescriptor [acked=0, resendCnt=0, rcvCnt=0, 
> reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode 
> [id=6090f64b-e019-440b-9d0e-c3642bd3a006, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47503], discPort=47503, order=3, intOrder=3, 
> lastExchangeTime=1445428027468, loc=false, ver=1.4.1#19700101-sha1:, 
> isClient=false], connected=false, connectCnt=1, queueLimit=5120]]
>   at 
> org.apache.ignite.internal.util.nio.GridNioRecoveryDescriptor.ackReceived(GridNioRecoveryDescriptor.java:181)
>   at 
> org.apache.ignite.internal.util.nio.GridNioRecoveryDescriptor.onHandshake(GridNioRecoveryDescriptor.java:251)
>   at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2331)
>   at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2084)
>   at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:1978)
>   at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1914)
>   at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1880)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1066)
>   at 
> 

[jira] [Updated] (IGNITE-1808) Wrong Jetty's thread pool size settings

[Roman Shtykh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roman Shtykh updated IGNITE-1808:
-
Attachment: ignite-1808.patch

> Wrong Jetty's thread pool size settings
> ---
>
> Key: IGNITE-1808
> URL: https://issues.apache.org/jira/browse/IGNITE-1808
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>Priority: Minor
> Attachments: ignite-1808.patch
>
>
> {code}
> new QueuedThreadPool(20, 200)
> {code}
> in GridJettyRestProtocol should be
> {code}
> new QueuedThreadPool(200, 20)
> {code}
> since QueuedThreadPool(int maxThreads, int minThreads)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1807) Visor console should write logs to file in quite mode

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-1807:


 Summary: Visor console should write logs to file in quite mode
 Key: IGNITE-1807
 URL: https://issues.apache.org/jira/browse/IGNITE-1807
 Project: Ignite
  Issue Type: Bug
  Components: UI
Affects Versions: ignite-1.4
Reporter: Alexey Kuznetsov
 Fix For: 1.5






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-647) org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs

[Anton Vinogradov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980025#comment-14980025
 ] 

Anton Vinogradov commented on IGNITE-647:
-

Same hangs at IgniteDynamicCacheStartNoExchangeTimeoutTest

> org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs
> --
>
> Key: IGNITE-647
> URL: https://issues.apache.org/jira/browse/IGNITE-647
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Yakov Zhdanov
>Assignee: Alexey Goncharuk
>Priority: Blocker
>  Labels: Muted_test
> Attachments: FairAffinityDynamicCacheSelfTest.testStartStopCache.txt, 
> threaddump.txt
>
>
> 1-2 runs out of ~10 local runs hanged for me



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-647) org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs

[Semen Boikov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979907#comment-14979907
 ] 

Semen Boikov commented on IGNITE-647:
-

Looks like 
CrossCacheTxRandomOperationsTest.testCrossCacheTxOperationsFairAffinity hangs 
because of this issue.

> org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs
> --
>
> Key: IGNITE-647
> URL: https://issues.apache.org/jira/browse/IGNITE-647
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Yakov Zhdanov
>Assignee: Alexey Goncharuk
>Priority: Blocker
>  Labels: Muted_test
> Attachments: FairAffinityDynamicCacheSelfTest.testStartStopCache.txt, 
> threaddump.txt
>
>
> 1-2 runs out of ~10 local runs hanged for me



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1168) REST API: type metadata for cache

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980028#comment-14980028
 ] 

ASF GitHub Bot commented on IGNITE-1168:


GitHub user nva opened a pull request:

https://github.com/apache/ignite/pull/181

IGNITE-1168 REST metadata command - return metadata in all caches.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nva/ignite ignite-1168

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/181.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 #181


commit abfb73ff0287b79a13c397bed7c19c23b745dee6
Author: Andrey 
Date:   2015-10-29T08:00:15Z

ignite-1168 REST metadata command change - return metadata in all caches.




> REST API: type metadata for cache
> -
>
> Key: IGNITE-1168
> URL: https://issues.apache.org/jira/browse/IGNITE-1168
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: 1.5
>
> Attachments: IGNITE-1168.patch, master_a1e5cc5_ignite-1168.patch
>
>
> Apache Ignite supports query so will be useful to implement command that 
> return type metadata for display in SQL query editor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-1687) Add possibility to insert fully qualified name to the query from metadata popup

[Andrey Novikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov reassigned IGNITE-1687:
--

Assignee: Andrey Novikov

> Add possibility to insert fully qualified name to the query from metadata 
> popup 
> 
>
> Key: IGNITE-1687
> URL: https://issues.apache.org/jira/browse/IGNITE-1687
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
>
> Such possibility will help user to construct cross-cache queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-1168) REST API: type metadata for cache

[Andrey Novikov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980272#comment-14980272
 ] 

Andrey Novikov edited comment on IGNITE-1168 at 10/29/15 11:13 AM:
---

Return metadata for all caches in one request. Semen, please review.


was (Author: anovikov):
Return metadata for all caches in one request.

> REST API: type metadata for cache
> -
>
> Key: IGNITE-1168
> URL: https://issues.apache.org/jira/browse/IGNITE-1168
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Semen Boikov
> Fix For: 1.5
>
> Attachments: IGNITE-1168.patch, master_a1e5cc5_ignite-1168.patch
>
>
> Apache Ignite supports query so will be useful to implement command that 
> return type metadata for display in SQL query editor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-1168) REST API: type metadata for cache

[Andrey Novikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov resolved IGNITE-1168.

Resolution: Fixed
  Assignee: Semen Boikov  (was: Andrey Novikov)

Return metadata for all caches in one request.

> REST API: type metadata for cache
> -
>
> Key: IGNITE-1168
> URL: https://issues.apache.org/jira/browse/IGNITE-1168
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Semen Boikov
> Fix For: 1.5
>
> Attachments: IGNITE-1168.patch, master_a1e5cc5_ignite-1168.patch
>
>
> Apache Ignite supports query so will be useful to implement command that 
> return type metadata for display in SQL query editor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)