Jufang He created FLINK-33869:
-
Summary: Add checkpoint metrics: the latency to close the file
Key: FLINK-33869
URL: https://issues.apache.org/jira/browse/FLINK-33869
Project: Flink
Issue Type
Jufang He created FLINK-33868:
-
Summary: Add checkpoint metrics: the latency to write the file
Key: FLINK-33868
URL: https://issues.apache.org/jira/browse/FLINK-33868
Project: Flink
Issue Type
Jufang He created FLINK-33867:
-
Summary: Add checkpoint metrics: the rate of file write
Key: FLINK-33867
URL: https://issues.apache.org/jira/browse/FLINK-33867
Project: Flink
Issue Type: Sub
to add to the interpretation:
> > > >>> - For non-source tasks, the time include the "travel of the
> > > barriers",
> > > >>> which can take long under back pressure
> > > >>> - For source tasks, it includes the "time to acquire the
&g
t; > >>> - For source tasks, it includes the "time to acquire the checkpoint
> > >>> lock", which can be long if the source is blocked in trying to emit
> > data
> > >>> (again, backpressure).
> > >>>
> > >>>
ussion is looking at ways to make
> >>> checkpoints much less susceptible to back pressure.
> >>>
> >>>
> >>>
> https://lists.apache.org/thread.html/fd5b6cceb4bffb635e26e7ec0787a8db454ddd64aadb40a0d08a90a8@%3Cdev.flink.apache.org%3E
> &g
ep 12, 2019 at 1:25 AM Seth Wiesman wrote:
>>
>> > Great timing, I just debugged this on Monday. E2e time is checkpoint
>> > coordinator to checkpoint coordinator, so it includes RPC to the source
>> and
>> > RPC from the operator back for the JM.
>> >
ml/fd5b6cceb4bffb635e26e7ec0787a8db454ddd64aadb40a0d08a90a8@%3Cdev.flink.apache.org%3E
>>>
>>> Hope that helps understanding what is going on.
>>>
>>> Best,
>>> Stephan
>>>
>>>
>>> On Thu, Sep 12, 2019 at 1:25 AM Seth Wiesman
includes RPC to the source
> and
> > RPC from the operator back for the JM.
> >
> > Seth
> >
> > > On Sep 11, 2019, at 6:17 PM, Jamie Grier
> > wrote:
> > >
> > > Hey all,
> > >
> > > I need to make sense of this behavior.
RPC to the source and
> RPC from the operator back for the JM.
>
> Seth
>
> > On Sep 11, 2019, at 6:17 PM, Jamie Grier
> wrote:
> >
> > Hey all,
> >
> > I need to make sense of this behavior. Any help would be appreciated.
> >
> > Here’s an exampl
e sense of this behavior. Any help would be appreciated.
>
> Here’s an example of a set of Flink checkpoint metrics I don’t understand.
> This is the first operator in a job and as you can see the end-to-end time
> for the checkpoint is long, but it’s not explained by either sync, a
Hey all,
I need to make sense of this behavior. Any help would be appreciated.
Here’s an example of a set of Flink checkpoint metrics I don’t understand.
This is the first operator in a job and as you can see the end-to-end time
for the checkpoint is long, but it’s not explained by either sync
Nico Kruber created FLINK-10962:
---
Summary: Allow correlations between subtask metrics and checkpoint
metrics
Key: FLINK-10962
URL: https://issues.apache.org/jira/browse/FLINK-10962
Project: Flink
Ufuk Celebi created FLINK-6171:
--
Summary: Some checkpoint metrics rely on latest stat snapshot
Key: FLINK-6171
URL: https://issues.apache.org/jira/browse/FLINK-6171
Project: Flink
Issue Type
Ufuk Celebi created FLINK-6170:
--
Summary: Some checkpoint metrics rely on latest stat snapshot
Key: FLINK-6170
URL: https://issues.apache.org/jira/browse/FLINK-6170
Project: Flink
Issue Type
Ufuk Celebi created FLINK-3131:
--
Summary: Expose checkpoint metrics
Key: FLINK-3131
URL: https://issues.apache.org/jira/browse/FLINK-3131
Project: Flink
Issue Type: Improvement
16 matches
Mail list logo
