[MTCGA]: new failures in builds [4483209] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

Re: SQL query timeout: in progress or abandoned

Ivan, thanks for sharing this discussion. Let's use it for our conversation. - Denis On Thu, Aug 8, 2019 at 11:15 PM Павлухин Иван wrote: > Just for the protocol. There was an original dev-list discussion [1]. > Added a link to the ticket as well. > > [1] >

Re: [EXTERNAL] Re: Replace or Put after PutAsync causes Ignite to hang

> the invoker thread is going to come back eventually Invoker thread can be anything, it can be busy, waiting or aborted. Async is just syntactic sugar to solve "callback hell", compiler transforms it into a state machine with callbacks. In general, the behavior is the same in the end -

Re: [EXTERNAL] Re: Replace or Put after PutAsync causes Ignite to hang

I'm not sure, but I think that in case of async, the invoker thread is going to come back eventually? In case of Java futures with listeners, I think listeners should be invoked from public pool. Regards, -- Ilya Kasnacheev пт, 9 авг. 2019 г. в 19:16, Pavel Tupitsyn : > Well, you can't just

Re: [EXTERNAL] Re: Replace or Put after PutAsync causes Ignite to hang

Well, you can't just take any running thread and make it run your code instead, right? On Fri, Aug 9, 2019 at 1:32 PM Ilya Kasnacheev wrote: > Hello! > > Why can't we dispatch those callbacks in the caller thread? > > Regards, > -- > Ilya Kasnacheev > > > пт, 9 авг. 2019 г. в 09:50, Pavel

New Branch created: ignite-2.7.6

Hi Igniters, This email is for informing about new branch available: 2.7.6 (based on 2.7.5). https://gitbox.apache.org/repos/asf?p=ignite.git;a=shortlog;h=refs/heads/ignite-2.7.6 The branch was set up in the GG's AI Teamcity Bot instance as triggered and tracked:

Re: [MTCGA]: new failures in builds [4480005] needs to be handled

The test is now Ignored. Thanks Ivan for fixing this пт, 9 авг. 2019 г. в 07:03, : > Hi Igniters, > > I've detected some new issue on TeamCity to be handled. You are more than > welcomed to help. > > If your changes can lead to this failure(s): We're grateful that you were > a volunteer to

Re: SecurityTestSuite as a separate test suite at TC

Excuse me! I was wrong. I try to find that parameter on Step 4: Run test suite. One more time, thank you! пт, 9 авг. 2019 г. в 14:05, Petr Ivanov : > Why do you think I did not use it? > > > On 9 Aug 2019, at 13:25, Denis Garus wrote: > > Great! > Could you please add surefire-fork-count-1 to

Re: SecurityTestSuite as a separate test suite at TC

Why do you think I did not use it? > On 9 Aug 2019, at 13:25, Denis Garus wrote: > > Great! > Could you please add surefire-fork-count-1 to additional Maven command line > parameters? > It's crucial. > > Thank you! > > пт, 9 авг. 2019 г. в 12:42, Petr Ivanov >:

Re: [EXTERNAL] Re: Replace or Put after PutAsync causes Ignite to hang

Hello! Why can't we dispatch those callbacks in the caller thread? Regards, -- Ilya Kasnacheev пт, 9 авг. 2019 г. в 09:50, Pavel Tupitsyn : > Иван, > > The fix is to dispatch those callbacks (future listeners) to a different > thread pool, not sure which one though. > If I would do a

Re: SecurityTestSuite as a separate test suite at TC

Great! Could you please add surefire-fork-count-1 to additional Maven command line parameters? It's crucial. Thank you! пт, 9 авг. 2019 г. в 12:42, Petr Ivanov : > Done [1] > > > [1] https://ci.ignite.apache.org/viewLog.html?buildId=4482200 > > On 9 Aug 2019, at 12:02, Denis Garus wrote: > >

[jira] [Created] (IGNITE-12056) Index creation sequence may influence on execution plan.

Stanilovsky Evgeny created IGNITE-12056: --- Summary: Index creation sequence may influence on execution plan. Key: IGNITE-12056 URL: https://issues.apache.org/jira/browse/IGNITE-12056 Project:

Re: SecurityTestSuite as a separate test suite at TC

Done [1] [1] https://ci.ignite.apache.org/viewLog.html?buildId=4482200 > On 9 Aug 2019, at 12:02, Denis Garus wrote: > > Sure! I created the task [1]. > > Thank you! > > 1. https://issues.apache.org/jira/browse/IGNITE-12055 > > > пт, 9

Re: SecurityTestSuite as a separate test suite at TC

Sure! I created the task [1]. Thank you! 1. https://issues.apache.org/jira/browse/IGNITE-12055 пт, 9 авг. 2019 г. в 11:38, Petr Ivanov : > Hi, Denis! > > > Could file a ticket with description, please? > > On 9 Aug 2019, at 11:35, Denis Garus wrote: > > Thanks all for the feedback! > > I

[jira] [Created] (IGNITE-12055) SecurityTestSuite as a separate test suite at TC

Denis Garus created IGNITE-12055: Summary: SecurityTestSuite as a separate test suite at TC Key: IGNITE-12055 URL: https://issues.apache.org/jira/browse/IGNITE-12055 Project: Ignite Issue

Re: SecurityTestSuite as a separate test suite at TC

Hi, Denis! Could file a ticket with description, please? > On 9 Aug 2019, at 11:35, Denis Garus wrote: > > Thanks all for the feedback! > > I think no one is against of proposal. > > Petr, could you please assist with wit separation of SecurityTestSuite? > > чт, 8 авг. 2019 г. в 14:43,

Re: SecurityTestSuite as a separate test suite at TC

Thanks all for the feedback! I think no one is against of proposal. Petr, could you please assist with wit separation of SecurityTestSuite? чт, 8 авг. 2019 г. в 14:43, Denis Garus : > Hello, Ivan! > > >> Could you please provide more details why do we need to run these tests > in forked JVM? >

Re: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Hello, Deni. > Nickolay, could you check if that's a quick upgrade? Yes, I will take a look. В Чт, 08/08/2019 в 11:08 -0700, Denis Magda пишет: > Dmitry, > > Please add this BTree corruption fix to the scope: > https://issues.apache.org/jira/browse/IGNITE-11953 > > Plus, I would upgrade our

Re: [EXTERNAL] Re: Replace or Put after PutAsync causes Ignite to hang

Иван, The fix is to dispatch those callbacks (future listeners) to a different thread pool, not sure which one though. If I would do a .NET-only fix, I would use the default thread pool (non Ignite-specific), for Java-side there is no such thing as I understand. Yes, let's have a ticket to track

Re: [EXTERNAL] Re: Replace or Put after PutAsync causes Ignite to hang

Ilya, Pavel, Do we a have a proposal how to fix the root cause of the problem? Should we a have a ticket for it? ср, 7 авг. 2019 г. в 17:48, Ilya Kasnacheev : > > Hello! > > I think we should definitely stop running futures out of striped pool, > while holding any cache logs (stripe thread

Re: SQL query timeout: in progress or abandoned

Just for the protocol. There was an original dev-list discussion [1]. Added a link to the ticket as well. [1] http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-7285-Add-default-query-timeout-td41828.html пт, 9 авг. 2019 г. в 01:22, Denis Magda : > > Hey Saikat, > > Are you still