RE: Continuous queries and duplicates

2018-11-30 Thread Sobolewski, Krzysztof
queries and duplicates Hello! There should be isolation in AI 2.7 as an experimental feature. Regards, -- Ilya Kasnacheev пн, 26 нояб. 2018 г. в 12:53, Sobolewski, Krzysztof : Thanks. This is a little disappointing. ScanQuery would probably work, but it’s not as efficient (can’t use indexes etc

RE: Continuous queries and duplicates

2018-11-26 Thread Sobolewski, Krzysztof
г. в 19:25, Sobolewski, Krzysztof mailto:krzysztof.sobolew...@gs.com>>: Hi, I'm wanting to use a ContinuousQuery and there is a slight issue with how it transitions from the initial query to the notifications phase. It turns out that if there are additions to the cache happening

Continuous queries and duplicates

2018-11-23 Thread Sobolewski, Krzysztof
Hi, I'm wanting to use a ContinuousQuery and there is a slight issue with how it transitions from the initial query to the notifications phase. It turns out that if there are additions to the cache happening while the continuous query runs, an entry may be reported twice - once by the initial

Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

2017-12-07 Thread Krzysztof Chmielewski
Hi all, I would like to ask, if there is a way to use custom DataRegionConfiguration (other than default) for storing IgniteAtomicReferences. I would like to use Ignite's 2.3 feature where I can turn on/off Persistent per Cache (via DataRegionConfiguration). I would like to enable persistent only

Compute async Job from Ignite Service and return IgniteFuture

2017-11-27 Thread Krzysztof Chmielewski
iceProxy.doStuff(); future.get(); I've noticed that my client stuck on doStuff.get(); Thanks Krzysztof -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Service and node failure

2017-11-27 Thread Krzysztof Chmielewski
Thanks for a fast response :) All is clear now. Regards, Krzysztof -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite Service and node failure

2017-11-27 Thread Krzysztof Chmielewski
().serviceProxy(...)) when we want to call the service's method or can we get it only once, keep the reference, and reusing it. Thanks Krzysztof -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Use @ServiceResource with property placeholder

2017-11-23 Thread Krzysztof Chmielewski
Hi all, is it possible to use @ServiceResource with service name from property placeholder? In my Ignite config.xml I'm already using values from properties file Thanks Krzysztof -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Unable to query system cache through Visor console

2017-11-22 Thread Krzysztof Chmielewski
Thanks for your response Denis. My uses case would be to list all Ignite semaphores and Ignite atomic references used in my Ignite grid. As fare as I know, those are stored in system caches. Thanks Krzysztof -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Unable to query system cache through Visor console

2017-11-22 Thread Krzysztof Chmielewski
default-ds-group* Im using Ignite 2.3.0 Thanks Krzysztof -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

IgniteCache.localEntries(CachePeekMode... peekModes) result

2017-09-01 Thread Krzysztof Chmielewski
ry object we can set the pageSize to get only a certain number of entries at once, and further pages are fetched automatically. Thanks, Krzysztof

Re: Partitioning on a non-uniform cluster

2016-11-18 Thread Krzysztof
For the second option: would not it cause the over-utilisation of CPUs on the nodes with two servers running? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Partitioning-on-a-non-uniform-cluster-tp8940p9076.html Sent from the Apache Ignite Users mailing list

Partitioning on a non-uniform cluster

2016-11-14 Thread Krzysztof
way to achieve balanced distribution cluster memory-wise? Thanks Krzysztof -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Partitioning-on-a-non-uniform-cluster-tp8940.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-11 Thread Krzysztof
Hello, We would appreciate confirmation that GridDhtAssignmentFetchFuture::requestFromNextNode() makes impossible to have a client communicating via NAT, even with AddressResolver - or a pointer where we make a mistake in the code/logic. Judging by the code, GridDhtAssignmentFetchFuture has no

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-10 Thread Krzysztof
We would really like to use Ignite for our project (http://gaia.esac.esa.int/documentation/GDR1/Data_analysis/sec_cu7var/sec_cu7introduction.html which is part of http://sci.esa.int/gaia/) but this is a blocker. Do you think we could make client behind the NAT working? Best regards, Krzysztof

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-06 Thread Krzysztof
easons are: ^-- Transactions in deadlock. ^-- Long running transactions (ignore if this is the case). ... I would appreciate clarifying this.. Krzysztof On Fri, Oct 7, 2016 at 12:58 AM, vkulichenko [via Apache Ignite Users] < ml-node+s70518n8134...@n6.nabble.com> wrote: > You set 47099 as a com

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-06 Thread Krzysztof
Thanks for the hint, but in the snippet I sent there's already: // Override default discovery SPI. cfg.setDiscoverySpi(spi); cfg.setAddressResolver(basicResolver); // it does not change anything (spi, commSpi have the resolve set too). Or do you mean something else? Cheers On Wed, Oct 5, 2016

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-05 Thread Krzysztof
8], sockAddrs=[0:0:0:0:0:0:0:1%lo:48500, > /127.0.0.1:48500, /192.168.168.8:48500], discPort=48 > > 500, order=218, intOrder=110, lastExchangeTime=1475627164474, > loc=false, ver=1.8.0#20161004-sha1:a370bad1, isClient=false] > > at > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.s

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-04 Thread Krzysztof
log4j and ignite-log4j from 1.8 on the classpath. Cheers Krzysztof On Tue, Oct 4, 2016 at 11:27 PM, vkulichenko [via Apache Ignite Users] <ml-node+s70518n8090...@n6.nabble.com> wrote: > All nodes should run on the same version. > > What is exactly different in log4j beh

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-04 Thread Krzysztof
ode(CacheMode.PARTITIONED); cacheCfg.setBackups(0); Any hints? Cheers On Tue, Oct 4, 2016 at 1:15 AM, vkulichenko [via Apache Ignite Users] <ml-node+s70518n8066...@n6.nabble.com> wrote: > Hi Krzysztof, > > This issue was fixed some time ago, so in 1.8 Ignite will publish pub