Re: Flink TaskManager memory configuration failed

2022-06-22 Thread Xintong Song
512mb is just too small for a TaskManager. You would need to either increase it, or decrease the other memory components (which currently use default values). The 64mb Total Flink Memory comes from the 512mb Total Process Memory minus 192mb minimum JVM Overhead and 256mb default JVM Metaspace. Be

Re: Flink TaskManager memory configuration failed

2022-06-22 Thread yu'an huang
Hi John, May I know what is your Flink version you are trying? On Thu, 23 Jun 2022 at 3:43 AM, John Tipper wrote: > Hi all, > > I'm wanting to run quite a number of PyFlink jobs on Kubernetes, where the > amount of state and number of events being processed is small and therefore > I'd like t

Flink TaskManager memory configuration failed

2022-06-22 Thread John Tipper
Hi all, I'm wanting to run quite a number of PyFlink jobs on Kubernetes, where the amount of state and number of events being processed is small and therefore I'd like to use as little memory in my clusters as possible so I can bin pack most efficiently. I'm running a Flink cluster per job. I'm

Re: Flink TaskManager Memory

2019-12-26 Thread vino yang
Hi Tim, Reference a blog comes from Ververica: "When you choose RocksDB as your state backend, your state lives as a serialized byte-string in either the off-heap memory or the local disk." It also contains many tune config options you can consider.[1] Best, Vino [1]: https://www.ververica.com

Flink TaskManager Memory

2019-12-26 Thread Timothy Victor
For Streaming Jobs that use RocksDB my understanding is that state is allocated off-year via RocksDB. If this is true then does it still make sense to leave 70% (default taskmanager.memory.fraction) of the heap for Flink Manged memory given that it is likely not being used for state?Or am I mi

Re: questions about yarn container(taskmanager)memory allocation

2019-05-20 Thread Xintong Song
Hi XiangWei, Thank you for the inputs. I agree with you that it is possible that containers may use extra memory in 1.8. As for native memory, it is memory used by JVM and other processes outside JVM. So it's not limited by MaxDirectMemorySize. The community is working on a refactoring plan about

questions about yarn container(taskmanager)memory allocation

2019-05-20 Thread XiangWei Huang
Hi all, Currently i am running my flink application in yarn session mode and using below commnad : *bin/yarn-session.sh -d -s 3 -jm 1024 -tm 4096* when taskmanager complete to started,i found the container launching command is : * bin/java -Xms2765m -Xmx2765m -XX:MaxDirectMemorySize=1331m .

Re: taskmanager memory leak

2016-07-21 Thread 김동일
skManager? >> - If you are running a job, do you use the RocksDB state backend, of the >> FileSystem state backend? >> - Does it grow infinitely, or simply up a certain point and then goes down >> again? >> >> Greetings, >> Stephan >> >> >

Re: taskmanager memory leak

2016-07-21 Thread Stephan Ewen
>>> even on an idle TaskManager? >>> - If you are running a job, do you use the RocksDB state backend, of >>> the FileSystem state backend? >>> - Does it grow infinitely, or simply up a certain point and then goes >>> down again? >>> >>

Re: taskmanager memory leak

2016-07-21 Thread 김동일
p a certain point and then goes down > again? > > Greetings, > Stephan > > > On Wed, Jul 20, 2016 at 5:58 PM, 김동일 <mailto:kim.s...@gmail.com>> wrote: > oh. my flink version is 1.0.3. > > > -- Forwarded message -- > From: 김동일 mailto:kim.s.

Re: taskmanager memory leak

2016-07-21 Thread Stephan Ewen
e backend, of >> the FileSystem state backend? >> - Does it grow infinitely, or simply up a certain point and then goes >> down again? >> >> Greetings, >> Stephan >> >> >> On Wed, Jul 20, 2016 at 5:58 PM, 김동일 wrote: >> >>> oh. my

Re: taskmanager memory leak

2016-07-20 Thread 김동일
n again? > > Greetings, > Stephan > > > On Wed, Jul 20, 2016 at 5:58 PM, 김동일 wrote: > >> oh. my flink version is 1.0.3. >> >> >> -- Forwarded message -- >> From: 김동일 >> Date: Thu, Jul 21, 2016 at 12:52 AM >> Subjec

Re: taskmanager memory leak

2016-07-20 Thread Stephan Ewen
12:52 AM > Subject: taskmanager memory leak > To: user@flink.apache.org > > > I've set up cluster(stand alone). > Taskmanager consumes memory over the Xmx property and it grows up > continuously. > I saw this link( > http://mail-

taskmanager memory leak

2016-07-20 Thread 김동일
I've set up cluster(stand alone). Taskmanager consumes memory over the Xmx property and it grows up continuously. I saw this link( http://mail-archives.apache.org/mod_mbox/flink-dev/201606.mbox/%3ccak2vtervsw4muboc4swix0mr6y9bijznjuypf6_f9f0g9-_...@mail.gmail.com%3E ). So i set the taskmanager.memo

Fwd: taskmanager memory leak

2016-07-20 Thread 김동일
oh. my flink version is 1.0.3. -- Forwarded message -- From: 김동일 Date: Thu, Jul 21, 2016 at 12:52 AM Subject: taskmanager memory leak To: user@flink.apache.org I've set up cluster(stand alone). Taskmanager consumes memory over the Xmx property and it grows up continuous

Re: Taskmanager memory

2015-12-09 Thread Stephan Ewen
n behalf of >> Stephan Ewen >> *Sent:* Wednesday, December 9, 2015 11:15 >> *To:* user@flink.apache.org >> *Subject:* Re: Taskmanager memory >> >> Off heap memory is freed when the memory consuming operators release the >> memory. >> >> The

Re: Taskmanager memory

2015-12-09 Thread Fabian Hueske
> > Thanks, > > Sebastian > -- > *From:* ewenstep...@gmail.com on behalf of > Stephan Ewen > *Sent:* Wednesday, December 9, 2015 11:15 > *To:* user@flink.apache.org > *Subject:* Re: Taskmanager memory > > Off heap memory is freed when the

Re: Taskmanager memory

2015-12-09 Thread Kruse, Sebastian
hanks, Sebastian From: ewenstep...@gmail.com on behalf of Stephan Ewen Sent: Wednesday, December 9, 2015 11:15 To: user@flink.apache.org Subject: Re: Taskmanager memory Off heap memory is freed when the memory consuming operators release the memory. The Java pr

Re: Taskmanager memory

2015-12-09 Thread Stephan Ewen
Off heap memory is freed when the memory consuming operators release the memory. The Java process releases that memory then on the next GC, as far as I know. On Wed, Dec 9, 2015 at 11:01 AM, Fabian Hueske wrote: > Streaming mode with on-heap memory won't help because the JVM allocates > all mem

Re: Taskmanager memory

2015-12-09 Thread Fabian Hueske
Streaming mode with on-heap memory won't help because the JVM allocates all memory but doesn't convert it to managed memory internally, right? Is offheap memory actually freed after it has been allocated as managed memory? Does this happen after a job finishes? 2015-12-09 10:44 GMT+01:00 Stephan

Re: Taskmanager memory

2015-12-09 Thread Stephan Ewen
@Sebastian: Getting memory away from the JVM is tricky always, completely independent of pre-allocation of managed memory or lazy allocation. But here is something that may work: - Start Flink in streaming mode - that will make it allocate managed memory lazily - Set the memory to offheap memo

Re: Taskmanager memory

2015-12-09 Thread Fabian Hueske
Hi Sebastian, There is no way to return memory from a Flink process except shutting the process down. I think YARN could help in your setup. In a YARN setup, you can flexibly start and stop Flink sessions with different configurations (memory, TMs, slots) or run a single job. When running a single

Taskmanager memory

2015-12-09 Thread Kruse, Sebastian
Hi everyone, I am currently looking into how Flink can coexist and interoperate with other frameworks in a cluster, such as plain single-machine processes or Spark?. ?Tachyon seems to be nice solution to exchange data between them. However, I think it is a problem that Flink's taskmanagers al