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

2015-10-02 Thread 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: ignite-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-1610) CPP: Implement reader and writer for iterators

2015-10-02 Thread Igor Sapego (JIRA) 
Igor Sapego created IGNITE-1610:
---

 Summary: CPP: Implement reader and writer for iterators
 Key: IGNITE-1610
 URL: https://issues.apache.org/jira/browse/IGNITE-1610
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: 1.1.4
Reporter: Igor Sapego
Assignee: Igor Sapego


Need to try and implement portable writer and portable reader that could work 
with iterators.



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

[jira] [Commented] (IGNITE-801) [Test] GridCacheReplicatedDataStructuresFailoverSelfTest hangs on TC

2015-10-02 Thread Denis Magda (JIRA) 

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

Denis Magda commented on IGNITE-801:


Fixed two more tests:
- countdown latch impl executed {{count()}} as a part of a transaction. That 
was redundant;
- atomic reference impl didn't process {{ClusterTopologyCheckedException}};
- updated {GridCacheUtils.retryTopologySafe}} method

There is one failing test is left that checks {{IgniteQueue}}. The reason of 
failure is unclear, have to keep debugging.

> [Test] GridCacheReplicatedDataStructuresFailoverSelfTest hangs on TC
> 
>
> Key: IGNITE-801
> URL: https://issues.apache.org/jira/browse/IGNITE-801
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Artem Shutak
>Assignee: Denis Magda
>  Labels: Muted_test
> Fix For: ignite-1.5
>
> Attachments: ignite-801.patch
>
>
> See GG-5306
> http://94.72.60.102/viewLog.html?buildId=113217=bt6=buildResultsDiv
> {noformat}
> 2013-05-31 10:39:07
> Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode):
> "Attach Listener" daemon prio=10 tid=0x03a94800 nid=0x648 waiting on 
> condition [0x]
>java.lang.Thread.State: RUNNABLE
> "tcp-disco-sock-reader-#2408%a940475f-1965-484a-8a43-0a1fcc3bf292" prio=10 
> tid=0x7f06f8b1a000 nid=0x42d runnable [0x7f0702d84000]
>java.lang.Thread.State: RUNNABLE
>   at java.net.SocketInputStream.socketRead0(Native Method)
>   at java.net.SocketInputStream.read(SocketInputStream.java:150)
>   at java.net.SocketInputStream.read(SocketInputStream.java:121)
>   at 
> org.gridgain.grid.marshaller.jdk.GridJdkMarshallerInputStreamWrapper.read(GridJdkMarshallerInputStreamWrapper.java:47)
>   at 
> java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2308)
>   at 
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2321)
>   at 
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2792)
>   at 
> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:799)
>   at java.io.ObjectInputStream.init(ObjectInputStream.java:299)
>   at 
> org.gridgain.grid.marshaller.jdk.GridJdkMarshallerObjectInputStream.init(GridJdkMarshallerObjectInputStream.java:30)
>   at 
> org.gridgain.grid.marshaller.jdk.GridJdkMarshaller.unmarshal(GridJdkMarshaller.java:115)
>   at 
> org.gridgain.grid.spi.discovery.tcp.GridTcpDiscoverySpi$SocketReader.body(GridTcpDiscoverySpi.java:3985)
>   at org.gridgain.grid.spi.GridSpiThread.run(GridSpiThread.java:56)
> "Thread-1905" prio=10 tid=0x7f06f8268000 nid=0x428 waiting on condition 
> [0x7f06e1f29000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
>   at java.lang.Thread.sleep(Native Method)
>   at 
> org.gridgain.grid.kernal.GridKernalGatewayImpl.writeLock(GridKernalGatewayImpl.java:89)
>   at org.gridgain.grid.kernal.GridKernal.stop0(GridKernal.java:1629)
>   - locked 0x00078a53c600 (a 
> org.gridgain.grid.util.GridBreaker)
>   at org.gridgain.grid.kernal.GridKernal.stop(GridKernal.java:1605)
>   at 
> org.gridgain.grid.GridFactory$GridNamedInstance.stop0(GridFactory.java:2295)
>   - locked 0x00078a473b60 (a 
> org.gridgain.grid.GridFactory$GridNamedInstance)
>   at 
> org.gridgain.grid.GridFactory$GridNamedInstance.stop(GridFactory.java:2256)
>   at 
> org.gridgain.grid.GridFactory$GridNamedInstance$2.run(GridFactory.java:2223)
> "Thread-1911" prio=10 tid=0x026b1000 nid=0x420 waiting on condition 
> [0x7f06e6af4000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
>   at java.lang.Thread.sleep(Native Method)
>   at 
> org.gridgain.grid.kernal.GridKernalGatewayImpl.writeLock(GridKernalGatewayImpl.java:89)
>   at org.gridgain.grid.kernal.GridKernal.stop0(GridKernal.java:1629)
>   - locked 0x000789b76068 (a 
> org.gridgain.grid.util.GridBreaker)
>   at org.gridgain.grid.kernal.GridKernal.stop(GridKernal.java:1605)
>   at 
> org.gridgain.grid.GridFactory$GridNamedInstance.stop0(GridFactory.java:2295)
>   - locked 0x00078a4738f8 (a 
> org.gridgain.grid.GridFactory$GridNamedInstance)
>   at 
> org.gridgain.grid.GridFactory$GridNamedInstance.stop(GridFactory.java:2256)
>   at 
> org.gridgain.grid.GridFactory$GridNamedInstance$2.run(GridFactory.java:2223)
> "SIGTERM handler" daemon prio=10 tid=0x01ec2800 nid=0x41e in 
> Object.wait() [0x7f06e8316000]
>java.lang.Thread.State: WAITING (on object monitor)
>   at java.lang.Object.wait(Native Method)
>   at java.lang.Thread.join(Thread.java:1258)
>   - locked 0x00078a473948 (a 
> org.gridgain.grid.GridFactory$GridNamedInstance$2)
>   at

[jira] [Updated] (IGNITE-1480) Platform .Net: IClusterNode.IsClient

2015-10-02 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-1480:

Assignee: Pavel  Tupitsyn  (was: Vladimir Ozerov)

> Platform .Net: IClusterNode.IsClient
> 
>
> Key: IGNITE-1480
> URL: https://issues.apache.org/jira/browse/IGNITE-1480
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>
> Ignite in Java has ClusterNode.isClient, need to implement in .Net.



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

[jira] [Commented] (IGNITE-1577) IlligateStateException when removing index during stop

2015-10-02 Thread Sergi Vladykin (JIRA) 

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

Sergi Vladykin commented on IGNITE-1577:


As I see from the stack trace the error happens when TtlManager tries to evict 
expired cache entry, so it is definitely depends on moment in time but does not 
depend on Java heap size at all.

AFAIK we have lots of places where we throw IllegalStateException when node 
stops. And as far as I understand it is just a cosmetic issue because after 
that everything works fine. Thus I think we need to strategically decide how to 
handle all these situations. 


> IlligateStateException when removing index during stop
> --
>
> Key: IGNITE-1577
> URL: https://issues.apache.org/jira/browse/IGNITE-1577
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Dmitriy Setrakyan
>Assignee: Sergi Vladykin
>Priority: Critical
> Fix For: ignite-1.5
>
>
> I ran string example which queries the streamed words onto 2 data nodes (2GB 
> each, started with ExampleNodeStartup class), and while running, killed 1 
> node. I also had 1 StreamWords and 1 QueryWords process.
> Got this error on the stopping node.
> {code}
> java.lang.IllegalStateException: Failed to remove from index (grid is 
> stopping).
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:837)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:433)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.clearIndex(GridCacheMapEntry.java:3553)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onTtlExpired(GridCacheMapEntry.java:3374)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:117)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager$CleanupWorker.body(GridCacheTtlManager.java:136)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Closed] (IGNITE-1570) Move .Net local benchmarks project to Ignite.

2015-10-02 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov closed IGNITE-1570.
---

> Move .Net local benchmarks project to Ignite.
> -
>
> Key: IGNITE-1570
> URL: https://issues.apache.org/jira/browse/IGNITE-1570
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: ignite-1.5
>
>




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

[jira] [Closed] (IGNITE-1588) CPP: Fix constructor of the IgniteJvmOption class

2015-10-02 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov closed IGNITE-1588.
---

> CPP: Fix constructor of the IgniteJvmOption class
> -
>
> Key: IGNITE-1588
> URL: https://issues.apache.org/jira/browse/IGNITE-1588
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
>
> Current implementation of the IgniteJvmOption class takes {{char*}} as 
> argument, when it should take {{const char*}} and copy it.



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

[jira] [Closed] (IGNITE-1586) CPP: Add isValid() method to all proxy-like classes

2015-10-02 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov closed IGNITE-1586.
---

> CPP: Add isValid() method to all proxy-like classes
> ---
>
> Key: IGNITE-1586
> URL: https://issues.apache.org/jira/browse/IGNITE-1586
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
>
> Need to add isValid() methods to proxy-like classes so users can check if 
> they can use an instance.



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

[jira] [Comment Edited] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

2015-10-02 Thread Gianfranco Murador (JIRA) 

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

Gianfranco Murador edited comment on IGNITE-429 at 10/2/15 9:35 AM:


Chan, 
 As the ticket is assigned to you, you can make any changes in your own branch 
on your fork and make a pull request , you can start with all changes that you 
see in my fork. 

Anton,  thanks for the tips. 
Regards, Gianfranco 




was (Author: glutters):
Chan, 
 As the ticket is assigned to you, you can make any changes in your own branch 
on your fork and make a pull request , you can start with all the changes that 
you see in my fork. 

Anton,  thanks for the tips. 
Regards, Gianfranco 



> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm 
> and stream them into Ignite caches. 
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable 
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.



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

[jira] [Assigned] (IGNITE-1562) .Net: Remove "Generic" word from "WriteGenericCollection" and "WriteGenericDictionary".

2015-10-02 Thread Pavel Tupitsyn (JIRA) 

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

Pavel  Tupitsyn reassigned IGNITE-1562:
---

Assignee: Pavel  Tupitsyn

> .Net: Remove "Generic" word from "WriteGenericCollection" and 
> "WriteGenericDictionary".
> ---
>
> Key: IGNITE-1562
> URL: https://issues.apache.org/jira/browse/IGNITE-1562
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Normally users will use these methods instead of non-generic. Lets make their 
> names as simple as possible.



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

[jira] [Commented] (IGNITE-1571) .Net: Improve Guid and DateTime reader/writer interface.

2015-10-02 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-1571:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1571 .Net: Improve Guid and DateTime reader/writer interface.



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

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

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

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


commit 6917ca308dacf7133ebbe3a39c2352f3c1413d9e
Author: ptupitsyn 
Date:   2015-10-01T16:11:30Z

IGNITE-1571 .Net: Improve Guid and DateTime reader/writer interface.

commit bf50af081c6a1aeaa9fac2bf71b6e669138b58e2
Author: ptupitsyn 
Date:   2015-10-01T16:18:58Z

Fix generic call

commit 289d26f89601dbfbb06872dee018999e068b3d73
Author: ptupitsyn 
Date:   2015-10-01T16:45:35Z

wip

commit 2a1e7d26f711818ea6319d6b9ee200ed26c7920d
Author: ptupitsyn 
Date:   2015-10-01T17:08:29Z

wip

commit 0599b8f0fecdc871c7de83d7995ee1ed66e07a83
Author: ptupitsyn 
Date:   2015-10-02T11:54:59Z

Merge remote-tracking branch 'remotes/upstream/ignite-1282' into ignite-1571

commit a8b1be32b4277159599dfc824f16723d69b680cf
Author: ptupitsyn 
Date:   2015-10-02T12:02:32Z

Merge remote-tracking branch 'remotes/upstream/ignite-1282' into ignite-1571

commit 191155cf2e26f8cd793acd5bf9aac9fdf94aad95
Author: ptupitsyn 
Date:   2015-10-02T12:05:07Z

wip remove array non-nullable methods

commit a54e681d215fd07d65a1772ea565e0df5f227c51
Author: ptupitsyn 
Date:   2015-10-02T12:39:27Z

Nullable renamings

commit 59789655a32357dba5282f3f8ccbc8e7e0d48641
Author: ptupitsyn 
Date:   2015-10-02T12:41:19Z

wip

commit 6a773fda64ea4f93cfd71859f5d292b40f745177
Author: ptupitsyn 
Date:   2015-10-02T12:53:02Z

Non-nullable Guid/DateTime done

commit 4625ae346eb3caef44312d1bb7b5b500fca752cf
Author: ptupitsyn 
Date:   2015-10-02T12:55:55Z

wip




> .Net: Improve Guid and DateTime reader/writer interface.
> 
>
> Key: IGNITE-1571
> URL: https://issues.apache.org/jira/browse/IGNITE-1571
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Currently we force user to write Guid and DateTime as nullables. We do this 
> to be more compatible with Java.
> But user is more likely to operate on plain types: Guid, Guid[], DateTime, 
> DateTime[]. 
> We need to add these methods to API, and rename existing ones to 
> "ReadNullableDateTime", etc..
> Note that while trivial to on writer side, it will be harder to implement for 
> readers. Currently we lookup by type ID, which will be equal for the type and 
> it's nullable counterpart. For this reason we probably must lookup by type ID 
> + type or simply by type.



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

[jira] [Updated] (IGNITE-469) when running selected tests from a test class #afterTestsStopped() is not invoked.

2015-10-02 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-469:
---
Assignee: (was: Vladimir Ozerov)

> when running selected tests from a test class #afterTestsStopped() is not 
> invoked.
> --
>
> Key: IGNITE-469
> URL: https://issues.apache.org/jira/browse/IGNITE-469
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: sprint-1
>Reporter: Ivan Veselovsky
> Fix For: ignite-1.5
>
> Attachments: IGNITE-469--a.patch
>
>
> JUnit test infrastructure in Ignite has custom test engine that invokes 
> #afterTestsStopped() when 
> org.apache.ignite.testframework.junits.GridAbstractTest#isLastTest() == true: 
> return cntrs.getStopped() == cntrs.getNumberOfTests();
> , where getNumberOfTests() is calculated by counting all the public class 
> methods starting with "test".
> When we execute selected tests (I guess, does not matter from maven or from 
> IDE), cntrs.getStopped() is always less than the total number of tests in the 
> test class, so #afterTestsStopped() is not executed. 
> This leaves unfinished processes like Ignite nodes that afterwards affect the 
> behavior of other tests.



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

[jira] [Commented] (IGNITE-1572) .Net: Check if we can get rid of "WritePortableOrSerializable" method.

2015-10-02 Thread Pavel Tupitsyn (JIRA) 

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

Pavel  Tupitsyn commented on IGNITE-1572:
-

Good catch, I have remove these wrappers, since we have 
SerializableObjectHolder in Writer/Reader.
However, one test (TestPortableObjectInTask) has failed. We have 2 issues:
* .Net writes user objects as FullObj (103) or PortObj (27), but Java always 
returns them as PortObj (27), so we loose that information. Removed wrappers 
indirectly solved that problem.
* In KeepPortable mode with Serializable object, we return PortableUserObject 
[SerializableObjectHolder] to the user, which is a bug, causes by the first 
issue.

> .Net: Check if we can get rid of "WritePortableOrSerializable" method.
> --
>
> Key: IGNITE-1572
> URL: https://issues.apache.org/jira/browse/IGNITE-1572
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: ignite-1.5
>
>
> We have lots of places where "WritePortableOrSerializable" routine is 
> invoked. It is not clear why do we need it provided that we already handle 
> [Serializable] classes properly. 
> Looks like we are able to get rid of it safely, aren't we? Need to 
> double-check.



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

[jira] [Comment Edited] (IGNITE-1589) Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails

2015-10-02 Thread Pavel Tupitsyn (JIRA) 

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

Pavel  Tupitsyn edited comment on IGNITE-1589 at 10/2/15 8:38 AM:
--

1,2) Both of these changes are made to make PlatformMemoryStream.Dispose work 
when used with PlatformRawMemory. But since we have IGNITE-1598 to fix Dispose 
usage, I have reverted PlatformRawMemory changes for now.


was (Author: ptupitsyn):
1,2) Both of these changes are made to make PlatformMemoryStream.Dispose work 
when used with PlatformRawMemory. Otherwise we break Liskov Substitution 
Principle, I think.

> Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails
> ---
>
> Key: IGNITE-1589
> URL: https://issues.apache.org/jira/browse/IGNITE-1589
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>




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

[jira] [Closed] (IGNITE-1589) Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails

2015-10-02 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov closed IGNITE-1589.
---

> Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails
> ---
>
> Key: IGNITE-1589
> URL: https://issues.apache.org/jira/browse/IGNITE-1589
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Vladimir Ozerov
> Fix For: ignite-1.5
>
>




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

[jira] [Resolved] (IGNITE-1534) Failed to map keys for cache (all partition nodes left the grid).

2015-10-02 Thread Semen Boikov (JIRA) 

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

Semen Boikov resolved IGNITE-1534.
--
Resolution: Fixed

Fix merged into master (commit 7b54cbd).

> Failed to map keys for cache (all partition nodes left the grid).
> -
>
> Key: IGNITE-1534
> URL: https://issues.apache.org/jira/browse/IGNITE-1534
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Andrey Gura
>Assignee: Semen Boikov
> Fix For: ignite-1.5
>
>
> During testing changes related with IGNITE-1171 the following problem was 
> found:
> {panel}
> Unhandled exception 
> org.apache.ignite.cache.CacheServerNotFoundException: Failed to map keys for 
> cache (all partition nodes left the grid).
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1612)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1744)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.getAndPut(IgniteCacheProxy.java:1043)
>   at io.vertx.spi.cluster.ignite.impl.MapImpl.put(MapImpl.java:85)
>   at io.vertx.core.impl.HAManager.(HAManager.java:147)
>   at io.vertx.core.impl.VertxImpl.lambda$null$143(VertxImpl.java:156)
>   at io.vertx.core.impl.VertxImpl$$Lambda$35/2107573573.handle(Unknown 
> Source)
>   at 
> io.vertx.core.net.impl.NetServerImpl.lambda$null$34(NetServerImpl.java:252)
>   at 
> io.vertx.core.net.impl.NetServerImpl$$Lambda$39/1662210125.handle(Unknown 
> Source)
>   at 
> io.vertx.core.impl.ContextImpl.lambda$wrapTask$20(ContextImpl.java:324)
>   at io.vertx.core.impl.ContextImpl$$Lambda$31/1504729381.run(Unknown 
> Source)
>   at 
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
>   at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
>   at 
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException: 
> Failed to map keys for cache (all partition nodes left the grid).
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:808)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:422)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$100(GridNearAtomicUpdateFuture.java:73)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$1$1.run(GridNearAtomicUpdateFuture.java:406)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6427)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:788)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   ... 1 more
> {panel}
> This exception occures on topology from 3 nodes that start dynamic cache with 
> the same configuration on all nodes and performs {{put}} operation. All 3 
> nodes are alive.
> The problem reproduces periodically.



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

[jira] [Closed] (IGNITE-1135) GridPartitionedGetFuture assertion error

2015-10-02 Thread Semen Boikov (JIRA) 

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

Semen Boikov closed IGNITE-1135.

Assignee: (was: Semen Boikov)

> GridPartitionedGetFuture assertion error
> 
>
> Key: IGNITE-1135
> URL: https://issues.apache.org/jira/browse/IGNITE-1135
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
> Fix For: ignite-1.5
>
>
> During working on IGNITE-1079 ticket the following problem was found:
> {noformat}
> Failed processing message [senderId=7a07cc81-11e5-42f2-8ffc-184c6c377fc5, 
> msg=GridNearGetResponse 
> [futId=575ef41be41-1a1482a7-e1b9-48c8-9cb7-382fe83792df, 
> miniId=675ef41be41-1a1482a7-e1b9-48c8-9cb7-382fe83792df, ver=GridCacheVersion 
> [topVer=48973890, nodeOrderDrId=3, globalTime=1437493884602, 
> order=1437493880034], entries=[GridCacheEntryInfo [key=KeyCacheObjectImpl 
> [val=7a07cc81-11e5-42f2-8ffc-184c6c377fc5, hasValBytes=true], 
> cacheId=414885281, val=null, ttl=0, expireTime=0, ver=GridCacheVersion 
> [topVer=48973890, nodeOrderDrId=7, globalTime=1437493884824, 
> order=1437493880064], isNew=false, deleted=false]], invalidParts=[], 
> topVer=AffinityTopologyVersion [topVer=7, minorTopVer=0], err=null]] 
> java.lang.AssertionError
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1811)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.createResultMap(GridPartitionedGetFuture.java:535)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.access$200(GridPartitionedGetFuture.java:45)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture$MiniFuture.onResult(GridPartitionedGetFuture.java:715)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.onResult(GridPartitionedGetFuture.java:234)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearGetResponse(GridDhtAtomicCache.java:2345)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1000(GridDhtAtomicCache.java:64)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$9.apply(GridDhtAtomicCache.java:218)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$9.apply(GridDhtAtomicCache.java:216)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:534)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:240)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:158)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:48)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:127)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:761)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:59)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:724)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> In order to reproduce this need to start IgniteComplexHATest (see 
> https://github.com/agura/vertx-ignite) and run tests several times. Test 
> hangs. Thread dump contains thread that hangs on waiting for future 
> completion:
> {noformat}
> "vert.x-worker-thread-3" #4236 prio=5 os_prio=0 tid=0x7f47f43c3800 
> nid=0xc2f waiting on condition [0x7f475ebe6000]
>java.lang.Thread.State: WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   - parking to wait for  <0xcee89bc8> (a 
> org.apache.ignite.internal.util.future.GridFutureAdapter$ChainFuture)
>   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
>   at 
>

[jira] [Commented] (IGNITE-1589) Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails

2015-10-02 Thread Pavel Tupitsyn (JIRA) 

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

Pavel  Tupitsyn commented on IGNITE-1589:
-

1,2) Both of these changes are made to make PlatformMemoryStream.Dispose work 
when used with PlatformRawMemory. Otherwise we break Liskov Substitution 
Principle, I think.

> Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails
> ---
>
> Key: IGNITE-1589
> URL: https://issues.apache.org/jira/browse/IGNITE-1589
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>




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

[jira] [Closed] (IGNITE-1565) Platform .Net: Fix examples

2015-10-02 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov closed IGNITE-1565.
---

> Platform .Net: Fix examples
> ---
>
> Key: IGNITE-1565
> URL: https://issues.apache.org/jira/browse/IGNITE-1565
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Vladimir Ozerov
> Fix For: ignite-1.5
>
>
> Paths have changed in ignite-1282 branch:
> * config paths should be fixed in examples
> * example files paths should be fixed in example tests



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

[jira] [Resolved] (IGNITE-1135) GridPartitionedGetFuture assertion error

2015-10-02 Thread Semen Boikov (JIRA) 

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

Semen Boikov resolved IGNITE-1135.
--
Resolution: Fixed

Fix merged into master (commit 7b54cbd).

> GridPartitionedGetFuture assertion error
> 
>
> Key: IGNITE-1135
> URL: https://issues.apache.org/jira/browse/IGNITE-1135
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Semen Boikov
> Fix For: ignite-1.5
>
>
> During working on IGNITE-1079 ticket the following problem was found:
> {noformat}
> Failed processing message [senderId=7a07cc81-11e5-42f2-8ffc-184c6c377fc5, 
> msg=GridNearGetResponse 
> [futId=575ef41be41-1a1482a7-e1b9-48c8-9cb7-382fe83792df, 
> miniId=675ef41be41-1a1482a7-e1b9-48c8-9cb7-382fe83792df, ver=GridCacheVersion 
> [topVer=48973890, nodeOrderDrId=3, globalTime=1437493884602, 
> order=1437493880034], entries=[GridCacheEntryInfo [key=KeyCacheObjectImpl 
> [val=7a07cc81-11e5-42f2-8ffc-184c6c377fc5, hasValBytes=true], 
> cacheId=414885281, val=null, ttl=0, expireTime=0, ver=GridCacheVersion 
> [topVer=48973890, nodeOrderDrId=7, globalTime=1437493884824, 
> order=1437493880064], isNew=false, deleted=false]], invalidParts=[], 
> topVer=AffinityTopologyVersion [topVer=7, minorTopVer=0], err=null]] 
> java.lang.AssertionError
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1811)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.createResultMap(GridPartitionedGetFuture.java:535)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.access$200(GridPartitionedGetFuture.java:45)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture$MiniFuture.onResult(GridPartitionedGetFuture.java:715)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.onResult(GridPartitionedGetFuture.java:234)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearGetResponse(GridDhtAtomicCache.java:2345)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1000(GridDhtAtomicCache.java:64)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$9.apply(GridDhtAtomicCache.java:218)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$9.apply(GridDhtAtomicCache.java:216)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:534)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:240)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:158)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:48)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:127)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:761)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:59)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:724)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> In order to reproduce this need to start IgniteComplexHATest (see 
> https://github.com/agura/vertx-ignite) and run tests several times. Test 
> hangs. Thread dump contains thread that hangs on waiting for future 
> completion:
> {noformat}
> "vert.x-worker-thread-3" #4236 prio=5 os_prio=0 tid=0x7f47f43c3800 
> nid=0xc2f waiting on condition [0x7f475ebe6000]
>java.lang.Thread.State: WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   - parking to wait for  <0xcee89bc8> (a 
> org.apache.ignite.internal.util.future.GridFutureAdapter$ChainFuture)
>   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
>

[jira] [Closed] (IGNITE-1534) Failed to map keys for cache (all partition nodes left the grid).

2015-10-02 Thread Semen Boikov (JIRA) 

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

Semen Boikov closed IGNITE-1534.

Assignee: (was: Semen Boikov)

> Failed to map keys for cache (all partition nodes left the grid).
> -
>
> Key: IGNITE-1534
> URL: https://issues.apache.org/jira/browse/IGNITE-1534
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Andrey Gura
> Fix For: ignite-1.5
>
>
> During testing changes related with IGNITE-1171 the following problem was 
> found:
> {panel}
> Unhandled exception 
> org.apache.ignite.cache.CacheServerNotFoundException: Failed to map keys for 
> cache (all partition nodes left the grid).
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1612)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1744)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.getAndPut(IgniteCacheProxy.java:1043)
>   at io.vertx.spi.cluster.ignite.impl.MapImpl.put(MapImpl.java:85)
>   at io.vertx.core.impl.HAManager.(HAManager.java:147)
>   at io.vertx.core.impl.VertxImpl.lambda$null$143(VertxImpl.java:156)
>   at io.vertx.core.impl.VertxImpl$$Lambda$35/2107573573.handle(Unknown 
> Source)
>   at 
> io.vertx.core.net.impl.NetServerImpl.lambda$null$34(NetServerImpl.java:252)
>   at 
> io.vertx.core.net.impl.NetServerImpl$$Lambda$39/1662210125.handle(Unknown 
> Source)
>   at 
> io.vertx.core.impl.ContextImpl.lambda$wrapTask$20(ContextImpl.java:324)
>   at io.vertx.core.impl.ContextImpl$$Lambda$31/1504729381.run(Unknown 
> Source)
>   at 
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
>   at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
>   at 
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException: 
> Failed to map keys for cache (all partition nodes left the grid).
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:808)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:422)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$100(GridNearAtomicUpdateFuture.java:73)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$1$1.run(GridNearAtomicUpdateFuture.java:406)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6427)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:788)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   ... 1 more
> {panel}
> This exception occures on topology from 3 nodes that start dynamic cache with 
> the same configuration on all nodes and performs {{put}} operation. All 3 
> nodes are alive.
> The problem reproduces periodically.



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

[jira] [Closed] (IGNITE-1454) CPP: Review all std:: usages in public API.

2015-10-02 Thread Igor Sapego (JIRA) 

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

Igor Sapego closed IGNITE-1454.
---

> CPP: Review all std:: usages in public API.
> ---
>
> Key: IGNITE-1454
> URL: https://issues.apache.org/jira/browse/IGNITE-1454
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
>Priority: Critical
> Fix For: ignite-1.5
>
>
> 1) All std:: usages in public API must reside in headers.
> 2) Consider getting rid of char* and use std::string instead in public API.



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

[jira] [Created] (IGNITE-1612) Do not upload ignite-apache-license-gen to maven

2015-10-02 Thread Anton Vinogradov (JIRA) 
Anton Vinogradov created IGNITE-1612:


 Summary: Do not upload ignite-apache-license-gen to maven
 Key: IGNITE-1612
 URL: https://issues.apache.org/jira/browse/IGNITE-1612
 Project: Ignite
  Issue Type: Test
Affects Versions: ignite-1.5
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov
Priority: Critical
 Fix For: ignite-1.5


Check it possible to restrict uploading to maven repository.



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

[jira] [Commented] (IGNITE-1562) .Net: Remove "Generic" word from "WriteGenericCollection" and "WriteGenericDictionary".

2015-10-02 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-1562:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1562 .Net: Remove "Generic" word from "WriteGenericCollection" and 
"WriteGenericDictionary".



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

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

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

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


commit a2d2f854ba847acf559275ca676d8cb55c8ec76c
Author: ptupitsyn 
Date:   2015-10-02T13:55:46Z

IGNITE-1562 .Net: Remove "Generic" word from "WriteGenericCollection" and 
"WriteGenericDictionary".

commit c9d0d74f0bc232b3417c309c23743345b2f108b5
Author: ptupitsyn 
Date:   2015-10-02T14:10:37Z

Fix reflective routines

commit 5a066cc6187519ec2391725be1153976641db308
Author: ptupitsyn 
Date:   2015-10-02T14:15:26Z

fixing API

commit 6860673890a957e1631bb76977d5f92ae893395a
Author: ptupitsyn 
Date:   2015-10-02T14:21:18Z

Test added

commit f02ed34ec4b55952b0e14367f250fcaeb76e985a
Author: ptupitsyn 
Date:   2015-10-02T15:18:29Z

wip

commit d5fd527bddc7fa934c960b125d7adb3c4df2fc3c
Author: ptupitsyn 
Date:   2015-10-02T15:20:18Z

test fixed




> .Net: Remove "Generic" word from "WriteGenericCollection" and 
> "WriteGenericDictionary".
> ---
>
> Key: IGNITE-1562
> URL: https://issues.apache.org/jira/browse/IGNITE-1562
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Normally users will use these methods instead of non-generic. Lets make their 
> names as simple as possible.



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

[jira] [Created] (IGNITE-1613) Platform .Net: Investigate Guid/DateTime/String interoperability with Java

2015-10-02 Thread Pavel Tupitsyn (JIRA) 
Pavel  Tupitsyn created IGNITE-1613:
---

 Summary: Platform .Net: Investigate Guid/DateTime/String 
interoperability with Java
 Key: IGNITE-1613
 URL: https://issues.apache.org/jira/browse/IGNITE-1613
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: ignite-1.5
Reporter: Pavel  Tupitsyn
Assignee: Pavel  Tupitsyn
 Fix For: ignite-1.5


Currently in .Net we:
* write Guid and DateTime in Java format
* calculate string hash code for field names with Java algorithm on each call

Need to investigate if the following makes sense:
1) In .Net always write Guid and DateTime in native .Net format as fast as 
possible; Make Java understand that format. (Not every Guid written in .Net 
will be read in Java, so we can win time).
2) Cache string hashcodes somehow.



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

[jira] [Commented] (IGNITE-1610) CPP: Implement reader and writer for iterators

2015-10-02 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-1610:


GitHub user isapego opened a pull request:

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

IGNITE-1610: Implemented portable reader and writer for iterators.



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

$ git pull https://github.com/isapego/ignite ignite-1282

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

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


commit cfd3355414b0fe425b8cba5dd032715ae5f6837f
Author: isapego 
Date:   2015-10-02T16:52:26Z

IGNITE-1610: Implemented portable reader and writer for iterators.




> CPP: Implement reader and writer for iterators
> --
>
> Key: IGNITE-1610
> URL: https://issues.apache.org/jira/browse/IGNITE-1610
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
>
> Need to try and implement portable writer and portable reader that could work 
> with iterators.



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

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

2015-10-02 Thread Semen Boikov (JIRA) 

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

Semen Boikov updated IGNITE-1607:
-
Fix Version/s: ignite-1.5

> 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: ignite-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] [Updated] (IGNITE-1122) Cache put hangs if key hashCode is implemented incorrectly

2015-10-02 Thread Valentin Kulichenko (JIRA) 

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

Valentin Kulichenko updated IGNITE-1122:

Priority: Blocker  (was: Major)

> Cache put hangs if key hashCode is implemented incorrectly
> --
>
> Key: IGNITE-1122
> URL: https://issues.apache.org/jira/browse/IGNITE-1122
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
>  Labels: Usability
> Fix For: ignite-1.5
>
>
> If key {{hashCode()}} returns inconsistent result (e.g., user used 
> {{Enum.hashCode()}} in his implementation), the exception below is thrown on 
> a server node and put operation hangs.
> {code}
> SEVERE: Future execution resulted in error: GridEmbeddedFuture 
> [embedded=GridFinishedFuture [resFlag=2, startTime=1436797251202]]
> class org.apache.ignite.IgniteCheckedException: Creating partition which does 
> not belong [part=118, topVer=AffinityTopologyVersion [topVer=5, 
> minorTopVer=4], this.topVer=AffinityTopologyVersion [topVer=5, minorTopVer=4]]
> at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6753)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:124)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils$22.apply(GridCacheUtils.java:851)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils$22.apply(GridCacheUtils.java:848)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:241)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:204)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearLockRequest(GridDhtTransactionalCacheAdapter.java:525)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$000(GridDhtTransactionalCacheAdapter.java:52)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$2.apply(GridDhtTransactionalCacheAdapter.java:96)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$2.apply(GridDhtTransactionalCacheAdapter.java:94)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:532)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:240)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:158)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:48)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:127)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:690)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:58)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:653)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
>  [part=118, msg=Creating partition which does not belong [part=118, 
> topVer=AffinityTopologyVersion [topVer=5, minorTopVer=4], 
> this.topVer=AffinityTopologyVersion [topVer=5, minorTopVer=4]]]
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:527)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:496)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.onAdded(GridDhtPartitionTopologyImpl.java:580)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.(GridDhtCacheEntry.java:79)
> at 
>