Abstract
Workflow provenance data represents the workflow execution behavior, allowing for tracing the generation of the scientific data-flow. Provenance is an important asset to analyze data, identify and handle errors that occurred during the workflow execution through runtime monitoring. The workflow execution engine can also use provenance data to set the initial amount of resources and plan adaptive task scheduling. However, efficiently managing provenance data from distributed workflow execution has several challenges. As the size of workflows increases (in terms of number of activity executions or volume of data to process), the amount of provenance data to be managed also grows, especially in fine grain. Thus, centralized approaches become unviable. In this work we propose an architecture that combines distributed workflow management techniques with distributed provenance data management.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
