[jira] [Commented] (FLINK-22055) RPC main thread executor may schedule commands with wrong time unit of delay

2021-03-31 Thread Xintong Song (Jira) 


[ 
https://issues.apache.org/jira/browse/FLINK-22055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17312271#comment-17312271
 ] 

Xintong Song commented on FLINK-22055:
--

[~Amon], you are assigned.

> RPC main thread executor may schedule commands with wrong time unit of delay
> 
>
> Key: FLINK-22055
> URL: https://issues.apache.org/jira/browse/FLINK-22055
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Coordination
>Affects Versions: 1.12.2, 1.13.0
>Reporter: Xintong Song
>Assignee: ZhangWei
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.13.0, 1.12.3
>
>
> There's a typo in \{{RpcEndpoint#MainThreadExecutor#schedule(callable, delay, 
> unit)}}, that may cause the command being scheduled with wrong time unit.
>  
> The issue is Major priority because currently it's not causing any actual 
> damage.



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

[jira] [Commented] (FLINK-22055) RPC main thread executor may schedule commands with wrong time unit of delay

2021-03-31 Thread ZhangWei (Jira) 


[ 
https://issues.apache.org/jira/browse/FLINK-22055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17312196#comment-17312196
 ] 

ZhangWei commented on FLINK-22055:
--

[~xintongsong]
I am est08zw, assign the ticket to me, thanks!

> RPC main thread executor may schedule commands with wrong time unit of delay
> 
>
> Key: FLINK-22055
> URL: https://issues.apache.org/jira/browse/FLINK-22055
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Coordination
>Affects Versions: 1.12.2, 1.13.0
>Reporter: Xintong Song
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.13.0, 1.12.3
>
>
> There's a typo in \{{RpcEndpoint#MainThreadExecutor#schedule(callable, delay, 
> unit)}}, that may cause the command being scheduled with wrong time unit.
>  
> The issue is Major priority because currently it's not causing any actual 
> damage.



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