[
https://issues.apache.org/jira/browse/NIFI-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197991#comment-15197991
]
Mark Payne commented on NIFI-1626:
----------------------------------
[~JPercivall] - I agree that this should be spelled out a bit more in
documentation. However, I think the Developer Guide is a more appropriate place
than the Admin Guide, as the developer ultimately is responsible for knowing
the type of data that is going to be stored there and should use a different
mechanism if the data is expected to grow being this limitation. I did update
the Developer Guide as suggested and realized that the State Management section
was actually outdated and did not reflect the API as it was published in 0.5.0.
I updated the Developer Guide to be more accurate wrt the API, as well.
> ZooKeeper State Provider should block requests > 1 MB
> -----------------------------------------------------
>
> Key: NIFI-1626
> URL: https://issues.apache.org/jira/browse/NIFI-1626
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments:
> 0001-NIFI-1626-Throw-an-Exception-proactively-if-too-much.patch,
> 0001-NIFI-1626-Updated-State-Management-section-of-Develo.patch
>
>
> ZooKeeper does not support setting data on a ZNode to a value greater than 1
> MB. However, the client doesn't does not check this - it sends the data to
> the server and lets the server reject the request. This can cause problems
> with ZooKeeper if the requests grow extremely large. As a result, we should
> prevent this from ever happening by throwing an Exception ourselves if
> attempting to set state to a value > 1 MB
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
