[ 
https://issues.apache.org/jira/browse/FLINK-17468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-17468:
-----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: 
auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Provide more detailed metrics why asynchronous part of checkpoint is taking 
> long time
> -------------------------------------------------------------------------------------
>
>                 Key: FLINK-17468
>                 URL: https://issues.apache.org/jira/browse/FLINK-17468
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / Checkpointing, Runtime / Metrics, Runtime / 
> State Backends
>    Affects Versions: 1.10.0
>            Reporter: Piotr Nowojski
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> As [reported by 
> users|https://lists.apache.org/thread.html/r0833452796ca7d1c9d5e35c110089c95cfdadee9d81884a13613a4ce%40%3Cuser.flink.apache.org%3E]
>  it's not obvious why asynchronous part of checkpoint is taking so long time.
> Maybe we could provide some more detailed metrics/UI/logs about uploading 
> files, materializing meta data, or other things that are happening during the 
> asynchronous checkpoint process?



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

Reply via email to