[jira] [Commented] (IGNITE-1526) IBM JDK is not fully supported by the platfrom

2015-10-06 Thread Andrey Gura (JIRA) 

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

Andrey Gura commented on IGNITE-1526:
-

The following changes are made:

# Added {{serialVersionUID}}'s to anonymous classes that have usages by 
{{JdkMarshaller}} in discovery. {{serialVersionUID}} generated by {{serialver}} 
tool from Oracle JDK.
# {{OptimizedMarshaller}} doesn't uses default {{serialVersionUID}} generator 
in case of class implements {{Serializable}} interface. In order to provide 
backward compatibility client can use 
{{-Dignite.marsh.optimized.useDefaultSUID=true}} system property.
# Multi JVM test framework refactored in order to work with {{JdkMarshaller}}.
# Marshaller class for "remote" nodes in Multi JVM tests can be configured with 
{{-Dtest.marshaller.class=}} system property. This property 
overrides similar property from {{GridTestProperties}} class.
# JDK for "remote" nodes in Multi JVM tests can be configured with 
{{-Dtest.multijvm.java.home=}} system property.

The following issues are not changed:

# {{PortableMarshaller}} Id mappers: in order to keep backwward compatibility.
# {{ClassesGenerator}}: because it doesn't have information about serializable 
anonymous class usages, so we can't require set SUID for all such classes.

Multi JVM Cache Full API test suite successfully passed with IBM JDK, Oracle 
JDK and mixed JDKs with all marshallers under Windows 7, Windows 8 and Linux.

PR created: https://github.com/apache/ignite/pull/137

Waiting for TC.


> IBM JDK is not fully supported by the platfrom
> --
>
> Key: IGNITE-1526
> URL: https://issues.apache.org/jira/browse/IGNITE-1526
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Andrey Gura
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> There are several issue related to IBM JDK.
> 1) It's not possible to compile the platform using IBM JDK ver 1.7;
> 2) Besides of the fact that two IBM nodes can connect to each other some 
> functionality still doesn't work. As an example 
> {{CacheClientPortablePutGetExample}} fails with the following stack trace
> {noformat}
> [14:38:56,930][ERROR][grid-nio-worker-0-#26%null%][TcpCommunicationSpi] 
> Caught unhandled exception in NIO worker thread (restart the node).
> class org.apache.ignite.IgniteException: Invalid field type: 0
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readRemovedField(PortableDirectMessageReader.java:670)
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readFieldHeader(PortableDirectMessageReader.java:520)
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readMessage(PortableDirectMessageReader.java:339)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:248)
>   at 
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:76)
>   at 
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:103)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>   at 
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:122)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2078)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:172)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:858)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1397)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1339)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1223)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
>   at java.lang.Thread.run(Thread.java:801)
> {noformat}
> 3) Oracle JVM based server node fails to connect to IBM server node producing 
> the stack trace below. Tested with JDK and Portable marshallers.
> {noformat}
> [13:47:33,935][SEVERE][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Failed 
> to
> unmarshal discovery data for component: 0
> class org.apache.ignite.IgniteCheckedException: Failed to deserialize object 
> wit
> h given class loader:

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

2015-10-06 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov commented on IGNITE-1562:
-

I do not understand the problem, honestly. "T[]" is always array irrespectively 
of how we write it: Write(), WriteArray(), WriteCollection or 
WriteCollection. So it should be written in the same way in all cases. The 
same goes for read side.

> .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] [Updated] (IGNITE-1497) Support CPU architectures different from x86/x64

2015-10-06 Thread Denis Magda (JIRA) 

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

Denis Magda updated IGNITE-1497:

Fix Version/s: 1.5

> Support CPU architectures different from x86/x64
> 
>
> Key: IGNITE-1497
> URL: https://issues.apache.org/jira/browse/IGNITE-1497
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
> Fix For: 1.5
>
>
> Ignite widely uses {{Unsafe}} instance throughout the code and the usage is 
> mostly based on the fact that the platform will be running on a little-endian 
> x86/x64 machine.
> As an example the following classes work with short, int, long and other type 
> values bigger than 1 byte in size without taking CPU endiannes into account:
> - {{DirectByteBufferStream}};
> - {{PortableObjectOffheapImpl}};
> - {{GridUnsafeDataOutput}};
> - etc.
> This leads to VM crashes on different CPU architectures:
> - IGNITE-1493;
> - 
> http://stackoverflow.com/questions/32592881/apache-ignite-arm-unsafe-getfloat-segmentation-fault
> All the classes that use {{Unsafe}} in Ignite have to be revisited and 
> modified in a way to support different CPU architectures.



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

[jira] [Updated] (IGNITE-1497) Support CPU architectures different from x86/x64

2015-10-06 Thread Denis Magda (JIRA) 

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

Denis Magda updated IGNITE-1497:

Assignee: Yakov Zhdanov

> Support CPU architectures different from x86/x64
> 
>
> Key: IGNITE-1497
> URL: https://issues.apache.org/jira/browse/IGNITE-1497
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Yakov Zhdanov
> Fix For: 1.5
>
>
> Ignite widely uses {{Unsafe}} instance throughout the code and the usage is 
> mostly based on the fact that the platform will be running on a little-endian 
> x86/x64 machine.
> As an example the following classes work with short, int, long and other type 
> values bigger than 1 byte in size without taking CPU endiannes into account:
> - {{DirectByteBufferStream}};
> - {{PortableObjectOffheapImpl}};
> - {{GridUnsafeDataOutput}};
> - etc.
> This leads to VM crashes on different CPU architectures:
> - IGNITE-1493;
> - 
> http://stackoverflow.com/questions/32592881/apache-ignite-arm-unsafe-getfloat-segmentation-fault
> All the classes that use {{Unsafe}} in Ignite have to be revisited and 
> modified in a way to support different CPU architectures.



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

[jira] [Updated] (IGNITE-1618) [Test failed] TransactionHeuristicException: Failed to locally write to cache

2015-10-06 Thread Anton Vinogradov (JIRA) 

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

Anton Vinogradov updated IGNITE-1618:
-
Issue Type: Test  (was: Bug)

> [Test failed] TransactionHeuristicException: Failed to locally write to cache
> -
>
> Key: IGNITE-1618
> URL: https://issues.apache.org/jira/browse/IGNITE-1618
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.4
>Reporter: Andrey Gura
>Priority: Blocker
>  Labels: Muted_test
> Fix For: ignite-1.5
>
> Attachments: test_deployment.log
>
>
> The following test fail:
>   * {{GridCacheDeploymentOffHeapSelfTest.testDeployment}}
>   * {{GridCacheDeploymentOffHeapSelfTest.testDeployment6}}
>   * {{GridCacheDeploymentOffHeapSelfTest.testDeployment7}}
> The stack trace:
> {noformat}
> org.apache.ignite.IgniteException: class 
> org.apache.ignite.transactions.TransactionHeuristicException: Failed to 
> locally write to cache (all transaction entries will be invalidated, however 
> there was a window when entries for this transaction were visible to others): 
> GridDhtTxLocal [nearNodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
> nearFutId=c5e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearMiniId=d5e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearFinFutId=46e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearFinMiniId=b6e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearXidVer=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
> globalTime=1444061036097, order=1444061035918], super=GridDhtTxLocalAdapter 
> [dhtThreadId=33042, needsCompletedVers=true, nearOnOriginatingNode=true, 
> nearNodes=[], dhtNodes=[100ca1fe-f561-4ddd-b6d9-88d7cf12e001], 
> explicitLock=false, super=IgniteTxLocalAdapter [txMap={IgniteTxKey 
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], cacheId=1]=IgniteTxEntry 
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], cacheId=1, 
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=13, hasValBytes=true], 
> cacheId=1], val=[op=CREATE, val=UserCacheObjectImpl 
> [val=org.apache.ignite.tests.p2p.CacheDeploymentTestValue@6c8704b3, 
> hasValBytes=true]], prevVal=[op=NOOP, val=null], entryProcessorsCol=null, 
> entryProcessorCalcVal=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=[], filtersPassed=false, 
> filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], 
> locPart=GridDhtLocalPartition [id=546, mapPubSize=1, 
> rmvQueue=GridCircularBuffer [sizeMask=127, idxGen=0], state=OWNING, 
> reservations=0, empty=false, createTime=10/05/2015 16:03:56, mapPubSize=1], 
> super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], val=null, 
> startVer=1444061035921, ver=GridCacheVersion [topVer=55541037, 
> nodeOrderDrId=2, globalTime=1444061036098, order=1444061035921], 
> hash=462848615, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
> [locs=[GridCacheMvccCandidate [nodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
> ver=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
> globalTime=1444061036098, order=1444061035920], timeout=0, ts=1444061036094, 
> threadId=33042, id=2544576, topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=0], reentry=null, 
> otherNodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, otherVer=GridCacheVersion 
> [topVer=55541037, nodeOrderDrId=2, globalTime=1444061036097, 
> order=1444061035918], mappedDhtNodes=null, mappedNearNodes=null, 
> ownerVer=null, key=KeyCacheObjectImpl [val=13, hasValBytes=true], 
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0,
>  prevVer=null, nextVer=null]], rmts=null]], flags=0]]], prepared=true, 
> locked=false, nodeId=null, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, xidVer=null]}, completedBase=null, 
> sndTransformedVals=false, super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=55541037, nodeOrderDrId=2, globalTime=1444061036098, 
> order=1444061035920], writeVer=GridCacheVersion [topVer=55541037, 
> nodeOrderDrId=2, globalTime=1444061036098, order=1444061035922], 
> implicit=true, implicitSingle=true, loc=true, threadId=33042, 
> startTime=1444061036094, nodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
> startVer=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
> globalTime=1444061036098, order=1444061035920], endVer=null, 
> isolation=READ_COMMITTED, concurrency=OPTIMISTIC, timeout=0, 
> sysInvalidate=false, sys=false, plc=2, commitVer=null, 
> finalizing=USER_FINISH, preparing=false, invalidParts={}, state=COMMITTING, 
> timedOut=false, topVer=AffinityTopologyVersion [topVer=2, minorTopVer=0], 
> duration=10ms, onePhaseCommit=true], size=1]]]
> at 
>

[jira] [Updated] (IGNITE-1618) [Test failed] TransactionHeuristicException: Failed to locally write to cache

2015-10-06 Thread Anton Vinogradov (JIRA) 

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

Anton Vinogradov updated IGNITE-1618:
-
Fix Version/s: ignite-1.5

> [Test failed] TransactionHeuristicException: Failed to locally write to cache
> -
>
> Key: IGNITE-1618
> URL: https://issues.apache.org/jira/browse/IGNITE-1618
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Andrey Gura
>Priority: Blocker
>  Labels: Muted_test
> Fix For: ignite-1.5
>
> Attachments: test_deployment.log
>
>
> The following test fail:
>   * {{GridCacheDeploymentOffHeapSelfTest.testDeployment}}
>   * {{GridCacheDeploymentOffHeapSelfTest.testDeployment6}}
>   * {{GridCacheDeploymentOffHeapSelfTest.testDeployment7}}
> The stack trace:
> {noformat}
> org.apache.ignite.IgniteException: class 
> org.apache.ignite.transactions.TransactionHeuristicException: Failed to 
> locally write to cache (all transaction entries will be invalidated, however 
> there was a window when entries for this transaction were visible to others): 
> GridDhtTxLocal [nearNodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
> nearFutId=c5e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearMiniId=d5e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearFinFutId=46e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearFinMiniId=b6e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearXidVer=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
> globalTime=1444061036097, order=1444061035918], super=GridDhtTxLocalAdapter 
> [dhtThreadId=33042, needsCompletedVers=true, nearOnOriginatingNode=true, 
> nearNodes=[], dhtNodes=[100ca1fe-f561-4ddd-b6d9-88d7cf12e001], 
> explicitLock=false, super=IgniteTxLocalAdapter [txMap={IgniteTxKey 
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], cacheId=1]=IgniteTxEntry 
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], cacheId=1, 
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=13, hasValBytes=true], 
> cacheId=1], val=[op=CREATE, val=UserCacheObjectImpl 
> [val=org.apache.ignite.tests.p2p.CacheDeploymentTestValue@6c8704b3, 
> hasValBytes=true]], prevVal=[op=NOOP, val=null], entryProcessorsCol=null, 
> entryProcessorCalcVal=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=[], filtersPassed=false, 
> filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], 
> locPart=GridDhtLocalPartition [id=546, mapPubSize=1, 
> rmvQueue=GridCircularBuffer [sizeMask=127, idxGen=0], state=OWNING, 
> reservations=0, empty=false, createTime=10/05/2015 16:03:56, mapPubSize=1], 
> super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], val=null, 
> startVer=1444061035921, ver=GridCacheVersion [topVer=55541037, 
> nodeOrderDrId=2, globalTime=1444061036098, order=1444061035921], 
> hash=462848615, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
> [locs=[GridCacheMvccCandidate [nodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
> ver=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
> globalTime=1444061036098, order=1444061035920], timeout=0, ts=1444061036094, 
> threadId=33042, id=2544576, topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=0], reentry=null, 
> otherNodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, otherVer=GridCacheVersion 
> [topVer=55541037, nodeOrderDrId=2, globalTime=1444061036097, 
> order=1444061035918], mappedDhtNodes=null, mappedNearNodes=null, 
> ownerVer=null, key=KeyCacheObjectImpl [val=13, hasValBytes=true], 
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0,
>  prevVer=null, nextVer=null]], rmts=null]], flags=0]]], prepared=true, 
> locked=false, nodeId=null, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, xidVer=null]}, completedBase=null, 
> sndTransformedVals=false, super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=55541037, nodeOrderDrId=2, globalTime=1444061036098, 
> order=1444061035920], writeVer=GridCacheVersion [topVer=55541037, 
> nodeOrderDrId=2, globalTime=1444061036098, order=1444061035922], 
> implicit=true, implicitSingle=true, loc=true, threadId=33042, 
> startTime=1444061036094, nodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
> startVer=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
> globalTime=1444061036098, order=1444061035920], endVer=null, 
> isolation=READ_COMMITTED, concurrency=OPTIMISTIC, timeout=0, 
> sysInvalidate=false, sys=false, plc=2, commitVer=null, 
> finalizing=USER_FINISH, preparing=false, invalidParts={}, state=COMMITTING, 
> timedOut=false, topVer=AffinityTopologyVersion [topVer=2, minorTopVer=0], 
> duration=10ms, onePhaseCommit=true], size=1]]]
> at 
>

[jira] [Comment Edited] (IGNITE-1257) Implement agent download dialog for page with such functionality

2015-10-06 Thread Vasiliy Sisko (JIRA) 

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

Vasiliy Sisko edited comment on IGNITE-1257 at 10/7/15 1:56 AM:


Implemented waiting of agent starting for metadata load and sql page.


was (Author: vsisko):
Implemented waiting of agent start for metadata load and sql page.

> Implement agent download dialog for page with such functionality
> 
>
> Key: IGNITE-1257
> URL: https://issues.apache.org/jira/browse/IGNITE-1257
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: ignite-1.5
>
>
> * Implement common agent download dialog as template use load from metadata 
> dialog.
> * Generate agent archive with properties file filled by user and server 
> settings (for zero configuration run of agent).
> * Use token instead of login, password in agent configuration.



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

[jira] [Commented] (IGNITE-1594) Home page for web console

2015-10-06 Thread Andrey Novikov (JIRA) 

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

Andrey Novikov commented on IGNITE-1594:


1,2,4 Fixed
3 If we reduce Sign In section then description section also will be reduced 
and will be appear ugly line breaks.

> Home page for web console
> -
>
> Key: IGNITE-1594
> URL: https://issues.apache.org/jira/browse/IGNITE-1594
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.5
>
>
> Home page should look as following:
> # Logo with Apache Ignite Web Console up top
> # Explanation of what web console is immediately below.
> # Login on the left
> # screenshots on the right



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

[jira] [Created] (IGNITE-1621) 'Clone' button doesn't work properly

2015-10-06 Thread Pavel Konstantinov (JIRA) 
Pavel Konstantinov created IGNITE-1621:
--

 Summary: 'Clone' button doesn't work properly
 Key: IGNITE-1621
 URL: https://issues.apache.org/jira/browse/IGNITE-1621
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Vasiliy Sisko


I'm entered the same name and clicked Confirm, got error that item with such 
name already exists, but after refreshing page I saw that new item with the 
same name was cloned anyway.



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

[jira] [Created] (IGNITE-1622) clear() method works incorrectly with near caches

2015-10-06 Thread Valentin Kulichenko (JIRA) 
Valentin Kulichenko created IGNITE-1622:
---

 Summary: clear() method works incorrectly with near caches
 Key: IGNITE-1622
 URL: https://issues.apache.org/jira/browse/IGNITE-1622
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Blocker
 Fix For: ignite-1.5


Currently {{IgniteCache.clear()}} method doesn't clear server nodes if there 
are near entries. Instead it should clear all caches, including near and 
readers.



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

[jira] [Commented] (IGNITE-1257) Implement agent download dialog for page with such functionality

2015-10-06 Thread Andrey Novikov (JIRA) 

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

Andrey Novikov commented on IGNITE-1257:


Need show dialog on lose connection to agent, node  on sql page.

> Implement agent download dialog for page with such functionality
> 
>
> Key: IGNITE-1257
> URL: https://issues.apache.org/jira/browse/IGNITE-1257
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: ignite-1.5
>
>
> * Implement common agent download dialog as template use load from metadata 
> dialog.
> * Generate agent archive with properties file filled by user and server 
> settings (for zero configuration run of agent).
> * Use token instead of login, password in agent configuration.



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

[jira] [Created] (IGNITE-1619) Platform .Net: Generic type is lost during array/collection serialization

2015-10-06 Thread Pavel Tupitsyn (JIRA) 
Pavel  Tupitsyn created IGNITE-1619:
---

 Summary: Platform .Net: Generic type is lost during 
array/collection serialization
 Key: IGNITE-1619
 URL: https://issues.apache.org/jira/browse/IGNITE-1619
 Project: Ignite
  Issue Type: Bug
  Components: interop
Affects Versions: ignite-1.4
Reporter: Pavel  Tupitsyn
Assignee: Pavel  Tupitsyn
 Fix For: ignite-1.5


We do not serialize collection/array element type, so on deserialization we can 
not recreate original collection. So generic arrays/collections can't be used 
in job arguments, service arguments, etc.





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

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

2015-10-06 Thread Pavel Tupitsyn (JIRA) 

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

Pavel  Tupitsyn edited comment on IGNITE-1562 at 10/6/15 9:34 AM:
--

My point is that WriteArray and WriteCollection methods do not make sense (and 
they work incorrectly), because depending on element type, there are multiple 
formats (primitive array, object array, collection, generic collection). Thus 
in each of these methods we have to select proper handler, the same way we do 
in the most common WriteObject() method. So we should remove these methods.

First, let's address generic type loss (IGNITE-1619), then we'll see if 
collection methods can be removed.

UPD: Difference between WriteCollection and WriteObject is in metadata type id. 
This is needed for interoperability. So looks like that we need to remove 
generic WriteCollection methods, and update non-generic methods documentation 
to clearly state that they are only for Java interop.


was (Author: ptupitsyn):
My point is that WriteArray and WriteCollection methods do not make sense (and 
they work incorrectly), because depending on element type, there are multiple 
formats (primitive array, object array, collection, generic collection). Thus 
in each of these methods we have to select proper handler, the same way we do 
in the most common WriteObject() method. So we should remove these methods.

First, let's address generic type loss (IGNITE-1619), then we'll see if 
collection methods can be removed.

UPD: Difference between WriteCollection and WriteObject is in metadata type id.

> .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] [Updated] (IGNITE-1619) Platform .Net: Generic type is lost during array/collection serialization

2015-10-06 Thread Pavel Tupitsyn (JIRA) 

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

Pavel  Tupitsyn updated IGNITE-1619:

Description: 
We do not serialize collection/array element type, so on deserialization we can 
not recreate original collection. So generic arrays/collections can't be used 
in job arguments, service arguments, etc.

* We should keep current format for non-generic collections, arrays of 
primitives, and arrays of objects
* Generic collections and arrays should be written with new TypeIds (not 
compatible with other platforms) and include type information

  was:
We do not serialize collection/array element type, so on deserialization we can 
not recreate original collection. So generic arrays/collections can't be used 
in job arguments, service arguments, etc.




> Platform .Net: Generic type is lost during array/collection serialization
> -
>
> Key: IGNITE-1619
> URL: https://issues.apache.org/jira/browse/IGNITE-1619
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>
> We do not serialize collection/array element type, so on deserialization we 
> can not recreate original collection. So generic arrays/collections can't be 
> used in job arguments, service arguments, etc.
> * We should keep current format for non-generic collections, arrays of 
> primitives, and arrays of objects
> * Generic collections and arrays should be written with new TypeIds (not 
> compatible with other platforms) and include type information



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

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

2015-10-06 Thread Anton Vinogradov (JIRA) 

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

Anton Vinogradov commented on IGNITE-429:
-

Chandresh, following problems still actual at pr-130:
1) Code contains redundant comments.
for example: // startTopology(stormStreamer);
2) Redundant newlines should be removed. At code and imports.
3) Newlines should be added where it necessary:
for example:
if (log.isDebugEnabled()) {
log.info("get tuple from storm  " + k + ", " + igniteGrid.get(k));
}
getStreamer().addData(k, igniteGrid.get(k));
5) @Override should be located according to Coding Guidelines.
6) Javadoc should present for each method and sentences should be finished with 
dot.
7) Code should be java7 compatible.

> 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] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

2015-10-06 Thread Anton Vinogradov (JIRA) 

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

Anton Vinogradov commented on IGNITE-429:
-

I've updated 
https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines 
Hope it will help.

> 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] [Commented] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used

2015-10-06 Thread Denis Magda (JIRA) 

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

Denis Magda commented on IGNITE-1272:
-

Custom class loaders won't be supported for {{PortableObject}} because it was 
designed for absolutely different use cases.
It means that we can ignore/skip the rest of failing tests for 
{{PortableMarshaller}} and should omit sending deployment info for caches that 
store portable objects.

Currently did the following:
- set {{deploymentEnabled}} flag per {{GridCacheContext}} and 
{{CacheObjectContext}};
- modified the code that used {{GridCacheSharedContext.deploymentEnabled()}} in 
a way to use {{GridCacheContext.deploymentEnabled()}};

Run some basic tests. The tests are failing because not all 
{{GridCacheMessages}} have properly set {{cacheId}} that is used to get a valid 
{{GridCacheContext}} in some places.
So what is left is to find those message for which it's obligatory to set valid 
{{cacheId}} and use it whenever it's needed.

> PortableMarshaller: issues when different class loaders are used
> 
>
> Key: IGNITE-1272
> URL: https://issues.apache.org/jira/browse/IGNITE-1272
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: ignite-1.5
>
> Attachments: ignite-1272.patch
>
>
> The reason is that a loader is not passed to required places when needed.
> Reproduced with the following tests:
> - {{IgniteCacheAbstractExecutionContextTest.testUserClassLoader()}} fails 
> with PortableMarshaller enabled.
> - {{GridDeploymentMessageCountSelfTest.testCacheValueDeploymentOnPut()}}
> Another issue is when {{PortableContext}} returns {{PortableClassDescriptor}} 
> by type id. Returned descriptor has a constructor which already has been 
> loaded with another class loader. Fix is not trivial and issue is reproduced 
> with {{GridP2PRemoteClassLoadersSelfTest}}
> Look for corresponding TODOs in the code.
> Unmute tests when fixed



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

[jira] [Updated] (IGNITE-1617) CPP: review string usage in public API

2015-10-06 Thread Igor Sapego (JIRA) 

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

Igor Sapego updated IGNITE-1617:

Assignee: Vladimir Ozerov  (was: Igor Sapego)

> CPP: review string usage in public API 
> ---
>
> Key: IGNITE-1617
> URL: https://issues.apache.org/jira/browse/IGNITE-1617
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
>
> Currently there is std::string type used in some parts of public API while 
> const char* used in some other parts. Need to review API and suggest solution 
> for the consistent string policy.



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

[jira] [Resolved] (IGNITE-1475) CPP: Implement shortcuts for array/collection/dictionary methods in reader/writer.

2015-10-06 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov resolved IGNITE-1475.
-
Resolution: Won't Fix

> CPP: Implement shortcuts for array/collection/dictionary methods in 
> reader/writer.
> --
>
> Key: IGNITE-1475
> URL: https://issues.apache.org/jira/browse/IGNITE-1475
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Currently user is forced to use our reader/writer wrappers for collections. 
> While really required in general case, this is not needed for the most common 
> data types: vectors, sets, maps, etc.
> We need to define shortcut methods in reader/writer .h files to support these 
> basic types.



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

[jira] [Closed] (IGNITE-1475) CPP: Implement shortcuts for array/collection/dictionary methods in reader/writer.

2015-10-06 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov closed IGNITE-1475.
---

> CPP: Implement shortcuts for array/collection/dictionary methods in 
> reader/writer.
> --
>
> Key: IGNITE-1475
> URL: https://issues.apache.org/jira/browse/IGNITE-1475
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Currently user is forced to use our reader/writer wrappers for collections. 
> While really required in general case, this is not needed for the most common 
> data types: vectors, sets, maps, etc.
> We need to define shortcut methods in reader/writer .h files to support these 
> basic types.



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

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

2015-10-06 Thread Chandresh Pancholi (JIRA) 

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

Chandresh Pancholi commented on IGNITE-429:
---

Anton,

Didn't get you. What do you mean by actual code?

> 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] [Created] (IGNITE-1620) [Test failed] IGFS:Directory creation in DUAL mode failed

2015-10-06 Thread Andrey Gura (JIRA) 
Andrey Gura created IGNITE-1620:
---

 Summary: [Test failed] IGFS:Directory creation in DUAL mode failed
 Key: IGNITE-1620
 URL: https://issues.apache.org/jira/browse/IGNITE-1620
 Project: Ignite
  Issue Type: Test
Reporter: Andrey Gura
Priority: Blocker
 Fix For: ignite-1.5


{{Hadoop1OverIgfsDualAsyncTest.testMkdirs}} and {{ 
Hadoop1OverIgfsDualSyncTest.testMkdirs}} test are failed.

{noformat}
[10:33:24,212][ERROR][test-runner][IgfsMetaManager] Directory creation in DUAL 
mode failed [path=/d/f, properties={permission=0777}]
class org.apache.ignite.IgniteException: Failed to make directories [path=/d/f, 
props={permission=0777}]
at 
org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.mkdirs(IgniteHadoopIgfsSecondaryFileSystem.java:303)
at 
org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onSuccess(IgfsMetaManager.java:2483)
at 
org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onSuccess(IgfsMetaManager.java:2481)
at 
org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3051)
at 
org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:2860)
at 
org.apache.ignite.internal.processors.igfs.IgfsMetaManager.mkdirsDual(IgfsMetaManager.java:2526)
at 
org.apache.ignite.internal.processors.igfs.IgfsImpl$11.call(IgfsImpl.java:782)
at 
org.apache.ignite.internal.processors.igfs.IgfsImpl$11.call(IgfsImpl.java:766)
at 
org.apache.ignite.internal.processors.igfs.IgfsImpl.safeOp(IgfsImpl.java:2014)
at 
org.apache.ignite.internal.processors.igfs.IgfsImpl.mkdirs(IgfsImpl.java:766)
at 
org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest.testMkdirs(IgfsAbstractSelfTest.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
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:1665)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
[10:33:24,214][ERROR][main][root] Test failed.
class org.apache.ignite.igfs.IgfsException: Generic IGFS error occurred.
at 
org.apache.ignite.internal.processors.igfs.IgfsUtils.toIgfsException(IgfsUtils.java:76)
at 
org.apache.ignite.internal.processors.igfs.IgfsImpl.safeOp(IgfsImpl.java:2017)
at 
org.apache.ignite.internal.processors.igfs.IgfsImpl.mkdirs(IgfsImpl.java:766)
at 
org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest.testMkdirs(IgfsAbstractSelfTest.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
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:1665)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create the 
path due to secondary file system exception: /d/f
at 
org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onFailure(IgfsMetaManager.java:2520)
at 
org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onFailure(IgfsMetaManager.java:2481)
at 
org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3054)
at 
org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:2860)
at 
org.apache.ignite.internal.processors.igfs.IgfsMetaManager.mkdirsDual(IgfsMetaManager.java:2526)
at 
org.apache.ignite.internal.processors.igfs.IgfsImpl$11.call(IgfsImpl.java:782)
at 
org.apache.ignite.internal.processors.igfs.IgfsImpl$11.call(IgfsImpl.java:766)
at 
org.apache.ignite.internal.processors.igfs.IgfsImpl.safeOp(IgfsImpl.java:2014)
... 10 more
Caused by: class org.apache.ignite.IgniteException: Failed to make directories 
[path=/d/f, props={permission=0777}]
at 
org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.mkdirs(IgniteHadoopIgfsSecondaryFileSystem.java:303)
at

[jira] [Commented] (IGNITE-708) Need to remove background partition exchange

2015-10-06 Thread Yakov Zhdanov (JIRA) 

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

Yakov Zhdanov commented on IGNITE-708:
--

Gian,

you removed body of {{onTimeout}} method, but {{ResendTimeoutObject}} still 
gets scheduled. This is not correct. Please also note that partitions resending 
is scheduled from different places and can't be just removed. Many tests 
failed. See TeamCity results for your PR: 
http://204.14.53.153/project.html?projectId=Ignite=projectOverview_Ignite=pull%2F129%2Fhead
 (please make sure you have TC green before submitting anything to review)

You should continue your investigation. Identify place in code when each node 
sends its partitions to oldest node and change it so partitions get sent only 
if anything changed locally.

Thanks!


> Need to remove background partition exchange
> 
>
> Key: IGNITE-708
> URL: https://issues.apache.org/jira/browse/IGNITE-708
> Project: Ignite
>  Issue Type: Task
>Affects Versions: ignite-1.4
>Reporter: Yakov Zhdanov
>Assignee: Gianfranco Murador
>Priority: Blocker
>  Labels: datagrid
> Fix For: ignite-1.5, ignite-1.6
>
>
> Now every node sends its partition map to cache coordinator (which is the 
> oldest node in topology) and coordinator spreads full partition map to every 
> node in topology. This happens for each cache separately. This seems to take 
> place even if there were no changes to local partition maps. Given we 
> guarantee communication message delivery this background process seems to be 
> an overkill.
> Exchange should happen only if any changes took place.
> After dynamic cache start has been introduced, we can have significant amount 
> of live caches at some point of app lifecycle and app may suffer from  
> background exchange which is obviously not a requirement (and may be never 
> has been the one).



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

[jira] [Commented] (IGNITE-638) Implement IgniteSemaphore data structure

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

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

ASF GitHub Bot commented on IGNITE-638:
---

GitHub user vladisav reopened a pull request:

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

IGNITE-638: Implements cache distributed semaphore

This interface provides a rich API for working with distributed semaphore.
Distributed semaphore provides functionality similar to 
java.util.concurrent.Semaphore.

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

$ git pull https://github.com/vladisav/ignite ignite-638

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

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


commit e9567adec4057b0a0528735d4934440f4cd9fee3
Author: vladisav 
Date:   2015-09-25T09:14:18Z

Implements distributed semaphore ignite-638

This interface provides a rich API for working with distributed semaphore.
Distributed semaphore provides functionality similar to 
java.util.concurrent.Semaphore.

commit be332a82711ddd7e9088e00d7f26edd7de407a11
Author: Vladisav Jelisavcic 
Date:   2015-10-01T18:19:32Z

Fixes formatting issues;

commit 77f9deb7f79acb04b73994e83efd4539646073e6
Author: Vladisav Jelisavcic 
Date:   2015-10-03T10:44:02Z

Fixes formatting issues;




> Implement IgniteSemaphore data structure
> 
>
> Key: IGNITE-638
> URL: https://issues.apache.org/jira/browse/IGNITE-638
> Project: Ignite
>  Issue Type: Sub-task
>  Components: data structures
>Reporter: Dmitriy Setrakyan
>Assignee: Vladisav Jelisavcic
>
> We need to add {{IgniteSemaphore}} data structure in addition to other data 
> structures provided by Ignite. {{IgniteSemaphore}} should have similar API to 
> {{java.util.concurrent.IgniteSemaphore}} class in JDK.
> As an example, you can see how 
> [IgniteCountDownLatch|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/IgniteCountDownLatch.java]
>  is implemented in 
> [GridCacheCountDownLatchImpl|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/datastructures/GridCacheCountDownLatchImpl.java]
>  class.
> In general we need to have an entity in ATOMIC cache storing number of 
> permits and allow user threads to block whenever no more permits are 
> available.



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

[jira] [Commented] (IGNITE-638) Implement IgniteSemaphore data structure

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

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

ASF GitHub Bot commented on IGNITE-638:
---

Github user vladisav closed the pull request at:

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


> Implement IgniteSemaphore data structure
> 
>
> Key: IGNITE-638
> URL: https://issues.apache.org/jira/browse/IGNITE-638
> Project: Ignite
>  Issue Type: Sub-task
>  Components: data structures
>Reporter: Dmitriy Setrakyan
>Assignee: Vladisav Jelisavcic
>
> We need to add {{IgniteSemaphore}} data structure in addition to other data 
> structures provided by Ignite. {{IgniteSemaphore}} should have similar API to 
> {{java.util.concurrent.IgniteSemaphore}} class in JDK.
> As an example, you can see how 
> [IgniteCountDownLatch|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/IgniteCountDownLatch.java]
>  is implemented in 
> [GridCacheCountDownLatchImpl|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/datastructures/GridCacheCountDownLatchImpl.java]
>  class.
> In general we need to have an entity in ATOMIC cache storing number of 
> permits and allow user threads to block whenever no more permits are 
> available.



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

[jira] [Commented] (IGNITE-1619) Platform .Net: Generic type is lost during array/collection serialization

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

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

ASF GitHub Bot commented on IGNITE-1619:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1619 Platform .Net: Generic type is lost during array/collection 
serialization



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

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

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

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


commit 1164ff10694ce4690f57190708d6bc4a6efaf9b5
Author: ptupitsyn 
Date:   2015-10-06T10:04:49Z

wip

commit c4fc5a9def2c46454a774a6527066d4742c9
Author: ptupitsyn 
Date:   2015-10-06T10:13:33Z

test added

commit 73700655a6d6f20dbe5ecd92a90fc5734a5ba5e4
Author: ptupitsyn 
Date:   2015-10-06T10:14:55Z

test wip

commit 2a70a47dc103e87bacd1792434aaabb408362dcd
Author: ptupitsyn 
Date:   2015-10-06T10:25:01Z

wip

commit 2f4204b5d57e411517893eb9c43436025eaf5b47
Author: ptupitsyn 
Date:   2015-10-06T10:32:16Z

wip

commit 3c76ef26b4204358d4f709516a94f6e351da3ca5
Author: ptupitsyn 
Date:   2015-10-06T10:49:14Z

wip WriteGenericArray

commit 53c2cb42f95e68e1836757a80725289b8851ac7d
Author: ptupitsyn 
Date:   2015-10-06T12:11:29Z

wip

commit 01e110f59fe2884cddb725b8c5947458b06cb840
Author: ptupitsyn 
Date:   2015-10-06T12:16:34Z

ReadWriteTypedArray done

commit d0aef6919f170af5e26a13a9240033a48871d631
Author: ptupitsyn 
Date:   2015-10-06T12:24:59Z

wip

commit cdf3397736bcf97eb64ee3ebfb4c1c9a54b7f27a
Author: ptupitsyn 
Date:   2015-10-06T12:32:51Z

wip

commit c7829e068bc05bf34d7609c0b9ee3c0631947225
Author: ptupitsyn 
Date:   2015-10-06T13:00:31Z

wip

commit f3204af7d5374f0daec2727c14607674dc9a9dd4
Author: ptupitsyn 
Date:   2015-10-06T13:01:23Z

wip

commit f495585f717c0f7eb338ae6020d9c079e0afb439
Author: ptupitsyn 
Date:   2015-10-06T13:06:36Z

wip cleanup

commit 15324f7f86a5d56b3377a01784d38dec4140b415
Author: ptupitsyn 
Date:   2015-10-06T13:59:22Z

ReadTypedCollection wip

commit f6486af2411528bf23dc92f39179d963d4c464c4
Author: ptupitsyn 
Date:   2015-10-06T14:23:10Z

Collections done without delegate caching

commit 24868ebde65eae94d42ba4271c745f86f6e70002
Author: ptupitsyn 
Date:   2015-10-06T14:49:44Z

ReplaceTypes

commit 24d62dac1d4b8675861d03abd6be9c8c01dc7f63
Author: ptupitsyn 
Date:   2015-10-06T14:55:45Z

wip

commit 6d9e324218e07188ee7e04bd073629e4e6c65867
Author: ptupitsyn 
Date:   2015-10-06T16:00:37Z

Fix interop collection reads

commit 1a7b68213801dfda2700720f320208c19bfcffc5
Author: ptupitsyn 
Date:   2015-10-06T16:05:51Z

fixing tests

commit d7c7c6d8ddd1c24ff2874a16c4b91c011f9a5f9b
Author: ptupitsyn 
Date:   2015-10-06T16:42:33Z

wip

commit 6d36c1facfd8cea3aa94f117da50380e92626ae8
Author: ptupitsyn 
Date:   2015-10-06T16:44:10Z

wip

commit 1e292481158408d5c512ebb804c087f645755b31
Author: ptupitsyn 
Date:   2015-10-06T16:58:37Z

wip

commit f54256ebc2f4bcb8c9de1775dcd8d623fcb3c1b0
Author: ptupitsyn 
Date:   2015-10-06T17:08:31Z

comment out "trying to be nice" code




> Platform .Net: Generic type is lost during array/collection serialization
> -
>
> Key: IGNITE-1619
> URL: https://issues.apache.org/jira/browse/IGNITE-1619
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>
> We do not serialize collection/array element type, so on deserialization we 
> can not recreate original collection. So generic arrays/collections can't be 
> used in job arguments, service arguments, etc.
> * We should keep current format for non-generic collections, arrays of 
> primitives, and arrays of objects
> * Generic collections and arrays should be written with new TypeIds (not 
> compatible with other platforms) and include type information



--

[jira] [Commented] (IGNITE-1397) Load/consistency test framework

2015-10-06 Thread Artem Shutak (JIRA) 

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

Artem Shutak commented on IGNITE-1397:
--

In process of testing new tests I've faced with hangs in cache. As a result 
benchmark execution hangs. To prevent it
- use an async cache and call {{get(long timeout)}} on cache future;
- add full thread dump printing for client node and server nodes in exception 
case.

> Load/consistency test framework
> ---
>
> Key: IGNITE-1397
> URL: https://issues.apache.org/jira/browse/IGNITE-1397
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Artem Shutak
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Need to create "Load/consistency test framework". See: 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316109.
> As POC it should be implemented test cases described on the wiki.



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