You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matthew Clarke (JIRA)" <ji...@apache.org> on 2017/11/13 21:14:00 UTC

[jira] [Commented] (NIFI-4602) TailFile does not recover cluster-wide state when Primary Node changes

    [ https://issues.apache.org/jira/browse/NIFI-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16250246#comment-16250246 ] 

Matthew Clarke commented on NIFI-4602:
--------------------------------------

Need to verify what happens when a log rolls.  Will the new primary node be able to pick up by grabbing lines from rolled log or will it just start tailing the latest log?


> TailFile does not recover cluster-wide state when Primary Node changes
> ----------------------------------------------------------------------
>
>                 Key: NIFI-4602
>                 URL: https://issues.apache.org/jira/browse/NIFI-4602
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>
> I created a TailFile processor and set the "File Location" property to "Remote." I then added some text to a file and started the TailFile processor (Primary Node Only).
> I disconnected the primary node from the cluster. A second node became the new Primary Node and continued tailing the data as expected. As new data was added, the node continued to emit FlowFiles.
> Then, I added Node 1 back to the cluster. Verified that Node 2 continued to poll data. I then disconnected Node 2 so that Node 1 once again became the Primary Node. At this point, Node 1 continued tailing from where it last left off, not where Node 2 left off.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)