[jira] [Closed] (FLINK-31396) Occasional inaccurate timeout time calculation with System.nanotime in batch read buffer pool

["Weijie Guo (Jira)" <ji...@apache.org>]

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

Weijie Guo closed FLINK-31396.
------------------------------
    Fix Version/s: 1.18.0
       Resolution: Fixed

master(1.18) via 49929f844975418850ec0334adf4d06c7c895d08.

> Occasional inaccurate timeout time calculation with System.nanotime in batch read buffer pool
> ---------------------------------------------------------------------------------------------
>
>                 Key: FLINK-31396
>                 URL: https://issues.apache.org/jira/browse/FLINK-31396
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Network
>    Affects Versions: 1.18.0
>            Reporter: Yuxin Tan
>            Assignee: Yuxin Tan
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.18.0
>
>
> When running TPC-DS tests, I encountered the read buffer request timeout because of configuring too less read buffers. But I found the timeout time may be less than 5m occasionally, 5m is the expected time. 
> I read the docs of System.nanotime, the docs say that  t1 < t0 should not be used, because of the possibility of numerical overflow. I tested the System.currentTimeMillis and it can work as expected.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)