[FLINK-15465] Avoid failing when required memory calculation not accurate in BinaryHashTable

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.10.0
• Component/s: Table SQL / Runtime
• Labels: pull-request-available
• Assignee: Jingsong Lee
• Reporter: Jingsong Lee
• Created: 03/Jan/20 05:59
• Updated: 07/Jan/20 10:43
• Resolved: 07/Jan/20 10:43

Description

In BinaryHashBucketArea.insertToBucket.

When BinaryHashTable.buildTableFromSpilledPartition."Build in memory hash table", it requires memory can put all records, if not, will fail.

Because the linked hash conflict solution, the required memory calculation are not accurate, in this case, we should apply for insufficient memory from heap.

And must be careful, the steal memory should not return to table.

Issue Links

• links to: GitHub Pull Request #10756