Any feedback?
Hi Igniters! If you run Ignite in a cloud environment, the community needs
your story. It doesn’t have to be any sophisticated architecture. The “it
just works” variants are the most wanted by developers at the beginning of
deploying Apache Ignite in the cloud.
Please share your experience with
Hi,
Did you try to print data inside local listener. As I understand it,
initial query is only when cintinuous query starts, after that, local
listener and remote filter (if provided) play role.
On Tue, Sep 28, 2021, 00:02 Latha Masters wrote:
> Hi all,
>
>
>
> We’ve run into an issue when
Hi all,
We’ve run into an issue when using ContinuousQuery and hoping someone can help
provide some insight.
1 ContinuousQuery query = new ContinuousQuery<>();
2query.setLocalListener(listener);
3query.setInitialQuery(new ScanQuery<>());
4
I switched to Ignite 2.11, and started to obtain the following messages for one
of Ignite nodes (I have two nodes in total launched within Docker for our
testing infrastructure)
ignite_2|
[12:30:35,205][WARNING][tcp-disco-ip-finder-cleaner-#8-#175][TcpDiscoverySpi]
Failed to ping
Actually Query interface doesn't define close() method, but QueryCursor
does.
In your snippets you're using try-with-resource construction for SELECT
queries which is good, but when you run MERGE INTO query you would also
get an QueryCursor as a result of
igniteCacheService.getCache(ID,
I can’t say whether it’s the problem but I can say that’s really not going to
help. The default for most of these thread pools is going to be 12 (the number
of cores). Each thread is going to have its own working set, stack, etc. If all
the threads are thrashing, it’s not going to be able to
out of curiosity, how does these poolSizes affects heap size usages? we are
using physical machines with total of 12 cores. we did have these sizes before
upgrade from 2.7.6 and had no heap issues at all. we do have same data size
Hi,
It looks like baseline topology auto-adjustment is in process. Did you
checked cluster state later?
Also to track auto-adjustment events please check your logs for messages
like:
Baseline auto-adjust will be executed right now ...
Baseline auto-adjust will be executed in ...
Baseline
