Skip to main content
Question

Lost records using Workspace runner

  • November 19, 2022
  • 1 reply
  • 9 views

albinepro
Supporter
Forum|alt.badge.img+7

I have been tweaking workspace briefly described in this question for better performance and encountered weird behaviour on setting up worskpace runner parameters. The workspace is loading XML data, parsing and fetching results to PostGIS database. When I setup the workspace runner to 4 concurrent processes and 4 workspace runs per process I end up with some features not being written. On contrary running directly the child workspace or setting up the workspace runner to just 1 concurrent proccess, all features are being written.

On the comparison you can see limited features written (left, import_RUIAN_c4_w4.log) and all features (right, import_runner_c1_w1.log) from the same XML:

logs.pngLooks like some translations fails in concurrent processes trying to delete some file:

ERROR |AttributeKeeper_6 (AttributeKeeperFactory): Failed to delete the following files: 'D:\Zakazky\APHA\FME\per_partes\import_RUIAN_1b_zapis_log.ffs'.  Please ensure that the files are not in use and that you have sufficient privileges to delete them.

How to prevent failing some of the workspace with more concurrent processes? It would greatly improve the performance. Mentioned logs attached.

EDIT:

I would need the workspace runner to stop writing FFS files. Feature caching is off. How to prevent this?

1 reply

albinepro
Supporter
Forum|alt.badge.img+7
  • Author
  • Supporter
  • January 3, 2023

I've probably found out a solution in better definition of Attribute Creator - adding up a condition to write null in case attibute is missing, so FME won't raise a warning in that case and stops to write FFS file.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings