Re: Ignite Usability: Deadlocks and Starvation

>It's not public API, just implementation detail. >GridFutureAdapter::unregisterWaiter is not thread state in general. It >won't work properly if the argument is not current thread. And also I >couldn't prove clearly it wouldn't drop some unrelated Node in concurrent >operation. Andrey, it seems

[GitHub] ignite pull request #2514: IGNITE-6170: JDBC: make consistent product name a...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/2514 IGNITE-6170: JDBC: make consistent product name across all drivers You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-6170

Re: Ignite Usability: Deadlocks and Starvation

Yakov, it would be good to get rid of the parameter at all. Strictly speaking, such tiny things are not bugs, but can lead to bugs, and I'm curious about the way of improving the situation. > Andrey, it seems unregisterWaiter() method is supposed to be called only > with current thread as paramet

Re: [DISCUSSION] Urgent Ignite bug fix release

Let's include to the release tickets with optimizations of checkpointing algorithm: https://issues.apache.org/jira/browse/IGNITE-6178 https://issues.apache.org/jira/browse/IGNITE-6033 https://issues.apache.org/jira/browse/IGNITE-5961 This will help users who are experiencing problems with slow

Re: [DISCUSS] Ignite Update Checker

Hey guys In my opinion, maven.org is still owned by a third party (Sonatype). We don't know what kind of data analysis or intelligence extraction they run. If Ignite servers all over the world were hitting maven.org periodically asking for an Ignite Maven artifact, it gives Sonatype a clear indic

[jira] [Created] (IGNITE-6184) No checkClusterState() in IgniteKernal.getOrCreateCaches()

Ilya Kasnacheev created IGNITE-6184: --- Summary: No checkClusterState() in IgniteKernal.getOrCreateCaches() Key: IGNITE-6184 URL: https://issues.apache.org/jira/browse/IGNITE-6184 Project: Ignite

[jira] [Created] (IGNITE-6185) Missed toString method in IPFinders

Vasiliy Sisko created IGNITE-6185: - Summary: Missed toString method in IPFinders Key: IGNITE-6185 URL: https://issues.apache.org/jira/browse/IGNITE-6185 Project: Ignite Issue Type: Bug Af

Re: Ignite Usability: Deadlocks and Starvation

Andrey, feel free to file a ticket and remove the parameter =) --Yakov

[jira] [Created] (IGNITE-6186) Remove redundant parameter of GridFutureAdapter::unregisterWaiter()

Andrey Kuznetsov created IGNITE-6186: Summary: Remove redundant parameter of GridFutureAdapter::unregisterWaiter() Key: IGNITE-6186 URL: https://issues.apache.org/jira/browse/IGNITE-6186 Project:

Re: [DISCUSS] Ignite Update Checker

Raul, any ideas on startup counter? BTW, we have google analytics applied to Ignite site. Can it be used to count node starts? --Yakov

Re: [DISCUSSION] Urgent Ignite bug fix release

Agree, let's release new version including tickets mentioned by Denis and Ivan. --Yakov

[GitHub] ignite pull request #2515: IGNITE-6185 Missed toString IPFinder information.

GitHub user vsisko opened a pull request: https://github.com/apache/ignite/pull/2515 IGNITE-6185 Missed toString IPFinder information. Missed toString IPFinder information. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/

[GitHub] ignite pull request #2516: ignite-5714-5

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

Re: Data compression in Ignite 2.0

Hi, should I close the initial ticket [1] as "Won't Fix" and add link to the new discusion about storage compression [2] in comments? [1] https://issues.apache.org/jira/browse/IGNITE-3592 [2] http://apache-ignite-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-td20679.html 2017-08-09

[jira] [Created] (IGNITE-6187) Cache JdbcDatabaseMetadata in JdbcConnection

Ilya Kasnacheev created IGNITE-6187: --- Summary: Cache JdbcDatabaseMetadata in JdbcConnection Key: IGNITE-6187 URL: https://issues.apache.org/jira/browse/IGNITE-6187 Project: Ignite Issue Typ

[GitHub] ignite pull request #2505: IGNITE-6168 Need SSL client authentication during...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2505 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

[jira] [Created] (IGNITE-6188) ODBC: SQLSQLFreeStmt failing if called before all the rows from the result set were fetched.

Igor Sapego created IGNITE-6188: --- Summary: ODBC: SQLSQLFreeStmt failing if called before all the rows from the result set were fetched. Key: IGNITE-6188 URL: https://issues.apache.org/jira/browse/IGNITE-6188

[GitHub] ignite pull request #2517: Ignite 2.1.3.b2

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/2517 Ignite 2.1.3.b2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.3.b2 Alternatively you can review and app

[jira] [Created] (IGNITE-6189) Benchmarks for check LFS used disk space

Aleksey Chetaev created IGNITE-6189: --- Summary: Benchmarks for check LFS used disk space Key: IGNITE-6189 URL: https://issues.apache.org/jira/browse/IGNITE-6189 Project: Ignite Issue Type: I

Re: How to add new build-plan in the TeamCity?

Hi, Do you need to add new build configuration to exist project or you want add new project for your module? About what module do we speak? 2017-08-15 18:57 GMT+03:00 daradurvs [via Apache Ignite Developers] < ml+s2346864n20860...@n4.nabble.com>: > Hi Igniters! > > I am working on new test modul

Re: [DISCUSSION] Urgent Ignite bug fix release

What do you, guys think about next warning? [2017-08-25 17:17:04,718][INFO ][test-runner-#1%internal.GridHomePathSelfTest%][GridHomePathSelfTest0] System cache's MemoryPolicy size is configured to 40 MB. Use MemoryConfiguration.systemCacheMemorySize property to change the setting. [2017-08-25 17:1

Re: [DISCUSSION] Urgent Ignite bug fix release

Igor, I would change the message. How about this: Required RAM size is larger than total physical memory available for OS. > Please change MemoryConfiguration.WhichProperty and > MemoryPolicyConfiguration.WhichProperty to decrease memory allocated for > each node. Also, can we calculate what the

[GitHub] ignite pull request #2203: IGNITE-5456 JDBC thin driver: the statement produ...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/2203 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feat

Re: [DISCUSSION] Urgent Ignite bug fix release

I suppose we should not forget JVM heap size and suggest to reduce both options On Fri, Aug 25, 2017 at 5:24 PM, Dmitriy Setrakyan wrote: > Igor, I would change the message. How about this: > > Required RAM size is larger than total physical memory available for OS. > > Please change MemoryConfi

[GitHub] ignite pull request #2518: IGNITE-2779 BinaryMarshaller caches must be clean...

GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/2518 IGNITE-2779 BinaryMarshaller caches must be cleaned during client reconnect. You can merge this pull request into a Git repository by running: $ git pull https://github.com/NSAmelchev/igni

Testing Ignite Applications Locally

Guys, I want to discuss the subject again. It is pretty vivid that having wide set of local unit and simple integration tests most likely help to avoid many failures and bugs when going to server environment. I participated in many POC and I can say for sure - if developers are not implementing l

Adding sqlline tool to Apache Ignite project

Hi Igniters, I've found one command line tool that can be used for execute queries (DDL/DML) with data from Apache Ignite grid via *org.apache.ignite.IgniteJdbcThinDriver*. Here you can find overview of internal commands of this tool: https://cwiki.apache.org/confluence/display/IGNITE/Overview+sq

[GitHub] ignite pull request #2519: Ignite 6124 last ver fix

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2519 Ignite 6124 last ver fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6124-lastVer-fix Alternati

Re: Adding sqlline tool to Apache Ignite project

Hi Ilya, It will be a useful addition to Ignite. I would include the tool in one of the nearest releases. It’s license is BSD-3 which is compatible with ours. However, there is a note on ASF side saying that BSD licenses can be included without advertising clause [1]. What does it mean for us?

Re: Testing Ignite Applications Locally

Yasha, Sure, I’ll help from the documentation point but will need raw material from you, guys - test snippets, essential configuration parameters, etc. — Denis > On Aug 25, 2017, at 8:30 AM, Yakov Zhdanov wrote: > > Guys, > > I want to discuss the subject again. It is pretty vivid that havi

Re: Adding sqlline tool to Apache Ignite project

Hi Denis, There are two kinds of BSD license, 3-clause and 4-clause. The difference between them is advertising clause: "3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University

Re: Adding sqlline tool to Apache Ignite project

Hi Ilya, Thanks for the clarification! Referring to the page shared by you [1] if we need to get author’s consent in a written form: A permissive license similar to the BSD 2-Clause License, but with a 3rd clause that prohibits others from using the name of the project or its contributors to p

[GitHub] ignite pull request #2520: IGNITE-6183 Make "Node crashed in the middle of c...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2520 IGNITE-6183 Make "Node crashed in the middle of checkpoint" message s… You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2521: Ignite 2.2 - PR for tests run

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2521 Ignite 2.2 - PR for tests run You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.2 Alternatively you can review an

Re: [DISCUSSION] Urgent Ignite bug fix release

An example of current impl: [2017-08-25 19:44:37,740][WARN ][disco-event-worker-#29%internal.GridHomePathSelfTest0%][GridDiscoveryManager] [2017-08-25 19:44:37,740][WARN ][disco-event-worker-#29%internal.GridHomePathSelfTest0%][GridDiscoveryManager] Not enough memory for current process [required

Re: [DISCUSSION] Urgent Ignite bug fix release

This message appears on topology change in case the available memory is exceeded 2017-08-25 19:47 GMT+03:00 Seliverstov Igor : > An example of current impl: > > > [2017-08-25 19:44:37,740][WARN ][disco-event-worker-#29%internal. > GridHomePathSelfTest0%][GridDiscoveryManager] > [2017-08-25 19:44:

Re: [DISCUSS] Ignite Update Checker

I agree with Raul. - providing a ping-back address to a 3rd party might be frown upon by some. And might have a consequences like stats collection about users' infrastructure. - checking an ASF git-repo is easy and won't download any binary data: everything is clear text and could be easily m

Re: [DISCUSSION] Urgent Ignite bug fix release

Igor, what is this flood of WARN messaging coming after the text? Are we really going to print this whole thing out? On Fri, Aug 25, 2017 at 9:49 AM, Seliverstov Igor wrote: > This message appears on topology change in case the available memory is > exceeded > > 2017-08-25 19:47 GMT+03:00 Selive

[jira] [Created] (IGNITE-6190) SQL query fails silently if Set is passed as a parameter

Denis Magda created IGNITE-6190: --- Summary: SQL query fails silently if Set is passed as a parameter Key: IGNITE-6190 URL: https://issues.apache.org/jira/browse/IGNITE-6190 Project: Ignite Issue

SQL fails silently when Set is used as argument

Igniters, One of our users reported this bug to me: https://issues.apache.org/jira/browse/IGNITE-6190 SQL gurus please take a look. — Denis

Re: [DISCUSSION] Urgent Ignite bug fix release

The message without logging layout: Not enough memory for current process [required=29251MB, available=15942MB]. Please change MemoryConfiguration.systemCacheMaxSize and MemoryConfiguration.defaultMemoryPolicySize to decrease memory allocated for each node. Current settings: HeapInit=250MB

Re: [DISCUSS] Ignite Update Checker

Cos, Raul, Thanks for the feedback. I completely agree about Maven Central being a 3rd party repo (did not think about that initially). All your suggestions make sense, but I would like to keep it as simple as possible, and so far everything suggested required GIT dependencies and extra work. How

Re: [DISCUSSION] Urgent Ignite bug fix release

Igor, Let me suggest this format. - Excessive memory usage by Ignite node process (performance may drop) [requested=29251MB, available=15942MB] Please tune the following settings: [MemoryConfiguration.defaultMemoryPolicySize = suggested value] Me

Re: [DISCUSSION] Urgent Ignite bug fix release

I like the format proposed by Denis, very clear. However, I also do not understand why a user should change the size of some system cache. How would a user ever know what value to put there? This value should be configured by Ignite automatically. D. On Fri, Aug 25, 2017 at 2:24 PM, Denis Magda

Re: Shell script to stop Ignite node

Huge +1 We badly need Linux specific installation packages. Sergey, can you file a ticket? D. On Tue, Aug 22, 2017 at 12:51 AM, Sergey Kozlov wrote: > Hi > > Looks like we're trying reinvent a bicycle. > > First we have to admit that current installation procedure is very poor > ("unzip and ru

Re: [DISCUSS] Ignite Update Checker

Hey Dmitriy and all Also, since we have GA enabled for the website, we can track how many times > this page was accessed, which will be equal to the number of starts. This > way, the counter information is tracked and monitored by the Ignite PMC. Unfortunately this won't work because GA is loade

Re: [DISCUSS] Ignite Update Checker

This will surely works to get the update info to the nodes. And it sounds like a legit approach. I cannot judge on the feasibility of the GA though - don't know squat about it ;) Thanks! -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opi

Re: [DISCUSS] Ignite Update Checker

Raul, Could point about Javascript, it will not work because it executes in the browser. This means we need a server-side script, like CGI we are using on our download page. How about this approach. We create something like ignite-version.cgi script which will invoke a call to GA and then return