bdoyle0182 edited a comment on pull request #5065: URL: https://github.com/apache/openwhisk/pull/5065#issuecomment-782275959
Thanks for the contribution. I have a couple of thoughts / experiences with akka 2.6. We eventually undoubtedly need to upgrade this project to akka 2.6. 1. There are a lot of hidden breaking changes or changes in behavior when upgrading live clusters. For example akka http needs an intermediary upgrade to a specific patch version of 2.6.x before you can upgrade to the latest 2.6.x on a live cluster. 2. This is less for this mr, but in akka 2.6 the untyped fsm is deprectated and will be removed after the 2.6 branch. So much of this project is built on the untyped fsm. We're going to have to make a dedicated effort at some point to migrate the fsm's to typed. 3. Naver is in the process of open sourcing the new scheduler, which is a major rearchitecting of the project. These changes need to be grandfathered in to untyped / we should wait to upgrade to 2.6 until we finish the scheduler. From my own team's experience with our own services, upgrading to akka 2.6 ended up being quite the headache that was a month's long process of learning little nuances and changes in behavior. I can try to collect all of those things and communicate that knowledge with the community, hopefully that can make the process smooth. The upgrade was valuable with the new features and improvements akka 2.6 offers even with the problems we faced. We need to do this upgrade at some point to keep up with akka, but there is going to need to be more community involvement and discussion on how we want to make this happen rather than just merging the one mr. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
