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: > > * > * ... > *

[jira] [Created] (IGNITE-5848) Ignite should support Hibernate 5.2.X

Nikolay Tikhonov created IGNITE-5848: Summary: Ignite should support Hibernate 5.2.X Key: IGNITE-5848 URL: https://issues.apache.org/jira/browse/IGNITE-5848 Project: Ignite Issue Type

[jira] [Created] (IGNITE-5489) Possible connection leaks when loadPreviousValue set to true

Nikolay Tikhonov created IGNITE-5489: Summary: Possible connection leaks when loadPreviousValue set to true Key: IGNITE-5489 URL: https://issues.apache.org/jira/browse/IGNITE-5489 Project: Ignite

[jira] [Created] (IGNITE-5290) Events might be missed during concurrent CQ registration and cache operations

Nikolay Tikhonov created IGNITE-5290: Summary: Events might be missed during concurrent CQ registration and cache operations Key: IGNITE-5290 URL: https://issues.apache.org/jira/browse/IGNITE-5290

[jira] [Created] (IGNITE-5214) ConcurrentModificationException with enable DEBUG log level

Nikolay Tikhonov created IGNITE-5214: Summary: ConcurrentModificationException with enable DEBUG log level Key: IGNITE-5214 URL: https://issues.apache.org/jira/browse/IGNITE-5214 Project: Ignite

[jira] [Created] (IGNITE-4939) Receive event before cache initialized

Nikolay Tikhonov created IGNITE-4939: Summary: Receive event before cache initialized Key: IGNITE-4939 URL: https://issues.apache.org/jira/browse/IGNITE-4939 Project: Ignite Issue Type

[jira] [Created] (IGNITE-4901) Decrease logging level for DataStremer retry

Nikolay Tikhonov created IGNITE-4901: Summary: Decrease logging level for DataStremer retry Key: IGNITE-4901 URL: https://issues.apache.org/jira/browse/IGNITE-4901 Project: Ignite Issue

[jira] [Created] (IGNITE-4590) Lock/unlock operations are hanging when topology changed

Nikolay Tikhonov created IGNITE-4590: Summary: Lock/unlock operations are hanging when topology changed Key: IGNITE-4590 URL: https://issues.apache.org/jira/browse/IGNITE-4590 Project: Ignite

[jira] [Created] (IGNITE-4589) Possible starvation during rebalancing for marshaller cache

Nikolay Tikhonov created IGNITE-4589: Summary: Possible starvation during rebalancing for marshaller cache Key: IGNITE-4589 URL: https://issues.apache.org/jira/browse/IGNITE-4589 Project: Ignite

[jira] [Created] (IGNITE-4344) Client node allocates off heap memories for caches

Nikolay Tikhonov created IGNITE-4344: Summary: Client node allocates off heap memories for caches Key: IGNITE-4344 URL: https://issues.apache.org/jira/browse/IGNITE-4344 Project: Ignite

[jira] [Created] (IGNITE-4324) ScanQuery throws incomprehensible exception when topology does not contain data nodes

Nikolay Tikhonov created IGNITE-4324: Summary: ScanQuery throws incomprehensible exception when topology does not contain data nodes Key: IGNITE-4324 URL: https://issues.apache.org/jira/browse/IGNITE-4324

[jira] [Created] (IGNITE-4052) Add ability to set up users for MESOS

Nikolay Tikhonov created IGNITE-4052: Summary: Add ability to set up users for MESOS Key: IGNITE-4052 URL: https://issues.apache.org/jira/browse/IGNITE-4052 Project: Ignite Issue Type

[jira] [Created] (IGNITE-4047) CQ skips events if autoUnsubscribe flag was set to false

Nikolay Tikhonov created IGNITE-4047: Summary: CQ skips events if autoUnsubscribe flag was set to false Key: IGNITE-4047 URL: https://issues.apache.org/jira/browse/IGNITE-4047 Project: Ignite

[jira] [Created] (IGNITE-4014) Transaction hangs if entry processor failed during serialization

Nikolay Tikhonov created IGNITE-4014: Summary: Transaction hangs if entry processor failed during serialization Key: IGNITE-4014 URL: https://issues.apache.org/jira/browse/IGNITE-4014 Project

[jira] [Created] (IGNITE-3907) Incorrect initialization CQ when node filter configured for cache

Nikolay Tikhonov created IGNITE-3907: Summary: Incorrect initialization CQ when node filter configured for cache Key: IGNITE-3907 URL: https://issues.apache.org/jira/browse/IGNITE-3907 Project

[jira] [Created] (IGNITE-3878) Add isPrimary() and isBackup() methods on CacheQUeryEntryEvent

Nikolay Tikhonov created IGNITE-3878: Summary: Add isPrimary() and isBackup() methods on CacheQUeryEntryEvent Key: IGNITE-3878 URL: https://issues.apache.org/jira/browse/IGNITE-3878 Project

[jira] [Created] (IGNITE-3867) ScanQuery ignore pageSize propertry

Nikolay Tikhonov created IGNITE-3867: Summary: ScanQuery ignore pageSize propertry Key: IGNITE-3867 URL: https://issues.apache.org/jira/browse/IGNITE-3867 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-3850) Need to add support WIN for YARN integration

Nikolay Tikhonov created IGNITE-3850: Summary: Need to add support WIN for YARN integration Key: IGNITE-3850 URL: https://issues.apache.org/jira/browse/IGNITE-3850 Project: Ignite Issue

[jira] [Created] (IGNITE-3653) P2P doesn't work for remote filter and filter factory.

Nikolay Tikhonov created IGNITE-3653: Summary: P2P doesn't work for remote filter and filter factory. Key: IGNITE-3653 URL: https://issues.apache.org/jira/browse/IGNITE-3653 Project: I

[jira] [Created] (IGNITE-3454) Used Thread.getContextClassLoader() classloader for P2P

Nikolay Tikhonov created IGNITE-3454: Summary: Used Thread.getContextClassLoader() classloader for P2P Key: IGNITE-3454 URL: https://issues.apache.org/jira/browse/IGNITE-3454 Project: Ignite

[jira] [Created] (IGNITE-3433) Uninformative error message for affinity function

Nikolay Tikhonov created IGNITE-3433: Summary: Uninformative error message for affinity function Key: IGNITE-3433 URL: https://issues.apache.org/jira/browse/IGNITE-3433 Project: Ignite

[jira] [Created] (IGNITE-3421) Add ability to configure maxIterCnt property in GridCacheQueryManager

Nikolay Tikhonov created IGNITE-3421: Summary: Add ability to configure maxIterCnt property in GridCacheQueryManager Key: IGNITE-3421 URL: https://issues.apache.org/jira/browse/IGNITE-3421

Re: Docker image for Ignite 1.6.0 release pull request

Hi Aliaksandr! I've reviewed and merge your changes to master. Thank you for your contribution! On Tue, Jun 7, 2016 at 5:31 PM, Denis Magda wrote: > Nikolay, > > As a maintainer of this component please do the review. > > — > Denis > > > On Jun 5, 2016, at 3:18 PM, zshamrock > wrote: > > > >

[jira] [Created] (IGNITE-3272) Memory consumption in ContinuousQueryHandler

Nikolay Tikhonov created IGNITE-3272: Summary: Memory consumption in ContinuousQueryHandler Key: IGNITE-3272 URL: https://issues.apache.org/jira/browse/IGNITE-3272 Project: Ignite Issue

[jira] [Created] (IGNITE-3268) Integration with YARN in net without internet

Nikolay Tikhonov created IGNITE-3268: Summary: Integration with YARN in net without internet Key: IGNITE-3268 URL: https://issues.apache.org/jira/browse/IGNITE-3268 Project: Ignite Issue

[jira] [Created] (IGNITE-3214) YARN allocates containers at random

Nikolay Tikhonov created IGNITE-3214: Summary: YARN allocates containers at random Key: IGNITE-3214 URL: https://issues.apache.org/jira/browse/IGNITE-3214 Project: Ignite Issue Type

[jira] [Created] (IGNITE-3188) Binary marshaller doesn't unmarshal a void type

Nikolay Tikhonov created IGNITE-3188: Summary: Binary marshaller doesn't unmarshal a void type Key: IGNITE-3188 URL: https://issues.apache.org/jira/browse/IGNITE-3188 Project: I

[jira] [Created] (IGNITE-3183) ScanQuery and localEntries are ignored keepBinary flag in OFFHEAP_TIERED mode

Nikolay Tikhonov created IGNITE-3183: Summary: ScanQuery and localEntries are ignored keepBinary flag in OFFHEAP_TIERED mode Key: IGNITE-3183 URL: https://issues.apache.org/jira/browse/IGNITE-3183

Re: [VOTE] Apache Ignite 1.6.0 RC1

+1 (binding) On Fri, May 20, 2016 at 10:38 AM, Anton Vinogradov wrote: > +1 (binding) > > On Fri, May 20, 2016 at 12:16 AM, Vladimir Ozerov > wrote: > > > Looks good to me. > > > > +1 (binding) > > > > On Thu, May 19, 2016 at 10:11 PM, Denis Magda > wrote: > > > > > +1 > > > > > > > On Wed, Ma

[jira] [Created] (IGNITE-3168) Ignite mesos framework should provide ability to configure timeouts.

Nikolay Tikhonov created IGNITE-3168: Summary: Ignite mesos framework should provide ability to configure timeouts. Key: IGNITE-3168 URL: https://issues.apache.org/jira/browse/IGNITE-3168 Project

[jira] [Created] (IGNITE-3083) Shmem loader failed with OverlappingFileLockException

Nikolay Tikhonov created IGNITE-3083: Summary: Shmem loader failed with OverlappingFileLockException Key: IGNITE-3083 URL: https://issues.apache.org/jira/browse/IGNITE-3083 Project: Ignite

Re: API for asynchronous execution.

akyan wrote: > Instead of the Async annotation, why not just have a setter > “setAsyncFilter(true)”? > > D. > > On Fri, Apr 15, 2016 at 4:33 AM, Nikolay Tikhonov > wrote: > > > Yakov is right. Benchmarks show performance drop 3-8% when using > > asynchronous call

Re: Small how to for Mesos + Ignite + Java

gt; > On Fri, Apr 15, 2016 at 6:36 AM, Nikolay Tikhonov > wrote: > > > Hi, > > Thank you for efforts and feedback! > > > > Vova, > > I'll change our documentation that points will be more clear. > > > > On Fri, Apr 15, 2016 at 4:25 PM, Vladimir

Re: Small how to for Mesos + Ignite + Java

Hi, Thank you for efforts and feedback! Vova, I'll change our documentation that points will be more clear. On Fri, Apr 15, 2016 at 4:25 PM, Vladimir Ozerov wrote: > Hi, > Thank you for such deep and thorough analysis. I think we definitely > reflect your findings in our documentation. > > Nick

Re: API for asynchronous execution.

ould ever want to have a synchronous callback? > > Aren’t all filter notifications supposed to be asynchronous, especially > if > > there is no performance degradation? > > > > D. > > > > On Thu, Apr 14, 2016 at 11:17 AM, Nikolay Tikhonov < > ntikho...@gridgain.c

Re: API for asynchronous execution.

IgniteConfiguration.setAsyncCallbackPoolSize(...) method. On Thu, Apr 14, 2016 at 8:10 PM, Dmitriy Setrakyan wrote: > Do we have a coding example for this functionality somewhere? It would be > nice to review the changes from usability standpoint. > > On Thu, Apr 14, 2016 at 3:58 AM, Nikolay Tikhonov > wrote: > &

Re: API for asynchronous execution.

We are close to completing IGNITE-2004 ticket. As part this ticket was made the following changes on public API - if callback has @IgniteAsyncCallback annotation then callback should be run asynchronously - these callbacks are executed in special pool (callback thread pool) which is configured by I

Re: API for asynchronous execution.

Vova, 1) As far as I remember, we enforce ordering of updates for the same key, > right? If yes, then stalled filter invoke for update #1 will stall all > further updates. > Invocation of filter will be implemented in thread-partition style for supporting ordering of updates. > 2) Listener noti

Re: API for asynchronous execution.

9, 2016 at 2:23 PM, Nikolay Tikhonov > wrote: > > > Hello Igniters, > > > > Lately I'm working on a ticket > > https://issues.apache.org/jira/browse/IGNITE-2004. As part of the ticket > > need to add API which will provide an ability to execute operation &

API for asynchronous execution.

Hello Igniters, Lately I'm working on a ticket https://issues.apache.org/jira/browse/IGNITE-2004. As part of the ticket need to add API which will provide an ability to execute operation asynchronously. The ability might be useful not only for continuous query filter but also for cache and discove

[jira] [Created] (IGNITE-2699) Starvation when CacheEntryListenerConfiguration.isSynchronous is true

Nikolay Tikhonov created IGNITE-2699: Summary: Starvation when CacheEntryListenerConfiguration.isSynchronous is true Key: IGNITE-2699 URL: https://issues.apache.org/jira/browse/IGNITE-2699

[jira] [Created] (IGNITE-2630) Make 'updateCntr' available through CacheInterceptor API

Nikolay Tikhonov created IGNITE-2630: Summary: Make 'updateCntr' available through CacheInterceptor API Key: IGNITE-2630 URL: https://issues.apache.org/jira/browse/IGNITE-2630 Proje

Re: Docker image

Val, Our docker repo contains not only the latest version or 1.0.0-incubating, there all versions. List of versions here [1]. I've updated "Dockerfile" tab, now it shows dockerfile from "1.5.0.final" tag. [1] https://hub.docker.com/r/apacheignite/ignite/tags On Fri, Jan 29, 2016 at 9:34 AM, Val

[jira] [Created] (IGNITE-2435) Mesos doesn't work with limited access to internet

Nikolay Tikhonov created IGNITE-2435: Summary: Mesos doesn't work with limited access to internet Key: IGNITE-2435 URL: https://issues.apache.org/jira/browse/IGNITE-2435 Project: I

Re: Intoduction

Hi Edouard! I think it useful future and don't see any reason why you can't implement this task. Feel free to ask if you have questions. On Wed, Jan 20, 2016 at 6:08 PM, Edouard Chevalier < edouard.cheval...@techmydata.net> wrote: > Hi all, > > I'm Edouard Chevalier and I would like to contribu

Re: Ignite docker image

confused. Can you please describe what happens right now > with the image we have stored on the docker hub? I am interested in what > Ignite version is stored there and what Ignite version is downloaded > whenever no specific version is passed. > > D. > > On Mon, Jan 11, 2016

Re: Ignite docker image

> > In that case, why does the docker image contain any version of Ignite at > all? > We download docker image which was built from Dockerfile (which contains specific version of Ignite) and the image contains Ignite distributive. Apache Ignite distributive is downloaded only once in during the bui

Re: Ignite docker image

On Mon, Jan 11, 2016 at 8:39 PM, Dmitriy Setrakyan wrote: > > > I am not sure I understand. Are you suggesting we have different docker > files for different versions? Yes, for each Ignite version need to create Dockerfile with version and tag on DockerHub. I would prefer that unless a version

Re: Ignite docker image

Dima, Docker hub shows Dockerfile for `1.0.0-incubating` tag [1]. For this tag it is correct. [2] I would prefer see Dockerfile for the latest version, but I can't find functionality to change it. I'll ask DockerHub community how fix it. 1. https://hub.docker.com/r/apacheignite/ignite/~/dockerfile

Re: [VOTE] Apache Ignite 1.5.0.final RC3

+1 (binding) On Tue, Dec 29, 2015 at 4:23 PM, Anton Vinogradov wrote: > +1 (binding) > > On Tue, Dec 29, 2015 at 4:17 PM, 姜 为 wrote: > > > +1 nice job! > > > > > 在 2015年12月29日，下午6:54，Anton Vinogradov 写道： > > > > > > Dear Sirs! > > > > > > We have uploaded release candidate to > > > https://dis

Re: [VOTE] Apache Ignite 1.5.0.final

+1 (binding) On Fri, Dec 25, 2015 at 4:00 PM, Anton Vinogradov wrote: > Dear Sirs! > > We have uploaded release candidate to > https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc1/ > > This is very important release containing initial versions of Ignite.NET > and Ignite C++ and many oth

Re: [VOTE] Apache Ignite 1.5.0-b1

+1 On Wed, Dec 2, 2015 at 3:21 PM, Anton Vinogradov wrote: > +1 > > On Wed, Dec 2, 2015 at 3:16 PM, Yakov Zhdanov wrote: > > > Dear Sirs! > > > > We have uploaded release candidate to > > https://dist.apache.org/repos/dist/dev/ignite/1.5.0-b1-rc1/ > > > > This is very important release containi

Re: Ignite-1.5 Release

I'm fully agree with Yakov. We plain to release massive changes and I think that it's good chance for community to play with new features and we can get more feedback. On Mon, Nov 30, 2015 at 7:32 PM, Alexey Kuznetsov wrote: > +1 for EA > > On Mon, Nov 30, 2015 at 11:30 PM, Yakov Zhdanov > wrot

Re: Necessity to have MBeanServerResource annotation

Artem right. The annotation should be removed in https://issues.apache.org/jira/browse/IGNITE-35 ticket. On Wed, Nov 25, 2015 at 12:34 PM, Yakov Zhdanov wrote: > Thanks for clarifications, Artem! > > --Yakov > > 2015-11-25 12:27 GMT+03:00 Artem Shutak : > > > Igniters, > > > > As I remember, sup

Re: Ignite-1.5 Release

I've merged changes related to IGNITE-426 (Make sure continuous queries notifications are not missed in case primary node fails ) task. On Thu, Nov 19, 2015 at 5:53 PM, Anton Vinogradov wrote: > Twitter intergration > *https://issues.apache.org/jira/browse/IGNITE-530 >

[jira] [Created] (IGNITE-1922) Add auth support to YARN module

Nikolay Tikhonov created IGNITE-1922: Summary: Add auth support to YARN module Key: IGNITE-1922 URL: https://issues.apache.org/jira/browse/IGNITE-1922 Project: Ignite Issue Type

Re: Ignite-1.5 Release

I implemented changes related to IGNITE-426 task. Currently investigating performance degradation for atomic caches. I expect the ticket to be merged in 2 days. On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk wrote: > IGNITE-950 is taking more time to be merged than I originally estimated. We >

Re: AWS Tests on TeamCity

Raul, AWS build on TC is broken by another reason. Admin investigates this issue. For local testing you could use AWS Free Tier. (https://aws.amazon.com/free/ ) On Thu, Oct 29, 2015 at 4:25 PM, Denis Magda wrote: > Nick, should know the credentials. > > Nick, please help Raul with the setup. >

Re: what is "communication encryption"?

12:18 PM, Branko Čibej wrote: > > > On 30.09.2015 11:18, Nikolay Tikhonov wrote: > > > SslContextFactory allows to set different encryption protocols (by > > default > > > TLS). I think that just "ssl" confuses users. Might be "ssl\tls=off"

Re: what is "communication encryption"?

SslContextFactory allows to set different encryption protocols (by default TLS). I think that just "ssl" confuses users. Might be "ssl\tls=off" more acceptable? On Wed, Sep 30, 2015 at 11:53 AM, Dmitriy Setrakyan wrote: > On Wed, Sep 30, 2015 at 10:18 AM, Alexey Goncharuk < > alexey.goncha...@gm

Re: IGNITE-1195

> > I am confused. Are we saying that we work with 2.7.0, but not 2.6.0? I this > case I am OK disabling the Yarn module during the build. Nick, can you > confirm? > Yes. Sergey Kozlov in first message describe how disable Yarn module during the build.

Re: IGNITE-1195

> > I think the same question stands - what is the main challenge here? Yarn module is compatible with Hadoop version 2.7.0 and above. Exist two way: set different variables for yarn and hadoop modules or make yarn module compiled with older hadoop versions.