Concurrent system jobs in Scale?

[EtienneB]

Hello,

I have sidegraded from Core to Scale last night. And I need to change some user permissions on folders because of Apps mainly.
Currently, I am changing a folder with 7TB or so data in it, which will take hours/days to complete I see.
In the mean time, when I want to add a dataset (even to another pool), or change a user setting (like adding an SSH key), it just queues them (waiting… it says under Jobs).

Is there a way to have some jobs to run concurrently? I understand you don’t want to mess with child datasets in a dataset that has pending ACL settings. But other actions all seem to be queued while I think you should be able to process them, like even ACL settings on smaller datasets separate from the large one.

Thanks

[EtienneB]

I found this post

Slow while setting ACL on RAIDDZ2 40Tb HDD dataset

Are you setting ACLs on the same datasets or separate ones? We set a global setacl lock in middleware to prevent users from clobbering same paths and to prevent overload. This could probably be relaxed to allow multiple ones on different datasets. If you’re recursing through millions of files it will potentially take a significant amount of time to complete since we have to write an ACL on every file and you’re probably iops constrained. The ACL setting application is written in C and using fts(…

In the mean time, the ACL change has been running for over 2 days, I do see progress in the shell, and expect I need another 2 full days for this dataset alone.