flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matteo Ferrario (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-7606) Memory leak on NestedMapsStateTable
Date Fri, 08 Sep 2017 15:58:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Matteo Ferrario updated FLINK-7606:
-----------------------------------
    Description: 
The NestedMapsStateTable grows up continuously without free the heap memory.
We created a simple job that processes a stream of messages and uses CEP to generate an outcome
message when a specific pattern is identified.
The messages coming from the stream are grouped by a key defined in a specific field of the
message.
We've also added the "within" clause (set as 5 minutes), indicating that two incoming messages
match the pattern only if they come in a certain time window.
What we've seen is that for every key present in the message, an NFA object is instantiated
in the NestedMapsStateTable and it is never deallocated.
Also the "within" clause didn't help: we've seen that if we send messages that don't match
the pattern, the memory grows up (I suppose that the state of NFA is updated) but it is not
cleaned also after the 5 minutes of time window defined in "within" clause.
If you need, I can provide more details about the job we've implemented and also the screenshots
about the memory leak.


  was:
The NestedMapsStateTable grows up continuously without free the heap memory.
We created a simple job that processes a stream of messages and uses CEP to generate an outcome
message when a specific pattern is identified.
The messages coming from the stream are grouped by a key defined in a specific field of the
message.
We've also added the "within" clause (set as 5 minutes), indicating that two incoming messages
match the pattern only if they come in a certain time window.
What we've seen is that for every key present in the message, an NFA object is instantiated
in the NestedMapsStateTable and it is never deallocated.
Also the "within" clause didn't help: we've seen that if we send messages that doesn't match
the pattern, the memory grows up (I suppose that the state of NFA is updated) but it is not
cleaned also after the 5 minutes of time window defined in "within" clause.
If you need, I can provide more details about the job we've implemented and also the screenshots
about the memory leak.



> Memory leak on NestedMapsStateTable
> -----------------------------------
>
>                 Key: FLINK-7606
>                 URL: https://issues.apache.org/jira/browse/FLINK-7606
>             Project: Flink
>          Issue Type: Bug
>          Components: CEP
>    Affects Versions: 1.3.1
>            Reporter: Matteo Ferrario
>
> The NestedMapsStateTable grows up continuously without free the heap memory.
> We created a simple job that processes a stream of messages and uses CEP to generate
an outcome message when a specific pattern is identified.
> The messages coming from the stream are grouped by a key defined in a specific field
of the message.
> We've also added the "within" clause (set as 5 minutes), indicating that two incoming
messages match the pattern only if they come in a certain time window.
> What we've seen is that for every key present in the message, an NFA object is instantiated
in the NestedMapsStateTable and it is never deallocated.
> Also the "within" clause didn't help: we've seen that if we send messages that don't
match the pattern, the memory grows up (I suppose that the state of NFA is updated) but it
is not cleaned also after the 5 minutes of time window defined in "within" clause.
> If you need, I can provide more details about the job we've implemented and also the
screenshots about the memory leak.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message