Hello!
The second one is clearly also a bug. You can sidestep it by setting log
level to INFO.
Regards,
--
Ilya Kasnacheev
пн, 1 февр. 2021 г. в 22:44, Paolo Bazzi :
> Hi all,
>
> I've getting a series of logger warnings when I startup an Ignite instance.
> I could get rid of most of them by
https://cwiki.apache.org/confluence/display/IGNITE/%28Partition+Map%29+Exchange+-+under+the+hood
As per the documentation, if we are using apache ignite thick client 2.8 and
above, it should not trigger PME in server nodes. But it does not look like
it is skipping, I see below logs
INFO
Hello Ivan,
Well, EVT_CACHE_REBALANCE_PART_LOADED is triggered when the corresponding
partition is fully rebalanced and moved into the "OWNING" state,
and so, invoking Affinity#isPrimaryOrBackup(ignite.cluster().localNode(),
key) on this node should return "true".
to be more precise, this
Hi,
These are legacy warnings that could be ignored.
The are coming because of this code:
Hi all,
I've getting a series of logger warnings when I startup an Ignite instance.
I could get rid of most of them by changing my configuration (e.g. setting a
default non-logging CheckpointSpi or non-logging CollisionSpi
implementation) or by adding VM parameters (avoid Java9 module access
Hi,
You can use any of your caches to perform the query, or alternatively
create a new one like so:
ignite.getOrCreateCache("MY_TEST_CACHE").query(new SqlFieldsQuery("SELECT
* FROM SYS.NODES")).getAll()
Thanks, Alex
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
You can use SqlFieldsQuery to return data from system views (of the node on
which you invoke the SqlFieldsQuery). Please note that cache SYS does not
exist initially, nor any other caches with schema SYS. You may use any
existing cache instead.
You can run any code on the server nodes
Hello!
I recommend collecting thread dumps from server nodes when you see this
issue, especially by simulating many new client connections at once. Then
you can triage why this would happen.
Regards,
--
Ilya Kasnacheev
пн, 1 февр. 2021 г. в 10:18, Naveen :
> Not really used with any earlier
What is the size of the cluster?
On Mon, Feb 1, 2021 at 10:18 AM Naveen wrote:
> Not really used with any earlier versions, most of the time have used thick
> clients only.
> to begin with, it takes around 100 to 200 ms, slowly it goes to 1 sec and
> keep increasing.
>
>
>
>
>
> --
> Sent from:
Hello!
You are running SqlFieldsQuery on client node here, but you are checking
metric on server. Metrics are per-node local.
Regards,
--
Ilya Kasnacheev
пн, 1 февр. 2021 г. в 14:16, 38797715 <38797...@qq.com>:
> It's amazing, let's simplify the problem.
>
> 1.Start a node using the
Hello!
I would expect that it includes current utilization of heap and off-heap as
well as all other memory occupied by the JVM and IIS internals.
Regards,
--
Ilya Kasnacheev
пн, 1 февр. 2021 г. в 16:31, Charlin S :
> Hi,
>
> i'm having doubts on the total memory utilisation of w3p
Hi,
i'm having doubts on the total memory utilisation of w3p processor, which
is connected with two ignites grid as client nodes.
Currently it occupies 801.0MB.
My question is, 801.0 includes JVM heap memory if not where can i find JVM
heap utilization.
[image: image.png]
JVM option :
It's amazing, let's simplify the problem.
1.Start a node using the following configuration file
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.springframework.org/schema/beans
Hello!
Please consult with
https://ignite.apache.org/docs/latest/persistence/persistence-tuning#enabling-direct-io
As far as my understanding goes, you only need to add ignite-direct-io
directory to your libs. You do not need to configure anything. Please
experiment with Ignite C++ to find out
can we enable this option via xml?
is there a C++ API to enable/disable it?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
loadCache usually will only affect local partitions. There are no
guarantees that entries loaded from cache store are in sync. Entries
touched via Ignite APIs should be in sync. loadCache will not overwrite
existing data.
Regards,
--
Ilya Kasnacheev
пн, 1 февр. 2021 г. в 07:29, eerick
Hello!
It will not affect RAM usage by Ignite (but may decrease the amount of disk
buffers held by the OS). It may affect performance, and is written in
expectation to improve it.
Regards,
--
Ilya Kasnacheev
пн, 1 февр. 2021 г. в 13:02, rakshita04 :
> Thanks for the response.
> One more
Thanks for the response.
One more question-
if we enable "Enabling Direct I/O", is there any performance implication or
side effect?
will it save some RAM for us? considering it will direct read/write to disk?
Also can we enable it using xml option?
regards,
Rakshita Chaudhary
--
Sent from:
Hello!
Please check out the following docs page:
https://ignite.apache.org/docs/latest/memory-architecture
https://ignite.apache.org/docs/latest/memory-configuration/data-regions
Regards,
--
Ilya Kasnacheev
пн, 1 февр. 2021 г. в 11:34, rakshita04 :
> Hi,
>
> We are using apache-ignite on
Hello!
No, this is not correct.
Even if table is created through JDBC, nodes will collect metrics for its
SqlFieldsQuery's:
| cache.SQL_PUBLIC_PERSON.QueryCompleted | 2 |
|
| cache.SQL_PUBLIC_PERSON.QueryExecuted | 2
Hi,
We are using apache-ignite on embedded environment where we have RAM
limitation.
We are using persistence feature and using hard disk for it.
but as we insert keys in our db we see free RAM decreasing.
if we are using persistence still some data goes to RAM?
Apart from what we configure for
21 matches
Mail list logo
