RE: Apache Ignite & unixODBC and truncating text

Yes, and maybe will difficult to find solution on this error: https://bugzilla.xamarin.com/show_bug.cgi?id=37368 If will be nessesery I can try to prepare VS 2017 and compile it one more time... So, here is my simple script: setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);

Re: Date type field in select query is returning wrong value when Time zones of Ignite Client and Server are different

Hi Thanks for your response. Temporary work-around that I found was to set Ignite Servers JVM timezone and Ignite Client JVM Timezone to a common value using _JAVA_OPTIONS="-Duser.timezone=xxx" -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Using native persistence question

Silly question, if I have native persistence on and a node goes down for some time, say I have a partitioned cache with backups or a replicated cache, so that cache lives on in the other nodes, will the old node handle this correct when it comes back online again and throw away any old cache en

Apache Ignite best practice

Hi, Sorry for bad english. Need council on configuring Ignite, which is used as a SQL Grid. The task is rather simple - to store in realtime information about connections to the services and to be able to quickly search for it. Tell me please in what direction to diagnose and what are the variants

Re: dotnet thin client - multiple hosts?

Hi Colin, There is a ticket for this improvement. https://issues.apache.org/jira/browse/IGNITE-7282 Thank you, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to access ignite web console in AWS Ec2

Hello! If we're talking about the same thing, you can specify non-random port when running via ./ignite-web-console-linux --server:port 3000 (and open 3000 in firewall rule, you can also use any other different port) Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: NullPointerException in GridDhtPartitionDemander

Hello! I think you should seek ways to avoid creating client for each request. This is slow and dangerous since clients are members of topology and join process is non-trivial. You can have your rebalancing postponed by joining clients, for example. Regards, -- Sent from: http://apache-ignite-

Re: Using native persistence question

Hello, Mikael. Yes, "old node" should handle this situation correctly. You can check these links for more information: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-DistributedRecovery https://cwiki.apache.org/conflue

Re: off heap memory usage

Thanks for this. The referenced post mentions AllocatedPages rather than PhysicalPages. Which would you advise is the most appropriate for this application? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

xml and java configuration

Hi! Is it possible to mix Ignite configuration so I can have the basic configuration in my xml files and add some extra configuration from the Java application or do I have to use one or the other ? Mikael

Re: xml and java configuration

Hello, Mikael. Yes, it possible. You can load IgniteConfiguration throw Ignition.loadSpringBean [1] method. After it you can modify result if you want. Please, look at example: ``` final String cfg = "modules/yardstick/config/ignite-localhost- config.xml"; IgniteConfiguration nodeCfg = Ignitio

RE: Why does Ignite de-allocate memory regions ONLY during shutdown?

Hi John, Could you please re-phrase you question. What issue are you trying to solve? Probably, you should address your question directly to dev-list. Anyway, you can read about memory region architecture at [1] and [2]. Hope it helps. [1] https://apacheignite.readme.io/docs/memory-architectu

Re: Apache Ignite & unixODBC and truncating text

I've checked the scenario with the pure ODBC and it seems like the issue is not with the ODBC driver, as it lets you insert and select varchar data of any length, but with the tools, which truncate any data that user passes to column size, which set to 64 by default for variable length columns. I'

Re: Date type field in select query is returning wrong value when Time zones of Ignite Client and Server are different

Hello! I have confirmed that the problem exists, raised https://issues.apache.org/jira/browse/IGNITE-7363 Regards, -- Ilya Kasnacheev 2018-01-09 11:09 GMT+03:00 kotamrajuyashasvi : > Hi > > Thanks for your response. > > Temporary work-around that I found was to set Ignite Servers JVM timezone

Re: Re: Some question regards the DataStorageConfiguration when used in multiple data regions.

Aaron, Could you provide steps to reproduce the issue? Can this issue be reproduced when there is only one cache and one data region? Or when all caches are in a single data region. Also please clarify, how you modify caches and what queried do you execute? Denis вт, 2 янв. 2018 г. в 16:26, aa.

ClassCastException using cache and continuous query

Hello, I'm trying to upgrade Ignite from 1.7.0 to 2.3.0 and I'm getting this exception: java.lang.ClassCastException: com.company.datastore.ignite.model.IgniteFetchItem cannot be cast to com.company.datastore.ignite.model.IgniteFetchItem. No other changes were made, just the ignite dependency up

Re: SQL and backing cache question

Hi Naveen, > Does it mean we do not need to develop these classes OR > just dont need to deployed on server node's classpath. In case of using BinaryObject you do not need to create the key and value types. > How do I resolve this issue?? It seems that "CITY_DETAILS_BINARY" cache is not created

Re: Best practice Apache Ignite Data-Grid with Java EE application

Hi Val, thanks for the fast feedback ;) Best Regards, Franz vkulichenko schrieb am Di., 9. Jan. 2018 um 00:27 Uhr: > Hi Franz, > > Running an Ignite client node embedded into an application would be the > best > way to interact with the cluster. You will have all the APIs available and > also

Re: JDBC Thin Client with Transactions

Hi, The transactional SQL should be rolled out in Q2 this year. "java.sql.SQLFeatureNotSupportedException: Transactions are not supported” exception is caused by this missing piece, yes. You can’t execute INSERTS, UPDATES, DELETES, MERGE queries inside of Ignite transactions. However, you can

Re: Ignite Memory Storage Options

1. Have a data region with the Ignite persistence enabled and set a little bit of RAM for that region. The more RAM you dedicate for the region the faster your queries will be. 2. Define two data regions - the first won’t have the persistence enabled and the second will be defined as in 1. — D

Re: Transaction operations using the Ignite Thin Client Protocol

+ dev list Igniters, Pavel, I think we need to bring support for key-value transactions to one of the future versions. As far as I understand, a server node, a thin client will be connected to, will be the transaction coordinator and the client will simply offloading everything to it. What do

Re: Ignite work directory usage?

It needs to be fixed if the users constantly bump into this issue. However, I guess it’s not a matter of urgency now. — Denis > On Jan 8, 2018, at 6:30 AM, ilya.kasnacheev wrote: > > Hello Denis! > > There seems to be cases where matching workDir for different nodes > (including client nodes)

Re: JDBC thin client load balancing and failover support

It should be supported for 2.4. Anyway, this should not be a showstopper because this logic can be embedded into an application. If the application loses a connection to one IP address it can re-connect to the cluster via a different one. — Denis > On Jan 8, 2018, at 11:37 PM, rizal123 wrote:

Creating multiple Ignite grids on same machine

I’m trying out a proposal for an Ignite based topology that will have two grids. I am using Ignite.Net 2.3. One grid is responsible for processing inbound events, the second is responsible for servicing read requests against an immutable query-efficient projection of the data held in the first g

IgniteOutOfMemoryException when using putAll instead of put

For testing I created a data region of 21 MB DataRegionConfiguration = (new DataRegionConfiguration) .setName("testRegion") .setInitialSize(21 * 1024 * 1024) .setMaxSize(21 * 1024 * 1024) .setPersistenceEnabled(false) .setPageEvictionMode(DataPageEvictionMode.RA

Re: JDBC thin client load balancing and failover support

Yes it is. I can do put some logic to re-route to another address if primary node is down. But I think this is not solution.. Btw, this is another question for me. How about the load-balancer? Currently i have 3 VM (3 ip address). Which will be used as 3 cluster ignite. Behind that, i have Oracle

Re: JDBC thin client load balancing and failover support

> I`m using JDBC Thin, at my datasource I put only one IP address. > How come the other cluster will get the data? If i only invoke into one Ip > address. The node the driver connects to forwards queries to the rest of cluster nodes. It’s just a gateway for the driver. The goal of the ticket is

Migrating from Oracle to Apache Ignite.

Hi, I have a project/poc, about migrating database oracle into in memory apache ignite. First of all, this is my topology. in case image not showing: https://ibb.co/cbi5cR I have done this thing: 1. Create node s

How possible we can get the reason why the ignite shut down itself?

Hi All, We have cache node(only one node not cluster), with native persistence enable, update of this cache will be frequently. But not so frequent, we use this cache to aggregate the open close and high low price. now only have about <1000 updates per seconds. we use the cache#invoke to up

Re: Connection problem between client and server

Hi Denis, Does Ignite dev team give any feedback for this? Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/