You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2022/01/13 15:03:50 UTC
[GitHub] [flink] akalash opened a new pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
akalash opened a new pull request #18354:
URL: https://github.com/apache/flink/pull/18354
…ing" limit in unaligned checkpoint documentation
<!--
*Thank you very much for contributing to Apache Flink - we are happy that you want to help us improve Flink. To help the community review your contribution in the best possible way, please go through the checklist below, which will get the contribution into a shape in which it can be best reviewed.*
*Please understand that we do not do this to make contributions to Flink a hassle. In order to uphold a high standard of quality for code contributions, while at the same time managing a large number of contributions, we need contributors to prepare the contributions well, and give reviewers enough contextual information for the review. Please also understand that contributions that do not follow this guide will take longer to review and thus typically be picked up with lower priority by the community.*
## Contribution Checklist
- Make sure that the pull request corresponds to a [JIRA issue](https://issues.apache.org/jira/projects/FLINK/issues). Exceptions are made for typos in JavaDoc or documentation files, which need no JIRA issue.
- Name the pull request in the form "[FLINK-XXXX] [component] Title of the pull request", where *FLINK-XXXX* should be replaced by the actual issue number. Skip *component* if you are unsure about which is the best component.
Typo fixes that have no associated JIRA issue should be named following this pattern: `[hotfix] [docs] Fix typo in event time introduction` or `[hotfix] [javadocs] Expand JavaDoc for PuncuatedWatermarkGenerator`.
- Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean verify` passes. You can set up Azure Pipelines CI to do that following [this guide](https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-Tutorial:SettingupAzurePipelinesforaforkoftheFlinkrepository).
- Each pull request should address only one issue, not mix up code from multiple issues.
- Each commit in the pull request has a meaningful commit message (including the JIRA id)
- Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below.
**(The sections below can be removed for hotfixes of typos)**
-->
## What is the purpose of the change
Added one more limit case for unaligned checkpoint documentation
## Verifying this change
It is documentation.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / **no**)
- The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
- The serializers: (yes / **no** / don't know)
- The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
- Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / **no** / don't know)
- The S3 file system connector: (yes / **no** / don't know)
## Documentation
- Does this pull request introduce a new feature? (yes / no)
- If yes, how is the feature documented? (not applicable / **docs** / JavaDocs / not documented)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] pnowojski commented on a change in pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
pnowojski commented on a change in pull request #18354:
URL: https://github.com/apache/flink/pull/18354#discussion_r785918553
##########
File path: docs/content.zh/docs/ops/state/checkpointing_under_backpressure.md
##########
@@ -129,6 +129,10 @@ In-flight 数据后再生成 Watermark **。如果您的 Pipeline 中使用了**
使用对齐 Checkpoint产生**不同的结果**。如果您的 Operator 依赖于最新的 Watermark 始终可用，解决办法是将 Watermark
存放在 OperatorState 中。在这种情况下，Watermark 应该使用单键 group 存放在 UnionState 以方便扩缩容。
+#### Interplay with long-running record processing
+
+Despite that unaligned checkpoints barriers are able to overtake all other records in the queue. The handling of this barrier still can be delayed if the current record takes a lot of time to be processed. This situation can occur when window operators emit heavy result or the flat map produce a lot of records for a single input. It also can happen in any other situation when the processing of the single record takes a while(a long record). As result, the time of the checkpoint can be higher than expected or it can be volatile from time to time.
Review comment:
- Please brake long line into a couple of shorter lines
- `window operators emit heavy result` -> `firing many timers all at once, for example in windowed operations`
- Maybe let's rephrase large record and flatMap to something like:
> Second problematic scenario might occur when system is being blocked waiting for more than one
> memory segment availability when processing a single input record. Flink can not interrupt processing of
> a single input record, and unaligned checkpoints have to wait for the currently processed record to be
> fully processed. This can cause problems in two scenarios. Either as a result of serialisation of a large
> record that doesn't fit into single memory segment or in a flatMap operation, that produces many output
> records for one input record. In such scenarios back pressure can block unaligned checkpoints until all of
> the memory segments required to process the single input record are available.
?
note: I'm not sure if we should use "memory segment" or "buffer" name (Depending what's used elsewhere in the docs).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] pnowojski commented on a change in pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
pnowojski commented on a change in pull request #18354:
URL: https://github.com/apache/flink/pull/18354#discussion_r786513195
##########
File path: docs/content.zh/docs/ops/state/checkpointing_under_backpressure.md
##########
@@ -129,6 +129,21 @@ In-flight 数据后再生成 Watermark **。如果您的 Pipeline 中使用了**
使用对齐 Checkpoint产生**不同的结果**。如果您的 Operator 依赖于最新的 Watermark 始终可用，解决办法是将 Watermark
存放在 OperatorState 中。在这种情况下，Watermark 应该使用单键 group 存放在 UnionState 以方便扩缩容。
+#### Interplay with long-running record processing
+
+Despite that unaligned checkpoints barriers are able to overtake all other records in the queue.
+The handling of this barrier still can be delayed if the current record takes a lot of time to be processed.
+This situation can occur when firing many timers all at once, for example in windowed operations.
+Second problematic scenario might occur when system is being blocked waiting for more than one
+network buffer availability when processing a single input record. Flink can not interrupt processing of
+a single input record, and unaligned checkpoints have to wait for the currently processed record to be
+fully processed. This can cause problems in two scenarios. Either as a result of serialisation of a large
+record that doesn't fit into single network buffer or in a flatMap operation, that produces many output
+records for one input record. In such scenarios back pressure can block unaligned checkpoints until all
+the network buffers required to process the single input record are available.
+It also can happen in any other situation when the processing of the single record takes a while(a long record).
+As result, the time of the checkpoint can be higher than expected or it can be volatile from time to time.
Review comment:
```suggestion
As result, the time of the checkpoint can be higher than expected or it can vary.
```
##########
File path: docs/content.zh/docs/ops/state/checkpointing_under_backpressure.md
##########
@@ -129,6 +129,21 @@ In-flight 数据后再生成 Watermark **。如果您的 Pipeline 中使用了**
使用对齐 Checkpoint产生**不同的结果**。如果您的 Operator 依赖于最新的 Watermark 始终可用，解决办法是将 Watermark
存放在 OperatorState 中。在这种情况下，Watermark 应该使用单键 group 存放在 UnionState 以方便扩缩容。
+#### Interplay with long-running record processing
+
+Despite that unaligned checkpoints barriers are able to overtake all other records in the queue.
+The handling of this barrier still can be delayed if the current record takes a lot of time to be processed.
+This situation can occur when firing many timers all at once, for example in windowed operations.
+Second problematic scenario might occur when system is being blocked waiting for more than one
+network buffer availability when processing a single input record. Flink can not interrupt processing of
+a single input record, and unaligned checkpoints have to wait for the currently processed record to be
+fully processed. This can cause problems in two scenarios. Either as a result of serialisation of a large
+record that doesn't fit into single network buffer or in a flatMap operation, that produces many output
+records for one input record. In such scenarios back pressure can block unaligned checkpoints until all
+the network buffers required to process the single input record are available.
+It also can happen in any other situation when the processing of the single record takes a while(a long record).
Review comment:
```suggestion
It also can happen in any other situation when the processing of the single record takes a while.
```
I think I would drop the "a long record"
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] pnowojski merged pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
pnowojski merged pull request #18354:
URL: https://github.com/apache/flink/pull/18354
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] akalash commented on a change in pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
akalash commented on a change in pull request #18354:
URL: https://github.com/apache/flink/pull/18354#discussion_r786124665
##########
File path: docs/content.zh/docs/ops/state/checkpointing_under_backpressure.md
##########
@@ -129,6 +129,10 @@ In-flight 数据后再生成 Watermark **。如果您的 Pipeline 中使用了**
使用对齐 Checkpoint产生**不同的结果**。如果您的 Operator 依赖于最新的 Watermark 始终可用，解决办法是将 Watermark
存放在 OperatorState 中。在这种情况下，Watermark 应该使用单键 group 存放在 UnionState 以方便扩缩容。
+#### Interplay with long-running record processing
+
+Despite that unaligned checkpoints barriers are able to overtake all other records in the queue. The handling of this barrier still can be delayed if the current record takes a lot of time to be processed. This situation can occur when window operators emit heavy result or the flat map produce a lot of records for a single input. It also can happen in any other situation when the processing of the single record takes a while(a long record). As result, the time of the checkpoint can be higher than expected or it can be volatile from time to time.
Review comment:
I have updated the current commit
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
flinkbot commented on pull request #18354:
URL: https://github.com/apache/flink/pull/18354#issuecomment-1012224474
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.
## Automated Checks
Last check on commit 7aae8934af87bb2cdba40facc91ad0ed266df2b4 (Thu Jan 13 15:08:57 UTC 2022)
✅no warnings
<sub>Mention the bot in a comment to re-run the automated checks.</sub>
## Review Progress
* ❓ 1. The [description] looks good.
* ❓ 2. There is [consensus] that the contribution should go into to Flink.
* ❓ 3. Needs [attention] from.
* ❓ 4. The change fits into the overall [architecture].
* ❓ 5. Overall code [quality] is good.
Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process.<details>
The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required <summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`)
- `@flinkbot approve all` to approve all aspects
- `@flinkbot approve-until architecture` to approve everything until `architecture`
- `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention
- `@flinkbot disapprove architecture` to remove an approval you gave earlier
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on pull request #18354:
URL: https://github.com/apache/flink/pull/18354#issuecomment-1014449494
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"status" : "CANCELED",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29563",
"triggerID" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"triggerType" : "PUSH"
}, {
"hash" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"status" : "PENDING",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29585",
"triggerID" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* 7aae8934af87bb2cdba40facc91ad0ed266df2b4 Azure: [CANCELED](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29563)
* 80cc40f2dc4121c04d58da7f8c91202094625869 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29585)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run azure` re-run the last Azure build
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on pull request #18354:
URL: https://github.com/apache/flink/pull/18354#issuecomment-1014449494
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"status" : "DELETED",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29563",
"triggerID" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"triggerType" : "PUSH"
}, {
"hash" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"status" : "FAILURE",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29585",
"triggerID" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* 80cc40f2dc4121c04d58da7f8c91202094625869 Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29585)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run azure` re-run the last Azure build
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on pull request #18354:
URL: https://github.com/apache/flink/pull/18354#issuecomment-1014449494
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"status" : "PENDING",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29563",
"triggerID" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* 7aae8934af87bb2cdba40facc91ad0ed266df2b4 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29563)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run azure` re-run the last Azure build
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on pull request #18354:
URL: https://github.com/apache/flink/pull/18354#issuecomment-1014449494
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"status" : "PENDING",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29563",
"triggerID" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"triggerType" : "PUSH"
}, {
"hash" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"status" : "PENDING",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29585",
"triggerID" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* 7aae8934af87bb2cdba40facc91ad0ed266df2b4 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29563)
* 80cc40f2dc4121c04d58da7f8c91202094625869 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29585)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run azure` re-run the last Azure build
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on pull request #18354:
URL: https://github.com/apache/flink/pull/18354#issuecomment-1014449494
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"status" : "DELETED",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29563",
"triggerID" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"triggerType" : "PUSH"
}, {
"hash" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"status" : "DELETED",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29585",
"triggerID" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"triggerType" : "PUSH"
}, {
"hash" : "c1441dd55ff1b42c6d9537eb55a4b96a3cf0c46e",
"status" : "SUCCESS",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29660",
"triggerID" : "c1441dd55ff1b42c6d9537eb55a4b96a3cf0c46e",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* c1441dd55ff1b42c6d9537eb55a4b96a3cf0c46e Azure: [SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29660)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run azure` re-run the last Azure build
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] akalash commented on a change in pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
akalash commented on a change in pull request #18354:
URL: https://github.com/apache/flink/pull/18354#discussion_r786110821
##########
File path: docs/content.zh/docs/ops/state/checkpointing_under_backpressure.md
##########
@@ -129,6 +129,10 @@ In-flight 数据后再生成 Watermark **。如果您的 Pipeline 中使用了**
使用对齐 Checkpoint产生**不同的结果**。如果您的 Operator 依赖于最新的 Watermark 始终可用，解决办法是将 Watermark
存放在 OperatorState 中。在这种情况下，Watermark 应该使用单键 group 存放在 UnionState 以方便扩缩容。
+#### Interplay with long-running record processing
+
+Despite that unaligned checkpoints barriers are able to overtake all other records in the queue. The handling of this barrier still can be delayed if the current record takes a lot of time to be processed. This situation can occur when window operators emit heavy result or the flat map produce a lot of records for a single input. It also can happen in any other situation when the processing of the single record takes a while(a long record). As result, the time of the checkpoint can be higher than expected or it can be volatile from time to time.
Review comment:
As I see, we call it `network buffers` in documentation
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on pull request #18354:
URL: https://github.com/apache/flink/pull/18354#issuecomment-1014449494
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"status" : "PENDING",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29563",
"triggerID" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"triggerType" : "PUSH"
}, {
"hash" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"status" : "UNKNOWN",
"url" : "TBD",
"triggerID" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* 7aae8934af87bb2cdba40facc91ad0ed266df2b4 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29563)
* 80cc40f2dc4121c04d58da7f8c91202094625869 UNKNOWN
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run azure` re-run the last Azure build
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
flinkbot commented on pull request #18354:
URL: https://github.com/apache/flink/pull/18354#issuecomment-1014449494
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"status" : "UNKNOWN",
"url" : "TBD",
"triggerID" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* 7aae8934af87bb2cdba40facc91ad0ed266df2b4 UNKNOWN
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run azure` re-run the last Azure build
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on pull request #18354:
URL: https://github.com/apache/flink/pull/18354#issuecomment-1014449494
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"status" : "DELETED",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29563",
"triggerID" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"triggerType" : "PUSH"
}, {
"hash" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"status" : "FAILURE",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29585",
"triggerID" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"triggerType" : "PUSH"
}, {
"hash" : "c1441dd55ff1b42c6d9537eb55a4b96a3cf0c46e",
"status" : "PENDING",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29660",
"triggerID" : "c1441dd55ff1b42c6d9537eb55a4b96a3cf0c46e",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* 80cc40f2dc4121c04d58da7f8c91202094625869 Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29585)
* c1441dd55ff1b42c6d9537eb55a4b96a3cf0c46e Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29660)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run azure` re-run the last Azure build
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #18354: [FLINK-25650][docs] Added "Interplay with long-running record process…
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on pull request #18354:
URL: https://github.com/apache/flink/pull/18354#issuecomment-1014449494
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"status" : "DELETED",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29563",
"triggerID" : "7aae8934af87bb2cdba40facc91ad0ed266df2b4",
"triggerType" : "PUSH"
}, {
"hash" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"status" : "FAILURE",
"url" : "https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29585",
"triggerID" : "80cc40f2dc4121c04d58da7f8c91202094625869",
"triggerType" : "PUSH"
}, {
"hash" : "c1441dd55ff1b42c6d9537eb55a4b96a3cf0c46e",
"status" : "UNKNOWN",
"url" : "TBD",
"triggerID" : "c1441dd55ff1b42c6d9537eb55a4b96a3cf0c46e",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* 80cc40f2dc4121c04d58da7f8c91202094625869 Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=29585)
* c1441dd55ff1b42c6d9537eb55a4b96a3cf0c46e UNKNOWN
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run azure` re-run the last Azure build
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org