Chris, In terms of round robin-ing between the repositories, yes, it follows a simple round-robin approach. In terms of sections within those containers, the answer is more of a "sort-of." Each FlowFile has what we refer to as a Resource Claim, which points to a location in the content repository. In the case of the FileSystemRepository (which is the default and almost all that's ever used right now), the Resource Claim maps to a file on disk. In order to be very efficient, we may write many FlowFiles to the same Resource Claim.
Once we finish writing to a particular Resource Claim, we close the resources and create a new one for the next FlowFile. When we create these Resource Claims, we do so in a round-robin fashion across the different Sections of the content repository. Sorry, this is a fairly long-winded answer to such a seemingly simple question :) but I wasn't sure how much detail you were looking for. If anything is not clear, let us know. Thanks -Mark > On Nov 25, 2015, at 5:12 AM, Chris Lim <[email protected]> wrote: > > Hi Guys, > > I am configuring our NiFi instance to have multiple content repositories > specifically with the "nifi.content.repository.directory." property setting > as mentioned in the Administrator's guide. Am I correct that flow file > contents are written to the repository using a round-robin algorithm? Also, > does the sections within a specific content repository follow the same > round-robin algorithm? > > Thanks, > Chris >
