Re: taskmanager.cpu.cores 1.7976931348623157E308

2020-12-07 Thread Rex Fenley
Thanks for all this feedback, this is really helpful! On Sun, Dec 6, 2020 at 7:23 PM Xintong Song wrote: > FYI, I've opened FLINK-20503 for this. > https://issues.apache.org/jira/browse/FLINK-20503 > > Thank you~ > > Xintong Song > > > > On Mon, Dec 7, 2020 at 11:10 AM Xintong Song > wrote: >

Re: taskmanager.cpu.cores 1.7976931348623157E308

2020-12-06 Thread Xintong Song
FYI, I've opened FLINK-20503 for this. https://issues.apache.org/jira/browse/FLINK-20503 Thank you~ Xintong Song On Mon, Dec 7, 2020 at 11:10 AM Xintong Song wrote: > I forgot to mention that it is designed that task managers always have > `Double#MAX_VALUE` cpu cores in local execution. >

Re: taskmanager.cpu.cores 1.7976931348623157E308

2020-12-06 Thread Xintong Song
I forgot to mention that it is designed that task managers always have `Double#MAX_VALUE` cpu cores in local execution. And I think Yangze is right. The log "The configuration option taskmanager.cpu.cores required for local execution is not set, setting it to" can be misleading for users. Will

Re: taskmanager.cpu.cores 1.7976931348623157E308

2020-12-06 Thread Xintong Song
Hi Rex, We're running this in a local environment so that may be contributing to > what we're seeing. > Just to double check on this. By `local environment`, you mean running flink without setting up a standalone cluster or submitting it to a K8s/Yarn cluster? (Typically executing from an IDE,

Re: taskmanager.cpu.cores 1.7976931348623157E308

2020-12-06 Thread Yangze Guo
My gut feeling is your "vmArgs" does not take effect. Best, Yangze Guo On Mon, Dec 7, 2020 at 10:32 AM Yangze Guo wrote: > > Hi, Rex, > > Can you share more logs for it. Did you see something like "The > configuration option taskmanager.cpu.cores required for local > execution is not set,

Re: taskmanager.cpu.cores 1.7976931348623157E308

2020-12-06 Thread Yangze Guo
Hi, Rex, Can you share more logs for it. Did you see something like "The configuration option taskmanager.cpu.cores required for local execution is not set, setting it to" in your logs? Best, Yangze Guo Best, Yangze Guo On Sat, Dec 5, 2020 at 6:53 PM David Anderson wrote: > >

Re: taskmanager.cpu.cores 1.7976931348623157E308

2020-12-05 Thread David Anderson
seeing. > > On Fri, Dec 4, 2020 at 10:41 PM Rex Fenley wrote: > >> Hello, >> >> I'm tuning flink for parallelism right now and when I look at the >> JobManager I see >> *taskmanager.cpu.cores* 1.7976931348623157E308 >> Which looks like the maximum double nu

Re: taskmanager.cpu.cores 1.7976931348623157E308

2020-12-04 Thread Rex Fenley
We're running this in a local environment so that may be contributing to what we're seeing. On Fri, Dec 4, 2020 at 10:41 PM Rex Fenley wrote: > Hello, > > I'm tuning flink for parallelism right now and when I look at the > JobManager I see > *taskmanager.cpu.cores* 1.79769

taskmanager.cpu.cores 1.7976931348623157E308

2020-12-04 Thread Rex Fenley
Hello, I'm tuning flink for parallelism right now and when I look at the JobManager I see *taskmanager.cpu.cores* 1.7976931348623157E308 Which looks like the maximum double number. We have 8 cpu cores, so we figured we'd bump to 16 for hyper threading. We have 37 operators so we rounded up