Re: ipFinder configuration for Samples

Huge +1. We should have VM IP finder with localhost (127.0.0.1). First, there will be no network clashes, second user will see almost correct IP config right away. All he need to change for production usage is IP address. On Tue, Oct 31, 2017 at 9:58 AM, Alexey Popov wrote: > Hi, Igniters > > I

Re: New Compatibility Testing Framework module in the project

Thanks for explanation 30.10.2017, 08:43, "Dmitry Pavlov" : > Hi Aleksei, > > Wiki in apache Ignite is used for design documents, Ignite Enhancement > Proposals (IEPs), introductory for ignite developers, etc, but not for > documentation. > > Readme.io is official Ignite documentation for ignite u

Re: ipFinder configuration for Samples

+1 There's the significant slowdown for a node start under Windows if the multicast discovery used. On Tue, Oct 31, 2017 at 10:37 AM, Vladimir Ozerov wrote: > Huge +1. We should have VM IP finder with localhost (127.0.0.1). First, > there will be no network clashes, second user will see almost

[jira] [Created] (IGNITE-6798) Ignite start without WAL with no exceptions

Alexander Belyak created IGNITE-6798: Summary: Ignite start without WAL with no exceptions Key: IGNITE-6798 URL: https://issues.apache.org/jira/browse/IGNITE-6798 Project: Ignite Issue Ty

Re: ipFinder configuration for Samples

Also, maybe include in the examples reference to the recommended failureDetectionTimeout setting and a preset value of 200ms for the local Ignite (current default is 10 seconds)? It should greatly improve start-up time for the VM IP finder. On 10/31/2017 12:37 PM, Sergey Kozlov wrote: +1 Th

[jira] [Created] (IGNITE-6799) Check of starvation in striped thread pool

Vladislav Pyatkov created IGNITE-6799: - Summary: Check of starvation in striped thread pool Key: IGNITE-6799 URL: https://issues.apache.org/jira/browse/IGNITE-6799 Project: Ignite Issue T

Re: Let's keep Apache Ignite docs up-to-date

Hi Denis, Are there plans to move away from readme.io? * It is not properly versioned, which is very painful * Documentation should be in Apache git, not on some third party site Thoughts? On Mon, Oct 30, 2017 at 11:24 PM, Denis Magda wrote: > Good point. Renamed: > https://cwiki.apache.org/c

Re: Let's keep Apache Ignite docs up-to-date

+1 to git case. On Tue, Oct 31, 2017 at 12:35 PM, Pavel Tupitsyn wrote: > Hi Denis, > > Are there plans to move away from readme.io? > > * It is not properly versioned, which is very painful > * Documentation should be in Apache git, not on some third party site > > Thoughts? > > On Mon, Oct 30,

Re: ipFinder configuration for Samples

+1 to this. Should we go even further and change Ignite configuration defaults to vm ip finder? Starting a standalone node with default config never works for me, multicast stuff hangs on my network for some reason. Pavel On Tue, Oct 31, 2017 at 12:00 PM, Evgeniy Ignatiev < yevgeniy.ignat...@gma

Re: ipFinder configuration for Samples

Changing failureDetectionTimeout is bad idea, because if used in practice it will increase probability of node failures due to GC or short network glitches. We should not change it. вт, 31 окт. 2017 г. в 12:54, Pavel Tupitsyn : > +1 to this. > > Should we go even further and change Ignite configu

Re: Ignite 2.0.0 GridUnsafe unmonitor

I agree with Denis, if we don't have such warning we should continiously warn users in wiki pages/blogs/presentations. It is simpler to warn from code. What do you think if we will issue warning only if size > 1. HashMap with 1 item will not cause deadlock. Moreover where can be some custom single

Re: [IGNITE-5717] improvements of MemoryPolicy default size

Hi Igniters, Up this discussion: there is still some thing to do in context of 32 bit VMs, see issue https://issues.apache.org/jira/browse/IGNITE-5618 Denis M. suggested solution for this: let's make the default size calculation more sophisticated. If Ignite is running in a 32 process and 20% of

[GitHub] ignite pull request #2924: IGNITE-6357: Added support of multiple SQL statem...

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

Re: ipFinder configuration for Samples

If having reduced timeout in example seems like a bad idea - then maybe just add it with a safe value of 10s and a comment with a reference to the documentation of tuning it - https://apacheignite.readme.io/docs/cluster-config#failure-detection-timeout ? From my experience people tend to judg

[GitHub] ignite pull request #2923: IGNITE-6690 DiscoverySpi: Clientmode Ignite shoul...

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

Re: not able to connect Ignite shell.

Hello! Are you sure you are running it in binary release folder and not in source release? You will have to build source release first. -- Ilya Kasnacheev 2017-10-24 9:44 GMT+03:00 DEVASISH PANDA : > Hi Guys, > > I am getting following error while connecting to ignite shell. > > [devasish@oc

[GitHub] ignite pull request #2925: IGNITE-6511: Fixed SQLGetDiagRec behaviour in ODB...

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

[GitHub] ignite pull request #2949: IGNITE-6765: Added ODBC test for closing cursor a...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2949 IGNITE-6765: Added ODBC test for closing cursor after DML execution You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite igni

[GitHub] ignite pull request #2950: Ignite-gg-13021: NPE on node stop when SSL is use...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2950 Ignite-gg-13021: NPE on node stop when SSL is used. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13021

[GitHub] ignite pull request #2950: Ignite-gg-13021: NPE on node stop when SSL is use...

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

[GitHub] ignite pull request #2951: Ignite-gg13021: NPE on node stop when SSL is used...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2951 Ignite-gg13021: NPE on node stop when SSL is used. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13021 A

[jira] [Created] (IGNITE-6800) С++: Continuous Query example:extra lines in log if run example with 3 standalone node

Irina Zaporozhtseva created IGNITE-6800: --- Summary: С++: Continuous Query example:extra lines in log if run example with 3 standalone node Key: IGNITE-6800 URL: https://issues.apache.org/jira/browse/IGNITE-68

[RESULT] [VOTE] Apache Ignite 2.3.0 Release (RC2)

Igniters, Apache Ignite 2.3.0 release (RC2) has been accepted. 6 "+1" binding votes received: - Alexey Kuznetsov - Anton Vinogradov - Denis Magda - Nikolai Tikhonov - Pavel Tupitsyn - Valentin Kulichenko Vote thread: *http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-3

[GitHub] ignite pull request #2952: fix for IGNITE-5795

GitHub user kukushal opened a pull request: https://github.com/apache/ignite/pull/2952 fix for IGNITE-5795 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5795-master Alternatively you can review an

Re: IGNITE-6252 patch

Hello, Thank you for your contribution! I've reviewed your changes and left comment to ticket. Could you look jira https://issues.apache.org/ jira/browse/IGNITE-6252? On Mon, Oct 30, 2017 at 10:57 AM, Sunny Chan, CLSA wrote: > Hello, > > During our testing we have found an issue and I have rais

[GitHub] ignite pull request #2953: IGNITE-6640: Introduction of models import/export

GitHub user ybabak opened a pull request: https://github.com/apache/ignite/pull/2953 IGNITE-6640: Introduction of models import/export You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6640 Alternativ

Re: [IGNITE-5717] improvements of MemoryPolicy default size

I'm ok with using 1GB only on a 32-bit system. Note, though, that there is no reliable way to detect this, so this will be a best-effort change. 2017-10-31 14:07 GMT+03:00 Dmitry Pavlov : > Hi Igniters, > > Up this discussion: there is still some thing to do in context of 32 bit > VMs, see issue

[jira] [Created] (IGNITE-6801) Ignite Kafka Connector certification with Confluent

Alexey Kukushkin created IGNITE-6801: Summary: Ignite Kafka Connector certification with Confluent Key: IGNITE-6801 URL: https://issues.apache.org/jira/browse/IGNITE-6801 Project: Ignite

Re: Let's keep Apache Ignite docs up-to-date

Hi Pavel, The lack of smooth versioning between pages on readme.io is redeemed with an easy to use editor. A doc writer don’t need to grasp any markup language, commit changes to some remote repo and check up final results. All the writer needs to do is to open a page and up

[GitHub] ignite pull request #2954: For testing.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2954 For testing. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13005 Alternatively you can review and apply th

Re: Let's keep Apache Ignite docs up-to-date

> easy to use editor Honestly, it sucks. I want to use my IDE and git instead of slow and buggy browser-based bs. > commit changes This is a good thing. I want to commit changes, see history, do other VCS stuff. > Github is also a third-party site I don't suggest github. We store code in Apache g

Re: Let's keep Apache Ignite docs up-to-date

Simplified: Current flow is over-complicated for me as developer, I see a lot of problems and have no clue how to fix them using readme.io or wiki. But I know how to fix them using git. I'm good at git, let me write documentation in way I'm good in :) On Tue, Oct 31, 2017 at 7:29 PM, Pavel Tupits

[jira] [Created] (IGNITE-6802) NullPointerException when WAL store and WAL archive paths are same

Alexey Kukushkin created IGNITE-6802: Summary: NullPointerException when WAL store and WAL archive paths are same Key: IGNITE-6802 URL: https://issues.apache.org/jira/browse/IGNITE-6802 Project:

[jira] [Created] (IGNITE-6803) UriDeploymentSpi affects execution of other tasks, including Ignite internals

Ilya Kasnacheev created IGNITE-6803: --- Summary: UriDeploymentSpi affects execution of other tasks, including Ignite internals Key: IGNITE-6803 URL: https://issues.apache.org/jira/browse/IGNITE-6803 P

[GitHub] ignite pull request #2955: IGNITE-6803 Inverse classloader widening conditio...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/2955 IGNITE-6803 Inverse classloader widening condition to fix UriDeploymentSpi. You can merge this pull request into a Git repository by running: $ git pull https://github.com/alamar/ignite ignite

Generate release notes for Apache Ignite 2.3.0

Hi Mauricio, Could you please generate release notes for AI 2.3.0 and publish them on the site? Vladimir.

[jira] [Created] (IGNITE-6804) Print a warning if HashMap is passed into bulk update operations

Denis Magda created IGNITE-6804: --- Summary: Print a warning if HashMap is passed into bulk update operations Key: IGNITE-6804 URL: https://issues.apache.org/jira/browse/IGNITE-6804 Project: Ignite

Re: Ignite 2.0.0 GridUnsafe unmonitor

Here is a ticket for the improvement: https://issues.apache.org/jira/browse/IGNITE-6804 — Denis > On Oct 31, 2017, at 3:55 AM, Dmitry Pavlov wrote: > > I agree with Denis, if we don't have such warning we should continiously warn > users in wiki pages/blogs/presentations. It is simpler to warn

Re: Generate release notes for Apache Ignite 2.3.0

Hi, Attached you can find the patch that updates the default docs to v2.3. Please merge it into the repo and let me know if you have any question. Best, Mauricio docupdate-release-2.3.0.patch.bz2 Description: BZip2 compressed data > On Oct 31, 2017, at 14:23, Vladimir Ozerov wrote: > >

[jira] [Created] (IGNITE-6805) Tests are red for another MAX_BLOCK_SIZE value (4 or 8 instead 32)

Aleksey Zinoviev created IGNITE-6805: Summary: Tests are red for another MAX_BLOCK_SIZE value (4 or 8 instead 32) Key: IGNITE-6805 URL: https://issues.apache.org/jira/browse/IGNITE-6805 Project: I

Re: Let's keep Apache Ignite docs up-to-date

Pavel, Could you show me any example of such a documentation where docs are stored in git and can be visualized by GitHub (dev stage) and 3rd party engine (release on the site)? In my understanding if take your approach then the community needs to develop a visualization engine for ignite.apa

Re: Ignite 2.0.0 GridUnsafe unmonitor

Guys, Printing a warning in this case is really strange idea. First, how would explain it in case of OPTIMISTIC/SERIALIZABLE transactions where deadlocks are impossible? Second, what would you do in case tow sorted maps are passed one by one in a transaction? User still may have a deadlock. :Last,

Re: Let's keep Apache Ignite docs up-to-date

Anton, The life is not about coding only :) Sometimes we need to learn new tools to produce nice looking, well organized and professional content. Take Photopshop or Mac Keynote for instance that help us out with diagrams and presentations creation. Readme.io does it job we

Re: Ignite 2.0.0 GridUnsafe unmonitor

Vladimir, That’s an oversight and lack of explanation on our side. The goal is to avoid unexpected deadlocks when a user passed a HashMap in cache.putAll. Before printing out a warning we can filter out OPTIMISTIC/SERIALIZABLE and other suitable scenarios. So you’re free to offer another solut

Re: Generate release notes for Apache Ignite 2.3.0

Thanks Mauricio! Merged the changes. — Denis > On Oct 31, 2017, at 10:41 AM, Mauricio Stekl wrote: > > Hi, > Attached you can find the patch that updates the default docs to v2.3. > > Please merge it into the repo and let me know if you have any question. > > Best, > Mauricio > > > > >

[jira] [Created] (IGNITE-6806) Document logs forwarding to ELK stack

Denis Magda created IGNITE-6806: --- Summary: Document logs forwarding to ELK stack Key: IGNITE-6806 URL: https://issues.apache.org/jira/browse/IGNITE-6806 Project: Ignite Issue Type: Task S

Re: [DISCUSS] Ignite Update Checker

Looks like we are getting somewhere with this. Please check [1] for the latest comment from the Infra team. I guess we can start with asking for a server-side redirect to GA as the immediate step. And explore it further possibilities as per Greg's recommendations. [1] https://is.gd/CL88O6 -- Wi

Re: [RESULT] [VOTE] Apache Ignite 2.3.0 Release (RC2)

The readme.io docs including the new SQL domain went to live: https://apacheignite-sql.readme.io/docs I’ll craft a public announcement in the nearest days. — Denis > On Oct 31, 2017, at 7:19 AM, Vladimir Ozerov wrote: > > Igniters, > > Apache Ignite 2.3.0 release (RC2) has been accepted. > >

Re: Generate release notes for Apache Ignite 2.3.0

Vladimir, The release notes are still missing: https://ignite.apache.org/releases/2.3.0/release_notes.html Usually the notes were generated by script contributed by Alexey Chetaev. It was planned to accept it to the Ignite codebase. Not sure it happened. *Alexey*, *Sergey K.*, could you help wi

Re: Ignite 2.0.0 GridUnsafe unmonitor

Vladimir, thank you. Good point for optimistic tx, but still putAll usage require using sorted collections. User, of course, may broke this scenario also by using sorted maps with incorrect custom comparators (one asc, one desc). Producing warning in code for Igntie for potential deadlock is good u

Re: [DISCUSS] Ignite Update Checker

Cos, thanks for helping out! By redirect, do you mean changing the .htaccess file to point a certain URL containing Ignite version to a GA URL? In that case, do you know if it will be possible to still send the latest Ignite version back as a response? D. On Tue, Oct 31, 2017 at 11:30 AM, Konstan

Re: [DISCUSS] Ignite Update Checker

Yes, that what I meant. It might not work per website (depends on how the server is configured), but server-wide redirects could be arranged. Also, there's a new discussion on the topic going on legal-discuss@ right now [1] [1] https://is.gd/RPaWQt -- With regards, Konstantin (Cos) Boudnik On

Re: Ignite 2.0.0 GridUnsafe unmonitor

I like the idea to print out a warning if unsorted map is provided. The fact that there are tons of other ways to get a deadlock doesn't mean that we should ignore this case which is actually very common. -Val On Tue, Oct 31, 2017 at 12:34 PM, Dmitry Pavlov wrote: > Vladimir, thank you. Good po

[jira] [Created] (IGNITE-6807) NPE is thrown if local query is executed on client

Valentin Kulichenko created IGNITE-6807: --- Summary: NPE is thrown if local query is executed on client Key: IGNITE-6807 URL: https://issues.apache.org/jira/browse/IGNITE-6807 Project: Ignite

Re: [RESULT] [VOTE] Apache Ignite 2.3.0 Release (RC2)

Great job on release! Is there a link to the release notes? The release notes link on the website is broken: https://ignite.apache.org/download.cgi D. On Tue, Oct 31, 2017 at 12:12 PM, Denis Magda wrote: > The readme.io docs including the new SQL domain went to live: > https://apacheignite-sql

Re: Let's keep Apache Ignite docs up-to-date

The main value of readme is that I can edit a document and it is visible to the whole world once I click a save button, without any git commands or builds. If anyone in the community can suggest a tool that will work the same way with Apache git repository directly, please send it here. D. On Tue

RE: IGNITE-6252 patch

I have reviewed and it looks good. From: Nikolai Tikhonov [mailto:ntikho...@apache.org] Sent: Tuesday, October 31, 2017 11:50 PM To: dev@ignite.apache.org; Sunny Chan, CLSA Subject: Re: IGNITE-6252 patch Hello, Thank you for your contribution! I've reviewed your changes and left comment to tick

Re: Let's keep Apache Ignite docs up-to-date

I would also consider having docs under separate git repository. Separate since we need to have an opportunity to revisit documentation for already released versions. --Yakov

Re: Ignite 2.0.0 GridUnsafe unmonitor

+1 for warning about potential deadlock and improving javadocs --Yakov

Re: Let's keep Apache Ignite docs up-to-date

On Tue, Oct 31, 2017 at 8:15 PM, Yakov Zhdanov wrote: > I would also consider having docs under separate git repository. Separate > since we need to have an opportunity to revisit documentation for already > released versions. > This should not be a problem.

Re: [RESULT] [VOTE] Apache Ignite 2.3.0 Release (RC2)

> Is there a link to the release notes? The release notes link on the website > is broken: > https://ignite.apache.org/download.cgi > That is being discussed here: http://apache-ignite-developers.2346864.n4.nabble.com/Generate-release-notes-for-Apache-Igni

Please add as contributor for web-console

Hello, Ingite community! My name is Alex. I would like to contribute to your great project Apache Ignite. I am a web developer, would like to improve Ignite web-console. My account in JIRA is "alexdel". Please grant me with contributor access. Regards! Alexander Kalinin

Re: Please add as contributor for web-console

Hi! Please read: https://ignite.apache.org/community/contribute.html#contribute I granted contributor rights in Ignite JIRA. Looking forward for your contribution. On Wed, Nov 1, 2017 at 11:44 AM, Калинин Александр wrote: > Hello, Ingite community! > > My name is Alex. I would like to contri