You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "herbherbherb (via GitHub)" <gi...@apache.org> on 2026/05/01 00:16:12 UTC

[PR] [FLINK-39585][runtime] Log execution graph creation failures at ERROR Level [flink]

herbherbherb opened a new pull request, #28080:
URL: https://github.com/apache/flink/pull/28080

     ## What is the purpose of the change
                                                                                                                                                                                                                           
     Promotes the single failure log in `CreatingExecutionGraph#handleExecutionGraphCreation`                                                                                                                              
     from INFO to ERROR. A non-null throwable here means the AdaptiveScheduler couldn't                                                                                                                                    
     build/restore the ExecutionGraph and the job is immediately transitioned to FAILED, so                                                                                                                                
     ERROR is the appropriate severity for that root-cause line.                                                                                                                                                           
                                                                                                                                                                                                                           
     ## Brief change log                                                                                                                                                                                                   
                                                                                                                                                                                                                           
       - `CreatingExecutionGraph.java`: change the throwable-branch log call from `info(...)` to `error(...)`.                                                                                                             
      
     ## Verifying this change                                                                                                                                                                                              
                                                                     
     This change is a trivial logging-severity adjustment without any test coverage.                                                                                                                                       
      
     ## Does this pull request potentially affect one of the following parts:                                                                                                                                              
                                                                     
       - Dependencies (does it add or upgrade a dependency): no                                                                                                                                                            
       - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no
       - The serializers: no                                                                                                                                                                                               
       - The runtime per-record code paths (performance sensitive): no
       - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no                                                                                      
       - The S3 file system connector: no                                                                                                                                                                                  
                                                                                                                                                                                                                           
     ## Documentation                                                                                                                                                                                                      
                                                                                                                                                                                                                           
       - Does this pull request introduce a new feature? no                                                                                                                                                                
       - If yes, how is the feature documented? not applicable
                                                                                                                                                                                                                           
     ---                                                             
                                                                                                                                                                                                                           
   ##### Was generative AI tooling used to co-author this PR?                                                                                                                                                            
      
     - [ ] Yes (please specify the tool below) 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] [FLINK-39585][runtime] Log execution graph creation failures at ERROR Level [flink]

Posted by "flinkbot (via GitHub)" <gi...@apache.org>.
flinkbot commented on PR #28080:
URL: https://github.com/apache/flink/pull/28080#issuecomment-4357045970

   <!--
   Meta data
   {
     "version" : 1,
     "metaDataEntries" : [ {
       "hash" : "1429c009197eeba0479c7775016a8a3faf915c2d",
       "status" : "UNKNOWN",
       "url" : "TBD",
       "triggerID" : "1429c009197eeba0479c7775016a8a3faf915c2d",
       "triggerType" : "PUSH"
     } ]
   }-->
   ## CI report:
   
   * 1429c009197eeba0479c7775016a8a3faf915c2d UNKNOWN
   
   <details>
   <summary>Bot commands</summary>
     The @flinkbot bot supports the following commands:
   
    - `@flinkbot run azure` re-run the last Azure build
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] [FLINK-39585][runtime] Log execution graph creation failures at ERROR Level [flink]

Posted by "herbherbherb (via GitHub)" <gi...@apache.org>.
herbherbherb commented on PR #28080:
URL: https://github.com/apache/flink/pull/28080#issuecomment-4375420602

   Thank you @spuru9, I don't have perm to merge this change, could you please help me with the merge please or let me know the check-in process please, thank you


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org