You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2022/06/28 06:41:00 UTC

[jira] [Commented] (FLINK-28274) ContinuousFileMonitoringFunction doesn't work with reactive mode

|  ![](cid:jira-generated-image-avatar-636e369d-9562-4ab8-8cef-4e1f50609768) |
[Robert
Metzger](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rmetzger)
**commented** on [![Bug](cid:jira-generated-image-avatar-45c25235-4a3a-4bfa-
aa37-ada100088036)
FLINK-28274](https://issues.apache.org/jira/browse/FLINK-28274)  
---|---  
|  
---  
|  [Re: ContinuousFileMonitoringFunction doesn't work with reactive
mode](https://issues.apache.org/jira/browse/FLINK-28274)  
---  
|

I currently don't have the capacity to look into fixing this, but if somebody
is interested, this is what I would do:  
1\. Add a new test using the file monitoring source to the ReactiveModeITCase
and verify that the test really fails. Maybe this is not the best way to test
the fix, but its a starting point for locally reproducing the issue.  
2\. I guess that the “computeVertexParallelismStoreForExecution” method is
where you’ll find the logic where reactive mode sets the parallelism  
3\. The fix is either ensuring that maxParallelism for the monitoring function
is set correctly, or somehow telling the adaptive scheduler to not change the
parallelism of that function (in a generic way)  
  
---  
|  |  [ ![Add Comment](cid:jira-generated-image-static-comment-
icon-98bffe42-f038-4323-a797-f47e338a518c)
](https://issues.apache.org/jira/browse/FLINK-28274#add-comment "Add Comment")
|  [Add Comment](https://issues.apache.org/jira/browse/FLINK-28274#add-comment
"Add Comment")  
---|---  
  
|  This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9) |  |
![Atlassian logo](https://issues.apache.org/jira/images/mail/atlassian-email-
logo.png)  
---