Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null

Cross-sending to user@ as well. On Tue, Sep 5, 2017 at 10:44 PM, kotamrajuyashasvi < kotamrajuyasha...@gmail.com> wrote: > Hi > > I'm using ignite with cassandra as persistent store. I have a POJO class > mapped to cassandra table. I have used > ignite-cassandra-store/KeyValuePersistenceSettings

Re: IgniteDataStreamer.addData - behavior for a FULL_SYNC Cache

On Tue, Sep 5, 2017 at 10:51 AM, mcherkasov wrote: > I think javadoc is the best source for this: > > /** > * Flag indicating that Ignite should wait for write or commit replies > from all nodes. > * This behavior guarantees that whenever any of the atomic or

Message Queue Size

hello igniters, When I start up the console, I get this warning - Message queue limit is set to 0 which may lead to potential OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to message queues growth on sender and receiver sides. I am wondering how can I set the

With onHeapCacheEnabled = false, BinaryOnHeapOutputStream is still used, why?

Hi, I'm running the CacheAPIExample below with no on-heap caching, locally using Intellij. The stack frame shows that the entry I put is written on heap (using BinaryOnheapOutputStream) and not off-heap (using BinaryOffheapOutputStream). What's going on? try (Ignite ignite =

Re: Issue with starting Ignite node on AWS

Most likely ignite-aws module is not enabled. For standalone node started using ignite.sh, move 'ignite-aws' folder from 'libs/optional' to 'libs' prior to node start. For embedded, add 'ignite-aws' Maven dependency along with 'ignite-core', 'ignite-spring' and any other that you might use. -Val

Re: Issue with starting Ignite node on AWS

Most likely ignite-aws module is not enabled. For standalone node started using ignite.sh, move 'ignite-aws' folder from 'libs/optional' to 'libs' prior to node start. For embedded, add 'ignite-aws' Maven dependency along with 'ignite-core', 'ignite-spring' and any other that you might use. -Val

Re: Issue with starting Ignite node on AWS

I'm also a newbie, but I'm running 2.1.0 and I seem to be hitting the same problem, which sounds like it was fixed a long time ago.Is there something else going on? I've uploaded the 2 lines I pass when creating the EC2 instance from the AMI as well as the config file I'm using, as well as the

Re: Data Page Locking

Thanks Mikhail! If I may ask two additional questions: 1. Is there any difference between data page eviction and check pointing (dirty pages being written to disk) when persistent store is enabled? My understanding is yes there is a difference: check pointing is a periodical process

Re: client thread dumps

Thank you for all your help ... -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Continuous Query event buffering OOME

Hi Michal, Those buffers are required to make sure that all messages are delivered to all subscribers and delivered in right order. However I agree, 1M is a relatively large number for this. I will check this question with Continuous Query experts and will update you tomorrow. Thanks, Mikhail.

Re: Data Page Locking

Hi John, it's for internal use only, for example, a page can be locked for a checkpoint, to avoid writes for the page while we writing it to a disk. These bytes are used by OffheapReadWriteLock class, you can look at its usage if want learns more about this. Thanks, Mikhail. -- Sent from:

Re: ignite compute job continuation documentation

Hi Anton, We have only docs that you mentioned. Do you have questions about continuation jobs? Thanks, Mikhail. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IgniteDataStreamer.addData - behavior for a FULL_SYNC Cache

I think javadoc is the best source for this: /** * Flag indicating that Ignite should wait for write or commit replies from all nodes. * This behavior guarantees that whenever any of the atomic or transactional writes * complete, all other participating nodes which cache the

Affinity and String key (was: SQLQuery with simple Join return no results)

Hi Denis, I don’t quite understand your comment “If you use Strings as the keys you won’t get affinity collocation set up properly”. I have an object with a plain String key, named switchId, and another object with a composite key, of which one field is switchId (of type String). I am using

ignite compute job continuation documentation

Hi folks, Is there any documentation of continuation support for grid job context ? Except ComputeFibonacciContinuationExample and javadocs

Re: client thread dumps

Hi, I think it's a collection of objects from previous exchanges. By default, GridCachePartitionExchangeManager stores 1000 objects, but since version 2.1 it's possible to reduce this size. I would recommend you to update to version 2.1 and try to reduce this property:

Re: IgniteDataStreamer.addData - behavior for a FULL_SYNC Cache

Hi Mikhail, I am just trying to understand the behavior of addData method in conjunction with FULL_SYNC. If we have just one server node left, then we are not really replicating, isn't it ? So let's say we have to persist 2 entries, and after 1 write and replication, one of the server goes down,

Re: copyOnRead to false

Hi, I want to clarify about usage copyOnRead=False: As far as I know, It should help in 1.x releases, with the default configuration, when entries stored in onheap and in 2.x releases, with onHeapCacheEnabled=true(it's not default). I think we should mention this in the documentation. Also, it

Re: client thread dumps

Hello Evgenii, We only used ignite for 2nd level cache, mostly we used get operation on cache however we monitor with Ignite visor console, not sure if that would make difference. Do you know what could be the reason for leak which shows on heap dump ? One instance of

Re: IgniteDataStreamer.addData - behavior for a FULL_SYNC Cache

Hi, it works as expected, with REPLICATED cache you can't lose you data while you have at least 1 server node alive. Why do you think it should throw an exception? Thanks, Mikhail. On Tue, Sep 5, 2017 at 5:05 PM, userx wrote: > Hi all, > > I am using IgniteDataStreamer to

Re: Task management - MapReduce & ForkJoin performance penalty

But of course, it could be changed. The community didn't decide yet if wiki doesn't have information about it. 2017-09-05 17:46 GMT+03:00 Evgenii Zhuravlev : > I think it was planned at the end of October. > > Evgenii > > 2017-09-05 17:41 GMT+03:00 ihorps

Re: Task management - MapReduce & ForkJoin performance penalty

I think it was planned at the end of October. Evgenii 2017-09-05 17:41 GMT+03:00 ihorps : > hi, @ezhuravlev > > This is what I'm looking for, many thanks! > > Some hints when v2.3 is planned to be release (I can't find it on wiki)? > > I'd rather wait for this API in Ignite

Re: ignite.active(true) blocking forever

Hi, I am sorry for the delay. I was able to reproduce this issue, and it looks like a bug. I created a jira ticket in order to track this https://issues.apache.org/jira/browse/IGNITE-6274 Thanks, Slava. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Task management - MapReduce & ForkJoin performance penalty

hi, @ezhuravlev This is what I'm looking for, many thanks! Some hints when v2.3 is planned to be release (I can't find it on wiki)? I'd rather wait for this API in Ignite then implementing it by myself an throw it later such as I'm in evaluation/prototype phase now. Best regards, ihorps --

Re: Task management - MapReduce & ForkJoin performance penalty

Hi, Here is a ticket for exactly what you want, it's in progress right now: https://issues.apache.org/jira/browse/IGNITE-5037 If you don't want to wait till it will be implemented, you can use affinityCall(...) or affinityRun(...) and somehow reduce result after it will be returned. Evgenii

IgniteDataStreamer.addData - behavior for a FULL_SYNC Cache

Hi all, I am using IgniteDataStreamer to write to a cache. As a part of my testing, I started 2 servers on a local node and 1 client locally. I put everything in debug mode in eclipse, and put a debug point where I am calling IgniteDataStreamer.addData(). After that i let 2-3 entries to be

Re: Re: Is there any way to listener to a specific remote cache's update events ?

Great, thanks this seem what we need, we will have a try, thanks you Nikolay! Regards Aaron aa...@tophold.com From: Nikolay Izhikov Date: 2017-09-05 19:38 To: user Subject: Re: Is there any way to listener to a specific remote cache's update events ? Hello, Aaron. I think continuous

Continuous Query event buffering OOME

Hi, We are using a simple replicated Ignite cache with a few continuous queries. Recently we were running into an OOME after several days of running it without a restart. The histogram shows that most of the heap is utilized by the buffered/cached continuous query entries. The code analysis

Is there any way to listener to a specific remote cache's update events ?

hi All, I look around the event section try to find a way to catch a specific cache's update events, and persist those event to a historical database. We have a instance update a market data Ignite cache; on another side we need persist all those historical events. The listener side host

Re: UPDATE SQL for nested BinaryObject throws exception.

Hi, FYI. Created tickets related to the subject: 1) https://issues.apache.org/jira/browse/IGNITE-6265 2) https://issues.apache.org/jira/browse/IGNITE-6266 3) https://issues.apache.org/jira/browse/IGNITE-6268 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: About Apache Ignite Partitioned Cache

Thanks Evgenii and Denis . On Tue, Sep 5, 2017 at 9:57 AM, Denis Mekhanikov wrote: > > The backups which is mentioned in the documentation, how do I define > which node is the primary node and which node is the backup node. > > You can either define your own affinity

Re: Serialization exception in Ignite compute job

HI, Thanks. Its clear now. And it solved the issue. Thanks again -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Specifying location of persistent storage location

Raymond, I think most of Ignite users run on ipv4. So, issues with v6 in this case are hardly possible =) --Yakov

RE: Specifying location of persistent storage location

Hi Pavel, Thanks for the pointer on how to have both the XML and .Net client configuration supplied to Ignite. Raymond. *From:* Pavel Tupitsyn [mailto:ptupit...@apache.org] *Sent:* Tuesday, September 5, 2017 8:56 PM *To:* d...@ignite.apache.org *Cc:* user@ignite.apache.org; Dmitriy

RE: Specifying location of persistent storage location

Hi Yakov, Yes, Dmitriy walked me through how setting the LocalHost results in the folder name for the persistent data to be fixed. I also fixed the port number as this is also an aspect of the folder name. Is there a known issue with IPv6 interfaces on a server hosting Ignite? Thanks,

Re: New API docs look for Ignite.NET

Great news, thanks a lot! On Tue, Sep 5, 2017 at 11:47 AM, Pavel Tupitsyn wrote: > DocFX takes around 30 seconds on my machine. > > > if you already tried that > Yes, everything is done on my side, see JIRA ticket [4] and preview [5] > above. > > On Tue, Sep 5, 2017 at

Re: Specifying location of persistent storage location

Ignite.NET does not have IgniteConfiguration.ConsistentId, here is the ticket: https://issues.apache.org/jira/browse/IGNITE-6249 Workaround is to use Spring XML for that particular property (keep everything else in .NET, configs will be merged):

Re: Specifying location of persistent storage location

+ dev Pavel Tupitsin, can you please check that org.apache.ignite.configuration.IgniteConfiguration#setConsistentId has it platform counterpart? I could not find it. Raymond, you can explicitly set a bind address for Ignite with public string Localhost { get; set; }. This will make consistent ID

Re: New API docs look for Ignite.NET

DocFX takes around 30 seconds on my machine. > if you already tried that Yes, everything is done on my side, see JIRA ticket [4] and preview [5] above. On Tue, Sep 5, 2017 at 11:45 AM, Ilya Suntsov wrote: > Pavel, thanks! > It is the great news! > Looks like DocFX will

Re: Failed to accept TCP connection. java.net.SocketException: Too many open files

Hi, Ignite Persistent store requires creating a number of files like a WAL (write-ahead log), page store (which is implemented as file per partition) etc. So, you need to increase the open files limit. In order to do that you can edit limits.conf (nofile - max number of open files) or you can use

Re: New API docs look for Ignite.NET

Pavel I like the idea to change Doxygen. It really becomes uncomfortable to regenerate often. Do you know how much DocFX faster than Doxygen (if you already tried that)? On Tue, Sep 5, 2017 at 11:16 AM, Pavel Tupitsyn wrote: > Igniters and users, > > Historically we've

Re: Failed to accept TCP connection. java.net.SocketException: Too many open files

Hi all, Looking at https://apacheignite.readme.io/v2.1/docs/jvm-and-system-tuning it looks like the recommended setting for ulimit is 32768. Pardon my limited knowledge, but can some one please tell me why this large number is required ? Current settings have 1024 as the limit but before I

New API docs look for Ignite.NET

Igniters and users, Historically we've been using Doxygen [1] to generate .NET API documentation [2]. Recently it became very slow on our code base (more than 30 minutes to generate), and I could not find any solution or tweak to fix that. Other issues include outdated looks and limited

Re: About Apache Ignite Partitioned Cache

> The backups which is mentioned in the documentation, how do I define which node is the primary node and which node is the backup node. You can either define your own affinity function or use RendezvousAffinityFunction and set a backup filter using setAffinityBackupFilter

Re: copyOnRead to false

Hello, thanks for the answer. The benchmark is actually our application stressed with several volumes. Some quite complex to describe. However, for these benchmarks we are only using one node. Basically we are loading a set of caches from the database, do a lot of querying both ScanQuery (on

Re: Quick questions on Evictions

Hi John, 1. Actually it is. By default data page eviction is disabled (DataPageEvictionMode.DISABLED) and when no memory left, it will throw IgniteOutOfMemoryException. 2. If you have enabled persistence - no data will be lost, dirty pages will be written do disk. In other words Ignite starts

Failed to accept TCP connection. java.net.SocketException: Too many open files

Hi all, I am not sure about the steps how the following error happened but can someone help explain what the logs have to say. 2017-09-05 04:45:52,731 WARN [tcp-disco-msg-worker-#3%e89cfda3-beb6-4eca-ada2-fb4c3b2eebbc%] {}

Re: Specifying location of persistent storage location

On Mon, Sep 4, 2017 at 8:40 PM, Raymond Wilson wrote: > Thanks. > > > > I get the utility of specifying the network address to bind to; I’m not > convinced using that to derive the name of the internal data store is a > good idea! J > For instance, what if you have