[jira] [Commented] (IGNITE-2177) User defined aggregate functions for SQL

2015-12-26 Thread Dmitriy Setrakyan (JIRA) 

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

Dmitriy Setrakyan commented on IGNITE-2177:
---

Sergi, 

# What is the purpose of the Alias methods?
# Do you mind defining the SqlAggregate function here? I looked at H2 API and 
don't think it will apply to us one-to-one. For example, do we need init(...) 
method?

> User defined aggregate functions for SQL
> 
>
> Key: IGNITE-2177
> URL: https://issues.apache.org/jira/browse/IGNITE-2177
> Project: Ignite
>  Issue Type: Wish
>Reporter: Sergi Vladykin
> Fix For: 1.6
>
>
> Need to design some factory like abstraction for creating map part and reduce 
> part of the aggregate. 



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

[jira] [Issue Comment Deleted] (IGNITE-2177) User defined aggregate functions for SQL

2015-12-26 Thread Dmitriy Setrakyan (JIRA) 

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

Dmitriy Setrakyan updated IGNITE-2177:
--
Comment: was deleted

(was: Sergi, 

# What is the purpose of the Alias methods?
# Do you mind defining the SqlAggregate function here? I looked at H2 API and 
don't think it will apply to us one-to-one. For example, do we need init(...) 
method?)

> User defined aggregate functions for SQL
> 
>
> Key: IGNITE-2177
> URL: https://issues.apache.org/jira/browse/IGNITE-2177
> Project: Ignite
>  Issue Type: Wish
>Reporter: Sergi Vladykin
> Fix For: 1.6
>
>
> Need to design some factory like abstraction for creating map part and reduce 
> part of the aggregate. 



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

[jira] [Commented] (IGNITE-2177) User defined aggregate functions for SQL

2015-12-26 Thread Dmitriy Setrakyan (JIRA) 

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

Dmitriy Setrakyan commented on IGNITE-2177:
---

Sergi, 

# What is the purpose of the Alias methods?
# Do you mind defining the SqlAggregate function here? I looked at H2 API and 
don't think it will apply to us one-to-one. For example, do we need init(...) 
method?

> User defined aggregate functions for SQL
> 
>
> Key: IGNITE-2177
> URL: https://issues.apache.org/jira/browse/IGNITE-2177
> Project: Ignite
>  Issue Type: Wish
>Reporter: Sergi Vladykin
> Fix For: 1.6
>
>
> Need to design some factory like abstraction for creating map part and reduce 
> part of the aggregate. 



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

[jira] [Issue Comment Deleted] (IGNITE-2177) User defined aggregate functions for SQL

2015-12-26 Thread Dmitriy Setrakyan (JIRA) 

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

Dmitriy Setrakyan updated IGNITE-2177:
--
Comment: was deleted

(was: Sergi, 

# What is the purpose of the Alias methods?
# Do you mind defining the SqlAggregate function here? I looked at H2 API and 
don't think it will apply to us one-to-one. For example, do we need init(...) 
method?)

> User defined aggregate functions for SQL
> 
>
> Key: IGNITE-2177
> URL: https://issues.apache.org/jira/browse/IGNITE-2177
> Project: Ignite
>  Issue Type: Wish
>Reporter: Sergi Vladykin
> Fix For: 1.6
>
>
> Need to design some factory like abstraction for creating map part and reduce 
> part of the aggregate. 



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

[jira] [Commented] (IGNITE-2177) User defined aggregate functions for SQL

2015-12-26 Thread Dmitriy Setrakyan (JIRA) 

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

Dmitriy Setrakyan commented on IGNITE-2177:
---

Sergi, 

# What is the purpose of the Alias methods?
# Do you mind defining the SqlAggregate function here? I looked at H2 API and 
don't think it will apply to us one-to-one. For example, do we need init(...) 
method?

> User defined aggregate functions for SQL
> 
>
> Key: IGNITE-2177
> URL: https://issues.apache.org/jira/browse/IGNITE-2177
> Project: Ignite
>  Issue Type: Wish
>Reporter: Sergi Vladykin
> Fix For: 1.6
>
>
> Need to design some factory like abstraction for creating map part and reduce 
> part of the aggregate. 



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

[jira] [Comment Edited] (IGNITE-2080) JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c

2015-12-26 Thread Andrey Gura (JIRA) 

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

Andrey Gura edited comment on IGNITE-2080 at 12/26/15 5:11 PM:
---

{{DirectByteBufferStreamImplV1}} and {{DirectByteBufferStreamImplV2}} classes 
modified in order to always have fixed byte order.

{{CacheAffinityCallSelfTest.testAffinityCallRestartNode}} test is incorrect and 
should be rewritten. The problem is in the following code snippet:

{code:java}
while (!fut.isDone())
grid(1).compute().affinityCall(CACHE_NAME, key, new CheckCallable(key, 
topVer, topVer + 1));
{code}

This cycle can execute too many {{affinityCall}} invokes until future 
completed. It leads to "Job failover failed because number of maximum failover 
attempts for affinity call" warning.

Please review https://github.com/apache/ignite/pull/362


was (Author: agura):
{{DirectByteBufferStreamImplV1}} and {{DirectByteBufferStreamImplV2}} classes 
modified in order to always have fixed byte order.

{{CacheAffinityCallSelfTest.testAffinityCallRestartNode}} test is incorrect and 
should be rewritten. The problem is in the following code snippet:

{code:java}
while (!fut.isDone())
grid(1).compute().affinityCall(CACHE_NAME, key, new CheckCallable(key, 
topVer, topVer + 1));
{code}

This cycle can execute too many {{affinityCall}} invokes until future 
completed. It leads to "Job failover failed because number of maximum failover 
attempts for affinity call" warning.


> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]  
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
>

[jira] [Assigned] (IGNITE-1417) .Net: Implement distributed queue.

2015-12-26 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn reassigned IGNITE-1417:
--

Assignee: Pavel Tupitsyn

> .Net: Implement distributed queue.
> --
>
> Key: IGNITE-1417
> URL: https://issues.apache.org/jira/browse/IGNITE-1417
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>Priority: Critical
>




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

[jira] [Updated] (IGNITE-369) Cache manager should switch cache statisticsEnabled property globaly

2015-12-26 Thread Alexey Goncharuk (JIRA) 

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

Alexey Goncharuk updated IGNITE-369:

Assignee: (was: Alexey Goncharuk)

> Cache manager should switch cache statisticsEnabled property globaly
> 
>
> Key: IGNITE-369
> URL: https://issues.apache.org/jira/browse/IGNITE-369
> Project: Ignite
>  Issue Type: Task
>Affects Versions: sprint-2
>Reporter: Alexey Kuznetsov
>
> Also you should take care about new nodes that joining grid.
> New node could have statisticsEnabled with opposite value that nodes in grid.



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

[jira] [Assigned] (IGNITE-2002) .Net: Data streamer does not work with peerClassLoadingEnabled

2015-12-26 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn reassigned IGNITE-2002:
--

Assignee: Alexey Goncharuk  (was: Pavel Tupitsyn)

> .Net: Data streamer does not work with peerClassLoadingEnabled
> --
>
> Key: IGNITE-2002
> URL: https://issues.apache.org/jira/browse/IGNITE-2002
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 1.6
>
>
> Add  to spring config, 
> run streamer tests or examples, there are exceptions in Java and flush hangs.



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

[jira] [Closed] (IGNITE-2297) DirectByteBufferStreamImplV2: add special cases for maps with a single element.

2015-12-26 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov closed IGNITE-2297.
---

> DirectByteBufferStreamImplV2: add special cases for maps with a single 
> element.
> ---
>
> Key: IGNITE-2297
> URL: https://issues.apache.org/jira/browse/IGNITE-2297
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> The biggest hotspot in a simple PUT scenario is Entry[] creation caused by 
> empty HashMap inflation inside DirectByteBufferStreamImplV2 read methods.
> It is interesting, that in lots cases the map being read contains only one 
> element. 
> Looks like this common case could be optimized - create a map with single 
> key/val pair with optional fallback to normal map.



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

[jira] [Resolved] (IGNITE-2297) DirectByteBufferStreamImplV2: add special cases for maps with a single element.

2015-12-26 Thread Vladimir Ozerov (JIRA) 

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

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

Re-checked - doesn't worth.

> DirectByteBufferStreamImplV2: add special cases for maps with a single 
> element.
> ---
>
> Key: IGNITE-2297
> URL: https://issues.apache.org/jira/browse/IGNITE-2297
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> The biggest hotspot in a simple PUT scenario is Entry[] creation caused by 
> empty HashMap inflation inside DirectByteBufferStreamImplV2 read methods.
> It is interesting, that in lots cases the map being read contains only one 
> element. 
> Looks like this common case could be optimized - create a map with single 
> key/val pair with optional fallback to normal map.



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

[jira] [Commented] (IGNITE-2080) JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c

2015-12-26 Thread Andrey Gura (JIRA) 

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

Andrey Gura commented on IGNITE-2080:
-

{{CacheAffinityCallSelfTest.testAffinityCallRestartNode}} test is incorrect and 
should be rewritten. The problem is in the following code snippet:

{code:java}
while (!fut.isDone())
grid(1).compute().affinityCall(CACHE_NAME, key, new CheckCallable(key, 
topVer, topVer + 1));
{code}

This cycle can execute too many {{affinityCall}} invokes until future 
completed. It leads to "Job failover failed because number of maximum failover 
attempts for affinity call" warning.


> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]  
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/c
> ache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+33
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/
> distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+28
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(Lorg/apache/ignite/internal/processors/cache/distributed/dh
> t/atomic/GridNearAtomicUpdateFuture;Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+3
> j  
>

[jira] [Comment Edited] (IGNITE-2080) JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c

2015-12-26 Thread Andrey Gura (JIRA) 

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

Andrey Gura edited comment on IGNITE-2080 at 12/26/15 5:00 PM:
---

{{DirectByteBufferStreamImplV1}} and {{DirectByteBufferStreamImplV2}} classes 
modified in order to always have fixed byte order.

{{CacheAffinityCallSelfTest.testAffinityCallRestartNode}} test is incorrect and 
should be rewritten. The problem is in the following code snippet:

{code:java}
while (!fut.isDone())
grid(1).compute().affinityCall(CACHE_NAME, key, new CheckCallable(key, 
topVer, topVer + 1));
{code}

This cycle can execute too many {{affinityCall}} invokes until future 
completed. It leads to "Job failover failed because number of maximum failover 
attempts for affinity call" warning.



was (Author: agura):
{{CacheAffinityCallSelfTest.testAffinityCallRestartNode}} test is incorrect and 
should be rewritten. The problem is in the following code snippet:

{code:java}
while (!fut.isDone())
grid(1).compute().affinityCall(CACHE_NAME, key, new CheckCallable(key, 
topVer, topVer + 1));
{code}

This cycle can execute too many {{affinityCall}} invokes until future 
completed. It leads to "Job failover failed because number of maximum failover 
attempts for affinity call" warning.


> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]  
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/c

[jira] [Assigned] (IGNITE-2080) JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c

2015-12-26 Thread Andrey Gura (JIRA) 

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

Andrey Gura reassigned IGNITE-2080:
---

Assignee: Andrey Gura

> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]  
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/c
> ache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+33
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/
> distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+28
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(Lorg/apache/ignite/internal/processors/cache/distributed/dh
> t/atomic/GridNearAtomicUpdateFuture;Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+3
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(Lorg/apache/ignite/internal/processors/affinity/Affinit
> yTopologyVersion;)V+595
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology()V+253
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map()V+60
> j  
>

[jira] [Comment Edited] (IGNITE-2080) JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c

2015-12-26 Thread Andrey Gura (JIRA) 

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

Andrey Gura edited comment on IGNITE-2080 at 12/26/15 5:30 PM:
---

{{DirectByteBufferStreamImplV1}} and {{DirectByteBufferStreamImplV2}} classes 
modified in order to always have fixed byte order.

{{CacheAffinityCallSelfTest.testAffinityCallRestartNode}} test is incorrect and 
should be rewritten. The problem is in the following code snippet:

{code:java}
while (!fut.isDone())
grid(1).compute().affinityCall(CACHE_NAME, key, new CheckCallable(key, 
topVer, topVer + 1));
{code}

This cycle can execute too many {{affinityCall}} invokes until future 
completed. It leads to "Job failover failed because number of maximum failover 
attempts for affinity call" warning.



was (Author: agura):
{{DirectByteBufferStreamImplV1}} and {{DirectByteBufferStreamImplV2}} classes 
modified in order to always have fixed byte order.

{{CacheAffinityCallSelfTest.testAffinityCallRestartNode}} test is incorrect and 
should be rewritten. The problem is in the following code snippet:

{code:java}
while (!fut.isDone())
grid(1).compute().affinityCall(CACHE_NAME, key, new CheckCallable(key, 
topVer, topVer + 1));
{code}

This cycle can execute too many {{affinityCall}} invokes until future 
completed. It leads to "Job failover failed because number of maximum failover 
attempts for affinity call" warning.

Please review https://github.com/apache/ignite/pull/362

> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]  
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j  
>

[jira] [Updated] (IGNITE-2263) Get rid of wrapping views where possible.

2015-12-26 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-2263:

Summary: Get rid of wrapping views where possible.  (was: Get rif of 
wrapping views where possible.)

> Get rid of wrapping views where possible.
> -
>
> Key: IGNITE-2263
> URL: https://issues.apache.org/jira/browse/IGNITE-2263
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.6
>
>
> We have about ~50-100 usages of things like F.view or F.viewReadOnly. In lots 
> cases it is not necessary, adds garbage, but doesn't add any value. 
> Need to revisit these places.



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

[jira] [Created] (IGNITE-2297) DirectByteBufferStreamImplV2: add special cases for maps with a single element.

2015-12-26 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-2297:
---

 Summary: DirectByteBufferStreamImplV2: add special cases for maps 
with a single element.
 Key: IGNITE-2297
 URL: https://issues.apache.org/jira/browse/IGNITE-2297
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.6


The biggest hotspot in a simple PUT scenario is Entry[] creation caused by 
empty HashMap inflation inside DirectByteBufferStreamImplV2 read methods.

It is interesting, that in lots cases the map being read contains only one 
element. 

Looks like this common case could be optimized - create a map with single 
key/val pair with optional fallback to normal map.



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

[jira] [Commented] (IGNITE-2264) Optimize GridDistributedTxMapping.

2015-12-26 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov commented on IGNITE-2264:
-

One more major problem - very often there is only one entry in mapping. And we 
create the whole LinkedHashSet for it. 
No need for this actually. We can use singleton set or so here.

> Optimize GridDistributedTxMapping.
> --
>
> Key: IGNITE-2264
> URL: https://issues.apache.org/jira/browse/IGNITE-2264
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.6
>
>
> This class has two methods: reads() and writes(). Together they return the 
> whole set of entries. 
> The problem is that each call creates collection wrapper over entries + 1 
> additional iterator per each traverse over collection. This seen as a garbage 
> "hotspot" in flight recorder.
> Actually there is no need for these methods. Instead, we can pass entries 
> collection directly and filter entries manually.



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

[jira] [Assigned] (IGNITE-2288) F.first(Collection) should use index-based lookup for Lists.

2015-12-26 Thread Ilya Lantukh (JIRA) 

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

Ilya Lantukh reassigned IGNITE-2288:


Assignee: Ilya Lantukh  (was: Vladimir Ozerov)

> F.first(Collection) should use index-based lookup for Lists.
> 
>
> Key: IGNITE-2288
> URL: https://issues.apache.org/jira/browse/IGNITE-2288
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Ilya Lantukh
> Fix For: 1.6
>
>
> There are lots of places in code where F.first(Collection) is used. Quite 
> often passed collection is a List. 
> Instead of gettting iterator, we should do "get(0)" in these cases. This will 
> allow us to prevent iterator creation.



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

[jira] [Commented] (IGNITE-2143) inner join produce wrong result and is very slow

2015-12-26 Thread Sergi Vladykin (JIRA) 

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

Sergi Vladykin commented on IGNITE-2143:


As you can see from the query plan your index on `type` field is never used. 
You need a single compound index on (type, create_at, url) fields in this exact 
order.

Notice that the bug with HAVING (IGNITE-2205) will be fixed in 1.5, so now the 
query will work wrong.

Also you should notice that Ignite SQL is designed for throughput first, while 
you are measuring latency of analytic query. I mean Spark works the following 
way: it splits dataset in a number of chunks and attempts to process these 
chunks as parallel as possible, while Ignite runs each query part just in a 
single thread on each node. If you choose correct indexes you can have 
performance much better than Spark (due to better algorithmic efficiency) + 
good throughput but obviously not in all cases. In the future we will improve 
Ignite SQL so that it will allow tuning for better parallelism and handle 
analytic (latency targeted, disregarding throughput) use cases better.

> inner join produce wrong result and is very slow
> 
>
> Key: IGNITE-2143
> URL: https://issues.apache.org/jira/browse/IGNITE-2143
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.5
> Environment: 3 nodes in docker containers.
>Reporter: Sergey Soldatov
>Priority: Critical
> Attachments: config.xml, ignite-cache-1.0.0.jar
>
>
> I have following query for gitarchive records processing.  
> {code}
> select 
>  lang, count(distinct ForkTable.repo_url) as cnt 
> from (
>  select repo_url, lang from gitrecord where type = 'ForkEvent' and 
>  lang is not null group by lang, repo_url) as ForkTable 
> inner join (
>  select repo_url, html_url from gitrecord where type='PullRequestEvent'   
>  
>  group by repo_url, html_url) as PullTable 
> on 
>  ForkTable.repo_url = PullTable.repo_url 
> group by lang 
> order by cnt desc
> {code}
> And there are two major problems:
> 1. It produces an incorrect result if it's running in cluster mode.
> 2. It's really slow. for 200k rows it takes 500+ seconds comparing to 20 on 
> Spark for the same query
> Steps to reproduce:
> 1. Download github archive for 1 day and put it to hdfs ("/Data" in my case):
> {code}wget http://data.githubarchive.org/2015-01-01-{0..23}.json.gz{code}
> 2. copy attached ignite-cache-1.0.0.jar to Ignite's lib dir 
> 3. run ignite with attached config.xml 
> 4. run spark-shell
> {code}
> spark-shell --packages org.apache.ignite:ignite-spark:1.5.0-b1 --repositories 
> http://www.gridgainsystems.com/nexus/content/repositories/external --jars 
> /usr/lib/ignite-hadoop/libs/ignite-cache-1.0.0.jar --master 
> spark://{spark-master}:7077
> {code}
> 5. load data and execute the query:
> {code}
> import org.apache.ignite._
> import org.apache.ignite.configuration._
> import org.apache.ignite.cache.query._
> import org.apache.ignite.spark._
> import org.apache.ignite.lang.IgniteBiPredicate
> import io.dtk._
> val df = sqlContext.read.json("/Data/*.gz")
> Ignition.setClientMode(true)
> val cacheName = "gitrecords"
> val rdd = df.select("id", "repo.url", 
> "payload.forkee.language","type","payload.pull_request.head.repo.html_url").map(row
>  => (row.getString(0), new GitRecord(0, 
> row.getString(1),row.getString(2),row.getString(3),row.getString(4
> val cfg = new 
> CacheConfiguration[String,GitRecord]().setName(cacheName).setIndexedTypes(classOf[String],classOf[GitRecord]).setLoadPreviousValue(true)
> val ic = new IgniteContext[String,GitRecord](sc, 
> "/usr/lib/ignite-hadoop/config/config.xml")
> val sharedRDD = ic.fromCache(cfg)
> sharedRDD.savePairs(rdd)
> sharedRDD.sql("select lang, count(distinct ForkTable.repo_url) as cnt from 
> (select repo_url, lang from gitrecord where type = 'ForkEvent' and lang is 
> not null group by lang, repo_url) as ForkTable inner join (select repo_url, 
> html_url from gitrecord where type='PullRequestEvent' group by repo_url, 
> html_url) as PullTable on ForkTable.repo_url = PullTable.repo_url group by 
> lang order by cnt desc").show
> {code}



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

[jira] [Issue Comment Deleted] (IGNITE-2297) DirectByteBufferStreamImplV2: add special cases for maps with a single element.

2015-12-26 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-2297:

Comment: was deleted

(was: Re-checked - doesn't worth.)

> DirectByteBufferStreamImplV2: add special cases for maps with a single 
> element.
> ---
>
> Key: IGNITE-2297
> URL: https://issues.apache.org/jira/browse/IGNITE-2297
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> The biggest hotspot in a simple PUT scenario is Entry[] creation caused by 
> empty HashMap inflation inside DirectByteBufferStreamImplV2 read methods.
> It is interesting, that in lots cases the map being read contains only one 
> element. 
> Looks like this common case could be optimized - create a map with single 
> key/val pair with optional fallback to normal map.



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

[jira] [Commented] (IGNITE-2177) User defined aggregate functions for SQL

2015-12-26 Thread Sergi Vladykin (JIRA) 

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

Sergi Vladykin commented on IGNITE-2177:


I think the code should look like the following:

We should have two interfaces:
{code}
interface DistributedSqlAggregate {
 String getMapAlias();
 
 String getReduceAlias();

 String getLocalAlias();
 
SqlAggregate createMapAggregate();

SqlAggregate createReduceAggregate();

   SqlAggregate createLocalAggregate();
}

interface SqlAggregate {
// This ineterface have to reflect 
https://github.com/h2database/h2database/blob/master/h2/src/main/org/h2/api/AggregateFunction.java
}

// And method on cache configuration
ccfg.setSqlAggregates(Class... clss);

{code}




> User defined aggregate functions for SQL
> 
>
> Key: IGNITE-2177
> URL: https://issues.apache.org/jira/browse/IGNITE-2177
> Project: Ignite
>  Issue Type: Wish
>Reporter: Sergi Vladykin
> Fix For: 1.6
>
>
> Need to design some factory like abstraction for creating map part and reduce 
> part of the aggregate. 



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

[jira] [Updated] (IGNITE-2288) F.first(Collection) should use index-based lookup for Lists.

2015-12-26 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-2288:

Issue Type: Sub-task  (was: Task)
Parent: IGNITE-2232

> F.first(Collection) should use index-based lookup for Lists.
> 
>
> Key: IGNITE-2288
> URL: https://issues.apache.org/jira/browse/IGNITE-2288
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> There are lots of places in code where F.first(Collection) is used. Quite 
> often passed collection is a List. 
> Instead of gettting iterator, we should do "get(0)" in these cases. This will 
> allow us to prevent iterator creation.



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

[jira] [Closed] (IGNITE-2161) We need to tune Ignite site CSS to make it looks good for printing

2015-12-26 Thread Pavel Konstantinov (JIRA) 

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

Pavel Konstantinov closed IGNITE-2161.
--
Assignee: (was: Pavel Konstantinov)

Tested on Mac Windows Ubuntu + FireFox, Chrome, Safari, MS IE, MS Edge

> We need to tune Ignite site CSS to make it looks good for printing
> --
>
> Key: IGNITE-2161
> URL: https://issues.apache.org/jira/browse/IGNITE-2161
> Project: Ignite
>  Issue Type: Bug
>  Components: website
>Reporter: Alexey Kuznetsov
> Fix For: 1.5
>
>
> Open in chrome https://ignite.apache.org/benchmarks/ignite-vs-hazelcast.html
> Click Print -> looks ugly.
> See some ideas here: 
> http://www.creativebloq.com/responsive-web-design/make-your-website-printable-css-3132929



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

[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9

2015-12-26 Thread Roman Shtykh (JIRA) 

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

Roman Shtykh commented on IGNITE-2016:
--

Denis,

Thanks for details on _IgniteDataStreamer_'s buffering.
Yes, after our discussion I have the same idea on how it will be implemented.

> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> 
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



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

[jira] [Commented] (IGNITE-2002) .Net: Data streamer does not work with peerClassLoadingEnabled

2015-12-26 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn commented on IGNITE-2002:


Looks like a bug in DataStreamerImpl:644 ("if (initPda)"). We should not 
deserialize BinaryObjects from .NET there.

> .Net: Data streamer does not work with peerClassLoadingEnabled
> --
>
> Key: IGNITE-2002
> URL: https://issues.apache.org/jira/browse/IGNITE-2002
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 1.6
>
>
> Add  to spring config, 
> run streamer tests or examples, there are exceptions in Java and flush hangs.



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

[jira] [Closed] (IGNITE-302) 2nd run CacheQueryExample fails on 2 nodes

2015-12-26 Thread Sergey Kozlov (JIRA) 

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

Sergey Kozlov closed IGNITE-302.


> 2nd run CacheQueryExample fails on 2 nodes
> --
>
> Key: IGNITE-302
> URL: https://issues.apache.org/jira/browse/IGNITE-302
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: sprint-2
>Reporter: Alexey Kuznetsov
>Assignee: Sergey Kozlov
>
> 1. Start two nodes by bin\ggstart.bat examples\config\example-cache.xml
> 2. Run in Idea CacheQueryExample twice
> 3. Second run hangs and one node has ClassNotFoundException:
> {noformat}
> [17:11:11,044][WARNING][gridgain-#23%sys-null%][GridDeploymentPerVersionStore]
>  Failed to load peer class (ignore if class got undeployed during preloa
> ding) [alias=o.g.examples.datagrid.CacheQueryExample$Person, 
> dep=SharedDeployment [rmv=false, super=GridDeployment [ts=1414415470972, 
> depMode=SHARED,
> clsLdr=GridDeploymentClassLoader 
> [id=909c9b15941-8a410e89-f7a0-4ec6-a6b4-c4d135de731a, singleNode=false, 
> nodeLdrMap={a73e5cd4-c058-46b8-a3d9-cb0f4bbad
> 5c1=0fe3bb15941-a73e5cd4-c058-46b8-a3d9-cb0f4bbad5c1, 
> 09497dce-3430-4555-8a75-676c0275119c=1e8b9b15941-09497dce-3430-4555-8a75-676c0275119c},
>  p2pTimeo
> ut=5000, usrVer=0, depMode=SHARED, quiet=false], 
> clsLdrId=909c9b15941-8a410e89-f7a0-4ec6-a6b4-c4d135de731a, userVer=0, 
> loc=false, sampleClsName=o.g.ex
> amples.datagrid.CacheQueryExample$Organization, pendingUndeploy=false, 
> undeployed=false, usage=0]]]
> [17:11:11,046][SEVERE][gridgain-#23%sys-null%][GridCacheIoManager] 
>  Failed to process message 
> [senderId=a73e5cd4-c058-46b8-a3d9-cb0f4bbad
> 5c1]
> class org.gridgain.grid.GridException: Failed to find class with given class 
> loader for unmarshalling (make sure same version of all classes are avail
> able on all nodes or enable peer-class-loading): 
> org.gridgain.grid.kernal.processors.cache.GridCacheDeploymentManager$CacheClassLoader@724a63f4
> For more information see:
> Troubleshooting:  http://bit.ly/GridGain-Troubleshooting
> Documentation Center: http://bit.ly/GridGain-Documentation
> at 
> org.gridgain.grid.marshaller.optimized.GridOptimizedMarshaller.unmarshal(GridOptimizedMarshaller.java:355)
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheMessage.unmarshalValueBytesCollection(GridCacheMessage.java:441)
> at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateRequest.finishUnmarshal(GridNearAtomicUpdateRequest.ja
> va:491)
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:752)
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:208)
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheIoManager.access$200(GridCacheIoManager.java:35)
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:128)
> at 
> org.gridgain.grid.kernal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:648)
> at 
> org.gridgain.grid.kernal.managers.communication.GridIoManager.access$1900(GridIoManager.java:48)
> at 
> org.gridgain.grid.kernal.managers.communication.GridIoManager$6.body(GridIoManager.java:609)
> at org.gridgain.grid.util.worker.GridWorker.run(GridWorker.java:137)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: Failed to load class 
> [name=org.gridgain.examples.datagrid.CacheQueryExample$Person, 
> ctx={1e8b9b15941-0949
> 7dce-3430-4555-8a75-676c0275119c=CachedDeploymentInfo 
> [sndId=09497dce-3430-4555-8a75-676c0275119c, 
> ldrId=1e8b9b15941-09497dce-3430-4555-8a75-676c02751
> 19c, userVer=0, depMode=SHARED, participants=null], 
> 0fe3bb15941-a73e5cd4-c058-46b8-a3d9-cb0f4bbad5c1=CachedDeploymentInfo 
> [sndId=a73e5cd4-c058-46b8-a3
> d9-cb0f4bbad5c1, ldrId=0fe3bb15941-a73e5cd4-c058-46b8-a3d9-cb0f4bbad5c1, 
> userVer=0, depMode=SHARED, participants=null]}]
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.findClass(GridCacheDeploymentManager.java:786)
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.loadClass(GridCacheDeploymentManager.java:743)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:270)
> at 
> org.gridgain.grid.marshaller.optimized.GridOptimizedMarshallerUtils.forName(GridOptimizedMarshallerUtils.java:92)
> at 
>

[jira] [Created] (IGNITE-2296) Apache copyright link opens 404 page

2015-12-26 Thread Sergey Kozlov (JIRA) 
Sergey Kozlov created IGNITE-2296:
-

 Summary: Apache copyright link opens 404 page
 Key: IGNITE-2296
 URL: https://issues.apache.org/jira/browse/IGNITE-2296
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.5
Reporter: Sergey Kozlov
 Fix For: 1.6


Scalar and Java docs pages has text "2015 Copyright © Apache Software 
Foundation" on bottom and it linked on https://apache.org/projects/ignite.html. 
But now it's 404 page and a correct URL is https://ignite.apache.org/



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

[jira] [Created] (IGNITE-2292) Add ability to build .NET platform from Maven.

2015-12-26 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-2292:
---

 Summary: Add ability to build .NET platform from Maven.
 Key: IGNITE-2292
 URL: https://issues.apache.org/jira/browse/IGNITE-2292
 Project: Ignite
  Issue Type: Task
  Components: general, interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
 Fix For: 1.6


Currently build procedure looks as follows:
1) Java is built from Maven
2) .NET is built manually using modules/platforms/dotnet/mkbuild.cmd
3) Docs fo Java, .NET and CPP are built form Maven

Looks like we should intergrate .NET buld into Maven process so that user can 
build the whole product with a single command. E.g.:
{code}mvn clean package [java_build_args] -Dignite.net.docs=true 
-Dignite.net.build =true -Dignite.net.build.x86=true 
-Dignite.net.build.x86.javaHome=[path to x86 JDK]{code}



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

[jira] [Created] (IGNITE-2293) Review CacheContinuousQueryHandler.EntryBuffer concurrency.

2015-12-26 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-2293:
---

 Summary: Review CacheContinuousQueryHandler.EntryBuffer 
concurrency.
 Key: IGNITE-2293
 URL: https://issues.apache.org/jira/browse/IGNITE-2293
 Project: Ignite
  Issue Type: Sub-task
  Components: cache
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
 Fix For: 1.6


EntryBuffer use GridConcurrentSkipListSet, AtomicLong and some non-blocking 
techniques. 
Provided that all operation inside the buffer is very small, most probably 
starightforward and simple critical section with "synchronized" will give 
better performance than current implementation.




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

[jira] [Created] (IGNITE-2294) Implement SQL DML (insert, update, delete) cluses.

2015-12-26 Thread Sergi Vladykin (JIRA) 
Sergi Vladykin created IGNITE-2294:
--

 Summary: Implement SQL DML (insert, update, delete) cluses.
 Key: IGNITE-2294
 URL: https://issues.apache.org/jira/browse/IGNITE-2294
 Project: Ignite
  Issue Type: Wish
Reporter: Sergi Vladykin
Assignee: Vladimir Ershov
 Fix For: 1.6


We need to add parsing for all the listed SQL commands and translate them into 
respective cache operations (putIfAbstent, put, remove).



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

[jira] [Created] (IGNITE-2295) .Net: Provide performance counters

2015-12-26 Thread Pavel Tupitsyn (JIRA) 
Pavel Tupitsyn created IGNITE-2295:
--

 Summary: .Net: Provide performance counters
 Key: IGNITE-2295
 URL: https://issues.apache.org/jira/browse/IGNITE-2295
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn
 Fix For: 1.6


Ignite.NET should be instrumented with Performance Monitor (perfmon) counters 
for diagnostic purposes. We can use existing metrics (cluster, cache, etc) to 
provide custom counters.



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

[jira] [Commented] (IGNITE-944) HTTP REST log command doesn't work

2015-12-26 Thread ASF GitHub Bot (JIRA) 

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

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

GitHub user samaitra opened a pull request:

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

IGNITE-944 HTTP REST log command doesn't work



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

$ git pull https://github.com/samaitra/ignite IGNITE-944

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

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


commit 0beb728f89e207652d29d887089ab571d58d
Author: samaitra 
Date:   2015-12-26T21:46:36Z

IGNITE-944 HTTP REST log command doesn't work




> HTTP REST log command doesn't work
> --
>
> Key: IGNITE-944
> URL: https://issues.apache.org/jira/browse/IGNITE-944
> Project: Ignite
>  Issue Type: Bug
>  Components: general, newbie
>Affects Versions: sprint-5
>Reporter: Sergey Kozlov
>Assignee: Saikat Maitra
>
> Request http://localhost:8080/ignite?cmd=log=1=0 returns following
> {noformat}
> {"error":"Failed to find registered handler for command: 
> LOG","response":null,"sessionToken":"","successStatus":1}
> {noformat}



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

[jira] [Assigned] (IGNITE-944) HTTP REST log command doesn't work

2015-12-26 Thread Saikat Maitra (JIRA) 

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

Saikat Maitra reassigned IGNITE-944:


Assignee: Saikat Maitra  (was: Chandresh Pancholi)

> HTTP REST log command doesn't work
> --
>
> Key: IGNITE-944
> URL: https://issues.apache.org/jira/browse/IGNITE-944
> Project: Ignite
>  Issue Type: Bug
>  Components: general, newbie
>Affects Versions: sprint-5
>Reporter: Sergey Kozlov
>Assignee: Saikat Maitra
>
> Request http://localhost:8080/ignite?cmd=log=1=0 returns following
> {noformat}
> {"error":"Failed to find registered handler for command: 
> LOG","response":null,"sessionToken":"","successStatus":1}
> {noformat}



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