You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@ignite.apache.org by DK <ma...@gmail.com> on 2021/09/01 04:04:29 UTC

Re: ignite dump

Hi,

We are on version 2.8.0 only and all our caches are PARTITIONED
non-transactional caches.

Thanks & Regards,
Devakumar J

On Wed, Sep 1, 2021 at 5:38 AM Alexandr Shapkin <as...@apache.org> wrote:

> Hello!
>
> What Ignite version are you running?
>
> I can see that a similar issue has been fixed in 2.8
> https://issues.apache.org/jira/browse/IGNITE-11755
>
> On 31 Aug 2021, at 19:22, DK <ma...@gmail.com> wrote:
>
> Hi Team,
>
> Any pointers on this, please?
>
> Seems internally H2StatementCache contains a huge set of data that were
> queried over a period of time.
>
> Thanks & Regards,
> Devakumar J
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>
> On Sun, Aug 29, 2021 at 7:37 PM DK <ma...@gmail.com> wrote:
>
>> Hi,
>>
>> One of our server node's heap usage keeps increasing by uptime and
>> finally ends up in node restart.
>>
>> When i checked the heap dump detachedConns holds up huge memory around
>> 12GB out of 16GB and GC also couldn't reclaim. This happens randomly in one
>> of the server node only (3 nodes running).
>>
>> Is this related to releasing or closing the thin client connection?
>>
>> <image003.jpg>
>>
>>
>> Thanks & Regards,
>> Devakumar J
>>
>
>
> --
> Thanks & Regards
>
> Devakumar J
>
>
>

-- 
Thanks & Regards

Devakumar J

Re: ignite dump

Posted by DK <ma...@gmail.com>.

Hi,

Do we have any suggestions for this detached connection memory leak on
version 2.8.0?

Migrating the cluster to the latest version might help here?

Thanks & Regards,
Devakumar J


On Fri, Sep 3, 2021 at 1:08 AM DK <ma...@gmail.com> wrote:

> Any thoughts on this please?
>
> Note: This happens only on one node at a time after 2 to 3 days up time.
> Slowly builds up and ends up OOM. On multiple heap dumps detached
> connection only the 90% contributor.
>
> Current running version : 2.8.0
>
> Thanks & Regards,
> Devakumar J
>
> On Wed, 1 Sep 2021, 12:04 DK, <ma...@gmail.com> wrote:
>
>> Hi,
>>
>> We are on version 2.8.0 only and all our caches are PARTITIONED
>> non-transactional caches.
>>
>> Thanks & Regards,
>> Devakumar J
>>
>> On Wed, Sep 1, 2021 at 5:38 AM Alexandr Shapkin <as...@apache.org>
>> wrote:
>>
>>> Hello!
>>>
>>> What Ignite version are you running?
>>>
>>> I can see that a similar issue has been fixed in 2.8
>>> https://issues.apache.org/jira/browse/IGNITE-11755
>>>
>>> On 31 Aug 2021, at 19:22, DK <ma...@gmail.com> wrote:
>>>
>>> Hi Team,
>>>
>>> Any pointers on this, please?
>>>
>>> Seems internally H2StatementCache contains a huge set of data that were
>>> queried over a period of time.
>>>
>>> Thanks & Regards,
>>> Devakumar J
>>>
>>>
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.
>>> www.avast.com
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>>>
>>> On Sun, Aug 29, 2021 at 7:37 PM DK <ma...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> One of our server node's heap usage keeps increasing by uptime and
>>>> finally ends up in node restart.
>>>>
>>>> When i checked the heap dump detachedConns holds up huge memory around
>>>> 12GB out of 16GB and GC also couldn't reclaim. This happens randomly in one
>>>> of the server node only (3 nodes running).
>>>>
>>>> Is this related to releasing or closing the thin client connection?
>>>>
>>>> <image003.jpg>
>>>>
>>>>
>>>> Thanks & Regards,
>>>> Devakumar J
>>>>
>>>
>>>
>>> --
>>> Thanks & Regards
>>>
>>> Devakumar J
>>>
>>>
>>>
>>
>> --
>> Thanks & Regards
>>
>> Devakumar J
>>
>

-- 
Thanks & Regards

Devakumar J

Re: ignite dump

Posted by DK <ma...@gmail.com>.

Any thoughts on this please?

Note: This happens only on one node at a time after 2 to 3 days up time.
Slowly builds up and ends up OOM. On multiple heap dumps detached
connection only the 90% contributor.

Current running version : 2.8.0

Thanks & Regards,
Devakumar J

On Wed, 1 Sep 2021, 12:04 DK, <ma...@gmail.com> wrote:

> Hi,
>
> We are on version 2.8.0 only and all our caches are PARTITIONED
> non-transactional caches.
>
> Thanks & Regards,
> Devakumar J
>
> On Wed, Sep 1, 2021 at 5:38 AM Alexandr Shapkin <as...@apache.org>
> wrote:
>
>> Hello!
>>
>> What Ignite version are you running?
>>
>> I can see that a similar issue has been fixed in 2.8
>> https://issues.apache.org/jira/browse/IGNITE-11755
>>
>> On 31 Aug 2021, at 19:22, DK <ma...@gmail.com> wrote:
>>
>> Hi Team,
>>
>> Any pointers on this, please?
>>
>> Seems internally H2StatementCache contains a huge set of data that were
>> queried over a period of time.
>>
>> Thanks & Regards,
>> Devakumar J
>>
>>
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.
>> www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>>
>> On Sun, Aug 29, 2021 at 7:37 PM DK <ma...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> One of our server node's heap usage keeps increasing by uptime and
>>> finally ends up in node restart.
>>>
>>> When i checked the heap dump detachedConns holds up huge memory around
>>> 12GB out of 16GB and GC also couldn't reclaim. This happens randomly in one
>>> of the server node only (3 nodes running).
>>>
>>> Is this related to releasing or closing the thin client connection?
>>>
>>> <image003.jpg>
>>>
>>>
>>> Thanks & Regards,
>>> Devakumar J
>>>
>>
>>
>> --
>> Thanks & Regards
>>
>> Devakumar J
>>
>>
>>
>
> --
> Thanks & Regards
>
> Devakumar J
>