ASF subversion and git services commented on NIFI-4775:

Commit 5f696482b06b868c88a96cf6666e21642dea386b in nifi's branch 
refs/heads/master from Brandon Rhys DeVries
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5f69648 ]

NIFI-4775: Updating documentation and updating rocksdb version

NIFI-4775: Rolling back fix for NIFI-6416

NIFI-4775: Documentation improvements

+1 from markobean

This closes #3648

Signed-off-by: Brandon <devri...@apache.org>

> Create a FlowFile repo backed by RocksDB
> ----------------------------------------
>                 Key: NIFI-4775
>                 URL: https://issues.apache.org/jira/browse/NIFI-4775
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Brandon DeVries
>            Priority: Major
>             Fix For: 1.10.0
>         Attachments: RocksDBFlowFileRepo.html, rocksdb-flowfile-repo.adoc
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
> Currently, when a FlowFile is written to the FlowFile Repository, the repo 
> can either fsync or not, depending on nifi.properties. We should allow a 
> third option, of fsync only for CREATE events. In this case, if we receive 
> new data from a source we can fsync the update to the FlowFile Repository 
> before ACK'ing the data from the source. This allows us to guarantee data 
> persistence without the overhead of an fsync for every FlowFile Repository 
> update.
> It may make sense, though, to be a bit more selective about when do this. For 
> example if the source is a system that does not allow us to acknowledge the 
> receipt of data, such as a ListenUDP processor, this doesn't really buy us 
> much. In such a case, we could be smart about avoiding the high cost of an 
> fsync. However, for something like GetSFTP where we have to remove the file 
> in order to 'acknowledge receipt' we can ensure that we wait for the fsync 
> before proceeding.
> NOTE: This functionality was ultimately provided in a new implementation 
> backed by RocksDB

This message was sent by Atlassian JIRA

Reply via email to