Re: IGNITE-3999 review

Hello, Amir. Please, see my jira comment - https://issues.apache.org/jira/browse/IGNITE-3999?focusedCommentId=16426473=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16426473 В Ср, 04/04/2018 в 20:16 -0400, Amir Akhmedov пишет: > Hi Nikolay, > > Just a gentle reminder

[jira] [Created] (IGNITE-8141) Improve OS config suggestions: SWAPPINESS

Reed Sandberg created IGNITE-8141: - Summary: Improve OS config suggestions: SWAPPINESS Key: IGNITE-8141 URL: https://issues.apache.org/jira/browse/IGNITE-8141 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-8140) Web console: "integer number too large" in generated project

Pavel Konstantinov created IGNITE-8140: -- Summary: Web console: "integer number too large" in generated project Key: IGNITE-8140 URL: https://issues.apache.org/jira/browse/IGNITE-8140 Project:

[jira] [Created] (IGNITE-8139) Need to have better control on the size of SQL on heap cache

Valentin Kulichenko created IGNITE-8139: --- Summary: Need to have better control on the size of SQL on heap cache Key: IGNITE-8139 URL: https://issues.apache.org/jira/browse/IGNITE-8139 Project:

Re: [jira] [Comment Edited] (IGNITE-6815) "Unexpected exception during cache update" via NullPointerException thrown using TouchedExpiryPolicy

Done! -- Denis On Wed, Apr 4, 2018 at 9:48 AM, Dmitry Pavlov wrote: > Hi PMCs, > > Please add Reed Sandberg > 28304fdb5984eb426fbf6c20a71c2072a3339c6a;s=Reed+Sandberg;st=author> >

Re: IGNITE-3999 review

Hi Nikolay, Just a gentle reminder :) Thanks, Amir On Fri, Mar 30, 2018 at 12:29 PM, Nikolay Izhikov wrote: > I will take a look at the next week. > > В Пт, 23/03/2018 в 09:50 +0700, Alexey Kuznetsov пишет: > > Vladimir, > > > > As SQL expert, could you review this PR? >

Re: Contribute to Apache Ignite

Welcome aboard Sergey! I've added you to the contributors' list in JIRA. -- Denis On Wed, Apr 4, 2018 at 3:59 PM, Serg Skudnov wrote: > Hello, Ignite Community. > > I want to start contribute to Apache Ignite, starting with that ticket: >

Re: Service grid redesign

I don't think peer class loading is even possible for services. I believe we should reuse DeploymentSpi [1] for versioning. [1] https://apacheignite.readme.io/docs/deployment-spi -Val On Wed, Apr 4, 2018 at 12:52 PM, Denis Magda wrote: > Sorry, that was me who renamed the

Contribute to Apache Ignite

Hello, Ignite Community. I want to start contribute to Apache Ignite, starting with that ticket: https://issues.apache.org/jira/browse/IGNITE-8138 Please, add me to the contributors list. Jira Username: coil Full Name:Sergey Skudnov Thanx.

[jira] [Created] (IGNITE-8138) Incorrect uptime in GG metrics for long running server node (1+ days)

Max Shonichev created IGNITE-8138: - Summary: Incorrect uptime in GG metrics for long running server node (1+ days) Key: IGNITE-8138 URL: https://issues.apache.org/jira/browse/IGNITE-8138 Project:

RE: Timeline for support of compute functions by thin clients

It would be nice if C# thin clients can upload C# compute functions to C# Ignite nodes, as can be done with the thick client. -Original Message- From: Sergey Kozlov [mailto:skoz...@gridgain.com] Sent: Thursday, April 5, 2018 2:14 AM To: dev@ignite.apache.org Subject: Re: Timeline for

Re: IGNITE-6879

Hi guys, According to ASF stats our spring data integration is 2 times more popular than spark integraion - 900 maven downloads vs. 400. So I would suggest us creating ignite-spring-data-2.0 module to support new deployments and leave ignite-spring-data to not break existing ones. -- Denis

Re: Data Loss while upgrading custom jar from old jar in server and client nodes

Ivan R., Alex G., persistence experts, Please have a look at this question. -- Denis On Mon, Apr 2, 2018 at 6:15 AM, Andrey Mashenkov wrote: > Crossposting to dev. > > Guys, > User use Ignite native persistence with CacheStore configured. > Seems, changing

Re: Service grid redesign

Sorry, that was me who renamed the IEP to "Oil Change in Service Grid". Was writing this email after the renaming. Like that title more because it's fun and highlights what we're intended to do - cleaning of our service grid engine and powering it up with new "liquid" (new communication and

Re: Memory usage per cache

On Wed, Apr 4, 2018 at 5:27 AM, Alexey Goncharuk wrote: > Denis, > > I think this particular metric should be deprecated. The most we can do > about it is to return the actual allocated size when a cache is the only > cache in a group and return -1 if there are

Re: Service grid redesign

Here is the correct link: https://cwiki.apache.org/confluence/display/IGNITE/IEP-17%3A+Oil+Change+in+Service+Grid I have looked at the tickets there, and I believe that we should not support peer-deployment for services. It is very hard and I do not think we should even try. I am proposing

Apache Ignite 2.5 release

Igniters, It's time to create branch for upcoming Apache Ignite 2.5 release in order to start stabilization process. If there are no any objections I'll create ignite-2.5 branch tomorrow. Also please check JIRA issues assigned to you and move it to the next version if this issues shouldn't be

[jira] [Created] (IGNITE-8137) Explain how to see SQL schema and table structure in Ignite

Denis Magda created IGNITE-8137: --- Summary: Explain how to see SQL schema and table structure in Ignite Key: IGNITE-8137 URL: https://issues.apache.org/jira/browse/IGNITE-8137 Project: Ignite

[GitHub] ignite pull request #3750: Ignite PDS 1 (Direct IO): failed test IgnitePdsCh...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3750 Ignite PDS 1 (Direct IO): failed test IgnitePdsCheckpointSimulationWithRealCpDisabledTest.testDirtyFlag() You can merge this pull request into a Git repository by running: $ git pull

Re: [jira] [Comment Edited] (IGNITE-6815) "Unexpected exception during cache update" via NullPointerException thrown using TouchedExpiryPolicy

Hi PMCs, Please add Reed Sandberg

[GitHub] ignite pull request #3726: IGNITE-6815 NPE when using expiry policy

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

[jira] [Created] (IGNITE-8136) Discovery service wrong works if node stopping by segmentation and hangs

Vladislav Pyatkov created IGNITE-8136: - Summary: Discovery service wrong works if node stopping by segmentation and hangs Key: IGNITE-8136 URL: https://issues.apache.org/jira/browse/IGNITE-8136

[GitHub] ignite pull request #3749: IGNITE-6892 OOM should be covered by failure hand...

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3749 IGNITE-6892 OOM should be covered by failure handler You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite ignite-6892

Re: [jira] [Comment Edited] (IGNITE-6815) "Unexpected exception during cache update" via NullPointerException thrown using TouchedExpiryPolicy

Hi Reed, Could you please update https://issues.apache.org/jira/browse/IGNITE-6815 status to Patch Available, so we can proceed with this contribution ? I saw second PR from you with some proposal for OS config advices. Could you please create issue corresponding to this PR and also set to

Re: Make TC issues seems to be hung up

Hi Alexey, Dmitriy thank you. It seems these 3 issues have a chance to be completed. ср, 4 апр. 2018 г. в 15:29, Alexey Goncharuk : > Replied in both tickets. > > 2018-04-04 11:52 GMT+03:00 Dmitriy Setrakyan : > > > Igniters, > > > > Dmitriy

[GitHub] ignite pull request #3577: IGNITE-7796: Adopt kNN classification example to ...

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

[GitHub] ignite pull request #3748: serialize only valuable part of GridLongList

GitHub user SharplEr opened a pull request: https://github.com/apache/ignite/pull/3748 serialize only valuable part of GridLongList For https://issues.apache.org/jira/browse/IGNITE-8054 You can merge this pull request into a Git repository by running: $ git pull

Re: IGNITE-6879

Hi Igniters, I am going to review these changes in 3-4 days. If everything is ok and if there is no objections, I will merge it. Hi Denis, are you agree with proposed change? Sincerely, Dmitriy Pavlov ср, 4 апр. 2018 г. в 14:26, Дмитрий Рябов : > I agree that

[GitHub] ignite pull request #2796: IGNITE-5504: Fluky test fixed.

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

Re: Timeline for support of compute functions by thin clients

I'm ok if it does not break the idea to restrict execution for the signed code only. On Wed, Apr 4, 2018 at 1:05 PM, Ilya Kasnacheev wrote: > Hello! > > > checksum of uploaded java code > > I argue not for Java code but for javascript/nashorn. Ruby or PHP guys > won't

[jira] [Created] (IGNITE-8135) Missing SQL-DDL Authorization

Alexey Kukushkin created IGNITE-8135: Summary: Missing SQL-DDL Authorization Key: IGNITE-8135 URL: https://issues.apache.org/jira/browse/IGNITE-8135 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #3515: IGNITE-7640: make DiscoveryDataClusterState immut...

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

[jira] [Created] (IGNITE-8134) Services can't be deployed on servers outside of baseline topology

Stanislav Lukyanov created IGNITE-8134: -- Summary: Services can't be deployed on servers outside of baseline topology Key: IGNITE-8134 URL: https://issues.apache.org/jira/browse/IGNITE-8134

Re: Service grid redesign

Vyacheslav, I've just posted my first draft of the IEP: https://cwiki.apache.org/confluence/display/IGNITE/IEP-17%3A+Service+grid+improvements It's not finished yet, but you can get the idea from it. If you have some thoughts on your mind, please let me know, I'll add them to the IEP. Denis ср,

[jira] [Created] (IGNITE-8133) Baseline topology documentation improvement

Stanislav Lukyanov created IGNITE-8133: -- Summary: Baseline topology documentation improvement Key: IGNITE-8133 URL: https://issues.apache.org/jira/browse/IGNITE-8133 Project: Ignite

Re: Make TC issues seems to be hung up

Replied in both tickets. 2018-04-04 11:52 GMT+03:00 Dmitriy Setrakyan : > Igniters, > > Dmitriy Pavlov is working very hard on making sure that we do not have > failing tests in Ignite. Let's help him in this effort. I would like to > encourage the committers responsible

Re: Memory usage per cache

Denis, I think this particular metric should be deprecated. The most we can do about it is to return the actual allocated size when a cache is the only cache in a group and return -1 if there are multiple caches in a group. However, this does not look like a consistent approach to me, so I would

[GitHub] ignite pull request #3744: Gg 13379 dev

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

[GitHub] ignite pull request #3733: ignite-8112: updated build configuration (direct-...

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

Re: IGNITE-6879

I agree that increasing complexity isn't good idea. Roman, can you document the migration guide? 2018-04-04 13:41 GMT+03:00 Alexey Kukushkin : > Roman, Dmitry, > > I also reviewed the fix and the code looks OK to me. But the fix has > significant implication - Ignite

[GitHub] ignite pull request #3747: IGNITE-5978

GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/3747 IGNITE-5978 Test fixed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/BiryukovVA/ignite IGNITE-5978 Alternatively you can review and

[GitHub] ignite pull request #3739: IGNITE-1776

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

[jira] [Created] (IGNITE-8132) A little re-design of Checkpointing section

Pavel Konstantinov created IGNITE-8132: -- Summary: A little re-design of Checkpointing section Key: IGNITE-8132 URL: https://issues.apache.org/jira/browse/IGNITE-8132 Project: Ignite

Re: IGNITE-6879

Roman, Dmitry, I also reviewed the fix and the code looks OK to me. But the fix has significant implication - Ignite no longer can be used with spring-data 1.0 due to no backward compatibility between spring 2.0 and 1.0 APIs. With this approach we must remember to add corresponding spring-data

Re: Service grid redesign

Denis, thanks for the link. I looked through the task and I think that understand your redesign point now. Do you have a clear plan or IEP for the whole redesign? I'm interested in this component and I'd like to take part in the development. On Mon, Apr 2, 2018 at 2:55 PM, Denis Mekhanikov

Re: Timeline for support of compute functions by thin clients

Hello! > checksum of uploaded java code I argue not for Java code but for javascript/nashorn. Ruby or PHP guys won't be happy about writing java, but they can easily do JS. (If we wanted Java, we could make it service grid-oriented. Which is an interesting idea btw. We can frame local

[jira] [Created] (IGNITE-8131) ZookeeperDiscoverySpiTest#testClientReconnectSessionExpire* tests fail on TC

Sergey Chugunov created IGNITE-8131: --- Summary: ZookeeperDiscoverySpiTest#testClientReconnectSessionExpire* tests fail on TC Key: IGNITE-8131 URL: https://issues.apache.org/jira/browse/IGNITE-8131

Re: Timeline for support of compute functions by thin clients

Hi We can introduce the rules to use compute tasks execution: 1. Disable by default that feature (enabling will require change a configuration property and restart cluster) 2. Disable by default code sending in the cluster (enabling will require change a configuration property and restart

[GitHub] ignite pull request #3746: ZK troubleshooting

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3746 ZK troubleshooting You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-zk-sch-troubleshooting Alternatively you can

[jira] [Created] (IGNITE-8130) WalModeChangeCoordinatorNotAffinityNodeSelfTest#testLocalCache fails sporadically in master

Alexey Goncharuk created IGNITE-8130: Summary: WalModeChangeCoordinatorNotAffinityNodeSelfTest#testLocalCache fails sporadically in master Key: IGNITE-8130 URL:

[GitHub] ignite pull request #3745: IGNITE-8122 Restore partition in state OWNING

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3745 IGNITE-8122 Restore partition in state OWNING You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8122 Alternatively

Re: abbrevation rules plugin

Both prefixes "Grid" and "Ignite" in class names are redundant for most cases. So there is no any rules for this. вт, 3 апр. 2018 г., 19:28 Vyacheslav Daradur : > Hi, Igniters! > > I got into the task [1] in agreement with Dmitry. > > I’ve prepared the PR [2] with following

Re: Make TC issues seems to be hung up

Igniters, Dmitriy Pavlov is working very hard on making sure that we do not have failing tests in Ignite. Let's help him in this effort. I would like to encourage the committers responsible for the failing tests to either fix them or remove them. Please respond here. D. On Tue, Apr 3, 2018 at

Re: IGNITE-6879

Hi! No, it wasn't a joke) 2018-04-04 11:22 GMT+03:00 Роман Меерсон : > Hi all! > I suppose Dmity`s message wasn`t april 1st joke) > So what about my PR? Would it be merged? > > вс, 1 апр. 2018 г. в 12:40, Дмитрий Рябов : > >> Dmitry, Alexey, code and

Re: Timeline for support of compute functions by thin clients

On Tue, Apr 3, 2018 at 5:48 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Dmitry, > > I just think that it's natural to have this functionality and that it would > drastically increase flexibility of thin client. Multiple requests from > users (one of them in this thread) seem

Re: IGNITE-6879

Hi all! I suppose Dmity`s message wasn`t april 1st joke) So what about my PR? Would it be merged? вс, 1 апр. 2018 г. в 12:40, Дмитрий Рябов : > Dmitry, Alexey, code and tests looks good for me. > > JIRA: https://issues.apache.org/jira/browse/IGNITE-6879 > PR:

[jira] [Created] (IGNITE-8129) JDBC: JdbcThinConnectionSSLTest.testDefaultContext

Peter Ivanov created IGNITE-8129: Summary: JDBC: JdbcThinConnectionSSLTest.testDefaultContext Key: IGNITE-8129 URL: https://issues.apache.org/jira/browse/IGNITE-8129 Project: Ignite Issue