NPE from the native persistence enable node

Hi All, As a simple native persistence node, if kill and reboot sometime NPE may thrown. From the code the really root cause should be the BPlusTree#doPut #putDown's Result is not Expected, But even in the CacheObjectBinaryProcessorImpl#metadata the holder != null should be checked

Re: Primary key bug

Hi, there might be a misunderstanding here of how Ignite SQL grid is implemented. Please note that Ignite does not use H2 as a storage. Ignite uses H2 only as a parser and planner. H2 hands a parsed and planned statement over to Ignite and then Ignite maps the statement to get/put/create

Node fails to recover

We are running an application on 2 servers with each running Ignite in a cluster. As the logs show below at some point the nodes had trouble communicating with each other. What I would really like to know is why one of the nodes seemed to recover and the other node did not. Is there something I

Re: Discovery node port range

Hello Ranjit! Running 20 nodes one one server is wasteful. I expect you would need to have ports range of 20 to run 20 nodes. This of course changes if each node runs under its own IP address (as it happens with containers). Also, client nodes don't need to bind to a fixed port. Any chance you

Re: Node fails to recover

Hello! 2018-01-04 22:16:12 INFO [ ] IgniteKernal:128 - FreeList [name=null, buckets=256, dataPages=5, reusePages=0] 2018-01-04 22:16:52 INFO [ ] TcpDiscoverySpi:128 - Finished serving remote node connection [rmtAddr=/192.168.202.110:55327, rmtPort=55327 As you may notice, there's a 30 seconds

Re: Discovery node port range

Ranjit, Embedded mode in Spark RDD will be deprecated in 2.4 which is about to be released. My recommendation would be to use standalone mode instead. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Node fails to recover

We didn’t have gc logging enabled. I can certainly enable it to for the future but that still leaves me wondering why Ignite didn’t “re-discover” the node once the garbage collection finished. Ralph > On Jan 17, 2018, at 10:35 AM, ilya.kasnacheev > wrote: > >

Re: Node fails to recover

It seems we did have Splunk collection garbage collection stats via JMX. I see no Full GCs happening at that time. There are minor GCs but they happen fairly frequently and don’t use much CPU time. Ralph > On Jan 17, 2018, at 10:52 AM, Ralph Goers wrote: > > We

Elixir/Erlang Apache Ignite Connector?

Hello, Just wanted to ask if there has been any work so far on an Elixir/Erlang Ignite connector as a strongly consistent in-memory database is something that would pair really nicely with the fault tolerance and high availability given from Erlang's OTP . It seems that it is plausible to

Primary key bug

Hi, Suppose we have following DDL: CREATE TABLE TEST ( org_id INT NOT NULL, drug_id INT NOT NULL, price DOUBLE NULL, qtty INT NULL, inter_id INT NULL, trade_id INT NULL, med_id INT NULL, medp_id INT NULL, avgprc DOUBLE NULL, avgprc_region DOUBLE NULL, region_id INTEGER NULL,

Re: 3rd Party Persistence and two phase commit

Hi! I just wanted to show an example, when Write-through mode is enabled and data is persisted by primary node - not transaction coordinator. Assume, we have transactional cache in cluster, near cache is disabled, node A is primary for key1, node B is neither primary nor backup for key1, and

Re: usage of Apache ignite as Key value DB

You have to run an Ignite instance to use it (you can embed it in your application), you can't just use the key value store on it's own, a LOCAL cache would be the closest to a Berkeley DB store. Docs at : https://apacheignite.readme.io/docs/data-grid Den 2018-01-17 kl. 11:05, skrev Rajesh

Re: ignite c++ client CacheEntryEventFilter has no effect!

Well, you can't run C++ jobs on Java node. You need to start some C++ nodes just as the exception message states. Best Regards, Igor On Wed, Jan 17, 2018 at 5:16 AM, Edward Wu wrote: > Yes, my server node is a plain Java node. > > > > -- > Sent from:

Re: Elixir/Erlang Apache Ignite Connector?

2.4 (soon to be released) will have a binary protocol that will provide limited API for various cache operations. Basically, you will be able to create a socket, connect to Ignite server and then run this operations. Here is the documentation (still work in progress, but gives a good idea about

Re: NPE from the native persistence enable node

Hi Aaron, Can you always reproduce the issue? Might be you have a reproducer for this issue? I created a ticket: https://issues.apache.org/jira/browse/IGNITE-7458 but I don't think that it will be fixed without a reproducer, so it will be great if you'll provide one, I'll attach it to the

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi Larry, I checked the code. The issue is specific to your test data. You have relatively large initial entries (4.7 Kbytes) with the same index length (it is a just String). Please note that the index can't fit into the single page (4K). The rest of entries during .get() (from Store) are

Re: Primary key bug

Hello, Alexey. Thank you for clarification. Is there any way to use in Ignite tables created directly in H2? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cannot insert data into table using JDBC

Hi Michael, The issue is almost fixed. The fix will be available as a part of Apache Ignite 2.4 release. On Tue, Dec 19, 2017 at 1:48 PM, Michael Jay <841519...@qq.com> wrote: > Hi,has it been solved or is it a bug? I just met with the same > problem.When I > set "streaming=false" ,it worked,

Integration with Hibernate 5.2.X for L2 Cache?

Is it possible to integrate Apache Ignite with Hibernate 5.2.X So that it can be used as an L2 cache? Or is the support only till 5.1.X? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Discovery node port range

Thanks Val. We are not using the RDD of ignite instead we are building the ignite cluster with in spark with custom code and use the key value store. We are using the static ip discovery while doing so. What we do is we read the data in avro from hadoop. Start the ignite node first in driver, and

Data lost when primary nodes down.

Hi, I have experiment create 2nodes server. (IP: 10.5.42.95 and 10.5.42.96) With this Ignite Configuration: IgniteConfiguration cfg = new IgniteConfiguration(); cfg.setIgniteInstanceName("BrandCluster"); TcpDiscoveryVmIpFinder ipFinder = new

Re: Purpose of cache in cache.query(Create Table ...) statement

Hi Andrey, This information will definitely be useful. Thank you. Regards, Shravya Nethula. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite loadCache performance issue

Denis Hi, Thx for the quick response. I have used at the older versions(1.3) so there was this "memoryMode" in there so I did not read the updated one. Thanks for the enlightenment. In order to manage the LRU functionality: Is there any way to disable off-heap(so the only memory would be on-heap

Re:Re: delete data error

This did not happen every time.When I run it several times,it will happen .And when it happened, then it will happened every time. This table is simple; I insert some data and when I finish the job,I will delete the data. Thanks. At 2018-01-17 20:20:34, "ilya.kasnacheev"

Ignite loadCache performance issue

I have a 3rd party Mysql table that will be cached partially by Ignite cluster. So on ignite, I have done this conf:

Re: 3rd Party Persistence and two phase commit

Denis, no, its valid case. you can set certain StoreFactory in cache configuration so that it create *different* instances of database(local) on different nodes. Then, my case will be applied. ср, 17 янв. 2018 г. в 14:45, Denis Mekhanikov : > Aleksey, > > You described

Re: delete data error

Hello Lucky! Does this happen every time when you try, or it is a one-time occurrence? Can you please share logs from your nodes and cache/table configurations? Ideally a small reproducer project. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: usage of Apache ignite as Key value DB

Hello Mikael, Thanks a ton for your response. I got descent understanding that for any operation I need to define cache and the cache item can be persisted. - Does it mean all CRUD operations would be performed via cache operations ? - Consider the case of berkley db where entities are stored

Re: usage of Apache ignite as Key value DB

There are a number of ways do to persistence for the cache, you can enable native persistence for a memory region and assign a cache to that region, all cache entries will be cached on disk och the ones you use most will be cached in RAM, another alternative is to add 3rd party class to enable

Re: Re: Nodes can not join the cluster after reboot

Hi Evgenii, What's more interesting If we reboot them in very shut time like one hour, from our monitor log we can find such like NODE_LEFT and NODE_JOIN events, every thing move smoothly . But if after several hours, problem below sure will happen if you try to reboot any node from

Re: 3rd Party Persistence and two phase commit

Hi, Aleksey, what is "local db"? I did not find anything on this in the documentation. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 3rd Party Persistence and two phase commit

Aleksey, You described an invalid case. Cache stores on all nodes for a single cache should point to the same database. Otherwise data won't be the same in different databases. Different nodes are not supposed to have personal local DBs. If you want nodes to store data on disk in distributed

Re: usage of Apache ignite as Key value DB

There are lots of examples not using SQL, have a look at: https://apacheignite.readme.io/docs/jcache Ignite implements the JCache API, just use get/put and so on. Den 2018-01-17 kl. 12:44, skrev Rajesh Kishore: This is much informative. Further I want to use key value apis instead of sql

Re: Primary key bug

Ignite's PRIMARY KEY does not map to H2 PRIMARY KEY constraint so you not seeing a primary key in H2 is OK. Ignite's PRIMARY KEY designates a binary object that Ignite SQL Grid will create for the underlying data grid cache key. Thus, in your example you will end up with two binary objects stored

Re: 3rd Party Persistence and two phase commit

Alexey, Of cause you can, but you will get an undefined behaviour in this case :) It is assumed, that all nodes are using the same database. Otherwise consistency is not guaranteed. Maybe it is worth to clarify this point in the documentation explicitly. Denis ср, 17 янв. 2018 г. в 15:10,

usage of Apache ignite as Key value DB

Hi, I am newbie to Apache Ignite. We are trying to explore Ignite as key value DB to be replaced with our existing Berkely DB in application. Currently, Bekley DB is embedded in the application and db container operations are performed using Berkely DB apis , similar functionalities we would

Re: 3rd Party Persistence and two phase commit

I meant local store = local db. ср, 17 янв. 2018 г. в 13:52, Andrey Nestrogaev : > Hi, > > Aleksey, what is "local db"? > I did not find anything on this in the documentation. > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- *Best

Re: 3rd Party Persistence and two phase commit

Local store = Apache Ignite Native Persistence? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: usage of Apache ignite as Key value DB

This is much informative. Further I want to use key value apis instead of sql apis which is only given in the example. The idea is that it should ease my migration process from Berkley dB based code where I am relying on key value apis to play with record in different dB containers, what is the

Re: Ignite loadCache performance issue

Hi Hasan! Try disabling *onheapCacheEnabled* and *evictionPolicy *properties from configuration. I think, it may have some performance impact. Also make sure, that your database is connected to Ignite nodes via high-throughput network, and is available from every data node. > Database has 3.2

Discovery node port range

Hi, We are using ignite key value store in spark embeded mode. As the resource is managed by yarn, sometimes when we request for 30 executor nodes, 20 nodes may get into one server. Which means we are starting 20 ignite server nodes in one server. Currently we have set the discovery port range as