Can we put some nodes on standby in Ignite?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Folks,
I am doing a putAll test with a simple Employee Pojo, stored as binary. The
cache is configured with,
Atomicity Mode = Transactional
Write Sync Mode = Full Sync
Backup Count - 1
Deployment config is, 2 large linux boxes,
Box 1 - 3 server nodes
Box 2 - 1 client node
500k load with batc
Update,
1. So there were 2 issues, there was old batch processing app that
periodically ran, that loaded lot of data in memory. Which i think was
causing some memory contention. So i shut that down for me tests.
2. Thread dumps showed some odd wait times between 2 get calls. I had
overtly complic
The production instance has issues with ignite heaping out, the solution we
attempted to implement was to set the default data region to have swap
enabled and also set a eviction policy on the server with a maxMemorySize
such that it was much less then the Xmx jvm memory size.
Testing locally with
what you are facing is, limitation of Cassandra. You can't query Cassandra
data if its not indexed or primary key. No matter what technology you top it
off with Cassandra, you can't query without index/PK, period. The
alternative is to Cache the entire table OR load it in cache and Cassandra
simult
> 12 processor Intel i7-8850 laptop which is running 100% so you must have
some good kit
I got those numbers on desktop i7-9700k. Laptops are still no match for
desktops (unfortunately).
> Does Java version have any bearing on performance?
Java version can certainly affect performance, but not in
Hi Andrey,
Do see the exception only in logs or your code experiences the
exception? It looks like the exception is treated as a failure but
actually it is not (as it is normal Ignite node stop). I would like to
understand how critical is it for users.
ср, 4 дек. 2019 г. в 19:25, Andrey Davydov :
