Re: IGNITE-8167

Any updates? On Sat, Apr 7, 2018 at 2:01 AM Denis Magda wrote: > Pavel, added you to JIRA contributors list. > > -- > Denis > > On Fri, Apr 6, 2018 at 8:12 AM, Pavel Sapezhko > wrote: > > > My JIRA ID: pavel.sapezhko > > As I mentioned above, first

[GitHub] ignite pull request #3898: IGNITE-4210 cache store loading test fixed

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/3898 IGNITE-4210 cache store loading test fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite IGNITE-4210 Alternatively you can

[GitHub] ignite pull request #3888: IGNITE-8346

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

Re: Can't run CPP tests locally on linux machine

Hello, Nikolay, CPP_STAGING is only needed for TC as we the TC obviously does not have root access on agents and thus can't install Ignite to /usr/local directory. Do you run your tests from the VM? Any test failures are not OK. Can you give me a full message? Best Regards, Igor On Fri, Apr

[GitHub] ignite pull request #3899: IGNITE-8355: Hotfix NPE on start node (discovery ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/3899 IGNITE-8355: Hotfix NPE on start node (discovery start race) You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-8356) Possible race at the discovery on the start node

Taras Ledkov created IGNITE-8356: Summary: Possible race at the discovery on the start node Key: IGNITE-8356 URL: https://issues.apache.org/jira/browse/IGNITE-8356 Project: Ignite Issue

[jira] [Created] (IGNITE-8358) Deadlock in IgnitePdsAtomicCacheRebalancingTest

Alexei Scherbakov created IGNITE-8358: - Summary: Deadlock in IgnitePdsAtomicCacheRebalancingTest Key: IGNITE-8358 URL: https://issues.apache.org/jira/browse/IGNITE-8358 Project: Ignite

Re: Writing a helper for KafkaStreamer

Hi Igniters, It seems issue is still in PA state. Who can pick up https://issues.apache.org/jira/browse/IGNITE-5416 review? Sincerely, Dmitriy Pavlov вт, 6 июн. 2017 г. в 10:56, Dmitriy Setrakyan : > Thanks, Mike! Sounds great. > > On Tue, Jun 6, 2017 at 12:26 AM,

Re: Replace Cron4J with Quartz for ignite-schedule module.

Hi Igniters, it seems ticket https://issues.apache.org/jira/browse/IGNITE-5565 is still in PA state. What are our next steps? Who did review of this patch? Sincerely, Dmitriy Pavlov ср, 28 июн. 2017 г. в 1:40, Denis Magda : > Yakov, > > No, the mentioned discussion didn’t

[GitHub] ignite pull request #3723: IGNITE-8013: CPP: Added check of pending snapshot...

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

[GitHub] ignite pull request #3724: IGNITE-8012: CPP: Changed passing by values to pa...

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

[jira] [Created] (IGNITE-8355) NPE on start node with enabled authentication

Taras Ledkov created IGNITE-8355: Summary: NPE on start node with enabled authentication Key: IGNITE-8355 URL: https://issues.apache.org/jira/browse/IGNITE-8355 Project: Ignite Issue Type:

Re: IGNITE-8167

Hi Pavel, It seems that Denis added you to the list of contributors. What updates do you expect? Sincerely, Dmitriy Pavlov пн, 23 апр. 2018 г. в 9:26, Pavel Sapezhko : > Any updates? > > On Sat, Apr 7, 2018 at 2:01 AM Denis Magda wrote: > > >

[GitHub] ignite pull request #3900: Ignite 2.4 master

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3900 Ignite 2.4 master for test purposes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4-master Alternatively

[jira] [Created] (IGNITE-8357) Recreated atomic sequence produces "Sequence was removed from cache"

Pavel Vinokurov created IGNITE-8357: --- Summary: Recreated atomic sequence produces "Sequence was removed from cache" Key: IGNITE-8357 URL: https://issues.apache.org/jira/browse/IGNITE-8357 Project:

[GitHub] ignite pull request #3872: IGNITE-8315 Prevent printing the partition distri...

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

Re: Topology-wide notification on critical errors

Hi Igniters, +1 to idea of sending this failure to 3rd party monitoring tool. I also think most of users have its favorite monitoring tool and connect all systems to it. But I'm not sure it is easy to implement. Sincerely, Dmitriy Pavlov сб, 21 апр. 2018 г. в 13:09, Dmitriy Setrakyan

[GitHub] ignite pull request #3901: -

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/3901 - You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-8156 Alternatively you can review and apply these changes as the

Re: Writing a helper for KafkaStreamer

Dmitriy, I think it would make sense to identify a few committers who could review this ticket and reach out to them. D. On Mon, Apr 23, 2018 at 6:05 AM, Dmitry Pavlov wrote: > Hi Igniters, > > It seems issue is still in PA state. > > Who can pick up

Re: IGNITE-6879

Hi all! Are there any news about PR merging? пн, 16 апр. 2018 г. в 19:43, Роман Меерсон : > Denis, > > module naming fixed > > пн, 16 апр. 2018 г. в 19:24, Denis Magda : > >> Roman, >> >> In my last reply, I voted for your approach - using

Re: IGNITE-6879

No, nothing yet. I'm going to look to new version. пн, 23 апр. 2018 г. в 17:43, Роман Меерсон : > Hi all! > > Are there any news about PR merging? > > пн, 16 апр. 2018 г. в 19:43, Роман Меерсон : > >> Denis, >> >> module naming fixed >> >> пн, 16 апр.

Re: Topology-wide notification on critical errors

Hello Denis! In my opinion, the primary users of this improvement will be developers, who at testing and pre-production stage are encountering errors only when trying production-size clusters. This means they end up with a dozen of log files and have no idea where to start looking at. Since it's

Re: Replace Cron4J with Quartz for ignite-schedule module.

Dmitriy, who is a good candidate within the community to review this ticket? On Mon, Apr 23, 2018 at 6:10 AM, Dmitry Pavlov wrote: > Hi Igniters, > > it seems ticket https://issues.apache.org/jira/browse/IGNITE-5565 is still > in PA state. What are our next steps? > > Who

[GitHub] ignite pull request #3890: IGNITE-8323 : Fixed discoveryEvent listener calls...

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

[jira] [Created] (IGNITE-8359) Severe performance degradation with persistence and data streaming on HDD

Joel Lang created IGNITE-8359: - Summary: Severe performance degradation with persistence and data streaming on HDD Key: IGNITE-8359 URL: https://issues.apache.org/jira/browse/IGNITE-8359 Project: Ignite

[GitHub] ignite pull request #3902: IGNITE 8075: NET: setRollbackOnTopologyChangeTime...

GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/3902 IGNITE 8075: NET: setRollbackOnTopologyChangeTimeout, withLabel, localActiveTransactions, setTxTimeoutOnPartitionMapExchange You can merge this pull request into a Git repository by running:

[GitHub] ignite pull request #3899: IGNITE-8355: Hotfix NPE on start node (discovery ...

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

[GitHub] ignite pull request #2627: IGNITE-5789: if server was restarted, client does...

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

MTCGA: .NET Core Linux tests: process crash (likely due to IGNITE-7770)

Igniters, Andrey G, Andrey K, .NET Core Linux tests started to fail and end prematurely (296 of 959 tests started) on 18 April, and looks like it is caused by IGNITE-7770 [1], because this is related to transactions. I would highly appreciate if you have a look. Let me know if you need help with

[GitHub] ignite pull request #3904: Ignite 2.5.1

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

Re: IGNITE-8167

I'll add to my to-do list. Igniters, any assistance is welcomed here (pre-review), especially from Native Persistence Experts Pavel, could you please add link to TC Run-All to ticket? пн, 23 апр. 2018 г. в 20:32, Pavel Sapezhko : > I've made the patch for some time

Re: Replace Cron4J with Quartz for ignite-schedule module.

Hi Andrey, Could you please pick up review? Sincerely, Dmitriy Pavlov пн, 23 апр. 2018 г. в 17:39, Dmitriy Setrakyan : > Dmitriy, who is a good candidate within the community to review this > ticket? > > On Mon, Apr 23, 2018 at 6:10 AM, Dmitry Pavlov

[jira] [Created] (IGNITE-8360) Page recovery from WAL can be very slow.

Alexei Scherbakov created IGNITE-8360: - Summary: Page recovery from WAL can be very slow. Key: IGNITE-8360 URL: https://issues.apache.org/jira/browse/IGNITE-8360 Project: Ignite Issue

[GitHub] ignite pull request #3903: IGNITE-8310: CPP compilation and tests with boost...

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/3903 IGNITE-8310: CPP compilation and tests with boost 1.62 You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-8310

Re: Orphaned, duplicate, and main-class tests!

Hello! I have reworked my change in three commits: https://github.com/apache/ignite/pull/3464 Part one is to delete some duplicate/unused tests and suites - IGNITE-8344 Part two is to rename abstract tests to *AbstractTest and load/performance

Re: IGNITE-8167

I've made the patch for some time ago. Tests have been passed. I've changed the state of Jira task to "Patch available" almost two weeks ago. The patch is just one line of code, so I think it can be reviewed fast :) Thanks. On Mon, Apr 23, 2018 at 1:23 PM Dmitry Pavlov

Re: GA Grid: Can IGNITE-8242 be include in 2.5 release?

Hi, Yury, there is no code/scope freeze. So feel free to merge your tickets. Thanks. On Sat, Apr 21, 2018 at 1:21 AM, Denis Magda wrote: > Those are isolated changes that shouldn't affect the rest of the platform. > > Andrey G., please approve the merge. I think it's fine to

Apache Ignite 2.4+ Go language client

Hi All, I hope you are well. I released Apache Ignite 2.4+ Go language client: https://github.com/apache-ignite/go-client I updated link here: https://github.com/golang/go/wiki/SQLDrivers Is it possible to add link to my repo to this page?:

Re: Apache Ignite 2.4+ Go language client

Hi Alexander, Awesome thing! Please note that before accepting the client we need to make sure it is operational. Community is currently working on formal test specification. I hope it will be ready soon. As far as NodeJS please note that it is already being developed by community at the moment

[jira] [Created] (IGNITE-8366) Replace service instance parameter with a class name in ServiceConfiguration

Denis Mekhanikov created IGNITE-8366: Summary: Replace service instance parameter with a class name in ServiceConfiguration Key: IGNITE-8366 URL: https://issues.apache.org/jira/browse/IGNITE-8366

RE: Apache Ignite 2.4+ Go language client

Hi Oleg, Thanks for your answer. > Community is currently working on formal test specification. Great. Waiting for this one. > As far as NodeJS please note that it is already being developed by community > at the moment [1]. Cool. I stop my initiatives. Thanks, Aleksandr From: Vladimir

[jira] [Created] (IGNITE-8362) Collect service deployment results asynchronously on coordinator

Denis Mekhanikov created IGNITE-8362: Summary: Collect service deployment results asynchronously on coordinator Key: IGNITE-8362 URL: https://issues.apache.org/jira/browse/IGNITE-8362 Project:

[jira] [Created] (IGNITE-8363) Handle topology changes during service deployment

Denis Mekhanikov created IGNITE-8363: Summary: Handle topology changes during service deployment Key: IGNITE-8363 URL: https://issues.apache.org/jira/browse/IGNITE-8363 Project: Ignite

[jira] [Created] (IGNITE-8364) Propagate deployed services to joining nodes

Denis Mekhanikov created IGNITE-8364: Summary: Propagate deployed services to joining nodes Key: IGNITE-8364 URL: https://issues.apache.org/jira/browse/IGNITE-8364 Project: Ignite Issue

Re: Atomic caches

Val, The logic you describe changed a while ago, with introduction of persistent storage and cache group mechanics. Currently there might exist multiple special caches where data structures are stored. The main reason for it was to give users ability to put different structures into different

Re: MTCGA: .NET Core Linux tests: process crash (likely due to IGNITE-7770)

Hi, Pavel, As I see from build logs, entire test suite crashes after TestTxRollbackOnly failure. It's unclear for me at the moment, why do we get "System.InvalidOperationException: Grid is in invalid state to perform this operation...", but let's merge the fix [1] for TestTxRollbackOnly first.

[jira] [Created] (IGNITE-8361) Use discovery messages for service deployment

Denis Mekhanikov created IGNITE-8361: Summary: Use discovery messages for service deployment Key: IGNITE-8361 URL: https://issues.apache.org/jira/browse/IGNITE-8361 Project: Ignite Issue

[jira] [Created] (IGNITE-8365) Introduce service failure events

Denis Mekhanikov created IGNITE-8365: Summary: Introduce service failure events Key: IGNITE-8365 URL: https://issues.apache.org/jira/browse/IGNITE-8365 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-8367) Implement hot redeployment of services

Denis Mekhanikov created IGNITE-8367: Summary: Implement hot redeployment of services Key: IGNITE-8367 URL: https://issues.apache.org/jira/browse/IGNITE-8367 Project: Ignite Issue Type:

Re: write-through when using SQL updates

Kind of this task was planned some time ago. In addition to what you're putting out, users are asking for an example that shows how to blend key-value and SQL APIs. I already have that example. Hopefully, we'll find resources to get it done soon: IGNITE-7728

[GitHub] ignite pull request #1917: IGNITE-5011: Add validation on args and show prop...

GitHub user vinx13 reopened a pull request: https://github.com/apache/ignite/pull/1917 IGNITE-5011: Add validation on args and show proper warnings on disco command You can merge this pull request into a Git repository by running: $ git pull https://github.com/vinx13/ignite

[GitHub] ignite pull request #1921: IGNITE-5151: Add some warning when offheap evicti...

GitHub user vinx13 reopened a pull request: https://github.com/apache/ignite/pull/1921 IGNITE-5151: Add some warning when offheap eviction occurs You can merge this pull request into a Git repository by running: $ git pull https://github.com/vinx13/ignite ignite-5151

[jira] [Created] (IGNITE-8368) Reimplement queries notebooks list table wth pc-items-table'

Alexander Kalinin created IGNITE-8368: - Summary: Reimplement queries notebooks list table wth pc-items-table' Key: IGNITE-8368 URL: https://issues.apache.org/jira/browse/IGNITE-8368 Project:

Re: Orphaned, duplicate, and main-class tests!

Alexey Goncharuk, Vladimir Ozerov, what do you think about these tests? I believe they were created as a part of variuos optimization and profiling activities. I also think we can remove them since nobody cares about them for too long. Thoughts? Yakov Zhdanov ср, 18 апр. 2018 г., 16:42 Ilya

[GitHub] ignite pull request #3905: IGNITE-5789: if server was restarted, client does...

GitHub user vk23 opened a pull request: https://github.com/apache/ignite/pull/3905 IGNITE-5789: if server was restarted, client doesn't create caches de… …fined in client's configuration 1. Modified test so it fails when client doesn't find its own cache after