Questions tagged [ignite]

Apache Ignite™ is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale. It provides high-performance, in-memory computing capabilities for large data sets.

What is Apache Ignite for?

Apache Ignite provides a framework for in-memory computing operations on large scale data sets. It supports the following features:

  • Memory-centric, strongly consistent, distributed storage
  • Distributed SQL - supports ANSI SQL in-memory and on-disk transactional database
  • Distributed Key-Value - supports in-memory and on-disk key-value transactional data grid
  • In-Memory Compute grid - supports collocated computations and executor services
  • In-Memory Service grid - supports clusters and compute contracts
  • In-Memory Streaming - supports data streaming services like Kafka
  • In-Memory File system - supports the IGFS (Ignite filesystem)

Apache Ignite architecture combines the performance and scale of in-memory computing together with the disk durability and strong consistency in one system. When native persistence is turned on, Ignite functions as a memory-centric system-of-record, where most of the processing happens in memory on cached data, but the superset of data and indexes gets persisted to disk.

When persistence is turned off, Ignite functions as a memory-only store, in which case it can be treated as a Distributed Cache, In-Memory Database (IMDB) or In-Memory Data Grid (IMDG).

Resources

2356 questions
32
votes
7 answers

Apache Spark vs Apache Ignite

Currently I'm studying Apache spark and Apache ignite frameworks. Some principle differences between them are described in this article ignite vs spark But I realized that I still don't understand their purposes. I mean for which problems spark…
Normal
  • 1,179
  • 1
  • 15
  • 31
19
votes
4 answers

OData Exception The limit of '0' for Top query has been exceeded

I am using OData Web API for Version 4, when I try to query OData web Api using $top parameter, it return me following exception message. The query specified in the URI is not valid. The limit of '0' for Top query has been exceeded. The value from…
Abdul Qadir Memon
  • 808
  • 1
  • 9
  • 25
18
votes
4 answers

Possible Memory Leak in Ignite DataStreamer

I'm running Ignite in a Kubernetes cluster with persistence enabled. Each machine has a Java Heap of 24GB with 20GB devoted to durable memory with a memory limit of 110GB. My relevant JVM options are -XX:+AlwaysPreTouch -XX:+UseG1GC…
kellanburket
  • 9,514
  • 2
  • 35
  • 65
15
votes
2 answers

Hazelcast vs. Ignite benchmark

I am using data grids as my primary "database". I noticed a drastic difference between Hazelcast and Ignite query performance. I optimized my data grid usage by the proper custom serialization and indexes, but the difference is still noticeable IMO.…
Alex Rogachevsky
  • 484
  • 1
  • 3
  • 13
11
votes
2 answers

Apache Ignite hangs on startup

We use apache ignite v2.2 as hibernate 2nd level cache in grails application. We have 4 nodes cluster with 10G RAM each. The first node starts ok. But subsequent hangs. Sometimes 2nd sometimes 3rd or 4th. Also successful startups happen but very…
Dmitry S
  • 111
  • 3
9
votes
1 answer

Apache Ignite Availability Issue w/Custom CacheStoreAdapter

I'm doing a PoC using apache ignite. Here is the scenario I'm testing: Start a cluster of 3 nodes and a client. Call get key. I log on node that caches this key. Call get key. I verify it gets stored value. Do a loadCache(). All nodes report…
Carlos Bribiescas
  • 3,740
  • 8
  • 29
  • 61
9
votes
1 answer

Apache Ignite: How does the indexing work?

How does Apache Ignite's indexing work? I haven't found those technical details in the documentation. Is it using a B-tree? Where is the index stored? How is it stored? What performance (in Big-O notation) does the index provide after build in…
Make42
  • 9,528
  • 15
  • 60
  • 125
7
votes
0 answers

Apache ignite node won't join cluster if server nodes start simultaneously

We have a problem with ignite when we start two ignite server nodes at the exact same time. We are currently implementing our own discovery mechanism by extending TcpDiscoveryIpFinderAdapter. The first time the TcpDiscoveryIpFinderAdapter is called…
6
votes
2 answers

Ignite not discoverable in kubernetes cluster with TcpDiscoveryKubernetesIpFinder

I am trying to make ignite deployed in k8s discoverable using TcpDiscoveryKubernetesIpFinder. I have also used all the deployment configurations as recommended in apache ignite documentation to make it discoverable. Ignite version is v2.6. When I…
Kaps
  • 2,107
  • 21
  • 35
6
votes
2 answers

Cluster wide connection resources management in Ignite, using Hikari

How can I manage resources on ignite. Given the application i am developing, i have a few connections that i used to keep, (JDBC/SAP/others). I used to keep all the connections in a pool and manage them using HIKARI. Now given that now I can have…
frewper
  • 1,309
  • 6
  • 17
  • 41
6
votes
3 answers

Apache Ignite : How to list all tables and all Caches

Is there any way to list all tables present in a specific Cache and list all caches present on a Apache Ignite Server? ----------------------------------UPDATED-------------------------- Hi, I am running following code to know Cache name and list…
Sushil
  • 263
  • 3
  • 13
6
votes
1 answer

Apache Ignite vs. Apache Storm (in-depth)

Apache Ignite and Apache Storm are two rather different technologies in many aspects - especially since Storm has one very specific use-case, while Ignite has quite a large set of tools under one roof. As I understand it, the core of Ignite is its…
Make42
  • 9,528
  • 15
  • 60
  • 125
6
votes
1 answer

apache ignite query

I have created a cache using Automatic Persistence, connecting to Mysql database. 1 million rows are populated on startup into that node. Node is in PARTITIONED mode When I try retrieving data from that Cache using SQL queries, it always returns…
GGN
  • 85
  • 11
5
votes
2 answers

ignite won't start with spring-boot 2.0.5 - h2 property NESTED_JOINS doesn't exist

I am using Ignite 2.6 and It is running well as a standalone Java application but it is not working with spring boot. I am getting this error [20:44:18,520][SEVERE][exchange-worker-#37][GridDhtPartitionsExchangeFuture] Failed to reinitialize…
Sandeep Patel
  • 3,557
  • 2
  • 14
  • 29
5
votes
1 answer

Apache Ignite - (jvm-pause-detector-worker) Possible too long JVM pause:

After using apache ignite 2.6, I am getting this warning constantly on JBoss start and stop. Could you please help me to know whats wrong configuration will lead this warnings. Please let me know if you need any more details
Sanjay
  • 71
  • 1
  • 5
1
2 3
99 100