Re: IGNITE-6879

Hi Alexey, Did you find the patch is looking good and is ready to be merged? Sincerely, Dmitriy Pavlov чт, 15 мар. 2018 г. в 11:19, Alexey Kukushkin : > Just found the fix is ready - I will review it today or tomorrow. >

Re: (Partition Map) Exchange at wiki

Awesome article, Dmitry! Denis Magda, should we put a link to it from apacheignite.readme.io? --Yakov

[GitHub] ignite pull request #3656: IGNITE-7754 dirty fix for FSYNC on archivation

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/3656 IGNITE-7754 dirty fix for FSYNC on archivation You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7754

[GitHub] ignite pull request #3657: IGNITE-7888: Added support for SQL_ATTR_LOGIN_TIM...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/3657 IGNITE-7888: Added support for SQL_ATTR_LOGIN_TIMEOUT You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7888

[jira] [Created] (IGNITE-7986) GridPartitionStateMap.entrySet() optimization.

Vitaliy Biryukov created IGNITE-7986: Summary: GridPartitionStateMap.entrySet() optimization. Key: IGNITE-7986 URL: https://issues.apache.org/jira/browse/IGNITE-7986 Project: Ignite

[GitHub] ignite pull request #3654: IGNITE-7581 avoiding ConcurrentModificationExcept...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3654 IGNITE-7581 avoiding ConcurrentModificationException when timeout worker handles tx You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3638: IGNITE-7916: GA Grid examples should be ready for...

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

[GitHub] ignite pull request #3643: IGNITE-7811: ODBC: Implemented connection failove...

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

[jira] [Created] (IGNITE-7984) DML: improve deadlock handling

Vladimir Ozerov created IGNITE-7984: --- Summary: DML: improve deadlock handling Key: IGNITE-7984 URL: https://issues.apache.org/jira/browse/IGNITE-7984 Project: Ignite Issue Type: Task

Re: [TeamCity] DataFrame Examples

+1 to sticking to one suite for now. Maybe someday when examples' tests will surpass adequate build time, we'll consider splitting them. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Code inspection

Filed https://issues.apache.org/jira/browse/IGNITE-7985 [1]. > On 18 Mar 2018, at 00:56, Dmitry Pavlov wrote: > > Hello Petr, > > Many members of the community would appreciate such additional code control, > and

[jira] [Created] (IGNITE-7985) Integration JetBrains IntelliJ IDEA code inspections as TC build

Peter Ivanov created IGNITE-7985: Summary: Integration JetBrains IntelliJ IDEA code inspections as TC build Key: IGNITE-7985 URL: https://issues.apache.org/jira/browse/IGNITE-7985 Project: Ignite

Re: IEP-14: Ignite failures handling (Discussion)

Andrey Gura, Why should we have any FailureHandler abstraction? We already have it - this is EventListener. In my view it is better (and cleaner design) to add events (similar to, for example, org.apache.ignite.events.EventType#EVT_NODE_SEGMENTED) like EVT_IGNITE_OOME, EVT_SYS_WORKER_FAILED and

[jira] [Created] (IGNITE-7983) NPE in TxRollbackOnTimeoutNearCacheTest.testRandomMixedTxConfigurations

Andrey Kuznetsov created IGNITE-7983: Summary: NPE in TxRollbackOnTimeoutNearCacheTest.testRandomMixedTxConfigurations Key: IGNITE-7983 URL: https://issues.apache.org/jira/browse/IGNITE-7983

Re: IGNITE-5357 is ready for review (Replicated cache reads load balancing)

Hi Vyacheslav, I've raised 1 concern and several questions in https://reviews.ignite.apache.org/ignite/review/IGNT-CR-509 Could you please address? Sincerely, Dmitriy Pavlov чт, 15 мар. 2018 г. в 13:30, Vyacheslav Daradur : > Dmitry, I'm looking forward to the news. > >

Re: [TeamCity] DataFrame Examples

Hi Igniters, It seems to me it is better to keep one suite. It is reasonable to separate suites if tests requires too much time to run. Using the same suite will save remarkable amount of agent time. Sincerely, Dmitriy Pavlov вс, 18 мар. 2018 г. в 19:34, Nikolay Izhikov :

[GitHub] ignite pull request #3658: ignite-7978 don't check tag on restore in GridCac...

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/3658 ignite-7978 don't check tag on restore in GridCacheDatabaseSharedManager You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-7982) IgniteRepositoryFactory are unable to instantiate non-lazy repository

Pavel Vinokurov created IGNITE-7982: --- Summary: IgniteRepositoryFactory are unable to instantiate non-lazy repository Key: IGNITE-7982 URL: https://issues.apache.org/jira/browse/IGNITE-7982 Project:

Re: Stop nodes after test by default - IGNITE-6842

Dmitry and other igniters, Will you have time to review this issue? I've preperated PR and TC for this, also I've fixed all comments made by Andrey Kuznetsov and Vyacheslav Daradur. I think this is important issue and will make test framework more stable and clear. TC:

Re: Stop nodes after test by default - IGNITE-6842

I agree it is important, I'm going to do a review, but do not have time slot to do. Who could pick up this review? Dmitriy G., could I ask you? пн, 19 мар. 2018 г. в 15:13, Maxim Muzafarov : > Dmitry and other igniters, > > Will you have time to review this issue? > I've

[jira] [Created] (IGNITE-7987) Affinity may be not calculated properly in case of merged exchanges with client nodes

Pavel Kovalenko created IGNITE-7987: --- Summary: Affinity may be not calculated properly in case of merged exchanges with client nodes Key: IGNITE-7987 URL: https://issues.apache.org/jira/browse/IGNITE-7987

[GitHub] ignite pull request #3660: IGNITE-7987 Use all discovery events for affinity...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3660 IGNITE-7987 Use all discovery events for affinity calculation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: [TeamCity] DataFrame Examples

Have you detached template for build Ignite Examples? > On 19 Mar 2018, at 18:08, Nikolay Izhikov wrote: > > Hello, guys. > > I merged to master my fix of tests. [1] > > I edited "Ignite Examples" configuration to Team City to enable testing of > Spark examples. > > 1.

Re: [TeamCity] DataFrame Examples

Petr, thanks for help with Team City configuration issue! В Пн, 19/03/2018 в 18:14 +0300, Nikolay Izhikov пишет: > Yes. > > В Пн, 19/03/2018 в 18:13 +0300, Petr Ivanov пишет: > > Have you detached template for build Ignite Examples? > > > > > > > On 19 Mar 2018, at 18:08, Nikolay Izhikov

[jira] [Created] (IGNITE-7989) ClassNotFoundException org.jsr166.ConcurrentHashMap8

Anton Kalashnikov created IGNITE-7989: - Summary: ClassNotFoundException org.jsr166.ConcurrentHashMap8 Key: IGNITE-7989 URL: https://issues.apache.org/jira/browse/IGNITE-7989 Project: Ignite

Re: [TeamCity] DataFrame Examples

Yes. В Пн, 19/03/2018 в 18:13 +0300, Petr Ivanov пишет: > Have you detached template for build Ignite Examples? > > > > On 19 Mar 2018, at 18:08, Nikolay Izhikov wrote: > > > > Hello, guys. > > > > I merged to master my fix of tests. [1] > > > > I edited "Ignite

[GitHub] ignite pull request #3659: IGNITE-7986: GridPartitionStateMap.entrySet() opt...

GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/3659 IGNITE-7986: GridPartitionStateMap.entrySet() optimization. You can merge this pull request into a Git repository by running: $ git pull https://github.com/BiryukovVA/ignite IGNITE-7986

[jira] [Created] (IGNITE-7988) SQL: Upload benchmarks in mvcc mode

Pavel Kuznetsov created IGNITE-7988: --- Summary: SQL: Upload benchmarks in mvcc mode Key: IGNITE-7988 URL: https://issues.apache.org/jira/browse/IGNITE-7988 Project: Ignite Issue Type: Task

Re: [TeamCity] DataFrame Examples

Hello, guys. I merged to master my fix of tests. [1] I edited "Ignite Examples" configuration to Team City to enable testing of Spark examples. 1. `spark` profile enabled for test plan. 2. `IgniteExamplesSparkSelfTestSuite` added to tests suites list. Test results [2] are OK. Please, Team

[GitHub] ignite pull request #3590: IGNITE-7816: Fixing Spark examples to run correct...

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

[jira] [Created] (IGNITE-7990) Integrate MLP with Distributed Dataset API

Anton Dmitriev created IGNITE-7990: -- Summary: Integrate MLP with Distributed Dataset API Key: IGNITE-7990 URL: https://issues.apache.org/jira/browse/IGNITE-7990 Project: Ignite Issue Type:

Apache Ignite community update for the week of March 19

Hello Igniters! Akmal Chaudhri is in Atlanta this week for a mini-Meetup tour evangelizing Apache Ignite. He just wrapped the OpenIoT Summit North America in Portland last week, where his popular session demonstrated data streaming to an Apache Ignite cluster from embedded devices and

[jira] [Created] (IGNITE-7993) Striped pool can't be disabled

Valentin Kulichenko created IGNITE-7993: --- Summary: Striped pool can't be disabled Key: IGNITE-7993 URL: https://issues.apache.org/jira/browse/IGNITE-7993 Project: Ignite Issue Type:

[GitHub] ignite pull request #3655: IGNITE-7984

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

Re: Ignite-7640 Refactor DiscoveryDataClusterState to be immutable (Done)

Unfortunately in these tests a lot of timeouts occurred. Could you please merge master into your banch and re-run tests? In this case we could be sure failures is not caused by current patch changes. Sincerely, Dmitriy Pavlov пт, 16 мар. 2018 г. в 16:40, Dmitry Pavlov :

[jira] [Created] (IGNITE-7991) MVCC TX Crash recovery

Igor Seliverstov created IGNITE-7991: Summary: MVCC TX Crash recovery Key: IGNITE-7991 URL: https://issues.apache.org/jira/browse/IGNITE-7991 Project: Ignite Issue Type: Task

2 phase waiting for partitions release

Hello Igniters, Current implementation of GridDhtPartitionsExchangeFuture#waitPartitionRelease function doesn't give us 100% guarantees that after this method completes there are no ongoing atomic or transactional updates on current node during main stage of PME. It gives us only guarantee that

Re: (Partition Map) Exchange at wiki

Sure, See a green callout block in this section: https://apacheignite.readme.io/v2.4/docs/cache-modes#section-overview -- Denis On Mon, Mar 19, 2018 at 4:28 AM, Yakov Zhdanov wrote: > Awesome article, Dmitry! > > Denis Magda, should we put a link to it from

[jira] [Created] (IGNITE-7992) Clarify how expiration policy works for durable memory and 3rd pary

Denis Magda created IGNITE-7992: --- Summary: Clarify how expiration policy works for durable memory and 3rd pary Key: IGNITE-7992 URL: https://issues.apache.org/jira/browse/IGNITE-7992 Project: Ignite

Re: (Partition Map) Exchange at wiki

Thank you, Denis. I'm really proud that the wiki now has a link even from official docs. Made some updates in the article. Sincerely Dmitry Pavlov вт, 20 мар. 2018 г., 1:54 Denis Magda : > Sure, > > See a green callout block in this section: >

Re: readme.io weird interface element

Prachi, has you filed the ticket or should I create one? > On 15 Mar 2018, at 23:07, Denis Magda wrote: > > Please create a ticket and let's fix it in the nearest future. > > -- > Denis > > On Thu, Mar 15, 2018 at 12:47 PM, Prachi Garg wrote: > >>

[jira] [Created] (IGNITE-7994) Web console: remove _auth method from frontend Auth service

Ilya Borisov created IGNITE-7994: Summary: Web console: remove _auth method from frontend Auth service Key: IGNITE-7994 URL: https://issues.apache.org/jira/browse/IGNITE-7994 Project: Ignite

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

Guys, What do we understand under "data corruption" here? If a storage is in corrupted state, does it mean that it needs to be completely removed and cluster needs to be restarted without data? If so, I'm not sure any mode that allows corruption makes much sense to me. How am I supposed to use a

[GitHub] ignite pull request #3620: Keep marshaller mappings in consistent state

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

Re: IEP-14: Ignite failures handling (Discussion)

On Mon, Mar 19, 2018 at 2:24 PM, Yakov Zhdanov wrote: > Andrey Gura, > > Why should we have any FailureHandler abstraction? We already have it - > this is EventListener. In my view it is better (and cleaner design) to add > events (similar to, for > example,

[GitHub] ignite pull request #3585: IGNITE-7029 Add an ability to provide multiple co...

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

[GitHub] ignite pull request #3392: ZookeeperDiscovery implementation

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

[jira] [Created] (IGNITE-7980) AgentManager state in frontend is mutable.

Alexander Kalinin created IGNITE-7980: - Summary: AgentManager state in frontend is mutable. Key: IGNITE-7980 URL: https://issues.apache.org/jira/browse/IGNITE-7980 Project: Ignite Issue

[jira] [Created] (IGNITE-7981) Thread hangs on ignite.cluster().active(false) method call

Oleg Ostanin created IGNITE-7981: Summary: Thread hangs on ignite.cluster().active(false) method call Key: IGNITE-7981 URL: https://issues.apache.org/jira/browse/IGNITE-7981 Project: Ignite

Re: MTCGA: IGNITE-7791 and GridDhtPartitionsSingleMessage

Hello Maxim, SingleMessage with exchId=null is sent when a node updates local partitions' state and schedules a background cluster notification. In contrast, when a partition map exchange happends, it is completed with exchId != null. I need more context regarding how this message interferes