Re: Questions about baseline auto-just

Hi, It looks like baseline topology auto-adjustment is in process. Did you checked cluster state later? Also to track auto-adjustment events please check your logs for messages like: Baseline auto-adjust will be executed right now ... Baseline auto-adjust will be executed in ... Baseline auto

Re: Questions related to check pointing

Hi Zhenya, Thanks for the pointers - I will look into them. I have been doing some additional reading into this and discovered we are using a 4.0 NFS client, which seems to be the first 'no-no'; we will look at updating to use the 41 NFS client. We have modified our default timer cadence for che

Re: Questions related to check pointing

fsync=37104ms too long for such pages amount : pages=33421, plz check how can you improve fsync on your storage.   > > >--- Forwarded message --- >From: "Raymond Wilson" < raymond_wil...@trimble.com > >To: user < user@ignite.apache.org >, "Zhenya Stanilovsky" < arzamas...@mail.ru >> >C

Re: Questions related to check pointing

I noticed an entry in the Ignite 2.9.1 changelog: - Improved checkpoint concurrent behaviour I am having trouble finding the relevant Jira ticket for this in the 2.9.1 Jira area at https://issues.apache.org/jira/browse/IGNITE-13876?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.9.1%20

Re: Questions related to check pointing

Hi Zhenya, 1. We currently use AWS EFS for primary storage, with provisioned IOPS to provide sufficient IO. Our Ignite cluster currently tops out at ~10% usage (with at least 5 nodes writing to it, including WAL and WAL archive), so we are not saturating the EFS interface. We use the default page

Re: Questions related to check pointing

* Additionally to Ilya reply you can check vendors page for additional info, all in this page are applicable for ignite too [1]. Increasing threads number leads to concurrent io usage, thus if your have something like nvme — it`s up to you but in case of sas possibly better would be to reduce

Re: Questions related to check pointing

As another detail, we have the WriteThrottlingEnabled property left at its default value of 'false', so I would not ordinarily expect throttling, correct? On Tue, Dec 29, 2020 at 10:04 AM Raymond Wilson wrote: > Hi Ilya, > > Regarding the throttling question, I have not yet looked at thread dump

Re: Questions related to check pointing

Hi Ilya, Regarding the throttling question, I have not yet looked at thread dumps - the observed behaviour has been seen in production metrics and logging. What would you expect a thread dump to show in this case? Given my description of the sizes of the data regions and the numbers of pages bein

Re: Questions related to check pointing

Hello! 1. If we knew the specific circumstances in which a specific setting value will yield the most benefit, we would've already set it to that value. A setting means that you may tune it and get better results, or not. But in general we can't promise you anything. I did see improvements from in

Re: Questions Regarding Critical Workkers Health Check

Hi, Question-1: Does the above log mean that the thread is really blocked? or is it just busy doing something else? The thread in question might be busy doing something else and did not update its heartbeat timestamp. See: https://apacheignite.readme.io/docs/critical-failures-handling#cri

Re: Questions on the mechanics of activated on-heap in ignite 2.x.x

Hello! 1. I'm not sure it will be immediately available on heap. 2. This sounds a more reasonable assumption. 3. I guess so, but the real issue here is that on-heap cache increases Full GC times. At some point it will become infeasible. 4. Yes, it would counteract the change to off-heap model. Re

Re: Questions regarding Data Availability/Replication. @Ignite Team, please answer as it's important for us.

Hi, The easiest solution that can be used here is just to have 2 server nodes in one cluster, make sure that all primary partitions will be on the SN1 only(it can be done using affinity function). Caches should be configured as Replicated and SN2 will have backups for everything. However, if you h

Re: questions

Hello! It's impossible to answer this question without going into specifics of your use case, which I don't have. Maybe you have a case to show? Regards, -- Ilya Kasnacheev пт, 23 авг. 2019 г. в 16:22, narges saleh : > Hello Ilya > > There are parallel streams inserting data for all the count

Re: questions

Hello Ilya There are parallel streams inserting data for all the countries into different nodes (and caches) and there are parallel queries against the distributed database for different countries, aggregating the data, in some cases inserting back the data, and others returning results. Yes, for

Re: questions

Hello! I don't think that partitioning by country or city is a good idea, since this distribution will be very uneven. You can have different ways of minimizing network hops, while keeping distributed nature of your database. Database isn't really distributed when for a given city query, only one

Re: questions

Hello Ilya, I agree with you that partitioning based on month was a bad example, because most will be idle. Country or customer are better examples of my case. There are limited number of them, but they are disproportionate and they are always active. Let's take the country example. I need to sear

Re: questions

Hello! Partitioning based on let's say user id is usually fair, because there usually are 100,000ths of users and neither of those owns disproportionate amount of data. Partitioning by month is especially bad, since in a given months, all of partitions will be basically idle save for one, and the

Re: questions

I am not sure you can find real world examples where caches can be evenly partitioned, if the partitioning factor is an affinity key. I comparing, with partitioning case with relational databases, say partitioning based on month of the year. I definitely don't have 100s of departments but I do have

Re: questions

Hello! 1) No. Ignite only rebalances data when nodes are joining or leaving cluster. 2) Ignite's affinity is not really well suited to such detailed manual assignment. It is assumed that your cache has large number of partitions (e.g. 1024) and data is distributed evenly between all partitions. Ha

Re: questions

Thanks Ilya for replies. 1) Doesn't ignite rebalance the nodes if there are additional nodes available and the data doesn't fit the cache current ignite node? Consider a scenario where I have 100 pods on a physical node, assuming pod = ignite node. 2) I am not sure what you mean by confining half

Re: questions

Hello! 1) When there is an overflow, either page eviction kicks in, or, if it is disabled, you get an IgniteOOM, after which the node is no longer usable. Please avoid overflowing any data regions since there's no graceful handling currently. 2) I don't think so. You can't easily confine half of c

Re: Questions on IgniteDataStreamer

Hello! Can you please at least share the exceptions you are getting? Regards, -- Ilya Kasnacheev сб, 1 июн. 2019 г. в 13:55, Om Thacker : > Hello vbm, > > I am working on the exact same problem. Did you find the solution for the > same. > I am using following code in my client application whi

Re: Questions on IgniteDataStreamer

Hello vbm, I am working on the exact same problem. Did you find the solution for the same. I am using following code in my client application which will listen to kafka connect (confluent). I have one to one mapping for kafka topic and ignite cache. When there is an insert into db, the kafka list

Re: Questions about how Ignite SQL Works

I get it. Thank you for answering my question Mikael :-) . > 在 2018年7月30日，16:18，Mikael 写道： > > Hi! > > With native persistence enabled it's all done for you, a query will search > both ram and disk contents and at a restart Ignite will load "missing" data > from disk when needed, so if you d

Re: Questions about how Ignite SQL Works

Hi! With native persistence enabled it's all done for you, a query will search both ram and disk contents and at a restart Ignite will load "missing" data from disk when needed, so if you do an SQL query it will load any data from disk if it should be included in the result, for the query poi

Re: Questions about how Ignite SQL Works

Okay, thank you. > 在 2018年7月30日，15:32，Prem Prakash Sharma > 写道： > > Don't know about the first question but if you have persistence enabled > ignite will load the data on startup > > Regards, > Prem > > On Mon, Jul 30, 2018, 1:00 PM Lijun Cao <641507...@qq.com >

Re: Questions about how Ignite SQL Works

Don't know about the first question but if you have persistence enabled ignite will load the data on startup Regards, Prem On Mon, Jul 30, 2018, 1:00 PM Lijun Cao <641507...@qq.com> wrote: > Hi: > > I have referenced *How Ignite SQL Works *document but I still have got 2 > questions. > > The fir

Re: Questions on IgniteDataStreamer

Hi, Can anyone provide some info on this ? Regards, Vishwas -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Questions on setting up firewall for multicast cluster discovery.

reboot. -Original Message- From: vkulichenko [mailto:valentin.kuliche...@gmail.com] Sent: 29 June 2018 15:05 To: user@ignite.apache.org Subject: Re: Questions on setting up firewall for multicast cluster discovery. Hi Jon, First of all, you don't have to use multicast for discovery.

Re: Questions on setting up firewall for multicast cluster discovery.

Hi Jon, First of all, you don't have to use multicast for discovery. Using static IP configuration or one other shared IP finder might simplify the setup: https://apacheignite.readme.io/docs/tcpip-discovery Second of all, I'm not sure I fully understand what you're trying to achieve. Are both nod

Re: Questions about SQL interface

Hello Wolfram, After some reflection, it doesn't clear to me that this behavior is a bug. SQL engine always works with binary objects. When some operation (insert, update etc) is executed via SQL api, you can think about it as using something like the following: cache.withKeepBinary().query(...) I

Re: Questions about SQL interface

Hello Slava, the workaround totally works for me, I already have an Interceptor for certain caches anyway. Thanks a lot for looking into this. Will you take care of the jira ticket, too? Cheers Wolfram On 23/01/2018 06:19, slava.koptilin wrote: Hello, Here is the SQL statement and the exc

Re: Questions about SQL interface

Hello, > Here is the SQL statement and the exception from the logs: > https://gist.github.com/wolframite/d0b28d8b7ce483f82b9fd145adb68abe I tried this use-case with cache configuration you provided and I was able to reproduce the issue. When insert/update operation is executed via SQL api, the ac

Re: Questions about SQL interface

Hello Slava, On 19/01/2018 19:48, slava.koptilin wrote: Hello Wolfram, 1. Duplication of table entries in sqlline (!tables) This is a known issue https://issues.apache.org/jira/browse/IGNITE-7277 This bug has been resolved in master branch and will be available in Apache Ignite 2.4. I see,

Re: Questions about SQL interface

Hello Wolfram, > 1. Duplication of table entries in sqlline (!tables) This is a known issue https://issues.apache.org/jira/browse/IGNITE-7277 This bug has been resolved in master branch and will be available in Apache Ignite 2.4. 3. Updating / Inserting via SQL fails Could you please provide SQL

Re: Questions regarding Ignite as hdfs cache

Hi, 1) I think you can run Ignite in the non-quiet mode with flag '-v' or even with DEBUG logs, it will definitely show information if it used. Otherwise, you can make some mistake in IGFS configuration and check if it will work. If you will face exceptions, this means that Ignite worked. 2,3,4)

Re: Questions about "ignite-indexing"

Hi Chris, It looks like Dmitry already answered your qns: http://apache-ignite-users.70518.x6.nabble.com/getAsMap-tt16242.html#a16347 > Hi Chris, > > 1. Indexing may slowdown insertions, but in will not be used if no > CacheConfiguration.setIndexedTypes() or > CacheConfiguration.setQueryEntiti

Re: Questions on Ignite Clients

abdul shareef wrote > Thanks Val. Is there a way to disable the startup message on the client > nodes? Not completely, bur you can disable the ASCII logo by setting -DIGNITE_NO_ASCII=true system property. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Que

Re: Questions on Ignite Clients

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. abdul shareef wrote > The client node is also taking time to

Re: Questions on Ignite Clients

Hi Tab, Client exchange heartbeats with only one of the server nodes. If there is a problem with this connection, it affects only client node, not server topology. As for non-discovery communication (i.e. any operation requests and responses), however, client can connect to any node in topology.

Re: Questions on Ignite Clients

Hi Val, Thanks for your response, I've subscribed to the group as you suggested. Just to confirm then, a client is not taking part in any kind of cluster heart beats or checks? I'd prefer it if there could be a 100% native .NET client as we've had trouble in the past where other vendors supplied

Re: Questions on Ignite Clients

Hi Tab, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. Tab Spangler wrote > (1) Are the Clients truly clients of

RE: Questions on Client Reconnect and Client Cache

Hi Mani, Cache configuration will indeed be broadcasted - that's how cache start procedure currently works, it doesn't depend on cache mode. However, if cache mode is LOCAL, the data will be stored only the node where you created it. -Val -- View this message in context: http://apache-ignite-

RE: Questions on Client Reconnect and Client Cache

lto:valentin.kuliche...@gmail.com] Sent: Thursday, January 12, 2017 2:57 AM To: user@ignite.apache.org Subject: RE: Questions on Client Reconnect and Client Cache Mani, 1. Specific timeout value depends on you environment network speed, etc. Basically, client will automatically reconnect to serve

RE: Questions on Client Reconnect and Client Cache

Mani, 1. Specific timeout value depends on you environment network speed, etc. Basically, client will automatically reconnect to server when the latter is restarted, but it will fail to do that if timeout expires. 2. Local cache must work, I would assume you're doing something. Please prepare a t

RE: Questions on Client Reconnect and Client Cache

. How can extract a field values from BinaryObject. Do you have any sample code? Cheers, Mani From: Andrey Mashenkov [mailto:andrey.mashen...@gmail.com] Sent: Wednesday, January 11, 2017 5:18 PM To: user@ignite.apache.org Subject: Re: Questions on Client Reconnect and Client Cache Hi, 1. It looks

Re: Questions on Client Reconnect and Client Cache

Hi, 1. It looks like connection timeouts is too low. Do you see any errors in client logs? 2. You can have local cache on client. See CacheConfiguration#cacheMode option [1] 3. You can try recommendation given in [2] thread. [1] http://apacheignite.gridgain.org/docs/cache-modes#local-mode [2] h

RE: Questions on Client Reconnect and Client Cache

Can someone throw some light and help on below questions From: Lakshminarayanan, Manikandan (Cognizant) Sent: Wednesday, January 11, 2017 8:54 AM To: 'user@ignite.apache.org' Subject: Questions on Client Reconnect and Client Cache Hi, Appreciate if anyone can answers below questions 1.

Re: Questions on transitioning from GridGain to Ignite

On Mon, Sep 14, 2015 at 4:48 PM, wrote: > Good stuff. This should be in a FAQ > Good point! We should add an FAQ session and add some of these answers there. > > Sent from My Phone > > On Sep 14, 2015, at 17:24, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > Hi Vinay, > > My

Re: Questions on transitioning from GridGain to Ignite

Good stuff. This should be in a FAQ Sent from My Phone > On Sep 14, 2015, at 17:24, Valentin Kulichenko > wrote: > > Hi Vinay, > > My answers are inline... > > -Val > >> On Mon, Sep 14, 2015 at 11:31 AM, Vinay B, wrote: >> Hi, >> We've used Gridgain for a while now, mostly for job distrib

Re: Questions on transitioning from GridGain to Ignite

Hi Vinay, My answers are inline... -Val On Mon, Sep 14, 2015 at 11:31 AM, Vinay B, wrote: > Hi, > We've used Gridgain for a while now, mostly for job distribution. It's > been a while since we upgraded and as a result, we currently run the open > source edition of gridgain (V 6.2.1) > > Since