[ 
https://issues.apache.org/jira/browse/FLINK-34310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815079#comment-17815079
 ] 

Yu Chen commented on FLINK-34310:
---------------------------------

Sorry for the late response.

Thanks [~yunta] for creating the Testing Instructions.  
{quote}When I test other features in my Local, I found Profiler page throw some 
exceptions. I'm not sure whether it's expected.  
{quote}
Hi [~fanrui], so far, the determination of whether the profiler is enabled or 
not is achieved by checking if the interface is registered with
`WebMonitorEndpoint`. Therefore, this behavior is by design.
But I think we can implement this check more elegantly in a later version by 
registering an interface to check the enabled status of the profiler.
 
{quote}[~Yu Chen] Could you estimate when the user doc 
(https://issues.apache.org/jira/browse/FLINK-33436) can be finished?{quote}
Hi [~lincoln.86xy] , really sorry for the late response. I was quite busy 
recently, is that OK for me to finish working on the documentation within the 
next week (before 02.18)?

> Release Testing Instructions: Verify FLINK-33325 Built-in cross-platform 
> powerful java profiler
> -----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-34310
>                 URL: https://issues.apache.org/jira/browse/FLINK-34310
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / REST, Runtime / Web Frontend
>    Affects Versions: 1.19.0
>            Reporter: lincoln lee
>            Assignee: Yun Tang
>            Priority: Blocker
>             Fix For: 1.19.0
>
>         Attachments: image-2024-02-06-14-09-39-874.png, screenshot-1.png, 
> screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png
>
>
> Instructions:
> 1. For the default case, it will print the hint to tell users how to enable 
> this feature.
>  !screenshot-2.png! 
> 2. After we add {{rest.profiling.enabled: true}} in the configurations, we 
> can use this feature now, and the default mode should be {{ITIMER}}
>  !screenshot-3.png! 
> 3. We cannot create another profiling while one is running
>  !screenshot-4.png! 
> 4. We can get at most 10 profilling snapshots by default, and the older one 
> will be deleted automaticially.
>  !screenshot-5.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to