aml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
>
> --
> Rishi Yagnik
>
> --
> View this message in context: Re: Ignite 1.6.0 suspected memory leak from
> DynamicCacheDescriptor
> <http://apache-
Hello Val..
Thanks, will try out and let you know ...
On Fri, Jul 7, 2017 at 12:25 PM, vkulichenko [via Apache Ignite Users] <
ml+s70518n1449...@n6.nabble.com> wrote:
> Hi Rishi,
>
> ignite.cluster().nodes() will give the list of nodes and full information
> about topology. Will this work for
Hi Rishi,
ignite.cluster().nodes() will give the list of nodes and full information
about topology. Will this work for you?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p14492.html
Hello Val,
Do you have any example on it ? would like to see how can we leverage that
piece of code for monitoring ?
Thanks for all your help..
On Thu, Jul 6, 2017 at 5:46 PM, vkulichenko [via Apache Ignite Users] <
ml+s70518n14430...@n6.nabble.com> wrote:
> Tom,
>
> It sounds like these jobs
Tom,
It sounds like these jobs are triggered pretty frequently. So why not create
a small application that will create an embedded client once and also have
an internal timer or cron based scheduler to execute jobs periodically. You
can do the topology check within this application as well,
Hi Val,
sorry for this late reply.
yes, we have a client node constantly joining and leaving topology.
does the new versions of Ignite have improvement on this issue?
the reason client node constantly joining and leaving topology is twofold:
1. we used a visor cli called by cron job to check
Hi,
It looks like there is client node constantly joining and leaving topology.
What is the reason for this?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p12894.html
Sent from the
reproduced the OOME, the heap dump here
https://drive.google.com/drive/folders/0BwY2dxDlRYhBMEhmckpWeHg1bjg?usp=sharing
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p12529.html
Sent from the
Thanks for your effort in patiently and promptly replies, we are trying to
reproduce the issue, will keep you posted.
Tom
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p9669.html
Sent from
Tom,
I am not sure there is a memory leak at all because I have no idea what you
code is doing. I'm just guessing here, but without success so far. Looking
through code didn't give anything useful as well, it looks correct. So if
you need my help further, please provide something that will help
How about this OOME?
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-GridDhtPartitionMap2-td9504.html
We found it on another client node in the same cluster, however it seems to
exhibit a different pattern of memory leak.
- Tom
--
View this message in
Well, I need to reproduce it to investigate further. I tried to dig up in the
code, but do not see anything that can lead to memory leak, and even to so
many instances of CacheConfiguration in this map. Is it possible for you to
create a reproducer for this? That would be really helpful.
-Val
> Are you sure that all of them are in this map? What is the size of rmtCfgs
map?
This map contains about 1/6 of the total CacheConfigurations, the size of
rmtCfg map is 227,306,792:
Class Name
| Shallow Heap
Are you sure that all of them are in this map? What is the size of rmtCfgs
map?
Actually this map can be non-empty only on a node which is not fully started
yet. Basically, when a new node joins a topology, it collects the
configuration from all nodes for validation check, does the check and
ic, so the embedded instance is the IgniteKernal object which implement the
Ignite interface.
> So these are instances are not really used by Ignite, but are saved
> somewhere, most likely in your code. Can you use heap dump to trace it?
Yes, there are a whole lot of CacheConfiguration objects
Embedded instance is the one started with Ignition.start().
I look at the histogram and see that there are more than 88000 instances of
CacheConfiguration in each application, while the number of caches is only
6. So these are instances are not really used by Ignite, but are saved
somewhere, most
What do you mean by "embedded instances"? if it's org.apache.ignite.Ignite
object then we have two, one for each .war application deployed.
And what do you mean by "not properly stopped and / or disconnected"? The
application call org.apache.ignite.Ignite.close() only when Tomcat shutdown.
What
and we have the iptables open on ports 3-5, wondering if it's related
to the symtom.
because it shows `cachesOnDisconnect
org.apache.ignite.internal.processors.cache.GridCacheProcessor` holds the
objects.
--
View this message in context:
> How many caches do you have?
there are only 2 caches
> Any idea why you have so many CacheConfiguration objects? Who holds
> references to them?
the shortest paths to the accumulation point for java.util.HashMap @
0x8423c790 shows who holds the references, as you can see below, it's an
How many caches do you have?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p9517.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Any idea why you have so many CacheConfiguration objects? Who holds
references to them?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p9515.html
Sent from the Apache Ignite Users
Hi Val, sorry I m afraid I cannot provide the heap dump because it might
contain some sensitive data.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p9507.html
Sent from the Apache Ignite
Thx Val for your reply, let me check if I can give you the .hprof file later.
This is the dominator tree showing all 23,850 items from
java.util.HashMap$Node[65535] @ 0xcd657f20, It's too many of them so I just
expand some of them and they are all holding CacheConfiguration objects.
CacheConfiguration objects consume 0% though, so there should be something
else. Is there any understanding what is actually consuming the space? Can
you upload the whole .hprof file somewhere?
-Val
--
View this message in context:
We have 2 machines (M1, M2)
In M1 running a Ignite server (I1) and a Tomcat server (T1), which hosted 2
Ignite clients (C1a, C1b),
similarly in M2 running a Ignite server (I2) and a Tomcat server (T2), which
hosted 2 Ignite clients (C2a, C2b).
OutOfMemoryError were found in both T1 and T2
25 matches
Mail list logo
