[GitHub] ignite pull request: IGNITE-1690 : Re-enabled test.

2016-05-24 Thread ilantukh 
GitHub user ilantukh opened a pull request:

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

IGNITE-1690 : Re-enabled test.



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

$ git pull https://github.com/ilantukh/ignite ignite-1690

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

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


commit 560bb36f7185baac8c4ea8c49e7a415e6bf134f4
Author: Ilya Lantukh 
Date:   2016-05-24T23:17:00Z

ignite-1690 : Re-enabled test.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1690 testing.

2016-05-24 Thread ilantukh 
Github user ilantukh closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Interested in this ticket IGNITE-2344

2016-05-24 Thread Dmitriy Setrakyan 
Hi Saikat,

Looks like this ticket was unassigned, so feel free to start on it. Feel
free to send your questions here.

D.

On Tue, May 24, 2016 at 10:34 AM, Saikat Maitra 
wrote:

> Hello,
>
> I am interested to pick up this ticket and wanted to know if anyone already
> started working on it.
>
> https://issues.apache.org/jira/browse/IGNITE-2344 - WebSessionFilter
> doesn't support session ID renewal
>
>
> Regards
> Saikat
>

Re: [apache/ignite] [IGNITE-2929] IgniteContext should not have type parameters (#740)

2016-05-24 Thread Alexey Goncharuk 
Folks,

The PR looks good to me. There is one concern - even though the type
parameters were placed to IgniteContext by mistake, removing them will
break backward compatibility. Are we ok with that?

Val, can you comment?

2016-05-21 8:32 GMT-07:00 MaBiao :

> @agoncharuk  Would you please help me to
> review this PR?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub
> 
>

[GitHub] ignite pull request: Ignite 3183

2016-05-24 Thread avinogradovgg 
GitHub user avinogradovgg opened a pull request:

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

Ignite 3183



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

$ git pull https://github.com/gridgain/apache-ignite ignite-3183

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

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


commit 09f978234b6062afa1e1658d5a6439365a856aca
Author: sboikov 
Date:   2016-01-14T11:42:44Z

Merge remote-tracking branch 'origin/ignite-1.5.4' into ignite-1.5.4

commit 30043e7892d0b52dc851ce5ec79c7eb3b7cc44fb
Author: Denis Magda 
Date:   2016-01-14T13:02:50Z

Added release notes

commit cc3db35925698f1670a8bf1c6a1830c0c9b51290
Author: vershov 
Date:   2016-01-14T14:21:56Z

IGNITE-2032 Unwind undeploys in preloader - Fixes #369.

Signed-off-by: Alexey Goncharuk 

commit a5c85ca7749ae90af2e4a29e2162713b480e40fa
Author: Valentin Kulichenko 
Date:   2016-01-15T06:58:41Z

Update notifier fixes

commit 8f32a29c5a7b28b7e1173582f4c7cef5b6d73b27
Author: Ignite Teamcity 
Date:   2016-01-15T11:00:29Z

1.5.4-SNAPSHOT

commit 6482dc80bf9cdf7aa4f592d9266c6745211b1c4c
Author: sboikov 
Date:   2016-01-15T12:15:02Z

ignite-2386 Fixed DiscoverManager to do not increase minor topology version 
if exchange is not triggered.
(cherry picked from commit d881417)

commit 4ba6574dfa8077f8de23c8c2663826f81c7fd187
Author: sboikov 
Date:   2016-01-18T15:15:04Z

ignite-1811 Optimized cache 'get' on affinity node.
(cherry picked from commit 83b2bf5e1f287dc83343945b0e47b83ee7724a8e)

Conflicts:

modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridPartitionedGetFuture.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/IgniteCacheStoreCollectionTest.java

commit 4b31f4e66c15003cee866a6e5660257346c16c1c
Author: sboikov 
Date:   2016-01-18T15:05:37Z

ignite-1811 Optimized cache 'get' on affinity node.
(cherry picked from commit 83b2bf5)

commit 1cf14fcff58c51a628df6309f05be7f0b840d5f8
Author: Pavel Tupitsyn 
Date:   2015-12-30T10:51:32Z

IGNITE-2228: .NET: Compute futures could be cancelled.

commit 2f292788cde807d5f1c80cf9fcb8b29cd4e5ee35
Author: Pavel Tupitsyn 
Date:   2016-01-18T10:01:43Z

IGNITE-2228: Platform compute futures cancellation support. This closes 
#394.

commit 1f5b4a3c478cdf4049af9600c7abe588c3d226fc
Author: vozerov-gridgain 
Date:   2016-01-18T14:24:18Z

.NET: IgniteFutureCancelledException is marked as serializable.

commit 03148776476f21e542640c204fc97508cde916fc
Author: nikolay_tikhonov 
Date:   2016-01-18T17:41:53Z

IGNITE-2384 Fixed "Notification missed in continuous query".

commit 612bcb6b4011f99d98c39196173ce7fa60862394
Author: sboikov 
Date:   2016-01-19T12:30:53Z

ignite-1.5.4 Pass currently written message class to MessageWriter.

commit 5ba47a03411f507d9db661f83b8fe487b77bec1a
Author: Pavel Tupitsyn 
Date:   2016-01-20T10:48:41Z

IGNITE-2414 .NET: TestWithExpiryPolicy is split into two parts: one is 
fine, another one is muted due to IGNITE-1423.

commit bfaf1a634b82bf2666c79bb8f54ce71797d9a778
Author: Denis Magda 
Date:   2016-01-20T10:48:47Z

Fixed queryEntities initialization from a default config

commit d0e763cbfbf7f915c942b90901678eba4abde138
Author: Anton Vinogradov 
Date:   2016-01-20T11:51:36Z

G-10964

commit 6577f1145eb67e505d69314250534f3b51ae2780
Author: Alexey Kuznetsov 
Date:   2016-01-20T14:42:04Z

Fixed Visor tasks (cherry picked from commit c77fc84).

commit e0ae5248064e22cc0537f22fc5daf24142390194
Author: Alexey Kuznetsov 
Date:   2016-01-21T05:31:01Z

Fixed Visor tasks (cherry picked from commit bccd459).

commit d5a5f6aa8dc193bec4307947d7b241b3c4f1397e
Author: Alexey Kuznetsov 
Date:   2016-01-21T05:40:15Z

Fixed Visor tasks.
(cherry picked from commit ba93717)

commit 0222978a64e00b015a3e0f737ba9a96c72d5f0fe
Author: sboikov 
Date:   2016-01-21T08:45:27Z

Added initialization of 'storeKeepBinary' flag for cache configurations 
received on discovery.
(cherry picked from commit d2f84d1)

commit 782e7438f7e46a87382da5ca07c1e2bb69a14d79
Author: Alexey Goncharuk 
Date:   2016-01-21T09:17:43Z

Init simple value type if it was not set for a cache configuration received 
on

Interested in this ticket IGNITE-2344

2016-05-24 Thread Saikat Maitra 
Hello,

I am interested to pick up this ticket and wanted to know if anyone already
started working on it.

https://issues.apache.org/jira/browse/IGNITE-2344 - WebSessionFilter
doesn't support session ID renewal


Regards
Saikat

[GitHub] ignite pull request: IGNITE-3189 .NET: TestCallJavaService fails o...

2016-05-24 Thread ptupitsyn 
GitHub user ptupitsyn opened a pull request:

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

IGNITE-3189 .NET: TestCallJavaService fails on TC



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

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

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

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


commit 3baa390c95630f4287e77114ddbad9a3d353b938
Author: Pavel Tupitsyn 
Date:   2016-05-24T16:03:25Z

wip

commit 7604bf522a03a6a31e3e3fffad7167e499f2ede8
Author: Pavel Tupitsyn 
Date:   2016-05-24T16:05:47Z

Disable all tests except services




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-3190) OffHeap cache metrics do not detected get from OffHeap

2016-05-24 Thread Vladislav Pyatkov (JIRA) 
Vladislav Pyatkov created IGNITE-3190:
-

 Summary: OffHeap cache metrics do not detected get from OffHeap
 Key: IGNITE-3190
 URL: https://issues.apache.org/jira/browse/IGNITE-3190
 Project: Ignite
  Issue Type: Bug
Reporter: Vladislav Pyatkov
Assignee: Vladislav Pyatkov


Simple configuration cache with OffHeap tiered (statistics must be enabled) 
never increase of get from OffHeap (CacheMetrics#getOffHeapGets always 0)

{code}
cache.put(46744, "val 46744");
cache.get(46744);
{code}

{noforamt}
016-05-24 14:19:31 INFO  ServerNode:78 - Swap put 0 get 0 (0, 0) entries count 0
2016-05-24 14:19:31 INFO  ServerNode:81 - OffHeap put 1 get 0 (0, 0) entries 
count 1
2016-05-24 14:19:31 INFO  ServerNode:84 - OnHeap put 1 get 1 (1, 0)
{noformat}



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

[jira] [Created] (IGNITE-3189) .NET: TestCallJavaService fails on TC

2016-05-24 Thread Pavel Tupitsyn (JIRA) 
Pavel Tupitsyn created IGNITE-3189:
--

 Summary: .NET: TestCallJavaService fails on TC
 Key: IGNITE-3189
 URL: https://issues.apache.org/jira/browse/IGNITE-3189
 Project: Ignite
  Issue Type: Test
  Components: platforms
Affects Versions: 1.7
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.7


Only fails in sync mode.



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

Re: About web console and web agent

2016-05-24 Thread Alexey Kuznetsov 
Hi!

>> I would like to ask, Web Console and Web Agent module,how to
install,config and use? Are the documents related is OK?

What are you trying to achieve?

 If you want to use Web Conosle - you may simply go to GridGain hosted
https://console.gridgain.com/
Register and give a try.

If you want to start Web Console locally - read
https://github.com/apache/ignite/blob/master/modules/web-console/DEVNOTES.txt
And follow instructions.

Hope that helps.


Alexey Kuznetsov

Re: Cache metrics return incorrect values

2016-05-24 Thread Denis Magda 
Hi Vlad,

In my understanding this should work or implemented this way for OFFHEAP_TIRED 
cache.

CacheMetrics.getCacheEvictions - incremented on every put & get operation 
because an entry “goes through” heap memory and evicted from there when it’s no 
longer needed (usually at the end of get or put operation).

CacheMetrics.getOffHeapGets - should be incremented every time the off-heap 
layer is accessed for a particular key. This can be an ordinary cache.get() 
call or during a cache.put() that unswaps an entry before the new value is put. 
In my understanding you can increase this statistics exactly in this method - 
GridCacheSwapManager#readOffheapPointer.

CacheMetrics.getOffHeapPuts - should be incremented every time a put operations 
happens and an entry is moved to off heap.

—
Denis

> On May 24, 2016, at 2:47 PM, Vladislav Pyatkov  wrote:
> 
> I try to understand how statistics work and fixe some problem.
> I first case:
> cache.put(46744, "val 46744");
> cache.get(46744);
> In statistic I see:
> 2016-05-24 14:19:31 INFO  ServerNode:78 - Swap put 0 get 0 (0, 0) entries
> count 0
> 2016-05-24 14:19:31 INFO  ServerNode:81 - OffHeap put 1 get 0 (0, 0)
> entries count 1
> 2016-05-24 14:19:31 INFO  ServerNode:84 - OnHeap put 1 get 1 (1, 0)
> 
> In brackets Hit and Miss values.
> 
> But I asume OffHeap get must to be one, because cache configured as
> OFFHEAP_TIERED and swapEnabled - false.
> 
> My investigation has lead to method
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager#readOffheapPointer.
> The method read only pointer from heap, but not get bytes of value and not
> increase any statistic.
> If each receive pointer increase statistic (OffHeap get I mean), then each
> OffHeap put will increased OffHeap get, because readOffheapPointer take
> place on OffHeap put.
> 
> The thing confuses my:
> Has any rules metrics works?
> Where works with metrics value must take place?

About web console and web agent

2016-05-24 Thread 李玉珏 

Hi:

I would like to ask, Web Console and Web Agent module,how to 
install,config and use? Are the documents related is OK?



在 16/5/18 00:23, Alexey Kuznetsov 写道:

First version of Web Console merged to ignite-1.6.

On Tue, May 17, 2016 at 9:31 PM, Pavel Tupitsyn 
wrote:


All done from .NET side as well.

On Tue, May 17, 2016 at 5:28 PM, Denis Magda  wrote:


Hi,

Reviewed and merged IGNITE-2394 (Cache loading from storage is called on
client nodes).
Finalized and merged IGNITE-3098 (UTF-16 surrogate pairs are not properly
serialized by BinaryMarshaller).

These are last things from my side for 1.6.

—
Denis


On May 17, 2016, at 11:09 AM, Pavel Tupitsyn 

wrote:

Hi,

Please note that documentation tickets do not hold the release

(IGNITE-3101

and subtasks).
Other than that, in .NET, recently emerged 'IGNITE-3139 UTF surrogates'

is

expected to be merged today.

Pavel.


On Tue, May 17, 2016 at 10:20 AM, Semyon Boikov 
wrote:


In 1.6 we implemented 'late affinity assignment' mode (see
https://issues.apache.org/jira/browse/IGNITE-324 and
IgniteConfiguration.isLateAffinityAssignment)

On Mon, May 16, 2016 at 7:03 PM, Alexey Kuznetsov <

akuznet...@gridgain.com

wrote:


https://issues.apache.org/jira/browse/IGNITE-2832
"CacheJdbcPojoStoreFactory.dataSource property should be replaced

with

Factory"
Reviewed by Semen and merged into ignite-1.6


On Mon, May 16, 2016 at 10:56 PM, Igor Sapego 
wrote:


Hi, here is a list of major C++ features included in 1.6:

* ODBC driver for Ignite (IGNITE-1786)
* Transactions API for CPP client (IGNITE-2805)
* Simplified Autotools build process (IGNITE-2823)
* Date and Timestamp types implementation (IGNITE-)

Best Regards,
Igor

On Fri, May 13, 2016 at 4:10 PM, Artem Shutak  and has

been

merged to 1.6.

Also, I'm going to finish the following issues before 1.6 relase

(they

all

almost done/under review/waiting for TC):
[1] IGNITE-3056 Service implementation class is required even if

it's

not

expected to be deployed on current node

[2] IGNITE-2921 ScanQueries over local partitions are not optimal

[3] IGNITE-2899 BinaryObject is deserialized before getting passed

to

CacheInterceptor <

https://issues.apache.org/jira/browse/IGNITE-2899>

Thanks,
-- Artem --

On Fri, May 13, 2016 at 5:26 AM, Dmitriy Setrakyan <

dsetrak...@apache.org>

wrote:


On Thu, May 12, 2016 at 9:08 AM, Alexey Kuznetsov <

akuznet...@gridgain.com

wrote:


Also I already implemented "CacheJdbcPojoStoreFactory.dataSource

property

should be replaced with Factory"
https://issues.apache.org/jira/browse/IGNITE-2832

And I think it will be cool to merge into ignite-1.6
But I need a review.

Val, could you take a look? You may compare branch ignite-2832

with

master.
To my knowledge, Val is traveling this weekend, so it would be

nice

if

someone else could pick it up.



On Thu, May 12, 2016 at 10:26 PM, Alexey Kuznetsov <
akuznet...@gridgain.com>
wrote:


I'm going to merge Ignite Web Console into ignite-1.6

https://issues.apache.org/jira/browse/IGNITE-843

On Thu, May 12, 2016 at 9:30 PM, Igor Sapego <

isap...@gridgain.com

wrote:

There is one more C++ ticket I'd like to be included in 1.6 -

IGNITE-3113

[1].

[1] - https://issues.apache.org/jira/browse/IGNITE-3113

Best Regards,
Igor

On Thu, May 12, 2016 at 3:44 PM, Pavel Tupitsyn <

ptupit...@gridgain.com

wrote:


And one more .NET ticket: IGNITE-3118 .NET:
CacheConfiguration.EvictionPolicy

On Thu, May 12, 2016 at 12:20 PM, Denis Magda <

dma...@gridgain.com>

wrote:

Yakov,

Processed all the tickets mentioned in 1. The only one is

left

is

the

following
https://issues.apache.org/jira/browse/IGNITE-2954 <
https://issues.apache.org/jira/browse/IGNITE-2954>

Alex G. I do remember you’ve fixed IGNITE-2954 before.

Have

you

merged it

into the master? Is the fix in ignite-1.6 already?

—
Denis


On May 11, 2016, at 8:56 AM, Yakov Zhdanov <

yzhda...@apache.org

wrote:

Guys,

I moved most of the tickets to 1.7 version.

I had to leave the following tickets untouched (~80

tickets):

1. labeled with - community important performance

customer -

Denis,

Vladimir and Val can you please review these tickets and

move

non-urgent

ones. You can use query below
2. with status "in progress". Please everyone having

such

tickets

move

it

yourself or finish it in 1.6
3. with status "patch available". Committers, please

split

the

reviews

and

let's include checked/tested fixes to 1.6. Others should

be

moved.

Sam, can you please review and merge -
https://issues.apache.org/jira/browse/IGNITE-2744 -

Optimize

"unwindEvict"

call in

[GitHub] ignite pull request: 7.5.23 2941 2942

2016-05-24 Thread avinogradovgg 
GitHub user avinogradovgg opened a pull request:

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

7.5.23 2941 2942



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

$ git pull https://github.com/gridgain/apache-ignite 
gridgain-7.5.23-2941-2942

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

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


commit fc48a8429a84ef6c87ed3225a218d7d3ae617e14
Author: vozerov-gridgain 
Date:   2016-01-08T07:48:42Z

Merge branch 'ignite-1.5.2' into ignite-1.5.3

commit 86740cefe212ed0f506d81056dd8e76de9a31e4f
Author: Ignite Teamcity 
Date:   2016-01-08T09:32:11Z

1.5.3-SNAPSHOT

commit 92229d2a6c6ef86772a62cb52b3aa07a55c99d89
Author: sboikov 
Date:   2016-01-13T05:56:34Z

ignite-2359 Added locking for files used by MarshallerContextImpl. (cherry 
picked from commit 1d8c4e2)

commit 2e4ce585d5f54502c6511d3425b1cd5fbf0a7f4f
Author: Ignite Teamcity 
Date:   2016-01-13T10:37:33Z

1.5.4-SNAPSHOT

commit 6e5f9f0c7d4c86773b1f0cd5c5a673acb58c86c2
Author: Denis Magda 
Date:   2016-01-13T11:42:27Z

Changed year to 2016 in Copyrights

commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583
Author: Alexey Goncharuk 
Date:   2016-01-13T13:47:32Z

IGNITE-2365 - Notify policy if swap or offheap is enabled and rebalanced 
entry was not preloaded.
IGNITE-2099 - Fixing custom collections.
This closes #396

commit 86c2ba2a601e82b824cf17422683e5398a4d8c7d
Author: sboikov 
Date:   2016-01-13T15:40:08Z

ignite-2350 Pass update notifier flag in discovery data (all cluster nodes 
will have the same notifier status as first cluster node)
(cherry picked from commit 7175a42)

commit e1a494df400fc37ca04e8d88d1cf20bca02607b4
Author: sboikov 
Date:   2016-01-14T11:16:33Z

Renamed fields to change fields write order (to preserve backward 
compatibility).
(cherry picked from commit 2a4adf5)

commit 09f978234b6062afa1e1658d5a6439365a856aca
Author: sboikov 
Date:   2016-01-14T11:42:44Z

Merge remote-tracking branch 'origin/ignite-1.5.4' into ignite-1.5.4

commit 30043e7892d0b52dc851ce5ec79c7eb3b7cc44fb
Author: Denis Magda 
Date:   2016-01-14T13:02:50Z

Added release notes

commit cc3db35925698f1670a8bf1c6a1830c0c9b51290
Author: vershov 
Date:   2016-01-14T14:21:56Z

IGNITE-2032 Unwind undeploys in preloader - Fixes #369.

Signed-off-by: Alexey Goncharuk 

commit a5c85ca7749ae90af2e4a29e2162713b480e40fa
Author: Valentin Kulichenko 
Date:   2016-01-15T06:58:41Z

Update notifier fixes

commit 8f32a29c5a7b28b7e1173582f4c7cef5b6d73b27
Author: Ignite Teamcity 
Date:   2016-01-15T11:00:29Z

1.5.4-SNAPSHOT

commit 6482dc80bf9cdf7aa4f592d9266c6745211b1c4c
Author: sboikov 
Date:   2016-01-15T12:15:02Z

ignite-2386 Fixed DiscoverManager to do not increase minor topology version 
if exchange is not triggered.
(cherry picked from commit d881417)

commit 4ba6574dfa8077f8de23c8c2663826f81c7fd187
Author: sboikov 
Date:   2016-01-18T15:15:04Z

ignite-1811 Optimized cache 'get' on affinity node.
(cherry picked from commit 83b2bf5e1f287dc83343945b0e47b83ee7724a8e)

Conflicts:

modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridPartitionedGetFuture.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/IgniteCacheStoreCollectionTest.java

commit 4b31f4e66c15003cee866a6e5660257346c16c1c
Author: sboikov 
Date:   2016-01-18T15:05:37Z

ignite-1811 Optimized cache 'get' on affinity node.
(cherry picked from commit 83b2bf5)

commit 1cf14fcff58c51a628df6309f05be7f0b840d5f8
Author: Pavel Tupitsyn 
Date:   2015-12-30T10:51:32Z

IGNITE-2228: .NET: Compute futures could be cancelled.

commit 2f292788cde807d5f1c80cf9fcb8b29cd4e5ee35
Author: Pavel Tupitsyn 
Date:   2016-01-18T10:01:43Z

IGNITE-2228: Platform compute futures cancellation support. This closes 
#394.

commit 1f5b4a3c478cdf4049af9600c7abe588c3d226fc
Author: vozerov-gridgain 
Date:   2016-01-18T14:24:18Z

.NET: IgniteFutureCancelledException is marked as serializable.

commit 03148776476f21e542640c204fc97508cde916fc
Author: nikolay_tikhonov 
Date:   2016-01-18T17:41:53Z

IGNITE-2384 Fixed "Notification missed in continuous query".

commit 612bcb6b4011f99d98c39196173ce7fa60862394
Author: sboikov

Cache metrics return incorrect values

2016-05-24 Thread Vladislav Pyatkov 
I try to understand how statistics work and fixe some problem.
I first case:
cache.put(46744, "val 46744");
cache.get(46744);
In statistic I see:
2016-05-24 14:19:31 INFO  ServerNode:78 - Swap put 0 get 0 (0, 0) entries
count 0
2016-05-24 14:19:31 INFO  ServerNode:81 - OffHeap put 1 get 0 (0, 0)
entries count 1
2016-05-24 14:19:31 INFO  ServerNode:84 - OnHeap put 1 get 1 (1, 0)

In brackets Hit and Miss values.

But I asume OffHeap get must to be one, because cache configured as
OFFHEAP_TIERED and swapEnabled - false.

My investigation has lead to method
org.apache.ignite.internal.processors.cache.GridCacheSwapManager#readOffheapPointer.
The method read only pointer from heap, but not get bytes of value and not
increase any statistic.
If each receive pointer increase statistic (OffHeap get I mean), then each
OffHeap put will increased OffHeap get, because readOffheapPointer take
place on OffHeap put.

The thing confuses my:
Has any rules metrics works?
Where works with metrics value must take place?

[GitHub] ignite pull request: IGNITE-2865 Continuous query event passed to ...

2016-05-24 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Integration with Apache Apex (incubating)

2016-05-24 Thread sbiradar1975 
Hello D,
I landed on this thread while searching for the Apache Ignite integration
with Apex. Is there an update on this topic somewhere that I might missing?  

Thanks!



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Integration-with-Apache-Apex-incubating-tp7535p9069.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

IgniteConfiguration.gridName is very confusing

2016-05-24 Thread Pavel Tupitsyn 
Igniters,

We have got a TON of questions on gridName property. Everyone thinks that
clusters are formed based on the gridName, that is, nodes with the same
grid name will join one cluster, and nodes with a different name will be in
a separate cluster.

I suggest to deprecate this property and add instanceName instead.

Thoughts?

Pavel.

[jira] [Created] (IGNITE-3188) Binary marshaller doesn't unmarshal a void type

2016-05-24 Thread Nikolay Tikhonov (JIRA) 
Nikolay Tikhonov created IGNITE-3188:


 Summary: Binary marshaller doesn't unmarshal a void type
 Key: IGNITE-3188
 URL: https://issues.apache.org/jira/browse/IGNITE-3188
 Project: Ignite
  Issue Type: Bug
  Components: cache, important
Affects Versions: 1.6
Reporter: Nikolay Tikhonov


The following code snippet failed with binary marshaller:
{{
BinaryMarshaller marsh = 
(BinaryMarshaller)ignite.configuration().getMarshaller();
Map map = new HashMap<>();
map.put(Void.class, Void.TYPE);
byte[] marshal = marsh.marshal(map);
marsh.unmarshal(marshal, null);
}}

Got expcetion:

{{
class org.apache.ignite.binary.BinaryObjectException: Failed to unmarshal 
object with optimized marshaller
at 
org.apache.ignite.internal.binary.BinaryUtils.doReadOptimized(BinaryUtils.java:1555)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1631)
at 
org.apache.ignite.internal.binary.BinaryUtils.doReadObject(BinaryUtils.java:1568)
at 
org.apache.ignite.internal.binary.BinaryUtils.deserializeOrUnmarshal(BinaryUtils.java:1915)
at 
org.apache.ignite.internal.binary.BinaryUtils.doReadMap(BinaryUtils.java:1899)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1596)
at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
at 
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
at 
org.apache.ignite.internal.processors.cache.BinarySerializationQuerySelfTest.testPlain(BinarySerializationQuerySelfTest.java:181)
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:1723)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1661)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to find class 
with given class loader for unmarshalling (make sure same versions of all 
classes are available on all nodes or enable peer-class-loading): 
sun.misc.Launcher$AppClassLoader@36d98810
at 
org.apache.ignite.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:225)
at 
org.apache.ignite.internal.binary.BinaryUtils.doReadOptimized(BinaryUtils.java:1552)
... 17 more
Caused by: java.lang.ClassNotFoundException: void
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:274)
at 
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8213)
at 
org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
at 
org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:270)
at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readClass(OptimizedObjectInputStream.java:353)
at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:364)
at 
org.apache.ignite.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:219)
... 18 more
}}



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

[GitHub] ignite pull request: ignite-2620

2016-05-24 Thread sboikov 
Github user sboikov closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [IGNITE-2323] Improvments for http client

2016-05-24 Thread chandresh pancholi 
Sure.

Thank you Denis.
On May 24, 2016 1:00 PM, "Denis Magda"  wrote:

> Chandresh,
>
> As I see development of NodeJS integration is presently postponed by the
> community and bunch of efforts is needed to make a decision on where to
> move with this.
>
> I would suggest you picking up another ticket for now.
>
> —
> Denis
>
> > On May 21, 2016, at 7:24 PM, chandresh pancholi <
> chandreshpancholi...@gmail.com> wrote:
> >
> > @Andery,Sam can you guys provide some starting pointer for me?
> >
> > Thanks
> >
> > On Sat, May 14, 2016 at 11:07 AM, Denis Magda 
> wrote:
> >
> >> Hi Chandresh,
> >>
> >> From what I see that task is planned to be done as a part of NodeJS
> >> integration. Andrey Gura and Sam Boikov should be working on that
> >> integration.
> >>
> >> Andrey, Sam, can you provide more details in the ticket so that
> Chandresh
> >> can start working on it?
> >>
> >> --
> >> Denis
> >>
> >>
> >> On Sat, May 14, 2016 at 6:31 AM, chandresh pancholi <
> >> chandreshpancholi...@gmail.com> wrote:
> >>
> >>> Hi Igniters,
> >>>
> >>> I know you all busy with your respective work. But can anyone help me
> out
> >>> with this ticket?
> >>> There aren't much information on JIRA.
> >>>
> >>> Thanks
> >>>
> >>> On Wed, May 11, 2016 at 12:52 PM, chandresh pancholi <
> >>> chandreshpancholi...@gmail.com> wrote:
> >>>
>  Hi Dmitriy,
> 
>  I have assigned it already to myself :) :) .
>  I have been busy with office work lately and didn't get a chance to
>  contribute.
> 
>  Please provide any input regarding ignite-2323 so that it will help me
> >> to
>  start working on it.
> 
>  Thanks
> 
> 
>  On Wed, May 11, 2016 at 12:45 PM, Dmitriy Setrakyan <
>  dsetrak...@gridgain.com> wrote:
> 
> > Hi Chandresh,
> >
> > Welcome to the Ignite community!
> >
> > Please review the following sections on our Wiki and Website to get
> > familiar with the development process:
> >
> > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > https://ignite.apache.org/community/contribute.html#contribute
> >
> > Also, please let us know your Jira username, so we could add you to
> >> the
> > list of Ignite contributors. This way you will be able to assign this
> > ticket to yourself.
> >
> > Looking forward to your contributions.
> >
> > Thanks,
> > D.
> >
> > On Tue, May 10, 2016 at 11:50 PM, chandresh pancholi <
> > chandreshpancholi...@gmail.com> wrote:
> >
> >> Hi,
> >>
> >> I would like to work on ticket Improvments for http client
> > [IGNITE-2323].
> >>
> >> Please suggest where to start or whats the entry point ?
> >>
> >> Thanks in advance.
> >>
> >> --
> >> Chandresh Pancholi
> >> Senior Software Engineer
> >> Flipkart.com
> >> Email-id:chandresh.panch...@flipkart.com
> >> Contact:08951803660
> >>
> >
> 
> 
> 
>  --
>  Chandresh Pancholi
>  Senior Software Engineer
>  Flipkart.com
>  Email-id:chandresh.panch...@flipkart.com
>  Contact:08951803660
> 
> >>>
> >>>
> >>>
> >>> --
> >>> Chandresh Pancholi
> >>> Senior Software Engineer
> >>> Flipkart.com
> >>> Email-id:chandresh.panch...@flipkart.com
> >>> Contact:08951803660
> >>>
> >>
> >
> >
> >
> > --
> > Chandresh Pancholi
> > Senior Software Engineer
> > Flipkart.com
> > Email-id:chandresh.panch...@flipkart.com
> > Contact:08951803660
>
>

Re: [IGNITE-2323] Improvments for http client

2016-05-24 Thread Denis Magda 
Chandresh,

As I see development of NodeJS integration is presently postponed by the 
community and bunch of efforts is needed to make a decision on where to move 
with this.

I would suggest you picking up another ticket for now.

—
Denis

> On May 21, 2016, at 7:24 PM, chandresh pancholi 
>  wrote:
> 
> @Andery,Sam can you guys provide some starting pointer for me?
> 
> Thanks
> 
> On Sat, May 14, 2016 at 11:07 AM, Denis Magda  wrote:
> 
>> Hi Chandresh,
>> 
>> From what I see that task is planned to be done as a part of NodeJS
>> integration. Andrey Gura and Sam Boikov should be working on that
>> integration.
>> 
>> Andrey, Sam, can you provide more details in the ticket so that Chandresh
>> can start working on it?
>> 
>> --
>> Denis
>> 
>> 
>> On Sat, May 14, 2016 at 6:31 AM, chandresh pancholi <
>> chandreshpancholi...@gmail.com> wrote:
>> 
>>> Hi Igniters,
>>> 
>>> I know you all busy with your respective work. But can anyone help me out
>>> with this ticket?
>>> There aren't much information on JIRA.
>>> 
>>> Thanks
>>> 
>>> On Wed, May 11, 2016 at 12:52 PM, chandresh pancholi <
>>> chandreshpancholi...@gmail.com> wrote:
>>> 
 Hi Dmitriy,
 
 I have assigned it already to myself :) :) .
 I have been busy with office work lately and didn't get a chance to
 contribute.
 
 Please provide any input regarding ignite-2323 so that it will help me
>> to
 start working on it.
 
 Thanks
 
 
 On Wed, May 11, 2016 at 12:45 PM, Dmitriy Setrakyan <
 dsetrak...@gridgain.com> wrote:
 
> Hi Chandresh,
> 
> Welcome to the Ignite community!
> 
> Please review the following sections on our Wiki and Website to get
> familiar with the development process:
> 
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> https://ignite.apache.org/community/contribute.html#contribute
> 
> Also, please let us know your Jira username, so we could add you to
>> the
> list of Ignite contributors. This way you will be able to assign this
> ticket to yourself.
> 
> Looking forward to your contributions.
> 
> Thanks,
> D.
> 
> On Tue, May 10, 2016 at 11:50 PM, chandresh pancholi <
> chandreshpancholi...@gmail.com> wrote:
> 
>> Hi,
>> 
>> I would like to work on ticket Improvments for http client
> [IGNITE-2323].
>> 
>> Please suggest where to start or whats the entry point ?
>> 
>> Thanks in advance.
>> 
>> --
>> Chandresh Pancholi
>> Senior Software Engineer
>> Flipkart.com
>> Email-id:chandresh.panch...@flipkart.com
>> Contact:08951803660
>> 
> 
 
 
 
 --
 Chandresh Pancholi
 Senior Software Engineer
 Flipkart.com
 Email-id:chandresh.panch...@flipkart.com
 Contact:08951803660
 
>>> 
>>> 
>>> 
>>> --
>>> Chandresh Pancholi
>>> Senior Software Engineer
>>> Flipkart.com
>>> Email-id:chandresh.panch...@flipkart.com
>>> Contact:08951803660
>>> 
>> 
> 
> 
> 
> -- 
> Chandresh Pancholi
> Senior Software Engineer
> Flipkart.com
> Email-id:chandresh.panch...@flipkart.com
> Contact:08951803660

[jira] [Created] (IGNITE-3187) IGFS: Print acceptable IGFS endpoints to the console on node start.

2016-05-24 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-3187:
---

 Summary: IGFS: Print acceptable IGFS endpoints to the console on 
node start.
 Key: IGNITE-3187
 URL: https://issues.apache.org/jira/browse/IGNITE-3187
 Project: Ignite
  Issue Type: Improvement
  Components: hadoop, IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.7


*Problem*
When user starts a node with IGFS, he need to know it's endpoint to be used in 
URI's (e.g. "igfs://igfs@"). There are non-trivial rules no how the scheme is 
formed, and sometime it is difficult to understand which scheme to use.

*Solution*
Let's print acceptable schemes to the console on node start.



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