[GitHub] ignite pull request #4792: Ignite 2.5 master

Github user alamar closed the pull request at: https://github.com/apache/ignite/pull/4792 ---

[GitHub] ignite pull request #4893: IGNITE-8879 Correct restoring of metastorage and ...

GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/4893 IGNITE-8879 Correct restoring of metastorage and skipping updates of … …other caches on localJoin of node not in baseline. You can merge this pull request into a Git repository by running:

Re: TDE Implementation details.

Hello, Dmitriy. Thank you for feedback! > 1) I suggest changing encrypt() and decrypt() method would take the same type > of parameters. > This uniformity will avoid implementors questions about why encrypt takes > byte[] but decrypt takes ByteBuffer. This is done by a reason. encrypt and

[jira] [Created] (IGNITE-9770) Re-run possible blockers from pr.html

Nikolai Kulagin created IGNITE-9770: --- Summary: Re-run possible blockers from pr.html Key: IGNITE-9770 URL: https://issues.apache.org/jira/browse/IGNITE-9770 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-9773) GridAffinityProcessorMemoryLeakTest should be fixed

Andrey Aleksandrov created IGNITE-9773: -- Summary: GridAffinityProcessorMemoryLeakTest should be fixed Key: IGNITE-9773 URL: https://issues.apache.org/jira/browse/IGNITE-9773 Project: Ignite

[jira] [Created] (IGNITE-9775) Cache.lostPartitions() is empty with single node remaining in the cluster

Roman Novichenok created IGNITE-9775: Summary: Cache.lostPartitions() is empty with single node remaining in the cluster Key: IGNITE-9775 URL: https://issues.apache.org/jira/browse/IGNITE-9775

Release process documentation in wiki

Hi Igniters, We had several hot discussions related to release, and one from reasons we need time to come to consensus was my poor understanding of the process. I decided to contribute currently found facts as a scheme of release process here

Re: TDE Implementation details.

Hi Igniters, I'm sorry I a little bit late to the party, but I found a couple of hours to take a look to TDE-1 implementation https://issues.apache.org/jira/browse/IGNITE-8485 . Nikolay kindly agreed to let me take a look. Most of the change was done well and I totally agree with it. Current

[GitHub] ignite pull request #4894: IGNITE-9673

GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/4894 IGNITE-9673 Fix deadlock of system threads. You can merge this pull request into a Git repository by running: $ git pull https://github.com/NSAmelchev/ignite ignite-9673 Alternatively

[GitHub] ignite pull request #4891: IGNITE-9750

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/4891 IGNITE-9750 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9750-1 Alternatively you can review and apply

Re: Release process documentation in wiki

Dmitriy, thank you. I also making some notes about release. Feedback are welcome. https://cwiki.apache.org/confluence/display/IGNITE/Release+manager+Notes В Вт, 02/10/2018 в 14:42 +0300, Dmitriy Pavlov пишет: > Hi Igniters, > > We had several hot discussions related to release, and one from

[jira] [Created] (IGNITE-9772) Remove term "fabric" from Apache Ignite project completely

Peter Ivanov created IGNITE-9772: Summary: Remove term "fabric" from Apache Ignite project completely Key: IGNITE-9772 URL: https://issues.apache.org/jira/browse/IGNITE-9772 Project: Ignite

[GitHub] ignite pull request #4892: Ignite 2.5.3

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/4892 Ignite 2.5.3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.3 Alternatively you can review and apply these

[jira] [Created] (IGNITE-9774) CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan hangs

Ivan Pavlukhin created IGNITE-9774: -- Summary: CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan hangs Key: IGNITE-9774 URL: https://issues.apache.org/jira/browse/IGNITE-9774

[GitHub] ignite pull request #4888: IGNITE-9760 Fixed NPE on concurrent WAL flush for...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4888 ---

[GitHub] ignite pull request #4895: TDR-18 Introduce read-only cluster mode

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/4895 TDR-18 Introduce read-only cluster mode You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite tdr-18 Alternatively

[GitHub] dspavlov closed pull request #20: Ignite 9645

dspavlov closed pull request #20: Ignite 9645 URL: https://github.com/apache/ignite-teamcity-bot/pull/20 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a

Re: [ML] New features and improvement of ML module for 2.7 release

Whole documentation for all significant features/improvements was prepared by different members of ML community and I hope it will be added to readme.io by @ybabak in a few days. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #4890: IGNITE-9761 fixed deadlock SegmentArchivedStorage...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4890 ---

[GitHub] ignite pull request #4896: Ignite 9084 2.5.1

GitHub user macrergate opened a pull request: https://github.com/apache/ignite/pull/4896 Ignite 9084 2.5.1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9084-2.5.1 Alternatively you can review

Re: [ML] New features and improvement of ML module for 2.7 release

Currently, in release 2.7, the ignite ML has a parity with a Spark ML by ML algorithms, feature preprocessing and other capabilities. I'm going to talk about that in October on two conferences 1) [Ru] Yaroslavl, Open Source Distributed Machine Learning Library for Apache Ignite

RE: Volunteer needed: AWS Elastic Load Balancer IP Findersimplemented

Hi, I took a look at the code, and I believe the patch needs to be enhanced. The patch is about adding TcpDiscoveryApplicationElbIpFinder, but it also deprecates the existing TcpDiscoveryElbIpFinder and replaces it with its copy named TcpDiscoveryClassicElbIpFinder. I’d really prefer if the

RE: Volunteer needed: AWS Elastic Load Balancer IP Findersimplemented

Also, it makes me nervous that we’re lacking any sort of functional tests for AWS-based IP finders (same for GCE, actually). I understand that it’s hard to include tests like that in regular TC runs because we’d have to include some sort of credentials. But let’s think of some sort of a middle

Re: Volunteer needed: AWS Elastic Load Balancer IP Findersimplemented

Thanks for the review Stan. I renamed the existing class TcpDiscoveryElbIpFinder since the name is not clear regarding the actual load balancer being used. The names TcpDiscoveryClassicElbIpFinder and TcpDiscoveryApplicationElbIpFinder provide a clear distinction. I deprecated the existing class

Re: Apache Ignite 2.7 release

I've caught a bug [1] in FsyncModeFileWriteAheadLogManager. It looks like a release blocker to me. [1] https://issues.apache.org/jira/browse/IGNITE-9776 вт, 2 окт. 2018 г. в 13:14, Dmitriy Pavlov : > Hi Anton, > > I definitely agree it is a blocker. > > Sincerely, > Dmitriy Pavlov > > вт, 2

[GitHub] ignite pull request #4897: IGNITE-9769 IgniteCacheAtomicProtocolTest.testPut...

GitHub user SomeFire opened a pull request: https://github.com/apache/ignite/pull/4897 IGNITE-9769 IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky You can merge this pull request into a Git repository by running: $ git pull https://github.com/SomeFire/ignite

[GitHub] ignite pull request #4898: 9769 tests

GitHub user SomeFire opened a pull request: https://github.com/apache/ignite/pull/4898 9769 tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/SomeFire/ignite 9769-tests Alternatively you can review and apply these changes

[jira] [Created] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call

Andrey Kuznetsov created IGNITE-9776: Summary: FsyncModeFileWriteAheadLogManager can block forever in log() call Key: IGNITE-9776 URL: https://issues.apache.org/jira/browse/IGNITE-9776 Project:

Re: Volunteer needed: AWS Elastic Load Balancer IP Findersimplemented

Hi Uday, We should keep classes name as is within all minor releases (2.x). We can schedule rename only to 3.0. We need to keep both classes and methods naming as is to provide compilation guarantee. If someone used existing TcpDiscoveryElbIpFinder from 2.6 release than his or her code should

Re: Apache Ignite 2.7 release

Andrey, Anton, How do you conclude that these tickets are blockers? What is the impact to users and in what circumstances users can met them? Note that we have many hundreds opened bugs, and yet we do not strive to include them all, because bug != blocker. So -1 from my side to including these

Re: Apache Ignite 2.7 release

Hi Igniters, Vladimir, NPEs or hangs in WAL is a completely non-functional grid (if persistence enabled). I see no reasons to release 2.7 with such symptoms until we're sure it is too rare/impossible to reproduce. But it seems it is not the case. I will definitely vote -1 for the release if I'm

[jira] [Created] (IGNITE-9771) Indirect SQL queries are failing

Sergey Grimstad created IGNITE-9771: --- Summary: Indirect SQL queries are failing Key: IGNITE-9771 URL: https://issues.apache.org/jira/browse/IGNITE-9771 Project: Ignite Issue Type: Bug

Re: [ML] New features and improvement of ML module for 2.7 release

Alexey, Thanks for spreading the word about the ML capabilities! *Prachi*, please help us to add the talks Alexey is going to give to Ignite events page: https://ignite.apache.org/events.html Btw, I gave a presentation about Ignite ML + TensorFlow integration today at IMC Summit in the US. It

[GitHub] ignite pull request #4900: Network discovery using consul and S3 resolver to...

GitHub user rahulbsw opened a pull request: https://github.com/apache/ignite/pull/4900 Network discovery using consul and S3 resolver to handle public and private IP mapping Module added to discover node using consul, update aws module adding S3 base address resolution service

[GitHub] ignite pull request #4899: Network discovery using consul and S3 resolver to...

Github user rahulbsw closed the pull request at: https://github.com/apache/ignite/pull/4899 ---

[GitHub] ignite pull request #4899: Network discovery using consul and S3 resolver to...

GitHub user rahulbsw opened a pull request: https://github.com/apache/ignite/pull/4899 Network discovery using consul and S3 resolver to handle public and private IP mapping Module added to discover node using consul, update aws module adding S3 base address resolution service

Re: Apache Ignite 2.7 release

Hello, Dmitriy. I'm sorry, but I don't understand your concern. Vladimir just asks experienced Ignite contributor to *explain impact* of a bug. Why are you scaring us with your "-1"? Is it Apache Way to do so? What should be done for you to return to a constructive discussion? В Ср, 03/10/2018

[jira] [Created] (IGNITE-9759) CacheAsyncOperationsFailoverTxTest#testAsyncFailover test hangs up

Alexey Stelmak created IGNITE-9759: -- Summary: CacheAsyncOperationsFailoverTxTest#testAsyncFailover test hangs up Key: IGNITE-9759 URL: https://issues.apache.org/jira/browse/IGNITE-9759 Project:

[GitHub] ignite pull request #4886: IGNITE-8803 Corrected output for quiet mode

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/4886 IGNITE-8803 Corrected output for quiet mode You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8803

[jira] [Created] (IGNITE-9760) NPE is possible during WAL flushing for FSYNC mode

Anton Kalashnikov created IGNITE-9760: - Summary: NPE is possible during WAL flushing for FSYNC mode Key: IGNITE-9760 URL: https://issues.apache.org/jira/browse/IGNITE-9760 Project: Ignite

[jira] [Created] (IGNITE-9761) Deadlock SegmentArchivedStorage <-> SegmentLockStorage

Anton Kalashnikov created IGNITE-9761: - Summary: Deadlock SegmentArchivedStorage <-> SegmentLockStorage Key: IGNITE-9761 URL: https://issues.apache.org/jira/browse/IGNITE-9761 Project: Ignite

[GitHub] ignite pull request #4883: Ignite 2.4.11

Github user Max-Pudov closed the pull request at: https://github.com/apache/ignite/pull/4883 ---

[GitHub] ignite pull request #4887: IGNITE-9390

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/4887 IGNITE-9390 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9390 Alternatively you can review and apply these

[jira] [Created] (IGNITE-9762) Network partition leads to failures in Ignite's cache

Mo created IGNITE-9762: -- Summary: Network partition leads to failures in Ignite's cache Key: IGNITE-9762 URL: https://issues.apache.org/jira/browse/IGNITE-9762 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #4889: IGNITE-7251 Remove term "fabric" from Ignite deli...

GitHub user vveider opened a pull request: https://github.com/apache/ignite/pull/4889 IGNITE-7251 Remove term "fabric" from Ignite deliverables * removed additional "fabric" inclusion You can merge this pull request into a Git repository by running: $ git pull

Re: Apache Ignite 2.7 release

Hi Igniters. I have one more possible blockers - deadlock in archiver - https://issues.apache.org/jira/browse/IGNITE-9761. I almost fixed it. It seems it should be include to scope. --  Best regards, Anton Kalashnikov 02.10.2018, 00:08, "Dmitriy Setrakyan" : > Thanks, got it. > > On Mon, Oct

[jira] [Created] (IGNITE-9765) Network partition leads to failures in Ignite's queue

Mo created IGNITE-9765: -- Summary: Network partition leads to failures in Ignite's queue Key: IGNITE-9765 URL: https://issues.apache.org/jira/browse/IGNITE-9765 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-9767) Network partition leads to failures in Ignite's semaphore

Mo created IGNITE-9767: -- Summary: Network partition leads to failures in Ignite's semaphore Key: IGNITE-9767 URL: https://issues.apache.org/jira/browse/IGNITE-9767 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-9764) Node may hang on start if cluster state is in transition

Alexey Goncharuk created IGNITE-9764: Summary: Node may hang on start if cluster state is in transition Key: IGNITE-9764 URL: https://issues.apache.org/jira/browse/IGNITE-9764 Project: Ignite

Re: Apache Ignite 2.7 release

Hi Anton, I definitely agree it is a blocker. Sincerely, Dmitriy Pavlov вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov : > Hi Igniters. > > I have one more possible blockers - deadlock in archiver - > https://issues.apache.org/jira/browse/IGNITE-9761. I almost fixed it. > It seems it should be

[jira] [Created] (IGNITE-9766) Network partition leads to failures in Ignite's set

Mo created IGNITE-9766: -- Summary: Network partition leads to failures in Ignite's set Key: IGNITE-9766 URL: https://issues.apache.org/jira/browse/IGNITE-9766 Project: Ignite Issue Type: Bug Affects

Re: Page IO statistics for Ignite

Hi, Thanks you for participate here. I've prepared some draft of IEP-27 , which aggregate information from the thread. Please take a look and give your feedback. Also there are some open questions: 1) We can simple

[jira] [Created] (IGNITE-9768) Network partition leads to failures in Ignite's atomic data types.

Mo created IGNITE-9768: -- Summary: Network partition leads to failures in Ignite's atomic data types. Key: IGNITE-9768 URL: https://issues.apache.org/jira/browse/IGNITE-9768 Project: Ignite Issue Type:

[GitHub] SomeFire opened a new pull request #24: IGNITE-9697 Autocomplete branch for TC field

SomeFire opened a new pull request #24: IGNITE-9697 Autocomplete branch for TC field URL: https://github.com/apache/ignite-teamcity-bot/pull/24 This is an automated message from the Apache Git Service. To respond to the

[jira] [Created] (IGNITE-9769) Replace sleep by fut.get() in the IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 test

Ryabov Dmitrii created IGNITE-9769: -- Summary: Replace sleep by fut.get() in the IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 test Key: IGNITE-9769 URL: https://issues.apache.org/jira/browse/IGNITE-9769

[GitHub] ignite pull request #4887: IGNITE-9390

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/4887 ---