Re: Serious memory leak in DefaultOperatorStateBackend

2018-02-22 Thread Stefan Richter
;> >> Best, >> Stefan >> >>> Am 22.02.2018 um 11:10 schrieb Gyula Fóra <gyula.f...@gmail.com>: >>> >>> Hi all, >>> >>> We have discovered a fairly serious memory leak >>> in DefaultOperatorStateBackend, with broadc

Re: Serious memory leak in DefaultOperatorStateBackend

2018-02-22 Thread Stefan Richter
that was once declared, and >>> you might make a case that this is a feature to have for the future. Then >>> again, we need a general decision about lazy and eager state IMO. >>> >>> Best, >>> Stefan >>> >>>> Am 22.02.2018 um 11:10

Re: Serious memory leak in DefaultOperatorStateBackend

2018-02-22 Thread Gyula Fóra
zy and eager state IMO. > > Best, > Stefan > > > Am 22.02.2018 um 11:10 schrieb Gyula Fóra <gyula.f...@gmail.com>: > > > > Hi all, > > > > We have discovered a fairly serious memory leak > > in DefaultOperatorStateBackend, with broadcast (

Re: Serious memory leak in DefaultOperatorStateBackend

2018-02-22 Thread Stefan Richter
Am 22.02.2018 um 11:10 schrieb Gyula Fóra <gyula.f...@gmail.com>: > > Hi all, > > We have discovered a fairly serious memory leak > in DefaultOperatorStateBackend, with broadcast (union) list states. > > The problem seems to occur when a broadcast state name is changed,

Serious memory leak in DefaultOperatorStateBackend

2018-02-22 Thread Gyula Fóra
Hi all, We have discovered a fairly serious memory leak in DefaultOperatorStateBackend, with broadcast (union) list states. The problem seems to occur when a broadcast state name is changed, in order to drop some state (intentionally). Flink does not drop the "garbage" broad