imply-cheddar commented on PR #13680: URL: https://github.com/apache/druid/pull/13680#issuecomment-1399922089
So, with the `useSharedLock` context flag, if you set it on an active supervisor, the new tasks that it fires up fail over and over again until all of the previous tasks are done handing off their data. (the previous tasks still have the exclusive lock and thus the shared lock doesn't work). In order to fully make this the default, it would be the absolute bestest if these types of tasks just natively transfered over to using the shared lock without failures. Does this PR include the changes to make that happen? Or, if we were to merge, would the next release suddenly have a bunch of failed tasks the first time the code gets deployed? -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
