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

Posted to commits@amoro.apache.org by "zhangwl9 (via GitHub)" <gi...@apache.org> on 2025/04/29 07:10:52 UTC

[I] [Bug]: Negative optimization duration appearing on the Optimizing_tables page [amoro]

zhangwl9 opened a new issue, #3540:
URL: https://github.com/apache/amoro/issues/3540

   ### What happened?
   
   As shown in the screenshot below, when refreshing the Optimizing_tables page, the duration value occasionally displays -1
   ![Image](https://github.com/user-attachments/assets/a15df0a1-db91-4ea5-84f9-3a1ebb4a4485)
   
   ### Affects Versions
   
   master
   
   ### What table formats are you seeing the problem on?
   
   Iceberg
   
   ### What engines are you seeing the problem on?
   
   Optimizer
   
   ### How to reproduce
   
   Refresh the Optimizing_Tables page more frequently
   
   ### Relevant log output
   
   ```shell
   
   ```
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's Code of 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: commits-unsubscribe@amoro.apache.org.apache.org

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

Re: [I] [Bug]: Negative optimization duration appearing on the Optimizing_tables page [amoro]

Posted by "zhangwl9 (via GitHub)" <gi...@apache.org>.

zhangwl9 commented on issue #3540:
URL: https://github.com/apache/amoro/issues/3540#issuecomment-2837778455

   As shown in the following figure, the data in the duration column is obtained by calculating duration = System.currentTimeMillis() - currentStatusStartTime.
   
   <!-- Failed to upload "image.png" -->
   
   However, as shown below, the in-memory value of currentStatusStartTime is in milliseconds like 12.586 s at the system.currentTimeMillis() level
   
   ![Image](https://github.com/user-attachments/assets/f86f61d5-530e-4e07-8d5c-bd9bbfe2e8ff)
   
   In the table "table_runtime" of MYSQL, the data type of the attribute optimizing_status_start_time （currentStatusStartTime）is timestamp, and the precision of this type is at the second level. The above value is saved as 13s in the database.
   
   If the Optimizing_Table page is queried at the moment of 12.896 s, the value of "duration" will be calculated as 12.896 - 13 = -0.104s and displayed as -1s.


-- 
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: commits-unsubscribe@amoro.apache.org

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

Re: [I] [Bug]: Negative optimization duration appearing on the Optimizing_tables page [amoro]

Posted by "xxubai (via GitHub)" <gi...@apache.org>.

xxubai closed issue #3540: [Bug]: Negative optimization duration appearing on the Optimizing_tables page
URL: https://github.com/apache/amoro/issues/3540


-- 
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: commits-unsubscribe@amoro.apache.org

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