Hi,
I'm new to the forum, tried the search function but found no topic yet that tackles the problem...
Using Workflow Manager 1.0.0.155
My workflow basically does the following:
Watchfolder --> Transcode to XDCAM 50 --> Change file names (Operations processor) --> delivery to Folder --> delivery to FTP (--> delete Original).
The machine used can handle 8 jobs at a time... what I would need to do is to make the FTP delivery node to only make one connection to the FTP server or only write one File to the server at a time. I get FTP delivery errors if FFASTrans tries to write multiple files simultaneously to the server I (have to) use.
The other part of the transcoding could proceed in the meantime (converting to XDCAM 50 and writing in the output folder), but
Is there any way to achieve "one connection / one file at a time" with a conditional node (check if FTP is transferring and hold till the transfer is done) or could I put this step of the delivery process in a separate workflow, basically only Watchfolder --> FTP delivery that is only executed once and not eight times when there are eight new files in the watchfolder?
Thanks for your help!
Best,
Ralph
Limit FTP delivery to one transfer at a time
Re: Limit FTP delivery to one transfer at a time
Hey @Ralph, welcome to the forum and thank you for using ffastrans! Glad you joined us here.
OK, first thing, please upgrade to 1.0.0.5, look on ffastrans.com for the "Bugfix update 1.0.0.5"
So, i see multiple possible solutions for you to limit the number of paralell FTP uploads down to one. Here are some, you can pick the one you like most
1) introduce a second ffastrans host as described in "complex deployment- Farm" here: http://ffastrans.com/wiki/doku.php?id=g ... e&s[]=farm - separate the ftp watchfolder and upload into a single workflow and set this workflow to run on the second ffastrans server. Configure your second ffastrans server to run only one job paralell
2) build a workflow without a monitor processor, start with the custom processor "files find" and set it to find all files to upload to ftp. Then connect an ftp node and upload only the first found file. Use the Webinterface scheduler to start the workflow every 1 Minute. If no file was found, set %s_source% to "" using a populate processor - this will delete the job from job history so you dont have one job every minute in your monitor that actually didnt do anything
3) ask me for a nodejs scritp that finds files and starts a simple workflow that only does ftp upload and delete. - same as above, use the webinterface scheduler to start the searching for files every minute
4) use this solution: viewtopic.php?f=5&t=875&p=5398&hilit=li ... lows#p5387
Here you can download the "additional processors" like files find:
http://ffastrans.com/wiki/doku.php?id=c ... processors
And yes, it is time for me to come up with a processor that starts a sub-workflow and also can wait for the sub-workflow to end but i don't think this would solve your problem
5) let me know any doubt
OK, first thing, please upgrade to 1.0.0.5, look on ffastrans.com for the "Bugfix update 1.0.0.5"
So, i see multiple possible solutions for you to limit the number of paralell FTP uploads down to one. Here are some, you can pick the one you like most
1) introduce a second ffastrans host as described in "complex deployment- Farm" here: http://ffastrans.com/wiki/doku.php?id=g ... e&s[]=farm - separate the ftp watchfolder and upload into a single workflow and set this workflow to run on the second ffastrans server. Configure your second ffastrans server to run only one job paralell
2) build a workflow without a monitor processor, start with the custom processor "files find" and set it to find all files to upload to ftp. Then connect an ftp node and upload only the first found file. Use the Webinterface scheduler to start the workflow every 1 Minute. If no file was found, set %s_source% to "" using a populate processor - this will delete the job from job history so you dont have one job every minute in your monitor that actually didnt do anything
3) ask me for a nodejs scritp that finds files and starts a simple workflow that only does ftp upload and delete. - same as above, use the webinterface scheduler to start the searching for files every minute
4) use this solution: viewtopic.php?f=5&t=875&p=5398&hilit=li ... lows#p5387
Here you can download the "additional processors" like files find:
http://ffastrans.com/wiki/doku.php?id=c ... processors
And yes, it is time for me to come up with a processor that starts a sub-workflow and also can wait for the sub-workflow to end but i don't think this would solve your problem
5) let me know any doubt
emcodem, wrapping since 2009 you got the rhyme?