[
https://issues.apache.org/jira/browse/NIFI-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946768#comment-16946768
]
Lei Wang commented on NIFI-6428:
--------------------------------
Hi Koji,
I am using the CaptureChangeMySQL to replicate my database. When the nifi
cluster do a primary swith or restarted, the binlog position often do not go
on with previous value. By looking the code, I think this is also caused by
the inTransaction instance.
How about add inTransaction to state-managed value？
I think this can resolve my problem.
> CaptureChangeMySQL throws IOException with BIGIN event due to lingering
> 'inTransaction' instance variable
> ---------------------------------------------------------------------------------------------------------
>
> Key: NIFI-6428
> URL: https://issues.apache.org/jira/browse/NIFI-6428
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Koji Kawamura
> Priority: Major
>
> Because of not clearing 'inTransaction' instance variable when the processor
> stops, when a user clears processor state and restart it with a specific
> initial binlog position, then if BEGIN event is received, the processor
> throws an IOException.
> The processor should reset 'inTransaction' to false, and also other instance
> variables when it start with an empty processor state.
> The issue was reported at NiFi user ML.
> [https://mail-archives.apache.org/mod_mbox/nifi-users/201907.mbox/%3C2019070919385393266224%40geekplus.com.cn%3E]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
