Ooyala Flex 6.0.7 Release Notes 2017-12-08
Ooyala Flex 6.0.7 is a maintenance release to fix issues found in production.
Publish job stays in "QUEUED" state while running on 18K assets hierarchy
When running a Transactional Publish job on a hierarchy of 18K assets, the job stayed in a QUEUED state, and did not proceed further.
Resolution: The error no longer occurs.
Publish: Out of memory due to large hierarchies
Ooyala Flex Publish was running out of memory when hierarchies with large numbers of items in them were being created in environments.
Resolution: When member lists were being built using the public API, they were being filtered to display only those members which had been published. However, when this filter was applied we were loading a structure called "AssetMembership" that loaded the requested asset and members. Groups with member logs would load a huge number of assets into memory, causing Publish to run out of memory.
From now on, when we build this list of members, we only verify whether the members are published or not.Move jobs repeatedly fail on Azure and S3, and cannot be retried, causing the asset path to be lost
Moving files to Blob storage fails about 60% of the time, either displaying an error that the destination already exists - which it does not - or the asset appears to be lost.
Resolution: The Check to return the file type as a "FOLDER" when the path does not have extension has been removed. This is to support files without extensions in our VFS library for Azure.
We have added a new check which returns file types as a "FOLDER" when the path ends with "/".
The MAM property that deals with session timeouts has changed from server.session.timeout to session.minutesToExpire. If a customer has not overridden the value, the default value is the same for both (30mins).