Hello!
What is the version of Ignite on your cluster? Please make sure that driver
version exactly matches cluster nodes' version.
Regards,
--
Ilya Kasnacheev
пн, 8 апр. 2019 г. в 16:17, shivakumar :
> Hi all,
> I'am getting this below exception while doing batch insert.
>
> *WARNING: Excepti
Hello!
I think they keep data on heap in hopes of further use which will not
happen.
Please make sure you close them explicitly.
Regards,
--
Ilya Kasnacheev
пн, 8 апр. 2019 г. в 20:49, kellan :
> But are they actually affecting anything? Like are my DataStreamers
> dropping
> data, or is it
Hello!
Have you tried it? Does it work?
Regards,
--
Ilya Kasnacheev
пн, 8 апр. 2019 г. в 14:31, kresimir.horvat :
> Hi,
>
> thank you for your replay. I will try solution you suggested.
>
> If I want to avoid modifications and commits of changes in docker container
> I will have to do the fol
HI Ilya Kasnacheev,
The cluster is deployed with 2.7.0 version of ignite.
if i use 2.6.0 version of jar then i'am not getting any exception but if i
use 2.7.0 version of jar then i'am getting this exception.
regards,
shiva
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
I thin you should not do conn.commit();
Instead you should do SET STREAMING OFF;
COMMIT; is a statement that's not INSERT, which is probably causing the
error.
Regards,
--
Ilya Kasnacheev
вт, 9 апр. 2019 г. в 15:23, shivakumar :
> HI Ilya Kasnacheev,
>
> The cluster is deployed with 2
I'm new with Ignite and I'm trying to test data quality and availability of
Ignite cluster.
I use the below xml configuration for setting cluster,
I want to setup a basic Ignite cluster to start playing around with. What I
am trying to achieve is setup 3 VMs in Azure that will make up the Ignite
Cluster. On the back-end I want to use either SQL (for my POC) which I will
later replace with Cassandra (for POC again - I think SQL would be easier
1) How does Ignite implement this Cache#boolean replace(K key, V oldValue, V
newValue) function?JSR107 tells that it's equivalent to: if
(cache.containsKey(key) && *equals*(cache.get(key), oldValue)) {
cache.put(key, newValue); return true; } else { return false; }but I assume
this is just logica
Hi,
solution you have suggested does work. So setting JMX_MON= before calling
control.sh will run script without exception.
Starting docker with NOJMX=1 and NOJMXI=1 doesn't. I found that
/docker/apache-ignite/run.sh script will start ignite.sh without -nojmx all
the time. If ignite.sh is started
Hello!
I suggest filing a ticket against Apache Ignite JIRA about that problem.
Regards,
--
Ilya Kasnacheev
вт, 9 апр. 2019 г. в 18:18, kresimir.horvat :
> Hi,
>
> solution you have suggested does work. So setting JMX_MON= before calling
> control.sh will run script without exception.
> Start
hi All,
I just encountered a situation in my k8s cluster where I'm running a 3 node
ignite setup, with 2 client nodes. The server nodes have 8GB of off-heap
per node, 8GB JVM (with g1gc) and 4GB of OS memory without persistence. I'm
using Ignite 2.7.
One of the ignite nodes got killed due to som
11 matches
Mail list logo