Support Questions

Find answers, ask questions, and share your expertise

Slow FTP downloads with NiFi

New Contributor

Hello guys! I'm new to this forum and to NiFi as well.

I'm trying to connect to an external FTP site, using ListFTP and FetchFTP processors on NiFi. The ListFTP object puts all files in a queue very fast, but the FetchFTP processor takes a lot of time to download the files, even using 5 threads on the FetchFTP it downloads 5 files and stand still for 30 seconds before starting the downloads again.

I've tried to download the same files via an external app, like Filezilla and the downloads are made in seconds.

Is there anything I can do to speed up this process?

Update:

I've tried using the GetFTP processor and it worked as fast as FileZilla. It seems that FetchFTP has some Polling Interval that isn't changeable by property.

15 REPLIES 15

@Denis Urbanavicius

Are NiFi and Filezilla running on the same system or different systems?

New Contributor

@Wynner

Yes, everything is running on the same machine.

@Denis Urbanavicius

How is the FetchFTP processor configured?

New Contributor

@Wynner

The only properties that aren't visible on this picture are hostname, port, user and password.

I've tried changing the Connection Timeout and Data Timeout, without any success.

27484-capturar.jpg

@Denis Urbanavicius

Try running the FetchFTP with a Completion Strategy of Delete File.

Does that make any difference?

New Contributor

I've tried using Delete File as Completion Strategy but it's still slow.

@Denis Urbanavicius

How is the Scheduling tab of the FetchFTP processor configured?

Concurrent tasks and run schedule.

New Contributor

5 concurrent tasks, 1 second run schedule

@Denis Urbanavicius

Try setting the run schedule to 0.

Explorer

Even I have similar issue. My FetchSFTP processor doesn't download large files. 

 

I am trying to download any file that is uploaded to FTP server. 

This is what I came up with -

 

image.png

 

It works perfectly for small files. For large files, the process stops at FectchSFTP processor. 

 

Here is the template - 

https://drive.google.com/file/d/1nPz6uUEwdYEopTH_7N1pDsvlX5Qx4uHu/view?usp=sharing

 

Can someone help please.?

@Wynner @denis_urbanavic 

 

Thanks.

 

 

Can you provide information about spec and configuration of NiFi?   Number Nodes, memory settings, disk size, are partitions configured separately?, etc..

Explorer

@stevenmatison 

Here you go - 

 

There is only 1 node (Standalone).

 
# Core Properties #
nifi.flow.configuration.file=./conf/flow.xml.gz
nifi.flow.configuration.archive.enabled=true
nifi.flow.configuration.archive.dir=./conf/archive/
nifi.flow.configuration.archive.max.time=30 days
nifi.flow.configuration.archive.max.storage=500 MB
nifi.flow.configuration.archive.max.count=
nifi.flowcontroller.autoResumeState=true
nifi.flowcontroller.graceful.shutdown.period=10 sec
nifi.flowservice.writedelay.interval=500 ms
nifi.administrative.yield.duration=30 sec
# If a component has no work to do (is "bored"), how long should we wait before checking again for work?
nifi.bored.yield.duration=10 millis
nifi.queue.backpressure.count=10000
nifi.queue.backpressure.size=1 GB

nifi.authorizer.configuration.file=./conf/authorizers.xml
nifi.login.identity.provider.configuration.file=./conf/login-identity-providers.xml
nifi.templates.directory=./conf/templates
nifi.ui.banner.text=
nifi.ui.autorefresh.interval=30 sec
nifi.nar.library.directory=./lib
nifi.nar.library.autoload.directory=./extensions
nifi.nar.working.directory=./work/nar/
nifi.documentation.working.directory=./work/docs/components

####################
# State Management #
####################
nifi.state.management.configuration.file=./conf/state-management.xml
# The ID of the local state provider
nifi.state.management.provider.local=local-provider
# The ID of the cluster-wide state provider. This will be ignored if NiFi is not clustered but must be populated if running in a cluster.
nifi.state.management.provider.cluster=zk-provider
# Specifies whether or not this instance of NiFi should run an embedded ZooKeeper server
nifi.state.management.embedded.zookeeper.start=false
# Properties file that provides the ZooKeeper properties to use if <nifi.state.management.embedded.zookeeper.start> is set to true
nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties


# H2 Settings
nifi.database.directory=./database_repository
nifi.h2.url.append=;LOCK_TIMEOUT=25000;WRITE_DELAY=0;AUTO_SERVER=FALSE

# FlowFile Repository
nifi.flowfile.repository.implementation=org.apache.nifi.controller.repository.WriteAheadFlowFileRepository
nifi.flowfile.repository.wal.implementation=org.apache.nifi.wali.SequentialAccessWriteAheadLog
nifi.flowfile.repository.directory=./flowfile_repository
nifi.flowfile.repository.partitions=256
nifi.flowfile.repository.checkpoint.interval=2 mins
nifi.flowfile.repository.always.sync=false

nifi.swap.manager.implementation=org.apache.nifi.controller.FileSystemSwapManager
nifi.queue.swap.threshold=20000
nifi.swap.in.period=5 sec
nifi.swap.in.threads=1
nifi.swap.out.period=5 sec
nifi.swap.out.threads=4

# Content Repository
nifi.content.repository.implementation=org.apache.nifi.controller.repository.FileSystemRepository
nifi.content.claim.max.appendable.size=1 MB
nifi.content.claim.max.flow.files=100
nifi.content.repository.directory.default=./content_repository
nifi.content.repository.archive.max.retention.period=12 hours
nifi.content.repository.archive.max.usage.percentage=50%
nifi.content.repository.archive.enabled=true
nifi.content.repository.always.sync=false
nifi.content.viewer.url=../nifi-content-viewer/

# Provenance Repository Properties
nifi.provenance.repository.implementation=org.apache.nifi.provenance.WriteAheadProvenanceRepository
nifi.provenance.repository.debug.frequency=1_000_000
nifi.provenance.repository.encryption.key.provider.implementation=
nifi.provenance.repository.encryption.key.provider.location=
nifi.provenance.repository.encryption.key.id=
nifi.provenance.repository.encryption.key=

# Persistent Provenance Repository Properties
nifi.provenance.repository.directory.default=./provenance_repository
nifi.provenance.repository.max.storage.time=24 hours
nifi.provenance.repository.max.storage.size=1 GB
nifi.provenance.repository.rollover.time=30 secs
nifi.provenance.repository.rollover.size=100 MB
nifi.provenance.repository.query.threads=2
nifi.provenance.repository.index.threads=2
nifi.provenance.repository.compress.on.rollover=true
nifi.provenance.repository.always.sync=false
# Comma-separated list of fields. Fields that are not indexed will not be searchable. Valid fields are:
# EventType, FlowFileUUID, Filename, TransitURI, ProcessorID, AlternateIdentifierURI, Relationship, Details
nifi.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship
# FlowFile Attributes that should be indexed and made searchable. Some examples to consider are filename, uuid, mime.type
nifi.provenance.repository.indexed.attributes=
# Large values for the shard size will result in more Java heap usage when searching the Provenance Repository
# but should provide better performance
nifi.provenance.repository.index.shard.size=500 MB
# Indicates the maximum length that a FlowFile attribute can be when retrieving a Provenance Event from
# the repository. If the length of any attribute exceeds this value, it will be truncated when the event is retrieved.
nifi.provenance.repository.max.attribute.length=65536
nifi.provenance.repository.concurrent.merge.threads=2

@shailuk 

How large are the large files?

How many concurrent tasks are configured in the FetchSFTP processor?

Explorer

@Wynner 

The file is 3 gb size. 

1 concurrent task.

With that big of a file, you are going to need to adjust settings (memory) and evaluate performance of the file repositories.  I would recommend to start with small files, and work your way up.  Complete a benchmark at each stage, then begin testing config changes.  This should be a lengthy evaluation where in the end, you end up with a configuration capable of consuming 3 gb files.

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.