[FALCON-1366] Process vertex in graphDb is committed before process submission is complete

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Invalid
• Affects Version/s: 0.6.1
• Fix Version/s: 0.7
• Assignee: Balu Vellanki
• Reporter: Balu Vellanki
• Created: 03/Aug/15 21:39
• Updated: 04/Aug/15 01:06
• Resolved: 04/Aug/15 01:06

Description

To reproduce the problem, submit a feed "TestFeed" with validity start as "2015-07-31 08:56" and End as "2015-07-31 10:00". Now using the UI, submit a process with validity start "2015-07-30 08:56" that will write output to "TestFeed", this will fail with error

Instance now(0,0) of feed TestFeed is before the start of feed Fri Jul 31 08:56:00 UTC 2015 for cluster primaryCluster

Now fix the validity time start and end of process, make it same as validity start and end of feed. Resubmit the process. It fails with Titan graphDB error.

Could not commit transaction due to exception during persistence

This is happening because the process name is committed to graphDB even before the process submission is successful in the config store. This needs to be fixed.