[
https://issues.apache.org/jira/browse/NIFI-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077577#comment-16077577
]
ASF GitHub Bot commented on NIFI-4155:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/1984
@JPercivall Thanks for your comment. Yes, I concerned about it may hammer
Zk, too. But now we have [Redis backed state
manager](https://github.com/apache/nifi/tree/master/nifi-nar-bundles/nifi-redis-bundle/nifi-redis-extensions/src/main/java/org/apache/nifi/redis/state)
too. That can perform well compared to Zk. Also I wrote [doc for Cluster
scope](https://github.com/apache/nifi/pull/1984/files#diff-64bdb3d4f3927cdfb538dd95975af65aR189)
to use it only if necessary, it wouldn't be enough, though..
I think 'being able to do something if they know what they're doing' is
better than not providing that option.
> Expand EnforceOrder capability to cluster
> -----------------------------------------
>
> Key: NIFI-4155
> URL: https://issues.apache.org/jira/browse/NIFI-4155
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
>
> Currently, EnforceOrder is able to enforce FlowFile ordering within a NiFi
> node, and it uses local managed state to track progress.
> If it is configurable which state management to use from Local and Cluster,
> EnforceOrder would be also able to enforce ordering across cluster with
> cluster scope state management. It would be useful for some use-cases.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
