Re: [DISCUSS] Page replacement improvement

2020-11-20 Thread Alex Plehanov
Zhenya, > Alexey, we already have changes that partially fixes this issue [1] IGNITE-13086 it's a minor improvement. We still have major problems with our page replacement algorithm (slow page selection and non-optimal page-fault rate). I think changing from random 5 pages to 7 will make things ev

Re: [DISCUSS] Page replacement improvement

2020-11-20 Thread Nikolay Izhikov
Hello, Alex. Do you have a reproducer for a Page memory issues, you described? What is consequences of that types of issues? Can we create some «benchmark» that will measure imrpovements of page replacement algorithm? May be we can use ducktape branch for it? > 20 нояб. 2020 г., в 12:05, Alex

[jira] [Created] (IGNITE-13741) NPE on client reconnect with static caches configured

2020-11-20 Thread Amelchev Nikita (Jira)
Amelchev Nikita created IGNITE-13741: Summary: NPE on client reconnect with static caches configured Key: IGNITE-13741 URL: https://issues.apache.org/jira/browse/IGNITE-13741 Project: Ignite

Re[2]: [DISCUSS] Page replacement improvement

2020-11-20 Thread Zhenya Stanilovsky
  >Zhenya, > >> Alexey, we already have changes that partially fixes this issue [1] >IGNITE-13086 it's a minor improvement. We still have major problems with >our page replacement algorithm (slow page selection and non-optimal >page-fault rate). I think changing from random 5 pages to 7 will m

[jira] [Created] (IGNITE-13742) Fix failed WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime

2020-11-20 Thread Ivan Bessonov (Jira)
Ivan Bessonov created IGNITE-13742: -- Summary: Fix failed WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime Key: IGNITE-13742 URL: https://issues.apache.org/jira/browse/IGNITE-1374

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

2020-11-20 Thread dpavlov . tasks
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New Critical Failure in master Thin client: Node.js https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ThinClientNodeJs?branch=%3Cdefault%3E No changes in the build

[DISCUSS] Release pub-sub Ignite extensions

2020-11-20 Thread Alexey Goncharuk
Igniters, I think we a bit overdue for releasing already migrated extension modules which were removed in Ignite 2.9. As Saikat mentioned, I suggest releasing the following modules: ignite-flink-ext ignite-flume-ext ignite-pub-sub-ext ignite-zeromq-ext ignite-twitter-ext ignite-rocketmq-ext ignite

Re: 2.9.1 release scope and dates

2020-11-20 Thread Steshin Vladimir
Yaroslav, Hi. I suggest to merge minor fix of javadoc: [1]. It should have appeared in 2.9. Commits in master: d3e5b7c11ed037670700eea75851e619d5d1b6b1 and 1654e9fac61842424c08d26a08ef67569f74746a [1] https://github.com/apache/ignite/pull/8448 19.11.2020 17:15, Ivan Daschinsky пишет:

Re: Ignite extensions - ignite-spring-data release.

2020-11-20 Thread Saikat Maitra
Hi Mikhail, Since spring-data-commons is common module and used internally we should be ok to not rename it to spring-data-commons-ext. Thank you for clarifying. Regards, Saikat On Thu, Nov 19, 2020 at 5:02 AM Mikhail Petrov wrote: > Petr, > > The purpose of the spring-data-commons modules is

Re: [DISCUSS] Release pub-sub Ignite extensions

2020-11-20 Thread Saikat Maitra
Thank you Alexey for preparing the release process. We should be good to release all the migrated modules. Regards, Saikat On Fri, Nov 20, 2020 at 5:43 AM Alexey Goncharuk wrote: > Igniters, > > I think we a bit overdue for releasing already migrated extension modules > which were removed in Ig