michaeljmarshall commented on issue #12944: URL: https://github.com/apache/pulsar/issues/12944#issuecomment-1113422906
We discussed the requirements for an Arm Docker image during our Pulsar Community meeting yesterday. The main dependency that hasn't been discussed here is our dependency on moving to Apache Bookkeeper version 4.15.0. That work is here: https://github.com/apache/pulsar/pull/15142. Also, the end goal should be to update our release procedure so that the release produces a multi-arch docker image. These are my notes from the meeting: > Michael: what needs to be done for an Arm docker image (https://github.com/apache/pulsar/issues/12944)? Matteo: need to get the go runtime for functions (that is easy). There are going to be conflicts in the Dockerfile because of removing Python 2. Python wheel files already have the script to build the Arm and the Intell files. We just need the Linux Intel and Linux Arm. Ideal state is that a release will have both images. Matteo doesn’t think CI should worry about this, but releases should. The build would specify the target arch. We’ll want to make sure that the release manager’s process is easy. Michael: is there anything about bookkeeper that should be optimized? Matteo: there are Linux Intel optimizations for the JNI. Therefore, it won’t be as fast on Arm. Bookkeeper would need to pack multiple shared libraries and cross compile for different target arch. Rocks DB does this. It makes the binary larger. That could be done in Bookkeeper. That isn’t a docker problem, though. Michael: do we need bookkeeper 4.15 for an Arm based docker image? Matteo: yes, and that is because we need it for the right Rocks DB version. Here is a link to the mailing list notes: https://lists.apache.org/thread/kpddnlm85yj9r3y16xol1v4778k1w5dy. -- 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]
