[
https://issues.apache.org/jira/browse/FLINK-14712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16974010#comment-16974010
]
lining commented on FLINK-14712:
There are two motivations for adding these metrics
1. For one vertex,
[
https://issues.apache.org/jira/browse/FLINK-14717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14717:
---
Description:
*Current*
The job's exceptions just show current attempt’s exceptions in web UI.
If the job
[
https://issues.apache.org/jira/browse/FLINK-14730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14730:
---
Description:
*Current*
If the resource requested by the job can‘t be satisfied by the cluster, the job
[
https://issues.apache.org/jira/browse/FLINK-14730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14730:
---
Description:
*Current*
if the resource requested by the job can‘t be satisfied by the cluster, the job
[
https://issues.apache.org/jira/browse/FLINK-14730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14730:
---
Description:
*Current*
if the resource requested by the job can‘t be satisfied by the cluster, the job
[
https://issues.apache.org/jira/browse/FLINK-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14738:
---
Description:
When the job is running, we can get the operator's metrics, such as [subtask
index].
[
https://issues.apache.org/jira/browse/FLINK-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14738:
---
Description: When the job is running, we could get operators' metrics. But
when it's finished, only get
[
https://issues.apache.org/jira/browse/FLINK-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14740:
---
Description:
*In current design:*
The DataSet job uses VertexID as the OperatorID in the
[
https://issues.apache.org/jira/browse/FLINK-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973973#comment-16973973
]
lining commented on FLINK-14740:
I agree not to expose operator id in web UI. But the problem is
[
https://issues.apache.org/jira/browse/FLINK-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14740:
---
Description:
In current design:
The DataSet job uses VertexID as the OperatorID in the OperatorMetricGroup
[
https://issues.apache.org/jira/browse/FLINK-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14740:
---
Comment: was deleted
(was: cc [~chesnay] )
> Create OperatorID for OperatorMetricGroup which in batch job
[
https://issues.apache.org/jira/browse/FLINK-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14740:
---
Description:
Now OperatorMetricGroup which in batch job use VertexId as OperatorId. For
chain operator,
[
https://issues.apache.org/jira/browse/FLINK-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973194#comment-16973194
]
lining commented on FLINK-14740:
cc [~chesnay]
> Create OperatorID for OperatorMetricGroup which in
lining created FLINK-14740:
--
Summary: Create OperatorID for OperatorMetricGroup which in batch
job
Key: FLINK-14740
URL: https://issues.apache.org/jira/browse/FLINK-14740
Project: Flink
Issue
[
https://issues.apache.org/jira/browse/FLINK-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973154#comment-16973154
]
lining commented on FLINK-14738:
[~chesnay] what do you think about it?
> Job which status is finished,
[
https://issues.apache.org/jira/browse/FLINK-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14738:
---
Description: When the job is running, we could get operators' metrics. But
when it's finished, just get
lining created FLINK-14738:
--
Summary: Job which status is finished, get operator metric
Key: FLINK-14738
URL: https://issues.apache.org/jira/browse/FLINK-14738
Project: Flink
Issue Type: Wish
lining created FLINK-14730:
--
Summary: Add pending slots for job
Key: FLINK-14730
URL: https://issues.apache.org/jira/browse/FLINK-14730
Project: Flink
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/FLINK-14717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14717:
---
Description:
Now JobExceptionsHandler just shows current attempt exceptions. If job
failovers, there may
[
https://issues.apache.org/jira/browse/FLINK-14717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14717:
---
Description:
Now JobExceptionsHandler just shows current attempt exceptions. If job
failovers, there may
[
https://issues.apache.org/jira/browse/FLINK-14717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16972183#comment-16972183
]
lining commented on FLINK-14717:
[~chesnay] what do you think it?
> JobExceptionsHandler show
[
https://issues.apache.org/jira/browse/FLINK-14717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14717:
---
Description: Now JobExceptionsHandler just shows current attempt
exceptions. If job failovers, there may
[
https://issues.apache.org/jira/browse/FLINK-14717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16972183#comment-16972183
]
lining edited comment on FLINK-14717 at 11/12/19 8:37 AM:
--
[~chesnay] what do
[
https://issues.apache.org/jira/browse/FLINK-14717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14717:
---
Description: Now
> JobExceptionsHandler show exceptions of prior attempts
>
[
https://issues.apache.org/jira/browse/FLINK-14717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14717:
---
Parent: FLINK-11374
Issue Type: Sub-task (was: Improvement)
> JobExceptionsHandler show exceptions
lining created FLINK-14717:
--
Summary: JobExceptionsHandler show exceptions of prior attempts
Key: FLINK-14717
URL: https://issues.apache.org/jira/browse/FLINK-14717
Project: Flink
Issue Type:
[
https://issues.apache.org/jira/browse/FLINK-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-11374:
---
Description:
Now failover just show limit size task failover latest time(ps:According to the
current flink
[
https://issues.apache.org/jira/browse/FLINK-14712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14712:
---
Issue Type: Improvement (was: Bug)
> Add NetWork metric for IOMetricsInfo
>
[
https://issues.apache.org/jira/browse/FLINK-14137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14137:
---
Parent: FLINK-14713
Issue Type: Sub-task (was: Improvement)
> Show Attempt History in Vertex
lining created FLINK-14713:
--
Summary: Show Attempt History in Vertex SubTask
Key: FLINK-14713
URL: https://issues.apache.org/jira/browse/FLINK-14713
Project: Flink
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/FLINK-14712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14712:
---
Description:
h4. (1) The current monitor is heavy-weight.
* Backpressure monitoring works by repeatedly
lining created FLINK-14712:
--
Summary: Add NetWork metric for IOMetricsInfo
Key: FLINK-14712
URL: https://issues.apache.org/jira/browse/FLINK-14712
Project: Flink
Issue Type: Bug
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Attachment: image-2019-10-24-16-22-27-360.png
> Update TaskManager's memory information to match its memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Description:
h3. Motivation
There are several shortcomings of current (Flink 1.9) Flink TaskManager memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Description:
h3. Motivation
There are several shortcomings of current (Flink 1.9) Flink TaskManager memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Attachment: image-2019-10-24-16-20-23-210.png
> Update TaskManager's memory information to match its memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Description:
h3. Motivation
There are several shortcomings of current (Flink 1.9) Flink TaskManager memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Attachment: image-2019-10-24-16-19-15-499.png
> Update TaskManager's memory information to match its memory
[
https://issues.apache.org/jira/browse/FLINK-11405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956798#comment-16956798
]
lining commented on FLINK-11405:
[~chesnay], I have added what exactly the JIRA want to accomplish.
[
https://issues.apache.org/jira/browse/FLINK-11405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-11405:
---
Description:
Now failover just show limit size task failover latest time(ps:According to the
current flink
[
https://issues.apache.org/jira/browse/FLINK-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16955913#comment-16955913
]
lining commented on FLINK-14422:
Sounds good.
> Expose TaskExecutor resource configurations to rest api
[
https://issues.apache.org/jira/browse/FLINK-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954387#comment-16954387
]
lining commented on FLINK-13894:
[~chesnay] Considering your and Robert‘s advice. It might be better to
[
https://issues.apache.org/jira/browse/FLINK-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-13894:
---
Description:
As FLINK-13868 has added ResourceId in rest api of subatsk. So we can according
to it add log
[
https://issues.apache.org/jira/browse/FLINK-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-13894:
---
Attachment: image-2019-10-18-16-27-11-784.png
> Web Ui add log url for subtask of vertex
>
[
https://issues.apache.org/jira/browse/FLINK-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-13894:
---
Attachment: image-2019-10-18-16-09-37-914.png
> Web Ui add log url for subtask of vertex
>
[
https://issues.apache.org/jira/browse/FLINK-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-13894:
---
Description:
As FLINK-13868 has added ResourceId in rest api of subatsk. So we can according
to it add log
[
https://issues.apache.org/jira/browse/FLINK-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-13894:
---
Comment: was deleted
(was: [~chesnay] I update description for the new screenshot. It takes into
account
[
https://issues.apache.org/jira/browse/FLINK-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954339#comment-16954339
]
lining commented on FLINK-13894:
[~chesnay] I update description for the new screenshot. It takes into
[
https://issues.apache.org/jira/browse/FLINK-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-13894:
---
Description:
As FLINK-13868 has added ResourceId in rest api of subatsk. So we can according
to it add log
[
https://issues.apache.org/jira/browse/FLINK-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-13894:
---
Attachment: image-2019-10-18-15-11-59-232.png
> Web Ui add log url for subtask of vertex
>
[
https://issues.apache.org/jira/browse/FLINK-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953620#comment-16953620
]
lining commented on FLINK-14422:
[~trohrmann] Here, I mainly want to get information about the
[
https://issues.apache.org/jira/browse/FLINK-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953620#comment-16953620
]
lining edited comment on FLINK-14422 at 10/17/19 10:44 AM:
---
[~trohrmann] here,
[
https://issues.apache.org/jira/browse/FLINK-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14422:
---
Summary: Expose TaskExecutor resource configurations to rest api (was:
Expose TaskExecutor resource
[
https://issues.apache.org/jira/browse/FLINK-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14435:
---
Description:
h5. data in json
{code:json}
{
"cpuAllocated": -1,
"cpuUsage": -1,
"taskHeapAllocated":
[
https://issues.apache.org/jira/browse/FLINK-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14435:
---
Description:
data in json
{
"cpuAllocated": -1,
"cpuUsage": -1,
"taskHeapAllocated": 966787072,
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Description:
h3. Motivation
There are several shortcomings of current (Flink 1.9) Flink TaskManager memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Description:
h3. Motivation
There are several shortcomings of current (Flink 1.9) Flink TaskManager memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Description:
h3. Motivation
There are several shortcomings of current (Flink 1.9) Flink TaskManager memory
lining created FLINK-14435:
--
Summary: Add TaskManagerResourceInfo in TaskManagerDetailsInfo to
show TaskManager Resource
Key: FLINK-14435
URL: https://issues.apache.org/jira/browse/FLINK-14435
Project:
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Description:
h3. Motivation
There are several shortcomings of current (Flink 1.9) Flink TaskManager memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Attachment: image-2019-10-17-18-29-53-329.png
> Update TaskManager's memory information to match its memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Description:
h3. Motivation
There are several shortcomings of current (Flink 1.9) Flink TaskManager memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Description:
h3. Motivation
There are several shortcomings of current (Flink 1.9) Flink TaskManager memory
[
https://issues.apache.org/jira/browse/FLINK-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14422:
---
Parent: FLINK-14431
Issue Type: Sub-task (was: Wish)
> Expose TaskExecutor resource configurations
[
https://issues.apache.org/jira/browse/FLINK-14406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14406:
---
Parent: FLINK-14431
Issue Type: Sub-task (was: Improvement)
> Add metric for manage memory
>
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Description:
h3. Motivation
There are several shortcomings of current (Flink 1.9) Flink TaskManager memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Attachment: image-2019-10-17-18-01-09-353.png
> Update TaskManager's memory information to match its memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Attachment: image-2019-10-17-17-58-50-342.png
> Update TaskManager's memory information to match its memory
[
https://issues.apache.org/jira/browse/FLINK-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14431:
---
Description:
h3. Motivation
There are several shortcomings of current (Flink 1.9) Flink TaskManager memory
lining created FLINK-14431:
--
Summary: Update TaskManager's memory information to match its
memory composition
Key: FLINK-14431
URL: https://issues.apache.org/jira/browse/FLINK-14431
Project: Flink
[
https://issues.apache.org/jira/browse/FLINK-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953351#comment-16953351
]
lining commented on FLINK-14422:
[~xintongsong] [~trohrm...@apache.org], how about it?
> Get
lining created FLINK-14422:
--
Summary: Get taskmanager resource config in rest api
Key: FLINK-14422
URL: https://issues.apache.org/jira/browse/FLINK-14422
Project: Flink
Issue Type: Wish
lining created FLINK-14406:
--
Summary: Add metric for manage memory
Key: FLINK-14406
URL: https://issues.apache.org/jira/browse/FLINK-14406
Project: Flink
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/FLINK-14404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952588#comment-16952588
]
lining commented on FLINK-14404:
Now it's fixing in FLINK-13983
> the jvm heap size from
[
https://issues.apache.org/jira/browse/FLINK-14404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14404:
---
Description:
In
lining created FLINK-14404:
--
Summary: the jvm heap size from calculateTaskManagerHeapSizeMB in
config.sh is different from TaskManagerServices.calculateHeapSizeMB
Key: FLINK-14404
URL:
[
https://issues.apache.org/jira/browse/FLINK-11405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-11405:
---
Description:
Now failover just show limit size task failover latest time(ps:According to the
current flink
[
https://issues.apache.org/jira/browse/FLINK-11405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-11405:
---
Description:
Now failover just show limit size task failover latest time(ps:According to the
current flink
[
https://issues.apache.org/jira/browse/FLINK-11405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-11405:
---
Description:
Now failover just show limit size task failover latest time(ps:According to the
current flink
[
https://issues.apache.org/jira/browse/FLINK-11405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-11405:
---
Summary: rest api can show more exceptions by query parameter (was: rest
api can more exceptions by query
[
https://issues.apache.org/jira/browse/FLINK-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16938375#comment-16938375
]
lining commented on FLINK-11374:
[~trohrmann], could you assign this issue to me? Then i and
[
https://issues.apache.org/jira/browse/FLINK-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937521#comment-16937521
]
lining edited comment on FLINK-11374 at 9/25/19 9:02 AM:
-
[~trohrmann], if
[
https://issues.apache.org/jira/browse/FLINK-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937521#comment-16937521
]
lining commented on FLINK-11374:
[~trohrmann], if [~vthinkxie] 's suggest is ok, we could do it
[
https://issues.apache.org/jira/browse/FLINK-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-11374:
---
Description:
Now failover just show limit size task failover latest time(ps:According to the
current flink
[
https://issues.apache.org/jira/browse/FLINK-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-11374:
---
Description: Now failover just show limit size task failover latest
time(ps: ). (was: Now failover just
[
https://issues.apache.org/jira/browse/FLINK-11405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-11405:
---
Summary: rest api can more exceptions by query parameter (was: rest api
can see task and task attempt
[
https://issues.apache.org/jira/browse/FLINK-14176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16936560#comment-16936560
]
lining commented on FLINK-14176:
!image-2019-09-24-16-42-36-198.png!
> add taskmanager link in vertex‘s
[
https://issues.apache.org/jira/browse/FLINK-14176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-14176:
---
Attachment: image-2019-09-24-16-42-36-198.png
> add taskmanager link in vertex‘s page of taskmanager
>
lining created FLINK-14176:
--
Summary: add taskmanager link in vertex‘s page of taskmanager
Key: FLINK-14176
URL: https://issues.apache.org/jira/browse/FLINK-14176
Project: Flink
Issue Type:
[
https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932080#comment-16932080
]
lining commented on FLINK-13987:
Could you show your JIAR about it?
> add new logs api, see more log
[
https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931971#comment-16931971
]
lining edited comment on FLINK-13987 at 9/18/19 5:42 AM:
-
I have disscussed with
[
https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931971#comment-16931971
]
lining edited comment on FLINK-13987 at 9/18/19 5:40 AM:
-
I hava disscussed with
[
https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931971#comment-16931971
]
lining edited comment on FLINK-13987 at 9/18/19 5:39 AM:
-
I hava disscussed with
[
https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931971#comment-16931971
]
lining commented on FLINK-13987:
I hava disscussed with till about that pr. It has updated for a long
[
https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-13987:
---
Description:
As the job running, the log files are becoming large.
Current log api returns all contents，it
[
https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-13987:
---
Description:
As the job running, the log files are becoming large.
Current log api returns all contents，it
[
https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-13987:
---
Description:
As the job running, the log files are becoming large.
Current log api returns all contents，it
[
https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-13987:
---
Description:
As the job running, the log files are becoming large.
Current log api often blocks or don't
[
https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lining updated FLINK-13987:
---
Description:
As log files becoming more large, current log api often blocks or don't work.
It's unfriendly
lining created FLINK-13987:
--
Summary: add new logs api, see more log files and can see logs by
pages
Key: FLINK-13987
URL: https://issues.apache.org/jira/browse/FLINK-13987
Project: Flink
Issue
201 - 300 of 452 matches
Mail list logo
