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

Till Rohrmann resolved FLINK-15942.
-----------------------------------
    Fix Version/s:     (was: 1.11.0)
       Resolution: Fixed

Fixed via

master:
43b4289c0851b93da7d57d97e911f8b8091f11f5
89b095fbdcb4eb6045db0e9ca5257a3c23582eb5

1.10.0:
67e1052f045fa0617ed672ff45ed91af7379d6ed
cea09a8bd8d35b58a5a3eb15ea7b537b16617535

> Improve logging of infinite resource profile
> --------------------------------------------
>
>                 Key: FLINK-15942
>                 URL: https://issues.apache.org/jira/browse/FLINK-15942
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Configuration, Runtime / Task
>    Affects Versions: 1.10.0
>            Reporter: Andrey Zagrebin
>            Assignee: Andrey Zagrebin
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> After we set task memory and CPU to infinity inĀ FLINK-15763, it spoiled the 
> logs:
> {code:java}
> 00:23:49,442 INFO 
> org.apache.flink.runtime.taskexecutor.slot.TaskSlotTableImpl - Free slot 
> TaskSlot(index:0, state:ACTIVE, resource profile: 
> ResourceProfile{cpuCores=44942328371557892500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000.0000000000000000,
>  taskHeapMemory=2097152.000tb (2305843009213693951 bytes), 
> taskOffHeapMemory=2097152.000tb (2305843009213693951 bytes), 
> managedMemory=20.000mb (20971520 bytes), networkMemory=16.000mb (16777216 
> bytes)}, allocationId: 349dacfbf1ac4d0b44a2d11e1976d264, jobId: 
> 689a0cf24b40f16b6f45157f78754c46).
> {code}
> We should treat the infinity as a special case and print it accordingly



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to