Hi did anyone have any possible suggestions for this? Thanks!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hmmm. Well, each node shares with other nodes (including clients) all
metadata (all CQ and etc...). Did you try to check this situation in a
thin client?
I think this is the normal amount of heap for a cluster like this.
Ilya Kazakov
пт, 13 нояб. 2020 г. в 22:15, ssansoy :
> Hi,
Hi, there are approx 6 server nodes, and only around 10 client nodes at the
moment (there will eventually be several hundred client nodes once this is
enabled in production if we can overcome these issues - and the cluster
metric messages which are causing over 1mb of allocations per sec).
Each
Hello!
Well, as I understand, you have a cluster with 50 caches and in each
client, you have this situation with 220 MB of metadata? But what
operations deploy your other clients? Maybe some continuous queries? Also
please tell me, how many nodes have your cluster?
--
Hi Andrew any thoughts on this? thanks!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
P.S. here's a screenshot of where this is coming from:
Note, some binary meta data seems to be about remote filters and
transformers that have been issued by other client apps connected to the
cluster (we do not want this stuff propagated to this client app either).
The rest of the binary meta
Hi,
Here is the client config:
">
">
"
Hello,
Let's start from the very beginning.
1) Could you please share the server and client config?
2) Java code of what you have in your client launcher application
I will try to investigate your case.
BR,
Andrew
10/28/2020 7:19 PM, ssansoy пишет:
Hi, could anyone please help understand
Hi, could anyone please help understand why the heap of a client app has such
large amounts of data pertaining to binary meta data?
Here it takes up 30mb but in our UAT environment we have approx 50 caches.
The binary meta data that gets added to the client's heap equats to around
220mb (even for
