wjmmjr commented on PR #16000: URL: https://github.com/apache/dolphinscheduler/pull/16000#issuecomment-2113860672
> > > -1 to this PR, you need to create DSIP first, I am not clear why this will cause `user confusion` and why set the uid can solve this? > > > > > > When deploying worker services using k8s, the user information in the container will be cleared after restarting the worker service, and the newly created users will not correspond to the users in the metadata table. Migrating services to new physical machines may also cause this issue. You can use native code for testing > > The main change in this pr is set the uid, please describe why the uid will affect this. We didn't meet this problem before. When deploying the dolphinscheduler worker service in a k8s environment and mounting PVC, all files in the PVC have corresponding users. When the dolphinscheduler worker service restarts, the users in the container are cleared, and the users are recreated in order of connecting to the dolphinscheduler worker. At this time, the username and userid are not consistent with the situation before restarting. Due to the username and userid matching in the PVC file, the user corresponding to the PVC file is incorrect after restarting the container -- 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]
