Re: Serialization issue with Ignite 1.5 built from master (357d791)

Paulo, The issue has been fixed and the fix was merged to master. You should be able to cherry-pick the commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583 and build Ignite from sources with this fix.

Re: How to get rid of the message( Received message without registered handler ) ?

When you run the ContinuousQuery in two of the server nodes, CacheObjectImpl pile up in the CacheContinuousQueryHandler.backupQueue and OOM occurred. And continue to display the message [Received message without registere

Re: Stupide question about Queue ?

Hi Murthy, Swap space allows to write evicted data to disc to avoid out of memory. This is not persistence, because this data will be lost if the node leaves topology. For caches persistence can be implemented with the help of CacheStore interface [1]. For queues and sets it's not possible now, I

Re: Stupide question about Queue ?

Created ticket for queue swapping feature: https://issues.apache.org/jira/browse/IGNITE-2389 Feel free to provide feedback. -Val On Thu, Jan 14, 2016 at 3:24 PM, Murthy Kakarlamudi wrote: > What are the possibilities for swap spaces? Can we persist the cache/queue > content to file system base

Loadcache behavior

I was loading data from AWS Redshift into Ignite through the loadcache API. cache.loadCache(null, "java.lang.Integer", "select * from lineorder where lo_orderdate > 19970101"); I ran this from a single client. The query basically ran on all the nodes. I had 1 client and 2 servers and the same que

Re: Stupide question about Queue ?

What are the possibilities for swap spaces? Can we persist the cache/queue content to file system based on the eviction policy? Thanks, Murthy. On Thu, Jan 14, 2016 at 5:23 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Agree with Denis. Sounds like this can be easily achieved

Re: Hem, registerUserClassDescriptor

Hi Yann, This is a known issue and there is 'in progress' ticket for this [1]. It should be fixed and merged to master shortly. For now the only workaround is to temporarily rename this classes, so that their simple names are not equal. Is it possible? [1] https://issues.apache.org/jira/browse/I

Re: Stupide question about Queue ?

Agree with Denis. Sounds like this can be easily achieved by enabling swap layer for queue cache. So we just need to put this on configuration. -Val On Thu, Jan 14, 2016 at 5:44 AM, Denis Magda wrote: > Hi, > > This seems to be an interesting functionality. As I understand you're > referring to

Re: Ignite "bugs" ?

Hi Yann, I was able to reproduce the issue and created a ticket [1]. Will fix it shortly by simply ignoring non-string properties. I found two places that can cause issues: update checker and node attributes. Looks like your issue was caused by the first one, it can be workarounded by disabling t

Re: Working with Ignite Cache on Scala Play

Avi, I think there is no need to start/stop nodes on each api interaction. Start/stop nodes is a quite heavy and also will trigger rebalancing in caches. I think you should just start several nodes only once. -- Alexey Kuznetsov GridGain Systems www.gridgain.com

Working with Ignite Cache on Scala Play

Hi, I just want to confirm whether the pattern I'm thinking of following for our requirement and also to clear some doubts I have. The requirement we have is to use Ignite Caching service to store values from a database to speed up api requests for that data. The application is a Scala Play

Re: isManagementEnabled vs isStatisticsEnabled.

Hi Vinay, Regardless of the fact that both flags trigger creation of the mentioned bean their purpose is different. If you set isStatisticsEnabled to 'true' then bunch of cache related metrics will be being gathered and become available via CacheMetrics and CacheMetricsMXBean. On the other

Re: Stupide question about Queue ?

Hi, This seems to be an interesting functionality. As I understand you're referring to [1]. Personally I think that it makes sense to support the same in Ignite. However I would just extend CollectionConfiguration adding ability to set an eviction policy and enable swap on demand. When evicti

Hem, registerUserClassDescriptor

Hello, me ; again... I continue to replace Hazelcast by ignite in my code. I have to use Queues, and sometime, tere some things I don't understand in the Ignite code. Well, In my case, I have multiple objects to push in Queues. Each of its have its own Queues.But this object are "primary keys" o

Re: Client & server in the same VM

Hi Daniel, It's easy to support your use case if to configure multicast [1] or static IP finders in a particular way. Please refer to these discussions happened earlier: http://apache-ignite-users.70518.x6.nabble.com/How-keep-separate-different-grid-instances-on-the-same-network-td1609.html ht

Client & server in the same VM

Hi there, I have an application where I need to share some data between all nodes, so we created a cluster with REPLICATED caches, so far so good. There are other pieces of data that we need to use that we don't need/want to keep local, so we are trying to setup a different cluster and let the ap

Stupide question about Queue ?

Hello, In hazelcast we can persist Queues in Database, this help me for example when consumer are down to no have OOM exception. But I don't see this possibility in Ignite docs ? This message and any attachments (the "message") is intended solely for the intended addressees and is confidenti

Re: TcpDiscoveryVmIpFinder's isShared property

Guys, this property is supported in VM IP finder for simplifying discovery in single VM. I agree, that name could be better, but I would not mess with it for now and just fix the javadocs (pls review, I did that in master). "isShared" is a property of any IP finder. If it is "true" then IP finder

Re: Ignite "bugs" ?

Hy Yann, My guess it is that TcpDiscoveryJdbcIpFinder hangs on an attempt to connect to the data source provided in its configuration. Probably your DB is not reachable from the Ignite node or it generates an error that is not forwarded to Ignite. In any case a threads dump knows the answer p

RE: Ignite "bugs" ?

Gotcha This is this part : TcpDiscoverySpi discoverySpi=new TcpDiscoverySpi(); TcpDiscoveryJdbcIpFinder ipFinder=new TcpDiscoveryJdbcIpFinder(); ipFinder.setDataSource(dataSource); discoverySpi.setIpFinder(ipFinder); config.setDiscoverySpi(discoveryS

RE: Ignite "bugs" ?

Hello. I'm not using config file I'm using java code to configure : @Produces @ApplicationScoped public Ignite produceInstance() { LOG.info("** Prepare Ignite "); IgniteConfiguration config = new IgniteConfiguration(); config.setClientMode(false); conf