Replace Cron4J with Quartz for ignite-schedule module.

[Alexey Kuznetsov]

Hi!

1) Cron4J is very old:
  Latest Cron4j 2.2.5 released: *28-Dec-2011 *
  Latest Quarz 2.3.0 released: *20-Apr-2017*

2) Not very friendly license:
  CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
  Quartz is freely usable, licensed under the *Apache 2.0* license.

So, if we replace Cron4J  with Quartz we can move *ignite-schedule* module
 from lgpl profile to main distribution.

Any objections?

If no, I will create JIRA issue and implement this change.

-- 
Alexey Kuznetsov

Re: Facing problem in examples.

[Denis Magda]

Thanks for confirming that the issue has been solved.

I’ve added a special documentation section [1] to avoid issues like that in the 
future and placed "Platforms Interoperability Getting Started” callout block to 
C++ Getting Started Guide [2] to draw attention to these extra settings.

[1] 
https://apacheignite-cpp.readme.io/docs/cross-platform-interoperability#binary-marshaller-configuration
 

[2] 
https://apacheignite-cpp.readme.io/v2.0/docs/getting-started-1#section-start-from-command-line
 


—
Denis

> On Jun 20, 2017, at 8:05 AM, Rahul.S  wrote:
> 
> BINGO!
> that helped alot, it is working now thank you very much people for such a
> positive and good support...
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/Facing-problem-in-examples-tp13894p13981.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

[GitHub] ignite pull request #2167: IGNITE-5533 Proper DROP of dynamic tables.

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

IGNITE-5533 Proper DROP of dynamic tables.



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

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

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

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


commit 2f5f910737f9195f0482cfd828eb27f0e98d7947
Author: Alexander Paschenko 
Date:   2017-06-20T18:24:58Z

IGNITE-5533 Proper DROP of dynamic tables.




---
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-5563) Ignite platform .NET tests failed with execution timeout

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-5563:
--

 Summary: Ignite platform .NET tests failed with execution timeout
 Key: IGNITE-5563
 URL: https://issues.apache.org/jira/browse/IGNITE-5563
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Pavlov


Probably there is some issue with grid activation
Not reproduced locally
Persistence is used with default settings, activation causes hang up

http://ci.ignite.apache.org/viewLog.html?buildId=676146=buildResultsDiv=Ignite20Tests_IgnitePlatformNet


http://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=676146&_focus=14881



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Ready for review - IGNITE-4926: .NET: Join fails in LINQ when subquery is using Select clause

[Pavel Tupitsyn]

Reviewed and merged to master. Thanks!

On Tue, Jun 20, 2017 at 6:20 PM, Guru Stron 
wrote:

> Hi,
>
> IGNITE-4926: .NET: Join fails in LINQ when subquery is using Select clause
> is ready for review.
>
> Pull request: https://github.com/apache/ignite/pull/2166
>
> Tests:
> http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_
> IgnitePlatformNet_Ignite20Tests=pull%2F2166%
> 2Fmerge=buildTypeStatusDiv
>
> Inspections:
> http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_
> IgnitePlatformNetInspections_Ignite20Tests=pull%2F2166%2Fmerge=
> buildTypeStatusDiv
>

[GitHub] ignite pull request #2166: IGNITE-4926: .NET: Join fails in LINQ when subque...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2143: IGNITE-5396: ODBC: Server cursor automatically cl...

[isapego]

Github user isapego closed the pull request at:

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


---
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 #2136: IGNITE-5377 ODBC: Exposed SqlFieldsQuery hints as...

[isapego]

Github user isapego closed the pull request at:

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


---
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: BinaryObjects and hashCode()

[Igor Rudyak]

Vladimir,

Thanks for the clarification.

Igor

On Jun 20, 2017 2:37 AM, "Vladimir Ozerov"  wrote:

> Igor,
>
> This exception is just a regression from recent work on binary
> serialization in the scope of 2.0 release. If BinaryMarshaller is set, we
> should not force users to have equals/hashCode methods on keys. There is a
> ticket [1], hopefully it will be merged to master soon.
>
> Vladimir.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-5383
>
> On Tue, Jun 20, 2017 at 1:08 AM, Igor Rudyak  wrote:
>
> > Hi,
> >
> > I am using simple POJO objects as key/value pair for my Ignite cache.
> Also
> > I would like to store objects as BinaryObjects. Thus Ignite cache was
> > created using:
> >
> > *mycache = ignite.getOrCreateCache("mycache").withKeepBinary()*
> >
> > When I am trying to put objects in the cache I am receiving such an
> error:
> >
> > *java.lang.IllegalArgumentException: Cache key must override hashCode()
> > and
> > equals() methods: com.test.MyKey*
> >
> > Isn't this contradicts to *BinaryObjects* concept? As far as there are no
> > *com.test.MyKey* class deployed on the server side all implemented class
> > methods (including *hashCode* and *equals*) are useless, cause they will
> > not be available on the server.
> >
> > Igor
> >
>

Ready for review - IGNITE-4926: .NET: Join fails in LINQ when subquery is using Select clause

[Guru Stron]

Hi,

IGNITE-4926: .NET: Join fails in LINQ when subquery is using Select clause
is ready for review.

Pull request: https://github.com/apache/ignite/pull/2166

Tests:
http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgnitePlatformNet_Ignite20Tests=pull%2F2166%2Fmerge=buildTypeStatusDiv

Inspections:
http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgnitePlatformNetInspections_Ignite20Tests=pull%2F2166%2Fmerge=buildTypeStatusDiv

[GitHub] ignite pull request #2166: IGNITE-4926: .NET: Join fails in LINQ when subque...

[gurustron]

GitHub user gurustron opened a pull request:

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

IGNITE-4926: .NET: Join fails in LINQ when subquery is using Select clause



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

$ git pull https://github.com/gurustron/ignite IGNITE-4926

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

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


commit a27b4aa67c074a9a653e1306ed79970d38c273ad
Author: gurustron 
Date:   2017-06-17T16:59:00Z

analyze joinclause in VisitQuerySourceReference

commit f517131581bf305108687f32df3927a98a56be31
Author: gurustron 
Date:   2017-06-20T15:09:53Z

some fixes




---
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 #2165: Ignite 3142

[vadopolski]

GitHub user vadopolski opened a pull request:

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

Ignite 3142



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

$ git pull https://github.com/vadopolski/ignite ignite-3142

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

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


commit 6e5f83233b5501bdb6a3bb03eb53f3be8871f786
Author: vopolski <2w3e4r5t>
Date:   2017-04-20T15:07:48Z

updating

commit 5cbd64bf094928db6f831ea634af81fec020fd47
Author: vopolski <2w3e4r5t>
Date:   2017-06-20T14:02:13Z

IGNITE-3142
Added EventsListenerTest.

commit 0306d2f2deb58a253f27d86e7208c6eeaae47907
Author: vopolski <2w3e4r5t>
Date:   2017-06-20T14:04:26Z

IGNITE-3142
Added EventsListenerTest.

commit 28419920a51f25c7dcdd4f4804dbfaf710740f8c
Author: vopolski <2w3e4r5t>
Date:   2017-06-20T14:44:48Z

IGNITE-3142
Added code style.




---
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-5562) Assertions in TCP discovery SPI when NTP is moving time backwards

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5562:


 Summary: Assertions in TCP discovery SPI when NTP is moving time 
backwards
 Key: IGNITE-5562
 URL: https://issues.apache.org/jira/browse/IGNITE-5562
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.7
Reporter: Alexey Goncharuk
 Fix For: 2.1


In several places in TcpDiscoverySPI, when metrics are updated, we assert that 
time is not negative. However, in some cases, this invariant may fail because 
of time adjustments. 

Since a missed metric is not critical for us, we should remove these assertions 
and replace negative time with 0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2163: new method in MarshallerContext interface to regi...

[sergey-chugunov-1985]

Github user sergey-chugunov-1985 closed the pull request at:

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


---
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 #2164: Ignite-1.8.8

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

Ignite-1.8.8



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

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

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

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


commit 2b3a180ff7692c0253da3ff7c32d65c09f9488d2
Author: Andrey Novikov 
Date:   2016-12-23T09:34:10Z

Web console beta-7.

(cherry picked from commit 8e7c852)

commit b252b441a9ada31c7200b385d75e0b3e7c0362dd
Author: Alexey Kuznetsov 
Date:   2016-12-23T11:20:44Z

Implemented Visor tasks for Services.

(cherry picked from commit fdf1f4b)

commit fb8191028eb19b0683b8239b7024f7fa6ccabd4e
Author: Alexey Kuznetsov 
Date:   2016-12-23T11:40:51Z

Updated classnames for ignite-1.7.5.

commit 2da2816fd74b17590f45781268337da5205c44fa
Author: Vasiliy Sisko 
Date:   2016-12-23T11:58:47Z

Fixed broken links.

(cherry picked from commit 6ca8670)

commit 2ccae40e2a21398d15c3762b72575216c56a7fb0
Author: dkarachentsev 
Date:   2016-12-23T14:51:49Z

IGNITE-4109 - BinaryType.isEnum() throws an exception if typeId==0

commit 9273e51cd039049a4aae73f9dcafc02915bc6153
Author: Alexandr Kuramshin 
Date:   2016-12-26T10:23:28Z

ignite-4167 Do not log cache key/values

commit 5769f44367cae5908cd291f226e9fccd68fe1c39
Author: Alexey Kuznetsov 
Date:   2016-12-27T08:14:13Z

Fixed Visor queries for BinaryObjects.

commit 5494dfb8dd222bf7aee8214b6bb201d3ae8a1ec5
Author: Ignite Teamcity 
Date:   2016-12-27T11:50:58Z

1.8.0-SNAPSHOT

commit b8cb82de65a529040ea18b0dc03fa7109c69bb4a
Author: Vasiliy Sisko 
Date:   2016-12-29T07:48:45Z

IGNITE-4442 Implemented cache affinity configuration.

(cherry picked from commit f4a1e6c)

commit 6c38eb28623271a3604ee8d966deb88677a3adb1
Author: devozerov 
Date:   2016-12-29T09:20:20Z

IGNITE-4167: Changed IGNITE_TO_STRING_INCLUDE_SENSITIVE default value to 
"true".

commit 864a95e13f1262f14351df0883d0a1abd1bf70c7
Author: sboikov 
Date:   2016-12-29T11:45:08Z

Removed duplicated benchmark.

commit da5b68cc89ba6eeff25beb66e3a4d8c2b9871ab3
Author: sboikov 
Date:   2016-12-29T12:46:59Z

For communication spi disabled pairedConnections by default, implemented 
NIO sessions balancing for this mode.

commit 71412cecd861119965a873520da96078f99c94e2
Author: Anton Vinogradov 
Date:   2016-12-30T10:41:34Z

IGNITE-4424 REPLICATED cache isn't synced across nodes

commit 121f034e5739dcc7dd9c9577c9a437acaf710a19
Author: devozerov 
Date:   2017-01-05T09:00:49Z

Merge branch 'ignite-1.8.2' into ignite-1.8.3

commit 494cf88209b196f2677e26f468aab1f98d791217
Author: devozerov 
Date:   2017-01-05T09:05:04Z

Merge branch 'ignite-1.7.5' into ignite-1.8.3

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryObjectExImpl.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryProcessor.java
#   
modules/platforms/dotnet/Apache.Ignite.Benchmarks/Properties/AssemblyInfo.cs
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests.NuGet/Properties/AssemblyInfo.cs
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests/Cache/Query/CacheQueriesCodeConfigurationTest.cs
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests/Properties/AssemblyInfo.cs
#   modules/platforms/dotnet/Apache.Ignite.NLog/Properties/AssemblyInfo.cs
#   modules/platforms/dotnet/Apache.Ignite/Properties/AssemblyInfo.cs
#   
modules/platforms/dotnet/examples/Apache.Ignite.Examples/Properties/AssemblyInfo.cs
#   
modules/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Properties/AssemblyInfo.cs

commit ac92bdb44ed0fb02893c1e7e9df4443a0a26d331
Author: Ivan Veselovskiy 
Date:   2016-12-19T08:57:00Z

IGNITE-3966: Hadoop: add Hadoop native library to Java arguments 
automatically. This closes #1320.

commit 1776e9eb04895bbb870f7c6aa89ca96db2af31b7
Author: tledkov-gridgain 
Date:   2016-12-29T08:14:10Z

IGNITE-4458: Hadoop: "striped" shuffle mode is default from now on. This 
closes #1390.

commit e7d781ee3221107d9a819dd70cb5776558a59e2a
Author: devozerov 
Date:   2017-01-05T08:30:42Z

IGNITE-4516: Hadoop: implemented optional compression for remote shuffle 
output. This closes #1399.

commit 

IGNITE-4908

[Александр Меньшиков]

Hello, Andrew!

What do you think about create sub task for IGNITE-4908 about creating
benchmark which highlights performance problem?
I think it helps us to agree about use-case which we want to test.

Link on Jira: https://issues.apache.org/jira/browse/IGNITE-4908

[GitHub] ignite pull request #2163: new method in MarshallerContext interface to regi...

[sergey-chugunov-1985]

GitHub user sergey-chugunov-1985 opened a pull request:

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

new method in MarshallerContext interface to register mappings locally



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

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

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

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


commit ffe1a010c9452954aabd091b25e3dc47128acdcd
Author: Alexey Goncharuk 
Date:   2017-06-09T14:20:07Z

Merge from ignite-5267

commit 65d21ebd094c2d93fe18693f5f1ff9dfbb330053
Author: Ilya Lantukh 
Date:   2017-06-09T14:45:56Z

ignite-5324 : Volatile data structures.

commit f9ed6120baa6d0db826f1e58f4fd7b791711734a
Author: Alexey Goncharuk 
Date:   2017-06-09T15:15:28Z

IGNITE-5267 - Fixed NPE in checkpointer

commit bdbba0ee9a5437a3f66d05c8175bfcb2f309b3bd
Author: Dmitriy Govorukhin 
Date:   2017-06-11T18:53:56Z

IGNITE-5392 - Joining node must accept cluster active status

commit 6bf5ce46c1e6c4e3dcf042ac91a5b61a726c5821
Author: Alexey Goncharuk 
Date:   2017-06-11T20:02:44Z

IGNITE-5267 - Moved ignite-ps module to ignite-core

commit 4dc81ca86347107848328d1e2e206b796976fb23
Author: Alexey Goncharuk 
Date:   2017-06-12T05:22:49Z

IGNITE-5267 - Added missing class

commit 195147d573d7cb3fc637f74937ee561b03a3c574
Author: Dmitriy Govorukhin 
Date:   2017-06-13T05:23:38Z

IGNITE-5267 - Activate nodes after start

commit d38dfcd5c4a49b6ec4be1cfdb4f28f7d152cd14a
Author: Dmitriy Govorukhin 
Date:   2017-06-13T10:01:16Z

ignite-5267-merge remove pds dependency, restore data structures only in 
snapshot operation

commit cf886fd5816534b46a1247d3bdc41061087608e4
Author: Dmitriy Govorukhin 
Date:   2017-06-13T10:22:30Z

ignite-2.1.1 fix java doc

commit d2dcc1d032c7f9692ddfe50fa8a80e375e8d4c9b
Author: Dmitriy Govorukhin 
Date:   2017-06-13T10:45:11Z

ignite-2.1.1 fix import

commit b65ca6854828c0f2368edab202ba00f31365a3e3
Author: Ivan Rakov 
Date:   2017-06-13T10:50:31Z

ignite-2.1.1 fixing pds tests

commit 1181b478d7810d4485da43204c9f64757be6a8e4
Author: Ivan Rakov 
Date:   2017-06-13T11:51:25Z

ignite-2.1.1 fixing pds tests

commit 68739b7cffae5b4bb3714dfe12bcf93327f136b8
Author: Alexey Kuznetsov 
Date:   2017-06-13T12:27:32Z

IGNITE-5267 Snapshots support.

commit ec50e23591c4d2e2332b7a81b7218ee44f358afe
Author: Ilya Lantukh 
Date:   2017-06-13T12:34:02Z

Merge with ignite-5267-merge.

commit 4342f46ab4258f8219e45f4b69435f38b6d0f2b5
Author: Ilya Lantukh 
Date:   2017-06-13T12:37:34Z

ignite-5267 : Test for unique name per group.

commit 2b0741039e7cc6e36871b97bab53780edfc84648
Author: Ilya Lantukh 
Date:   2017-06-13T12:38:55Z

ignite-5267 : Removed redundant test.

commit 4a86cae203ed9aed953cd6093884cf8cab4531e3
Author: Dmitriy Govorukhin 
Date:   2017-06-13T12:48:39Z

ignite-2.1.1 fix state processor, skip if daemon

commit 5c567aeb5458159bc41dbd251dfa8a65701f4861
Author: Ivan Rakov 
Date:   2017-06-13T13:06:42Z

ignite-2.1.1 moving pds tests that depend on indexing to separate suite

commit 5e9d9ebc1140f9647fc1b325ba81d0ad6c2c69f3
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:21:20Z

ignite-2.1.1 Added description to MX bean

commit 2c2a9e652b13cf60b7e878a4e20f4ab4ae014e9c
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:21:39Z

Merge remote-tracking branch 'professional/ignite-2.1.1' into ignite-2.1.1

commit 9141b3698d0ec98e512efbc78864cc06781fd8c7
Author: devozerov 
Date:   2017-06-13T13:32:28Z

IGNITE-5267: Fixed too early StoredCacheData initialization.

commit 0a00f03da78649320cb0bb3579f44d6fe037facc
Author: devozerov 
Date:   2017-06-13T13:32:58Z

Merge remote-tracking branch 'upstream/ignite-2.1.1' into ignite-2.1.1

commit 2d8c6519d36e2d7890a45b258d3b7439942dca66
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:39:13Z

ignite-2.1.1 Add joining node tests

commit c5cee32a510e5a3524ff88119acfd1963c74d8ad
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:39:30Z

Merge remote-tracking branch 'professional/ignite-2.1.1' into ignite-2.1.1

commit 

[jira] [Created] (IGNITE-5561) Warn about long-running cache store operations

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5561:


 Summary: Warn about long-running cache store operations
 Key: IGNITE-5561
 URL: https://issues.apache.org/jira/browse/IGNITE-5561
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 1.7
Reporter: Alexey Goncharuk
 Fix For: 2.1


When a cache store is used, it may become very confusing if a cache store 
performs a very long-running operation, because in this case, Ignite would 
output a warning about long-running cache operations. I think, in addition to 
that, we should measure and output a warning if a specific cache store 
operation took too long.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5560) A failed service must be redeployed when possible

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5560:


 Summary: A failed service must be redeployed when possible
 Key: IGNITE-5560
 URL: https://issues.apache.org/jira/browse/IGNITE-5560
 Project: Ignite
  Issue Type: Improvement
  Components: managed services
Affects Versions: 1.7
Reporter: Alexey Goncharuk
 Fix For: 2.1


I observed the following behavior: when a service deployment (or run) fails 
with an unexpected exception, Ignite just outputs a warning to the console and 
does not attempt anything to recover. 
In our deployment, we rely on a cluster singleton to be always present in a 
cluster. 
If a service fails, Ignite should attempt to failover this service to some 
other node, if possible



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5559) New method on MarshallerContextImpl to register mappings locally

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5559:
---

 Summary: New method on MarshallerContextImpl to register mappings 
locally
 Key: IGNITE-5559
 URL: https://issues.apache.org/jira/browse/IGNITE-5559
 Project: Ignite
  Issue Type: Improvement
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
Priority: Minor
 Fix For: 2.1


As Ignite got a new persistent store functionality, it becomes possible to save 
caches content to disk, restore from it later and even move data using plain 
files from one cluster to another.

In that case marshaller mappings may be saved on disk as well and restored 
later as well on other Ignite clusters.

As mappings are restored on each node locally and don't require exchanging any 
messages among the cluster new convenient method 
{{MarshallerContextImpl::registerClassNameLocally}} is needed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5558) Add ability to read WAL outside of an Ignite node

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5558:


 Summary: Add ability to read WAL outside of an Ignite node
 Key: IGNITE-5558
 URL: https://issues.apache.org/jira/browse/IGNITE-5558
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.1
Reporter: Alexey Goncharuk
 Fix For: 2.2


Currently, the WAL iterator can be obtained from the WAL manager when an Ignite 
node is up and running.
However, it may be extremely useful to read WAL in an 'offline' mode, when a 
node is not started up. This may be required for crash analysis or to export 
committed data to some external systems.

In the future we can make this even a public interface, however as a starting 
point, I would like to keep it in private package because moving to the public 
package will require Iterator and records to be public too.

So, as a starting point, we need:
 * An object that will allow us to get WALIterator instances (probably, should 
be closeable)
 * A method on this object which will create an iterator by a file name or file 
names

Using this object should not require an active Ignite instance running.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Questions about IGNITE-4684

[Александр Меньшиков]

Hello, Igniters!

Can someone clarify the crux of ignite-4684 to me? I asked some questions
inside Jira's discussion. Link:
https://issues.apache.org/jira/browse/IGNITE-4684

In short:
1) What implementation of the IgniteCache we are interested in?
2) What locks we are interested in?

[jira] [Created] (IGNITE-5557) ODBC: Implement benchmarks

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-5557:
---

 Summary: ODBC: Implement benchmarks
 Key: IGNITE-5557
 URL: https://issues.apache.org/jira/browse/IGNITE-5557
 Project: Ignite
  Issue Type: Task
  Components: odbc
Affects Versions: 2.0
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 2.1


We need to implement benchmarks to find out the performance of the ODBC driver 
and keep tracking it when implementing new features.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5556) Integer to Long cast exception during load test when print cache size

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-5556:
---

 Summary: Integer to Long cast exception during load test when 
print cache size
 Key: IGNITE-5556
 URL: https://issues.apache.org/jira/browse/IGNITE-5556
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ksenia Rybakova


"java.lang.Integer cannot be cast to java.lang.Long" occurs during preloading 
phase of load test. 

{noformat}
<13:13:02> Failed to print cache size 
[cache=orgCache, msg=class org.apache.ignite.IgniteCheckedException: 
java.lang.Integer cannot be cast to java.lang.Long]
[2017-06-20 13:13:02,845][ERROR][pool-4-thread-1][GridTaskWorker] Failed to 
reduce job results due to undeclared user exception 
[task=o.a.i.i.processors.cache.GridCacheAdapter$SizeLongTask@2d899933, 
err=java.lang.ClassCastException: java.lang.Integer cannot be cast to 
java.lang.Long]
java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.Long
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$SizeLongTask.reduce(GridCacheAdapter.java:6266)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$SizeLongTask.reduce(GridCacheAdapter.java:6210)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker$6.call(GridTaskWorker.java:1113)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6608)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:938)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.processDelayedResponses(GridTaskWorker.java:687)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:538)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:744)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:443)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:399)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.sizeLongAsync(GridCacheAdapter.java:3742)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.sizeLong(GridCacheAdapter.java:3688)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.sizeLong(IgniteCacheProxy.java:1054)
at 
org.apache.ignite.yardstick.PreloadLogger.printCacheStatistics(PreloadLogger.java:89)
at 
org.apache.ignite.yardstick.PreloadLogger.printCachesStatistics(PreloadLogger.java:72)
at org.apache.ignite.yardstick.PreloadLogger.run(PreloadLogger.java:63)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
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)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2162: IGNITE-5126 JDBC thin driver: support batches

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5126  JDBC thin driver: support batches



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

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

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

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


commit 13c34d3b8725f54fcb5a7a3eae97786792dfede8
Author: tledkov-gridgain 
Date:   2017-06-16T14:47:06Z

IGNITE-5126: save the progress

commit c95d9b365bc2aa27a9a02e7151b3c89d273987a7
Author: tledkov-gridgain 
Date:   2017-06-19T09:39:49Z

Merge branch '_master' into ignite-5126

commit a29d78880cfc1b4ba2507336f81550c18bcc1d75
Author: tledkov-gridgain 
Date:   2017-06-19T14:39:05Z

IGNITE-5126: save the progress

commit fa028e7cfd840a5a6598efec849bb61c58ff457c
Author: tledkov-gridgain 
Date:   2017-06-20T10:02:06Z

IGNITE-5126: save the progress

commit 92129279fa8a61596a782d64d8061e2df2148c93
Author: tledkov-gridgain 
Date:   2017-06-20T10:04:01Z

IGNITE-5126: minors




---
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-5555) Ignite PDS 1: JVM crash onteamcity

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-:
--

 Summary: Ignite PDS 1: JVM crash onteamcity
 Key: IGNITE-
 URL: https://issues.apache.org/jira/browse/IGNITE-
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Pavlov


http://ci.ignite.apache.org/viewLog.html?buildId=675694=buildResultsDiv=Ignite20Tests_IgnitePds1#

Stacktrace indicates failure was in ignite code
{noformat}
[12:37:10][org.apache.ignite:ignite-core] 
[12:37:10][org.apache.ignite:ignite-core] Thread [name="main", id=1, 
state=RUNNABLE, blockCnt=254, waitCnt=281]
[12:37:10][org.apache.ignite:ignite-core] at 
sun.management.ThreadImpl.dumpThreads0(Native Method)
[12:37:10][org.apache.ignite:ignite-core] at 
sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:446)
[12:37:10][org.apache.ignite:ignite-core] at 
o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1272)
[12:37:10][org.apache.ignite:ignite-core] at 
o.a.i.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1937)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestCase.runBare(TestCase.java:141)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult$1.protect(TestResult.java:122)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult.runProtected(TestResult.java:142)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult.run(TestResult.java:125)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestCase.run(TestCase.java:129)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.runTest(TestSuite.java:255)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.run(TestSuite.java:250)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.runTest(TestSuite.java:255)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.run(TestSuite.java:250)
[12:37:10][org.apache.ignite:ignite-core] at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Ready for review: IGNITE-5442 .NET: LINQ Conditional statement will fail for some types

[Pavel Tupitsyn]

Reviewed and merged to master.
Thank you for the contribution!

Pavel

On Fri, Jun 16, 2017 at 4:05 PM, Guru Stron 
wrote:

> Hi guys,
>
>  IGNITE-5442 is ready for review)
>
> https://github.com/apache/ignite/pull/2144
>
> Ignite Platform .NET
> http://ci.ignite.apache.org/viewQueued.html?itemId=670159;
> tab=queuedBuildOverviewTab
>
> Ignite Platform .NET Inspections
> http://ci.ignite.apache.org/viewQueued.html?itemId=670160;
> tab=queuedBuildOverviewTab
>

[GitHub] ignite pull request #2144: IGNITE-5442 .NET: LINQ Conditional statement will...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-5554) ServiceProcessor may process failed reassignments in timeout thread

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5554:


 Summary: ServiceProcessor may process failed reassignments in 
timeout thread
 Key: IGNITE-5554
 URL: https://issues.apache.org/jira/browse/IGNITE-5554
 Project: Ignite
  Issue Type: Bug
  Components: managed services
Affects Versions: 1.7
Reporter: Alexey Goncharuk
 Fix For: 2.2


The following parts of GridServiceProcessor look wrong to me: 
In GridServiceProcessor.TopologyListener#onReassignmentFailed
{code}
@Override public void onTimeout() {
onReassignmentFailed(topVer, retries);
}
{code}

And in GridServiceProcessor#onDeployment
{code}
@Override public void onTimeout() {
.
// Try again.
onDeployment(dep, topVer);
}
{code}

The rest of ServiceProcessor relies on the deployments being processed in a 
single thread, while this code will be executed in the timeout processor 
thread. Not only can it take a lot of time to reassign, which will stall the 
timeout thread, but it may also break the service assignment logic.

The corresponding calls should be wrapped to runnables and submitted to the 
depExe.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5553) Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-5553:
--

 Summary: Ignite PDS 2: IgnitePersistentStoreDataStructuresTest 
testSet assertion error
 Key: IGNITE-5553
 URL: https://issues.apache.org/jira/browse/IGNITE-5553
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Pavlov


http://ci.ignite.apache.org/viewLog.html?buildId=675215=buildResultsDiv=Ignite20Tests_IgnitePds2#testNameId-7043871603266099589

Reproducable locally (stable)

{noformat}
junit.framework.AssertionFailedError: 
Expected :100
Actual   :0
 
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at junit.framework.TestCase.assertEquals(TestCase.java:409)
at 
org.apache.ignite.internal.processors.cache.persistence.IgnitePersistentStoreDataStructuresTest.testSet(IgnitePersistentStoreDataStructuresTest.java:195)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: BinaryObjects and hashCode()

[Vladimir Ozerov]

Igor,

This exception is just a regression from recent work on binary
serialization in the scope of 2.0 release. If BinaryMarshaller is set, we
should not force users to have equals/hashCode methods on keys. There is a
ticket [1], hopefully it will be merged to master soon.

Vladimir.

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

On Tue, Jun 20, 2017 at 1:08 AM, Igor Rudyak  wrote:

> Hi,
>
> I am using simple POJO objects as key/value pair for my Ignite cache. Also
> I would like to store objects as BinaryObjects. Thus Ignite cache was
> created using:
>
> *mycache = ignite.getOrCreateCache("mycache").withKeepBinary()*
>
> When I am trying to put objects in the cache I am receiving such an error:
>
> *java.lang.IllegalArgumentException: Cache key must override hashCode()
> and
> equals() methods: com.test.MyKey*
>
> Isn't this contradicts to *BinaryObjects* concept? As far as there are no
> *com.test.MyKey* class deployed on the server side all implemented class
> methods (including *hashCode* and *equals*) are useless, cause they will
> not be available on the server.
>
> Igor
>

[jira] [Created] (IGNITE-5552) ServiceProcessor recalculates all service assignments even if there is a pending topology change

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5552:


 Summary: ServiceProcessor recalculates all service assignments 
even if there is a pending topology change
 Key: IGNITE-5552
 URL: https://issues.apache.org/jira/browse/IGNITE-5552
 Project: Ignite
  Issue Type: Improvement
  Components: managed services
Affects Versions: 1.7
Reporter: Alexey Goncharuk
 Fix For: 2.2


This behavior was observed in a real cluster of hundreds of nodes and hundreds 
of services.

After a ~30 new nodes startup, we expected node singletons to be deployed 
immediately, but the services were deployed with ~4hr delay on last nodes. The 
reason for this is the fact that ALL service deployments are recalculated on 
ALL discovery events. In this case, a single discovery event was processed in a 
time span of 2-5 minutes, which with the lateAffinityAssignment=true yielded a 
4hr delay for the last node.

The quick change that may improve things a lot is aborting current assignment 
calculations if there is a pending discovery event needs to be processed.

The rest of the optimizations are put to 
https://issues.apache.org/jira/browse/IGNITE-5551



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5551) Optimize service deployment assignments object

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5551:


 Summary: Optimize service deployment assignments object
 Key: IGNITE-5551
 URL: https://issues.apache.org/jira/browse/IGNITE-5551
 Project: Ignite
  Issue Type: Improvement
  Components: managed services
Affects Versions: 1.7
Reporter: Alexey Goncharuk
 Fix For: 2.2


1) The deployment assignment is stored using a map [node ID -> number of 
assigned services]. However, this assignment is not very effective for cases 
when service configuration is (maxPerCluster = 0, maxPerNode > 0), because in 
this case, we can avoid assignment recalculation at all. The assignment for 
this case may look like (eachNode=N). In this case, the assignment does not 
change and we can effectively skip it during the reassign loop.

2) We store zero assignment counters, which does not make sense at all - if 
there are no service deployments for a node, there should be no corresponding 
entry in the map at all. The size of assignments for (maxPerCluster > 0) 
configurations is O(number of nodes in the cluster), but it should be 
O(maxPerCluster).

3) If an assignment did not change, we should not commit the assignment 
transaction - this is redundant



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5550) Ignite PDS 1 Test Suite: test reports there are not shutdown nodes

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-5550:
--

 Summary: Ignite PDS 1 Test Suite: test reports there are not 
shutdown nodes
 Key: IGNITE-5550
 URL: https://issues.apache.org/jira/browse/IGNITE-5550
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Pavlov

[jira] [Created] (IGNITE-5549) Ignite Cache Failover2: test suite hands up for more than 2 hours

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-5549:
--

 Summary: Ignite Cache Failover2: test suite hands up for more than 
2 hours
 Key: IGNITE-5549
 URL: https://issues.apache.org/jira/browse/IGNITE-5549
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Pavlov


http://ci.ignite.apache.org/viewLog.html?buildId=675158=buildResultsDiv=Ignite20Tests_IgniteCacheFailover2

http://ci.ignite.apache.org/viewLog.html?buildId=674915=buildResultsDiv=Ignite20Tests_IgniteCacheFailover2

http://ci.ignite.apache.org/viewLog.html?buildId=674698=buildResultsDiv=Ignite20Tests_IgniteCacheFailover2

http://ci.ignite.apache.org/viewLog.html?buildId=674698=buildResultsDiv=Ignite20Tests_IgniteCacheFailover2



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Transparent Data Encryption (TDE) in Apache Ignite

[Vyacheslav Daradur]

Hi Igniters.

I have some user cases where I need fast storage with TDE support.
It is requered for PCI DSS certification.

As far as I know AI doesn't support it.

I looked at other storages.
Many storages support it or are engaged in development this feature.

Cassandra community are working on TDE support.[1]

Oracle support it.[2] Moreover it supports indexing and querying on
encrypted data.

I think it will be very usefull to support TDE by AI.

What do you think? Maybe development is already under way?

[1] https://issues.apache.org/jira/browse/CASSANDRA-9945
[2]
https://docs.oracle.com/cd/B19306_01/network.102/b14268/asotrans.htm#ASOAG600

-- 
Best Regards, Vyacheslav D.