[GitHub] ignite pull request #3694: IGNITE-5819: SQL: add support for TRUNCATE TABLE ...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/3694 IGNITE-5819: SQL: add support for TRUNCATE TABLE command. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-5819

Re: Apache Ignite nightly release builds

Created a JIRA ticket for that: https://issues.apache.org/jira/browse/IGNITE-8040 -- Denis On Fri, Mar 23, 2018 at 1:27 AM, Dmitriy Setrakyan wrote: > Awesome! Finally instead of asking our users to build from the master, we > can provide a link to the nightly build

[jira] [Created] (IGNITE-8040) Add Ignite nightly builds references to the site

Denis Magda created IGNITE-8040: --- Summary: Add Ignite nightly builds references to the site Key: IGNITE-8040 URL: https://issues.apache.org/jira/browse/IGNITE-8040 Project: Ignite Issue Type:

Re: What's about releasing Ignite 2.5 a bit earlier?

Petr, I think your statement in regards the non-readiness for the production usage is too strong :) The issue you listed treated as usability ones by me. Agree that it's inconvenient to inject ‘--add-modules’ here and there but it doesn't lead to failures at runtime. If I'm still missing

Re: What's about releasing Ignite 2.5 a bit earlier?

Agree with no blocker. Then as developers we just have to send a clear message that "we making it towards Java9/10 honest support, but do not use it yet on prod environments” :) > On 23 Mar 2018, at 22:41, Denis Magda wrote: > > Petr, > > I guess we would need much more

Re: Ignite Direct I/O plugin description added to wiki

Dmitriy, Prachi, Thanks to both of you for the development and documentation of the feature. I've added a reference from readme to Direct I/O section on wiki so that people can learn even more about the capability. -- Denis On Fri, Mar 23, 2018 at 2:34 PM, Dmitry Pavlov

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

Dmitry, Thanks for clarification. So it sounds like if we fix all other modes as we discuss here, NONE would be the only one allowing corruption. I also don't see much sense in this and I think we should clearly state this in the doc, as well print out a warning if NONE mode is used. Eventually,

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

Hi Val, NONE means that the WAL log is disabled and not written at all. Use of the mode is at your own risk. It is possible that restore state after the crash at the middle of checkpoint will not succeed. I do not see much sence in it, especially in production. BACKGROUND is full functional WAL

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

I agree. In my view, any possibility to get a corrupted storage is a bug which needs to be fixed. BTW, can someone explain semantics of NONE mode? What is the difference from BACKGROUND from user's perspective? Is there any particular use case where it can be used? -Val On Fri, Mar 23, 2018 at

Re: Ignite Direct I/O plugin description added to wiki

Hi Prachi, Yes, it's a great description. I'm impressed by how informative and short you managed to make it. Thank you! Sincerely, Dmitriy Pavlov сб, 24 мар. 2018 г. в 0:29, Prachi Garg : > Dmitriy, > > I have documented the Direct I/O plugin. Please review [1] and

Re: Ignite Direct I/O plugin description added to wiki

Dmitriy, I have documented the Direct I/O plugin. Please review [1] and provide comments/feedback in the ticket [2]. [1] https://apacheignite.readme.io/v2.4/docs/durable-memory-tuning#section-enabling-direct-i-o [2] https://issues.apache.org/jira/browse/IGNITE-7466 -Prachi On Wed, Mar 21,

Re: What's about releasing Ignite 2.5 a bit earlier?

Petr, I guess we would need much more time to handle all Java 9/10 tasks. Since none of them looks like a blocker to me, I would suggest us not to rush and target the tasks for 2.4 release. Overall, I see that we're in an agreement in regards the earlier date of 2.5 release. I'll let the rest of

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

Andrey, I understand your point but you are trying to build one more mechanism and introduce abstractions that are already here. Again, please take a look at segmentation policy and event types we already have. Thanks! Yakov

Re: Memory usage per cache

Denis, I'll need to conduct some experiments to estimate the difference. And the answer will depend on numerous parameters: object sizes, number of caches, that share the same data region and so on. пт, 23 марта 2018, 21:53 Denis Magda : > Andrey, > > How good will be the

Re: Rebalancing - how to make it faster

Ilya, That's a decent boost (5-20%) even having WAL enabled. Not sure that we should stake on the WAL "off" mode here because if the whole cluster goes down, it's then the data consistency is questionable. As an architect, I wouldn't disable WAL for the sake of rebalancing; it's too risky. If

Re: Mass TC Run-All during this weekend

Ignite the Team City :) -- Denis On Fri, Mar 23, 2018 at 7:00 AM, Dmitry Pavlov wrote: > Hi Igniters, > > To get the full picture of the tests now, I'm not going to, I'm going to > run a massive Run All this weekend. > > I'm going to start it at 20:00 MSK (17:00 UTC). >

Re: Service grid redesign

Denis, Thanks for the extensive analysis. There is a vast room for optimizations on the service grid side. Yakov, Sam, Alex G., How do you like the idea of the usage of discovery protocol for the service grid system messages exchange? Any pitfalls? -- Denis On Fri, Mar 23, 2018 at 8:01 AM,

Re: Memory usage per cache

Andrey, How good will be the estimate if we go for 1. and utilize pagesFillFactor somehow? In other words, how big can be a difference between 100% precise calculation you the approach you're suggesting? -- Denis On Thu, Mar 22, 2018 at 11:17 AM, Andrey Kuznetsov wrote: >

[jira] [Created] (IGNITE-8039) Binary Client Protocol spec: data types/format clarifications

Alexey Kosenchuk created IGNITE-8039: Summary: Binary Client Protocol spec: data types/format clarifications Key: IGNITE-8039 URL: https://issues.apache.org/jira/browse/IGNITE-8039 Project:

[jira] [Created] (IGNITE-8038) DynamicColumnsConcurrentTransactionalPartitionedSelfTest#testDropColumnCoordinatorChange is flaky

Sergey Chugunov created IGNITE-8038: --- Summary: DynamicColumnsConcurrentTransactionalPartitionedSelfTest#testDropColumnCoordinatorChange is flaky Key: IGNITE-8038 URL:

[jira] [Created] (IGNITE-8037) DynamicColumnsConcurrentTransactionalPartitionedSelfTest#testClientReconnectWithNonDynamicCacheRestart is flaky

Sergey Chugunov created IGNITE-8037: --- Summary: DynamicColumnsConcurrentTransactionalPartitionedSelfTest#testClientReconnectWithNonDynamicCacheRestart is flaky Key: IGNITE-8037 URL:

[GitHub] ignite pull request #3693: IGNITE-8036 MulticastIpFinder is replaced with Vm...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3693 IGNITE-8036 MulticastIpFinder is replaced with VmIpFinder You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-8036) DynamicColumnsAbstractConcurrentSelfTest should not use MulticastIpFinder

Sergey Chugunov created IGNITE-8036: --- Summary: DynamicColumnsAbstractConcurrentSelfTest should not use MulticastIpFinder Key: IGNITE-8036 URL: https://issues.apache.org/jira/browse/IGNITE-8036

Re: .NET: Add "authenticationEnabled" flag to IgntieConfiguration

Thanks, got it, will do. On Fri, Mar 23, 2018 at 4:36 PM, Dmitry Pavlov wrote: > Hi Pavel, > > Related ticket is https://issues.apache.org/jira/browse/IGNITE-7436 > > Sincerely, > Dmitriy Pavlov > > пт, 23 мар. 2018 г. в 16:24, Pavel Tupitsyn : > > >

Re: Service grid redesign

I think it is about time we take another look at our service functionality. All the points you have raised sound reasonable to me. On Fri, Mar 23, 2018 at 6:01 PM, Denis Mekhanikov wrote: > Igniters, > > I'd like to start a discussion on Ignite service grid redesign. > We

Service grid redesign

Igniters, I'd like to start a discussion on Ignite service grid redesign. We have a number of problems in our current architecture, that have to be addressed. Here are the most severe ones: One of them is lack of guarantee, that service is successfully deployed and ready for work by the time,

Mass TC Run-All during this weekend

Hi Igniters, To get the full picture of the tests now, I'm not going to, I'm going to run a massive Run All this weekend. I'm going to start it at 20:00 MSK (17:00 UTC). Are there any objections? If you need to run your branches, rearrange them at the beginning of the queue .. Sincerely,

[jira] [Created] (IGNITE-8035) Duplicated events in ContinuousQuery's Events Listener

Ruslan Gilemzyanov created IGNITE-8035: -- Summary: Duplicated events in ContinuousQuery's Events Listener Key: IGNITE-8035 URL: https://issues.apache.org/jira/browse/IGNITE-8035 Project: Ignite

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

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

Re: Rebalancing - how to make it faster

Denis, > - Don't you want to aggregate the tickets under an IEP? Yes, I think so. > - Does it mean we're going to update our B+Tree implementation? Any ideas how risky it is? One of tickets that I created ( https://issues.apache.org/jira/browse/IGNITE-7935) involves B+Tree modification, but I am

Re: .NET: Add "authenticationEnabled" flag to IgntieConfiguration

Hi Pavel, Related ticket is https://issues.apache.org/jira/browse/IGNITE-7436 Sincerely, Dmitriy Pavlov пт, 23 мар. 2018 г. в 16:24, Pavel Tupitsyn : > Please provide description in IGNITE-8034 and link Java-side ticket there. > > On Fri, Mar 23, 2018 at 4:23 PM, Pavel

Re: .NET: Add "authenticationEnabled" flag to IgntieConfiguration

Hi Pavel, I added the link to original ticket. On Fri, Mar 23, 2018 at 4:24 PM, Pavel Tupitsyn wrote: > Please provide description in IGNITE-8034 and link Java-side ticket there. > > On Fri, Mar 23, 2018 at 4:23 PM, Pavel Tupitsyn > wrote: > >> Hi

Re: .NET: Add "authenticationEnabled" flag to IgntieConfiguration

Please provide description in IGNITE-8034 and link Java-side ticket there. On Fri, Mar 23, 2018 at 4:23 PM, Pavel Tupitsyn wrote: > Hi Vladimir, > > Can you provide more details? > * What does it do? > * Do we need to only propagate the flag to .NET or do anything else? >

Re: .NET: Add "authenticationEnabled" flag to IgntieConfiguration

Hi Vladimir, Can you provide more details? * What does it do? * Do we need to only propagate the flag to .NET or do anything else? * Related ticket? Thanks, Pavel On Fri, Mar 23, 2018 at 2:25 PM, Vladimir Ozerov wrote: > Pavel, > > We introduced new flag

[GitHub] ignite pull request #3692: Suspend resume benchmark

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/3692 Suspend resume benchmark You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite suspend-resume-benchmark Alternatively you can review and

.NET: Add "authenticationEnabled" flag to IgntieConfiguration

Pavel, We introduced new flag IgniteConfiguration.authenticationEnabled recently. Would you mind adding it to IgniteConfigutation.cs [1]? Vladimir. [1] https://issues.apache.org/jira/browse/IGNITE-8034

[jira] [Created] (IGNITE-8034) .NET: Add "authenticationEnabled" flag to IgniteConfiguration

Vladimir Ozerov created IGNITE-8034: --- Summary: .NET: Add "authenticationEnabled" flag to IgniteConfiguration Key: IGNITE-8034 URL: https://issues.apache.org/jira/browse/IGNITE-8034 Project: Ignite

[GitHub] ignite pull request #3572: IGNITE-7814 returned scala211.library.version par...

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

Re: Test 150 clients migrated to `Cache [6]` suite

No objections then. > On 23 Mar 2018, at 13:03, Dmitry Pavlov wrote: > > Hi Dmitriy, > > Thank you for this improvement. > > Hi Petr, > > IMO there is no need to keep Obsolete suites for so long time because > Igniters ususally do not use test history (excepting TC

[GitHub] ignite pull request #3691: IGNITE-7691: Provide info about DECIMAL column sc...

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/3691 IGNITE-7691: Provide info about DECIMAL column scale and precision You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite

[jira] [Created] (IGNITE-8033) Flaky failure TxOptimisticDeadlockDetectionCrossCacheTest.testDeadlock on TC

Aleksey Plekhanov created IGNITE-8033: - Summary: Flaky failure TxOptimisticDeadlockDetectionCrossCacheTest.testDeadlock on TC Key: IGNITE-8033 URL: https://issues.apache.org/jira/browse/IGNITE-8033

[jira] [Created] (IGNITE-8032) Fix issues within TX DML reducer.

Sergey Kalashnikov created IGNITE-8032: -- Summary: Fix issues within TX DML reducer. Key: IGNITE-8032 URL: https://issues.apache.org/jira/browse/IGNITE-8032 Project: Ignite Issue Type:

[GitHub] ignite pull request #3690: IGNITE-7928 .NET: Exception is not propagated to ...

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/3690 IGNITE-7928 .NET: Exception is not propagated to the C# client and th… …e app hangs You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8031) MVCC TX: TxLog does not support partitions rebalance at the moment. We need to implement it.

Roman Kondakov created IGNITE-8031: -- Summary: MVCC TX: TxLog does not support partitions rebalance at the moment. We need to implement it. Key: IGNITE-8031 URL: https://issues.apache.org/jira/browse/IGNITE-8031

Re: Server stores cache data on-heap if client has near cache - IGNITE-4662

Hi Igniters, Alexey, please step in. I did not fully understand issue description, and can't identify if data is still not moved from onheap. I suggest to consider it as outdated if we don't have any additional info. Sincerely, Dmitriy Pavlov чт, 22 мар. 2018 г. в 10:48, Vyacheslav Daradur

[GitHub] ignite pull request #3689: Ignite-1.6.15

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

Re: Test 150 clients migrated to `Cache [6]` suite

Hi Dmitriy, Thank you for this improvement. Hi Petr, IMO there is no need to keep Obsolete suites for so long time because Igniters ususally do not use test history (excepting TC Jedi who helps with monitoring). Moreover, test history itself is global, so still no need to keep suites too

[jira] [Created] (IGNITE-8030) Cluster hangs on deactivation process in time stopping indexed cache

Vladislav Pyatkov created IGNITE-8030: - Summary: Cluster hangs on deactivation process in time stopping indexed cache Key: IGNITE-8030 URL: https://issues.apache.org/jira/browse/IGNITE-8030

Re: Nodes which started in separate JVM couldn't stop properly (in tests)

Dmitry, Nikolay, thanks for your help! Since the changes are merged we are able to implement this feature in Compatibility Testing Framework. It provides us to work flexibly with multi-version cluster and implement new testing scenarios (I know that Ignite doesn't have such feature yet). Does

Re: What's about releasing Ignite 2.5 a bit earlier?

Hi Igniters, There are two tickets I forgot to mention, it is optimisation of Native Persistence: Performing data pages IO outside locks - https://issues.apache.org/jira/browse/IGNITE-7606 - Write removed dirty page during replacement without holding segment write lock -

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

Hi Ivan, IMO we have to add extra FSYNCS for BACKGROUND WAL. Agree? Sincerely, Dmitriy Pavlov пт, 23 мар. 2018 г. в 12:23, Ivan Rakov : > Igniters, there's another important question about this matter. > Do we want to add extra FSYNCS for BACKGROUND WAL mode? I think

[GitHub] ignite pull request #3688: check if changing finder helps to fix the test ha...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3688 check if changing finder helps to fix the test hangs You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

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

Igniters, there's another important question about this matter. Do we want to add extra FSYNCS for BACKGROUND WAL mode? I think that we have to do it: it will cause similar performance drop, but if we consider LOG_ONLY broken without these fixes, BACKGROUND is broken as well. Best Regards,

[jira] [Created] (IGNITE-8029) Web console: wrong behaviour of cluster activation component

Pavel Konstantinov created IGNITE-8029: -- Summary: Web console: wrong behaviour of cluster activation component Key: IGNITE-8029 URL: https://issues.apache.org/jira/browse/IGNITE-8029 Project:

Re: Test 150 clients migrated to `Cache [6]` suite

Nice work! Yet, I have to ask to keep '~[Obsolete] 150 Clients’ build configuration for at least month from latest run until its build history is removed by autoclean — it’ll be nice to keep that test history. > On 23 Mar 2018, at 11:53, Дмитрий Рябов wrote: > >

Re: What's about releasing Ignite 2.5 a bit earlier?

I agree. Fix of LOG_ONLY is critical for Ignite durability and can be done quickly. Another reason to release 2.5 earlier is fix of https://issues.apache.org/jira/browse/IGNITE-7751. It's another critical bug that possibly can lead to checkpoint buffer overflow and corruption of internal data

Test 150 clients migrated to `Cache [6]` suite

Hello Igniters! I migrated test `IgniteCache150ClientsTest` from `150 Clients` suite to ` Cache [6]`, because `150 Clients` contains only one test class and makes ~6min excess Ignite build. So, test suites `150 Clients` and `~[Obsolete] 150 Clients` will be deleted soon.

Re: Apache Ignite nightly release builds

Awesome! Finally instead of asking our users to build from the master, we can provide a link to the nightly build instead. Denis, can you please add these links to the website? D. On Thu, Mar 22, 2018 at 1:27 PM, Petr Ivanov wrote: > It works, thanks! > > > Here is

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

Fixes are quite simple. I expect them to be merged in master in a week in worst case. Best Regards, Ivan Rakov On 22.03.2018 17:49, Denis Magda wrote: Ivan, How quick are you going to merge the fix into the master? Many persistence related optimizations have already stacked up. Probably, we

[GitHub] ignite pull request #3687: IGNITE-8025 runMultiThreadedAsync cancellation fi...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3687 IGNITE-8025 runMultiThreadedAsync cancellation fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite