Hi guys,
I use JDBC client driver to create a table,like:
stmt.executeUpdate("CREATE TABLE IF NOT EXISTS person ( id int,orgId LONG,
name VARCHAR, salary LONG ,PRIMARY KEY (id)) WITH \"backups=1,
affinityKey=id\"");
Could I use SqlQuery API to query this cache? I tried this way but does not
Hi,
I have a spring boot application which runs ignite in embedded mode; the
application will run in my laptop and will have a single node only. What is
the best way to set this up?
Thanks
Sumanta
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
This should be super simple...
Started 2 nodes from the command line, they saw each other and now show
servers=2. Completely default configuration.
Installed the ODBC Driver and set up a DSN.
Started a C# app to open a connection and issue a create table sql
statement.
It fails with "Failed to
Hi,
I have an Ignite cluster with 10nodes. Here is the snippet from one of the
ignite server log.
>>> [13:03:54] Topology snapshot [ver=11, servers=10, clients=0, CPUs=352,
>>> heap=1000.0GB]
Now I created a cache with mode PARTITIONED and loaded some data into the
cache without
Hi everyone. I want to use "QueryEntity Based Configuration."
my model (i.e. valueType) is wrapedMap -
*class Model {
Map data;
Object get(String key){}
}*
I want that my "indexes" to be my "data" 's some keys. Can I use it for my
case? And how?
Will following config
Hi Ranjeev,
Also it is possible cache.get() return value is deserialized only once on
client side,
but when you use EntryProcessor, entry is deserialized before EP invoke,
then request result serialized before being sent back to client and then
deserialized on client.
Try to use get() for simple
That worked, is it a reentry issue?
Should be flagged as a bug?
Because reconnecting a continuous query from a disconnect event should be
standard right?
On 14 Nov 2017 6:35 p.m., "ezhuravlev" wrote:
> Try to start a new thread and access cache from it.
>
> Evgenii
>
>
IGNITE_HOME = null is usually no problem. What and how should I set? I use
Ignite in embedded mode...
Lukas Lentner, B. Sc.
St.-Cajetan-Straße 13
81669 München
Deutschland
Fon: +49 / 89 / 44 38 61 27
Mobile: +49 / 176 / 24 77 09 22
E-Mail: kont...@lukaslentner.de
Website:
Hello!
My recommendation here is to always leave some extra RAM and heap so that a
hot spot won't cause OOM. Maybe use less RAM-intensive algorithms.
Without stack traces and logs it's hard to say more, but OOM may not be a
recoverable error with Ignite.
Regards,
--
Ilya Kasnacheev
Hello Ray,
Have you tried to rewrite ingestion using cache API, DML or better yet
DataStreamer? Because it's non-trivial to reason about problem when extra
Spark layer is added.
Why do you have such non-trivial amount of fields (and indices) in cache key
object? Maybe try synthetic keys?
Try to start a new thread and access cache from it.
Evgenii
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Lukas, what about GC pauses in your cluster? What is the max?
What are network specs?
Also, do you use bare metal servers or virtual machines?
--Yakov
Hi Lukas,
Several "Finished serving remote node connection" shows that the node was
cut off the cluster (some socket issues)
Please enable DEBUG level for logs to see more details about possible
reasons (socket errors, malformed messages, etc)
Thanks,
Alexey
--
Sent from:
Hi Lukas,
It seems that a new node is just misconfigured and it can't correctly assign
partitions by Affinity Function.
Please set a valid IGNITE_HOME and verify that Affinity Function [1] matches
the cluster config
2017-11-11 06:10:34:973 + [main] INFO
14 matches
Mail list logo