Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Fileservices.RemoveSuperFile - strange behavior.

Description

Simple call. WU: W20150604-230404 boca_prod
FileServices.RemoveSuperFile('~thor_data400::in::utility::full_daily','~thor_data400::in::eq_utils_new_20150604');

It says in the ECLAgent log.
00000009 2015-06-04 23:04:38.430 4389 4389 "Obtained run lock"
0000000A 2015-06-04 23:40:17.006 4389 4389 "WARNING: addSubFile: File thor_data400::in::eq_utils_new_20150604 is not a subfile of thor_data400::in::utility::full_daily"
0000000B 2015-06-04 23:40:17.010 4389 4389 "CDFAction lock timed out on thor_data400::in::utility::full_daily"
0000000C 2015-06-04 23:40:18.555 4389 4389 "CDistributedFileTransaction: Transaction pausing"

20 minutes after this went into pause mode, I aborted. Shouldn't this have released the lock and failed?

Additionally, When I look at the logical file through ECL Watch it shows that it is a member of this Superfile.

Conclusion

None

Activity

Show:

Jacob Cobbett-Smith June 9, 2015 at 1:21 PM

>0000000A 2015-06-04 23:40:17.006 4389 4389 "WARNING: addSubFile: File thor_data400::in::eq_utils_new_20150604 is not a subfile of thor_data400::in::utility::full_daily"

That warning is actually from removeSubFile (error text was wrong), corrected in 5.2.0 https://hpccsystems.atlassian.net/browse/HPCC-12638

At the time of the call it must have indeed be missing from the super.

However, I agree it's odd that it proceeded to lock.
If the file were present, then the semantics are to block if the super is locked for read (as it presumably was here)
But the fact it was trying to remove a subfile that wasn't a subfile (at the time) should have meant it just aborted yes.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Pull Request URL

Affects versions

Created June 5, 2015 at 4:29 AM
Updated July 23, 2015 at 4:38 PM
Resolved July 22, 2015 at 8:51 AM