1. No idea, have not seen any problems myself.
2. By default all entries are saved off heap (not disk, heap outside the
Java heap to avoid GC problems), you can configure it to use heap or off
heap memory as you want.
Mikael
Den 2018-06-30 kl. 22:43, skrev smovva:
I have started my
I have started my cluster and pushed some data into a cache. Cluster details
are provided below. The cache has persistence enabled.
I see a couple of issues with how data is cached.
1. Out of 8 nodes only 2 nodes have some entries. I ran all my keys through
Murmur3 hash and they seemed to be
Hi, kvenkatramtreddy!
Could you please provide a full log, not only stack trace with an exception?
On Sat, Jun 30, 2018 at 3:24 PM kvenkatramtreddy
wrote:
> Hi,
>
> Node stopped automatically after 48 hours uptime. Please find the logs
> below.
>
> I got 2 hosts and 3 Ignite nodes
>
>
> Host
You can start a transaction in the stream receiver to make it atomic.
On Fri, Jun 29, 2018, 1:02 PM breischl wrote:
> StreamTransformer does an invoke() pretty much exactly like what I'm doing,
> so that would not seem to change anything.
>
>
>
I am writing a program in Golang that connects to local Ignite clusters
through an ODBC driver package written in Go.
During development I began getting this error repeatedly:
I have looked into the source code of the golang ODBC driver I used, which
calls `SQLCloseCursor` promptly when my
Hi,
Node stopped automatically after 48 hours uptime. Please find the logs
below.
I got 2 hosts and 3 Ignite nodes
Host 1, Node 1
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=5582ed60, uptime=48:00:04.981]
^-- H/N/C [hosts=2, nodes=3, CPUs=4]
Hi
I am doing a POC on HDP 2.5 Cluster with Ignite as Hadoop Accelerator.
we have 3 node cluster each with 8 core and 60G RAM.
I was able to run hive on Tez query on a sample data set and finished in 32
sec.
The same query took 94 sec in Hive + IGFS + Ignite-MR.
I followed most of the
