How do you check that the second node doesn't keep any records? What your
verification method?
-
Denis
On Tue, Aug 18, 2020 at 3:17 AM itsmeravikiran.c
wrote:
> Our application running with 2 ignite node,.
> But data is available in one node, and not available in the second node.
> Our cache
>
> However as I read them again, I realised that it was anyway necessary to
> load the cache before executing the SELECT sql queries on top of a cache,
> now, would this hold true in the case of Spring Data as well ? (Very likely
> yes, but want to get the confirmation) If so, then are we
Hi Denis,
Thanks for taking time to reply and sharing those links. I can confirm to
you that I've read through them before and have been following them as
well.
However as I read them again, I realised that it was anyway necessary to
load the cache before executing the SELECT sql queries on top
Courtney,
The CacheBasedDataset.close() method below only destroys the helper cache
derived from
the original data, and used to train the model. It does not touch the
original data set.
@Override public void close() {
datasetCache.destroy(); // destroy the helper cache derived from the
Hi,
Please see here re baseline topology:
https://apacheignite.readme.io/docs/baseline-topology
The first activation is manual. You need to start as many nodes as
necessary, wait until
they have all initialized and are showing "cluster is inactive" in the
log then issue an
activation
Hi,
When all baseline nodes have joined the cluster it will self-activate.
After self-activation Ignite::isActive() will return true
https://ignite.apache.org/releases/latest/cppdoc/classignite_1_1Ignite.html#a5455dd6d8f8453073fbd32c60fe0c3af
When isActive() returns true it means, by
Hi,
As long as you see state=ACTIVE and servers=(number of nodes in your
config), the cluster has been formed and is active.
You can check by executing sql queries and putting data into it.
If you are having issues w/your existing cluster then send the logs from
all nodes on startup.
Let
Hi,
Going by the thread dump, the event api thread is holding a lock others
need to proceed,
while event storage thread is itself waiting for another condition to
proceed.
The method you are calling determined that you are not accessing ignite
from the same thread
that started it and is
Can you please share the entire source code? We also need to see how you're
checking that data is still there.
Evgenii
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Srikanta,
You forgot to share the configuration. Anyway, I think it's clear what you
are looking for.
Check this example showing how to configure CacheJdbcPojoStoreFactory
programmatically (click on the "Java" tab, by default the example shows the
XML version):
I'm trying to integrate a Spring data project (without JPA) with Ignite and
struggling to understand some basic traits. Would be very helpful if you
can share some insights on the issue I'm facing.
Currently the cache has been defined as below with the client node, this
config is not present in
Still seeing the same issue in 2.8.1 unfortunately.
I have a related question however.
Assuming I perform the following operation on node 1 of my 3 node cluster
(All caches use CacheRebalanceMode.SYNC,
CacheWriteSynchronizationMode.FULL_SYNC, CacheAtomicityMode.TRANSACTIONAL):
$ ./control.sh --baseline
Control utility [ver. 2.8.0#20200226-sha1:341b01df]
2020 Copyright(C) Apache Software Foundation
User:
Time: 2020-08-21T09:13:11.334
Command [BASELINE] started
Arguments: --baseline
Hello,
in order to provide "easy" multinode, we have set all of our caches to
REPLICATED and FULL_ASYNC. We get an improvment (Around 20%) with a second
node, but it is very clear that somehow the grid is waiting (95% cpu
utilization with 1 node, 75% with 2 nodes).
I understand that I should
Hello,
Our set up :
Server nodes : 3
Writer application : 1
A event storage spi that writes the cache_put events that have been
generated due to a dbeaver update into a ignite cache.
We restarted one of the servers yesterday during regular business hours and
noticed that the server was not
15 matches
Mail list logo
