[FLINK-15942] Improve logging of infinite resource profile

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.0
• Fix Version/s: 1.10.0
• Component/s: Runtime / Configuration, Runtime / Task
• Labels: pull-request-available
• Assignee: Andrey Zagrebin
• Reporter: Andrey Zagrebin
• Created: 06/Feb/20 16:11
• Updated: 07/Feb/20 17:13
• Resolved: 07/Feb/20 17:13

Description

After we set task memory and CPU to infinity in FLINK-15763, it spoiled the logs:

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).

We should treat the infinity as a special case and print it accordingly

Issue Links

• is caused by: FLINK-15763 Check or set necessary resource configuration options to defaults for local execution ignoring FLIP-49
• links to: GitHub Pull Request #11039