[jira] [Updated] (FLINK-10724) Refactor failure handling in check point coordinator

2019-01-23 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot updated FLINK-10724:
---
Labels: pull-request-available  (was: )

> Refactor failure handling in check point coordinator
> 
>
> Key: FLINK-10724
> URL: https://issues.apache.org/jira/browse/FLINK-10724
> Project: Flink
>  Issue Type: Improvement
>  Components: State Backends, Checkpointing
>Reporter: Andrey Zagrebin
>Assignee: vinoyang
>Priority: Major
>  Labels: pull-request-available
>
> At the moment failure handling of asynchronously triggered checkpoint in 
> check point coordinator happens in different places. We could organise it 
> similar way as failure handling of synchronous triggering of checkpoint in 
> *CheckpointTriggerResult* where we classify error cases. This will simplify 
> e.g. integration of error counter for FLINK-4810.
> See also discussion here: [https://github.com/apache/flink/pull/6567]
> The specific design document : 
> https://docs.google.com/document/d/1ce7RtecuTxcVUJlnU44hzcO2Dwq9g4Oyd8_biy94hJc/edit?usp=sharing



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-10724) Refactor failure handling in check point coordinator

2018-12-15 Thread vinoyang (JIRA)


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

vinoyang updated FLINK-10724:
-
Description: 
At the moment failure handling of asynchronously triggered checkpoint in check 
point coordinator happens in different places. We could organise it similar way 
as failure handling of synchronous triggering of checkpoint in 
*CheckpointTriggerResult* where we classify error cases. This will simplify 
e.g. integration of error counter for FLINK-4810.

See also discussion here: [https://github.com/apache/flink/pull/6567]

The specific design document : 
https://docs.google.com/document/d/1ce7RtecuTxcVUJlnU44hzcO2Dwq9g4Oyd8_biy94hJc/edit?usp=sharing

  was:
At the moment failure handling of asynchronously triggered checkpoint in check 
point coordinator happens in different places. We could organise it similar way 
as failure handling of synchronous triggering of checkpoint in 
*CheckpointTriggerResult* where we classify error cases. This will simplify 
e.g. integration of error counter for FLINK-4810.

See also discussion here: [https://github.com/apache/flink/pull/6567]


> Refactor failure handling in check point coordinator
> 
>
> Key: FLINK-10724
> URL: https://issues.apache.org/jira/browse/FLINK-10724
> Project: Flink
>  Issue Type: Improvement
>  Components: State Backends, Checkpointing
>Reporter: Andrey Zagrebin
>Assignee: vinoyang
>Priority: Major
>
> At the moment failure handling of asynchronously triggered checkpoint in 
> check point coordinator happens in different places. We could organise it 
> similar way as failure handling of synchronous triggering of checkpoint in 
> *CheckpointTriggerResult* where we classify error cases. This will simplify 
> e.g. integration of error counter for FLINK-4810.
> See also discussion here: [https://github.com/apache/flink/pull/6567]
> The specific design document : 
> https://docs.google.com/document/d/1ce7RtecuTxcVUJlnU44hzcO2Dwq9g4Oyd8_biy94hJc/edit?usp=sharing



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-10724) Refactor failure handling in check point coordinator

2018-12-10 Thread Andrey Zagrebin (JIRA)


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

Andrey Zagrebin updated FLINK-10724:

Description: 
At the moment failure handling of asynchronously triggered checkpoint in check 
point coordinator happens in different places. We could organise it similar way 
as failure handling of synchronous triggering of checkpoint in 
*CheckpointTriggerResult* where we classify error cases. This will simplify 
e.g. integration of error counter for FLINK-4810.

See also discussion here: [https://github.com/apache/flink/pull/6567]

  was:
At the moment failure handling of asynchronously triggered checkpoint in check 
point coordinator happens in different places. We could organise it similar way 
as failure handling of synchronous triggering of checkpoint in 
*CheckpointTriggerResult* where we classify error cases. This will simplify 
e.g. integration of error counter for FLINK-10074.

See also discussion here: [https://github.com/apache/flink/pull/6567]


> Refactor failure handling in check point coordinator
> 
>
> Key: FLINK-10724
> URL: https://issues.apache.org/jira/browse/FLINK-10724
> Project: Flink
>  Issue Type: Improvement
>  Components: State Backends, Checkpointing
>Reporter: Andrey Zagrebin
>Assignee: vinoyang
>Priority: Major
>
> At the moment failure handling of asynchronously triggered checkpoint in 
> check point coordinator happens in different places. We could organise it 
> similar way as failure handling of synchronous triggering of checkpoint in 
> *CheckpointTriggerResult* where we classify error cases. This will simplify 
> e.g. integration of error counter for FLINK-4810.
> See also discussion here: [https://github.com/apache/flink/pull/6567]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-10724) Refactor failure handling in check point coordinator

2018-10-30 Thread Andrey Zagrebin (JIRA)


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

Andrey Zagrebin updated FLINK-10724:

Description: 
At the moment failure handling of asynchronously triggered checkpoint in check 
point coordinator happens in different places. We could organise it similar way 
as failure handling of synchronous triggering of checkpoint in 
*CheckpointTriggerResult* where we classify error cases. This will simplify 
e.g. integration of error counter for FLINK-10074.

See also discussion here: [https://github.com/apache/flink/pull/6567]

  was:
At the moment failure handling of asynchronously triggered checkpoint in check 
point coordinator happens in different places. We could organise it similar way 
as failure handling of synchronous triggering of checkpoint in 
*CheckpointTriggerResult* where ** classify error cases. This will simplify 
e.g. integration of error counter for FLINK-10074.

See also discussion here: https://github.com/apache/flink/pull/6567


> Refactor failure handling in check point coordinator
> 
>
> Key: FLINK-10724
> URL: https://issues.apache.org/jira/browse/FLINK-10724
> Project: Flink
>  Issue Type: Improvement
>  Components: State Backends, Checkpointing
>Reporter: Andrey Zagrebin
>Assignee: vinoyang
>Priority: Major
>
> At the moment failure handling of asynchronously triggered checkpoint in 
> check point coordinator happens in different places. We could organise it 
> similar way as failure handling of synchronous triggering of checkpoint in 
> *CheckpointTriggerResult* where we classify error cases. This will simplify 
> e.g. integration of error counter for FLINK-10074.
> See also discussion here: [https://github.com/apache/flink/pull/6567]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-10724) Refactor failure handling in check point coordinator

2018-10-30 Thread Andrey Zagrebin (JIRA)


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

Andrey Zagrebin updated FLINK-10724:

Description: 
At the moment failure handling of asynchronously triggered checkpoint in check 
point coordinator happens in different places. We could organise it similar way 
as failure handling of synchronous triggering of checkpoint in 
*CheckpointTriggerResult* where ** classify error cases. This will simplify 
e.g. integration of error counter for FLINK-10074.

See also discussion here: https://github.com/apache/flink/pull/6567

  was:At the moment failure handling of asynchronously triggered checkpoint in 
check point coordinator happens in different places. We could organise it 
similar way as failure handling of synchronous triggering of checkpoint in 
*CheckpointTriggerResult* where ** classify error cases. This will simplify 
e.g. integration of error counter for FLINK-10074.


> Refactor failure handling in check point coordinator
> 
>
> Key: FLINK-10724
> URL: https://issues.apache.org/jira/browse/FLINK-10724
> Project: Flink
>  Issue Type: Improvement
>  Components: State Backends, Checkpointing
>Reporter: Andrey Zagrebin
>Assignee: vinoyang
>Priority: Major
>
> At the moment failure handling of asynchronously triggered checkpoint in 
> check point coordinator happens in different places. We could organise it 
> similar way as failure handling of synchronous triggering of checkpoint in 
> *CheckpointTriggerResult* where ** classify error cases. This will simplify 
> e.g. integration of error counter for FLINK-10074.
> See also discussion here: https://github.com/apache/flink/pull/6567



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)