andygrove commented on PR #2514: URL: https://github.com/apache/datafusion-ballista/pull/2514#issuecomment-5950904957
Worth noting that this PR does have implications for rolling upgrades. Across a major version upgrade there's no order that keeps every client working. Clients still on the old major are rejected once the scheduler moves to the new one, and a client that upgrades first won't work with the old scheduler. So clients and the cluster have to move to a new major together, and clients will see errors in between. That's better than wrong results, but it isn't a rolling upgrade story. #2071 covered rolling upgrades for schedulers and executors, but clients weren't part of that. We probably need to come up with a real design for this at some point. -- 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]
