[
https://issues.apache.org/jira/browse/APEXCORE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224941#comment-15224941
]
ASF GitHub Bot commented on APEXCORE-419:
-----------------------------------------
Github user tweise commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/293#discussion_r58437448
--- Diff:
engine/src/main/java/com/datatorrent/stram/StreamingContainerManager.java ---
@@ -1911,12 +1911,17 @@ public void updateRecoveryCheckpoints(PTOperator
operator, UpdateCheckpointsCont
ctx.committedWindowId.setValue(operator.getRecoveryCheckpoint().windowId);
}
- if (operator.getState() == PTOperator.State.ACTIVE && (ctx.currentTms
- operator.stats.lastWindowIdChangeTms) >
operator.stats.windowProcessingTimeoutMillis) {
+ if (operator.getState() == PTOperator.State.ACTIVE &&
+ (ctx.currentTms - operator.stats.lastWindowIdChangeTms) >
operator.stats.windowProcessingTimeoutMillis) {
--- End diff --
Why this change?
> When operator is blocked, print out a warning instead of debug
> --------------------------------------------------------------
>
> Key: APEXCORE-419
> URL: https://issues.apache.org/jira/browse/APEXCORE-419
> Project: Apache Apex Core
> Issue Type: Improvement
> Reporter: David Yan
> Assignee: David Yan
> Priority: Trivial
>
> This is because when an operator is blocked, it usually means something bad
> has happened and should be a warning instead of a debug statement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
