Re: Cluster auto activation design proposal

How about this: > *interface ClusterActivator {* > *boolean activate(Collection nodes);**}* Out of the box, we can provide this implementation of the activation filter: > > *ClusterInitialActiveSet implements ClusterActivator { * > *InigeInitialActiveSet(String... addresses);**}*

Re: IgniteFuture -> CompletableFuture

>>Vova, I am not sure I understand. How will it be released? This can be a module containing only java8 related stuff including method that converts IgniteFuture to completable future. And it should be built with java8. --Yakov

[GitHub] ignite pull request #2578: IGNITE-6014 Transaction records in WAL.

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/2578 IGNITE-6014 Transaction records in WAL. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6014 Alternatively you

[GitHub] ignite pull request #2579: Ignite 6014 on 2.1.4 branch

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/2579 Ignite 6014 on 2.1.4 branch You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6014-2.1.4 Alternatively you can

[GitHub] ignite pull request #2577: IGNITE-5999 : Fixed calculation of moving partiti...

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2577 IGNITE-5999 : Fixed calculation of moving partitions count. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: IgniteFuture -> CompletableFuture

Exactly. On Fri, Sep 1, 2017 at 2:51 PM, Yakov Zhdanov wrote: > >>Vova, I am not sure I understand. How will it be released? > > This can be a module containing only java8 related stuff including method > that converts IgniteFuture to completable future. And it should be

[GitHub] ignite pull request #2464: IGNITE-5849 metastorage

Github user kdudkov closed the pull request at: https://github.com/apache/ignite/pull/2464 --- 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

[GitHub] ignite pull request #1893: Ignite-3054 nio connections

Github user kdudkov closed the pull request at: https://github.com/apache/ignite/pull/1893 --- 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

Re: Hopeless looping in TcpCommunicationSpi

Ilya, I reviewed your test and I now see the point. Is the same possible with server-server? Or failure process will be initiated for remote node by local one? Will the following work for client? If connection fails then client takes a pause for 1 sec with Thread.sleep() and takes another

[jira] [Created] (IGNITE-6245) ODBC: update query should return affected rows number for non-batch queries as well.

Andrew Mashenkov created IGNITE-6245: Summary: ODBC: update query should return affected rows number for non-batch queries as well. Key: IGNITE-6245 URL: https://issues.apache.org/jira/browse/IGNITE-6245

[GitHub] ignite pull request #2581: IGNITE-6188: ODBC: Fix for SQLFreeStmt(SQL_CLOSE)...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2581 IGNITE-6188: ODBC: Fix for SQLFreeStmt(SQL_CLOSE). You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6188

Re: Ignite Durable Memory & Persistent Store introduction for developers

Dmitriy, First of all, thanks for putting this low level details on paper! Current and future community members will be grateful to you. Second, let me be a reviewer of the page and suggest some improvements. Until the review is over I would encourage us to hold on with any public

Re: How to configure ignite-jcl and Ignite-slf4j logger

Hi Denis, JCL it's wrapper for logging system (similar sl4j) which can be used together with log4j. I guess that JavaDoc correct. On Fri, Sep 1, 2017 at 5:40 PM, Denis Magda wrote: > Nikolai, > > Looking at JCL documentation I see the usage of Log4j together with JCL: > > *

[GitHub] ignite pull request #2580: IGNITE-6236 .NET: Thin client: cache.Get and Put ...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2580 IGNITE-6236 .NET: Thin client: cache.Get and Put for user types You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Hopeless looping in TcpCommunicationSpi

Yes, the same problem is possible with server-server communication. I've amended my pull request to include a test for that. There are already Thread.sleeps() in this look so I propose to add a countdown to maxConnectionAttempts instead of while(true) Ideally we should find a way to log last

Re: How to configure ignite-jcl and Ignite-slf4j logger

Nikolai, Looking at JCL documentation I see the usage of Log4j together with JCL: * * ... * property name="gridLogger" * bean class="org.apache.ignite.logger.jcl.JclLogger" * constructor-arg type="org.apache.commons.logging.Log" * bean

[jira] [Created] (IGNITE-6244) .NET: Thin client: ScanQuery

Pavel Tupitsyn created IGNITE-6244: -- Summary: .NET: Thin client: ScanQuery Key: IGNITE-6244 URL: https://issues.apache.org/jira/browse/IGNITE-6244 Project: Ignite Issue Type: Improvement

[GitHub] ignite pull request #2298: IGNITE-5750 Change HMSM format to hh:mm:ss.mmm

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2298 --- 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

Re: How to configure ignite-jcl and Ignite-slf4j logger

Nikolai, I have specified 'gridlogger' property in 'IgniteConfiguration', but looks like it does not get instantiated. ... On Fri, Sep 1, 2017 at 10:16 AM, Nikolay

Re: Ignite Durable Memory & Persistent Store introduction for developers

Hi Denis, Sure, I would be glad if you have some time to review the page. Thank you for edits and careful review! According to recent questions and feedback from Igniters, I would also like to extend section about memory organization. Please give me a couple of days to address your questions

[jira] [Created] (IGNITE-6246) Document Durable Memory and Linux Kernel Tuning Parameters

Denis Magda created IGNITE-6246: --- Summary: Document Durable Memory and Linux Kernel Tuning Parameters Key: IGNITE-6246 URL: https://issues.apache.org/jira/browse/IGNITE-6246 Project: Ignite

Durable Memory and Ignite Persistence Tuning

Igniters, I see a lot of complains regarding the performance of the subj on the user list. At the same time, I do believe that in most scenarios it’s a lack of knowledge that we keep in secret. It's time to document Durable Memory and its Native Persistence tuning parameters. Let's start

[jira] [Created] (IGNITE-6247) Review Ignite & Cassandra Integration Documentation

Denis Magda created IGNITE-6247: --- Summary: Review Ignite & Cassandra Integration Documentation Key: IGNITE-6247 URL: https://issues.apache.org/jira/browse/IGNITE-6247 Project: Ignite Issue

[GitHub] ignite pull request #2582: IGNITE-6133

GitHub user vk23 opened a pull request: https://github.com/apache/ignite/pull/2582 IGNITE-6133 Added clearNodeLocalMap() method for IgniteMXBean. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vk23/ignite master Alternatively

Re: Durable Memory and Ignite Persistence Tuning

200% agree. UX is major problem for Ignite (especially so for 2.0 with all major redev). Removing (!) configuration properties should be THE GOAL, not adding new one or documenting them (which is a crutch to begin with). When I see a product with dozens config properties or more I desperately

Re: Durable Memory and Ignite Persistence Tuning

Just to spice it up: in my experience, having a few hundred parameters one can tweak (I am making up the number here) is a tough UX call. In JVM, we had a team that worked on heuristics that would auto-tune a bunch of things during the VM startup. Hence, providing the best user experience in most

Re: Durable Memory and Ignite Persistence Tuning

It doesn’t matter how many configuration parameters your platform, database or operating system has - the performance tuning usually takes place in business deployments. The performance optimizations might happen behind the scene by heuristic algorithms or basic checks or be explained in

Re: Durable Memory and Ignite Persistence Tuning

My points was in support of auto-tune for Ignite's internals. As far as environment, sure, we need to have a doc. -- Nikita Ivanov On Fri, Sep 1, 2017 at 1:23 PM, Denis Magda wrote: > It doesn’t matter how many configuration parameters your platform, > database or operating

Re: How to configure ignite-jcl and Ignite-slf4j logger

Yes, I tried using it, but strangely this is the output I get when use -DIGNITE_QUIET=false ( I set this property in Idea ->Run -> Edit Configurations -> VM options) log4j:WARN No appenders could be found for logger (org.apache.ignite.internal.util.typedef.G). log4j:WARN Please initialize the

Re: How to configure ignite-jcl and Ignite-slf4j logger

Prachi, It looks like you're running in quiet mode. Did you try to set -DIGNITE_QUIET=false system property? -Val On Fri, Sep 1, 2017 at 10:43 AM, Prachi Garg wrote: > Nikolai, > > I have specified 'gridlogger' property in 'IgniteConfiguration', but looks > like it does

Re: Durable Memory and Ignite Persistence Tuning

Cos, great point! I think the Ignite community should start load testing with default settings, without any config changes. This should open a lot of holes. ⁣D.​ On Sep 1, 2017, 9:57 PM, at 9:57 PM, Konstantin Boudnik wrote: >Just to spice it up: in my experience, having a

Re: Durable Memory and Ignite Persistence Tuning

Cos, Sure, as I see from the @dev list a lot of efforts are put to the auto-tune way. We need to keep to this way whenever it’s possible. However, it might be the case that we can’t auto-tune some parameters (Linux kernel behavior) or we know that setting A will be auto-tuned in release 2.x

[GitHub] ignite pull request #2570: IGNITE-6233 .NET: Extract type codes to a separat...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2570 --- 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

Re: IgniteFuture -> CompletableFuture

Agree. Vladimir's suggestions should work. We cannot drop Java7 now. --Yakov

Re: Hopeless looping in TcpCommunicationSpi

Ilya, can you please provide more details? Is this client or server failing to connect? --Yakov

Re: How to configure ignite-jcl and Ignite-slf4j logger

Hello Prachi! You need to set gridLogger property in IgniteConfiguration and remove ignite-log4j dependency from POM file. For example for Sl4j logger: *igniteConfiguration.setGridLogger(new Slf4jLogger());* and for Jc logger: *igniteConfiguration.setGridLogger(new JclLogger());* On Fri, Sep

[GitHub] ignite pull request #2575: IGNITE-6071 Finite number of attempts in reserveC...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/2575 IGNITE-6071 Finite number of attempts in reserveClient() You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6071

Re: Hopeless looping in TcpCommunicationSpi

Hello Yakov, This is client repeatedly failing (for some spurious reason) after it connects to socket in createTcpClient() It would then return null and reserveClient() will retry. Forever. I've prepared a sample pull request to reproduce and remedy the problem:

Re: IgniteFuture -> CompletableFuture

On Thu, Aug 31, 2017 at 3:39 PM, Vladimir Ozerov wrote: > There is no need to migrate to Java 8 to support CompletableFuture. Create > separate Maven project and compile it with Java 8 - this is it. > Vova, I am not sure I understand. How will it be released? > > On Thu,

Re: IgniteFuture -> CompletableFuture

We can build project using java 8 partially for java 7 and partially for java 8 (target bytecode version). I guess for end user it will be something like 2 artifacts to be dependent from - group: 'org.apache.ignite', name: 'ignite-core', version: '2.3' - group: 'org.apache.ignite', name:

Re: Cluster auto activation design proposal

Dmitriy, The idea is interesting however I cannot come up with a clear use case which can be widely adopted. I would give users a simple API at first to cover 80% of their needs and then collect some feedback and start thinking about adding new functionality. Makes sense? Sergey. On Thu, Aug

[jira] [Created] (IGNITE-6243) RazorSQL crashed on try edit, describe and another actions with table.

Aleksey Chetaev created IGNITE-6243: --- Summary: RazorSQL crashed on try edit, describe and another actions with table. Key: IGNITE-6243 URL: https://issues.apache.org/jira/browse/IGNITE-6243

Re: [DISCUSSION] Urgent Ignite bug fix release

Hi, Reasonable question, but I propose to keep 2.2 as a release version for this urgent release, since we never released X.Y.Z version before. Let's discuss this at separate thread. Could you please start it? On Fri, Sep 1, 2017 at 4:49 AM, 李玉珏@163 <18624049...@163.com> wrote: > Since it's an

Re: IGNITE-2779 BinaryMarshaller caches must be cleaned during client reconnect.

Hi, Igniters. I have done issue 2779 - BinaryMarshaller caches must be cleaned during client reconnect.[1] Could you, please, review? Solution: We stop server nodes and keep alive the client. Then we take a new instance of the cache and client node throws an exception in

Re: [DISCUSSION] Urgent Ignite bug fix release

Hi, at least for this release I suggest to keep versioning as is and use 2.2 Without solved issue with http://apache-ignite-developers.2346864.n4.nabble.com/usage-analytics-td19504.html Ignite will not remind users about latest available ignite version. Versioning structure change will confuse

[GitHub] ignite pull request #2576: IGNITE-5849 refactor DataPageIO & FreeList, intro...

GitHub user kdudkov opened a pull request: https://github.com/apache/ignite/pull/2576 IGNITE-5849 refactor DataPageIO & FreeList, introduce MetaStorage You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite