[GitHub] ignite pull request #1016: IGNITE-2881 : SPI queries not working

2016-08-31 Thread AMashenkov
GitHub user AMashenkov opened a pull request:

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

IGNITE-2881 : SPI queries not working

... fixed

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

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

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

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


commit 30aa287b881d4f9dc3fd5eec9840eab8d9a20828
Author: sboikov 
Date:   2016-05-24T13:57:20Z

ignite-2620 Skip empty entries in GridCacheMapEntry.onTtlExpired
(cherry picked from commit 6fc274a)

commit e2db87bb1b6c71d7978af17e9f2005ba1c661ab4
Author: sboikov 
Date:   2016-05-25T07:06:43Z

Added trace logging for entry/offheap updates.
(cherry picked from commit 9b2767f)

commit 6fcc7a41d8676956983792717483318b85781479
Author: MaBiao 
Date:   2016-05-25T09:54:40Z

IGNITE-2538 - IgniteRDD count() and isEmpty() method use IgniteCache API

commit e274d44a37fd1269e7a3a5fe1ee6139fd0b0
Author: Denis Magda 
Date:   2016-05-26T11:57:52Z

IGNITE-3188: Binary marshaller doesn't unmarshal a void type (added tests)

commit 6687e2bfb9627ce08c1c258527e2927606a500ed
Author: Yakov Zhdanov 
Date:   2016-05-13T08:48:00Z

review IGNITE-2708 Need to validate that SPIs are started only once
(cherry picked from commit cd063da)

commit 40a41fc50bdb73d50e2aa13da8203784be98e38a
Author: Yakov Zhdanov 
Date:   2016-05-13T08:59:02Z

reverting review IGNITE-2708 Need to validate that SPIs are started only 
once
(cherry picked from commit bf561e1)

commit d05786d8bfc8177223b6db9a98bd3c8170b6bcf1
Author: Ryan Zhao 
Date:   2016-05-13T09:00:43Z

review IGNITE-2708 Need to validate that SPIs are started only once (commit 
with proper author)
(cherry picked from commit 98338ff)

commit 9d937ca34775f39b46568eb3fca4585ce00a0fb1
Author: Yakov Zhdanov 
Date:   2016-05-13T09:54:01Z

review IGNITE-2708 Need to validate that SPIs are started only once (added 
logic to protect properly started grids)
(cherry picked from commit b8d624a)

commit edc2947d7340cac4a3c90fa726c23d5d47798ab9
Author: vozerov-gridgain 
Date:   2016-05-25T10:07:03Z

IGNITE-3191: IGFS: Improved error logging for operations in dual mode.

commit 2f1747d726da87b67f6c5323b3e64762d56398cb
Author: vozerov-gridgain 
Date:   2016-05-27T11:40:17Z

Merge remote-tracking branch 'upstream/gridgain-7.6.1' into gridgain-7.6.1

commit 1bb8b647264593034659b7db929c2664dec603e1
Author: sboikov 
Date:   2016-05-27T11:21:01Z

ignite-3116 Fixed NodeStoppingException in GridDhtGetFuture.
(cherry picked from commit 303d3ca)

commit 47c575c8696d51b675a16aa260ec9d398e0a68e9
Author: nikolay_tikhonov 
Date:   2016-05-30T09:42:37Z

Added benchmark property file.

commit 00e2dda9a850f74178ee893a3acf74ddc30d4a13
Author: nikolay_tikhonov 
Date:   2016-05-30T11:45:38Z

Updated benchmark property file.

commit a28e16e24adb0a03df959830517db84d2505c481
Author: Vladislav Pyatkov 
Date:   2016-05-31T07:01:46Z

IGNITE-3190: OffHeap cache metrics doesn't work properly for OFFHEAP_TIRED 
mode.
Reviewed and merged by Denis Magda (dma...@gridgain.com)
(cherry picked from commit 7533dfc)

commit 56c605622dbecf71f3ee87cc41a16d2ee87e92d3
Author: vozerov-gridgain 
Date:   2016-05-26T08:15:48Z

IGNITE-3200: Resolved classloader leak.

commit a815067a0e8e7cfc9f49c57efe2b2eba562e9071
Author: vozerov-gridgain 
Date:   2016-05-31T07:23:00Z

IGNITE-3202: Hadoop: Implemented user name mappers.

commit 421cf03b03276d0ab6c32ef6665d547746446dfc
Author: vozerov-gridgain 
Date:   2016-05-31T07:40:24Z

7.5.24: Added missing JavaDocs.

commit 167e47781f65c056b9d273eea52d268bc9a8fa0b
Author: Denis Magda 
Date:   2016-05-31T10:50:06Z

IGNITE-2708: fix tests that don't create unique IndexingSPI per node
(cherry picked from commit f90e424)

commit 21bdf3148f05481d86e77e13b282ac44c6c3a059
Author: vozerov-gridgain 
Date:   2016-05-31T10:54:32Z

Added pacajge info for java.org.apache.ignite.hadoop.util package.

commit 3ca9febeb2bf53d17b6dea739938cff40c5fa67d
Author: vozerov-gridgain 
Date:   2016-05-31T11:03:48Z

Merge remote-tracking branch 'upstream/gridgain-7.6.1' into gridgain-7.6.1

commit f175d3c670025bd619ec347dba2a5c5f68f4cc32
Author: Vladislav Pyatkov 
Date:   2016-06-02T13:14:10Z


[GitHub] ignite pull request #1015: IGNITE-2881 SPI queries not working

2016-08-31 Thread AMashenkov
GitHub user AMashenkov opened a pull request:

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

IGNITE-2881 SPI queries not working

... fixed

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

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

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

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






---
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 #1014: IGNITE-3628: Added fetch page size to configurati...

2016-08-31 Thread isapego
GitHub user isapego opened a pull request:

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

IGNITE-3628: Added fetch page size to configuration params.



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

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

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

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


commit d23936c0251a376dff964c53e51834793e47468c
Author: isapego 
Date:   2016-08-30T15:26:09Z

IGNITE-3628: Benchmark stub.

commit e0b4b44710c0661fef0d4c98aeb02b22275afba1
Author: isapego 
Date:   2016-08-30T15:44:28Z

IGNITE-3628: Adjusted benchmark.

commit 73df311b13aaf648c8edfbf41af65fca2dd3c8b6
Author: isapego 
Date:   2016-08-30T16:45:46Z

IGNITE-3628: Benchmark is ready.

commit 6c75f03b41ae7a587f1039322407147642f8996a
Author: isapego 
Date:   2016-08-30T17:25:04Z

IGNITE-3628: Improved benchmark.

commit dabd86c62e39eb983ef3d198c8b8ee96d2623c84
Author: Andrey Novikov 
Date:   2016-08-31T09:00:19Z

IGNITE-3811 Fixed query for merge with complex key on SQL Server.

commit e960c00574127b489ee6acc3b53b7f468c71aff6
Author: isapego 
Date:   2016-08-31T09:57:26Z

IGNITE-3628: Changed default page size to 1024.

commit 70e69cb7aa08c268b07920838add4a40e28fe25d
Author: isapego 
Date:   2016-08-31T13:47:11Z

IGNITE-3390: Added DSN configuration window.

commit 727edc57bd26f2cdda32f50ea873230402b902df
Author: isapego 
Date:   2016-08-31T14:15:35Z

Merge branch 'ignite-1.6.7' into ignite-3628

commit 72a37710ae3f8ac6fdbfc87bd98f656ac7fc6ea4
Author: isapego 
Date:   2016-08-31T15:30:37Z

IGNITE-3628: Added fetch page size to configuration params.

commit a2961f5fe56a36b996cc54fdb5d46a9cfab61e7c
Author: isapego 
Date:   2016-08-31T16:37:40Z

IGNITE-3628: Added Fetch page size param to configuration dialog.

commit 442dfc2e283da9af43534005076ad97d16b6ad90
Author: isapego 
Date:   2016-08-31T16:50:55Z

IGNITE-3628: Added tests.




---
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.
---


Pull request for IGNITE-3699

2016-08-31 Thread Amir Akhmedov
Hi community,

I raised a pull request [1] Can you please review it?

[1] https://github.com/apache/ignite/pull/1011

Thanks.


[jira] [Created] (IGNITE-3815) CacheJdbcPojoStore.loadCache() should check arguments and fail with appropriate exception message

2016-08-31 Thread Alexey Kuznetsov (JIRA)
Alexey Kuznetsov created IGNITE-3815:


 Summary: CacheJdbcPojoStore.loadCache() should check arguments and 
fail with appropriate exception message
 Key: IGNITE-3815
 URL: https://issues.apache.org/jira/browse/IGNITE-3815
 Project: Ignite
  Issue Type: Task
  Components: cache
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.8


CacheJdbcPojoStore.loadCache() method accepts arguments in following format: 
closure, keyType1, sql1, ..., keyTypeN, sqlN.

We could easily check that keyType1, ..., keyTypeN are configured in store
and throw appropriate exception that will help users to understand what is 
wrong.



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


[jira] [Created] (IGNITE-3814) Unstable results of compute benchmarks

2016-08-31 Thread Ilya Suntsov (JIRA)
Ilya Suntsov created IGNITE-3814:


 Summary: Unstable results of compute benchmarks
 Key: IGNITE-3814
 URL: https://issues.apache.org/jira/browse/IGNITE-3814
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
 Environment: Ubuntu 14.04
jdk 1.7, jdk 1.8
Reporter: Ilya Suntsov


I've run the following compute benchmarks:
* exec-compute
* run-compute
* broad-compute
* apply-compute
and got huge difference between the best and worst results e.g. for 
exec-compute we have the following numbers:
1   1222.38
2   1220.63
3   1044.53
4   1342.39
5   1393.57
5   1064.66

delta between 3-rd and 4-th runs is 28%.
I think we should re-work these benchmarks.



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


Re: Simulating network outages

2016-08-31 Thread Yakov Zhdanov
You can shutdown and then restart (after some sleep) network stack on the
host. I remember doing that on Fedora several years ago for exactly the
same purposes.



--Yakov

2016-08-31 15:21 GMT+03:00 Alexey Goncharuk :

> Hi,
>
> As a starting point you can take a look
> at org.apache.ignite.spi.discovery.tcp.ServerImpl#forceNextNodeFailure
> which forces DiscoverySpi to drop next node from the topology (not sure if
> this is what you need). Another idea is to create a test discovery SPI
> which will terminate all it's threads when a test flag is set. Such nodes
> also should be segmented from the topology.
>
> Yakov, do you have other ideas?
>
> 2016-08-31 0:06 GMT+03:00 Anand Kumar Sankaran  >:
>
> > Hi
> >
> > I am implementing a segmentation resolver to handle split brain
> > scenarios.  I need to simulate network outages to unit test this
> behavior.
> > Any suggestions on how to simulate this?  I see that the TcpDiscoverySpi
> > has timeouts, is there a way to mock TcpDiscoverySpi to think that there
> is
> > a network outage to simulate such conditions?
> >
> > Thanks.
> >
> > --
> > anand
> >
>


[GitHub] ignite pull request #1012: IGNITE-3390: Added DSN configuration window.

2016-08-31 Thread isapego
Github user isapego closed the pull request at:

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


---
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 #1013: IGNITE-3646 IGFS: Local secondary: Support symlin...

2016-08-31 Thread tledkov-gridgain
GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-3646 IGFS: Local secondary: Support symlinks for mkdirs operation.



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

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

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

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


commit dabd86c62e39eb983ef3d198c8b8ee96d2623c84
Author: Andrey Novikov 
Date:   2016-08-31T09:00:19Z

IGNITE-3811 Fixed query for merge with complex key on SQL Server.

commit 684f7af64169912959d1545990c736433494fa32
Author: tledkov-gridgain 
Date:   2016-08-31T13:09:17Z

IGNITE-3646 IGFS: Local secondary: Support symlinks for mkdirs operation.




---
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-3813) High contention on GridCacheMapEntry.obsolete() on loading data to data stremer with composite keys

2016-08-31 Thread Dmitry Karachentsev (JIRA)
Dmitry Karachentsev created IGNITE-3813:
---

 Summary: High contention on GridCacheMapEntry.obsolete() on 
loading data to data stremer with composite keys
 Key: IGNITE-3813
 URL: https://issues.apache.org/jira/browse/IGNITE-3813
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 1.7
Reporter: Dmitry Karachentsev
 Fix For: 1.8


On loading entries with non-primitive key to data streamer too many calls to 
metadata cache which causes high contention on GridCacheMapEntry.

Example thread dump in attachment.



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


[GitHub] ignite pull request #1012: IGNITE-3390: Added DSN configuration window.

2016-08-31 Thread isapego
GitHub user isapego opened a pull request:

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

IGNITE-3390: Added DSN configuration window.



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

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

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

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


commit dabd86c62e39eb983ef3d198c8b8ee96d2623c84
Author: Andrey Novikov 
Date:   2016-08-31T09:00:19Z

IGNITE-3811 Fixed query for merge with complex key on SQL Server.

commit 5477d3c1e342adda9fc03bc6b4d8811885ae4664
Author: isapego 
Date:   2016-08-31T12:23:59Z

IGNITE-3390: Added DSN configuration window.




---
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: Simulating network outages

2016-08-31 Thread Alexey Goncharuk
Hi,

As a starting point you can take a look
at org.apache.ignite.spi.discovery.tcp.ServerImpl#forceNextNodeFailure
which forces DiscoverySpi to drop next node from the topology (not sure if
this is what you need). Another idea is to create a test discovery SPI
which will terminate all it's threads when a test flag is set. Such nodes
also should be segmented from the topology.

Yakov, do you have other ideas?

2016-08-31 0:06 GMT+03:00 Anand Kumar Sankaran :

> Hi
>
> I am implementing a segmentation resolver to handle split brain
> scenarios.  I need to simulate network outages to unit test this behavior.
> Any suggestions on how to simulate this?  I see that the TcpDiscoverySpi
> has timeouts, is there a way to mock TcpDiscoverySpi to think that there is
> a network outage to simulate such conditions?
>
> Thanks.
>
> --
> anand
>


[jira] [Created] (IGNITE-3812) Add executors configuration validation.

2016-08-31 Thread Andrew Mashenkov (JIRA)
Andrew Mashenkov created IGNITE-3812:


 Summary: Add executors configuration validation.
 Key: IGNITE-3812
 URL: https://issues.apache.org/jira/browse/IGNITE-3812
 Project: Ignite
  Issue Type: Task
Reporter: Andrew Mashenkov


An IllegalArgumentException will be thrown from one of java standard 
implementation of ThreadPool without any information about wrong parameter  if 
incorrect value provided (e.g. threadPoolSize <= 0). So, it is not obvious 
which executor service initialization failed.

See IgnitionEx.IgniteNamedInstance class



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