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

Caused by IGNITE-8552. Will investigate. пт, 21 сент. 2018 г. в 5:39, : > Hi Ignite Developer, > > I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. > I hope you can help. > > *New test failure in master >

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

Igniters, Tests began constantly fails with an exception - `java.sql.Timestamp cannot be cast to java.sql.Date`. The most suspicious commit relates to [1] issue. I've rerun TC using new MTCGA.Bot feature `comment to the JIRA`. Test failure can be also found in `pull/4692/head` PR of TC build [2]

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

Vladimir, Thank you! On Fri, 21 Sep 2018 at 09:28 Vladimir Ozerov wrote: > Caused by IGNITE-8552. Will investigate. > > пт, 21 сент. 2018 г. в 5:39, : > > > Hi Ignite Developer, > > > > I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. > > I hope you can help. > > > >

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

Hi, Dmitriy, I checked 7618 and previous commits: test fails locally starting from 7618. It fails because `cache.get()` remembers deactivated state and doesn't check current state. 2018-09-20 18:41 GMT+03:00 Dmitriy Pavlov : > Hi, > > IgniteStandByClusterTest seems to fail, Dmitriy G., Ivan,

[GitHub] ignite pull request #4801: IGNITE-9658 Add ability to skip free initialized ...

GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/4801 IGNITE-9658 Add ability to skip free initialized memory regions on de… …activation. You can merge this pull request into a Git repository by running: $ git pull

Re: Using materialised views for queries with joins

Sven, At this point you can do that with CQ and normal cache - just list for events from other caches, and update your own cache as needed. Or you can query your tables periodically and save query result to the cache. Essentially these are very simplified foundation of materialized views in real

IgniteEvents for MVCC caches

Hi Igniters, As you might know MVCC was introduced in Apache Ignite. We started IgniteEvents implementation for MVCC caches and faced some obstacles. I would like to start a discussion about next steps which should be done to deal with current problems. -- Best regards, Ivan Pavlukhin

[GitHub] ignite pull request #4802: IGNITE-9657 Fix socket leak in TcpDiscoverySpi

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/4802 IGNITE-9657 Fix socket leak in TcpDiscoverySpi You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9657

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

Dmitry, Dmitry I've run MTCGA.Bot with additional commenting to JIRA [1] and bot have shown the report [2] of TC Run all without mentioning `IgniteOptimizationDateFuncSpec` test failure. Any ideas why it happens? [1] https://issues.apache.org/jira/browse/IGNITE-8552 [2]

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

Hi Maxim, I think it is because the test already failed in master, so bot considers this test failure in the branch is not an issue. The bot does not analyze dates and happens-before of builds :). So Run History for master contains failures, and the bot excludes this test from blockers.

[GitHub] ignite pull request #4803: IGNITE-9618 Need to be replace the data compressi...

GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4803 IGNITE-9618 Need to be replace the data compression algorithm Signed-off-by: a-polyakov You can merge this pull request into a Git repository by running: $ git pull

Re: IgniteEvents for MVCC caches

Hi Igniters, As you might know MVCC was introduced in Apache Ignite. We started IgniteEvents support implementation for MVCC caches and faced some obstacles. I would like to start a discussion about next steps which should be done to deal with current problems. The main theme is about

Re: IgniteEvents for MVCC caches

Hi Ivan, Lock\Unlock events can be used for explicit lock once IGNITE-9324 will be resolved. Most likely we should rethink Lock\Unlock events semantic for mvcc mode rather then just deprecate them. For update events we can provide tx XID as well to allow entry events and TX commit\rollback

[GitHub] ignite pull request #4747: IGNITE-9580: Added setMaxSize for ignite configur...

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

Page IO statistics for Ignite

Hi Igniters, I started IGNITE-8580 ticket related to print page read/write metrics and did some investigation what other databases provide for the similar purposes. Based on the investigation I want to propose my raw vision of how to IGNITE can

[GitHub] ignite pull request #4750: IGNITE-8770: OutOfMemory in Queries1 suite in mas...

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

[jira] [Created] (IGNITE-9661) Improve partition states validation

Pavel Kovalenko created IGNITE-9661: --- Summary: Improve partition states validation Key: IGNITE-9661 URL: https://issues.apache.org/jira/browse/IGNITE-9661 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-9662) Web Console: Optimize Nginx settings

Alexey Kuznetsov created IGNITE-9662: Summary: Web Console: Optimize Nginx settings Key: IGNITE-9662 URL: https://issues.apache.org/jira/browse/IGNITE-9662 Project: Ignite Issue Type:

Re: Apache Ignite 2.7 release

Hello, Igniters. I ping assigners in all tickets hase been planned for 2.7 and work is started. I plan to move all tickets in 'Open' state to 2.8 on Moday, 24 September. Please, respond, if you have any objections. В Ср, 19/09/2018 в 16:02 +0300, Andrey Gura пишет: > Nikolay, > > since we

[jira] [Created] (IGNITE-9664) Found unexpected checkpoint marker after node deactivation.

Stanilovsky Evgeny created IGNITE-9664: -- Summary: Found unexpected checkpoint marker after node deactivation. Key: IGNITE-9664 URL: https://issues.apache.org/jira/browse/IGNITE-9664 Project:

[GitHub] ignite pull request #4806: Add activeAsync to Ignite iface

GitHub user avplatonov opened a pull request: https://github.com/apache/ignite/pull/4806 Add activeAsync to Ignite iface First part of task about avoiding deadlocks while Ignite:active() and stopping grid simultaneously calling You can merge this pull request into a Git

[GitHub] ignite pull request #4804: IGNITE-7251 Remove term "fabric" from Ignite deli...

GitHub user vveider opened a pull request: https://github.com/apache/ignite/pull/4804 IGNITE-7251 Remove term "fabric" from Ignite deliverables You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7251

[GitHub] ignite pull request #4805: IGNITE-9615 Fix exceptions thrown from methods of...

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/4805 IGNITE-9615 Fix exceptions thrown from methods of jdbc2.IgniteConnection You can merge this pull request into a Git repository by running: $ git pull

Re: Switching to real FailureHandler in tests

Thanks to all for participating the discussion. I've updated [1]: now it requires new handler from [2] for completion. [1] https://issues.apache.org/jira/browse/IGNITE-9660 [2] https://issues.apache.org/jira/browse/IGNITE-8227 чт, 20 сент. 2018 г. в 21:56, Vladimir Ozerov : > Stop node handler

[jira] [Created] (IGNITE-9663) MVCC: Data node failure can cause TX hanging.

Andrew Mashenkov created IGNITE-9663: Summary: MVCC: Data node failure can cause TX hanging. Key: IGNITE-9663 URL: https://issues.apache.org/jira/browse/IGNITE-9663 Project: Ignite Issue

[GitHub] ignite pull request #4584: IGNITE-2.4.8.b5

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

[GitHub] ignite pull request #4493: Ignite 1.8.21

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

Re: Apache Ignite 2.7 - Release Procedure issues

Hi, Nikolay I’ve tested vote_3_step_1 and vote_3_step_2 scripts from [1] and they are OK. My configuration: - generated gnupg key (~/.gnupg) - Ubuntu 16.04 (with latest updates) - packages: subversion git unzip alien rpm fakeroot gcc dpkg-sig gnupg-agent Please double check you environment

Re: Page IO statistics for Ignite

Hello Yuri, I might give useful feedback if see how the metrics will look like from the API standpoint. If it's not difficult please create a draft. AS for the interface, in addition to JMX and SQL we need to ensure Visor CMD and Web Console gets updated. *Alex K.*, please join the thread and

Re: Upsource lags and connection timeouts

Folks, Thanks for the investigation! Could you please let us know once the problem will be solved? пт, 21 сент. 2018 г. в 19:28, Dmitriy Pavlov : > Hi Anton, Petr, > > I confirm that TC Bot writes a lot of stuff, so it may create problems for > Cassandra storage. > > The latest version of Bot

Re: Python thin client installation instructions

Hi Dmitry, Thank you for taking the time to explain me everything in such detail :) I am trying to do this because I have to document. In general, I am assuming that a Python thin client user would already have Python installed and be using it. So, I would not suggest adding any disclaimers

Re: IgniteEvents for MVCC caches

Hello Ivan, First of all, it looks like that EVT_CACHE_ENTRY_CREATED, > EVT_CACHE_ENTRY_DESTROYED are legacy came from Ignite 1.x time and have a > little value nowadays. Does anyone have something against deprecating them? These events are used in a pure caching or in-memory data grid use

[GitHub] ignite pull request #4719: IGNITE-9365 Availability zones via spring

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

Re: Python thin client installation instructions

I would add a disclaimer or a prerequisite step. That what other companies do if a user needs to do some basic installation steps. At least mention it. -- Denis On Fri, Sep 21, 2018 at 3:04 PM Prachi Garg wrote: > Hi Dmitry, > > Thank you for taking the time to explain me everything in such

Re: Python thin client installation instructions

Yes, I will mention the prerequisites. -Prachi > On Sep 21, 2018, at 5:18 PM, Denis Magda wrote: > > I would add a disclaimer or a prerequisite step. That what other companies > do if a user needs to do some basic installation steps. At least mention it. > > -- > Denis > >> On Fri, Sep 21,

Fwd: .NET java thread count keeps growing

Pavel, Do you think we can get it fixed in 2.7 time frame? -- Denis -- Forwarded message - From: Ilya Kasnacheev Date: Tue, Sep 18, 2018 at 9:30 AM Subject: Re: .NET java thread count keeps growing To: Hello! I can observe the problem that you are describing. I have created

Re: [GitHub] SomeFire commented on a change in pull request #14: Performance

Got it, thanks! I'll watch this ticket too. пт, 21 сент. 2018 г. в 20:16, Dmitrii Ryabov : > Hi, Dmitiy, > > I created ticket [1] 3 days ago. > > [1] https://issues.apache.org/jira/browse/INFRA-17032 > > 2018-09-19 20:51 GMT+03:00 Dmitriy Pavlov : > >> Hi Dmitriy Ryabov, >> >> could you please

[GitHub] ignite pull request #4808: IGNITE-9655: fix for RPM build

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/4808 IGNITE-9655: fix for RPM build You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-9655 Alternatively you can review and

Re: Apache Ignite 2.7 - Release Procedure issues

Hello, Petr. Seems that rpm build script doesn't work on a lates Ubuntu Linux. I've created a ticket [1] and found a fix for it [2] With one line fix rpm build is working under my environment. Can you check fix on your environment? [1] https://issues.apache.org/jira/browse/IGNITE-9665 [2]

[GitHub] ignite pull request #4809: IGNITE-9082 Throwing checked exception during tx ...

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/4809 IGNITE-9082 Throwing checked exception during tx commit without node stopping leads to data corruption You can merge this pull request into a Git repository by running: $ git pull

Re: [GitHub] SomeFire commented on a change in pull request #14: Performance

Hi, Dmitiy, I created ticket [1] 3 days ago. [1] https://issues.apache.org/jira/browse/INFRA-17032 2018-09-19 20:51 GMT+03:00 Dmitriy Pavlov : > Hi Dmitriy Ryabov, > > could you please create and share INFRA ticket to disable comment > forwarding to the dev list? > > Sincerely, > Dmitriy

[GitHub] ignite pull request #4751: IGNITE-9589

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

[GitHub] ignite pull request #4807: Ignite 2.4.8 p5

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/4807 Ignite 2.4.8 p5 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.8-p5 Alternatively you can review and

Re: Upsource lags and connection timeouts

Anton, We shared this issue with Jetbrains and they found no current problems in logs, except possible problems with database connection (Apache Cassandra). Currently there are no errors in logs. Possible troublemakers though exist: - MTCGA utility “lives” on the same server, possible

Re: Upsource lags and connection timeouts

Hi Anton, Petr, I confirm that TC Bot writes a lot of stuff, so it may create problems for Cassandra storage. The latest version of Bot has optimization of data saving, and its reduces amount of data to be saved to disk. But still, disc separation is a better solution. Sincerely, Dmitriy Pavlov

Teamcity bot failed to load DB

Hi Igniters, Unfortunately, during a regular update, TC Bot database failed to be loaded, so currently, all accumulated builds were lost. This mean - re-login is required for all users, - it may be not so precise detection of blockers, - and some notifications to the dev. list may reappear.

[jira] [Created] (IGNITE-9665) RPM build doesn't work on lates Ubuntu linux

Nikolay Izhikov created IGNITE-9665: --- Summary: RPM build doesn't work on lates Ubuntu linux Key: IGNITE-9665 URL: https://issues.apache.org/jira/browse/IGNITE-9665 Project: Ignite Issue