[GitHub] ignite pull request #2289: IGNITE-5744

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

IGNITE-5744



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

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

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

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


commit 707c454ad9c3b4132e2d0a20d15dc1eb2ed295b0
Author: Alexey Goncharuk 
Date:   2017-07-12T07:53:46Z

Corrected fix for REST processor wrt authentication

commit f3828261b30c12d5aa181914033afe46c787f87e
Author: Alexey Kuznetsov 
Date:   2017-07-12T07:57:50Z

IGNITE-5639 Added duration for empty result set.

commit 5859b192ba28d53e1bccb01ce3005821e26b5347
Author: devozerov 
Date:   2017-07-12T09:46:42Z

AI 2.1 release notes.

commit 8afdc7baae73ecba67e0735baa97d03f2c4fc715
Author: devozerov 
Date:   2017-07-12T10:51:43Z

Removed CacheBinaryAutoStoreExample and relevant bean "h2-example-db" from 
example-default.xml because example duplicated existing CacheAutoStoreExample.

commit c6ee085b8a1321ce7fa15f8adf74fa7a01f7a445
Author: Dmitriy Govorukhin 
Date:   2017-07-12T11:22:03Z

Fixed page acquire during checkpoint

commit 0cb6ac06a43ac72c707b29d7216bd4cb711a
Author: Oleg Ostanin 
Date:   2017-07-12T12:57:40Z

IGNITE-5740 - Added transaction load timing benchmark

commit 3787181310597b7a6e633e745ba08209abd038a9
Author: Alexey Goncharuk 
Date:   2017-07-12T15:28:57Z

More verbose logging

commit 21964fb5f6fb6fee891283332202cbc9ed5ac3f3
Author: Dmitry Pavlov 
Date:   2017-07-12T15:59:10Z

Optimized snapshot progress tracking

commit 9496bf337d98559805c611b57140bea65c586602
Author: Alexander Paschenko 
Date:   2017-07-13T04:04:28Z

IGNITE-5744 Ignore non user caches when automatically choosing a queryable 
cache inside JDBC driver




---
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: Changing public IgniteCompute API to improve changes in 5037 ticket

[Valentin Kulichenko]

Hi Max,

This ticket doesn't assume any API changes, it's about broken
functionality. I would start with checking what tests we have
for @AffinityKeyMapped and creating missing one. From what I understand
functionality is broken completely or almost completely, so I guess testing
coverage is very weak there.

-Val

On Wed, Jul 12, 2017 at 4:27 PM, Kozlov Maxim  wrote:

> Igniters,
>
> jira: https://issues.apache.org/jira/browse/IGNITE-5037 <
> https://issues.apache.org/jira/browse/IGNITE-5037>
> How do you look to solve this ticket by adding two methods to the public
> IgniteCompute API?
>
> @IgniteAsyncSupported
> public void affinityRun(@NotNull Collection cacheNames,
> Collection keys, IgniteRunnable job)
> throws IgniteException;
>
> @IgniteAsyncSupported
> public  R affinityCall(@NotNull Collection cacheNames,
> Collection keys, IgniteCallable job)
> throws IgniteException;
>
> There is also a question of how to act when changing the topology during
> the execution of the job.
> 1) complete with an exception;
> 2) stop execution and wait until the topology is rebuilt and continue
> execution;
>
> I think the second way, do you think?
>
> --
> Best Regards,
> Max K.
>
>
>
>
>

Changing public IgniteCompute API to improve changes in 5037 ticket

[Kozlov Maxim]

Igniters,

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

How do you look to solve this ticket by adding two methods to the public 
IgniteCompute API?

@IgniteAsyncSupported
public void affinityRun(@NotNull Collection cacheNames, 
Collection keys, IgniteRunnable job)
throws IgniteException;

@IgniteAsyncSupported
public  R affinityCall(@NotNull Collection cacheNames, 
Collection keys, IgniteCallable job)
throws IgniteException;

There is also a question of how to act when changing the topology during the 
execution of the job.
1) complete with an exception;
2) stop execution and wait until the topology is rebuilt and continue execution;

I think the second way, do you think?

--
Best Regards,
Max K.

[GitHub] ignite pull request #2288: ignite-5489 Fixed possible connection leaks when ...

[agura]

GitHub user agura opened a pull request:

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

ignite-5489 Fixed possible connection leaks when loadPreviousValue set to 
true



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

$ git pull https://github.com/agura/incubator-ignite ignite-5489-master

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

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


commit 611f625eb4435f90b06c03b9d3656d5405b6847e
Author: Tikhonov Nikolay 
Date:   2017-06-21T14:55:05Z

ignite-5489 Fixed possible connection leaks when loadPreviousValue set to 
true




---
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 #2287: ignite-5489 Fixed possible connection leaks when ...

[agura]

GitHub user agura opened a pull request:

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

ignite-5489 Fixed possible connection leaks when loadPreviousValue set to 
true



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

$ git pull https://github.com/agura/incubator-ignite ignite-5489

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

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


commit 260f9b2d01b16a98fcb7bc721573b95a72adade2
Author: Pavel Tupitsyn 
Date:   2016-10-31T15:37:49Z

.NET: Fix license header

commit e7d7a59eff6da1cd62e8ffb64405cdf12607b49d
Author: Pavel Tupitsyn 
Date:   2016-10-31T15:43:15Z

IGNITE-4153 .NET: IgniteConfiguration.FailureDetectionTimeout property is 
missing

commit d0f4b23600c655dfb94f6fe0205d1cca7cf19d36
Author: AKuznetsov 
Date:   2016-10-31T16:06:58Z

Fixed license.

commit 5fac786b6dbb179127ac725180acb54d0f6f4b0a
Author: devozerov 
Date:   2016-10-31T18:31:05Z

Merge branch 'ignite-1.6.10' into ignite-1.7.3

commit b8b9abe863ed8139553a9ad7013dfad5a363b4da
Author: devozerov 
Date:   2016-10-31T18:31:22Z

Fixes after merge.

commit 61ab650ecd353b4014a30f793090e9dab3519ad5
Author: devozerov 
Date:   2016-10-31T18:33:59Z

Fixes after merge.

commit 4495efc2aa37ca31214558968fa83598317e830a
Author: Pavel Tupitsyn 
Date:   2016-11-01T10:22:30Z

IGNITE-4117 .NET: Fix ClientReconnectTask completion timing

This closes #1195

commit dc0adf641f0ddac19af84ba0d701b33ee520b067
Author: Pavel Tupitsyn 
Date:   2016-08-16T15:11:34Z

IGNITE-3368 .NET: Improve test coverage

This closes #953

# Conflicts:
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests/Cache/CacheAbstractTest.cs

commit cd0275d95dc6524464a154c74b1e62559b3d8af4
Author: Pavel Tupitsyn 
Date:   2016-08-19T14:34:00Z

IGNITE-3711 .NET: Fix PlatformRawMemory coverage issue

commit d7dee5248332c6c6276c9e21aed4afb3abdd4340
Author: Pavel Tupitsyn 
Date:   2016-07-29T12:40:42Z

IGNITE-3604 .NET: Fix inconsistent namespace imports in examples

Conflicts:
modules/platforms/dotnet/Apache.Ignite.sln.DotSettings

commit 390c8d59cf8d44d9703e5fbf8d9c0f8028a4a172
Author: Pavel Tupitsyn 
Date:   2016-08-11T13:18:14Z

IGNITE-3675 .NET: Use separate caches for different entities in 
QueryExample.

commit 861c1736facdf76c71e93ddada0d8e15b5b2950c
Author: Pavel Tupitsyn 
Date:   2016-08-11T14:32:13Z

IGNITE-3673 .NET: Add examples for distributed joins.

commit 3a9cbed4e692e76ad884e60a4f5edc670e6b3c8f
Author: Pavel Tupitsyn 
Date:   2016-08-08T14:00:04Z

IGNITE-3630 .NET: Add pure binary mode example with put-get and queries.

commit d5e15af76044cf65385672f8528d48ecdeca3cb6
Author: Pavel Tupitsyn 
Date:   2016-11-02T09:02:00Z

IGNITE-4121 .NET: add ScanQuery example

commit 74f8308d10fc011c00e52efcdb315b35cc79e60a
Author: Pavel Tupitsyn 
Date:   2016-11-02T12:59:15Z

IGNITE-4123 .NET: Remove [Serializable] from Employee in examples

commit 92fff630fbf36c82f93bbd9ddd53d11bed44e772
Author: devozerov 
Date:   2016-11-02T14:50:51Z

Restored services compatibility.

commit a62a0136d295486d95c6e2ab5bba88270d831753
Author: dkarachentsev 
Date:   2016-11-02T16:07:45Z

GG-11655 - Fix merge

commit 348593986b56ddfcec4a4455e49d9b279eae4dc8
Author: devozerov 
Date:   2016-11-05T10:28:03Z

Merge branch 'ignite-1.7.3' into ignite-1.7.4

commit 175da6b7e394dd76c27d5155ff98a5b2ef03bb9d
Author: tledkov-gridgain 
Date:   2016-11-07T06:16:58Z

IGNITE-3432:  check data/meta cache names are different for different IGFS 
instances. This closes #1201

commit ead15193899d08f41491166003cabed0560f0c59
Author: Pavel Tupitsyn 
Date:   2016-11-07T07:49:03Z

IGNITE-4028 Get rid of OP_META in PlatformAbstractTarget

This closes #1192

commit 40ef2f5ae42826fe8fd077e3013e8f55c8512bdd
Author: Dmitriy Govorukhin 
Date:   2016-11-07T09:09:41Z

ignite-4178 support permission builder

commit df670c7d64046d282c053f296c47a4743c58c8b1
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:40:00Z

IGNITE-4118 .NET: Optimistic transaction example

This closes #1200

commit 474f22fda4c7cf4d7b2623c451cd7c10f0d8c636
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:55:20Z

IGNITE-4119 .NET: add TransactionDeadlockException

[jira] [Created] (IGNITE-5742) .NET: PersistentStore example

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5742:
--

 Summary: .NET: PersistentStore example
 Key: IGNITE-5742
 URL: https://issues.apache.org/jira/browse/IGNITE-5742
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 2.1
Reporter: Pavel Tupitsyn
 Fix For: 2.2


See {{PersistentStoreExample.java}}, add similar example in .NET.



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

Re: Apache Ignite 2.1 scope

[Denis Magda]

Cos,

IMO, If we really want to get a valuable feedback from a wider audience then in 
addition to the new version the audience has to be given both a high-level and 
deep documentation, proper messaging, etc. It will take time to soak in the 
information and a week might not be enough in general.

This is why I would not make the voting process longer but rather give the 
release and all the materials to our users and look forward to the feedback. 
Basing on the feedback we can always release a next version whenever is needed.

—
Denis
  
> On Jul 10, 2017, at 3:01 PM, Konstantin Boudnik  wrote:
> 
> That's an interesting statement to make, considering the a PMC is
> legally responsible for the release they are making and voting for.
> What I believe it would achieve is to give a wider group of our users
> a chance to get and install the new version and try some of the most
> prominent features, while giving the feedback. Even if expressed in
> the form of non-binding votes.
> --
>  Take care,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
> 
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
> 
> 
> On Sat, Jul 8, 2017 at 8:26 AM, Dmitriy Setrakyan  
> wrote:
>> Cos,
>> 
>> I am not sure what a 7 day vote will accomplish. As we all know, Apache
>> [VOTE] is not about the release quality, but about proper build procedure,
>> release signing, and licensing. I do not see the community needing more
>> time than usual to verify this release.
>> 
>> D.
>> 
>> On Fri, Jul 7, 2017 at 8:14 PM, Konstantin Boudnik  wrote:
>> 
>>> Fair enough, I will try to collect more and share with the team.
>>> 
>>> And +1 on the proposed release schedule: considering the complexity of the
>>> changes we better have some time to play with the bits. In fact, I'd
>>> suggest
>>> we give it 7 days for the [VOTE] so people have time to play with the bits.
>>> Thoughts?
>>> 
>>> Cos
>>> 
>>> On Thu, Jul 06, 2017 at 11:06AM, Vladimir Ozerov wrote:
 Cos,
 
 I am not aware of performance degradation in regards to Cassandra. AFAIK
 there were extensive benchmarking prior to 2.0 release. And in the end
>>> 2.0
 release had performance not worse than 1.9. If you have more information
>>> on
 the matter, let's discuss it in the separate thread.
 
 On Thu, Jul 6, 2017 at 11:04 AM, Vladimir Ozerov 
 wrote:
 
> Vyacheslav, Denis,
> 
> 7 July is too abrupt date. Scope of 2.1 is still too broad, and what is
> more important - persistent store has been merged only several days
>>> ago. We
> need some room for stabilization. I propose the following timeline:
> 16 July - code freeze
> 17-21 July - QA
> 21-24 July - vote and release
> 
> On Thu, Jul 6, 2017 at 4:30 AM, Konstantin Boudnik 
>>> wrote:
> 
>> Thanks everyone for giving us enough time to take a look into the code
>> and architecture of this new feature. The webinar was certainly quite
>> helpful (thanks Denis!).
>> 
>> It seems to be a good time to add the feature into the dot-release, so
>> more users can have a taste of it "officially". I have a somewhat
>> unrelated question though: it seems that 2.0 has significant
>> performance degradation compared to 1.8 when it get to the working
>> with external distributed storage (like Cassandra). Could it be caused
>> by all the changes that were made between 1.8 and 2.0 in the
>> preparation for the coming persistent store functionality? Are we
>> publishing/collecting say yardstick reports for our own releases?
>> 
>> Thanks!
>>  Cos
>> --
>>  Take care,
>> Konstantin (Cos) Boudnik
>> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>> 
>> Disclaimer: Opinions expressed in this email are those of the author,
>> and do not necessarily represent the views of any company the author
>> might be affiliated with at the moment of writing.
>> 
>> 
>> On Tue, Jul 4, 2017 at 3:20 AM, Vladimir Ozerov > wrote:
>>> Igniters,
>>> 
>>> Persistent store has been merged to master branch! "master-bak"
>>> branch
>> was
>>> created to keep the state before merge for safety. As release date
>>> for
>> 2.1
>>> is mid July, I created "ignite-2.1" branch where we will stabilize
>>> the
>>> release as usual. Please push features and fixes planned for 2.1
>> release to
>>> this branch. The rest commits should go to master.
>>> 
>>> Vladimir.
>>> 
>>> On Mon, Jul 3, 2017 at 4:18 PM, Vladimir Ozerov <
>>> voze...@gridgain.com>
>>> wrote:
>>> 
 Hi Denis,
 
 Awesome news! I'll take care of 

[jira] [Created] (IGNITE-5743) .NET: PageMemory and PersistentStore documentation

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5743:
--

 Summary: .NET: PageMemory and PersistentStore documentation
 Key: IGNITE-5743
 URL: https://issues.apache.org/jira/browse/IGNITE-5743
 Project: Ignite
  Issue Type: Task
  Components: documentation, platforms
Affects Versions: 2.1
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.1


Add documentation on https://apacheignite-net.readme.io/docs.
It should mostly refer to Java pages, but we need configuration examples in C# 
and app.config XML.



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

Re: Patch for IGNITE-5597 is ready.

[Elen Code]

Many thanks.
Done.
Andrei 

On Wednesday, July 12, 2017 3:03 PM, Anton Vinogradov 
 wrote:
 

 Hi,

Thanks for interest to Apache Ignite development.

I'd like to propose you to make direct "review request".
This should help to speedup review process, you can find tips here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#
HowtoContribute-SubmittingforReview

On Tue, Jul 11, 2017 at 12:48 PM, Elen Code 
wrote:

> Hi Ignite team,
> I'm finished with https://issues.apache.org/jira/browse/IGNITE-5597. It
> is small ticket about changing JavaDocs.Please review pull-request:
> https://github.com/apache/ignite/pull/2268
>
> Regards,Andrei


   

[jira] [Created] (IGNITE-5741) Replace HeapByteBuffer to DirectByteBuffer in WAL RecordsIterator

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-5741:
--

 Summary: Replace HeapByteBuffer to DirectByteBuffer in WAL 
RecordsIterator
 Key: IGNITE-5741
 URL: https://issues.apache.org/jira/browse/IGNITE-5741
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Affects Versions: 2.1
Reporter: Dmitriy Govorukhin
Priority: Critical
 Fix For: 2.2


In current implementation we can get OOM during iterate on wal records, because 
some wal record may be very large (more that 64Mb). We read using  
HeapByteBuffer, FileChannel reserve buffer same size as our HeapByteBuffer, but 
by default FileChannel can not allocate buffer more that 64Mb. (maxMemory = 
VM.maxDirectMemory())

{code}
[16:07:54]W: [org.apache.ignite:ignite-core] [2017-07-12 
13:07:54,809][ERROR][exchange-worker-#55966%node0-primary%][GridDhtPartitionsExchangeFuture]
 Failed to reinitialize local partitions (preloading will be stopped): 
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=3, 
minorTopVer=1], nodeId=105056d5, evt=DISCOVERY_CUSTOM_EVT]
[16:07:54]W: [org.apache.ignite:ignite-core] 
java.lang.OutOfMemoryError: Direct buffer memory
[16:07:54]W: [org.apache.ignite:ignite-core]at 
java.nio.Bits.reserveMemory(Bits.java:658)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
java.nio.DirectByteBuffer.(DirectByteBuffer.java:123)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:306)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
sun.nio.ch.Util.getTemporaryDirectBuffer(Util.java:174)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
sun.nio.ch.IOUtil.read(IOUtil.java:195)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:149)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIO.read(RandomAccessFileIO.java:62)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileInput.ensure(FileInput.java:116)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:303)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readByte(FileInput.java:376)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readUnsignedByte(FileInput.java:385)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:697)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:673)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.initReadHandle(AbstractWalRecordsIterator.java:243)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.advanceSegment(FileWriteAheadLogManager.java:2452)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:149)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.(FileWriteAheadLogManager.java:2352)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.(FileWriteAheadLogManager.java:2290)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.replay(FileWriteAheadLogManager.java:553)
[16:07:54]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreMemory(GridCacheDatabaseSharedManager.java:1313)
[16:07:54]W: [org.apache.ignite:ignite-core]at 

RE: Hello

[andrey.davydov]

Hello Pavel. I’m has no experience how to contribute to apache backed projects. 
But I would like to implement https://issues.apache.org/jira/browse/IGNITE-5602 
feature. Issue was created after my request in freshdesk. I’ve already post 
patch in issue comment.  

Отправлено из Почты для Windows 10

От: Pavel Tupitsyn
Отправлено: 12 июля 2017 г. в 17:57
Кому: dev@ignite.apache.org
Тема: Re: Hello

Hello Andrey, welcome to Apache Ignite developers mailing list.
Do you need help with something?

On Wed, Jul 12, 2017 at 5:45 PM,  wrote:

> Hello
>
>

Re: Hello

[Pavel Tupitsyn]

Hello Andrey, welcome to Apache Ignite developers mailing list.
Do you need help with something?

On Wed, Jul 12, 2017 at 5:45 PM,  wrote:

> Hello
>
>

Hello

[andrey.davydov]

Hello

Hello

[andrey.davydov]

Hello

[GitHub] ignite pull request #2286: IGNITE-5740 created new benchmark for load transa...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-5740 created new benchmark for load transaction



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

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

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

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


commit 9502400e348c8a0184ff11a26a3c0ed893bb4d82
Author: oleg-ostanin 
Date:   2017-07-12T11:06:32Z

IGNITE-5740 created new benchmark for load transaction




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

[Anton Vinogradov]

Hi,

Thanks for interest to Apache Ignite development.

I'd like to propose you to make direct "review request".
This should help to speedup review process, you can find tips here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#
HowtoContribute-SubmittingforReview

On Wed, Jul 12, 2017 at 1:48 PM, Evgeniy Ignatiev <
yevgeniy.ignat...@gmail.com> wrote:

> Provided a patch - https://github.com/apache/ignite/pull/2285, the change
> is straight-forward - simply placed PluginProvider#onIgniteStart right
> after components #onKernalStart callbacks are called. In basic test suite
> (as I can see it includes platform and plugin tests) -
> http://ci.ignite.apache.org/viewLog.html?buildId=720722=
> buildResultsDiv=IgniteTests_IgniteBasic there seem to be no
> new failed platform tests, other failed tests seem to fail in several other
> reviews too and be unrelated to my changes.
>
> Would you be so kind to review my pull-request?
>
> Best regards,
>
> Evgeniy.
>
>
> On 05.07.2017 12:35, Evgeniy Ignatiev wrote:
>
>> Would you mind if I pick the https://issues.apache.org/jira
>> /browse/IGNITE-5123 and place PluginProvider#onIgniteStart after the
>> component callbacks are called to comply with its Javadoc?
>>
>>
>> On 04.07.2017 18:06, Evgeniy Ignatiev wrote:
>>
>>> As it is explicitly stated in Javadoc of PluginProvider#onIgniteStart
>>> that all internal components should be started before this method is
>>> called, which is not true, as internal component callbacks are called right
>>> after the PluginProvider#onIgniteStart.
>>>
>>> On 7/2/2017 12:58 PM, Evgeniy Ignatiev wrote:
>>>
 Hello, Igniters.

 Looking at the ticket https://issues.apache.org/jira/browse/IGNITE-5123,
 the IgniteKernal#start notifies plugin providers, calling
 PluginProvider#onIgniteStart, before components are notified, when caches
 are created in GridCacheProcessor#onIgniteStart. Does it make sense to
 move plugin providers notification after components are notified, probably
 right before lifecycle beans notification, so to ensure that caches are
 started before PluginProvider#onIgniteStart method is called?



>>>
>>
>

Re: Patch for IGNITE-5597 is ready.

[Anton Vinogradov]

Hi,

Thanks for interest to Apache Ignite development.

I'd like to propose you to make direct "review request".
This should help to speedup review process, you can find tips here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#
HowtoContribute-SubmittingforReview

On Tue, Jul 11, 2017 at 12:48 PM, Elen Code 
wrote:

> Hi Ignite team,
> I'm finished with https://issues.apache.org/jira/browse/IGNITE-5597. It
> is small ticket about changing JavaDocs.Please review pull-request:
> https://github.com/apache/ignite/pull/2268
>
> Regards,Andrei

Re: IGNITE-5123

[Evgeniy Ignatiev]

Provided a patch - https://github.com/apache/ignite/pull/2285, the 
change is straight-forward - simply placed PluginProvider#onIgniteStart 
right after components #onKernalStart callbacks are called. In basic 
test suite (as I can see it includes platform and plugin tests) - 
http://ci.ignite.apache.org/viewLog.html?buildId=720722=buildResultsDiv=IgniteTests_IgniteBasic 
there seem to be no new failed platform tests, other failed tests seem 
to fail in several other reviews too and be unrelated to my changes.


Would you be so kind to review my pull-request?

Best regards,

Evgeniy.

On 05.07.2017 12:35, Evgeniy Ignatiev wrote:
Would you mind if I pick the 
https://issues.apache.org/jira/browse/IGNITE-5123 and place 
PluginProvider#onIgniteStart after the component callbacks are called 
to comply with its Javadoc?



On 04.07.2017 18:06, Evgeniy Ignatiev wrote:
As it is explicitly stated in Javadoc of PluginProvider#onIgniteStart 
that all internal components should be started before this method is 
called, which is not true, as internal component callbacks are called 
right after the PluginProvider#onIgniteStart.


On 7/2/2017 12:58 PM, Evgeniy Ignatiev wrote:

Hello, Igniters.

Looking at the ticket 
https://issues.apache.org/jira/browse/IGNITE-5123, the 
IgniteKernal#start notifies plugin providers, calling 
PluginProvider#onIgniteStart, before components are notified, when 
caches are created in GridCacheProcessor#onIgniteStart. Does it make 
sense to move plugin providers notification after components are 
notified, probably right before lifecycle beans notification, so to 
ensure that caches are started before PluginProvider#onIgniteStart 
method is called?

[jira] [Created] (IGNITE-5739) JVM crash on node deactivation

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-5739:


 Summary: JVM crash on node deactivation
 Key: IGNITE-5739
 URL: https://issues.apache.org/jira/browse/IGNITE-5739
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.1
Reporter: Alexey Kuznetsov
Assignee: Semen Boikov
 Fix For: 2.1


Start one node (with persistence).
Activate
Deactivate - node crashed.



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

[jira] [Created] (IGNITE-5740) Transactional load benchmark

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-5740:


 Summary: Transactional load benchmark
 Key: IGNITE-5740
 URL: https://issues.apache.org/jira/browse/IGNITE-5740
 Project: Ignite
  Issue Type: Improvement
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


We need to create an additional benchmark to measure huge transactions time. 



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

[jira] [Created] (IGNITE-5737) Web Console: make cluster a root configuration entity

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-5737:


 Summary: Web Console: make cluster a root configuration entity
 Key: IGNITE-5737
 URL: https://issues.apache.org/jira/browse/IGNITE-5737
 Project: Ignite
  Issue Type: Sub-task
  Components: UI, wizards
Reporter: Ilya Borisov
Assignee: Andrey Novikov


It has been agreed upon to make cluster a root entity for configuration 
screens. That means that all caches/igfs/models will not be shared among 
clusters and be owned by a single cluster instead of current many to many 
relation.

Backend requirements:
1. Implement REST endpoints to manage clusters.

Frontend requirements:
1. Remove cluster selection from cluster edit screens.
2. Remove cluster selection from basic/caches/igfss/models screens.



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

Re: Testing of backward compatibility in Ignite

[Semyon Boikov]

It is possible to implement a test plugin which will
override DiscoveryNodeValidationProcessor.

Also IMO it is better to start different Ignite versions in different
processes to avoid potential problems with custom classloaders (there is
already some helper classes for multi-jvm tests).

Thanks

On Wed, Jul 12, 2017 at 12:44 PM, Anton Vinogradov  wrote:

> Semen,
>
> As far as I know, it is possible to allow nodes with different versions to
> join topology.
> Some products based on Ignite provides this feature.
>
> We'd like to check that changes at Ignite will not break compatibility
> feature of these products.
>
> Could you provide some tips how to connect different versions of Ignite in
> proper way?
>
>
> On Wed, Jul 12, 2017 at 12:05 PM, Semyon Boikov 
> wrote:
>
> > Hi Vyacheslav,
> >
> > Currently Ignite nodes with different versions can not join the same
> > cluster, look at OsDiscoveryNodeValidationProcessor (this check is
> called
> > from discovery ServerImpl IgniteSpiContext.validateNode).
> >
> > Thanks
> >
> > On Wed, Jul 12, 2017 at 11:09 AM, Vyacheslav Daradur <
> daradu...@gmail.com>
> > wrote:
> >
> > > Hi Igniters.
> > >
> > > There is a need to test backward compatibility with previous release
> > within
> > > a task[1].
> > >
> > > As far as I understand: it needs to provide methods in the
> > > Ignite-test-framework to start instance of specific version of Ignite.
> > >
> > > I popose to add such api in the project, for example: "Ignite
> > > startGrid(String ver)"
> > >
> > > My main idea of implementation is:
> > > 1) download "jar" from the Maven repo
> > > 2) Wrap it in a custom classloader
> > > 3) Start instance via the classloader
> > >
> > > I've created a ticket[2] for this task.
> > >
> > > Guys, please, share your thoughts about described problem and ways of
> > > implementation?
> > >
> > > [1] BinaryMarshaller should write ints in "varint" encoding where it
> > makes
> > > sense 
> > > [2] Provide API to test compatibility with old releases
> > > 
> > >
> > > --
> > > Best Regards, Vyacheslav D.
> > >
> >
>

Re: Testing of backward compatibility in Ignite

[Anton Vinogradov]

Semen,

As far as I know, it is possible to allow nodes with different versions to
join topology.
Some products based on Ignite provides this feature.

We'd like to check that changes at Ignite will not break compatibility
feature of these products.

Could you provide some tips how to connect different versions of Ignite in
proper way?


On Wed, Jul 12, 2017 at 12:05 PM, Semyon Boikov 
wrote:

> Hi Vyacheslav,
>
> Currently Ignite nodes with different versions can not join the same
> cluster, look at OsDiscoveryNodeValidationProcessor (this check is called
> from discovery ServerImpl IgniteSpiContext.validateNode).
>
> Thanks
>
> On Wed, Jul 12, 2017 at 11:09 AM, Vyacheslav Daradur 
> wrote:
>
> > Hi Igniters.
> >
> > There is a need to test backward compatibility with previous release
> within
> > a task[1].
> >
> > As far as I understand: it needs to provide methods in the
> > Ignite-test-framework to start instance of specific version of Ignite.
> >
> > I popose to add such api in the project, for example: "Ignite
> > startGrid(String ver)"
> >
> > My main idea of implementation is:
> > 1) download "jar" from the Maven repo
> > 2) Wrap it in a custom classloader
> > 3) Start instance via the classloader
> >
> > I've created a ticket[2] for this task.
> >
> > Guys, please, share your thoughts about described problem and ways of
> > implementation?
> >
> > [1] BinaryMarshaller should write ints in "varint" encoding where it
> makes
> > sense 
> > [2] Provide API to test compatibility with old releases
> > 
> >
> > --
> > Best Regards, Vyacheslav D.
> >
>

[GitHub] ignite pull request #2285: IGNITE-5123

[YevIgn]

GitHub user YevIgn opened a pull request:

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

IGNITE-5123



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

$ git pull https://github.com/YevIgn/ignite ignite-5123

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

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


commit b329b100549d6608f126bc35c9cc62c2e6e693e7
Author: Evgeniy Ignatiev 
Date:   2017-07-12T09:33:06Z

IGNITE-5123 Reorder ignite plugin provider on Ignite start callback call

So that PluginProvider#onIgniteStart will be called after internal
components start callbacks have been executed to comply with itself
javadoc.




---
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 #2284: Ignite 5103 Drop client from cluster on missed he...

[dkarachentsev]

GitHub user dkarachentsev opened a pull request:

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

Ignite 5103 Drop client from cluster on missed heartbeats



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

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

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

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


commit 260f9b2d01b16a98fcb7bc721573b95a72adade2
Author: Pavel Tupitsyn 
Date:   2016-10-31T15:37:49Z

.NET: Fix license header

commit e7d7a59eff6da1cd62e8ffb64405cdf12607b49d
Author: Pavel Tupitsyn 
Date:   2016-10-31T15:43:15Z

IGNITE-4153 .NET: IgniteConfiguration.FailureDetectionTimeout property is 
missing

commit d0f4b23600c655dfb94f6fe0205d1cca7cf19d36
Author: AKuznetsov 
Date:   2016-10-31T16:06:58Z

Fixed license.

commit 5fac786b6dbb179127ac725180acb54d0f6f4b0a
Author: devozerov 
Date:   2016-10-31T18:31:05Z

Merge branch 'ignite-1.6.10' into ignite-1.7.3

commit b8b9abe863ed8139553a9ad7013dfad5a363b4da
Author: devozerov 
Date:   2016-10-31T18:31:22Z

Fixes after merge.

commit 61ab650ecd353b4014a30f793090e9dab3519ad5
Author: devozerov 
Date:   2016-10-31T18:33:59Z

Fixes after merge.

commit 4495efc2aa37ca31214558968fa83598317e830a
Author: Pavel Tupitsyn 
Date:   2016-11-01T10:22:30Z

IGNITE-4117 .NET: Fix ClientReconnectTask completion timing

This closes #1195

commit dc0adf641f0ddac19af84ba0d701b33ee520b067
Author: Pavel Tupitsyn 
Date:   2016-08-16T15:11:34Z

IGNITE-3368 .NET: Improve test coverage

This closes #953

# Conflicts:
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests/Cache/CacheAbstractTest.cs

commit cd0275d95dc6524464a154c74b1e62559b3d8af4
Author: Pavel Tupitsyn 
Date:   2016-08-19T14:34:00Z

IGNITE-3711 .NET: Fix PlatformRawMemory coverage issue

commit d7dee5248332c6c6276c9e21aed4afb3abdd4340
Author: Pavel Tupitsyn 
Date:   2016-07-29T12:40:42Z

IGNITE-3604 .NET: Fix inconsistent namespace imports in examples

Conflicts:
modules/platforms/dotnet/Apache.Ignite.sln.DotSettings

commit 390c8d59cf8d44d9703e5fbf8d9c0f8028a4a172
Author: Pavel Tupitsyn 
Date:   2016-08-11T13:18:14Z

IGNITE-3675 .NET: Use separate caches for different entities in 
QueryExample.

commit 861c1736facdf76c71e93ddada0d8e15b5b2950c
Author: Pavel Tupitsyn 
Date:   2016-08-11T14:32:13Z

IGNITE-3673 .NET: Add examples for distributed joins.

commit 3a9cbed4e692e76ad884e60a4f5edc670e6b3c8f
Author: Pavel Tupitsyn 
Date:   2016-08-08T14:00:04Z

IGNITE-3630 .NET: Add pure binary mode example with put-get and queries.

commit d5e15af76044cf65385672f8528d48ecdeca3cb6
Author: Pavel Tupitsyn 
Date:   2016-11-02T09:02:00Z

IGNITE-4121 .NET: add ScanQuery example

commit 74f8308d10fc011c00e52efcdb315b35cc79e60a
Author: Pavel Tupitsyn 
Date:   2016-11-02T12:59:15Z

IGNITE-4123 .NET: Remove [Serializable] from Employee in examples

commit 92fff630fbf36c82f93bbd9ddd53d11bed44e772
Author: devozerov 
Date:   2016-11-02T14:50:51Z

Restored services compatibility.

commit a62a0136d295486d95c6e2ab5bba88270d831753
Author: dkarachentsev 
Date:   2016-11-02T16:07:45Z

GG-11655 - Fix merge

commit 348593986b56ddfcec4a4455e49d9b279eae4dc8
Author: devozerov 
Date:   2016-11-05T10:28:03Z

Merge branch 'ignite-1.7.3' into ignite-1.7.4

commit 175da6b7e394dd76c27d5155ff98a5b2ef03bb9d
Author: tledkov-gridgain 
Date:   2016-11-07T06:16:58Z

IGNITE-3432:  check data/meta cache names are different for different IGFS 
instances. This closes #1201

commit ead15193899d08f41491166003cabed0560f0c59
Author: Pavel Tupitsyn 
Date:   2016-11-07T07:49:03Z

IGNITE-4028 Get rid of OP_META in PlatformAbstractTarget

This closes #1192

commit 40ef2f5ae42826fe8fd077e3013e8f55c8512bdd
Author: Dmitriy Govorukhin 
Date:   2016-11-07T09:09:41Z

ignite-4178 support permission builder

commit df670c7d64046d282c053f296c47a4743c58c8b1
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:40:00Z

IGNITE-4118 .NET: Optimistic transaction example

This closes #1200

commit 474f22fda4c7cf4d7b2623c451cd7c10f0d8c636
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:55:20Z

IGNITE-4119 .NET: add TransactionDeadlockException

commit 

Re: Testing of backward compatibility in Ignite

[Semyon Boikov]

Hi Vyacheslav,

Currently Ignite nodes with different versions can not join the same
cluster, look at OsDiscoveryNodeValidationProcessor (this check is called
from discovery ServerImpl IgniteSpiContext.validateNode).

Thanks

On Wed, Jul 12, 2017 at 11:09 AM, Vyacheslav Daradur 
wrote:

> Hi Igniters.
>
> There is a need to test backward compatibility with previous release within
> a task[1].
>
> As far as I understand: it needs to provide methods in the
> Ignite-test-framework to start instance of specific version of Ignite.
>
> I popose to add such api in the project, for example: "Ignite
> startGrid(String ver)"
>
> My main idea of implementation is:
> 1) download "jar" from the Maven repo
> 2) Wrap it in a custom classloader
> 3) Start instance via the classloader
>
> I've created a ticket[2] for this task.
>
> Guys, please, share your thoughts about described problem and ways of
> implementation?
>
> [1] BinaryMarshaller should write ints in "varint" encoding where it makes
> sense 
> [2] Provide API to test compatibility with old releases
> 
>
> --
> Best Regards, Vyacheslav D.
>

[jira] [Created] (IGNITE-5736) Add test of backward-compatibility

[Vyacheslav Daradur (JIRA)]

Vyacheslav Daradur created IGNITE-5736:
--

 Summary: Add test of backward-compatibility
 Key: IGNITE-5736
 URL: https://issues.apache.org/jira/browse/IGNITE-5736
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
 Fix For: 2.2


Need to add unit-test to test compatibility with AI 2.0.



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

Testing of backward compatibility in Ignite

[Vyacheslav Daradur]

Hi Igniters.

There is a need to test backward compatibility with previous release within
a task[1].

As far as I understand: it needs to provide methods in the
Ignite-test-framework to start instance of specific version of Ignite.

I popose to add such api in the project, for example: "Ignite
startGrid(String ver)"

My main idea of implementation is:
1) download "jar" from the Maven repo
2) Wrap it in a custom classloader
3) Start instance via the classloader

I've created a ticket[2] for this task.

Guys, please, share your thoughts about described problem and ways of
implementation?

[1] BinaryMarshaller should write ints in "varint" encoding where it makes
sense 
[2] Provide API to test compatibility with old releases


-- 
Best Regards, Vyacheslav D.

[jira] [Created] (IGNITE-5735) NPE during populated data (CacheQueryDdlExample)

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-5735:


 Summary: NPE during populated data (CacheQueryDdlExample)
 Key: IGNITE-5735
 URL: https://issues.apache.org/jira/browse/IGNITE-5735
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.1
Reporter: Ilya Suntsov
 Fix For: 2.1


Steps for reproduce:
1. Start 2 nodes with *examples/config/example-ignite.xml*
2. Start *CacheQueryDdlExample*
Result:
Om example node:
{noformat}
[10:19:17]__   
[10:19:17]   /  _/ ___/ |/ /  _/_  __/ __/ 
[10:19:17]  _/ // (7 7// /  / / / _/   
[10:19:17] /___/\___/_/|_/___/ /_/ /___/  
[10:19:17] 
[10:19:17] ver. 2.1.2#20170711-sha1:2a2c8030
[10:19:17] 2017 Copyright(C) Apache Software Foundation
[10:19:17] 
[10:19:17] Ignite documentation: http://ignite.apache.org
[10:19:17] 
[10:19:17] Quiet mode.
[10:19:17]   ^-- Logging to file 
'/Users/gridgain/Downloads/gridgain-enterprise-fabric-8.1.2/work/log/ignite-9ef688f8.log'
[10:19:17]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[10:19:17] 
[10:19:17] OS: Mac OS X 10.10.5 x86_64
[10:19:17] VM information: Java(TM) SE Runtime Environment 1.8.0_45-b14 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 25.45-b02
[10:19:17] Initial heap size is 256MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[10:19:17] Configured plugins:
[10:19:17]   ^-- GridGain 8.1.2#20170711-sha1:ff30520a
[10:19:17]   ^-- 2017 Copyright(C) GridGain Systems
[10:19:17] 
[10:19:17] Message queue limit is set to 0 which may lead to potential OOMEs 
when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to 
message queues growth on sender and receiver sides.
[10:19:17] Security status [authentication=off, tls/ssl=off]
[10:19:18] Rolling updates are disabled. GridGain version update will require 
full cluster restart. Consider changing 
'GridGainConfiguration.rollingUpdatesEnabled' configuration property.
[2017-07-12 10:19:20,162][ERROR][main][GridEntLicenseProcessor] License 
violation detected:
  ^-- Maximum number of nodes (3/2) is exceeded.
[2017-07-12 10:19:20,162][ERROR][main][GridEntLicenseProcessor] Contact 
sa...@gridgain.com for further assistance. Make sure to include your license 
ID: 9D50E008-472D-430F-8B2D-CFB8A3894C0D
[2017-07-12 10:19:20,163][ERROR][main][GridEntLicenseProcessor] License 
grace/burst period - left 1 hour.
[10:19:20] Performance suggestions for grid  (fix if possible)
[10:19:20] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[10:19:20]   ^-- Disable grid events (remove 'includeEventTypes' from 
configuration)
[10:19:20]   ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM options)
[10:19:20]   ^-- Specify JVM heap max size (add '-Xmx[g|G|m|M|k|K]' to 
JVM options)
[10:19:20]   ^-- Set max direct memory size if getting 'OOME: Direct buffer 
memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
[10:19:20]   ^-- Disable processing of calls to System.gc() (add 
'-XX:+DisableExplicitGC' to JVM options)
[10:19:20] Refer to this page for more performance suggestions: 
https://apacheignite.readme.io/docs/jvm-and-system-tuning
[10:19:20] 
[10:19:20] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[10:19:20] 
[10:19:20] Ignite node started OK (id=9ef688f8)
[10:19:20] Topology snapshot [ver=3, servers=3, clients=0, CPUs=8, heap=5.6GB]

>>> Cache query DDL example started.

>>> Created database objects.

>>> Populated data.
{noformat}

On remote nodes;
{noformat}
SEVERE: Failed to read message [msg=GridIoMessage [plc=0, topic=null, 
topicOrd=-1, ordered=false, timeout=0, skipOnTimeout=false, msg=null], 
buf=java.nio.DirectByteBuffer[pos=4 lim=10001 cap=32768], 
reader=DirectMessageReader [state=DirectMessageState [pos=0, stack=[StateItem 
[stream=DirectByteBufferStreamImplV2 [baseOff=140343292566528, arrOff=-1, 
tmpArrOff=0, tmpArrBytes=0, msgTypeDone=false, msg=null, mapIt=null, it=null, 
arrPos=-1, keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0, 
uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true], 
state=0], null, null, null, null, null, null, null, null, null]], 
lastRead=false], ses=GridSelectorNioSessionImpl [worker=DirectNioClientWorker 
[super=AbstractNioClientWorker [idx=2, bytesRcvd=117764, bytesSent=5240, 
bytesRcvd0=20086, bytesSent0=56, select=true, super=GridWorker 
[name=grid-nio-worker-tcp-comm-2, igniteInstanceName=null, finished=false, 
hashCode=158461243, interrupted=false, 
runner=grid-nio-worker-tcp-comm-2-#19%null%]]], 
writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768], 
readBuf=java.nio.DirectByteBuffer[pos=4 lim=10001 cap=32768], 
inRecovery=GridNioRecoveryDescriptor [acked=10, resendCnt=0, rcvCnt=10, 
sentCnt=10, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode 
[id=9ef688f8-ba58-4b40-8d7c-01c2b8bb7f57, 

[GitHub] ignite pull request #2264: IGNITE-5711 Allowed to run queries on caches with...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1987: IGNITE-3562: Updated updated Lucene version.

[asfgit]

Github user asfgit closed the pull request at:

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


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