You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/10 13:14:00 UTC
[jira] [Commented] (NIFI-5645) Auto reconnect
ConsumeWindowsEventLog if no log is consumed for configured time period
[ https://issues.apache.org/jira/browse/NIFI-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644944#comment-16644944 ]
ASF GitHub Bot commented on NIFI-5645:
--------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/3037
Will review...
> Auto reconnect ConsumeWindowsEventLog if no log is consumed for configured time period
> --------------------------------------------------------------------------------------
>
> Key: NIFI-5645
> URL: https://issues.apache.org/jira/browse/NIFI-5645
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.0.0
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Priority: Major
>
> While ConsumeWindowsEventLog is running, if Windows Event Log service is restarted, or ERROR_EVT_QUERY_RESULT_STALE (15011) is returned, the processor keeps running, but will not receive further log events.
> Current work-around is restarting the processor manually.
> We could implement auto-reconnect logic like below, so that the processor can recover from such situation automatically.
> * Add a new processor property, ''Inactive duration to reconnect", e.g. "3 mins"
> * At onTrigger, check how long has it passed since the last message was received. If it exceeds the configured duration, reset the consumer
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)