calvinjiang opened a new issue, #12279:
URL: https://github.com/apache/dolphinscheduler/issues/12279

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   Currently when creating a user in DolphinScheduler the API will create the 
resource directory at the same time. Sometimes the settings of storage is not 
correct, so the process of creating the resource file will throw an exception. 
But the strategy of rollback didn't work. It's because that the annotation of 
'@Transactional' just deal with the exception of the RuntimeException type by 
default.
   
   
![image](https://user-images.githubusercontent.com/4928204/194749641-ce531436-5cb8-4a3a-b46e-6c633e85aecd.png)
   
   
![image](https://user-images.githubusercontent.com/4928204/194747885-74de5537-2afe-4e48-8a61-80e0ea25ef9c.png)
   
   
   ### What you expected to happen
   
   When creating a user and throwing an exception the user shouldn't be created 
successfully.
   
   ### How to reproduce
   
   First of all you should modify the file of 'common.properties' to set a few 
settings of resource storage like:
   ```
   resource.storage.type=HDFS
   resource.storage.upload.base.path=/dolphinscheduler
   resource.hdfs.root.user=calvin
   resource.hdfs.fs.defaultFS=hdfs://xxxxxx:8020
   ```
   To make sure the user 'calvin' has no permissions to access the resource 
file '/dolphinscheduler'.
   
   And then to create a new user  you will see this problem.
   
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   dev
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to