TangSiyang2001 opened a new issue, #19940:
URL: https://github.com/apache/doris/issues/19940

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Description
   
   Run an `insert`, and then execute `show load` command, we could find that in 
`TaskInfo`, `timeout(s)` would always be 3600, regardless of the real timeout 
val.
   ```
   mysql> show load\G;
   *************************** 1. row ***************************
            JobId: 13003
            Label: orc_s32
            State: FINISHED
         Progress: Unknown id: 13003
             Type: INSERT
          EtlInfo: NULL
         TaskInfo: cluster:N/A; timeout(s):3600; max_filter_ratio:0.0
         ErrorMsg: NULL
       CreateTime: 2023-05-22 18:41:27
     EtlStartTime: 2023-05-22 18:41:27
    EtlFinishTime: 2023-05-22 18:41:27
    LoadStartTime: 2023-05-22 18:41:27
   LoadFinishTime: 2023-05-22 18:45:54
              URL: 
       JobDetails: {"Unfinished 
backends":{},"ScannedRows":0,"TaskNumber":0,"LoadBytes":0,"All 
backends":{},"FileNumber":0,"FileSize":0}
    TransactionId: 2003
     ErrorTablets: {}
             User: root
          Comment: 
   ```
   
   ### Solution
   
   Actually, there are two problems to be resolved: 
   1. The `insert_load_default_timeout_second` should be consistent to the 
default val of `insert_timeout` session var.
   2. The InsertLoadJob is created to record the finish state of an `insert` 
stmt. Set the timeout property correctly when created.
   
    
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to